Transaction Return eP from country AID: 2.16.840.1.113883.3.1937.777.11.4.19Version Label: 2021-04-30T13:56:40Concepts: 91 (Groups: 23 - Items: 68) |
Click on triangles in the first column to open/close groups. Click the [-] sign to hide a column. Choose a column with 'Show column' to show it again. You can drag columns to re-arrange the view.
Name | ID[‑] | Mandatory[‑] | Max[‑] | Datatype CC[‑] | Datatype[‑] | Properties[‑] | Example[‑] | Codes[‑] | Description[‑] | Context[‑] | Source[‑] | Rationale[‑] | Operationalizations[‑] | Comment[‑] | Mapping[‑] | Terminology[‑] | Value Set[‑] | Type[‑] | Parent concept[‑] | Inherit from[‑] |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Patient Data | epsos-dataelement-5 | - | 1 | 0 … 1 | Information about the patient |
|
hl7:recordTarget - 1 … * R
hl7:recordTarget - 1 … * R
hl7:recordTarget - 1 … * R
hl7:recordTarget - 1 … * R
|
|
Group | |||||||||||
Identification | epsos-dataelement-6 | + | 1 | 1 … 1 M | Country ID, unique for the patient in that country. Example: ID for United Kingdom patient |
|
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
|
|
Group | Patient Data | ||||||||||
National Health Care patient ID (country of affiliation) | epsos-dataelement-7 | + | 1 | 1 … 1 M Identifier | Identifier | 999999512; 943 476 5919 | Country ID from the country of origin, unique for the patient in that country. Example: ID for United Kingdom patient |
|
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
|
|
Item | Identification | ||||||||
Other Identifier | epsos-dataelement-235 | - | n | 0 … * Identifier | Identifier | Other identifiers than the national health care patient IDs from either the country of affiliation or the country of treatment |
|
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
hl7:id - 1 … * R (Patient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number))
|
|
Item | Identification | |||||||||
Personal Information | epsos-dataelement-8 | - | 1 | 1 … 1 R | Personal information about the patient |
|
hl7:patient - 1 … 1 M
hl7:patient - 1 … 1 M
hl7:patient - 1 … 1 M
hl7:patient - 1 … 1 M
|
|
Group | Patient Data | ||||||||||
Full Name | epsos-dataelement-9 | - | 1 | 1 … 1 R | The full name of the patient |
|
hl7:name - 1 … * R (Patient Name)
hl7:name - 1 … * R (Patient Name)
hl7:name - 1 … * R (Patient Name)
hl7:name - 1 … * R (Patient Name)
|
|
Group | Personal Information | ||||||||||
Given name | epsos-dataelement-12 | - | 1 | 1 … 1 R String | String | John | The Name of the patient (Example: John). This field can contain more than one element |
|
hl7:given - 1 … * M (Patient's Given Name)
hl7:given - 1 … * M (Patient's Given Name)
hl7:given - 1 … * M (Patient's Given Name)
hl7:given - 1 … * M (Patient's Given Name)
|
|
Item | Full Name | ||||||||
Family Name/Surname | epsos-dataelement-13 | - | 1 | 1 … 1 R String | String | Español Smith | This field can containe more than one element. |
|
hl7:family - 1 … * M (Patient's Family Name/Surname)
hl7:family - 1 … * M (Patient's Family Name/Surname)
hl7:family - 1 … * M (Patient's Family Name/Surname)
hl7:family - 1 … * M (Patient's Family Name/Surname)
|
|
Item | Full Name | ||||||||
Prefix | epsos-dataelement-263 | - | 1 | 0 … 1 String | String |
|
hl7:prefix - 0 … * R (Patient's Prefix)
hl7:prefix - 0 … * R (Patient's Prefix)
hl7:prefix - 0 … * R (Patient's Prefix)
hl7:prefix - 0 … * R (Patient's Prefix)
|
|
Item | Full Name | ||||||||||
Suffix | epsos-dataelement-264 | - | 1 | 0 … 1 String | String |
|
|
Item | Full Name | |||||||||||
Date of Birth | epsos-dataelement-10 | - | 1 | 1 … 1 R Date | Date |
|
091/01/2009 | The date of birth of the patient. This field may contain only the year if day and month are not available |
|
hl7:birthTime - 1 … 1 M (Patient's Date of Birth. The patient date of birth may be a partial date such as only the year.)
hl7:birthTime - 1 … 1 M (Patient's Date of Birth. The patient date of birth may be a partial date such as only the year.)
hl7:birthTime - 1 … 1 M (Patient's Date of Birth. The patient date of birth may be a partial date such as only the year.)
hl7:birthTime - 1 … 1 M (Patient's Date of Birth. The patient date of birth may be a partial date such as only the year.)
|
|
Item | Personal Information | |||||||
Gender | epsos-dataelement-11 | - | 1 | 1 … 1 R Code | Code | M |
|
It must contained a recognized valid value for this field. |
|
hl7:administrativeGenderCode - 1 … 1 R (Patient's Gender)
hl7:administrativeGenderCode - 1 … 1 R (Patient's Gender)
hl7:administrativeGenderCode - 1 … 1 R (Patient's Gender)
hl7:administrativeGenderCode - 1 … 1 R (Patient's Gender)
|
|
eHDSIAdministrativeGender 2020-04-21T18:00:00 (dynamic)
|
Item | Personal Information | ||||||
Contact Information | epsos-dataelement-26 | - | n | 0 … * | Contact information of the patient, including information of the contacts of the patient. |
|
hl7:patientRole - 1 … 1 M
hl7:patientRole - 1 … 1 M
hl7:patientRole - 1 … 1 M
hl7:patientRole - 1 … 1 M
|
|
Group | Patient Data | ||||||||||
Address | epsos-dataelement-27 | - | n | 0 … * | Address of the patient |
|
hl7:addr - 1 … 1 R (The patient address element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present.)
hl7:addr - 1 … 1 R (The patient address element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present.)
hl7:addr - 1 … 1 R (The patient address element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present.)
hl7:addr - 1 … 1 R (The patient address element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present.)
|
|
Group | Contact Information | ||||||||||
Street | epsos-dataelement-51 | - | 1 | 0 … 1 String | String | Oxford | Name of street where the patient lives |
|
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
|
|
Item | Address | ||||||||
Number of Street | epsos-dataelement-52 | - | 1 | 0 … 1 String | String | 221 | House number where the patient lives |
|
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
hl7:streetAddressLine - 0 … * R (Patient's Number of Street/Patient's Number of Street)
|
|
Item | Address | ||||||||
City | epsos-dataelement-55 | - | 1 | 0 … 1 String | String | London | City where the patient lives |
|
hl7:city - 0 … 1 R (Patient's City)
hl7:city - 0 … 1 R (Patient's City)
hl7:city - 0 … 1 R (Patient's City)
hl7:city - 0 … 1 R (Patient's City)
|
|
Item | Address | ||||||||
Postal Code | epsos-dataelement-53 | - | 1 | 0 … 1 String | String | W1W 8LG | Postal code where the patient lives |
|
hl7:postalCode - 0 … 1 R (Patient's Postal Code)
hl7:postalCode - 0 … 1 R (Patient's Postal Code)
hl7:postalCode - 0 … 1 R (Patient's Postal Code)
hl7:postalCode - 0 … 1 R (Patient's Postal Code)
|
|
Item | Address | ||||||||
State or Province | epsos-dataelement-56 | - | 1 | 0 … 1 String | String | London | State or province where the patient lives |
|
hl7:state - 0 … 1 R (Patient's State or Province)
hl7:state - 0 … 1 R (Patient's State or Province)
hl7:state - 0 … 1 R (Patient's State or Province)
hl7:state - 0 … 1 R (Patient's State or Province)
|
|
Item | Address | ||||||||
Country | epsos-dataelement-54 | - | 1 | 0 … 1 String | String | UK | Country where the patient lives |
|
hl7:country - 0 … 1 R (Patient's Country. When used addr.country it is always bound to the epSOSCountry value set)
hl7:country - 0 … 1 R (Patient's Country. When used addr.country it is always bound to the epSOSCountry value set)
hl7:country - 0 … 1 R (Patient's Country. When used addr.country it is always bound to the epSOSCountry value set)
hl7:country - 0 … 1 R (Patient's Country. When used addr.country it is always bound to the epSOSCountry value set)
|
|
Item | Address | ||||||||
Telecom | epsos-dataelement-300 | - | n | 1 … * R | Telecommunication addresses of the patient |
|
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
|
|
Group | Contact Information | ||||||||||
Telephone No | epsos-dataelement-28 | - | n | 0 … * String | String | +45 20 7025 6161 | Telephone number of the patient |
|
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
|
|
Item | Telecom | ||||||||
epsos-dataelement-29 | - | n | 0 … * String | String | jens@hotmail.com | Email address of the patient |
|
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
hl7:telecom - 1 … * R (Patient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.)
|
|
Item | Telecom | |||||||||
Preferred HP to contact | epsos-dataelement-30 | - | 1 | 0 … 1 | Preferred Health Professional to contact. A foreign HP may need a contact (HP/legal organization) who knows the patient |
|
hl7:participant[hl7:templateId/@root='1.3.6.1.4.1.19376.1.5.3.1.2.4'] - 0 … * R (Contact person / Preferred Health Professional to contact about patient.)
hl7:participant[hl7:templateId/@root='1.3.6.1.4.1.19376.1.5.3.1.2.4'] - 0 … * R (Contact person / Preferred Health Professional to contact about patient.)
|
|
Group | Contact Information | ||||||||||
Full Name | epsos-dataelement-46 | + | 1 | 1 … 1 M | 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) |
|
hl7:name - 1 … 1 R (Patient Contact's Name / Preferred HP's Name)
hl7:name - 1 … 1 R (Patient Contact's Name / Preferred HP's Name)
|
|
Group | Preferred HP to contact | ||||||||||
Given Name | epsos-dataelement-47 | - | 1 | 0 … 1 C String | String | John | The Name of the HP (Example: John). This field can contain more than one element |
|
hl7:given - 1 … * R (Patient Contact's Given Name / Preferred HP's Given Name)
hl7:given - 1 … * R (Patient Contact's Given Name / Preferred HP's Given Name)
|
|
Item | Full Name | ||||||||
Family Name/Surname | epsos-dataelement-48 | - | 1 | 0 … 1 C String | String | Español Smith | This field can contain more than one element. |
|
hl7:family - 1 … * R (Patient Contact's Family Name/Surname / Preferred HP's Family Name/Surname)
hl7:family - 1 … * R (Patient Contact's Family Name/Surname / Preferred HP's Family Name/Surname)
|
|
Item | Full Name | ||||||||
Prefix | epsos-dataelement-265 | - | 1 | 0 … 1 C String | String |
|
|
Item | Full Name | |||||||||||
Suffix | epsos-dataelement-266 | - | 1 | 0 … 1 C String | String |
|
|
Item | Full Name | |||||||||||
Telephone No | epsos-dataelement-41 | - | n | 1 … * R String | String | +45 20 7025 6161 | Telephone number of the HP/name of the legal organization |
|
hl7:telecom - 1 … * R (Patient Contact's / Preferred HP's/Legal Organization telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'UNK' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present)
hl7:telecom - 1 … * R (Patient Contact's / Preferred HP's/Legal Organization telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'UNK' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present)
|
|
Item | Preferred HP to contact | ||||||||
epsos-dataelement-43 | - | n | 1 … * R String | String | Email address of the HP/name of the legal organization |
|
hl7:telecom - 1 … * R (Patient Contact's / Preferred HP's/Legal Organization telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'UNK' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present)
hl7:telecom - 1 … * R (Patient Contact's / Preferred HP's/Legal Organization telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'UNK' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present)
|
|
Item | Preferred HP to contact | ||||||||||
Clinical Data | epsos-dataelement-16 | - | n | 0 … * | Clinical information of the patient |
|
hl7:structuredBody - 1 … 1 M
hl7:structuredBody - 1 … 1 M
hl7:structuredBody - 1 … 1 M
|
|
Group | |||||||||||
Medication | epsos-dataelement-101 | - | 1 | 0 … 1 |
|
hl7:section - 1 … 1 M
hl7:section - 1 … 1 M
hl7:section - 1 … 1 M
|
|
Group | Clinical Data | |||||||||||
Prescription | epsos-dataelement-102 | - | n | 0 … * |
|
|
Group | Medication | ||||||||||||
Prescription identification | epsos-dataelement-134 | + | 1 | 1 … 1 M Identifier | Identifier | Unique identification of the prescription |
|
|
Item | Prescription | ||||||||||
Medicinal product code | epsos-dataelement-135 | - | 1 | 0 … 1 R Code | Code | Code that identifies the medicinal product description |
|
hl7:code - 0 … 1 R ( The <code> element of the <manufacturedMaterial> describes the medication. For the scope of epSOS this is used to convey the “Country A Cross-border/regional/national medicinal product code. In a CDA document, the <originalText> shall contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant. Note: When the text is supplied from the narrative, the implication is that if the components of a combination medication are supplied in an entry, these must also be displayed in narrative text; the combination medication will not be able to be broken down into its component parts. This is entirely consistent with the CDA Release 2.0 requirements that the narrative supply the necessary and relevant human readable information content. )
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
hl7:code - 0 … 1 R (The element is used to convey a regional/national medicinal product code or MPID compliant with the IDMP system.The element MUST NOT be used to convey:ATC code (see generalizedMedicineClass instead)PCID code compliant with the IDMP system (containerPackagedMedicine.code to be added later for this use)The <originalText> under the code MAY be included, but is not expected to be processed by the recipient of the document. If included, it SHALL contain a <reference> whose URI value points to the generic name and strength of the medication in the narrative, or just the generic name alone if strength is not relevant.If the code is not available, the whole field SHOULD be skipped.)
|
|
Item | Prescription | |||||||||
Date of issue of prescription | epsos-dataelement-136 | + | 1 | 1 … 1 M Date | Date |
|
Date when medicine has been prescribed |
|
|
Item | Prescription | |||||||||
Brand name | epsos-dataelement-137 | - | 1 | 1 … 1 R String | String | Original brand name of the medicine (in the language of the country in which the prescription was made) |
|
hl7:name - 0 … 1 R ( In an epSOS ePrescriprion or eDispensation document, the element should contain the brand name of the medication.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
hl7:name - 0 … 1 R (If present in the document, the element SHALL contain the brand name (invented name) of the medicinal product according to its marketing authorization. No additional information about the product (such as strength, dose form, package type, etc) is normally permitted, unless it is an inseparable part of the brand name, as authorized by a Medicines Agency.If the information about the brand name is not available (for example it cannot be extracted from the long textual description of the medicinal product or the prescription is active ingredient based), the whole field SHOULD be skipped.)
|
|
Item | Prescription | |||||||||
Active ingredient | epsos-dataelement-103 | + | n | 1 … * M String | String | Paracetamol | Substance that alone or in combination with one or more other ingredients produces the intended activity of a medicinal product. |
|
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
epsos:name - 0 … 1 (Name of the substance)
|
|
Item | Prescription | ||||||||
Active ingredient code | epsos-dataelement-104 | + | n | 1 … * M Code | Code |
|
Code that identifies the Active ingredient |
|
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
epsos:code - 1 … 1 R
|
|
eHDSIActiveIngredient 2021-04-19T15:45:00 (dynamic)
|
Item | Prescription | |||||||
Strength | epsos-dataelement-105 | + | n | 1 … * M Quantity | Quantity | 500 mg per tablet | 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 |
|
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio. )
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the epSOSUnits Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>mg/dose</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the epSOSUnits Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>mg/dose</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the epSOSUnits Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>mg/dose</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the epSOSUnits Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>mg/dose</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the eHDSIUnit Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>mg/dose</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the eHDSIUnit Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation>
<epsos:originalText>mg/dose</epsos:originalText>
</epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:quantity - 1 … 1 M ( The medication strength is represented as the ratio of the active ingredient(s) to a unit of medication. The element contains the numerator and denominator of the strength ratio.The denominator element should contain an amount with its corresponding unit. Only when the numerator comes in a fractional form and cannot be separated into the numerator and denominator form, or is related to a unit of administration, a unit of '1' in the denominator is allowed.The units used must come from the eHDSIUnit Value Set.
The preferred way is to provide the medication strength in a coded form using the @numerator and @denominator attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation>
<epsos:originalText>mg/dose</epsos:originalText>
</epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
|
|
Item | Prescription | ||||||||
Medicinal product package size | epsos-dataelement-138 | - | 1 | 1 … 1 R Count | Count | The size of the package prescribed |
|
epsos:capacityQuantity - 1 … 1 M ()
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>packets each containing 21 tables of A and 7 tables of B</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.For sending an overall amount prescription, set the whole quantity here in combination with one package in the supply element.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>tablets</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>tablets</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.For sending an overall amount prescription, set the whole quantity here in combination with one package in the supply element.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>tablets</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.For sending an overall amount prescription, set the whole quantity here in combination with one package in the supply element.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation> <epsos:originalText>tablets</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.For sending an overall amount prescription, set the whole quantity here in combination with one package in the supply element.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation><epsos:originalText>tablets</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
epsos:capacityQuantity - 1 … 1 M (This element describes the capacity of the packaging.For sending an overall amount prescription, set the whole quantity here in combination with one package in the supply element.
The preferred way is to provide the capacity quantity in a coded form using the @unit and @value attributes.
If no coded information is available and even the use of UCUM annotations is not sufficient and more information is available within the national infrastructure, the originalText element can be used to add additional information:<epsos:translation><epsos:originalText>tablets</epsos:originalText></epsos:translation>
To improve understanding for the receiver, the additional information has to be provided in English.
)
|
|
Item | Prescription | |||||||||
Pharmaceutical dose form | epsos-dataelement-106 | + | 1 | 1 … 1 M Code | Code | tablets; syrup |
|
It is the form in which a pharmaceutical product is presented in the medicinal product package (e.g. tablets, syrup) |
|
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is epSOSDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is epSOSDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is epSOSDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is epSOSDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is epSOSDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is epSOSDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is eHDSIDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
epsos:formCode - 1 … 1 R (This code represents the form of the medication (e.g. tablet, capsule, liquid). The value of this code affects the units used in the substance administration quantity element – if the form is a tablet, for example, the unit is 1; if the form is a liquid, the unit will be part of UCUM. The value set is eHDSIDoseForm, OID: 1.3.6.1.4.1.12559.11.10.1.3.1.42.2. )
|
|
eHDSIDoseForm 2021-04-19T15:55:00 (dynamic)
|
Item | Prescription | ||||||
Number of packages | epsos-dataelement-139 | - | 1 | 1 … 1 R Quantity | Quantity | Number of boxes that have been prescribed |
|
|
Item | Prescription | ||||||||||
Number of units per intake | epsos-dataelement-107 | - | 1 | 1 … 1 R Quantity | Quantity | 1 tablet | The number of units per intake that the patient is taking (e.g. 1 tablet) |
|
hl7:doseQuantity - 0 … 1 R (The dose is specified in the <doseQuantity> element.If a dose range is given (e.g., 1-2 tablets, or 325-750mg), then the <low> and <high> bounds are specified in their respective elements...If the dose is in countable items (tablets, caplets, "eaches"), then the unit should be valorized = ‘1’. In this case it is allowed to used the UCUM annotations for describing the type of countable items (e.g. .{tablet}, {puff},..).The unit attribute – when expresses unit of measures- shall be derived from the Value Sets epSOSUnits, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 based on the UCUM code system. The countable units attribute is derived from the value set epSOSDoseForm, OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.2)
hl7:doseQuantity - 0 … 1 R (The dose is specified in the <doseQuantity> element.If a dose range is given (e.g., 1-2 tablets, or 325-750mg), then the <low> and <high> bounds are specified in their respective elements...If the dose is in countable items (tablets, caplets, "eaches"), then the unit should be valorized = ‘1’. In this case it is allowed to used the UCUM annotations for describing the type of countable items (e.g. .{tablet}, {puff},..).The unit attribute – when expresses unit of measures- shall be derived from the Value Sets epSOSUnits, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 based on the UCUM code system. The countable units attribute is derived from the value set epSOSDoseForm, OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.2)
hl7:doseQuantity - 0 … 1 R (The dose is specified in the <doseQuantity> element.If a dose range is given (e.g., 1-2 tablets, or 325-750mg), then the <low> and <high> bounds are specified in their respective elements...If the dose is in countable items (tablets, caplets, "eaches"), then the unit should be valorized = ‘1’. In this case it is allowed to used the UCUM annotations for describing the type of countable items (e.g. .{tablet}, {puff},..).The unit attribute – when expresses unit of measures- shall be derived from the Value Sets epSOSUnits, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 based on the UCUM code system. The countable units attribute is derived from the value set epSOSDoseForm, OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.2)
hl7:doseQuantity - 0 … 1 R (The dose is specified in the <doseQuantity> element.If a dose range is given (e.g., 1-2 tablets, or 325-750mg), then the <low> and <high> bounds are specified in their respective elements...If the dose is in countable items (tablets, caplets, "eaches"), then the unit should be valorized = ‘1’. In this case it is allowed to used the UCUM annotations for describing the type of countable items (e.g. .{tablet}, {puff},..).The unit attribute – when expresses unit of measures- shall be derived from the Value Sets epSOSUnits, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 based on the UCUM code system. The countable units attribute is derived from the value set epSOSDoseForm, OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.2)
hl7:doseQuantity - 0 … 1 R (The dose is specified in the <doseQuantity> element.If a dose range is given (e.g., 1-2 tablets, or 325-750mg), then the <low> and <high> bounds are specified in their respective elements...If the dose is in countable items (tablets, caplets, "eaches"), then the unit should be valorized = ‘1’. In this case it is allowed to used the UCUM annotations for describing the type of countable items (e.g. .{tablet}, {puff},..).The unit attribute – when expresses unit of measures- shall be derived from the Value Sets eHDSIUnit, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 based on the UCUM code system. The countable units attribute is derived from the value set eHDSIDoseForm, OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.2)
|
|
Item | Prescription | ||||||||
Frequency of intakes | epsos-dataelement-108 | - | n | 1 … * R Quantity | Quantity | each 24 hours | Frequency of intakes (per hours/day/month/ week..). Example: each 24 hours |
|
hl7:effectiveTime[position()>1] - 1 … * R (The second <effectiveTime> element records the frequency of administration. This <effectiveTime> element must be intersected with the previous time specification (operator='A'), producing the bounded set containing only those time specifications that fall within the start and stop time of the medication regimen. Several common frequency expressions appear in the table below, along with their XML representations. This effectiveTime has a xsi:type of either TS, PIVL_TS, EIVL_TS, or SXPR_TS. FrequencyDescriptionXML Representationb.i.d.Twice a day<effectiveTime xsi:type='PIVL_TS' institutionSpecified='true' operator='A'> <period value='12' unit='h' /></effectiveTime> q12hEvery 12 hours<effectiveTime xsi:type='PIVL_TS' institutionSpecified='false' operator='A'> <period value='12' unit='h' /></effectiveTime> OnceOnce, on 2005-09-01 at 1:18am.<effectiveTime xsi:type='TS' value='200509010118'/> t.i.d.Three times a day, at times determined by the person administering the medication .<effectiveTime xsi:type='PIVL_TS' institutionSpecified='true' operator='A'> <period value='8' unit='h' /></effectiveTime> q8hEvery 8 hours<effectiveTime xsi:type='PIVL_TS' institutionSpecified='false' operator='A'> <period value='8' unit='h' /></effectiveTime> qamIn the morning<effectiveTime xsi:type='EIVL' operator='A'> <event code='ACM'/></effectiveTime> Every day at 8 in the morning for 10 minutes<effectiveTime xsi:type='PIVL_TS' operator='A'> <phase> <low value="198701010800" inclusive="true"/> <width value="10" unit="min"/> </phase> <period value='1' unit='d'/></effectiveTime> q4-6hEvery 4 to 6 hours.<effectiveTime xsi:type="PIVL_TS" institutionSpecified="false" operator="A"> <period xsi:type="PPD_PQ" value="5" unit="h"> <standardDeviation value="1" unit="h"/> </period></effectiveTime> The mean (average) of the low and high values is specified for the period. The mean of 4 and 6 is 5. The standard deviation is recorded as one half the differences between the high and low values, with an unspecified distribution. The type attribute of the <effectiveTime> element describes the kind of frequency specification it contains. More detail is given for each type in the table below. xsi:typeDescriptionTSAn xsi:type of TS represents a single point in time, and is the simplest of all to represent. The value attribute of the <effectiveTime> element specifies the point in time in HL7 date-time format (CCYYMMDDHHMMSS) PIVL_TSAn xsi:type of PIVL_TS is the most commonly used, representing a periodic interval of time. The <low> element of <phase> may be present. If so it specifies the starting point, and only the lower order components of this value are relevant with respect to the <period>. The <width> element represents the duration of the dose administration (e.g., for IV administration). The <period> indicates how often the dose is given. Legal values for the unit attribute of <period> are s, min, h, d, wk and mo representing seconds,
minutes, hours, days, weeks, and months respectively. EIVL_TSAn xsi:type of EIVL_TS represents an event based time interval, where the event is not a precise time, but is often used for timing purposes (e.g. with meals, between meals, before breakfast, before sleep). Refer to the HL7 TimingEvent vocabulary for the codes to use for the <event> element. This interval may specify an <offset> which provides information about the time offset from the specified event (e.g., <offset><low value='-1' unit='h'/><width value='10' unit='min'/></offset> means 1 hour before the event. In that
same example, the <width> element indicates the duration for the dose to be given. SXPR_TSAn xsi:type of SXPR_TS represents a parenthetical set of time expressions. This type is used when the frequency varies over time (e.g., for some cases of tapered dosing, or to handle split dosing). The <comp> elements of this <effectiveTime> element are themselves time expressions (using any of the types listed above). Each <comp> element may specify an operator (e.g. to intersect or form the union of two sets). )
hl7:effectiveTime[position()>1] - 1 … * R (The second <effectiveTime> element records the frequency of administration. This <effectiveTime> element must be intersected with the previous time specification (operator='A'), producing the bounded set containing only those time specifications that fall within the start and stop time of the medication regimen. Several common frequency expressions appear in the table below, along with their XML representations. This effectiveTime has a xsi:type of either TS, PIVL_TS, EIVL_TS, or SXPR_TS. FrequencyDescriptionXML Representationb.i.d.Twice a day<effectiveTime xsi:type='PIVL_TS' institutionSpecified='true' operator='A'> <period value='12' unit='h' /></effectiveTime> q12hEvery 12 hours<effectiveTime xsi:type='PIVL_TS' institutionSpecified='false' operator='A'> <period value='12' unit='h' /></effectiveTime> OnceOnce, on 2005-09-01 at 1:18am.<effectiveTime xsi:type='TS' value='200509010118'/> t.i.d.Three times a day, at times determined by the person administering the medication .<effectiveTime xsi:type='PIVL_TS' institutionSpecified='true' operator='A'> <period value='8' unit='h' /></effectiveTime> q8hEvery 8 hours<effectiveTime xsi:type='PIVL_TS' institutionSpecified='false' operator='A'> <period value='8' unit='h' /></effectiveTime> qamIn the morning<effectiveTime xsi:type='EIVL' operator='A'> <event code='ACM'/></effectiveTime> Every day at 8 in the morning for 10 minutes<effectiveTime xsi:type='PIVL_TS' operator='A'> <phase> <low value="198701010800" inclusive="true"/> <width value="10" unit="min"/> </phase> <period value='1' unit='d'/></effectiveTime> q4-6hEvery 4 to 6 hours.<effectiveTime xsi:type="PIVL_TS" institutionSpecified="false" operator="A"> <period xsi:type="PPD_PQ" value="5" unit="h"> <standardDeviation value="1" unit="h"/> </period></effectiveTime> The mean (average) of the low and high values is specified for the period. The mean of 4 and 6 is 5. The standard deviation is recorded as one half the differences between the high and low values, with an unspecified distribution. The type attribute of the <effectiveTime> element describes the kind of frequency specification it contains. More detail is given for each type in the table below. xsi:typeDescriptionTSAn xsi:type of TS represents a single point in time, and is the simplest of all to represent. The value attribute of the <effectiveTime> element specifies the point in time in HL7 date-time format (CCYYMMDDHHMMSS) PIVL_TSAn xsi:type of PIVL_TS is the most commonly used, representing a periodic interval of time. The <low> element of <phase> may be present. If so it specifies the starting point, and only the lower order components of this value are relevant with respect to the <period>. The <width> element represents the duration of the dose administration (e.g., for IV administration). The <period> indicates how often the dose is given. Legal values for the unit attribute of <period> are s, min, h, d, wk and mo representing seconds,
minutes, hours, days, weeks, and months respectively. EIVL_TSAn xsi:type of EIVL_TS represents an event based time interval, where the event is not a precise time, but is often used for timing purposes (e.g. with meals, between meals, before breakfast, before sleep). Refer to the HL7 TimingEvent vocabulary for the codes to use for the <event> element. This interval may specify an <offset> which provides information about the time offset from the specified event (e.g., <offset><low value='-1' unit='h'/><width value='10' unit='min'/></offset> means 1 hour before the event. In that
same example, the <width> element indicates the duration for the dose to be given. SXPR_TSAn xsi:type of SXPR_TS represents a parenthetical set of time expressions. This type is used when the frequency varies over time (e.g., for some cases of tapered dosing, or to handle split dosing). The <comp> elements of this <effectiveTime> element are themselves time expressions (using any of the types listed above). Each <comp> element may specify an operator (e.g. to intersect or form the union of two sets). )
hl7:effectiveTime[@xsi:type='EIVL_TS'] - 0 … 1 C (An xsi:type of EIVL_TS represents an event based time interval, where the event is not a precise time, but is often used for timing purposes (e.g. with meals, between meals, before breakfast, before sleep). Refer to the epSOSTimingEvent value set for the codes to use for the <event> element. This interval may specify an <offset> which provides information about the time offset from the specified event (e.g., <offset><low value='-1' unit='h'/><width value='10' unit='min'/></offset> means 1 hour before the event. In that same example, the <width> element indicates the duration for the dose to be given.)
hl7:effectiveTime[@xsi:type='PIVL_TS'] - 0 … 1 C (An xsi:type of PIVL_TS is the most commonly used, representing a periodic interval of time. The <low> element of <phase> may be present. If so it specifies the starting point, and only the lower order components of this value are relevant with respect to the <period>. The <width> element represents the duration of the dose administration (e.g., for IV administration). The <period> indicates how often the dose is given. Legal values for the unit attribute of <period> are s, min, h, d, wk and mo representing seconds, minutes, hours, days, weeks, and months respectively.)
hl7:effectiveTime[@value or @nullFlavor] - 0 … 1 C (This required element describes the frequency of intakes. If not known it shall be valued with the nullflavor "UNK".An xsi:type of TS represents a single point in time, and is the simplest of all to represent. The value attribute of the <effectiveTime> element specifies the point in time in HL7 date-time format (CCYYMMDDHHMMSS))
hl7:effectiveTime[@xsi:type='SXPR_TS'] - 0 … 1 C (An xsi:type of SXPR_TS represents a parenthetical set of time expressions. This type is used when the frequency varies over time (e.g., for some cases of tapered dosing, or to handle split dosing). The <comp> elements of this <effectiveTime> element are themselves time expressions (using any of the types listed above). Each <comp> element may specify an operator (e.g. to intersect or form the union of two sets).)
hl7:effectiveTime[@xsi:type='EIVL_TS'] - 0 … 1 C (An xsi:type of EIVL_TS represents an event based time interval, where the event is not a precise time, but is often used for timing purposes (e.g. with meals, between meals, before breakfast, before sleep). Refer to the epSOSTimingEvent value set for the codes to use for the <event> element. This interval may specify an <offset> which provides information about the time offset from the specified event (e.g., <offset><low value='-1' unit='h'/><width value='10' unit='min'/></offset> means 1 hour before the event. In that same example, the <width> element indicates the duration for the dose to be given.)
hl7:effectiveTime[@xsi:type='PIVL_TS'] - 0 … 1 C (An xsi:type of PIVL_TS is the most commonly used, representing a periodic interval of time. The <low> element of <phase> may be present. If so it specifies the starting point, and only the lower order components of this value are relevant with respect to the <period>. The <width> element represents the duration of the dose administration (e.g., for IV administration). The <period> indicates how often the dose is given. Legal values for the unit attribute of <period> are s, min, h, d, wk and mo representing seconds, minutes, hours, days, weeks, and months respectively.)
hl7:effectiveTime[(@value or @nullFlavor) and not(@xsi:type='IVL_TS' or @xsi:type='PIVL_TS' or @xsi:type='EIVL_TS' or @xsi:type='SXPR_TS')] - 0 … 1 C (This required element describes the frequency of intakes. If not known it shall be valued with the nullflavor "UNK".An xsi:type of TS represents a single point in time, and is the simplest of all to represent. The value attribute of the <effectiveTime> element specifies the point in time in HL7 date-time format (CCYYMMDDHHMMSS))
hl7:effectiveTime[@xsi:type='SXPR_TS'] - 0 … 1 C (An xsi:type of SXPR_TS represents a parenthetical set of time expressions. This type is used when the frequency varies over time (e.g., for some cases of tapered dosing, or to handle split dosing). The <comp> elements of this <effectiveTime> element are themselves time expressions (using any of the types listed above). Each <comp> element may specify an operator (e.g. to intersect or form the union of two sets).)
hl7:effectiveTime[@xsi:type='EIVL_TS'] - 0 … 1 C (An xsi:type of EIVL_TS represents an event based time interval, where the event is not a precise time, but is often used for timing purposes (e.g. with meals, between meals, before breakfast, before sleep). Refer to the eHDSITimingEvent value set for the codes to use for the <event> element. This interval may specify an <offset> which provides information about the time offset from the specified event (e.g., <offset><low value='-1' unit='h'/><width value='10' unit='min'/></offset> means 1 hour before the event. In that same example, the <width> element indicates the duration for the dose to be given.)
hl7:effectiveTime[@xsi:type='PIVL_TS'] - 0 … 1 C (An xsi:type of PIVL_TS is the most commonly used, representing a periodic interval of time. The <low> element of <phase> may be present. If so it specifies the starting point, and only the lower order components of this value are relevant with respect to the <period>. The <width> element represents the duration of the dose administration (e.g., for IV administration). The <period> indicates how often the dose is given. Legal values for the unit attribute of <period> are s, min, h, d, wk and mo representing seconds, minutes, hours, days, weeks, and months respectively.)
hl7:effectiveTime[(@value or @nullFlavor) and not(@xsi:type='IVL_TS' or @xsi:type='PIVL_TS' or @xsi:type='EIVL_TS' or @xsi:type='SXPR_TS')] - 0 … 1 C (This required element describes the frequency of intakes. If not known it shall be valued with the nullflavor "UNK".An xsi:type of TS represents a single point in time, and is the simplest of all to represent. The value attribute of the <effectiveTime> element specifies the point in time in HL7 date-time format (CCYYMMDDHHMMSS))
hl7:effectiveTime[@xsi:type='SXPR_TS'] - 0 … 1 C (An xsi:type of SXPR_TS represents a parenthetical set of time expressions. This type is used when the frequency varies over time (e.g., for some cases of tapered dosing, or to handle split dosing). The <comp> elements of this <effectiveTime> element are themselves time expressions (using any of the types listed above). Each <comp> element may specify an operator (e.g. to intersect or form the union of two sets).)
hl7:effectiveTime[@xsi:type='EIVL_TS'] - 0 … 1 C (An xsi:type of EIVL_TS represents an event based time interval, where the event is not a precise time, but is often used for timing purposes (e.g. with meals, between meals, before breakfast, before sleep). Refer to the eHDSITimingEvent value set for the codes to use for the <event> element. This interval may specify an <offset> which provides information about the time offset from the specified event (e.g., <offset><low value='-1' unit='h'/><width value='10' unit='min'/></offset> means 1 hour before the event. In that same example, the <width> element indicates the duration for the dose to be given.)
hl7:effectiveTime[(@value or @nullFlavor) and not(@xsi:type='IVL_TS' or @xsi:type='PIVL_TS' or @xsi:type='EIVL_TS' or @xsi:type='SXPR_TS')] - 0 … 1 C (This required element describes the frequency of intakes. If not known it shall be valued with the nullflavor "UNK".An xsi:type of TS represents a single point in time, and is the simplest of all to represent. The value attribute of the <effectiveTime> element specifies the point in time in HL7 date-time format (CCYYMMDDHHMMSS))
hl7:effectiveTime[@xsi:type='PIVL_TS'] - 0 … 1 C (An xsi:type of PIVL_TS is the most commonly used, representing a periodic interval of time. The <low> element of <phase> may be present. If so it specifies the starting point, and only the lower order components of this value are relevant with respect to the <period>. The <width> element represents the duration of the dose administration (e.g., for IV administration). The <period> indicates how often the dose is given. Legal values for the unit attribute of <period> are s, min, h, d, wk and mo representing seconds, minutes, hours, days, weeks, and months respectively.)
hl7:effectiveTime[@xsi:type='SXPR_TS'] - 0 … 1 C (An xsi:type of SXPR_TS represents a parenthetical set of time expressions. This type is used when the frequency varies over time (e.g., for some cases of tapered dosing, or to handle split dosing). The <comp> elements of this <effectiveTime> element are themselves time expressions (using any of the types listed above). Each <comp> element may specify an operator (e.g. to intersect or form the union of two sets).)
|
|
Item | Prescription | ||||||||
Duration of treatment | epsos-dataelement-109 | - | 1 | 1 … 1 R Quantity | Quantity | during 14 days |
|
hl7:effectiveTime[1] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[1] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R (The first <effectiveTime> element encodes the start and stop time of the medication regimen or the length of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop/length and frequency information between EMR systems. If no information is available for the dosage period, a nullFlavor attribute has to be provided with the value 'UNK'.Case 1: specified intervalThe <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the <high> value represents the stop time.In case of unbounded period (continuous therapy) the <high> element will be valued with the nullFlavor attribute to NA.The <high> value records the end of the medication regime. For example.Case 2: 'floating' periodIf the start and/or stop time is unknown, but the length of the medication regimen is known, it shall be indicated in the <width> value.)
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R (The first <effectiveTime> element encodes the start and stop time of the medication regimen or the length of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop/length and frequency information between EMR systems. If no information is available for the dosage period, a nullFlavor attribute has to be provided with the value 'UNK'.Case 1: specified intervalThe <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the <high> value represents the stop time.In case of unbounded period (continuous therapy) the <high> element will be valued with the nullFlavor attribute to NA.The <high> value records the end of the medication regime. For example.Case 2: 'floating' periodIf the start and/or stop time is unknown, but the length of the medication regimen is known, it shall be indicated in the <width> value.)
|
|
Item | Prescription | |||||||||
Date of onset of treatment | epsos-dataelement-110 | - | 1 | 1 … 1 R Date/time | Date/time | Date when patient needs to start taking the medicine prescribed |
|
hl7:effectiveTime[1] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[1] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R ( The first <effectiveTime> element encodes the start and stop time of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop and frequency information between EMR systems. The <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the
<high> value represents the stop time. If either the <low> or the <high> value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK. The <high> value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the <low> value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely. )
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R (The first <effectiveTime> element encodes the start and stop time of the medication regimen or the length of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop/length and frequency information between EMR systems. If no information is available for the dosage period, a nullFlavor attribute has to be provided with the value 'UNK'.Case 1: specified intervalThe <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the <high> value represents the stop time.In case of unbounded period (continuous therapy) the <high> element will be valued with the nullFlavor attribute to NA.The <high> value records the end of the medication regime. For example.Case 2: 'floating' periodIf the start and/or stop time is unknown, but the length of the medication regimen is known, it shall be indicated in the <width> value.)
hl7:effectiveTime[@xsi:type='IVL_TS'] - 1 … 1 R (The first <effectiveTime> element encodes the start and stop time of the medication regimen or the length of the medication regimen. This an interval of time (xsi:type='IVL_TS'), and must be specified as shown. This is an additional constraint placed upon CDA Release 2.0 by this profile, and simplifies the exchange of start/stop/length and frequency information between EMR systems. If no information is available for the dosage period, a nullFlavor attribute has to be provided with the value 'UNK'.Case 1: specified intervalThe <low> and <high> values of the first <effectiveTime> element represent the start and stop times for the medication. The <low> value represents the start time, and the <high> value represents the stop time.In case of unbounded period (continuous therapy) the <high> element will be valued with the nullFlavor attribute to NA.The <high> value records the end of the medication regime. For example.Case 2: 'floating' periodIf the start and/or stop time is unknown, but the length of the medication regimen is known, it shall be indicated in the <width> value.)
|
|
Item | Prescription | |||||||||
Route of administration | epsos-dataelement-140 | - | 1 | 0 … 1 R Code | Code |
|
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) |
|
hl7:routeCode - 0 … 1 R ( The <routeCode> element specifies the route of administration using the EDQM route of administration vocabulary. A code must be specified if the route is known, and the displayName attribute should be specified. If the route is unknown, this element shall not be sent. )
hl7:routeCode - 0 … 1 R ( The element specifies the route of administration using the EDQM route of administration vocabulary. A code must be specified if the route is known, and the displayName attribute should be specified. If the route is unknown, this element shall not be sent. )
hl7:routeCode - 0 … 1 R ( The element specifies the route of administration using the EDQM route of administration vocabulary. A code must be specified if the route is known, and the displayName attribute should be specified. If the route is unknown, this element shall not be sent. )
hl7:routeCode - 0 … 1 R ( The element specifies the route of administration using the EDQM route of administration vocabulary. A code must be specified if the route is known, and the displayName attribute should be specified. If the route is unknown, this element shall not be sent. )
hl7:routeCode - 0 … 1 R ( The element specifies the route of administration using the EDQM route of administration vocabulary. A code must be specified if the route is known, and the displayName attribute should be specified. If the route is unknown, this element shall not be sent. )
hl7:routeCode - 0 … 1 R ( The element specifies the route of administration using the EDQM route of administration vocabulary. A code must be specified if the route is known, and the displayName attribute should be specified. If the route is unknown, this element shall not be sent. )
|
|
eHDSIRouteofAdministration 2021-04-16T17:00:00 (dynamic)
|
Item | Prescription | |||||||
Instructions to patient | epsos-dataelement-141 | - | 1 | 0 … 1 R String | String | The prescriber might give to the patient instructions; They must be presented in the original language. |
|
hl7:text - 0 … 1 R
hl7:text - 0 … 1 R
|
|
Item | Prescription | |||||||||
Advice to dispenser | epsos-dataelement-142 | - | 1 | 0 … 1 String | String | 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. |
|
hl7:text - 0 … 1 R (The element contains a free text representation of the instruction. For CDA this SHALL 1520 contain a element to the link text of the comment in the narrative portion of the document. The comment itself is not the act being coded, so it appears in the of the , not as part of the .)
|
|
Item | Prescription | |||||||||
Prescriber | epsos-dataelement-236 | - | 1 | 0 … 1 |
|
|
Group | Prescription | ||||||||||||
Prescriber Profession | epsos-dataelement-237 | - | 1 | 0 … 1 Code | Code |
|
|
|
eHDSIHealthcareProfessionalRole 2020-04-22T15:51:00 (dynamic)
|
Item | Prescriber | |||||||||
Prescriber Speciality | epsos-dataelement-238 | - | n | 0 … * Code | Code | 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. |
|
|
Item | Prescriber | ||||||||||
Timestamp of Prescribing | epsos-dataelement-239 | - | 1 | 0 … 1 Date/time | Date/time |
|
Date/time the medication was prescribed |
|
|
Item | Prescriber | |||||||||
Prescriber Identification | epsos-dataelement-240 | - | 1 | 0 … 1 Identifier | Identifier | Unique identification of the prescriber |
|
|
Item | Prescriber | ||||||||||
Prescriber Full Name | epsos-dataelement-241 | - | 1 | 0 … 1 | The full name of the Health Professional |
|
|
Group | Prescriber | |||||||||||
Given Name | epsos-dataelement-242 | - | 1 | 0 … 1 String | String | John | The Name of the Prescriber (Example: John). This field can contain more than one element |
|
|
Item | Prescriber Full Name | |||||||||
Family Name/Surname | epsos-dataelement-243 | - | 1 | 0 … 1 String | String | Español Smith | This field can contain more than one element. |
|
|
Item | Prescriber Full Name | |||||||||
Prefix | epsos-dataelement-269 | - | 1 | 0 … 1 String | String |
|
|
Item | Prescriber Full Name | |||||||||||
Suffix | epsos-dataelement-270 | - | 1 | 0 … 1 String | String |
|
|
Item | Prescriber Full Name | |||||||||||
Prescriber Telecom | epsos-dataelement-282 | - | n | 0 … * |
|
|
Group | Prescriber | ||||||||||||
Telephone No | epsos-dataelement-280 | - | 1 | 0 … 1 String | String |
|
|
Item | Prescriber Telecom | |||||||||||
epsos-dataelement-281 | - | 1 | 0 … 1 String | String |
|
|
Item | Prescriber Telecom | ||||||||||||
Prescriber Healthcare Facility | epsos-dataelement-244 | - | 1 | 0 … 1 | Information about the healthcare facility where the health professional works |
|
|
Group | Prescriber | |||||||||||
Identifier | epsos-dataelement-245 | - | 1 | 0 … 1 Identifier | Identifier | Unique identification of the healthcare facility |
|
|
Item | Prescriber Healthcare Facility | ||||||||||
Name | epsos-dataelement-246 | - | 1 | 0 … 1 String | String | St. Johns Hospital | Name of the healthcare facility |
|
|
Item | Prescriber Healthcare Facility | |||||||||
Healthcare Facility Telecom | epsos-dataelement-283 | - | n | 0 … * |
|
|
Group | Prescriber Healthcare Facility | ||||||||||||
Telephone No | epsos-dataelement-278 | - | 1 | 0 … 1 String | String |
|
|
Item | Healthcare Facility Telecom | |||||||||||
epsos-dataelement-279 | - | 1 | 0 … 1 String | String |
|
|
Item | Healthcare Facility Telecom | ||||||||||||
Prescriber Credentialing Organization | epsos-dataelement-290 | - | 1 | 0 … 1 | The organization which provided the credentialing for the prescriber |
|
|
Group | Prescriber | |||||||||||
Identifier | epsos-dataelement-291 | - | 1 | 0 … 1 Identifier | Identifier | Unique identification of the organization which provided the credentialing for the prescriber |
|
|
Item | Prescriber Credentialing Organization | ||||||||||
Name | epsos-dataelement-292 | - | 1 | 0 … 1 String | String | The name of the organization which provided the credentialing for the prescriber |
|
|
Item | Prescriber Credentialing Organization | ||||||||||
Document Data | epsos-dataelement-62 | + | 1 | 1 … 1 M | Information about the document itself |
|
|
Group | ||||||||||||
Identification | epsos-dataelement-176 | + | 1 | 1 … 1 M Identifier | Identifier | Identification of the document |
|
hl7:id - 0 … * R (The ClinicalDocument/id element is an instance identifier data type. The root attribute is an OID. If there is a value in @extension, then the root uniquely identifies the scope of the extension. If there is no value in @extension then @root SHALL uniquely identify the documentUUIDs SHALL be represented in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where each X is a character from the set [A-Fa-f0-9].OIDs SHALL be represented in dotted decimal notation, where each decimal number is either 0, or starts with a nonzero digit. More formally, an OID SHALL be in the form ([0-2])(.([1-9][0-9]*|0))+.)
hl7:id - 1 … 1 R (The ClinicalDocument/id element is an instance identifier data type. The root attribute is an OID. If there is a value in @extension, then the root uniquely identifies the scope of the extension. If there is no value in @extension then @root SHALL uniquely identify the documentUUIDs SHALL be represented in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where each X is a character from the set [A-Fa-f0-9].OIDs SHALL be represented in dotted decimal notation, where each decimal number is either 0, or starts with a nonzero digit. More formally, an OID SHALL be in the form ([0-2])(.([1-9][0-9]*|0))+.)
hl7:id - 1 … 1 R (The ClinicalDocument/id element is an instance identifier data type. The root attribute is an OID. If there is a value in @extension, then the root uniquely identifies the scope of the extension. If there is no value in @extension then @root SHALL uniquely identify the documentUUIDs SHALL be represented in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where each X is a character from the set [A-Fa-f0-9].OIDs SHALL be represented in dotted decimal notation, where each decimal number is either 0, or starts with a nonzero digit. More formally, an OID SHALL be in the form ([0-2])(.([1-9][0-9]*|0))+.)
|
|
Item | Document Data | |||||||||
Type | epsos-dataelement-296 | + | 1 | 1 … 1 M Code | Code |
|
|
Type of the document |
|
hl7:code - 1 … 1 M (Determines the document type "epSOS Patient Summary Document")
hl7:code - 1 … 1 M (Determines the document type "epSOS Patient Summary Document")
hl7:code - 1 … 1 M (Determines the document type "epSOS Patient Summary Document")
|
|
eHDSIDocumentCode 2020-04-22T12:30:00 (dynamic)
|
Item | Document Data | ||||||
Confidentiality | epsos-dataelement-297 | - | 1 | 0 … 1 R Code | Code |
|
|
Confidentiality of the document as a whole |
|
hl7:confidentialityCode - 1 … 1 R (ClinicalDocument/confidentialityCode shall be present in accordance with the HL7 CDA R2 standard.)
hl7:confidentialityCode - 1 … 1 R (ClinicalDocument/confidentialityCode shall be present in accordance with the HL7 CDA R2 standard.)
hl7:confidentialityCode - 1 … 1 R (ClinicalDocument/confidentialityCode shall be present in accordance with the HL7 CDA R2 standard.)
|
|
eHDSIConfidentiality 2020-04-22T10:00:00 (dynamic)
|
Item | Document Data | ||||||
Language | epsos-dataelement-298 | + | 1 | 1 … 1 M Code | Code | en-GB; nl-NL; nl-BE; de-DE; de-AT | The principal language of the document | 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 |
|
hl7:languageCode - 1 … 1 M (Document Language Code 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)
hl7:languageCode - 1 … 1 M (Document Language Code 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)
hl7:languageCode - 1 … 1 M (Document Language CodeThe language code SHALL be in the form nn-CC.The nn portion SHALL be an ISO-639-1 language code in lower case.The CC portion SHALL be an ISO-3166 country code in upper case.)
|
|
Item | Document Data | |||||||
Country A | epsos-dataelement-63 | + | 1 | 1 … 1 M Code | Code | United Kindom |
|
Name of country A |
|
|
eHDSICountry 2020-04-22T12:30:00 (dynamic)
|
Item | Document Data | |||||||
Topicality | epsos-dataelement-64 | + | 1 | 1 … 1 M |
|
|
Group | Document Data | ||||||||||||
Date Created | epsos-dataelement-65 | + | 1 | 1 … 1 M Date/time | Date/time |
|
01/01/2009 | Date on which the document was generated |
|
hl7:effectiveTime - 1 … 1 M (Relevant times for the Patient SummaryBy definition, a Patient Summary document describes the Patient Summary at the time of creation of the document, represented by the /ClinicalDocument/effectiveTime XML Element.The time when this instance of the document has been authored may be instead recorded by the /ClinicalDocument/author/time element. (e.g. when a “spider” has collected information for generating this instance of the document; or a practitioner updated its local summary document).Finally, the latest summary update, intended as the last date documented by this summary (e.g. the last update occurred to the PHR from which the PS data has been extracted) can be represented by the /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high XML Element (see section 2.1, CONF-2, CONF-3 and CONF-4 of the CCD specification).)
hl7:effectiveTime - 1 … 1 M (Relevant times for the Patient SummaryBy definition, a Patient Summary document describes the Patient Summary at the time of creation of the document, represented by the /ClinicalDocument/effectiveTime XML Element.The time when this instance of the document has been authored may be instead recorded by the /ClinicalDocument/author/time element. (e.g. when a “spider” has collected information for generating this instance of the document; or a practitioner updated its local summary document).Finally, the latest summary update, intended as the last date documented by this summary (e.g. the last update occurred to the PHR from which the PS data has been extracted) can be represented by the /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high XML Element (see section 2.1, CONF-2, CONF-3 and CONF-4 of the CCD specification).)
hl7:effectiveTime - 1 … 1 M (Relevant times for the Patient SummaryBy definition, a Patient Summary document describes the Patient Summary at the time of creation of the document, represented by the /ClinicalDocument/effectiveTime XML Element.The time when this instance of the document has been authored may be instead recorded by the /ClinicalDocument/author/time element. (e.g. when a “spider” has collected information for generating this instance of the document; or a practitioner updated its local summary document).Finally, the latest summary update, intended as the last date documented by this summary (e.g. the last update occurred to the PHR from which the PS data has been extracted) can be represented by the /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high XML Element (see section 2.1, CONF-2, CONF-3 and CONF-4 of the CCD specification).)
|
|
Item | Topicality | |||||||
Author | epsos-dataelement-67 | - | 1 | 0 … 1 | 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. |
|
hl7:author - 1 … * R
hl7:author - 1 … * R
hl7:author - 1 … * R
|
|
Group | Document Data | ||||||||||
Author Identification | epsos-dataelement-22 | + | 1 | 1 … 1 M Identifier | Identifier | Unique identification of the Health Professional. |
|
hl7:id - 1 … * R (HP ID number)
hl7:id - 1 … * R (Identification of the Healthcare Practitioner that is the author of this document.)
hl7:id - 1 … * R (Identification of the Healthcare Practitioner that is the author of this document.)
|
|
Item | Author | |||||||||
Author Full Name | epsos-dataelement-19 | + | 1 | 1 … 1 M | The full name of the Health Professional |
|
hl7:name - 1 … 1 R (HP Name)
hl7:name - 1 … 1 R (HP Name)
hl7:name - 1 … 1 R (HP Name)
|
|
Group | Author | ||||||||||
Given Name | epsos-dataelement-20 | + | 1 | 1 … 1 M String | String | John | The Name of the HP (Example: John). This field can contain more than one element |
|
hl7:given - 1 … * M (HP Given Name)
hl7:given - 1 … * M (HP Given Name)
hl7:given - 1 … * M (HP Given Name)
|
|
Item | Author Full Name | ||||||||
Family Name/Surname | epsos-dataelement-21 | + | 1 | 1 … 1 M String | String | Español Smith | This field can contain more than one element. |
|
hl7:family - 1 … * M (HP Family Name/Surname)
hl7:family - 1 … * M (HP Family Name/Surname)
hl7:family - 1 … * M (HP Family Name/Surname)
|
|
Item | Author Full Name | ||||||||
Prefix | epsos-dataelement-273 | - | 1 | 0 … 1 String | String |
|
hl7:prefix - 0 … * R (HP Prefix)
hl7:prefix - 0 … * R (HP Prefix)
hl7:prefix - 0 … * R (HP Prefix)
|
|
Item | Author Full Name | ||||||||||
Suffix | epsos-dataelement-274 | - | 1 | 0 … 1 String | String |
|
hl7:suffix - 0 … * R (HP Suffix)
hl7:suffix - 0 … * R (HP Suffix)
hl7:suffix - 0 … * R (HP Suffix)
|
|
Item | Author Full Name | ||||||||||
Author Healthcare Facility | epsos-dataelement-23 | - | 1 | 0 … 1 | Information about the healthcare facility where the health professional works |
|
hl7:representedOrganization - 1 … 1 R
hl7:representedOrganization - 1 … 1 R
hl7:representedOrganization - 1 … 1 R
classCode - 0 … 1
classCode - 0 … 1
classCode - 0 … 1
classCode - 0 … 1
|
|
Group | Author | ||||||||||
Identifier | epsos-dataelement-25 | + | 1 | 1 … 1 M Identifier | Identifier | Unique identification of the healthcare facility |
|
hl7:id - 1 … 1 R (Healthcare Facility's Id)
hl7:id - 1 … 1 R (Healthcare Facility's Id)
hl7:id - 1 … 1 R (Healthcare Facility's Id)
hl7:id - 1 … 1 R (Healthcare Facility's Id)
|
|
Item | Author Healthcare Facility | |||||||||
Name | epsos-dataelement-24 | + | 1 | 1 … 1 M String | String | St. Johns Hospital | Name of the healthcare facility |
|
hl7:name - 1 … 1 R (Healthcare Facility's Name)
hl7:name - 1 … 1 R (Healthcare Facility's Name)
hl7:name - 1 … 1 R (Healthcare Facility's Name)
hl7:name - 1 … 1 R (Healthcare Facility's Name)
|
|
Item | Author Healthcare Facility |