Back To Index  <<  Back To Templates

active Template  epSOS CDA legalAuthenticator

Id 2.16.840.1.113883.3.1937.777.11.10.109 Effective Date 2013‑12‑20
Status active Active Version Label
Name epSOSCDAlegalAuthenticator Display Name epSOS 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.”
Classification CDA Header Level Template
Open/Closed Open (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 7 templates, Uses 1 template
Used by as Name Version
1.3.6.1.4.1.12559.11.10.1.3.1.1.1 Include active epSOS-ePrescription 2013‑12‑20
1.3.6.1.4.1.12559.11.10.1.3.1.1.2 Include active epSOS-eDispensation 2013‑12‑20
1.3.6.1.4.1.12559.11.10.1.3.1.1.3 Include active epSOS-Patient Summary 2013‑12‑20
1.3.6.1.4.1.12559.11.10.1.3.1.1.4 Include active epSOS-Health Care Encounter Report 2013‑12‑20
1.3.6.1.4.1.12559.11.10.1.3.1.1.5 Include active epSOS-Medication Related Overview 2013‑12‑20
1.3.6.1.4.1.12559.11.10.1.3.1.1.6 Include active eHDSI-ePrescription PDF embedded 2017‑03‑11 22:32:59
1.3.6.1.4.1.12559.11.10.1.3.1.1.7 Include active eHDSI-Patient Summary PDF embedded 2017‑03‑11 18:41:31
Uses as Name Version
2.16.840.1.113883.3.1937.777.11.10.111 Containment active epSOS CDA Organization DYNAMIC
Relationship Adaptation: template 2.16.840.1.113883.10.12.106 (2005‑09‑07)
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>
notice There are open issues with this item:
  • epsos-issue-235: hl7:assignedPerson contains twice the element hl7:name (In Progress)
  • epsos-issue-253: Adapt conformancy of family and given elements conform the EXPAND specifications (Feedback needed)
Item DT Card Conf Description Label
hl7:legalAuthenticator
R 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. R1.11.9
hl7:time
TS.EPSOS.TZ 1 … 1 M Time of signing the document R1.11.9
hl7:signatureCode
CS 1 … 1 R Signature code R1.11.9
@code
CONF 0 … 1 F S
hl7:assignedEntity
1 … 1 M The regional authority that is responsible for the legal authentication of the CDA document R1.11.9
hl7:id
1 … 1 M Unique identification of legal authenticator R1.11.9
hl7:addr
AD.EPSOS 1 … * R IHE PCC
hl7:telecom
TEL 1 … * 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_cs 0 … 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 epSOSTelecomAddress (DYNAMIC)
@nullFlavor
cs 0 … 1 F NI
  Example <telecom use="WP" value="tel:+45 20 7025 6161"/><telecom use="HP" value="mailto:jsmith@myprovider.co.uk"/>
hl7:assignedPerson
1 … 1 R IHE PCC
@classCode
cs 0 … 1 F PSN
@determinerCode
cs 0 … 1 F INSTANCE
hl7:name
PN 1 … 1 R HP Name IHE PCC
  Example <name>
  <given>John</given>  <family>Español Smith</family></name>
hl7:family
1 … * M HP Family Name/Surname R1.10.1
hl7:given
1 … * M HP Given Name R1.10.2
hl7:prefix
0 … * R HP Prefix R1.10.3
hl7:suffix
0 … * R HP Suffix R1.10.4
hl7:representedOrganization
1 … 1 M Contains 2.16.840.1.113883.3.1937.777.11.10.111 epSOS CDA Organization (DYNAMIC) R1.11.9
treeblank treeblank where [not(@nullFlavor)]