Back To Index  <<  Back To Scenarios

draft Transaction 2.16.840.1.113883.3.1937.777.10.4.23 Return MRO

Data Set 2.16.840.1.113883.3.1937.777.10.1.1 epSOS Data Set

folder draft Patient Data
Id epsos-dataelement-5 (2013‑05‑31)
Cardinality 0..1
Description Information about the patient
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
folder draft 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft National Health Care patient ID (country of treatment)
Id epsos-dataelement-234 (2013‑11‑25 12:03:28)
Cardinality 1..1 Mandatory
Description Country ID given in the country of treatment, unique for the patient in that country. Identifier that identifies that patient within the country B eHealth Infrastructure.
Value Domain Type identifier
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return PS of country A (0..0 Not present) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
folder draft 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Date of Birth
Id 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
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft Gender
Id 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 M
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Request eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..*) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Address
Id epsos-dataelement-27 (2013‑06‑03)
Cardinality 0..*
Description Address of the patient
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..* Required) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
draft Email
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
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
folder draft 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
draft Given Name
Id 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
target This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Family Name/Surname
Id 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
target This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Prefix
Id 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
target This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Suffix
Id 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
target This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Conditional) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
draft Email
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
target This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
folder draft Clinical Data
Id epsos-dataelement-16 (2013‑05‑30)
Cardinality 0..1
Description Clinical information of the patient
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Medical Problems
Id epsos-dataelement-82 (2013‑05‑31)
Cardinality 0..1
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Problem/Diagnosis
Id epsos-dataelement-228 (2013‑10‑24 14:26:14)
Cardinality Conditional

Condition Card/Conf
Current problem/diagnosis 0..*
otherwise 0..0 Not present
Concept inherits from epsos-dataelement-83 (2013‑05‑31)
Description
Comment
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..* Conditional) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Problem/diagnosis Description
Id epsos-dataelement-229 (2013‑10‑24 14:26:31)
Cardinality 1..1 Required
Concept inherits from epsos-dataelement-84 (2013‑05‑31)
Description Problems or diagnosis not included under the definition of ‘Current problems or diagnosis’. Example: hepatic cyst (the patient has been treated with an hepatic cystectomy that solved the problem and therefore it ́s a closed problem)
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Problem/diagnosis Id (Code)
Id epsos-dataelement-230 (2013‑10‑24 14:26:31)
Cardinality 1..1 Required
Concept inherits from epsos-dataelement-85 (2013‑05‑31)
Description Normalized identifier
Value Domain Type code
Choice list
Concept List epsos-dataelement-85.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.5 (version DYNAMIC)
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Problem Status
Id epsos-dataelement-307 (2013‑10‑24 14:23:02)
Cardinality 0..1
Concept inherits from epsos-dataelement-305 (2013‑11‑28 16:40:53)
Description
Value Domain Type code
Choice list
Concept List epsos-dataelement-305.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.15 (version DYNAMIC)
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Problem Severity
Id epsos-dataelement-303 (2013‑10‑24 14:23:02)
Cardinality 0..1
Concept inherits from epsos-dataelement-301 (2013‑11‑28)
Description
Value Domain Type code
Choice list
Concept List epsos-dataelement-301.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.13 (version DYNAMIC)
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Onset Time
Id epsos-dataelement-231 (2013‑10‑24 14:26:31)
Cardinality 1..1 Required
Concept inherits from epsos-dataelement-86 (2013‑05‑31)
Description Date of problem onset
Value Domain Type date
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Disability or function
Id epsos-dataelement-98 (2013‑05‑31)
Cardinality 0..*
notice There is an open issue with this item:
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Invalidity description
Id epsos-dataelement-99 (2013‑05‑31)
Cardinality 0..1 Required
Description Need of the patient to be continuously assisted by third parties. Invalidity status may influence decisions about how to administer treatments
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Onset time
Id epsos-dataelement-132 (2013‑09‑26 17:03:54)
Cardinality 0..1
Description Date of invalidity onset
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Medication
Id epsos-dataelement-101 (2013‑05‑31)
Cardinality 0..1
notice There is an open issue with this item:
Description
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
folder draft Prescription
Id epsos-dataelement-102 (2013‑05‑31)
Cardinality Conditional

