CDA+-+Header+Analysis

Header Status

 * || **Commented CCD** || **Commented HITSP/IHE** || **Draft Publication** || **Developer** || **"QA-er"** || **Projected Date** ||
 * **CDA Header** || QA Completed || [|QA Completed (3/29)] ||  ||   ||   ||   ||
 * Note:** To download Commented CCD or Commented HITSP/IHE XML files, please right click the link and choose “save link as...”

Header Decisions
Click here to view the resolved header issues which were removed from the Active Harmonization Issues tracker after resolution was achieved. Click here to view the actRelationship Proposals for the header consolidation. Will add guidance in introductory portion of IG that unless otherwise specified, a SHALL requirement allows a nullFlavor. We will add clarification that any contact information is acceptable. || Further decided to raise the VA’s validator error to NIST to resolve. Click here for the response from NIST. || A new value set of telecom types will be created. ||  ||   ||
 * **Element** || **U.S. Realm CDA Header** || **Document Specific Requirements** || **Comments** ||
 * clinicalDocument.id || Allow for both OID and UUID as the clinicalDocument.id || The Diagnostic Imaging Report (DIR) will restrict the id to OID. ||  ||
 * ..clinicalDocument.effectiveTime || Element SHALL be precise to the day and SHOULD be precise to the minute ||  || Took the action item to review the relationship of time zone precision to effectiveTime in the guides that are in scope. ||
 * ..recordTarget || 1..* ||  ||   ||
 * .......recordTarget.id || 1..* ||  ||   ||
 * .......recordTarget.addr || 1..* ||  || **Issue:** V.A.-1 ||
 * .......recordTarget.telecom || Element SHALL be present, but that it could be nullFlavor ||  || **Issue:** V.A.-2
 * ............recordTarget.administrativeGenderCode || Adopt HL7 administrativeGenderCode value set ||  || **Issue:** V.A.-4
 * ............recordTarget.birthTime || Adopt H&P birthTime constraint from CONF.-32 ||  || **Issue:** V.A.-5 ||
 * ............recordTarget.languageCommunication || 1..* ||  || Further decided to include implementation guidance regarding NULL flavors (in case it is unknown). ||
 * .................recordTarget.proficiencyLevelCode || 0..1 ||  ||   ||
 * "Name" || Include additional constraints from C83 2.2.2.1.1 “Patient Name Constraints” section (statements 1-6 are good candidates) ||  || **Issue:** V.A.-3 ||
 * "Address" || Include additional conformance testable constraints from C83 2.2.2.1.2 “Address Constraints” section ||  ||   ||
 * "Telecom" || Include additional constraints from C83 2.2.2.1.3 “Person Phone/Email/URL Constraints”