Data Set (for transaction) 2.16.840.1.113883.3.1937.777.10.4.19

Data Set 2.16.840.1.113883.3.1937.777.10.1.1 epSOS Data Set

Patient Data

Id	epsos-dataelement-5 (2013‑05‑31)
Cardinality	0..1
Description	Information about the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

Identification

Id	epsos-dataelement-6 (2013‑05‑31)
Cardinality	1..1 Mandatory
Description	Country ID, unique for the patient in that country. Example: ID for United Kingdom patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

National Health Care patient ID (country of affiliation)

Id	epsos-dataelement-7 (2013‑05‑31)
Cardinality	1..1 Mandatory
Description	Country ID from the country of origin, unique for the patient in that country. Example: ID for United Kingdom patient
Value Domain	Type	identifier
Example	NL-Burgerservicenummer 999999512
Example	UK-NHS Number 943 476 5919
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Other Identifier

Id	epsos-dataelement-235 (2013‑11‑25 12:06:30)
Cardinality	0..*
Description	Other identifiers than the national health care patient IDs from either the country of affiliation or the country of treatment
Value Domain	Type	identifier
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Personal Information

Id	epsos-dataelement-8 (2013‑05‑31)
Cardinality	1..1 Required
Description	Personal information about the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

Full Name

Id	epsos-dataelement-9 (2013‑05‑31)
Cardinality	1..1 Required
Description	The full name of the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

Given name

Id	epsos-dataelement-12 (2013‑05‑31)
Cardinality	1..1 Required
Description	The Name of the patient (Example: John). This field can contain more than one element
Value Domain	Type	string
Example	John
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Family Name/Surname

Id	epsos-dataelement-13 (2013‑05‑31)
Cardinality	1..1 Required
Description	This field can containe more than one element.
Value Domain	Type	string
Example	Español Smith
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Prefix

Id	epsos-dataelement-263 (2013‑11‑27 11:44:16)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Suffix

Id	epsos-dataelement-264 (2013‑11‑27 11:44:29)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Date of Birth

epsos-dataelement-10 (2013‑05‑31)

Cardinality

1..1 Required

Description

The date of birth of the patient. This field may contain only the year if day and month are not available

Value Domain

Type

date

Property

Timestamp precision
day, month and year

Example

091/01/2009

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)

This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)

This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)

This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)

This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Gender

epsos-dataelement-11 (2013‑05‑31)

Cardinality

1..1 Required

Description

It must contained a recognized valid value for this field.

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-11.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.34 (version DYNAMIC)

Example

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)

This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)

This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)

This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Contact Information

Id	epsos-dataelement-26 (2013‑06‑03)
Cardinality	0..*
Description	Contact information of the patient, including information of the contacts of the patient.
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Address

Id	epsos-dataelement-27 (2013‑06‑03)
Cardinality	0..*
Description	Address of the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Street

Id	epsos-dataelement-51 (2013‑06‑04)
Cardinality	0..1
Description	Name of street where the patient lives
Value Domain	Type	string
Example	Oxford
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Number of Street

Id	epsos-dataelement-52 (2013‑06‑04)
Cardinality	0..1
Description	House number where the patient lives
Value Domain	Type	string
Example	221
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

City

Id	epsos-dataelement-55 (2013‑06‑04)
Cardinality	0..1
Description	City where the patient lives
Value Domain	Type	string
Example	London
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Postal Code

Id	epsos-dataelement-53 (2013‑06‑04)
Cardinality	0..1
Description	Postal code where the patient lives
Value Domain	Type	string
Example	W1W 8LG
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

State or Province

Id	epsos-dataelement-56 (2013‑06‑04)
Cardinality	0..1
Description	State or province where the patient lives
Value Domain	Type	string
Example	London
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Country

Id	epsos-dataelement-54 (2013‑06‑04)
Cardinality	0..1
Description	Country where the patient lives
Value Domain	Type	string
Example	UK
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Telecom

Id	epsos-dataelement-300 (2013‑11‑27 16:52:13)
Cardinality	*1.. Required**
Description	Telecommunication addresses of the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..* Required) in scenario Patient Summary (PS)

