⚠️ 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.

4. Downloads

Packages serve as the principal distribution mechanism for sets of profiles and are the recommended method for resource versioning. The fhir.onc.ctm package includes all essential components of this IG.

At this stage, this IG contains two CapabilityStatements as its downloadable conformance artifacts. These describe how the actor systems are expected to implement and interact with each other. Examples will follow in subsequent releases.

This guide does not define its own profiles. Instead, it reuses the profiles published in its package dependencies. These profiles are listed on the Data Mapping page.

4.1. Dependencies

This Implementation Guide relies on the following package dependencies:

• test.fhir.onc.ctm 0.1.0
• hl7.fhir.us.core 6.1.0
• hl7.fhir.r4.core 4.0.1
• hl7.fhir.uv.bulkdata 2.0.0
• hl7.fhir.uv.smart-app-launch 2.1.0
• us.nlm.vsac 0.11.0
• hl7.fhir.uv.sdc 3.0.0
• hl7.fhir.r4.examples 4.0.1
• us.cdc.phinvads 0.12.0
• ihe.formatcode.fhir 1.1.0
• hl7.fhir.us.mcode 4.0.0
• hl7.terminology.r4 6.2.0
• hl7.fhir.uv.extensions.r4 5.2.0
• hl7.fhir.uv.genomics-reporting 2.0.0

Ensure that these dependencies are downloaded and integrated into your system prior to implementing the CTM IG.

4.2. Usage

The package provides the conformance resources of this IG, which for instance can be:

• Used as a reference when designing and implementing the actor systems described in the CapabilityStatements.
• Deployed in specialized environments, such as a local FHIR server or validation engine, to ensure compliance and interoperability.
• Combined with the package dependencies to resolve and validate against the profiles that this IG reuses.
• Employed to populate your system with example test data, facilitating development and testing activities.

4.2.1. Manual Download and Unpacking

Packages can be manually downloaded via the Simplifier interface here. Once downloaded, unpack the files for use.

4.2.2. NPM

The npm command can be used for downloading and installing FHIR packages. Documentation is available here.

4.2.3. Firely Terminal

Firely Terminal functions as a FHIR package manager and facilitates easy package installation. Installation guidance and usage examples can be found here.