Specification - Extended HL7 CDA® R2 Implementation Guide: Public Health Case Report, Release 2: the Electronic Initial Case Report (eICR), Release 1, STU Release 1.1 - US Realm
Document Description extended per TSC Tracker 12574, extension TSC GF 15952, JIRA TSC-29, TSC-123
Existing WordingInitial Case Report Trigger Code Result Observation (urn:hl7ii:2.16.840.1.1138188.8.131.52.2.3.2:2016-12-01) This template is based on the C-CDA R2.1 template Result Observation (V3) and further constrained. code/@code is further constrained to be: This code SHALL contain exactly one [1..1] @code, which MAY be selected from ValueSet Trigger code for laboratory test names (RCTC subset) urn:oid:2.16.840.1.1137184.108.40.2066.42 DYNAMIC (CONF:3284-305). It also states: "Either code or value or both shall contain a trigger code". This template can either contain a trigger code in the code (e.g. lab test name) and/or a trigger code in the value (e.g. result of test: organism or substance). This means that an eICR can either be triggered on a particular lab test code or an organism or substance that is detected as a result of that test. However, the following, which is allowed in the base Result Observation template, is disallowed by the eICR template:
Stool Culture This should be allowed.
Proposed WordingUpdate CONF:3284-305 This code SHOULD (or MAY) contain exactly one [1..1] @code, which MAY be selected from ValueSet Trigger code for laboratory test names (RCTC subset) urn:oid:2.16.840.1.1137220.127.116.116.42 DYNAMIC (CONF:3284-305). Using SHOULD instead of SHALL would allow not using a code, but it would throw a Schematron warning. Using MAY instead of SHALL would allow not using a code and would not throw any warnings. Need to decide on which of the above is desirable for the disposition. Could also constrain the values allowed for nullFlavor (maybe just "OTH"?).