Concept

Telephone No

Id	epsos-dataelement-28 (2013‑06‑03)
Cardinality	0..*
Description	Telephone number of the patient
Value Domain	Type	string
Example	+45 20 7025 6161
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Id	epsos-dataelement-29 (2013‑06‑03)
Cardinality	0..*
Description	Email address of the patient
Value Domain	Type	string
Example	jens@hotmail.com
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Preferred HP to contact

Id	epsos-dataelement-30 (2013‑06‑03)
Cardinality	0..1
Description	Preferred Health Professional to contact. A foreign HP may need a contact (HP/legal organization) who knows the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Full Name

Id	epsos-dataelement-46 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	Name of the HP/name of the legal organization. If it is an HP, the structure of the name will be the same as described in ‘Full name’ (Given name, family name/surname)
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Given Name

epsos-dataelement-47 (2013‑06‑03)

Cardinality

Conditional

Condition	Card/Conf
If it is an HP	0..1 Required
otherwise	0..0 Not present

Description

The Name of the HP (Example: John). This field can contain more than one element

Value Domain

Type

string

Example

John

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)

This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Family Name/Surname

epsos-dataelement-48 (2013‑06‑03)

Cardinality

Conditional

Condition	Card/Conf
If it is an HP	0..1 Required
otherwise	0..0 Not present

Description

This field can contain more than one element.

Value Domain

Type

string

Example

Español Smith

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)

This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prefix

epsos-dataelement-265 (2013‑11‑27 11:44:48)

Cardinality

Conditional

Condition	Card/Conf
If it is an HP	0..1 Required
otherwise	0..0 Not present

Description

Value Domain

Type

string

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)

This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Suffix

epsos-dataelement-266 (2013‑11‑27 11:45:03)

Cardinality

Conditional

Condition	Card/Conf
If it is an HP	0..1 Required
otherwise	0..0 Not present

Description

Value Domain

Type

string

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)

This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Telephone No

Id	epsos-dataelement-41 (2013‑06‑03)
Cardinality	*1.. Required**
Description	Telephone number of the HP/name of the legal organization
Value Domain	Type	string
Example	+45 20 7025 6161
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Id	epsos-dataelement-43 (2013‑06‑03)
Cardinality	*1.. Required**
Description	Email address of the HP/name of the legal organization
Value Domain	Type	string
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Clinical Data

Id	epsos-dataelement-16 (2013‑05‑30)
Cardinality	0..*
Description	Clinical information of the patient
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Medication

Id	epsos-dataelement-101 (2013‑05‑31)
Cardinality	0..1
	There is an open issue with this item: epsos-issue-42: Status (Open)
Description
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Prescription

Id	epsos-dataelement-102 (2013‑05‑31)
Cardinality	0..*
Description
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..* Conditional) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Prescription identification

Id	epsos-dataelement-134 (2013‑09‑27 10:48:19)
Cardinality	1..1 Mandatory
Description	Unique identification of the prescription
Value Domain	Type	identifier
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Medicinal product code

Id	epsos-dataelement-135 (2013‑09‑27 10:50:26)
Cardinality	0..1 Required
Description	Code that identifies the medicinal product description
Value Domain	Type	code
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)

Date of issue of prescription

epsos-dataelement-136 (2013‑09‑27 10:51:52)

Cardinality

1..1 Mandatory

Description

Date when medicine has been prescribed

Value Domain

Type

date

Property

Timestamp precision
at least day, month and year

Used by

4 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)

This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Brand name

Id	epsos-dataelement-137 (2013‑09‑27 10:52:59)
Cardinality	1..1 Required
Description	Original brand name of the medicine (in the language of the country in which the prescription was made)
Value Domain	Type	string
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)

Active ingredient

Id	epsos-dataelement-103 (2013‑05‑31)
Cardinality	*1.. Mandatory**
Description	Substance that alone or in combination with one or more other ingredients produces the intended activity of a medicinal product.
Value Domain	Type	string
Example	Paracetamol
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..* Required) in scenario Patient Summary (PS)

