Difference between revisions of "1.3.6.1.4.1.19376.1.3.3.1.5"
| Line 7: | Line 7: | ||
This module is out of the XDS-Lab Specification and documented there in an <authenticator> element. This module does not change requirements stated in that specification but is structured as a module to ensure consistent content representation and re-usability. | This module is out of the XDS-Lab Specification and documented there in an <authenticator> element. This module does not change requirements stated in that specification but is structured as a module to ensure consistent content representation and re-usability. | ||
| − | |||
The figure below shows how the information for this element is coded, and further constraints are provided in the following sections. | The figure below shows how the information for this element is coded, and further constraints are provided in the following sections. | ||
Revision as of 14:01, 13 June 2008
Return to: PCC TF-1/PHLAB/XDSLAB Harmonization
Development Only
The PCC Wiki Content is used only for development of IHE PCC Content. The Normative content of the PCC Technical Framework and the current supplements can be found at http://www.ihe.net/Technical_Framework/index.cfm#PCC
Laboratory Result Verifier 1.3.6.1.4.1.19376.1.3.3.1.5
Laboratory Result Verifiers shall be recorded as authenticators in the CDA Header and as participants with typeCode equal to 'AUTHEN' in the structured body as demonstrated in the figure below. Laboratory result verification can be done in multiple levels of the document to reflect verification scope in the case where multiple Laboratory Result Verifiers participated in the validation of documents content. A verification of a single result will be documented at the observation level and will supersede verification entities at higher levels of the document (such as at the section or header level).
These participants shall conform to the General Constraints found in HL7 CRS: 2.1.1 with respect to the requirements for name, address, telephone numbers and other contact information.
This module is out of the XDS-Lab Specification and documented there in an <authenticator> element. This module does not change requirements stated in that specification but is structured as a module to ensure consistent content representation and re-usability.
The figure below shows how the information for this element is coded, and further constraints are provided in the following sections.
Uses
See Templates using Laboratory Result Verifier
Specification
<ClinicalDocument
...
<authenticator>
<templateId root="TBD"/>
<time value="20080124171911.0425-0500"/>
<signatureCode code="S"/>
<assignedEntity>
<id extension="274" root="1.19.6.11.13"/>
<addr>
<streetAddressLine>7000 Laboratory Drive</streetAddressLine>
<city>Chicago</city>
<state>IL</state>
<postalCode>60622</postalCode>
<country>USA</country>
</addr>
<telecom value="tel: 312-555-5555"/>
<assignedPerson>
<name>
<suffix>MT ASCP</suffix>
<family>Technologist</family>
<given>274</given>
</name>
</assignedPerson>
<representedOrganization>
<id extension="rm83747" root="1.19.6.11.13"/>
<name>Laboratory</name>
<telecom value="tel: 312-555-5555"/>
<addr>
<streetAddressLine>1234 Laboratory Drive</streetAddressLine>
<city>Chicago</city>
<state>IL</state>
<postalCode>60622</postalCode>
<country>USA</country></addr>
</representedOrganization>
</assignedEntity>
</authenticator>
...
<structuredBody>
...
<entry>
<act>
...
<entryRelationship>
<observation>
<participant typeCode='AUTHEN'>
<templateId root="TBD"/>
<time value="20080123211000.007-0500"/>
<participatRole>
<id extension="332" root="1.19.6.11.13"/>
<addr>
<streetAddressLine>
7000 Laboratory Drive
</streetAddressLine>
<city>Chicago</city>
<state>IL</state>
<postalCode>60622</postalCode>
<country>USA</country>
</addr>
<telecom value="tel: 312-555-5555"/>
<playingEntity>
<name>
<suffix>MT ASCP</suffix>
<family>Technologist</family>
<given>332</given>
</name>
</playingEntity>
</participatRole>
</observation>
</entryRelationship>
...
</act>
</entry>
...
</structuredBody>
|
@typeCode='AUTHEN'
In the body, the <participant> element representing a laboratory result verifier shall be present and shall be set to 'AUTHEN'.
<templateId root='1.3.6.1.4.1.19376.1.3.3.1.5/>
The <templateId> element identifies this <authenticator> as a laboratory result verifier. The templateId shall have root='1.3.6.1.4.1.19376.1.3.3.1.5'.
In the body, <templateId> element identifies a <participant> as a laboratory result verifier. The templateId shall have root='1.3.6.1.4.1.19376.1.3.3.1.5'.
<time/>
The
<signatureCode/>
In the case of the <authenticator>, the <signatureCode> element shall be present and shall have code='S' to indicate 'signed'.
<assignedEntity/> or <participatRole/>
An assignedEntity sub-element under the authenticator shall be present.
In the body, the participatRole under the participant shall be present.
<id/>
Unique identifier of this person/organization (lab result verifier) in the affinity domain shall be present.
<addr/>
The address of this person/organization (lab result verifier) shall be present.
<telecom/>
The telecom of this person/organization (lab result verifier) shall be present.
<name/>
In the case of the <authenticator>, either an <assignedPerson> or a <representedOrganization> shall be present. In either case, the <name> sub-element shall be present.
In the case of the <participatRole>, a <playingEntity> shall be present and it's <name> sub-element shall be present.