Condition Card/Conf
All prescribed medicine whose period of time indicated for the treatment has not yet expired 0..* Required
otherwise 0..0 Not present
Description
Used by 4 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..* Conditional) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)
draft Date of issue of prescription
Id 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)
draft Active ingredient
Id epsos-dataelement-103 (2013‑05‑31)
Cardinality 1..* Required
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
target This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..* Required) in scenario Patient Summary (PS)
draft Active ingredient code
Id 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
target This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..* Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..* Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)
draft Pharmaceutical dose form
Id 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..* Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..* Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Required) in scenario Patient Summary (PS)
draft Route of administration
Id 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
target This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Prescriber
Id epsos-dataelement-236 (2013‑11‑27 11:02:18)
Cardinality 0..1
Description
Used by 4 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
draft Prescriber Profession
Id 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Prescriber Speciality
Id epsos-dataelement-238 (2013‑11‑27 11:03:56)
Cardinality 0..1
notice 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
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Timestamp of Prescribing
Id 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Prescriber Telecom
Id epsos-dataelement-282 (2013‑11‑27 12:27:48)
Cardinality 0..*
Description
Used by 4 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Email
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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Healthcare Facility Telecom
Id epsos-dataelement-283 (2013‑11‑27 12:28:21)
Cardinality 0..*
Description
Used by 4 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (0..*) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Email
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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Dispense
Id epsos-dataelement-143 (2013‑09‑27 11:07:44)
Cardinality 0..*
notice There is an open issue with this item:
Description Information about dispensed medication
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
Concept
draft Dispense identification
Id epsos-dataelement-165 (2013‑09‑27 11:24:33)
Cardinality 1..1 Mandatory
Description Unique identification of the dispensed medication
Value Domain Type identifier
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
draft Date of issue of dispense
Id epsos-dataelement-173 (2013‑09‑27 11:56:36)
Cardinality 1..1 Required
Description Date when the medicine has been dispensed
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
draft Related Prescription
Id epsos-dataelement-162 (2013‑09‑27 11:23:03)
Cardinality 0..1 Required
Description The ID of the prescription serving as the basis for the dispensation
Value Domain Type identifier
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
draft Related Prescription Item
Id epsos-dataelement-299 (2013‑11‑27 15:46:07)
Cardinality 0..1 Required
Description Identification of the item or medicine of the related prescription (country A) of the dispensed medicine. One prescription might contain more than one item or medicine. In the country where prescriptions contain just one item, then the prescription ID=Prescription ID item.
Value Domain Type string
Used by 2 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
draft Brand name
Id epsos-dataelement-172 (2013‑09‑27 11:55:24)
Cardinality 0..1 Required
Concept inherits from epsos-dataelement-137 (2013‑09‑27 10:52:59)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
draft Active ingredient
Id epsos-dataelement-160 (2013‑09‑27 11:21:54)
Cardinality 1..* Mandatory
Concept inherits from epsos-dataelement-103 (2013‑05‑31)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..* Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)
draft Active ingredient code
Id epsos-dataelement-159 (2013‑09‑27 11:21:31)
Cardinality 1..* Required
Concept inherits from epsos-dataelement-104 (2013‑05‑31)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
draft Strength
Id epsos-dataelement-156 (2013‑09‑27 11:19:20)
Cardinality 1..* Mandatory
Concept inherits from epsos-dataelement-105 (2013‑05‑31)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..* Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)
draft Medicinal product package size
Id epsos-dataelement-158 (2013‑09‑27 11:20:47)
Cardinality 1..1 Mandatory
Concept inherits from epsos-dataelement-138 (2013‑09‑27 10:54:04)
Description The size of the package prescribed
Value Domain Type count
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
draft Pharmaceutical dose form
Id epsos-dataelement-154 (2013‑09‑27 11:17:44)
Cardinality 1..1 Mandatory
Concept inherits from epsos-dataelement-106 (2013‑05‑31)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
draft Route of administration
Id epsos-dataelement-153 (2013‑09‑27 11:17:25)
Cardinality 0..1 Required
Concept inherits from epsos-dataelement-140 (2013‑09‑27 11:05:39)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
draft Number of packages
Id epsos-dataelement-152 (2013‑09‑27 11:16:30)
Cardinality 0..1 Required
Concept inherits from epsos-dataelement-139 (2013‑09‑27 11:00:57)
Description Number of boxes that have been prescribed
Value Domain Type quantity
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
draft Number of units per intake
Id epsos-dataelement-151 (2013‑09‑27 11:16:10)
Cardinality 1..1 Required
Concept inherits from epsos-dataelement-107 (2013‑05‑31)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
draft Frequency of intakes
Id epsos-dataelement-150 (2013‑09‑27 11:15:17)
Cardinality 1..* Required
Concept inherits from epsos-dataelement-108 (2013‑05‑31)
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 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)
draft Substitution
Id epsos-dataelement-149 (2013‑09‑27 11:14:52)
Cardinality 0..1 Required
Description
Value Domain Type code
Choice list
Concept List epsos-dataelement-149.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.7 (version DYNAMIC)
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
draft Duration of treatment
Id epsos-dataelement-148 (2013‑09‑27 11:13:14)
Cardinality 0..1
Description
Value Domain Type duration
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Date of onset of treatment according to prescription
Id epsos-dataelement-147 (2013‑09‑27 11:11:54)
Cardinality 0..1
Description Date when the patient needs to start taking the medicine prescribed
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Validity of prescription
Id epsos-dataelement-146 (2013‑09‑27 11:10:32)
Cardinality 1..1 Required
Description Date of the end of the treatment or prescriptions where the end of treatment has expired
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
draft Date of onset of dispense
Id epsos-dataelement-145 (2013‑09‑27 11:09:52)
Cardinality 0..1
Description Date when the patient starts taking the medicine dispensed
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Expected date of end of treatment
Id epsos-dataelement-144 (2013‑09‑27 11:08:29)
Cardinality 0..1
Description Expectation when the patient stops taking the medicine dispensed
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Dispenser
Id epsos-dataelement-247 (2013‑11‑27 11:33:04)
Cardinality 0..1
notice There is an open issue with this item:
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
Concept
draft Timestamp of dispensing
Id epsos-dataelement-248 (2013‑11‑27 11:34:46)
Cardinality 0..1
Description Date/time the medication was dispensed
Value Domain Type datetime
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Dispenser Identification
Id epsos-dataelement-249 (2013‑11‑27 11:35:25)
Cardinality 0..1
Description Unique identification of the dispenser
Value Domain Type identifier
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Dispenser Full Name
Id epsos-dataelement-250 (2013‑11‑27 11:36:33)
Cardinality 0..*
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
Concept
draft Given
Id epsos-dataelement-251 (2013‑11‑27 11:36:48)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Family Name/Surname
Id epsos-dataelement-252 (2013‑11‑27 11:36:56)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Prefix
Id epsos-dataelement-271 (2013‑11‑27 11:46:35)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Suffix
Id epsos-dataelement-272 (2013‑11‑27 11:46:50)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Dispenser Telecom
Id epsos-dataelement-287 (2013‑11‑27 12:30:01)
Cardinality 0..*
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
Concept
draft Telephone No
Id epsos-dataelement-288 (2013‑11‑27 12:30:34)
Cardinality 0..1
Description
Value Domain Type count
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Email
Id epsos-dataelement-289 (2013‑11‑27 12:30:44)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Dispenser Healthcare Facility
Id epsos-dataelement-253 (2013‑11‑27 11:37:14)
Cardinality 0..*
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
Concept
draft Identifier
Id epsos-dataelement-254 (2013‑11‑27 11:37:32)
Cardinality 0..1
Description Unique identification of the healthcare facility
Value Domain Type identifier
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Name
Id epsos-dataelement-255 (2013‑11‑27 11:37:55)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Address
Id epsos-dataelement-256 (2013‑11‑27 11:38:16)
Cardinality 0..1
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
Concept
draft Street
Id epsos-dataelement-257 (2013‑11‑27 11:39:11)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Number of Street
Id epsos-dataelement-258 (2013‑11‑27 11:39:19)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft City
Id epsos-dataelement-259 (2013‑11‑27 11:39:29)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Postal Code
Id epsos-dataelement-260 (2013‑11‑27 11:39:37)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft State or Province
Id epsos-dataelement-261 (2013‑11‑27 11:39:47)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Country
Id epsos-dataelement-262 (2013‑11‑27 11:39:58)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Healthcare Facility Telecom
Id epsos-dataelement-284 (2013‑11‑27 12:29:02)
Cardinality 0..1
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)
Concept
draft Telephone No
Id epsos-dataelement-285 (2013‑11‑27 12:29:20)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Email
Id epsos-dataelement-286 (2013‑11‑27 12:29:33)
Cardinality 0..1
Description
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Dispenser Credentialing Organization
Id epsos-dataelement-293 (2013‑11‑27 13:40:22)
Cardinality 0..*
Description The organization which provided the credentialing for the dispenser
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
Concept
draft Identification
Id epsos-dataelement-294 (2013‑11‑27 13:41:16)
Cardinality 0..1
Description Unique identification of the organization which provided the credentialing for the dispenser
Value Domain Type identifier
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
draft Name
Id epsos-dataelement-295 (2013‑11‑27 13:41:34)
Cardinality 0..1
Description The name of the organization which provided the credentialing for the dispenser
Value Domain Type string
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
folder draft Physical Findings
Id epsos-dataelement-117 (2013‑05‑31)
Cardinality 0..* Required
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Vital Signs Observations
Id epsos-dataelement-118 (2013‑05‑31)
Cardinality 0..1
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Blood Pressure
Id epsos-dataelement-119 (2013‑05‑31)
Cardinality 0..1 Required
Description One value of blood pressure which includes: systolic Blood Pressure and Diastolic Blood pressure
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Systolic Blood Pressure
Id epsos-dataelement-120 (2013‑05‑31)
Cardinality 0..1 Required
Description
Terminology Asscociation This concept is represented by code "8480-6" (INTRAVASCULAR SYSTOLIC) from code system 8480-62 LOINC
Value Domain Type quantity
Property
Range unit min. fraction digits default fixed
min include max include        
mm[Hg]  
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Diastolic Blood Pressure
Id epsos-dataelement-121 (2013‑05‑31)
Cardinality 0..1 Required
Description
Terminology Asscociation This concept is represented by code "8462-4" (INTRAVASCULAR DIASTOLIC) from code system 8462-42 LOINC
Value Domain Type quantity
Property
Range unit min. fraction digits default fixed
min include max include        
mm[Hg]  
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Date when blood pressure was measured
Id epsos-dataelement-122 (2013‑05‑31)
Cardinality 0..1 Required
Description Date when blood pressure was measured
Value Domain Type date
Example 01/01/2010
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Diagnostic Tests
Id epsos-dataelement-123 (2013‑05‑31)
Cardinality 0..* Required
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Blood Group
Id epsos-dataelement-124 (2013‑05‑31)
Cardinality 0..1 Required
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
draft Result of Blood Group
Id epsos-dataelement-125 (2013‑05‑31)
Cardinality 0..1 Required
Description Result from the blood group test made to the patient
Value Domain Type code
Choice list
Concept List epsos-dataelement-125.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.20 (version DYNAMIC)
Example blood group A
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Date
Id epsos-dataelement-126 (2013‑05‑31)
Cardinality 0..1 Required
Description Date in which the blood group test was done. This field may contain only the year if day and month are not available. Eg: 01/01/2009
Value Domain Type date
Property
Timestamp precision
day, month and year
Example 01/01/2009
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Vaccination
Id epsos-dataelement-167 (2013‑09‑27)
Cardinality 0..* Required
Description
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Vaccine brand name
Id epsos-dataelement-168 (2013‑09‑27 11:27:51)
Cardinality 0..1 Required
Description Brand name of the vaccination
Value Domain Type string
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Vaccine description
Id epsos-dataelement-171 (2013‑09‑27 11:29:50)
Cardinality 0..1 Required
Description Description of the vaccine
Value Domain Type string
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Vaccine code
Id epsos-dataelement-170 (2013‑09‑27 11:29:18)
Cardinality 0..1 Required
Description The code of the vaccine
Value Domain Type code
Choice list
Concept List epsos-dataelement-170.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.28 (version DYNAMIC)
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Vaccination date
Id epsos-dataelement-169 (2013‑09‑27 11:28:23)
Cardinality 0..1 Required
Description The date the vaccination was done
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Allergy
Id epsos-dataelement-58 (2013‑05‑31)
Cardinality 0..* Required
Description Allergies and intolerances
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Allergy description
Id epsos-dataelement-68 (2013‑05‑31)
Cardinality 1..1 Required
Description Description of the clinical manifestation of the allergy reaction. Example: Anaphylactic shock, angioedema (the clinical manifestation also gives information about the severity of the observed reaction)
Value Domain Type string
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Allergy code
Id epsos-dataelement-69 (2013‑05‑31)
Cardinality 1..1 Required
Description The code of the allergy
Value Domain Type code
Choice list
Concept List epsos-dataelement-69.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.11 (version DYNAMIC)
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.18 (version DYNAMIC)
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Allergy Severity
Id epsos-dataelement-304 (2013‑05‑31)
Cardinality 0..1
Description
Value Domain Type code
Choice list
Concept List epsos-dataelement-304.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.13 (version DYNAMIC)
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Onset Date
Id epsos-dataelement-70 (2013‑05‑31)
Cardinality 0..1
Description Date when the allergy started
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Agent description
Id epsos-dataelement-71 (2013‑05‑31)
Cardinality 1..1 Required
Description Describes the agent (drug, food, chemical agent, etc) that is responsible for the adverse reaction
Value Domain Type string
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Agent Code
Id epsos-dataelement-72 (2013‑05‑31)
Cardinality 1..1 Required
Description The code of the allergen agent
Value Domain Type code
Choice list
Concept List epsos-dataelement-72.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.19 (version DYNAMIC)
Terminology Asscociation: This concept list is represented by Value Set 2.16.840.1.113883.3.1937.777.10.11.1 (version DYNAMIC)
Used by 3 scenarios, inherited once
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Pregnancy History
Id epsos-dataelement-115 (2013‑05‑31)
Cardinality 0..* Required
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Expected date of delivery
Id epsos-dataelement-116 (2013‑05‑31)
Cardinality 0..1 Required
Description Date in which the woman is due to give birth. Year, day and month are required.
Terminology Asscociation This concept is represented by code "11778-8" (Delivery date Clinical.estimated) from code system 11778-82 LOINC
Terminology Asscociation This concept is represented by code "11779-6" (Delivery date Estimated from last menstrual period) from code system 11779-62 LOINC
Terminology Asscociation This concept is represented by code "11780-4" (Delivery date Estimated from ovulation) from code system 11780-42 LOINC
Terminology Asscociation This concept is represented by code "11781-2" (Delivery US.composite.estimated) from code system 11781-22 LOINC
Value Domain Type date
Property
Timestamp precision
at least day, month and year
Example 01/01/2010
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Social History
Id epsos-dataelement-111 (2013‑05‑31)
Cardinality 0..1 Required
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
folder draft Social History Observations
Id epsos-dataelement-112 (2013‑05‑31)
Cardinality 0..* Required
Description
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..*) in scenario Patient Summary (PS)
Concept
draft Social History Observations related to: smoke, alcohol and diet
Id epsos-dataelement-113 (2013‑05‑31)
Cardinality 0..1 Required
Description
Value Domain Type code
Choice list
Concept List epsos-dataelement-113.0
Terminology Asscociation: This concept list is represented by Value Set 1.3.6.1.4.1.12559.11.10.1.3.1.42.14 (version DYNAMIC)
Example cigarette smoker
Example alcohol consumption
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Date range of observation
Id epsos-dataelement-114 (2013‑05‑31)
Cardinality 0..1 Required
Description
Value Domain Type string
Example 1974 to 2004
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
folder draft Document Data
Id epsos-dataelement-62 (2013‑06‑03)
Cardinality 1..1 Required
Description Information about the document itself
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Request eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (0..1) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft Type
Id 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
target This concept is used in transaction Request eP from country A (1..1) in scenario ePrescription (eP)
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Request MRO (1..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Request PS of country A (1..1) in scenario Patient Summary (PS)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft Confidentiality
Id 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
target This concept is used in transaction Return eP from country A (0..1 Required) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1 Required) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft Country B
Id epsos-dataelement-179 (2013‑10‑22 14:53:35)
Cardinality 1..1 Mandatory
Description Name of country B
Value Domain Type code
Choice list
Concept List epsos-dataelement-179.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)
Used by 3 scenarios, inherited 0 times
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
folder draft Topicality
Id epsos-dataelement-64 (2013‑06‑03)
Cardinality 1..1 Required
Description
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
draft Date Created
Id 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft Date of Last Update
Id epsos-dataelement-66 (2013‑06‑03)
Cardinality 1..1 Mandatory
Description Date on which the document was updated (date of last version)
Value Domain Type datetime
Property
Timestamp precision
at least day, month and year
Example 01/01/2012
Used by 2 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
folder draft Author
Id epsos-dataelement-67 (2013‑06‑03)
Cardinality 1..1 Mandatory
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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
Concept
draft 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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
folder draft Author Full Name
Id epsos-dataelement-19 (2013‑06‑03)
Cardinality 1..1 Required
Description The full name of the Health Professional
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
Concept
draft Given Name
Id epsos-dataelement-20 (2013‑06‑03)
Cardinality 0..* Required
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
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..* Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..* Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft Family Name/Surname
Id epsos-dataelement-21 (2013‑06‑03)
Cardinality 1..1 Required
Description This field can contain more than one element.
Value Domain Type string
Example Español Smith
Used by 5 scenarios, inherited 0 times
target This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
target This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft 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
target This concept is used in transaction Return eP from country A (0..1) in scenario ePrescription (eP)
target This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Return PS of country A (0..1) in scenario Patient Summary (PS)
draft Author Role
Id epsos-dataelement-180 (2013‑10‑22 14:55:03)
Cardinality 1..1
Description Role or specialism the author was in when sending the document.
Value Domain Type code
Choice list
Concept List epsos-dataelement-180.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 2 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (1..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1) in scenario Health Care Encounter Report (HCER)
folder draft Legal Entity
Id epsos-dataelement-177 (2013‑10‑22 14:49:20)
Cardinality 1..1 Required
Description Responsible for the data in the document
Used by 2 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)
Concept
draft Health Professional ID
Id epsos-dataelement-185 (2013‑10‑22 15:04:01)
Cardinality 0..1 Required
Description Health professional ID responsible for the data in the document
Value Domain Type identifier
Used by 2 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
draft Healthcare Provider ID
Id epsos-dataelement-181 (2013‑10‑22 14:56:55)
Cardinality 0..1 Required
Description Legal organization ID responsible for the data in het document
Value Domain Type identifier
Used by 2 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)
folder draft Health Professional Full Name
Id epsos-dataelement-275 (2013‑11‑27 11:48:33)
Cardinality 0..1
Description
Used by one scenario, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
Concept
draft Given Name
Id epsos-dataelement-183 (2013‑10‑22 14:59:02)
Cardinality 0..1 Required
Description Given name of the Health professional responsible for the data in the document
Value Domain Type string
Used by one scenario, inherited 0 times
target This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
draft Family Name/Surname
Id epsos-dataelement-184 (2013‑10‑22 15:02:05)
Cardinality 1..1 Required
Description Family name/Surname of the health professional responsible for the data in the document
Value Domain Type string
Used by one scenario, inherited 0 times
target This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
draft Prefix
Id epsos-dataelement-276 (2013‑11‑27 11:49:30)
Cardinality 0..1
Description Prefix of the health professional responsible for the data in the document
Value Domain Type string
Used by one scenario, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
draft Suffix
Id epsos-dataelement-277 (2013‑11‑27 11:49:43)
Cardinality 0..1
Description Suffix of the health professional responsible for the data in the document
Value Domain Type string
Used by one scenario, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
draft Health Professional Role
Id epsos-dataelement-182 (2013‑10‑22 14:58:14)
Cardinality 0..1
Description Role the health professional is in while being responsible for the document data
Value Domain Type code
Choice list
Concept List epsos-dataelement-182.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 2 scenarios, inherited 0 times
target This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
target This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)