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
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.