This page is part of the CCDA: Consolidated CDA Release (v3.0.0-ballot: CCDA 3.0 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. . For a full list of available versions, see the Directory of published versions
Full Implementation Guide
The entire implementation guide (including the HTML files, definitions, validation information, etc.) may be downloaded here.
In addition there are format specific definitions files.
Examples: all the examples that are used in this Implementation Guide available for download:
IG | Package | FHIR | Comment |
---|---|---|---|
Consolidated CDA | hl7.cda.us.ccda#3.0.0-ballot | R5 | |
HL7 Terminology (THO) | hl7.terminology.r5#5.3.0 | R5 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r5#1.0.0 | R5 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack |
Clinical Document Architecture | hl7.cda.uv.core#2.0.0-sd-snapshot1 | R5 | |
HL7 Terminology (THO) | hl7.terminology#5.2.0 | R4 | |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 | |
us.nlm.vsac#0.17.0 | R4 | ||
us.cdc.phinvads#0.12.0 | R4 | ||
US Core Implementation Guide | hl7.fhir.us.core#7.0.0-ballot | R4 | |
HL7 Terminology (THO) | hl7.terminology.r4#5.3.0 | R4 | |
Bulk Data Access IG | hl7.fhir.uv.bulkdata#2.0.0 | R4 | |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.0.0 | R4 | |
Structured Data Capture | hl7.fhir.uv.sdc#3.0.0 | R4 | |
FHIR R4 package : Examples | hl7.fhir.r4.examples#4.0.1 | R4 | |
IHE FormatCode Vocabulary | ihe.formatcode.fhir#1.1.0 | R4 | |
FHIR Extensions Pack | hl7.fhir.uv.extensions#5.1.0-ballot1 | R5 |
Package hl7.fhir.uv.extensions.r5#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.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.r4.examples#4.0.1 Example resources in the R4 version of the FHIR standard |
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.uv.extensions#5.1.0-ballot1 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Dec 19, 2023 08:38+1100+11:00) |
Package hl7.fhir.us.core#7.0.0-ballot 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 Tue, Dec 19, 2023 21:01+0000+00:00) |
There are no Global profiles defined
This publication includes IP covered under the following statements.