Specification - Extended

HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes DSTU Release 2.1 - US Realm

Document Description

extended per extended per TSC tracker 12437, again with 14128 and jira.hl7.org/browse/TSC-38

Existing Wording

We have seen real-world implementation defects where planned future encounters appear in the Encounters section rather than the Plan of Treatment section where they should be. I think some developers are just querying their database encounter tables for all encounters for a particular patient and sticking everything in the Encounters section regardless of whether they are past or future. Let's introduce a new conformance rule to ensure each Encounter activity ends before the document header effectiveTime. ---------- 3.22 Encounter Activity (V3) [encounter: identifier urn:hl7ii:2.16.840.1.113883.10.20.22.4.49:2015-08-01 (open)] ... 6. SHALL contain exactly one [1..1] effectiveTime (CONF:1198-8715).

Proposed Wording

6. SHALL contain exactly one [1..1] effectiveTime (CONF:1198-8715). The effectiveTime/high/@value SHALL be on or before the document header /ClinicalDocument/effectiveTime/high/@value.