Template

Show index

Template CZ CDA LegalAuthenticator 2020‑05‑20 15:53:28

Id1.2.203.24341.11.10.2.4Effective Date2020‑05‑20 15:53:28
Statusdraft DraftVersion Label
NameCZCDALegalAuthenticatorDisplay NameCZ CDA LegalAuthenticator
Description
The person taking responsibility for the medical content of the document. In Spain this is the regional authority in healthcare. This regional authority healthcare organization will send this to the NCP. The definition of the legal authenticator may vary accoriding to the rules set up in the framework agreement particular to each state. It may be a person or a regional authority, or an NCP.

In any case, as well described in the IG CDA R2 – "Imaging Integration: Local policies may choose to delegate the function of legal authentication to a device or system that generates the clinical document. In these cases, the legal authenticator is a person accepting responsibility for the document, not the generating device or system.”
ClassificationCDA Header Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 1 transaction and 1 template, Uses 1 template
Used by as NameVersion
2.16.840.1.113883.3.1937.777.49.4.2Transactiondraft PS created2022‑05‑19 08:45:25
1.2.203.24341.11.10.1.1Includedraft CZ-EU Patient Summary2019‑11‑28 20:23:19
Uses as NameVersion
1.2.203.24341.11.10.9.3Containmentdraft CZ CDA OrganizationDYNAMIC
RelationshipAdaptation: template 2.16.840.1.113883.3.1937.777.11.10.109 eHDSI LegalAuthenticator (2020‑04‑16 10:57:13)
ref
epsos-

Adaptation: template 2.16.840.1.113883.10.12.106 CDA legalAuthenticator (2005‑09‑07)
ref
ad1bbr-
Example
Example
<legalAuthenticator>
  <time value="20111013150937"/>  <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>
ItemDTCardConfDescriptionLabel
hl7:legalAuthenticator
RThe person taking responsibility for the medical content of the document. In Spain this is the regional authority in healthcare. This regional authority healthcare organization will send this to the NCP. The definition of the legal authenticator may vary accoriding to the rules set up in the framework agreement particular to each state. It may be a person or a regional authority, or an NCP.R1.11.9
hl7:time
TS.EPSOS.TZ1 … 1MTime of signing the documentR1.11.9
hl7:signatureCode
CS1 … 1RSignature codeR1.11.9
@code
CONF0 … 1FS
hl7:assignedEntity
1 … 1MThe entity that is responsible for the legal authentication of the CDA documentR1.11.9
hl7:id
1 … 1MUnique identification of legal authenticatorR1.11.9
hl7:addr
AD.EPSOS1 … *RIHE PCC
hl7:telecom
TEL1 … *R

Legal Authenticator's Telecom

If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present.

Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.

R1.10.9.4 / R1.10.9.4.1 / R1.10.9.4.2
@use
set_cs0 … 1 
 CONF
The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
@nullFlavor
cs0 … 1FNI
 Example<telecom use="WP" value="tel:+420 207 025 616"/><telecom use="HP" value="mailto:jsmith@myprovider.co.uk"/>
hl7:assignedPerson
1 … 1RIHE PCC
@classCode
cs0 … 1FPSN
@determinerCode
cs0 … 1FINSTANCE
hl7:name
PN1 … 1RName of the legal authenticatorIHE PCC
 Example<name>
  <given>John</given>  <family>Español Smith</family></name>
hl7:family
1 … *MFamily Name/SurnameR1.10.1
hl7:given
1 … *MGiven NameR1.10.2
hl7:prefix
0 … *RPrefixR1.10.3
hl7:suffix
0 … *RSuffixR1.10.4
hl7:representedOrganization
1 … 1MContains 1.2.203.24341.11.10.9.3 CZ CDA Organization (DYNAMIC)R1.11.9