Issue 2.16.840.1.113883.3.1937.777.10.6.42

(epsos-issue-42) Status

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.42)

Last assignment to Giorgio Cangioli

Issue

Status

epsos-issue-42

Type

Clarification needed

Status

Open, assigned

Priority

normal

Object(s)

Data element epsos-dataelement-101 "Medication" from dataset "epSOS Data Set" 2013‑05‑30
Path to element: Clinical Data

Medication

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

Concept

Prescription

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

Concept

Prescription identification

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

Medicinal product code

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

Date of issue of prescription

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

Description

Date when medicine has been prescribed

Value Domain

Type

date

Property

Timestamp precision
at least day, month and year

Used by

4 scenarios, inherited 0 times

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

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

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

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

Brand name

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

Active ingredient

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

Active ingredient code

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

Description

Code that identifies the Active ingredient

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-104.0

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

Used by

4 scenarios, inherited once

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

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

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

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

Strength

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

Medicinal product package size

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

Pharmaceutical dose form

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

Description

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

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-106.0

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

Example

tablets

Example

syrup

Used by

4 scenarios, inherited once

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

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

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

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

Number of packages

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

Number of units per intake

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

Frequency of intakes

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

Duration of treatment

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

Date of onset of treatment

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

Route of administration

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

Description

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

NOTE FOR GUIDANCE ON DATA ELEMENTS AND STANDARDS FOR DRUG DICTIONARIES

(EMEA/CHMP/ICH/168535/2005)

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-140.0

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

Used by

4 scenarios, inherited once

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

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

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

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

Instructions to patient

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

Advice to dispenser

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

Prescriber

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

Concept

Prescriber Profession

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

Description

Value Domain

Type

code

Choice list

Concept List		epsos-dataelement-237.0

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

Used by

4 scenarios, inherited 0 times

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

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

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

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

Prescriber Speciality

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

Timestamp of Prescribing

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

Description

Date/time the medication was prescribed

Value Domain

Type

datetime

Property

Timestamp precision
at least day, month and year

Used by

4 scenarios, inherited 0 times

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

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

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

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

Prescriber Identification

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

Prescriber Full Name

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

Concept

Given Name

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

Family Name/Surname

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

Prefix

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

Suffix

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

Prescriber Telecom

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

Concept

Telephone No

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

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

Prescriber Healthcare Facility

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

Concept

Identifier

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

Name

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

Healthcare Facility Telecom

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

Concept

Telephone No

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

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

Prescriber Credentialing Organization

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

Concept

Identifier

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

Name

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

Dispense

Id	epsos-dataelement-143 (2013‑09‑27 11:07:44)
	There is an open issue with this item: epsos-issue-39: Element Indication (Open)
Description	Information about dispensed medication
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)

Concept

Dispense identification

Id	epsos-dataelement-165 (2013‑09‑27 11:24:33)
Description	Unique identification of the dispensed medication
Value Domain	Type	identifier
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

Date of issue of dispense

epsos-dataelement-173 (2013‑09‑27 11:56:36)

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

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

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

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

Related Prescription

Id	epsos-dataelement-162 (2013‑09‑27 11:23:03)
Description	The ID of the prescription serving as the basis for the dispensation
Value Domain	Type	identifier
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)

Related Prescription Item

Id	epsos-dataelement-299 (2013‑11‑27 15:46:07)
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
	This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)

Brand name

Id	epsos-dataelement-172 (2013‑09‑27 11:55:24)
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
	This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)

Active ingredient

Id	epsos-dataelement-160 (2013‑09‑27 11:21:54)
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
	This concept is used in transaction Send eD to country A (1..* Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)

Active ingredient code

epsos-dataelement-159 (2013‑09‑27 11:21:31)

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

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

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

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

Strength

Id	epsos-dataelement-156 (2013‑09‑27 11:19:20)
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
	This concept is used in transaction Send eD to country A (1..* Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..* Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario Health Care Encounter Report (HCER)

Medicinal product package size

Id	epsos-dataelement-158 (2013‑09‑27 11:20:47)
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
	This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Mandatory) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario Health Care Encounter Report (HCER)

Pharmaceutical dose form

epsos-dataelement-154 (2013‑09‑27 11:17:44)

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

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

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

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

Route of administration

epsos-dataelement-153 (2013‑09‑27 11:17:25)

Concept inherits from

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

Description

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

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

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

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

Number of packages

Id	epsos-dataelement-152 (2013‑09‑27 11:16:30)
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
	This concept is used in transaction Send eD to country A (0..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1 Required) in scenario Health Care Encounter Report (HCER)

Number of units per intake

Id	epsos-dataelement-151 (2013‑09‑27 11:16:10)
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
	This concept is used in transaction Send eD to country A (1..1 Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..1 Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..1 Required) in scenario Health Care Encounter Report (HCER)