Active ingredient code

epsos-dataelement-104 (2013‑05‑31)

Cardinality

1..* Mandatory

Description

Code that identifies the Active ingredient

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-104.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.24 (version DYNAMIC)

Used by

4 scenarios, inherited once

This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario ePrescription (eP)

This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (1..* Mandatory) in scenario Patient Summary (PS)

Strength

Id	epsos-dataelement-105 (2013‑05‑31)
Cardinality	*1.. Mandatory**
Description	The content of the active ingredient expressed quantitatively per dosage unit, per unit of volume or per unit of weight, according to the pharmaceutical dose form. Example: 500 mg per tablet
Value Domain	Type	quantity
Example	500 mg per tablet
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..* Mandatory) in scenario Patient Summary (PS)

Medicinal product package size

Id	epsos-dataelement-138 (2013‑09‑27 10:54:04)
Cardinality	1..1 Required
Description	The size of the package prescribed
Value Domain	Type	count
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)

Pharmaceutical dose form

epsos-dataelement-106 (2013‑05‑31)

Cardinality

1..1 Mandatory

Description

It is the form in which a pharmaceutical product is presented in the medicinal product package (e.g. tablets, syrup)

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-106.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.2 (version DYNAMIC)

Example

tablets

Example

syrup

Used by

4 scenarios, inherited once

This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)

This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Number of packages

Id	epsos-dataelement-139 (2013‑09‑27 11:00:57)
Cardinality	1..1 Required
Description	Number of boxes that have been prescribed
Value Domain	Type	quantity
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)

Number of units per intake

Id	epsos-dataelement-107 (2013‑05‑31)
Cardinality	1..1 Required
Description	The number of units per intake that the patient is taking (e.g. 1 tablet)
Comment	Posology has been defined from the functional point of view as containing these three components: number of units per intake, frequency of intakes and duration of treatment:(example: 1 unit/intake every 24 hours for a duration of 14 days. There has to be space for posology in free text with the possibility of a null flavor
Value Domain	Type	quantity
Example	1 tablet
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)

Frequency of intakes

Id	epsos-dataelement-108 (2013‑05‑31)
Cardinality	*1.. Required**
Description	Frequency of intakes (per hours/day/month/ week..). Example: each 24 hours
Comment	There has to be space for posology in free text with the possibility of a null flavor
Value Domain	Type	quantity
Example	each 24 hours
Used by	4 scenarios, inherited once
	This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..* Required) in scenario Patient Summary (PS)

Duration of treatment

Id	epsos-dataelement-109 (2013‑05‑31)
Cardinality	1..1 Required
Description
Comment	There has to be space for posology in free text with the possibility of a null flavor
Value Domain	Type	quantity
Example	during 14 days
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)

Date of onset of treatment

Id	epsos-dataelement-110 (2013‑05‑31)
Cardinality	1..1 Required
Description	Date when patient needs to start taking the medicine prescribed
Value Domain	Type	datetime
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)

Route of administration

epsos-dataelement-140 (2013‑09‑27 11:05:39)

Cardinality

0..1 Required

Description

Indicates the part of the body through or into which, or the way in which, the medicinal product is intended to be introduced. In some cases a medicinal product can be intended for more than one route and/or method of administration.

NOTE FOR GUIDANCE ON DATA ELEMENTS AND STANDARDS FOR DRUG DICTIONARIES

(EMEA/CHMP/ICH/168535/2005)

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-140.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.12 (version DYNAMIC)

Used by

4 scenarios, inherited once

This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)

This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)

Instructions to patient

Id	epsos-dataelement-141 (2013‑09‑27 11:06:50)
Cardinality	0..1 Required
Description	The prescriber might give to the patient instructions; They must be presented in the original language.
Value Domain	Type	text
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)

Advice to dispenser

Id	epsos-dataelement-142 (2013‑09‑27 11:07:18)
Cardinality	0..1
Description	The prescriber might give instructions to the dispenser. The information will be in the original language as automatic translation is not secure enough. To avoid legal and ethical issues to the dispenser, it should be wise to implement an option that allows the dispenser to decide, knowing that this data is available, whether he wants to consult it or not.
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber

