USCDI+ Clinical Trials Matching Implementation Guide
0.1.0
⚠️ 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.
This section includes example FHIR instances that illustrate how clinical data relevant to clinical trial matching may be represented using existing US Core and mCODE examples. These examples are pulled directly from US Core and mCODE example instances and are included here to help implementers understand how data commonly needed for CTM workflows may already appear in standards-based FHIR resources. They are not intended to introduce new CTM requirements or to define a required payload structure for trial matching. Instead, they show how existing US Core and mCODE representations can support CTM use cases when exchanged or referenced as part of Provider-initiated or CTM Service-initiated trial matching workflows.
The examples include representative patient, condition, procedure, observation, and medication-related resources. Together, they demonstrate how information such as demographics, cancer diagnoses, prior procedures, treatment history, smoking status, pregnancy status, laboratory results, cancer staging, performance status, comorbidities, TNM categories, and medication administration may be represented using existing US Core and mCODE patterns.
Implementers should use these examples as helpful reference material when designing, testing, or validating CTM-related exchanges. The applicable conformance requirements remain those defined by the relevant profiles, value sets, CapabilityStatements, and workflow guidance elsewhere in this implementation guide.