Consolidated CDA (C-CDA) 1.1 and 2.1
This DECOR project is part of the HL7 Templates Work Group project that defined a generic template exchange format (Templates DSTU, see: HL7 Templates Standard: Specification and Use of Reusable Information Constraint Templates, Release 1) for various template creation suites. It must be noted that this setup is an amalgamation of C-CDA 1.1 and 2.1: Templates and Value Sets are labeled appropriately with "1.1" or "2.1" respectively but appear as versions of each other. Unlike Lantana's Trifolia Workbench that has an implementation guide viewpoint, the ART-DECOR library here looks at versions of the different document level templates with all subsequent and referenced templates and value sets. It acts as a Building Block Repository (BBR) that allows easy re-use of template s and value sets.Conversions from Lantana's Trifolia Workbench
The templates and value sets for 1.1 and 2.1 in this decor project are tranformations from the proprietary export format of the Trifolia Workbench. They have been revised and corrected manually to fit the requirements of the Templates DSTU and to allow proper schematron generation. Please note that parts of the Trifolia Workbench maybe copyrighted by Lantana Consulting Group (see http://www.lantanagroup.com)Status
Please note that definitions here may be IN REVIEW STATUS.
The "source of truth" are the C-CDA specifications from HL7 International.
IMPORTANT NOTES
HL7 licenses its standards and select IP free of charge. If you did not acquire a free license from HL7 for this document, you are not authorized to access or make any use of it. To obtain a free license, please visit http://www.HL7.org/implement/standards/index.cfm.If you are the individual that obtained the license for this HL7 Standard, specification or other freely licensed work (in each and every instance "Specified Material"), the following describes the permitted uses of the Material.
A. HL7 INDIVIDUAL, STUDENT AND HEALTH PROFESSIONAL MEMBERS, who register and agree to the terms of HL7’s license, are authorized, without additional charge, to read, and to use Specified Material to develop and sell products and services that implement, but do not directly incorporate, the Specified Material in whole or in part without paying license fees to HL7.
INDIVIDUAL, STUDENT AND HEALTH PROFESSIONAL MEMBERS wishing to incorporate additional items of Special Material in whole or part, into products and services, or to enjoy additional authorizations granted to HL7 ORGANIZATIONAL MEMBERS as noted below, must become ORGANIZATIONAL MEMBERS of HL7.
B. HL7 ORGANIZATION MEMBERS, who register and agree to the terms of HL7's License, are authorized, without additional charge, on a perpetual (except as provided for in the full license terms governing the Material), non-exclusive and worldwide basis, the right to (a) download, copy (for internal purposes only) and share this Material with your employees and consultants for study purposes, and (b) utilize the Material for the purpose of developing, making, having made, using, marketing, importing, offering to sell or license, and selling or licensing, and to otherwise distribute, Compliant Products, in all cases subject to the conditions set forth in this Agreement and any relevant patent and other intellectual property rights of third parties (which may include members of HL7). No other license, sublicense, or other rights of any kind are granted under this Agreement.
C. NON-MEMBERS, who register and agree to the terms of HL7’s IP policy for Specified Material, are authorized, without additional charge, to read and use the Specified Material for evaluating whether to implement, or in implementing, the Specified Material, and to use Specified Material to develop and sell products and services that implement, but do not directly incorporate, the Specified Material in whole or in part.
NON-MEMBERS wishing to incorporate additional items of Specified Material in whole or part, into products and services, or to enjoy the additional authorizations granted to HL7 ORGANIZATIONAL MEMBERS, as noted above, must become ORGANIZATIONAL MEMBERS of HL7.
Please see http://www.HL7.org/legal/ippolicy.cfm for the full license terms governing the Material.
Technical corrections based on issues signalled by variuos sources and an internal ART-DECOR expert group review process to address problems raised in conjunction with the DSTU HL7 Templates Standard: Specification and Use of Reusable Information Constraint Templates, Release 1
- Added datatype CS to various elements like statusCode etc
- Review of all assert statements: it seems that the original asserts all uses the context of the top element of the respective template where they are mentioned while there hierarchical position is nested in an element. E.g. an assert aiming on a @value attribute in a cda:time element in an cda:performer element in an cda: observation and positioned within the cda:performer element had originally the xpath cda:performer/cda:time/@value. Asserts following the Templates DSTU R1 inherit their context from the element where they are mentioned in, so the correct xpath for this example is simply @value
- The 191 original assert has been brought down to 124 due to the possibility to explicitly express choices, some of the asserts where expressed as cardinality constraints rather than an assert
- Errors in xpath expressions of the asserts have been correct, like "not(informant) or informant/cda:*/addr" to "not(cda:informant) or cda:informant/cda:*/cda:addr"
-
The stdc: extensions have been explicitly included as an element definition rather an assert statement with a constrain that would have failed anyway. In essence sdtc:raceCode in patient, sdtc:id in relatedSubject/subject, sdtc:deceasedInd and sdtc:deceasedTime in subject, sdtc:birthTime in associatedPerson and sdtc:dischargeDispositionCode in encounter; a good summary of CDA R2 stdc extensions can be found at http://motorcycleguy.blogspot.de/2012/06/extending-cda-for-qrda.html, the list of all CDA R2 extensions is summarized at http://wiki.hl7.org/index.php?title=CDA_R2_Extensions
- In template "2.16.840.1.113883.10.20.22.4.18" (MedicationDispense) the assert the checks US addresses was checking an incorrect path
- Added datatype CS to every relevant element in all templates (realmCode, languageCode, statusCode). This causes derived schematron rules to only consider attribute @code
Minor fixes:
-
Set PolicyActivity Template 2.16.840.1.113883.10.20.22.4.61 to open (closed would never work due to incomplete definitions)
-
Fixed a typo in Xpath expression in a schematron assert
- Add missing building block repository reference ad2bbr-, and added value set reference that caused value set ResponsibleParty to be unresolvable.
- Add missing value set Medication Product Form (2.16.840.1.113883.3.88.12.3221.8.11)
- Replaced context path cda:ClinicalDocument with // to indicate that the document might be wrapped by something else. The cda:ClinicalDocument path was actually causing a duplicate path indicator as the root element was also ClinicalDocument.