| Name |
Id |
| epSOS Data Set |
2.16.840.1.113883.2.4.3.11.60.22.1.1 |
| Description |
| This data set represents the full data set as developed in the EU programme epSOS. |
  |
Patient Data |
|
|
| Concept |
| |
Identification |
| Id |
epsos-dataelement-6 |
| Description |
Country ID, unique for the patient in that country. Example: ID for United Kingdom
patient
|
| Used in |
5 scenarios, inherited 0 times |
 |
This concept is used in transaction Request eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request MRO (0..*) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request PS of country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
| Concept |
|
National Health Care patient ID (country of affiliation) |
|
|
|
National Health Care patient ID (country of treatment) |
| Id |
epsos-dataelement-234 |
| Description |
Country ID given in the country of treatment, unique for the patient in that country.
Identifier that identifies that patient within the country B eHealth Infrastructure.
|
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (0..0 Not present) in scenario
|
|
|
Other Identifier |
| Id |
epsos-dataelement-235 |
| Description |
Other identifiers than the national health care patient IDs from either the country
of affiliation or the country of treatment
|
| Value Domain |
Type |
identifier |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..*) in scenario
|
|
This concept is used in transaction Send eD to country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
| |
Personal Information |
|
|
| Concept |
| |
Full Name |
|
|
| Concept |
|
Given name |
| Id |
epsos-dataelement-12 |
| Description |
The Name of the patient (Example: John). This field can contain more than one element |
| Value Domain |
Type |
string |
| Example |
John |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Request eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Request MRO (0..*) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request PS of country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-13 |
| Description |
This field can containe more than one element. |
| Value Domain |
Type |
string |
| Example |
Español Smith |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Request eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Request MRO (0..*) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request PS of country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Prefix |
|
|
|
Suffix |
|
|
|
|
Date of Birth |
| Id |
epsos-dataelement-10 |
| Description |
The date of birth of the patient. This field may contain only the year if day and
month are not available
|
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| day, month and year |
|
| Example |
091/01/2009 |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Request eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Request MRO (0..*) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request PS of country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Gender |
| Id |
epsos-dataelement-11 |
| Description |
It must contained a recognized valid value for this field. |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-11.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSAdministrativeGender (DYNAMIC)
|
|
| Example |
M |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Request eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Request MRO (0..*) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request PS of country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Contact Information |
| Id |
epsos-dataelement-26 |
| Description |
Contact information of the patient, including information of the contacts of the patient. |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..*) in scenario
|
|
This concept is used in transaction Send eD to country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
| |
Address |
|
|
| Concept |
|
Street |
| Id |
epsos-dataelement-51 |
| Description |
Name of street where the patient lives |
| Value Domain |
Type |
string |
| Example |
Oxford |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Number of Street |
| Id |
epsos-dataelement-52 |
| Description |
House number where the patient lives |
| Value Domain |
Type |
string |
| Example |
221 |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
City |
| Id |
epsos-dataelement-55 |
| Description |
City where the patient lives |
| Value Domain |
Type |
string |
| Example |
London |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Postal Code |
| Id |
epsos-dataelement-53 |
| Description |
Postal code where the patient lives |
| Value Domain |
Type |
string |
| Example |
W1W 8LG |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
State or Province |
| Id |
epsos-dataelement-56 |
| Description |
State or province where the patient lives |
| Value Domain |
Type |
string |
| Example |
London |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Country |
| Id |
epsos-dataelement-54 |
| Description |
Country where the patient lives |
| Value Domain |
Type |
string |
| Example |
UK |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Telecom |
| Id |
epsos-dataelement-300 |
| Description |
Telecommunication addresses of the patient |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..* Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..* Required) in scenario
|
|
| Concept |
|
Telephone No |
| Id |
epsos-dataelement-28 |
| Description |
Telephone number of the patient |
| Value Domain |
Type |
string |
| Example |
+45 20 7025 6161 |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..*) in scenario
|
|
This concept is used in transaction Send eD to country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-29 |
| Description |
Email address of the patient |
| Value Domain |
Type |
string |
| Example |
jens@hotmail.com |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..*) in scenario
|
|
This concept is used in transaction Send eD to country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
| |
Preferred HP to contact |
| Id |
epsos-dataelement-30 |
| Description |
Preferred Health Professional to contact. A foreign HP may need a contact (HP/legal
organization) who knows the patient
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
| |
Full Name |
| Id |
epsos-dataelement-46 |
| Description |
Name of the HP/name of the legal organization. If it is an HP, the structure of the
name will be the same as described in ‘Full name’ (Given name, family name/surname)
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Given Name |
| Id |
epsos-dataelement-47 |
| Description |
The Name of the HP (Example: John). This field can contain more than one element |
| Value Domain |
Type |
string |
| Example |
John |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-48 |
| Description |
This field can contain more than one element. |
| Value Domain |
Type |
string |
| Example |
Español Smith |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Prefix |
| Id |
epsos-dataelement-265 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Suffix |
| Id |
epsos-dataelement-266 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1 Conditional) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Conditional) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Telephone No |
| Id |
epsos-dataelement-41 |
| Description |
Telephone number of the HP/name of the legal organization |
| Value Domain |
Type |
string |
| Example |
+45 20 7025 6161 |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..* Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-43 |
| Description |
Email address of the HP/name of the legal organization |
| Value Domain |
Type |
string |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..* Required) in scenario
|
|
This concept is used in transaction Send eD to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
| |
Legal Organization to contact |
| Id |
epsos-dataelement-31 |
| Description |
Legal organization to contact about patient. A foreign HP may need a contact (HP/legal
organization) who knows the patient
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Organization Name |
| Id |
epsos-dataelement-33 |
| Description |
Name of the organization |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Telephone No |
| Id |
epsos-dataelement-49 |
| Description |
Telephone number of the organization |
| Value Domain |
Type |
string |
| Example |
+45 20 7025 6161 |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-50 |
| Description |
Email address of the organization |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
| |
Contact Person/legal guardian |
| Id |
epsos-dataelement-34 |
| Description |
Contact or guardian of the patient |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Role of that person |
| Id |
epsos-dataelement-35 |
| Description |
The role of the person: contact person or legal guardian |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-35.0
|
| Concept |
Description |
Assigned references |
| Contact Person |
|
code "CON" from code system "RoleClass"
code "ECON" from code system "RoleClass"
|
| Legal Guardian |
|
code "GUARD" from code system "RoleClass"
|
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| |
Full Name |
| Id |
epsos-dataelement-36 |
| Description |
Full name of the contact person or guardian |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Given Name |
| Id |
epsos-dataelement-37 |
| Description |
The Name of the person (Example: John). This field can contain more than one element |
| Value Domain |
Type |
string |
| Example |
John |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-38 |
| Description |
This field can contain more than one element. |
| Value Domain |
Type |
string |
| Example |
Español Smith |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Prefix |
| Id |
epsos-dataelement-267 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Suffix |
| Id |
epsos-dataelement-268 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Telephone No |
| Id |
epsos-dataelement-39 |
| Description |
Telephone number of the person |
| Value Domain |
Type |
string |
| Example |
+45 20 7025 6161 |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-40 |
| Description |
Email address of the person |
| Value Domain |
Type |
string |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
|
|
Return date |
| Id |
epsos-dataelement-127 |
| Description |
Estimated date of return to country A |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
|
|
| |
Insurance Information |
| Id |
epsos-dataelement-14 |
| Description |
Information about the insurance of the patient |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Insurance Number |
| Id |
epsos-dataelement-15 |
| Description |
European Health Insurance Code (EHIC) number of the patient |
| Value Domain |
Type |
identifier |
| Example |
QQ 12 34 56 A |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
Clinical Data |
|
|
| Concept |
| |
Alerts |
| Id |
epsos-dataelement-197 |
| Description |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Allergy description |
| Id |
epsos-dataelement-204 |
| Inherited concept |
epsos-dataelement-58 as of 2013‑05‑31 |
| Description |
Description of the clinical manifestation of the allergy reaction. Example: Anaphylactic
shock, angioedema (the clinical manifestation also gives information about the severity
of the observed reaction)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Allergy description |
| Id |
epsos-dataelement-205 |
| Inherited concept |
epsos-dataelement-68 as of 2013‑05‑31 |
| Description |
Description of the clinical manifestation of the allergy reaction. Example: Anaphylactic
shock, angioedema (the clinical manifestation also gives information about the severity
of the observed reaction)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Allergy code |
| Id |
epsos-dataelement-206 |
| Inherited concept |
epsos-dataelement-69 as of 2013‑05‑31 |
| Description |
The code of the allergy |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-69.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSReactionAllergy (DYNAMIC)
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSAdverseEventType (DYNAMIC)
|
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Onset Date |
| Id |
epsos-dataelement-207 |
| Inherited concept |
epsos-dataelement-70 as of 2013‑05‑31 |
| Description |
Date when the allergy started |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Agent description |
| Id |
epsos-dataelement-208 |
| Inherited concept |
epsos-dataelement-71 as of 2013‑05‑31 |
| Description |
Describes the agent (drug, food, chemical agent, etc) that is responsible for the
adverse reaction
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Agent Code |
| Id |
epsos-dataelement-209 |
| Inherited concept |
epsos-dataelement-72 as of 2013‑05‑31 |
| Description |
The code of the allergen agent |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-72.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSAllergenNoDrugs (DYNAMIC)
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSWHO-ATC (DYNAMIC)
|
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Medical Alert Information |
| Id |
epsos-dataelement-214 |
| Description |
|
| Comment |
Other alerts not included in allergies |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Health Care Alert code |
| Id |
epsos-dataelement-216 |
 |