Id	epsos-dataelement-236 (2013‑11‑27 11:02:18)
Cardinality	0..1
Description
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Prescriber Profession

epsos-dataelement-237 (2013‑11‑27 11:03:07)

Cardinality

0..1

Description

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-237.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.1 (version DYNAMIC)

Used by

4 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)

This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber Speciality

Id	epsos-dataelement-238 (2013‑11‑27 11:03:56)
Cardinality	0..*
	There is an open issue with this item: epsos-issue-49: Missing value set binding for Prescriber Speciality (Open)
Description	Some countries need the specialty of the prescriber for the epSOS ePrescription to be seen as valid. In the epSOS phase 1 ePrescription data set, this element is not basic (minimum), therefore not always filled in. The proposal is to define the specialty of the prescriber as a basic element, so it should be filled in, if available. As it could be that this information is not available in every country, null values should be allowed.
Value Domain	Type	code
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Timestamp of Prescribing

epsos-dataelement-239 (2013‑11‑27 11:04:21)

Cardinality

0..1

Description

Date/time the medication was prescribed

Value Domain

Type

datetime

Property

Timestamp precision
at least day, month and year

Used by

4 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)

This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber Identification

Id	epsos-dataelement-240 (2013‑11‑27 11:04:55)
Cardinality	0..1
Description	Unique identification of the prescriber
Value Domain	Type	identifier
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber Full Name

Id	epsos-dataelement-241 (2013‑11‑27 11:05:18)
Cardinality	0..1
Description	The full name of the Health Professional
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Given Name

Id	epsos-dataelement-242 (2013‑11‑27 11:05:49)
Cardinality	0..1
Description	The Name of the Prescriber (Example: John). This field can contain more than one element
Value Domain	Type	string
Example	John
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Family Name/Surname

Id	epsos-dataelement-243 (2013‑11‑27 11:06:25)
Cardinality	0..1
Description	This field can contain more than one element.
Value Domain	Type	string
Example	Español Smith
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prefix

Id	epsos-dataelement-269 (2013‑11‑27 11:45:59)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Suffix

Id	epsos-dataelement-270 (2013‑11‑27 11:46:17)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber Telecom

Id	epsos-dataelement-282 (2013‑11‑27 12:27:48)
Cardinality	0..*
Description
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Telephone No

Id	epsos-dataelement-280 (2013‑11‑27 12:27:03)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Id	epsos-dataelement-281 (2013‑11‑27 12:27:19)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber Healthcare Facility

Id	epsos-dataelement-244 (2013‑11‑27 11:09:08)
Cardinality	0..1
Description	Information about the healthcare facility where the health professional works
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Identifier

Id	epsos-dataelement-245 (2013‑11‑27 11:09:42)
Cardinality	0..1
Description	Unique identification of the healthcare facility
Value Domain	Type	identifier
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Name

Id	epsos-dataelement-246 (2013‑11‑27 11:09:57)
Cardinality	0..1
Description	Name of the healthcare facility
Value Domain	Type	string
Example	St. Johns Hospital
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Healthcare Facility Telecom

Id	epsos-dataelement-283 (2013‑11‑27 12:28:21)
Cardinality	0..*
Description
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Telephone No

Id	epsos-dataelement-278 (2013‑11‑27 12:24:25)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Id	epsos-dataelement-279 (2013‑11‑27 12:24:51)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Prescriber Credentialing Organization

Id	epsos-dataelement-290 (2013‑11‑27 13:38:39)
Cardinality	0..1
Description	The organization which provided the credentialing for the prescriber
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)

Concept

Identifier

Id	epsos-dataelement-291 (2013‑11‑27 13:39:16)
Cardinality	0..1
Description	Unique identification of the organization which provided the credentialing for the prescriber
Value Domain	Type	identifier
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Name

Id	epsos-dataelement-292 (2013‑11‑27 13:39:55)
Cardinality	0..1
Description	The name of the organization which provided the credentialing for the prescriber
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Document Data

