⚠️ This is a developmental version of the guide and is under active development. Content may change at any time without notice. No official release has been made. The final base canonical URL and hosting location have not yet been determined. This guide should not be used for production implementations.

3.1. CapabilityStatement

These CapabilityStatements apply primarily to Sponsor-initiated Trial Matching, where the CTM Matching Service acts as a FHIR client and the Provider FHIR Server acts as a FHIR server. They summarize the FHIR requirements for that exchange pattern.

They should not be read as the primary conformance artifacts for Provider-initiated Trial Matching, which is a CDS Hooks-based workflow described elsewhere in this guide.

• In Provider-initiated Trial Matching, the primary interaction is a CDS Hooks workflow. The Provider System acts as the CDS Client, discovers the CTM service at {baseURL}/cds-services, sends the CDS Hooks request, and receives CDS Hooks cards in response. In this pattern, the CTM service is not necessarily a FHIR server, and the main conformance guidance is described in the Provider-intiated Trial Matching narrative, CDS Hooks discovery guidance, prefetch guidance, and example request/response payloads.

• In Sponsor-initiated Trial Matching, the primary interaction is a FHIR RESTful exchange. The CTM Matching Service acts as the FHIR client, and the Provider FHIR Server acts as the FHIR server. The CapabilityStatements in this section are primarily intended to describe that pattern.

Accordingly, the CapabilityStatements below should be read mainly as Sponsor-Initiated conformance artifacts. The Provider-initiated scenario remains important, but its primary conformance artifacts are the workflow narrative, CDS Hooks discovery/service examples, prefetch guidance, and CTM card guidance rather than FHIR REST CapabilityStatements. CDS Hooks itself defines the client/service model, discovery endpoint, prefetch mechanism, and card-based response pattern.

Name	Description	Canonical
CTMMatchingService	Requirements for the CTM Matching Service participating in USCDI+ CTM. This CapabilityStatement primarily applies to Sponsor-initiated Trial Matching, where the CTM Matching Service acts as a FHIR RESTful client and retrieves CTM-relevant data from a Provider FHIR Server. In Provider-initiated Trial Matching, the CTM Matching Service acts as a CDS Hooks service and responds to requests from the Provider System; that CDS Hooks behavior is described elsewhere in this guide and is not fully represented by this CapabilityStatement.	http://fhir.org/guides/onc/ctm/CapabilityStatement/CTMMatchingService
CTMProviderFHIRServer	Requirements for the Provider FHIR Server participating in USCDI+ CTM. This CapabilityStatement primarily applies to Sponsor-initiated Trial Matching, where the Provider FHIR Server acts as the FHIR RESTful server and responds to requests initiated by the CTM Matching Service. In Provider-initiated Trial Matching, the Provider System acts as the CDS Hooks client and may use the Provider FHIR Server internally to prepare CTM-relevant input data; that CDS Hooks-based behavior is described elsewhere in this guide and is not fully represented by this CapabilityStatement.	http://fhir.org/guides/onc/ctm/CapabilityStatement/CTMProviderFHIRServer