Id2.16.840.1.113883.3.1937.777.11.10.106
ref
epsos-
Effective Date2020‑04‑16 10:56:17
Statusretired RetiredVersion Label
NameeHDSIDocumentationOfPCPRDisplay NameeHDSI DocumentationOf PCPR
Description
/ClinicalDocument/author/assignedAuthor
/ClinicalDocument/documentationOf/serviceEvent/performer (this applies to the prescriber and the dispenser).

The template ID referenced here refers to HP information in the /ClinicalDocument/documentationOf/serviceEvent/performer structure. In this document, the same requriements apply to the person author of the document (if there is one), and to the prescrober and dispenser (see body).

When there is no HP but we have the method of assembly of data by a device, such as the “spider” method, we have the following expression; ClinicalDocument/author/assignedAuthor/assignedAuthoringDevice.

When the data is collected from different sources & pre-existing documents that are part of a bigger system. In that case the organization responsible of that collection “signed” the PS as responsible.

ClinicalDocument/author/assignedAuthor/representedOrganization

ClassificationCDA Header Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 0 templates, Uses 2 templates
Uses as NameVersion
2.16.840.1.113883.3.1937.777.11.10.111Containmentactive eHDSI OrganizationDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.113Containmentactive eHDSI PersonDYNAMIC
RelationshipSpecialization: template 2.16.840.1.113883.10.12.110 CDA documentationOf (2005‑09‑07)
ref
ad1bbr-
ItemDTCardConfDescriptionLabel
hl7:documentationOf
0 … *ReHDSdotsPCPR
@typeCode
cs1 … 1FDOC
hl7:serviceEvent
1 … 1ReHDSdotsPCPR
@classCode
cs1 … 1FPCPR
@moodCode
cs1 … 1FEVN
hl7:id
II.EPSOS0 … *ReHDSdotsPCPR
hl7:code
CE.EPSOS0 … 1ReHDSdotsPCPR
Choice1 … 1Elements to choose from:
  • hl7:effectiveTime[hl7:high]
  • hl7:effectiveTime[@nullFlavor or @value]
hl7:effectiveTime
IVL_TS … 1ReHDSdotsPCPR
where [hl7:high]
hl7:low
TS0 … 1ReHDSdotsPCPR
hl7:high
TS1 … 1ReHDSdotsPCPR
hl7:effectiveTime
TS … 1ReHDSdotsPCPR
where [@nullFlavor or @value]
hl7:performer
0 … *Rrepresents the healthcare providers involved in the current or pertinent historical care of the patient. Preferably, the patient’s key healthcare providers would be listed, particularly their primary physician and any active consulting physicians, therapists, and counselorseHDSdotsPCPR
@typeCode
cs1 … 1R
 CONF
The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.19601 x_ServiceEventPerformer (DYNAMIC)
hl7:functionCode
CE.EPSOS1 … 1ReHDSdotsPCPR
 CONF
The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.1 eHDSIHealthcareProfessionalRole (DYNAMIC)
hl7:time
IVL_TS0 … 1ReHDSdotsPCPR
hl7:assignedEntity
1 … 1MeHDSdotsPCPR
hl7:id
II.EPSOS1 … *RHP ID numbereHDSdotsPCPR
hl7:code
CE.EPSOS0 … 1RHP SpecialtyeHDSdotsPCPR
hl7:addr
AD.EPSOS1 … *RIHE PCC
hl7:telecom
TEL1 … *R

Performer'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.8
@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:+45 20 7025 6161"/><telecom use="HP" value="mailto:jsmith@myprovider.co.uk"/>
hl7:assignedPerson
0 … 1Contains 2.16.840.1.113883.3.1937.777.11.10.113 eHDSI Person (DYNAMIC)eHDSdotsPCPR
hl7:representedOrganization
0 … 1Contains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC)eHDSdotsPCPR