minimal Common Oncology Data Elements (mCODE) Implementation Guide, published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 4.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-mCODE-ig/ and changes regularly. See the Directory of published versions
You can also download:
The source code for this Implementation Guide can be found on HL7 GitHub https://github.com/HL7/fhir-mCODE-ig.
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.us.mcode.r4) and R4B (hl7.fhir.us.mcode.r4b) are available.
IG | Package | FHIR | Comment |
---|---|---|---|
minimal Common Oncology Data Elements (mCODE) Implementation Guide | hl7.fhir.us.mcode#4.0.0-ballot | R4 | |
HL7 Terminology (THO) | hl7.terminology.r4#6.0.2 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
Genomics Reporting Implementation Guide | hl7.fhir.uv.genomics-reporting#2.0.0 | R4 | |
FHIR Extensions Pack | hl7.fhir.uv.extensions#5.1.0-cibuild | R5 | |
HL7 Terminology (THO) | hl7.terminology.r5#5.3.0 | R5 | |
US Core Implementation Guide | hl7.fhir.us.core#6.1.0 | R4 | |
HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 | |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 | |
Bulk Data Access IG | hl7.fhir.uv.bulkdata#2.0.0 | R4 | |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.1.0 | R4 | |
VSAC | us.nlm.vsac#0.11.0 | R4 | |
Structured Data Capture | hl7.fhir.uv.sdc#3.0.0 | R4 | |
PHINVads | us.cdc.phinvads#0.12.0 | R4 | |
IHE FormatCode Vocabulary | ihe.formatcode.fhir#1.1.0 | R4 |
Package hl7.fhir.uv.genomics-reporting#2.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, May 9, 2022 16:52+0000+00:00) |
Package hl7.fhir.uv.extensions#5.1.0-cibuild This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Mar 12, 2024 13:29+1100+11:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00) |
Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. |
Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00) |
Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00) |
There are no Global profiles defined
This publication includes IP covered under the following statements.