0.1.0 - ci-build
MatchSyncIG - Local Development build (v0.1.0). See the Directory of published versions
IG | Package | FHIR | Comment |
---|---|---|---|
MatchSyncIG | nmdp.fhir.matchsync#0.1.0 | R4 | |
HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
US Core Implementation Guide | hl7.fhir.us.core#4.0.0 | R4 | |
FHIR Bulk Data Access | hl7.fhir.uv.bulkdata#1.0.1 | R4 | |
us.nlm.vsac#0.3.0 | R4 | ||
minimal Common Oncology Data Elements (mCODE) Implementation Guide | hl7.fhir.us.mcode#2.0.0 | R4 | |
US Core Implementation Guide | hl7.fhir.us.core#4.0.0 | R4 | |
Genomics Reporting Implementation Guide | hl7.fhir.uv.genomics-reporting#2.0.0 | R4 |
Package hl7.fhir.uv.bulkdata#1.0.1 |
Package us.nlm.vsac#0.3.0 |
Package hl7.fhir.us.core#4.0.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 Mon, Jun 28, 2021 19:09+0000+00:00) |
Package hl7.fhir.us.core#4.0.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 Mon, Jun 28, 2021 19:09+0000+00:00) |
Package hl7.fhir.us.mcode#2.0.0 mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records. (built Tue, Jan 18, 2022 03:16+0000+00:00) |
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) |
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 (nmdp.fhir.matchsync.r4) and R4B (nmdp.fhir.matchsync.r4b) are available.
There are no Global profiles defined
This publication includes IP covered under the following statements.