The C-CDA on FHIR Implementation Guide is a US Realm Implementation Guide of the FHIR Specification addressing the key aspects of Consolidated CDA (C-CDA) required for Meaningful Use (MU). This IG publication release focuses on providing data mappings for problems, allergies, medications, immunization, patient and procedures (PAMI+), and results, vitals, encounters, and social determinants of health. The clinical document header and document guidance from the earlier publications have not been updated since 2020.
descmd
The C-CDA on FHIR Implementation Guide is a US Realm Implementation Guide of the FHIR Specification addressing the key aspects of Consolidated CDA (C-CDA) required for Meaningful Use (MU). This IG publication release focuses on providing data mappings for problems, allergies, medications, immunization, patient and procedures (PAMI+), and results, vitals, encounters, and social determinants of health. The clinical document header and document guidance from the earlier publications have not been updated since 2020.
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'In addition to the context of the previous section, CDA often requires elements to be present but the usage of a null value (@nullFlavor) is allowed. Generally when a CDA element is required (i.e. SHALL [1..1]), implementers will need to do one of the following when converting data into CDA:' (1 uses)
Draft is there
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/condition-category|0.5.0 (2 uses)
Illustrative OID not available for validation in tx.fhir.org as used in C-CDA examples: https://cdasearch.hl7.org/examples/view/Problems/Problem%20Value%2C%20Translation%2C%20Qualifier%20examples This is deliebrately used in this guide to illustrate OID to urn:oid conversion in C-CDA to FHIR when URL is unavailable.
A definition for CodeSystem 'urn:oid:2.16.840.1.113883.3.247.1.1' could not be found, so the code cannot be validated (2 uses)
These are example identifiers with arbitrary identifier systems. There is no reason the validator should know them.
No definition could be found for URL value 'urn:oid:1.3.6.1.4.1.22812.3.2009316.3' (1 uses)
No definition could be found for URL value 'urn:oid:1.3.6.1.4.1.22812.3.2009316.3.4.1.2.1' (2 uses)
No definition could be found for URL value 'urn:oid:1.3.6.1.4.1.22812.3.2009316.3.4.10.2' (4 uses)
No definition could be found for URL value 'urn:oid:1.3.6.1.4.1.22812.3.2009316.3.4.7' (2 uses)
No definition could be found for URL value 'urn:oid:2.16.840.1.113883.19.5.9999.456' (1 uses)
This guide addresses current regulations. Any party interested in future work is invited to participate.
The ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 8.0.1. This reference is getting old and the more recent version should be considered (1 uses)
The ImplementationGuide uses package hl7.fhir.uv.extensions.r4#5.1.0 released on 2024-04-27, but the most recent appropriate version is 5.2.0. This reference is getting old and the more recent version should be considered (1 uses)
This is a validator issue, not an IG issue
Source Code System http://loinc.org is only supported on the terminology server, so the source codes are not validated for performance reasons (2 uses)
Source Code System http://snomed.info/sct is only supported on the terminology server, so the source codes are not validated for performance reasons (8 uses)
Target Code System http://loinc.org is only supported on the terminology server, so the target codes are not validated for performance reasons (2 uses)
Target Code System http://snomed.info/sct is only supported on the terminology server, so the target codes are not validated for performance reasons (7 uses)