Frequency of intakes

Id	epsos-dataelement-150 (2013‑09‑27 11:15:17)
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
	This concept is used in transaction Send eD to country A (1..* Required) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (1..* Required) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (1..* Required) in scenario Health Care Encounter Report (HCER)

Substitution

epsos-dataelement-149 (2013‑09‑27 11:14:52)

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

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

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

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

Duration of treatment

Id	epsos-dataelement-148 (2013‑09‑27 11:13:14)
Description
Value Domain	Type	duration
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Date of onset of treatment according to prescription

epsos-dataelement-147 (2013‑09‑27 11:11:54)

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

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

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

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

Validity of prescription

epsos-dataelement-146 (2013‑09‑27 11:10:32)

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

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

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

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

Date of onset of dispense

epsos-dataelement-145 (2013‑09‑27 11:09:52)

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

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

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

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

Expected date of end of treatment

epsos-dataelement-144 (2013‑09‑27 11:08:29)

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

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

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

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

Dispenser

Id	epsos-dataelement-247 (2013‑11‑27 11:33:04)
	There is an open issue with this item: epsos-issue-50: Missing concepts for Dispenser? (Open)
Description
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Concept

Timestamp of dispensing

epsos-dataelement-248 (2013‑11‑27 11:34:46)

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

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

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

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

Dispenser Identification

Id	epsos-dataelement-249 (2013‑11‑27 11:35:25)
Description	Unique identification of the dispenser
Value Domain	Type	identifier
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Dispenser Full Name

Id	epsos-dataelement-250 (2013‑11‑27 11:36:33)
Description
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Concept

Given

Id	epsos-dataelement-251 (2013‑11‑27 11:36:48)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Family Name/Surname

Id	epsos-dataelement-252 (2013‑11‑27 11:36:56)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Prefix

Id	epsos-dataelement-271 (2013‑11‑27 11:46:35)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Suffix

Id	epsos-dataelement-272 (2013‑11‑27 11:46:50)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Dispenser Telecom

Id	epsos-dataelement-287 (2013‑11‑27 12:30:01)
Description
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..*) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)

Concept

Telephone No

Id	epsos-dataelement-288 (2013‑11‑27 12:30:34)
Description
Value Domain	Type	count
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Id	epsos-dataelement-289 (2013‑11‑27 12:30:44)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Dispenser Healthcare Facility

Id	epsos-dataelement-253 (2013‑11‑27 11:37:14)
Description
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Concept

Identifier

Id	epsos-dataelement-254 (2013‑11‑27 11:37:32)
Description	Unique identification of the healthcare facility
Value Domain	Type	identifier
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Name

Id	epsos-dataelement-255 (2013‑11‑27 11:37:55)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Address

Id	epsos-dataelement-256 (2013‑11‑27 11:38:16)
Description
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Concept

Street

Id	epsos-dataelement-257 (2013‑11‑27 11:39:11)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Number of Street

Id	epsos-dataelement-258 (2013‑11‑27 11:39:19)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

City

Id	epsos-dataelement-259 (2013‑11‑27 11:39:29)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Postal Code

Id	epsos-dataelement-260 (2013‑11‑27 11:39:37)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

State or Province

Id	epsos-dataelement-261 (2013‑11‑27 11:39:47)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Country

Id	epsos-dataelement-262 (2013‑11‑27 11:39:58)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Healthcare Facility Telecom

Id	epsos-dataelement-284 (2013‑11‑27 12:29:02)
Description
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..*) in scenario Health Care Encounter Report (HCER)

Concept

Telephone No

Id	epsos-dataelement-285 (2013‑11‑27 12:29:20)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Id	epsos-dataelement-286 (2013‑11‑27 12:29:33)
Description
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Dispenser Credentialing Organization

Id	epsos-dataelement-293 (2013‑11‑27 13:40:22)
Description	The organization which provided the credentialing for the dispenser
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..*) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Concept

Identification

Id	epsos-dataelement-294 (2013‑11‑27 13:41:16)
Description	Unique identification of the organization which provided the credentialing for the dispenser
Value Domain	Type	identifier
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Name

Id	epsos-dataelement-295 (2013‑11‑27 13:41:34)
Description	The name of the organization which provided the credentialing for the dispenser
Value Domain	Type	string
Used by	3 scenarios, inherited 0 times
	This concept is used in transaction Send eD to country A (0..1) in scenario eDispensation (eD)
	This concept is used in transaction Return MRO (0..1) in scenario Medication Related Overview (MRO)
	This concept is used in transaction Send HCER to country A (0..1) in scenario Health Care Encounter Report (HCER)

Details

Click here for all issue details