There is an open issue with this item:
- epsos-issue-47: Missing value set binding for Health Care Alert code (Open)
|
| Description |
The code of the health care alert |
| Value Domain |
Type |
code |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Health Care Alert description |
| Id |
epsos-dataelement-215 |
| Description |
Medical Alert Information: any other clinical information that is imperative to know
so that the life or health of the patient does not come under threat
|
| Value Domain |
Type |
string |
| Example |
intolerance to aspirin due to gastrointestinal bleeding |
| Example |
intolerance to captopril because of cough (the patient is not allergic to captopril
but can´t tolerate it because of persistent cough
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
History of Past Illness |
| Id |
epsos-dataelement-192 |
| Description |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Problem/diagnosis Description |
| Id |
epsos-dataelement-222 |
| Inherited concept |
epsos-dataelement-83 as of 2013‑05‑31 |
| Description |
Problems or diagnosis not included under the definition of ‘Current problems or diagnosis’.
Example: hepatic cyst (the patient has been treated with an hepatic cystectomy that
solved the problem and therefore it ́s a closed problem)
|
| Comment |
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Problem/diagnosis Description |
| Id |
epsos-dataelement-223 |
| Inherited concept |
epsos-dataelement-84 as of 2013‑05‑31 |
| Description |
Problems or diagnosis not included under the definition of ‘Current problems or diagnosis’.
Example: hepatic cyst (the patient has been treated with an hepatic cystectomy that
solved the problem and therefore it ́s a closed problem)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem/diagnosis Id (Code) |
| Id |
epsos-dataelement-224 |
| Inherited concept |
epsos-dataelement-85 as of 2013‑05‑31 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-85.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSIllnessesandDisorders (DYNAMIC)
|
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem Status |
| Id |
epsos-dataelement-306 |
| Inherited concept |
epsos-dataelement-305 as of 2013‑11‑28 16:40:53 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-305.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSStatusCode (DYNAMIC)
|
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem Severity |
| Id |
epsos-dataelement-302 |
| Inherited concept |
epsos-dataelement-301 as of 2013‑11‑28 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-301.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSSeverity (DYNAMIC)
|
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Onset Time |
| Id |
epsos-dataelement-225 |
| Inherited concept |
epsos-dataelement-86 as of 2013‑05‑31 |
| Description |
Date of problem onset |
| Value Domain |
Type |
date |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
End date |
| Id |
epsos-dataelement-226 |
| Inherited concept |
epsos-dataelement-174 as of 2013‑10‑16 14:07:46 |
| Description |
Problem resolution date |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Resolution Circumstances |
| Id |
epsos-dataelement-227 |
| Inherited concept |
epsos-dataelement-175 as of 2013‑10‑16 14:09:33 |
| Description |
Describes the reason by which the problem changed the status from current to inactive
(e.g. surgical procedure, medical treatment, etc). This field includes ‘free text’
if the resolution circumstances are not already included in other fields. Example:
It can happen that this field is already included in other like Surgical Procedure,
medical device etc, eg: hepatic cystectomy (this wil be the ‘Resolution Circumstances’
for the problem ‘hepatic cyst’ and will be included in surgical procedures)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Vaccine brand name |
| Id |
epsos-dataelement-217 |
| Inherited concept |
epsos-dataelement-167 as of 2013‑09‑27 |
| Description |
Brand name of the vaccination |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Vaccine brand name |
| Id |
epsos-dataelement-218 |
| Inherited concept |
epsos-dataelement-168 as of 2013‑09‑27 11:27:51 |
| Description |
Brand name of the vaccination |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Vaccine description |
| Id |
epsos-dataelement-219 |
| Inherited concept |
epsos-dataelement-171 as of 2013‑09‑27 11:29:50 |
| Description |
Description of the vaccine |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Vaccine code |
| Id |
epsos-dataelement-220 |
| Inherited concept |
epsos-dataelement-170 as of 2013‑09‑27 11:29:18 |
| Description |
The code of the vaccine |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-170.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSVaccine (DYNAMIC)
|
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Vaccination date |
| Id |
epsos-dataelement-221 |
| Inherited concept |
epsos-dataelement-169 as of 2013‑09‑27 11:28:23 |
| Description |
The date the vaccination was done |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Procedure description |
| Id |
epsos-dataelement-210 |
| Inherited concept |
epsos-dataelement-1 as of 2013‑05‑31 |
| Description |
Describes the type of procedure that has been executed as part of the healthcare event. |
| Value Domain |
Type |
string |
| Example |
Colonoscopy |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Procedure description |
| Id |
epsos-dataelement-211 |
| Inherited concept |
epsos-dataelement-3 as of 2013‑05‑31 |
| Description |
Describes the type of procedure that has been executed as part of the healthcare event. |
| Value Domain |
Type |
string |
| Example |
Colonoscopy |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Procedure Id (code) |
| Id |
epsos-dataelement-212 |
| Inherited concept |
epsos-dataelement-2 as of 2013‑05‑31 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-2.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSProcedures (DYNAMIC)
|
|
| Example |
73761001 |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Procedure Date |
| Id |
epsos-dataelement-213 |
| Inherited concept |
epsos-dataelement-4 as of 2013‑05‑31 |
| Description |
Date when procedure was performed |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Example |
02/14/2013 |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
Medical Problems |
| Id |
epsos-dataelement-82 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Problem/diagnosis Description |
| Id |
epsos-dataelement-228 |
| Inherited concept |
epsos-dataelement-83 as of 2013‑05‑31 |
| Description |
Problems or diagnosis not included under the definition of ‘Current problems or diagnosis’.
Example: hepatic cyst (the patient has been treated with an hepatic cystectomy that
solved the problem and therefore it ́s a closed problem)
|
| Comment |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..* Conditional) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Problem/diagnosis Description |
| Id |
epsos-dataelement-229 |
| Inherited concept |
epsos-dataelement-84 as of 2013‑05‑31 |
| Description |
Problems or diagnosis not included under the definition of ‘Current problems or diagnosis’.
Example: hepatic cyst (the patient has been treated with an hepatic cystectomy that
solved the problem and therefore it ́s a closed problem)
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem/diagnosis Id (Code) |
| Id |
epsos-dataelement-230 |
| Inherited concept |
epsos-dataelement-85 as of 2013‑05‑31 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-85.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSIllnessesandDisorders (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem Status |
| Id |
epsos-dataelement-307 |
| Inherited concept |
epsos-dataelement-305 as of 2013‑11‑28 16:40:53 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-305.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSStatusCode (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem Severity |
| Id |
epsos-dataelement-303 |
| Inherited concept |
epsos-dataelement-301 as of 2013‑11‑28 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-301.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSSeverity (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Onset Time |
| Id |
epsos-dataelement-231 |
| Inherited concept |
epsos-dataelement-86 as of 2013‑05‑31 |
| Description |
Date of problem onset |
| Value Domain |
Type |
date |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
End date |
| Id |
epsos-dataelement-232 |
| Inherited concept |
epsos-dataelement-174 as of 2013‑10‑16 14:07:46 |
| Description |
Problem resolution date |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Resolution Circumstances |
| Id |
epsos-dataelement-233 |
| Inherited concept |
epsos-dataelement-175 as of 2013‑10‑16 14:09:33 |
| Description |
Describes the reason by which the problem changed the status from current to inactive
(e.g. surgical procedure, medical treatment, etc). This field includes ‘free text’
if the resolution circumstances are not already included in other fields. Example:
It can happen that this field is already included in other like Surgical Procedure,
medical device etc, eg: hepatic cystectomy (this wil be the ‘Resolution Circumstances’
for the problem ‘hepatic cyst’ and will be included in surgical procedures)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Procedure description |
| Id |
epsos-dataelement-188 |
| Inherited concept |
epsos-dataelement-1 as of 2013‑05‑31 |
| Description |
Describes the type of procedure that has been executed as part of the healthcare event. |
| Value Domain |
Type |
string |
| Example |
Colonoscopy |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Procedure description |
| Id |
epsos-dataelement-189 |
| Inherited concept |
epsos-dataelement-3 as of 2013‑05‑31 |
| Description |
Describes the type of procedure that has been executed as part of the healthcare event. |
| Value Domain |
Type |
string |
| Example |
Colonoscopy |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Procedure Id (code) |
| Id |
epsos-dataelement-190 |
| Inherited concept |
epsos-dataelement-2 as of 2013‑05‑31 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-2.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSProcedures (DYNAMIC)
|
|
| Example |
73761001 |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Procedure Date |
| Id |
epsos-dataelement-191 |
| Inherited concept |
epsos-dataelement-4 as of 2013‑05‑31 |
| Description |
Date when procedure was performed |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Example |
02/14/2013 |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Medical Devices and Implants |
| Id |
epsos-dataelement-87 |
| Description |
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Medical Devices and Implants Description |
| Id |
epsos-dataelement-88 |
| Description |
Describes the patient's implanted and external medical devices and equipment that
their health status depends on. Includes devices as cardiac pacemakers, implantable
defribillator, prothesis, feromagnetic bone implants etc that are important to be
known by HP.
|
| Value Domain |
Type |
string |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Device Code |
| Id |
epsos-dataelement-89 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-89.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSMedicalDevices (DYNAMIC)
|
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Implant Date |
| Id |
epsos-dataelement-90 |
| Description |
|
| Value Domain |
Type |
date |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Treatments |
| Id |
epsos-dataelement-128 |
| Description |
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Treatment description |
| Id |
epsos-dataelement-129 |
| Description |
Therapeutic treatment that does not include drugs (diet, physical excersize constraints
etc)
|
| Value Domain |
Type |
string |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Treatment code |
| Id |
epsos-dataelement-130 |
|
There is an open issue with this item:
|
| Description |
normalized identifier, concept code |
| Value Domain |
Type |
code |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Onset time |
| Id |
epsos-dataelement-131 |
| Description |
Date of treatment onset |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Care plan |
| Id |
epsos-dataelement-95 |
| Description |
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Recommendations Description |
| Id |
epsos-dataelement-96 |
| Description |
Therapeutic recommendations that do not include drugs (diet, physical exercise constraints,
etc.)
|
| Value Domain |
Type |
string |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Recommendations Id (code) |
| Id |
epsos-dataelement-97 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-94.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSResolutionOutcome (DYNAMIC)
|
|
| Example |
73761001 |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Disability or function |
| Id |
epsos-dataelement-98 |
|
There is an open issue with this item:
|
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Invalidity description |
| Id |
epsos-dataelement-99 |
| Description |
Need of the patient to be continuously assisted by third parties. Invalidity status
may influence decisions about how to administer treatments
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Invalidity code |
| Id |
epsos-dataelement-100 |
| Description |
Code that identifies the invalidity |
| Value Domain |
Type |
code |
| Example |
73761001 |
|
|
Onset time |
| Id |
epsos-dataelement-132 |
| Description |
Date of invalidity onset |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
Medication |
| Id |
epsos-dataelement-101 |
|
There is an open issue with this item:
|
| Description |
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
| |
Prescription |
| Id |
epsos-dataelement-102 |
| Description |
|
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..* Conditional) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Conditional) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Prescription identification |
| Id |
epsos-dataelement-134 |
| Description |
Unique identification of the prescription |
| Value Domain |
Type |
identifier |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Medicinal product code |
| Id |
epsos-dataelement-135 |
| Description |
Code that identifies the medicinal product description |
| Value Domain |
Type |
code |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1 Required) in scenario
|
|
|
Date of issue of prescription |
| Id |
epsos-dataelement-136 |
| Description |
Date when medicine has been prescribed |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Brand name |
| Id |
epsos-dataelement-137 |
| Description |
Original brand name of the medicine (in the language of the country in which the prescription
was made)
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Required) in scenario
|
|
|
Active ingredient |
| Id |
epsos-dataelement-103 |
| 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 in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..* Required) in scenario
|
|
|
Active ingredient code |
| Id |
epsos-dataelement-104 |
| 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 epSOSActiveIngredient (DYNAMIC)
|
|
| Used in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..* Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..* Mandatory) in scenario
|
|
|
Strength |
| Id |
epsos-dataelement-105 |
| 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 in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..* Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..* Mandatory) in scenario
|
|
|
Medicinal product package size |
| Id |
epsos-dataelement-138 |
| Description |
The size of the package prescribed |
| Value Domain |
Type |
count |
| Used in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Required) in scenario
|
|
|
Pharmaceutical dose form |
| Id |
epsos-dataelement-106 |
| 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 epSOSDoseForm (DYNAMIC)
|
|
| Example |
tablets |
| Example |
syrup |
| Used in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Number of packages |
| Id |
epsos-dataelement-139 |
| Description |
Number of boxes that have been prescribed |
| Value Domain |
Type |
quantity |
| Used in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Required) in scenario
|
|
|
Number of units per intake |
| Id |
epsos-dataelement-107 |
| 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 in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Required) in scenario
|
|
|
Frequency of intakes |
| Id |
epsos-dataelement-108 |
| 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 in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (1..* Required) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..* Required) in scenario
|
|
|
Duration of treatment |
| Id |
epsos-dataelement-109 |
| 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 in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Required) in scenario
|
|
|
Date of onset of treatment |
| Id |
epsos-dataelement-110 |
| Description |
Date when patient needs to start taking the medicine prescribed |
| Value Domain |
Type |
datetime |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Required) in scenario
|
|
|
Route of administration |
| Id |
epsos-dataelement-140 |
| 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 epSOSRouteofAdministration (DYNAMIC)
|
|
| Used in |
4 scenarios, inherited once |
|
This concept is used in transaction Return eP from country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1 Required) in scenario
|
|
|
Instructions to patient |
| Id |
epsos-dataelement-141 |
| Description |
The prescriber might give to the patient instructions; They must be presented in the
original language.
|
| Value Domain |
Type |
text |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1 Required) in scenario
|
|
|
Advice to dispenser |
| Id |
epsos-dataelement-142 |
| 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 in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| |
Prescriber |
|
|
| Concept |
|
Prescriber Profession |
| Id |
epsos-dataelement-237 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
|
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Prescriber Speciality |
| Id |
epsos-dataelement-238 |
|
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 in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Timestamp of Prescribing |
| Id |
epsos-dataelement-239 |
| Description |
Date/time the medication was prescribed |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Prescriber Identification |
| Id |
epsos-dataelement-240 |
| Description |
Unique identification of the prescriber |
| Value Domain |
Type |
identifier |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| |
Prescriber Full Name |
| Id |
epsos-dataelement-241 |
| Description |
The full name of the Health Professional |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Given Name |
| Id |
epsos-dataelement-242 |
| Description |
The Name of the Prescriber (Example: John). This field can contain more than one element |
| Value Domain |
Type |
string |
| Example |
John |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-243 |
| Description |
This field can contain more than one element. |
| Value Domain |
Type |
string |
| Example |
Español Smith |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Prefix |
| Id |
epsos-dataelement-269 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Suffix |
| Id |
epsos-dataelement-270 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Prescriber Telecom |
|
|
| Concept |
|
Telephone No |
| Id |
epsos-dataelement-280 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-281 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Prescriber Healthcare Facility |
| Id |
epsos-dataelement-244 |
| Description |
Information about the healthcare facility where the health professional works |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Identifier |
| Id |
epsos-dataelement-245 |
| Description |
Unique identification of the healthcare facility |
| Value Domain |
Type |
identifier |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Name |
| Id |
epsos-dataelement-246 |
| Description |
Name of the healthcare facility |
| Value Domain |
Type |
string |
| Example |
St. Johns Hospital |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| |
Healthcare Facility Telecom |
|
|
| Concept |
|
Telephone No |
| Id |
epsos-dataelement-278 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-279 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
Prescriber Credentialing Organization |
| Id |
epsos-dataelement-290 |
| Description |
The organization which provided the credentialing for the prescriber |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Identifier |
| Id |
epsos-dataelement-291 |
| Description |
Unique identification of the organization which provided the credentialing for the
prescriber
|
| Value Domain |
Type |
identifier |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Name |
| Id |
epsos-dataelement-292 |
| Description |
The name of the organization which provided the credentialing for the prescriber |
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
|
| |
Dispense |
| Id |
epsos-dataelement-143 |
|
There are open issues with this item:
|
| Description |
Information about dispensed medication |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
| Concept |
|
Dispense identification |
| Id |
epsos-dataelement-165 |
| Description |
Unique identification of the dispensed medication |
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
|
Date of issue of dispense |
| Id |
epsos-dataelement-173 |
| Description |
Date when the medicine has been dispensed |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
|
Related Prescription |
| Id |
epsos-dataelement-162 |
| Description |
The ID of the prescription serving as the basis for the dispensation |
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
|
Related Prescription Item |
| Id |
epsos-dataelement-299 |
| 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 in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
|
Brand name |
| Id |
epsos-dataelement-172 |
| Inherited concept |
epsos-dataelement-137 as of 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
|
Active ingredient |
| Id |
epsos-dataelement-160 |
| Inherited concept |
epsos-dataelement-103 as of 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..* Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario
|
|
|
Active ingredient code |
| Id |
epsos-dataelement-159 |
| Inherited concept |
epsos-dataelement-104 as of 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 epSOSActiveIngredient (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Required) in scenario
|
|
|
Strength |
| Id |
epsos-dataelement-156 |
| Inherited concept |
epsos-dataelement-105 as of 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..* Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..* Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Mandatory) in scenario
|
|
|
Medicinal product package size |
| Id |
epsos-dataelement-158 |
| Inherited concept |
epsos-dataelement-138 as of 2013‑09‑27 10:54:04 |
| Description |
The size of the package prescribed |
| Value Domain |
Type |
count |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
|
Pharmaceutical dose form |
| Id |
epsos-dataelement-154 |
| Inherited concept |
epsos-dataelement-106 as of 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 epSOSDoseForm (DYNAMIC)
|
|
| Example |
tablets |
| Example |
syrup |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
|
Route of administration |
| Id |
epsos-dataelement-153 |
| Inherited concept |
epsos-dataelement-140 as of 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 epSOSRouteofAdministration (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
|
Number of packages |
| Id |
epsos-dataelement-152 |
| Inherited concept |
epsos-dataelement-139 as of 2013‑09‑27 11:00:57 |
| Description |
Number of boxes that have been prescribed |
| Value Domain |
Type |
quantity |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
|
Number of units per intake |
| Id |
epsos-dataelement-151 |
| Inherited concept |
epsos-dataelement-107 as of 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
|
Frequency of intakes |
| Id |
epsos-dataelement-150 |
| Inherited concept |
epsos-dataelement-108 as of 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..* Required) in scenario
|
|
This concept is used in transaction Return MRO (1..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..* Required) in scenario
|
|
|
Substitution |
| Id |
epsos-dataelement-149 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-149.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSSubstitutionCode (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
|
Duration of treatment |
| Id |
epsos-dataelement-148 |
| Description |
|
| Value Domain |
Type |
duration |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Date of onset of treatment according to prescription |
| Id |
epsos-dataelement-147 |
| 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Validity of prescription |
| Id |
epsos-dataelement-146 |
| 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 in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
|
Date of onset of dispense |
| Id |
epsos-dataelement-145 |
| Description |
Date when the patient starts taking the medicine dispensed |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Expected date of end of treatment |
| Id |
epsos-dataelement-144 |
| Description |
Expectation when the patient stops taking the medicine dispensed |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| |
Dispenser |
| Id |
epsos-dataelement-247 |
|
There is an open issue with this item:
|
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| Concept |
|
Timestamp of dispensing |
| Id |
epsos-dataelement-248 |
| Description |
Date/time the medication was dispensed |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Dispenser Identification |
| Id |
epsos-dataelement-249 |
| Description |
Unique identification of the dispenser |
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| |
Dispenser Full Name |
| Id |
epsos-dataelement-250 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| Concept |
|
Given |
| Id |
epsos-dataelement-251 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-252 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Prefix |
| Id |
epsos-dataelement-271 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Suffix |
| Id |
epsos-dataelement-272 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
| |
Dispenser Telecom |
| Id |
epsos-dataelement-287 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..*) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
| Concept |
|
Telephone No |
| Id |
epsos-dataelement-288 |
| Description |
|
| Value Domain |
Type |
count |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-289 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
| |
Dispenser Healthcare Facility |
| Id |
epsos-dataelement-253 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| Concept |
|
Identifier |
| Id |
epsos-dataelement-254 |
| Description |
Unique identification of the healthcare facility |
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Name |
| Id |
epsos-dataelement-255 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| |
Address |
| Id |
epsos-dataelement-256 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| Concept |
|
Street |
| Id |
epsos-dataelement-257 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Number of Street |
| Id |
epsos-dataelement-258 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
City |
| Id |
epsos-dataelement-259 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Postal Code |
| Id |
epsos-dataelement-260 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
State or Province |
| Id |
epsos-dataelement-261 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Country |
| Id |
epsos-dataelement-262 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
| |
Healthcare Facility Telecom |
| Id |
epsos-dataelement-284 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..*) in scenario
|
|
| Concept |
|
Telephone No |
| Id |
epsos-dataelement-285 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Email |
| Id |
epsos-dataelement-286 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
|
| |
Dispenser Credentialing Organization |
| Id |
epsos-dataelement-293 |
| Description |
The organization which provided the credentialing for the dispenser |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..*) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
| Concept |
|
Identification |
| Id |
epsos-dataelement-294 |
| Description |
Unique identification of the organization which provided the credentialing for the
dispenser
|
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
Name |
| Id |
epsos-dataelement-295 |
| Description |
The name of the organization which provided the credentialing for the dispenser |
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
|
|
|
| |
Surgical Procedure |
| Id |
epsos-dataelement-1 |
| Description |
|
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
This concept is represented by template id 1.3.6.1.4.1.19376.1.5.3.1.4.19 with the element id = epsos-template-element-62
|
|
| Concept |
|
Procedure description |
| Id |
epsos-dataelement-3 |
| Description |
Describes the type of procedure that has been executed as part of the healthcare event. |
| Value Domain |
Type |
string |
| Example |
Colonoscopy |
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
This concept is represented by template id 1.3.6.1.4.1.19376.1.5.3.1.4.19 with the element id = epsos-template-element-64
|
|
|
Procedure Id (code) |
| Id |
epsos-dataelement-2 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-2.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSProcedures (DYNAMIC)
|
|
| Example |
73761001 |
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
This concept is represented by template id 1.3.6.1.4.1.19376.1.5.3.1.4.19 with the element id = epsos-template-element-63
|
|
|
Procedure Date |
| Id |
epsos-dataelement-4 |
| Description |
Date when procedure was performed |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Example |
02/14/2013 |
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Problem/Diagnosis |
| Id |
epsos-dataelement-83 |
| Description |
|
| Comment |
|
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Problem/diagnosis Description |
| Id |
epsos-dataelement-84 |
| Description |
Problems or diagnosis not included under the definition of ‘Current problems or diagnosis’.
Example: hepatic cyst (the patient has been treated with an hepatic cystectomy that
solved the problem and therefore it ́s a closed problem)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem/diagnosis Id (Code) |
| Id |
epsos-dataelement-85 |
| Description |
Normalized identifier |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-85.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSIllnessesandDisorders (DYNAMIC)
|
|
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem Status |
| Id |
epsos-dataelement-305 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-305.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSStatusCode (DYNAMIC)
|
|
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Problem Severity |
| Id |
epsos-dataelement-301 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-301.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSSeverity (DYNAMIC)
|
|
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Onset Time |
| Id |
epsos-dataelement-86 |
| Description |
Date of problem onset |
| Value Domain |
Type |
date |
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
End date |
| Id |
epsos-dataelement-174 |
| Description |
Problem resolution date |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Resolution Circumstances |
| Id |
epsos-dataelement-175 |
| Description |
Describes the reason by which the problem changed the status from current to inactive
(e.g. surgical procedure, medical treatment, etc). This field includes ‘free text’
if the resolution circumstances are not already included in other fields. Example:
It can happen that this field is already included in other like Surgical Procedure,
medical device etc, eg: hepatic cystectomy (this wil be the ‘Resolution Circumstances’
for the problem ‘hepatic cyst’ and will be included in surgical procedures)
|
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 2 times |
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Physical Findings |
| Id |
epsos-dataelement-117 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
| |
Vital Signs Observations |
| Id |
epsos-dataelement-118 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
| |
Blood Pressure |
| Id |
epsos-dataelement-119 |
| Description |
One value of blood pressure which includes: systolic Blood Pressure and Diastolic
Blood pressure
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Systolic Blood Pressure |
| Id |
epsos-dataelement-120 |
| Description |
|
| Terminology Asscociation |
This concept is represented by code "8480-6" from code system 2.16.840.1.113883.6.1 LOINC |
| Value Domain |
Type |
quantity |
| Property |
| Range |
unit |
min. fraction digits |
default |
fixed |
| min include |
max include |
|
|
|
|
|
|
mm[Hg] |
|
|
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Diastolic Blood Pressure |
| Id |
epsos-dataelement-121 |
| Description |
|
| Terminology Asscociation |
This concept is represented by code "8462-4" from code system 2.16.840.1.113883.6.1 LOINC |
| Value Domain |
Type |
quantity |
| Property |
| Range |
unit |
min. fraction digits |
default |
fixed |
| min include |
max include |
|
|
|
|
|
|
mm[Hg] |
|
|
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Date when blood pressure was measured |
| Id |
epsos-dataelement-122 |
| Description |
Date when blood pressure was measured |
| Value Domain |
Type |
date |
| Example |
01/01/2010 |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
Diagnostic Tests |
| Id |
epsos-dataelement-123 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
| |
Blood Group |
| Id |
epsos-dataelement-124 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Result of Blood Group |
| Id |
epsos-dataelement-125 |
| Description |
Result from the blood group test made to the patient |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-125.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSBloodGroup (DYNAMIC)
|
|
| Example |
blood group A |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Date |
| Id |
epsos-dataelement-126 |
| Description |
Date in which the blood group test was done. This field may contain only the year
if day and month are not available. Eg: 01/01/2009
|
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| day, month and year |
|
| Example |
01/01/2009 |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
| |
Vaccination |
| Id |
epsos-dataelement-167 |
| Description |
|
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Vaccine brand name |
| Id |
epsos-dataelement-168 |
| Description |
Brand name of the vaccination |
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Vaccine description |
| Id |
epsos-dataelement-171 |
| Description |
Description of the vaccine |
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Vaccine code |
| Id |
epsos-dataelement-170 |
| Description |
The code of the vaccine |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-170.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSVaccine (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Vaccination date |
| Id |
epsos-dataelement-169 |
| Description |
The date the vaccination was done |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Allergy |
| Id |
epsos-dataelement-58 |
| Description |
Allergies and intolerances |
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Allergy description |
| Id |
epsos-dataelement-68 |
| Description |
Description of the clinical manifestation of the allergy reaction. Example: Anaphylactic
shock, angioedema (the clinical manifestation also gives information about the severity
of the observed reaction)
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Allergy code |
| Id |
epsos-dataelement-69 |
| Description |
The code of the allergy |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-69.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSReactionAllergy (DYNAMIC)
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSAdverseEventType (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Allergy Severity |
| Id |
epsos-dataelement-304 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-304.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSSeverity (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Onset Date |
| Id |
epsos-dataelement-70 |
| Description |
Date when the allergy started |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Agent description |
| Id |
epsos-dataelement-71 |
| Description |
Describes the agent (drug, food, chemical agent, etc) that is responsible for the
adverse reaction
|
| Value Domain |
Type |
string |
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Agent Code |
| Id |
epsos-dataelement-72 |
| Description |
The code of the allergen agent |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-72.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSAllergenNoDrugs (DYNAMIC)
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSWHO-ATC (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited once |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Pregnancy History |
| Id |
epsos-dataelement-115 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Expected date of delivery |
| Id |
epsos-dataelement-116 |
| Description |
Date in which the woman is due to give birth. Year, day and month are required. |
| Terminology Asscociation |
This concept is represented by code "11778-8" from code system 2.16.840.1.113883.6.1 LOINC |
| Terminology Asscociation |
This concept is represented by code "11779-6" from code system 2.16.840.1.113883.6.1 LOINC |
| Terminology Asscociation |
This concept is represented by code "11780-4" from code system 2.16.840.1.113883.6.1 LOINC |
| Terminology Asscociation |
This concept is represented by code "11781-2" from code system 2.16.840.1.113883.6.1 LOINC |
| Value Domain |
Type |
date |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Example |
01/01/2010 |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
| |
Social History |
| Id |
epsos-dataelement-111 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
| |
Social History Observations |
| Id |
epsos-dataelement-112 |
| Description |
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..*) in scenario
|
|
| Concept |
|
Social History Observations related to: smoke, alcohol and diet |
| Id |
epsos-dataelement-113 |
| Description |
|
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-113.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSSocialHistory (DYNAMIC)
|
|
| Example |
cigarette smoker |
| Example |
alcohol consumption |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Date range of observation |
| Id |
epsos-dataelement-114 |
| Description |
|
| Value Domain |
Type |
string |
| Example |
1974 to 2004 |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
|
| |
Document Data |
|
|
| Concept |
|
Identification |
| Id |
epsos-dataelement-176 |
| Description |
Identification of the document |
| Value Domain |
Type |
identifier |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Type |
| Id |
epsos-dataelement-296 |
| Description |
Type of the document |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-296.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSDocumentCode (DYNAMIC)
|
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Request eP from country A (1..1) in scenario
|
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request MRO (1..1) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Request PS of country A (1..1) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Confidentiality |
| Id |
epsos-dataelement-297 |
| Description |
Confidentiality of the document as a whole |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-297.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSConfidentiality (DYNAMIC)
|
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1 Required) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1 Required) in scenario
|
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1 Required) in scenario
|
|
|
Language |
| Id |
epsos-dataelement-298 |
| Description |
The principal language of the document |
| Operationalization |
The language code SHALL be in the form nn-CC. The nn portion SHALL be an ISO-639-1
language code in lower case derived by the Value Set epSOSLanguage. The CC portion
SHALL be an ISO-3166 country code in upper case derived by the value Set epSOSCountry
|
| Value Domain |
Type |
code |
| Example |
English in United Kingdom en-GB
|
| Example |
Dutch in The Netherlands nl-NL
|
| Example |
Dutch in Belgium nl-BE
|
| Example |
German in Germany de-DE
|
| Example |
German in Austria de-AT
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Country A |
| Id |
epsos-dataelement-63 |
| Description |
Name of country A |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-63.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSCountry (DYNAMIC)
|
|
| Example |
United Kindom |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Country B |
| Id |
epsos-dataelement-179 |
| Description |
Name of country B |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-179.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSCountry (DYNAMIC)
|
|
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
|
Nature |
| Id |
epsos-dataelement-186 |
| Description |
Define the context in which it was generated. Distinguish among three methodological
approaches to build the document: direct human intervention of a HP, automatically
generated and mixed approach
|
| Value Domain |
Type |
code |
|
| |
Topicality |
| Id |
epsos-dataelement-64 |
| Description |
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
| Concept |
|
Date Created |
| Id |
epsos-dataelement-65 |
| Description |
Date on which the document was generated |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Example |
01/01/2009 |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Date of Last Update |
| Id |
epsos-dataelement-66 |
| Description |
Date on which the document was updated (date of last version) |
| Value Domain |
Type |
datetime |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Example |
01/01/2012 |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
|
| |
Author |
| Id |
epsos-dataelement-67 |
| Description |
To highlight if the data is collected manually by an HP or is collected automatically
from different sources (eg: hospital doctor repository, GPs...etc) through predetermined
clinical rules.
|
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Author Identification |
| Id |
epsos-dataelement-22 |
| Description |
Unique identification of the Health Professional. |
| Value Domain |
Type |
identifier |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
| |
Author Full Name |
| Id |
epsos-dataelement-19 |
| Description |
The full name of the Health Professional |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
| Concept |
|
Given Name |
| Id |
epsos-dataelement-20 |
| Description |
The Name of the HP (Example: John). This field can contain more than one element |
| Value Domain |
Type |
string |
| Example |
John |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (0..* Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..* Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-21 |
| Description |
This field can contain more than one element. |
| Value Domain |
Type |
string |
| Example |
Español Smith |
| Used in |
5 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Prefix |
| Id |
epsos-dataelement-273 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
Suffix |
| Id |
epsos-dataelement-274 |
| Description |
|
| Value Domain |
Type |
string |
| Used in |
4 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
|
|
Author Role |
| Id |
epsos-dataelement-180 |
| Description |
Role or specialism the author was in when sending the document. |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-180.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSHealthcareProfessionalRoles (DYNAMIC) from 2013‑10‑22 15:42:28
|
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1) in scenario
|
|
| |
Author Healthcare Facility |
| Id |
epsos-dataelement-23 |
| Description |
Information about the healthcare facility where the health professional works |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (0..1) in scenario
|
|
This concept is used in transaction Send eD to country A (0..1) in scenario
|
|
This concept is used in transaction Return PS of country A (0..1) in scenario
|
|
| Concept |
|
Identifier |
| Id |
epsos-dataelement-25 |
| Description |
Unique identification of the healthcare facility |
| Value Domain |
Type |
identifier |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
Name |
| Id |
epsos-dataelement-24 |
| Description |
Name of the healthcare facility |
| Value Domain |
Type |
string |
| Example |
St. Johns Hospital |
| Used in |
3 scenarios, inherited 0 times |
|
This concept is used in transaction Return eP from country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Send eD to country A (1..1 Mandatory) in scenario
|
|
This concept is used in transaction Return PS of country A (1..1 Mandatory) in scenario
|
|
|
|
| |
Legal Entity |
| Id |
epsos-dataelement-177 |
| Description |
Responsible for the data in the document |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (1..1 Required) in scenario
|
|
| Concept |
|
Health Professional ID |
| Id |
epsos-dataelement-185 |
| Description |
Health professional ID responsible for the data in the document |
| Value Domain |
Type |
identifier |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
|
Healthcare Provider ID |
| Id |
epsos-dataelement-181 |
| Description |
Legal organization ID responsible for the data in het document |
| Value Domain |
Type |
identifier |
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1 Required) in scenario
|
|
| |
Health Professional Full Name |
| Id |
epsos-dataelement-275 |
| Description |
|
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
| Concept |
|
Given Name |
| Id |
epsos-dataelement-183 |
| Description |
Given name of the Health professional responsible for the data in the document |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1 Required) in scenario
|
|
|
Family Name/Surname |
| Id |
epsos-dataelement-184 |
| Description |
Family name/Surname of the health professional responsible for the data in the document |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return MRO (1..1 Required) in scenario
|
|
|
Prefix |
| Id |
epsos-dataelement-276 |
| Description |
Prefix of the health professional responsible for the data in the document |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
|
Suffix |
| Id |
epsos-dataelement-277 |
| Description |
Suffix of the health professional responsible for the data in the document |
| Value Domain |
Type |
string |
| Used in |
one scenario, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
|
|
Health Professional Role |
| Id |
epsos-dataelement-182 |
| Description |
Role the health professional is in while being responsible for the document data |
| Value Domain |
Type |
code |
| Choice list |
| Concept List |
epsos-dataelement-182.0
|
|
| Terminology Asscociation: This concept list is represented by Value Set epSOSHealthcareProfessionalRoles (DYNAMIC) from 2013‑10‑22 15:21:34
|
|
| Used in |
2 scenarios, inherited 0 times |
|
This concept is used in transaction Return MRO (0..1) in scenario
|
|
This concept is used in transaction Send HCER to country A (0..1) in scenario
|
|
|
|
|
|
|