Item | DT | Card | Conf | Description | Label |
---|
hl7:ClinicalDocument
| | | | | XeHLport |
hl7:realmCode
| CS | 0 … 1 | | This element SHOULD be present and is valued from the RealmOfUse [2.16.840.1.113883.1.11.11050] subset, within the VocabularyDomainQualifier value set. In the international context of this profile used as it is without any further extension, the realm code SHALL be <realmCode code="UV"/> (universal). Whenever a national extension has been defined and is used, the realm code SHALL identify this national extension. | XeHLport |
| Example | Example for a French extension <realmCode code="FR"/> |
hl7:typeId
| II | 1 … 1 | M | This element is a technology-neutral explicit reference to the standard CDA R2. It SHALL be present and valued as follows: ClinicalDocument/typeId@root = "2.16.840.1.113883.1.3" (which is the OID for HL7 Registered models); ClinicalDocument.typeId@extension = "POCD_HD000040" (which is the unique identifier for the CDA, Release Two Hierarchical Description). | XeHLport |
@root
| uid | 1 … 1 | F | 2.16.840.1.113883.1.3 |
@extension
| st | 1 … 1 | F | POCD_HD000040 |
hl7:templateId
| II | 1 … 1 | M | This element is identifying the set of constraints applied to the CDA R2 standard by this specification of a laboratory report. | XeHLport |
@root
| uid | 1 … 1 | F | 2.16.840.1.113883.3.1937.99.61.67.10.9 |
hl7:templateId
| II | 0 … * | | This element is identifying the set of constraints applied to the CDA R2 standard by this specification of a laboratory report. | XeHLport |
@root
| uid | 0 … 1 | F | 1.3.6.1.4.1.19376.1.3.3 |
hl7:id
| II | 1 … 1 | M | ClinicalDocument/Id SHALL be present. It represents the unique instance identifier of the clinical document. The combination of the root and extension attributes SHALL provide a globally unique identifier, in accordance with CDA R2, without further constraints. | XeHLport |
| Example | Example using the extension attribute <id root="1.3.6.1.4.1.19376.1.3.4" extension="abc2"/> |
| Example | Example without the extension attribute <!-- In this case the OID populated in the root attribute is the unique instance identifier itself (The OID in this example is constructed from the OID dedicated to all examples in IHE LAB TF: 1.3.6.1.4.1.19376.1.3.4)--> <id root="1.3.6.1.4.1.19376.1.3.4.1232669"/> |
hl7:code
| CE | 1 … 1 | M | ClinicalDocument/code SHALL be present. The laboratory report can be either a multi-disciplinary report or a single discipline report. Multi-disciplinary Laboratory Report: The LOINC code identifying the type of document as a (potentially) multidisciplinary laboratory report (presenting results from many specialties) is: <code codeSystem="2.16.840.1.113883.6.1" codeSystemName=”LOINC” code="11502-2" displayName="LABORATORY REPORT.TOTAL"/> Single Discipline Laboratory Report: Use the appropriate LOINC code as listed in Value-Set “Laboratory Specialties”. | XeHLport |
| CONF | |
hl7:title
| ST | 1 … 1 | M | | XeHLport |
hl7:effectiveTime
| TS | 1 … 1 | R | ClinicalDocument/effectiveTime SHALL be present. It contains the creation date & time of the laboratory report as an electronic document. In case this is a new revision replacing a previous version (identified in parentDocument), this is the date & time of the new revision. | XeHLport |
| Example | <effectiveTime value="20080624131933.0000-0500"/> |
hl7:confidentialityCode
| CE | 1 … 1 | R | | XeHLport |
hl7:languageCode
| CS | 1 … 1 | R | | XeHLport |
| Example | Example of a report authored in American English <languageCode code="en-US"/> |
| Example | Example of a report authored in French <languageCode code="fr-FR"/> |
hl7:setId
| II | 1 … 1 | M | ClinicalDocument/setId SHALL be present to enable further updates of the clinical document. It is an identifier that is common across all revisions of this laboratory report. | XeHLport |
| Example | <setId root="1.3.6.1.4.1.19376.1.3.4" extension="abc2"/> |
hl7:versionNumber
| INT | 0 … 1 | | ClinicalDocument/versionNumber MAY be present. As requested by the CDA standard, it is an integer value used as versioning. | XeHLport |
Choice | 1 … * | | The base XD-LAB report template covers three varieties of laboratory reports: - Human (patient): The document reports laboratory observations produced on specimens collected exclusively from the patient.
- Non-Human Subject: The document reports laboratory observations produced on specimens collected from a non-human material (e.g., water, milk, etc.) or living subject (e.g., animal).
- Human (patient) paired with Non-Human Subject: The document reports laboratory observations produced on a non-human specimen with a relationship to a human patient (e.g., peanut butter eaten by a patient, a ferret that bit a patient).
This template limits the choice to Human subjects. Elements to choose from: |
Included | 0 … * | | from 1.3.6.1.4.1.19376.1.3.3.1.1 Human Patient (DYNAMIC)
Human (patient): The document reports laboratory observations produced on specimens collected exclusively from the patient. All persons (including the patient) and organizations mentioned in the document SHALL provide elements name, addr and telecom. |
hl7:recordTarget
| | 0 … * | R | | Humarget |
hl7:patientRole
| | 1 … 1 | R | | Humarget |
hl7:id
| II | 1 … * | R | | Humarget |
hl7:addr
| AD | 1 … * | | All persons (including the patient) and organizations mentioned in the document SHALL provide elements name, addr and telecom. | Humarget |
hl7:telecom
| TEL | 1 … * | | All persons (including the patient) and organizations mentioned in the document SHALL provide elements name, addr and telecom. | Humarget |
hl7:patient
| | 1 … 1 | | | Humarget |
hl7:id
| II | 0 … 1 | | | Humarget |
hl7:name
| PN | 1 … * | | | Humarget |
hl7:administrativeGenderCode
| CE | 1 … 1 | R | | Humarget |
hl7:birthTime
| TS | 1 … 1 | R | | Humarget |
Included | | NP | from 1.3.6.1.4.1.19376.1.3.3.1.2 Non-Human Subject (DYNAMIC)
Non-Human Subject: The document reports laboratory observations produced on specimens collected from a non-human material (e.g., water, milk, etc.) or living subject (e.g., animal). |
hl7:recordTarget
| | 1 … * | NP | | Nonhrget |
@typeCode
| cs | 0 … 1 | F | RCT |
@contextControlCode
| cs | 0 … 1 | F | OP |
hl7:templateId
| II | 1 … 1 | M | | Nonhrget |
@root
| uid | 1 … 1 | F | 1.3.6.1.4.1.19376.1.3.3.1.2 |
hl7:patientRole
| | 1 … 1 | R | | Nonhrget |
@classCode
| cs | 0 … 1 | F | PAT |
hl7:id
| II | 1 … * | R | | Nonhrget |
hl7:patient
| | 1 … 1 | | | Nonhrget |
@classCode
| cs | 0 … 1 | F | PSN |
@determinerCode
| cs | 0 … 1 | F | INSTANCE |
@nullFlavor
| cs | 1 … 1 | F | OTH |
Included | | NP | from 1.3.6.1.4.1.19376.1.3.3.1.3 Human Patient with Non-Human Subject (DYNAMIC)
Human (patient) paired with Non-Human Subject: The document reports laboratory observations produced on a non-human specimen with a relationship to a human patient (e.g., peanut butter eaten by a patient, a ferret that bit a patient). |
hl7:recordTarget
| | 1 … * | NP | | Humarget |
hl7:templateId
| II | 1 … 1 | M | | Humarget |
@root
| uid | 1 … 1 | F | 1.3.6.1.4.1.19376.1.3.3.1.3 |
hl7:patientRole
| | 1 … 1 | R | | Humarget |
hl7:id
| II | 1 … * | R | | Humarget |
hl7:addr
| AD | 1 … * | | | Humarget |
hl7:telecom
| TEL | 1 … * | | | Humarget |
hl7:patient
| | 1 … 1 | | | Humarget |
hl7:id
| II | 0 … 1 | | | Humarget |
hl7:name
| PN | 1 … * | | | Humarget |
hl7:administrativeGenderCode
| CE | 1 … 1 | R | | Humarget |
hl7:birthTime
| TS | 1 … 1 | R | | Humarget |
Included | 1 … * | R | from 2.16.840.1.113883.3.1937.99.61.67.10.2 XeH CDA author (DYNAMIC)
The laboratory report can be authored by a software system or by a person or by both. The author/time element carries the date&time the laboratory report was produced.
|
hl7:author
| | 1 … * | R | | XeHSthor |
@typeCode
| cs | 0 … 1 | F | AUT |
@contextControlCode
| cs | 0 … 1 | F | OP |
| Example | <author> <time value="201212290600+0100"/> <assignedAuthor> <id root="2.16.840.1.113883.2.9.4.3.2" extension="RSSMRA00A01F205F" assigningAuthorityName="Ministero Economia e Finanze"/> <addr use="WP"> <streetAddressLine>Viale della Cristallina 3</streetAddressLine> <city>Bologna</city> <state>BO</state> <postalCode>40121</postalCode> <country>IT</country> </addr> <telecom use="WP" value="tel:+39-051-34343434"/> <assignedPerson> <name> <given>Paolo</given> <family>Rossi</family> </name> </assignedPerson> </assignedAuthor> <representedOrganization> <!-- template 'IPS CDA Organization' (dynamic) --> </representedOrganization></author> |
hl7:functionCode
| CE.IPS | 0 … 1 | R | | XeHSthor |
hl7:time
| TS.IPS.TZ | 1 … 1 | R | The author/time element represents the start time of the author’s participation in the creation of the clinical document. | XeHSthor |
| Example | <time value="201212290600+0100"/> |
hl7:assignedAuthor
| | 1 … 1 | R | | XeHSthor |
@classCode
| cs | 0 … 1 | F | ASSIGNED |
hl7:id
| II | 1 … * | R | Author Identifier(s) | XeHSthor |
@nullFlavor
| cs | 0 … 1 | | |
hl7:code
| CE.IPS (extensible) | 0 … 1 | R | A code, which identifies the profession/competence/specialty of the author when it is a person. | XeHSthor |
| CONF | |
| Example | <code code="221" codeSystem="2.16.840.1.113883.2.9.6.2.7" codeSystemName="ISCO" displayName="Medical doctors"/> |
hl7:addr
| AD.IPS | 1 … * | R | | XeHSthor |
| Example | <addr use="WP"> <streetAddressLine>Viale della Cristallina 3</streetAddressLine> <city>Bologna</city> <state>BO</state> <postalCode>40121</postalCode> <country>IT</country></addr> |
hl7:telecom
| TEL.IPS | 1 … * | R | | XeHSthor |
@use
| set_cs | 0 … 1 | | |
| CONF | |
@value
| st | 0 … 1 | | |
| Example | <telecom use="WP" value="tel:+39-051-34343434"/> |
| Example | <telecom nullFlavor="NI"/> |
Choice | 1 … 1 | | Elements to choose from: |
hl7:assignedPerson
| | 0 … 1 | C | | XeHSthor |
@classCode
| cs | 0 … 1 | F | PSN |
@determinerCode
| cs | 0 … 1 | F | INSTANCE |
hl7:name
| PN | 1 … * | R | Name of the person (e.g. the Healthcare Professional) authoring this document | XeHSthor |
| Example | <name> <given>John</given> <family>Español Smith</family></name> |
hl7:family
| | 1 … * | R | | XeHSthor |
hl7:given
| | 1 … * | R | | XeHSthor |
hl7:assignedAuthoringDevice
| | 0 … 1 | C | Contains 2.16.840.1.113883.10.22.9.2 IPS CDA Device (DYNAMIC) | XeHSthor |
| Example | <assignedAuthoringDevice classCode="DEV" determinerCode="INSTANCE"> <softwareName displayName="Turriano"/></assignedAuthoringDevice> |
hl7:representedOrganization
| | 0 … 1 | R | Contains 2.16.840.1.113883.10.22.9.1 IPS CDA Organization (DYNAMIC) | XeHSthor |
Included | 1 … 1 | R | from 2.16.840.1.113883.3.1937.99.61.67.10.5 XeH CDA custodian (DYNAMIC)
It represents the organization that is in charge of maintaining the laboratory report. |
hl7:custodian
| | 1 … 1 | R | | XeHSdian |
@typeCode
| cs | 0 … 1 | F | CST |
| Example | <custodian typeCode="CST"> <assignedCustodian classCode="ASSIGNED"> <representedCustodianOrganization classCode="ORG" determinerCode="INSTANCE"> <!-- template 'IPS CDA Organization' (dynamic) --> </representedCustodianOrganization> </assignedCustodian></custodian> |
hl7:assignedCustodian
| | 1 … 1 | R | | XeHSdian |
@classCode
| cs | 0 … 1 | F | ASSIGNED |
hl7:representedCustodianOrganization
| | 1 … 1 | R | Contains 2.16.840.1.113883.10.22.9.1 IPS CDA Organization (DYNAMIC) | XeHSdian |
@classCode
| cs | 0 … 1 | F | ORG |
@determinerCode
| cs | 0 … 1 | F | INSTANCE |
Included | 0 … * | | from 2.16.840.1.113883.3.1937.99.61.67.10.15 XeH Information Recipient (DYNAMIC)
The informationRecipient/intendedRecipient element can be multiple. It introduces an intended recipient of the laboratory report, other than the Ordering Provider (described as a referrer participant). These elements carry the list of the originally intended recipients of the laboratory report, i.e., those who were known at the time the report was created and published for sharing.
|
hl7:informationRecipient
| | 0 … * | | | XeHSient |
hl7:templateId
| II | 1 … 1 | M | | XeHSient |
@root
| uid | 1 … 1 | F | 2.16.840.1.113883.3.1937.99.61.67.10.15 |
hl7:templateId
| II | 0 … * | R | | XeHSient |
hl7:intendedRecipient
| | 1 … 1 | R | | XeHSient |
hl7:id
| II | 0 … * | R | | XeHSient |
hl7:addr
| AD | 1 … * | | | XeHSient |
hl7:telecom
| TEL | 1 … * | | | XeHSient |
hl7:informationRecipient
| | 0 … 1 | | Contains 1.3.6.1.4.1.19376.1.3.10.9.18 PlayingEntity or person with Name (DYNAMIC) | XeHSient |
hl7:receivedOrganization
| | 0 … 1 | | Contains 1.3.6.1.4.1.19376.1.3.10.9.13 Organization with Name, Addr, Telecom (DYNAMIC) | XeHSient |
Included | 0 … 1 | | from 2.16.840.1.113883.3.1937.99.61.67.10.3 XeH CDA legalAuthenticator (DYNAMIC)
This element carries the person who has legally authenticated the report, and the organization represented by this person. The sub-element time carries the date&time this legal authentication took place. The sub-element signatureCode carries the “signed” (S) status If this entity happens also to be one of the validators of the laboratory results in the report, it SHALL also be documented as a validator. |
hl7:legalAuthenticator
| | 0 … 1 | R | | XeHSator |
| Example | <legalAuthenticator> <time value="20111013150937-0800"/> <signatureCode code="S"/> <assignedEntity> <id extension="admin" root="2.16.17.710.780.1000.903.1.1.3.3"/> <assignedPerson> <name> <given>John</given> <family>Español Smith</family> </name> </assignedPerson> <representedOrganization> <name>Healthcare Facility's name</name> <addr> <country>NL</country> <streetName>Duinweg</streetName> <houseNumber>23</houseNumber> <postalCode>7364 RX</postalCode> <city>Amsterdam</city> </addr> </representedOrganization> </assignedEntity></legalAuthenticator> |
hl7:time
| TS.IPS.TZ | 1 … 1 | M | Time of signing the document | XeHSator |
hl7:signatureCode
| CS | 0 … 1 | R | Signature code | XeHSator |
@code
| CONF | 0 … 1 | F | S |
hl7:assignedEntity
| | 0 … 1 | R | The entity that is responsible for the legal authentication of the CDA document | XeHSator |
hl7:id
| | 1 … * | R | Unique identification of legal authenticator | XeHSator |
hl7:addr
| AD.IPS | 1 … * | R | | XeHSator |
hl7:telecom
| TEL.IPS | 1 … * | R | | XeHSator |
hl7:assignedPerson
| | 1 … 1 | R | | XeHSator |
@classCode
| cs | 0 … 1 | F | PSN |
@determinerCode
| cs | 0 … 1 | F | INSTANCE |
hl7:name
| PN | 1 … * | R | Name of the legal authenticator | XeHSator |
| Example | <name> <given>John</given> <family>Español Smith</family></name> |
hl7:family
| | 1 … * | R | HP Family Name/Surname | XeHSator |
hl7:given
| | 1 … * | R | HP Given Name | XeHSator |
hl7:representedOrganization
| | 1 … 1 | M | Organization the legal authenticator is acting for Contains 2.16.840.1.113883.10.22.9.1 IPS CDA Organization (DYNAMIC) | XeHSator |
Included | 0 … * | | from 2.16.840.1.113883.3.1937.99.61.67.10.13 XeH Results Validator (DYNAMIC)
When present it represents the clinical expert who performed the clinical validation (see the entries “validator” and “clinical expert” in the glossary in LAB TF-1:1.11) of the report or of a subset of its results, also called the validator. There MAY be more than one validator of the report. All the validators SHALL appear in the report header as authenticator elements AND, in the case of multiple validators, each individual validator SHALL be associated with the particular sections of the report he or she validated. In this case, the validator of a section SHALL also appear in the entry this section is derived from. |
hl7:authenticator
| | 0 … * | R | | XeHCator |
@typeCode
| cs | 1 … 1 | F | AUTHEN |
hl7:templateId
| II | 1 … 1 | M | | XeHCator |
@root
| uid | 1 … 1 | F | 1.3.6.1.4.1.19376.1.3.3.1.5 |
hl7:time
| TS | 1 … 1 | R | | XeHCator |
hl7:signatureCode
| CS | 1 … 1 | R | | XeHCator |
hl7:assignedEntity
| | 1 … 1 | R | | XeHCator |
@classCode
| cs | 0 … 1 | F | ASSIGNED |
hl7:id
| II | 1 … * | R | | XeHCator |
hl7:code
| CE | 0 … 1 | R | | XeHCator |
hl7:addr
| AD | 1 … * | R | | XeHCator |
hl7:telecom
| TEL | 1 … * | R | | XeHCator |
| Schematron assert | role | error | |
| test | not(hl7:assignedPerson) or hl7:assignedPerson/hl7:name | |
| Message | the <name> sub-element of <assignedPerson> SHALL be present. | |
hl7:assignedPerson
| | 0 … 1 | R | | XeHCator |
hl7:representedOrganization
| | 0 … 1 | R | | XeHCator |
Included | 0 … * | | from 2.16.840.1.113883.3.1937.99.61.67.10.4 XeH Ordering/Referring Provider (DYNAMIC)
In particular, when the ordering provider of the order (or group of orders) fulfilled by this laboratory report is present in the CDA, it SHALL be documented as a participant with the attribute typeCode valued “REF” (referrer). |
hl7:participant
| | 0 … * | | Referral Ordering Physician | XeHOider |
@typeCode
| cs | 1 … 1 | F | REF |
hl7:templateId
| II | 1 … 1 | | | XeHOider |
@root
| uid | 1 … 1 | F | 2.16.840.1.113883.3.1937.99.61.67.10.4 |
hl7:time
| IVL_TS | 1 … 1 | R | This element represents the date and time the order was placed. Time MAY be present. | XeHOider |
hl7:associatedEntity
| | 1 … 1 | | | XeHOider |
hl7:addr
| AD | 0 … * | R | The address of this person (referral ordering physician) SHALL be present. | XeHOider |
hl7:telecom
| TEL | 0 … * | R | The telecom of this person (referral ordering physician) SHALL be present. | XeHOider |
| Schematron assert | role | error | |
| test | not(hl7:assignedPerson) or hl7:assignedPerson/hl7:name | |
| Message | The <name> sub-element SHALL be present when <assignedPerson> present. | |
hl7:associatedPerson
| | 0 … 1 | R | | XeHOider |
hl7:scopingOrganization
| | 0 … 1 | | | XeHOider |
Included | 0 … * | | from 2.16.840.1.113883.3.1937.99.61.67.10.6 XeH inFulfillmentOf (DYNAMIC)
It represents the Placer Order or the Placer Group that was fulfilled, the id of which is carried by inFulfillmentOf/order/id. |
hl7:inFulfillmentOf
| | 0 … * | | | XeHSntOf |
@typeCode
| cs | 0 … 1 | F | FLFS |
hl7:order
| | 1 … 1 | R | | XeHSntOf |
@classCode
| cs | 0 … 1 | F | ACT |
@moodCode
| cs | 1 … 1 | F | RQO |
hl7:id
| II | 1 … * | R | Identifier of the order
| XeHSntOf |
hl7:code
| CE | 0 … 1 | | Type of order | XeHSntOf |
hl7:priorityCode
| CE | 0 … 1 | | | XeHSntOf |
| CONF | |
Included | 0 … * | | from 2.16.840.1.113883.3.1937.99.61.67.10.14 XeH DocumentationOf (report) (DYNAMIC) |
hl7:documentationOf
| | 0 … * | | | XeHRonOf |
hl7:serviceEvent
| | 1 … 1 | R | | XeHRonOf |
hl7:effectiveTime
| IVL_TS | 0 … 1 | | Use of sub element documentationOf/serviceEvent/effectiveTime to document the time boundaries of events in the document is appropriate. | XeHRonOf |
lab:statusCode
| CS | 0 … 1 | | This Laboratory Report Content Module can express both final and non-final reports. To distinguish between the two, the statusCode element has been added to the documentationOf/serviceEvent element. A non-final report is a report documenting a serviceEvent, which is in the status "active". This sub-element serviceEvent/statusCode is optional. When it is not present the serviceEvent is assumed to be in the status "completed". | XeHRonOf |
| CONF | |
hl7:performer
| | 0 … * | | Laboratory Performer template in the CDA header Contains 1.3.6.1.4.1.19376.1.3.3.1.7 Laboratory Performer (DYNAMIC) | XeHRonOf |
Included | 0 … * | | from 2.16.840.1.113883.10.22.2.7 IPS CDA relatedDocument (DYNAMIC)
This element SHALL be present in case of an update replacement of a previous report. In this case relatedDocument@typeCode attribute SHALL be valued "RPLC", the new report replacing the parent one. |
hl7:relatedDocument
| | 0 … * | R | | IPSCment |
@typeCode
| cs | 1 … 1 | R | |
| CONF | |
hl7:parentDocument
| | 1 … 1 | R | | IPSCment |
@classCode
| cs | 0 … 1 | F | DOCCLIN |
@moodCode
| cs | 0 … 1 | F | EVN |
hl7:id
| II | 1 … * | R | | IPSCment |
hl7:code
| CD.IPS | 0 … 1 | R | | IPSCment |
@codeSystem
| CONF | 0 … 1 | F | 2.16.840.1.113883.6.1 |
hl7:text
| ED | 0 … 1 | R | | IPSCment |
hl7:setId
| II | 0 … 1 | R | | IPSCment |
hl7:versionNumber
| INT | 0 … 1 | R | | IPSCment |
Included | 0 … 1 | | from 2.16.840.1.113883.3.1937.99.61.67.10.7 XeH ComponentOf (DYNAMIC)
It describes the encounter during which the reported lab observations were ordered. When present the encounter : - is identified with an id element: encompassingEncounter/id
- have an effective time that represents the time interval (possibly still running, e.g., an inpatient current stay) of the encounter or a point in time at which the encounter took place (e.g., an outpatient consultation): encompassingEncounter/ effectiveTime
The encounter can provide any number of encounter participants (encompassingEncounter/encounterParticipant/assignedEntity). The encounter could precise the patient location during this encounter. This is the healthcare facility in which the patient was located when the reported lab test observations were ordered: encompassingEncounter/location/healthCareFacility. This healthcare facility can be represented as a physical place (e.g., room, floor, building, office) or as an organization (e.g., service, department, team) or both: healthCareFacility/location, healthCareFacility/serviceProviderOrganization. |
hl7:componentOf
| | 0 … 1 | | | XeHSntOf |
@typeCode
| cs | 0 … 1 | F | COMP |
hl7:encompassingEncounter
| | 1 … 1 | R | | XeHSntOf |
@classCode
| cs | 0 … 1 | F | ENC |
@moodCode
| cs | 0 … 1 | F | EVN |
hl7:id
| II | 0 … * | R | Identifier of the encounter (e.g. identifier of the hospital stay) | XeHSntOf |
hl7:code
| CE | 0 … 1 | | Code describing the kind of clinical encounter during which the documented act(s) or ServiceEvent occurred.
| XeHSntOf |
| CONF | |
hl7:effectiveTime
| IVL_TS | 1 … 1 | R | | XeHSntOf |
hl7:low
| IVXB_TS | 1 … 1 | R | Start date time of the encounter (e.g. date of admission) | XeHSntOf |
hl7:high
| IVXB_TS | 1 … 1 | R | End date time of the encounter (e.g. date of discharge)
| XeHSntOf |
hl7:dischargeDispositionCode
| CE | 0 … 1 | R | Depict the disposition of the patient at the time of hospital discharge (e.g., discharged to home, expired, against medical advice, etc.).
| XeHSntOf |
| CONF | shall be drawn from concept domain "EncounterDischargeDisposition" |
|
hl7:responsibleParty
| | 0 … 1 | | The provider (person or organization) who has primary responsibility for the encounter. The responsible provider is not necessarily present in an encounter, but is accountable for the action through the power to delegate, and the duty to review actions with the performing participant.
When the responsible party is an organization, the responsible party is reflected by the presence of a scoping Organization, without a playing entity. Contains 2.16.840.1.113883.10.12.153 CDA AssignedEntity (DYNAMIC) | XeHSntOf |
@typeCode
| cs | 0 … 1 | F | RESP |
hl7:encounterParticipant
| | 0 … * | | Represents clinicians directly associated with the encounter (e.g. by initiating, terminating, or overseeing it).
| XeHSntOf |
@typeCode
| cs | 1 … 1 | R | |
| CONF | |
hl7:time
| IVL_TS | 0 … 1 | | The time when the participation occurred
| XeHSntOf |
hl7:assignedEntity
| | 1 … 1 | R | The clinician assigned to the role (e.g. Admitter) by the scoping organization (e.g the hospital)
Contains 2.16.840.1.113883.10.12.153 CDA AssignedEntity (DYNAMIC) | XeHSntOf |
hl7:location
| | 0 … 1 | | The location where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.)
The setting of an encounter (e.g. cardiology clinic, primary care clinic, rehabilitation hospital, skilled nursing facility) can be expressed in HealthCareFacility.code. Note that setting and physical location are not the same. | XeHSntOf |
@typeCode
| cs | 0 … 1 | F | LOC |
hl7:healthCareFacility
| | 1 … 1 | R | | XeHSntOf |
@classCode
| cs | 0 … 1 | F | SDLOC |
hl7:id
| II | 0 … * | | | XeHSntOf |
hl7:code
| CE | 0 … 1 | | | XeHSntOf |
| CONF | |
hl7:location
| | 0 … 1 | | Contains 2.16.840.1.113883.10.12.317 CDA Place (DYNAMIC) | XeHSntOf |
hl7:serviceProviderOrganization
| | 0 … 1 | | Contains 2.16.840.1.113883.10.12.151 CDA Organization (DYNAMIC) | XeHSntOf |
hl7:component
| | 1 … 1 | R | | XeHLport |
hl7:structuredBody
| | 1 … 1 | R | | XeHLport |
hl7:component
| | 1 … * | R | Content Modules for CDA Sections (Level 2) A laboratory report SHALL have a structuredBody. This body is organized as a tree of up to two levels of sections, delivering the human-readable content of the report: Top level sections represent laboratory specialties. A top level section SHALL contain either one text block carrying all the text results produced for this specialty along with a single Laboratory Data Processing Entry or a set of Laboratory Report Item Sections. In the first case the specialty section happens to also be a leaf section. In the latter case, each (second level) leaf section contained in the (top level) specialty section represents a Report Item: i.e., a battery, a specimen study (especially in microbiology), or an individual test. In addition, any leaf section SHALL contain a single Laboratory Data Processing Entry containing the observations of that section in a machine-readable format. Contains 1.3.6.1.4.1.19376.1.3.3.2.1 Laboratory Specialty Section (DYNAMIC) | XeHLport |
| Schematron assert | role | error | |
| test | //hl7:templateId[@root='1.3.6.1.4.1.19376.1.3.1.6'] | |
| Message | Lab report SHALL contain Laboratory Observation | |