TO CDA R2 there is a need to communicate information for which there is no suitable representation in CDA R2, extensions to CDA R2 have been developed. These extensions are described above in the context of the section where they are used. This section serves to summarize the extensions and provide implementation guidance. Extensions in this guide include: sdtc:raceCode—The raceCode extension allows for multiple races to be reported for a patient. sdtc:deceasedInd—The deceasedIndextension (= or in the family “true” “false”) history organizer on the related subject is used inside to indicate if a family member is deceased. sdtc:deceasedTime—The deceasedTime extension in the family history organizer on the related subject allows for reporting the date and time a family member died. sdtc:birthTime—The <sdtc:birthTime> element allows for the date of any person to be recorded. The purpose of this extension is to allow the recording of the subscriber or member of a health plan in cases where the health plan eligibility system has different information on file than the provider does for the patient. To resolve issues that need to be addressed by extension, the developers of this guide chose to approach extensions as follows: An extension is a collection of element or attribute declarations and rules for their application to the CDA Release 2.0. single namespace for all extension elements or attributes that may be used by this guide will be defined. The namespace for extensions created by the HL7 Structured Documents Working Group (formerly Structured Documents Technical Committee) shall be urn:hl7-org:sdtc. This namespace shall be used as the namespace for any extension elements or attributes that are defined by this implementation guide. Each extension element shall use the same HL7 vocabularies and data types used by CDA Release 2.0. Each extension element shall use the same conventions for order and naming as is used by the current HL7 tooling. An extension element shall appear in the XML where the expected RIM element of the same name would have appeared had that element not been otherwise constrained from appearing in the CDA XML schema.
TO CDA R2 there is a need to communicate information for which there is no suitable representation in CDA R2, extensions to CDA R2 have been developed. These extensions are described above in the context of the section where they are used. This section serves to summarize the extensions and provide implementation guidance. Extensions in this guide include: sdtc:raceCode—The raceCode extension allows for multiple races to be reported for a patient. sdtc:deceasedInd—The deceasedIndextension (= “true” or “false”) in the family history organizer on the related subject is used inside to indicate if a family member is deceased. sdtc:deceasedTime—The deceasedTime extension in the family history organizer on the related subject allows for reporting the date and time a family member died. sdtc:birthTime—The <sdtc:birthTime> element allows for the date of any person to be recorded. The purpose of this extension is to allow the recording of the subscriber or member of a health plan in cases where the health plan eligibility system has different information on file than the provider does for the patient. To resolve issues that need to be addressed by extension, the developers of this guide chose to approach extensions as follows: An extension is a collection of element or attribute declarations and rules for their application to the CDA Release 2.0. single namespace for all extension elements or attributes that may be used by this guide will be defined. The namespace for extensions created by the HL7 Structured Documents Working Group (formerly Structured Documents Technical Committee) shall be urn:hl7-org:sdtc. This namespace shall be used as the namespace for any extension elements or attributes that are defined by this implementation guide. Each extension element shall use the same HL7 vocabularies and data types used by CDA Release 2.0. Each extension element shall use the same conventions for order and naming as is used by the current HL7 tooling. An extension element shall appear in the XML where the expected RIM element of the same name would have appeared had that element not been otherwise constrained from appearing in the CDA XML schema.