Id	epsos-dataelement-62 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	Information about the document itself
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Request eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Request MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Request PS of country A (0..1) in scenario Patient Summary (PS)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

Identification

Id	epsos-dataelement-176 (2013‑10‑22 14:47:34)
Cardinality	1..1 Mandatory
Description	Identification of the document
Value Domain	Type	identifier
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Type

epsos-dataelement-296 (2013‑11‑27 14:10:56)

Cardinality

1..1 Mandatory

Description

Type of the document

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-296.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.32 (version DYNAMIC)

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Request eP from country A (1..1) in scenario ePrescription (eP)

This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)

This concept is used in transaction Request MRO (1..1) in scenario Medication Related Overview (MRO)

This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Request PS of country A (1..1) in scenario Patient Summary (PS)

This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Confidentiality

epsos-dataelement-297 (2013‑11‑27 14:11:34)

Cardinality

0..1 Required

Description

Confidentiality of the document as a whole

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-297.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.31 (version DYNAMIC)

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)

This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)

Language

Id	epsos-dataelement-298 (2013‑11‑27 14:12:11)
Cardinality	1..1 Mandatory
Description	The principal language of the document
Operationalization	The language code SHALL be in the form nn-CC. The nn portion SHALL be an ISO-639-1 language code in lower case derived by the Value Set epSOSLanguage. The CC portion SHALL be an ISO-3166 country code in upper case derived by the value Set epSOSCountry
Value Domain	Type	code
Example	English in United Kingdom en-GB
Example	Dutch in The Netherlands nl-NL
Example	Dutch in Belgium nl-BE
Example	German in Germany de-DE
Example	German in Austria de-AT
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Country A

epsos-dataelement-63 (2013‑06‑03)

Cardinality

1..1 Mandatory

Description

Name of country A

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-63.0

Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.4 (version DYNAMIC)

Example

United Kindom

Used by

2 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)

This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Topicality

Id	epsos-dataelement-64 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

Date Created

epsos-dataelement-65 (2013‑06‑03)

Cardinality

1..1 Mandatory

Description

Date on which the document was generated

Value Domain

Type

datetime

Property

Timestamp precision
at least day, month and year

Example

01/01/2009

Used by

5 scenarios, inherited 0 times

This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)

This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)

This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)

This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Author

Id	epsos-dataelement-67 (2013‑06‑03)
Cardinality	0..1
Description	To highlight if the data is collected manually by an HP or is collected automatically from different sources (eg: hospital doctor repository, GPs...etc) through predetermined clinical rules.
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Author Identification

Id	epsos-dataelement-22 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	Unique identification of the Health Professional.
Value Domain	Type	identifier
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Author Full Name

Id	epsos-dataelement-19 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	The full name of the Health Professional
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Concept

Given Name

Id	epsos-dataelement-20 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	The Name of the HP (Example: John). This field can contain more than one element
Value Domain	Type	string
Example	John
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Family Name/Surname

Id	epsos-dataelement-21 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	This field can contain more than one element.
Value Domain	Type	string
Example	Español Smith
Used by	5 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Prefix

Id	epsos-dataelement-273 (2013‑11‑27 11:47:15)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Suffix

Id	epsos-dataelement-274 (2013‑11‑27 11:47:25)
Cardinality	0..1
Description
Value Domain	Type	string
Used by	4 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Author Healthcare Facility

Id	epsos-dataelement-23 (2013‑06‑03)
Cardinality	0..1
Description	Information about the healthcare facility where the health professional works
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)

Concept

Identifier

Id	epsos-dataelement-25 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	Unique identification of the healthcare facility
Value Domain	Type	identifier
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Name

Id	epsos-dataelement-24 (2013‑06‑03)
Cardinality	1..1 Mandatory
Description	Name of the healthcare facility
Value Domain	Type	string
Example	St. Johns Hospital
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)

Transaction 2.16.840.1.113883.3.1937.777.10.4.19 Return eP from country A

Data Set 2.16.840.1.113883.3.1937.777.10.1.1 epSOS Data Set