DECOR Information for Project: epSOS (epsos-)

Issues already assigned

Currently assigned to: 5 (id Giorgio Cangioli)

open (epsos-issue-2) Add laparoscopic colectomy

Change Request (issue id 2.16.840.1.113883.3.1937.777.10.6.2)
Last assignment to Giorgio Cangioli
Issue Add laparoscopic colectomy
Id epsos-issue-2
Type Change Request
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-10 (2013‑06‑03)
Value Set Name Value Set Id Version / effective date Status
epSOSProcedures 1.3.6.1.4.1.12559.11.10.1.3.1.42.10 July 2009 - 2013‑06‑03 Draft
notice There is an open issue with this item:
A valid code from the code system:
Code System Name Code System Id Code System Version
 SNOMED-CT 2.16.840.1.113883.6.96
Or one of the following:
Level/ Type Code Display Name Code System Description
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Details arrowright Click here for all issue details

open (epsos-issue-24) Value set epSOSCodeProb without dataset binding

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.24)
Last assignment to Giorgio Cangioli
Issue Value set epSOSCodeProb without dataset binding
Id epsos-issue-24
Type Clarification needed
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-23 (2013‑06‑03)
Description
Contents are under IP and only available to epSOS participants. Refer to epSOS for access
Value Set Name Value Set Id Version / effective date Status
epSOSCodeProb 1.3.6.1.4.1.12559.11.10.1.3.1.42.23 July 2009 - 2013‑06‑03 Draft
notice There is an open issue with this item:
  • epsos-issue-24: Value set epSOSCodeProb without dataset binding (Open)
A valid code from the code system:
Code System Name Code System Id Code System Version
 SNOMED-CT 2.16.840.1.113883.6.96
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Details arrowright Click here for all issue details

open (epsos-issue-37) Value set epSOSDisplayLabel without dataset binding

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.37)
Last assignment to Giorgio Cangioli
Issue Value set epSOSDisplayLabel without dataset binding
Id epsos-issue-37
Type Clarification needed
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-46 (2013‑06‑03)
Description
The Value Set is used to denominate all the labels and messages adopted for the epSOS CDA display
Value Set Name Value Set Id Version / effective date Status
epSOSDisplayLabel 1.3.6.1.4.1.12559.11.10.1.3.1.42.46 2013‑06‑03 Draft
notice There is an open issue with this item:
  • epsos-issue-37: Value set epSOSDisplayLabel without dataset binding (Open)
Source Code System:
  • 1.3.6.1.4.1.12559.11.10.1.3.1.44.4 epSOSDisplayLabel
Level/ Type Code Display Name Code System Description
0-L 1 Active Ingredient epSOSDisplayLabel
0-L 10 Clinical Manifestation epSOSDisplayLabel
0-L 107 I confirm that the patient –data subject has consented to the following statement: ‘I agree that my Patient Summary may be transferred to a registered Health Professional in [COUNTRY B] for the purposes of providing me with medical care and/or medication’ epSOSDisplayLabel
0-L 11 Closed/Inactive Problem epSOSDisplayLabel
0-L 12 Contact Information epSOSDisplayLabel
0-L 13 Country epSOSDisplayLabel
0-L 14 Country A Medicinal Product Code epSOSDisplayLabel
0-L 15 Creation Date epSOSDisplayLabel
0-L 16 Custodian epSOSDisplayLabel
0-L 17 Date epSOSDisplayLabel
0-L 18 Date To epSOSDisplayLabel
0-L 19 Date of Birth epSOSDisplayLabel
0-L 2 Active Problem epSOSDisplayLabel
0-L 20 Date of Prescription epSOSDisplayLabel
0-L 21 Device/Implant epSOSDisplayLabel
0-L 22 Dispense epSOSDisplayLabel
0-L 23 Dispensed Package Size epSOSDisplayLabel
0-L 24 Dispensed Product epSOSDisplayLabel
0-L 25 Dose Form epSOSDisplayLabel
0-L 26 End Date epSOSDisplayLabel
0-L 27 Every epSOSDisplayLabel
0-L 28 Facility ID epSOSDisplayLabel
0-L 29 Facility Name epSOSDisplayLabel
0-L 3 Address epSOSDisplayLabel
0-L 30 Family Name epSOSDisplayLabel
0-L 31 for epSOSDisplayLabel
0-L 32 Frequency of Intakes epSOSDisplayLabel
0-L 33 Gender epSOSDisplayLabel
0-L 34 Given Name epSOSDisplayLabel
0-L 35 Guardian epSOSDisplayLabel
0-L 36 Implant Date epSOSDisplayLabel
0-L 37 Instructions to patient epSOSDisplayLabel
0-L 38 Is substitution of brand name allowed? epSOSDisplayLabel
0-L 39 Last Update epSOSDisplayLabel
0-L 4 Advise to the dispenser epSOSDisplayLabel
0-L 40 Legal Authenticator epSOSDisplayLabel
0-L 41 National Insurance Number epSOSDisplayLabel
0-L 42 No epSOSDisplayLabel
0-L 43 Number of packages epSOSDisplayLabel
0-L 44 Observation Type epSOSDisplayLabel
0-L 45 Onset Date epSOSDisplayLabel
0-L 46 Organisation Identifier epSOSDisplayLabel
0-L 47 Organisation Name epSOSDisplayLabel
0-L 48 Other Active Ingredients epSOSDisplayLabel
0-L 49 Other Contacts epSOSDisplayLabel
0-L 5 Agent epSOSDisplayLabel
0-L 50 Package Size epSOSDisplayLabel
0-L 51 Patient epSOSDisplayLabel
0-L 52 Patient IDs epSOSDisplayLabel
0-L 53 per unit epSOSDisplayLabel
0-L 54 Preferred HP/Legal organization to contact epSOSDisplayLabel
0-L 55 Prefix epSOSDisplayLabel
0-L 56 Prescriber epSOSDisplayLabel
0-L 57 Prescriber details epSOSDisplayLabel
0-L 58 Prescription ID epSOSDisplayLabel
0-L 59 Prescription Item Details epSOSDisplayLabel
0-L 6 at epSOSDisplayLabel
0-L 60 Prescription Item ID epSOSDisplayLabel
0-L 61 Prescription Items List epSOSDisplayLabel
0-L 62 Procedure epSOSDisplayLabel
0-L 63 Procedure Date epSOSDisplayLabel
0-L 64 Profession epSOSDisplayLabel
0-L 65 Reaction Type epSOSDisplayLabel
0-L 66 Regional/National Health ID epSOSDisplayLabel
0-L 67 Route of Administration epSOSDisplayLabel
0-L 68 See details epSOSDisplayLabel
0-L 69 Specialty epSOSDisplayLabel
0-L 7 Author (HP) epSOSDisplayLabel
0-L 70 Strength epSOSDisplayLabel
0-L 71 Substitute epSOSDisplayLabel
0-L 72 The Active Problem section is missing ! epSOSDisplayLabel
0-L 73 The Allergies, adverse reactions, alerts section is missing ! epSOSDisplayLabel
0-L 74 The Medical Devices and implants section is missing ! epSOSDisplayLabel
0-L 75 The Medication Summary section is missing ! epSOSDisplayLabel
0-L 76 The History of Procedures section is missing ! epSOSDisplayLabel
0-L 77 unit(s) epSOSDisplayLabel
0-L 78 Units per intake epSOSDisplayLabel
0-L 79 Vaccination epSOSDisplayLabel
0-L 8 Authoring Device epSOSDisplayLabel
0-L 80 Vaccination Date epSOSDisplayLabel
0-L 81 Yes epSOSDisplayLabel
0-L 82 I have identified the patient-data subject epSOSDisplayLabel
0-L 83 I confirm that the patient –data subject has consented to the following statement: ‘I agree that my ePrescription may be transferred to a registered Health Professional in [COUNTRY B] for the purposes of providing me with medical care and/or medication’ epSOSDisplayLabel
0-L 84 Observation Value epSOSDisplayLabel
0-L 85 Date From epSOSDisplayLabel
0-L 9 Brand Name epSOSDisplayLabel
0-L 99 Physical Findings epSOSDisplayLabel
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Details arrowright Click here for all issue details

open (epsos-issue-31) Value set epSOSPersonalRelationship without dataset binding

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.31)
Last assignment to Giorgio Cangioli
Issue Value set epSOSPersonalRelationship without dataset binding
Id epsos-issue-31
Type Clarification needed
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-38 (2013‑06‑03)
Description
The Value Set is used (optionally) to code the type of contact relationship between a person and the patient.
Value Set Name Value Set Id Version / effective date Status
epSOSPersonalRelationship 1.3.6.1.4.1.12559.11.10.1.3.1.42.38 913-20091020 - 2013‑06‑03 Draft
notice There is an open issue with this item:
  • epsos-issue-31: Value set epSOSPersonalRelationship without dataset binding (Open)
Source Code System:
  • 2.16.840.1.113883.5.111 RoleCode
Level/ Type Code Display Name Code System Description
0-L AUNT aunt RoleCode
0-L CHILD child RoleCode
0-L CHLDADOPT adopted child RoleCode
0-L CHLDFOST foster child RoleCode
0-L CHLDINLAW child in-law RoleCode
0-L COUSN cousin RoleCode
0-L DAU natural daughter RoleCode
0-L DAUADOPT adopted daughter RoleCode
0-L DAUC daughter RoleCode
0-L DAUFOST foster daughter RoleCode
0-L DAUINLAW daughter in-law RoleCode
0-L DOMPART domestic partner RoleCode
0-L FAMMEMB family member RoleCode
0-L FRND unrelated friend RoleCode
0-L FTH father RoleCode
0-L FTHINLAW father-in-law RoleCode
0-L GGRPRN great grandparent RoleCode
0-L GRNDCHILD grandchild RoleCode
0-L GRPRN grandparent RoleCode
0-L MTH mother RoleCode
0-L MTHINLAW mother-in-law RoleCode
0-L NBOR neighbor RoleCode
0-L NCHILD natural child RoleCode
0-L NIENEPH niece/nephew RoleCode
0-L PRN parent RoleCode
0-L PRNINLAW parent in-law RoleCode
0-L ROOM roomate RoleCode
0-L SIB sibling RoleCode
0-L SIGOTHR significant other RoleCode
0-L SON natural son RoleCode
0-L SONADOPT adopted son RoleCode
0-L SONC son RoleCode
0-L SONFOST foster son RoleCode
0-L SONINLAW son in-law RoleCode
0-L SPS spouse RoleCode
0-L STPCHLD step child RoleCode
0-L STPDAU stepdaughter RoleCode
0-L STPSON stepson RoleCode
0-L UNCLE uncle RoleCode
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Details arrowright Click here for all issue details

open (epsos-issue-32) Value set epSOSRoleClass without dataset binding

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.32)
Last assignment to Giorgio Cangioli
Issue Value set epSOSRoleClass without dataset binding
Id epsos-issue-32
Type Clarification needed
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-39 (2013‑06‑03)
Description
The Value Set is used to make the distinction between an emergency contact and the next of kin for a patient.
Value Set Name Value Set Id Version / effective date Status
epSOSRoleClass 1.3.6.1.4.1.12559.11.10.1.3.1.42.39 913-20091020 - 2013‑06‑03 Draft
notice There are open issues with this item:
  • epsos-issue-32: Value set epSOSRoleClass without dataset binding (Open)
  • epsos-issue-38: Two different descriptions in the documentation (Open)
Source Code System:
  • 2.16.840.1.113883.5.110 RoleClass
Level/ Type Code Display Name Code System Description
0-L ECON emergency contact RoleClass
0-L NOK next of kin RoleClass
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Issue epsos-issue-38
Details arrowright Click here for all issue details

open (epsos-issue-33) Value set epSOSTimingAddress without dataset binding

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.33)
Last assignment to Giorgio Cangioli
Issue Value set epSOSTimingAddress without dataset binding
Id epsos-issue-33
Type Clarification needed
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-40 (2013‑06‑03)
Description
The Value Set is used (optionally) to code the usage of a phone number, email and all telecommunications. Can be used for all phone numbers mentioned in the three CDA-documents.
Value Set Name Value Set Id Version / effective date Status
epSOSTelecomAddress 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 913-20091020 - 2013‑06‑03 Draft
notice There is an open issue with this item:
  • epsos-issue-33: Value set epSOSTimingAddress without dataset binding (Open)
Source Code System:
  • 2.16.840.1.113883.5.1119 AddressUse
Level/ Type Code Display Name Code System Description
0-L AS answering service AddressUse
0-L EC emergency contact AddressUse
0-L H home AddressUse
0-L HP primary home AddressUse
0-L HV vacation home AddressUse
0-L MC mobile contact AddressUse
0-L PG pager AddressUse
0-L WP work place AddressUse
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Details arrowright Click here for all issue details

open (epsos-issue-38) Two different descriptions in the documentation

Clarification needed (issue id 2.16.840.1.113883.3.1937.777.10.6.38)
Last assignment to Giorgio Cangioli
Issue Two different descriptions in the documentation
Id epsos-issue-38
Type Clarification needed
Status open Open, assigned
Priority normal
Object(s) Value set epsos-valueset-39 (2013‑06‑03)
Description
The Value Set is used to make the distinction between an emergency contact and the next of kin for a patient.
Value Set Name Value Set Id Version / effective date Status
epSOSRoleClass 1.3.6.1.4.1.12559.11.10.1.3.1.42.39 913-20091020 - 2013‑06‑03 Draft
notice There are open issues with this item:
  • epsos-issue-32: Value set epSOSRoleClass without dataset binding (Open)
  • epsos-issue-38: Two different descriptions in the documentation (Open)
Source Code System:
  • 2.16.840.1.113883.5.110 RoleClass
Level/ Type Code Display Name Code System Description
0-L ECON emergency contact RoleClass
0-L NOK next of kin RoleClass
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download CSV XML 
Issue Value set epSOSRoleClass without dataset binding epsos-issue-32
Details arrowright Click here for all issue details

open (epsos-issue-39) Element Indication

Change Request (issue id 2.16.840.1.113883.3.1937.777.10.6.39)
Last assignment to Giorgio Cangioli
Issue Element Indication
Id epsos-issue-39
Type Change Request
Status open Open, assigned
Priority normal
Object(s) Data element epsos-dataelement-143 "Dispense" from dataset "epSOS Data Set" 2013‑05‑30
Path to element: Clinical Data / Medication
folder draft Dispense
Id epsos-dataelement-143 (2013‑09‑27 11:07:44)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
Details arrowright Click here for all issue details

open (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
Id epsos-issue-42
Type Clarification needed
Status open 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
folder draft Medication
Id epsos-dataelement-101 (2013‑05‑31)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)