| Name |
Details [‑] |
|
  Patient Attributes 1 … 1 Required
hl7ips-dataelement-2.1
|
|
|
| Id |
hl7ips-dataelement-2.1 (2017‑12‑05 15:26:38)
|
| Cardinality |
1 … 1 Required
|
| Description |
Collection
of data used for identification and assurance of identity within a patient
summary.
Every PS
conformant to IPS must contain ’Patient’s Name’ from this IPS collection.
Insurance information is necessary in some
countries
|
| Inclusion Criteria |
While
this data may also fulfil an administrative role in planned care or in the
follow up after unplanned care, the defined use case of unscheduled care for
the IPS suggests that the immediate use of this data will be used for
identification purposes. In the eHN
guide-line these data elements span three categories, i.e., ‘Identification’,
‘Personal Information’ and ‘Insurance Information’
|
|
| Rationale |
An IPS
Attribute Collection will provide various data used individually or
collectively to identify, or to assure the identity of a person and/or patient
to an attending clinician at the point of care.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
 Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:patientRole 1 … 1 Mandatory
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:patientRole 1 … 1 Mandatory
|
|
|
| Patient's Name 1 … * Required
hl7ips-dataelement-3
|
|
|
| Id |
hl7ips-dataelement-3 (2017‑12‑05 17:36:20)
|
| Cardinality |
1 … * Required
|
| Description |
The name of a person is a familiar, cross-sector idea, independent of a particular
use case. It is explained in the Primitive Values clause.
|
|
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Operationalization |
It requires family and given name components.
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:name 1 … * Mandatory
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:name 1 … * Mandatory
|
|
|
| Patient’s address and telecom 0 … * Required
hl7ips-dataelement-155
|
|
|
| Id |
hl7ips-dataelement-155 (2017‑12‑24 16:23:21)
|
| Cardinality |
0 … * Required
|
| Description |
This Label Concept positions the nested attributes. However, it is useful to note
that the patient’s address is administrative but can also be used in the clinical
process to assist with the verification of the patient’s identification.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
|
|
|
| Address 0 … * Required
hl7ips-dataelement-162
|
|
|
| Id |
hl7ips-dataelement-162 (2017‑12‑24 16:28:32)
|
| Cardinality |
0 … * Required
|
|
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:addr 1 … * Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:addr 1 … * Required
|
|
|
| Telecoms 0 … * Required
hl7ips-dataelement-100
|
|
|
| Id |
hl7ips-dataelement-100 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … * Required
|
|
|
| Value Domain |
Count |
| Used by
|
one transaction, one template, inherited once |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:telecom 1 … * Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:telecom 1 … * Required
This concept is inherited by concept
Telecoms in dataset hl7ips-dataelement-178
|
|
|
| Administrative Gender 0 … 1 Required
hl7ips-dataelement-4
|
|
|
| Id |
hl7ips-dataelement-4 (2017‑12‑05 17:37:51)
|
| Cardinality |
0 … 1 Required
|
| Description |
Some countries require ‘gender’ as part of their identification of the patient. Administrative
gender SHALL be specified from a value set including, ‘Male’, ‘Female’, ‘Unknown’,
‘Neutral’
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:administrativeGenderCode 1 … 1 Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:administrativeGenderCode 1 … 1 Required
|
|
|
| Date of Birth 1 … 1 Required
hl7ips-dataelement-5
|
|
|
| Id |
hl7ips-dataelement-5 (2017‑12‑05 17:38:12)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:birthTime 1 … 1 Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:birthTime 1 … 1 Required
|
|
|
| Patient’s preferred language 0 … 1
hl7ips-dataelement-135
|
|
|
| Id |
hl7ips-dataelement-135 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:languageCode 1 … 1 Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:languageCode 1 … 1 Required
|
|
|
| Healthcare related Identifiers 0 … * Required
hl7ips-dataelement-202
|
|
|
| Id |
hl7ips-dataelement-202 (2017‑12‑30 15:05:17)
|
| Cardinality |
0 … * Required
|
| Description |
A list of patient identifiers.
Notes: Arguably a national health number would be of more use locally than for cross-border
purposes. It is also possible, even probable, that a person will have several numbers,
each one related to one or more healthcare providers. In an international context,
a national healthcare identifier may be useful. However not all countries have such
a registration scheme in place.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:id 1 … * Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:id 1 … * Required
|
|
|
| Patient Identifier 0 … * Required
hl7ips-dataelement-6
|
|
|
| Id |
hl7ips-dataelement-6 (2017‑12‑05 17:39:17)
|
| Cardinality |
0 … * Required
|
| Description |
Note, Patient Number is often used as a synonym, albeit that the identifier is not
necessarily numeric; some jurisdictions use the Social Security Number as a healthcare
identifier.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Identifier |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
|
|
|
| Insurance Information 0 … *
hl7ips-dataelement-203
|
|
|
| Id |
hl7ips-dataelement-203 (2017‑12‑30 15:06:49)
|
| Cardinality |
0 … *
|
| Description |
Insurance information is not always required in a patient summary. However, in some
jurisdictions, the insurance number is also used as the patient identifier. It is
necessary not just for identification but also forms access to funding for care. In
those countries that require such information, it must be present.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … *) in scenario IPS Originated
|
|
|
| Insurance identifier 0 … * Required
hl7ips-dataelement-7
|
|
|
| Id |
hl7ips-dataelement-7 (2017‑12‑05 17:40:40)
|
| Cardinality |
0 … * Required
|
| Value Domain |
Identifier |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:id 1 … * Required
This concept is represented by template IPS CDA recordTarget (versie 2017‑04‑11) hl7:id 1 … * Required
|
|
|
| Patient’s Address Book 0 … 1 Required
hl7ips-dataelement-154
|
|
|
| Id |
hl7ips-dataelement-154 (2017‑12‑24 16:22:01)
|
| Cardinality |
0 … 1 Required
|
| Description |
People and organizations address details relevant for the planned and unplanned care.
Considered to be generic to the English language and not specific to this standard.
Notes: A list relating to people or organisations details who might need to be contacted
for this care event; it is not to do with previous care events involving this patient.
These entities can be considered as providers (person or organisation) who are wholly
or partially responsible for the safety and well-being of the subject of care.
|
| Rationale |
This IPS Attribute Collection provides an Address Book resource detailing the address
details of the patient, and people and organisations relevant to the patient with
respect to the IPS.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:participant[hl7:templateId/@root='2.16.840.1.113883.10.22.2.5']
0 … * Required
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:participant[hl7:templateId/@root='2.16.840.1.113883.10.22.2.5']
0 … * Required
|
|
|
| Preferred Healthcare providers 0 … 1 Required
hl7ips-dataelement-163
|
|
|
| Id |
hl7ips-dataelement-163 (2017‑12‑24 16:29:15)
|
| Cardinality |
0 … 1 Required
|
| Description |
If known, this information shall be provided. Note it is not necessarily the case
that Preferred Healthcare Provider is the same party as the source of the patient
summary; the latter is given by the Provenance meta data. ‘Preferred’ indicates the
most relevant entity to be contacted for use in this patient summary.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:participant[hl7:templateId/@root='2.16.840.1.113883.10.22.2.5']
0 … * Required
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:participant[hl7:templateId/@root='2.16.840.1.113883.10.22.2.5']
0 … * Required
|
|
|
| Healthcare Provider (person) Conditional
hl7ips-dataelement-165
|
|
|
| Id |
hl7ips-dataelement-165 (2017‑12‑24 16:30:40)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … * |
exist(Healthcare Provider (organisation)) |
| 1 … * Required |
otherwise |
|
|
| Synonyms |
HP
HCP
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Conditional) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:associatedPerson 0 … Conditional
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:associatedPerson 0 … Conditional
|
|
|
| Name 1 … * Required
hl7ips-dataelement-121
|
|
|
| Id |
hl7ips-dataelement-121 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … * Required
|
|
|
| Operationalization |
It requires family and given name components.
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 2 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:name 1 … * Required
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:name 1 … * Required
This concept is inherited by concept
Name in dataset hl7ips-dataelement-157
This concept is inherited by concept
Name in dataset hl7ips-dataelement-118
|
|
|
| Telecoms 0 … * Required
hl7ips-dataelement-169
|
|
|
| Id |
hl7ips-dataelement-169 (2017‑12‑25 09:40:30)
|
| Cardinality |
0 … * Required
|
|
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 2 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:telecom 1 … * Required
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:telecom 1 … * Required
This concept is inherited by concept
Telecoms in dataset hl7ips-dataelement-174
This concept is inherited by concept
Telecoms in dataset hl7ips-dataelement-122
|
|
|
| Healthcare Provider (organisation) Conditional
hl7ips-dataelement-166
|
|
|
| Id |
hl7ips-dataelement-166 (2017‑12‑24 16:31:09)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … * |
exist(Healthcare Provider (person)) |
| 1 … * Required |
otherwise |
|
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Conditional) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:scopingOrganization 0 … Conditional
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:scopingOrganization 0 … Conditional
|
|
|
| Organisation’s Name 1 … * Required
hl7ips-dataelement-172
|
|
|
| Id |
hl7ips-dataelement-172 (2017‑12‑25 09:42:30)
|
| Cardinality |
1 … * Required
|
| Value Domain |
String |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:name 1 … * Required
This concept is represented by template IPS Patient Contacts (versie 2017‑04‑12) hl7:name 1 … * Required
|
|
|
| Telecoms 0 … * Required
hl7ips-dataelement-174
|
|
|
|
|
| Other's Contacts’ Details 0 … 1
hl7ips-dataelement-164
|
|
|
| Id |
hl7ips-dataelement-164 (2017‑12‑24 16:29:36)
|
| Cardinality |
0 … 1
|
| Description |
The urgency of the scenario suggests that the contact details will be minimised to
the most likely means of getting in touch. The role distinguishes between individuals
(and organisations) by means of their function with respect to the patient’s care
to enable the relevant person to be contacted by the healthcare provider at the point
of care. The role can be both functional (e.g. doctor) and a specialisation (e.g.
specialist).
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Contact 1 … * Required
hl7ips-dataelement-167
|
|
|
| Id |
hl7ips-dataelement-167 (2017‑12‑24 16:32:11)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Role 0 … 1 Required
hl7ips-dataelement-175
|
|
|
| Id |
hl7ips-dataelement-175 (2017‑12‑25 09:45:41)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Name 1 … * Required
hl7ips-dataelement-157
|
|
|
| Id |
hl7ips-dataelement-157 (2017‑12‑24 16:25:00)
|
| Cardinality |
1 … * Required
|
| Concept inherits from |
hl7ips-dataelement-121 (2017‑12‑19 12:39:26)
|
|
|
| Operationalization |
It requires family and given name components.
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Address 0 … *
hl7ips-dataelement-120
|
|
|
| Id |
hl7ips-dataelement-120 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … *
|
|
|
| Operationalization |
Address |
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … *) in scenario IPS Originated
|
|
|
| Telecoms 0 … * Required
hl7ips-dataelement-122
|
|
|
|
|
| Advance Directives 0 … 1
hl7ips-dataelement-8
|
|
|
| Id |
hl7ips-dataelement-8 (2017‑12‑05 17:41:55)
|
| Cardinality |
0 … 1
|
| Synonyms |
AD Section
Living will
Personal directive
|
| Description |
Provision for healthcare decisions in the event that, in the future, a person is unable
to make those decisions.
A conformant IPS document may not include this section.
Healthcare directives concerning life or after life wishes of the patient
|
| Rationale |
Deemed to be of value in unplanned care if a life-threatening event or fatality occurs
and the patient or a legitimate decision maker has stipulated what should happen with
respect to the patient who is too ill or hurt to express their wishes.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Advance Directives 1 … 1 Required
hl7ips-dataelement-24
|
|
|
| Id |
hl7ips-dataelement-24 (2017‑12‑05 17:57:26)
|
| Cardinality |
1 … 1 Required
|
| Synonym |
AD List
|
| Description |
A list comprising one or more advance directives
Note: Although not in this version of the standard, future versions of the Advanced
Directives IPS Section might also include definitions and descriptions regarding ‘CONSENT
practices’ as directives and mandates from particular jurisdictions
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, 0 templates, inherited once |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Advance Directive 1 … * Required
hl7ips-dataelement-179
|
|
|
| Id |
hl7ips-dataelement-179 (2017‑12‑25 12:42:26)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Person authorising Directive 0 … 1 Required
hl7ips-dataelement-22
|
|
|
| Id |
hl7ips-dataelement-22 (2017‑12‑05 17:53:40)
|
| Cardinality |
0 … 1 Required
|
| Description |
The source of each directive if known; the decision maker is usually the patient and/or
a delegated person such as a Legal Guardian. If the authority is not the patient,
then it will be someone to contact for further information and clarification of the
patient’s wishes. The postal address elements are not included reflecting the urgency
for the contact; however, full details should be consistent and available from the
Patient’s Address Book.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Name 0 … * Required
hl7ips-dataelement-118
|
|
|
| Id |
hl7ips-dataelement-118 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … * Required
|
| Concept inherits from |
hl7ips-dataelement-121 (2017‑12‑19 12:39:26)
|
|
|
| Operationalization |
It requires family and given name components.
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
|
|
|
| Telecoms 0 … * Required
hl7ips-dataelement-178
|
|
|
| Id |
hl7ips-dataelement-178 (2017‑12‑25 09:52:33)
|
| Cardinality |
0 … * Required
|
| Concept inherits from |
hl7ips-dataelement-100 (2017‑12‑19 12:39:26)
|
|
|
| Value Domain |
Count |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
|
|
|
| Directive category 0 … *
hl7ips-dataelement-180
|
|
|
| Id |
hl7ips-dataelement-180 (2017‑12‑25 18:48:23)
|
| Cardinality |
0 … *
|
| Description |
There are Directives related to decisions prior and after death. For example, directives
prior to death might relate to Blood transfusions, and Non-Resuscitation and post
death directives might relate to organ donation.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … *) in scenario IPS Originated
|
|
|
| Description Conditional
hl7ips-dataelement-26
|
|
|
| Id |
hl7ips-dataelement-26 (2017‑12‑05 17:58:46)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … * |
exist(../Reference to Legal Document) |
| 1 … * Required |
otherwise |
|
|
| Description |
Textual description of the directive.
Derived models may choose to use distinct elements for each narrative directive or
to collect them into a single section level narrative block.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Conditional) in scenario IPS Originated
|
|
|
| Reference to Legal Document Conditional
hl7ips-dataelement-27
|
|
|
| Id |
hl7ips-dataelement-27 (2017‑12‑05 18:00:07)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … * |
exists(../Description) |
| 1 … * Required |
otherwise |
|
|
| Description |
The Directives may take the form of a reference to a legal document (e.g. Living Will)
or an external textual description.
|
|
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Conditional) in scenario IPS Originated
|
|
|
| Allergies and Intolerances 1 … 1 Required
hl7ips-dataelement-9
|
|
|
| Id |
hl7ips-dataelement-9 (2017‑12‑05 17:42:46)
|
| Cardinality |
1 … 1 Required
|
| Description |
Relevant patient’s allergies and/or intolerance conditions.
NOTE 1 to entry: At a minimum, it should list currently active and any relevant historical
allergies and adverse reactions.
NOTE 2 to entry: ‘Alerts’ was used to describe this Section in the eHN guidance -lines,
but ‘Alerts’ are far more general and are not regarded here as a synonym.
Every PS conformant to IPS must contain this IPS section.
Allergies and Intolerances affecting the Patient.
|
| Rationale |
To inform the treatment and care provisioning of an attending clinician to identify
problem or to avoid adverse events arising from action taken. At a minimum, it should
list currently active and any relevant historical allergies and adverse reactions.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Allergies/Intolerances Content Status Conditional
hl7ips-dataelement-182
|
|
|
| Id |
hl7ips-dataelement-182 (2017‑12‑25 18:54:28)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../Allergy or Intolerance list) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
As this IPS Section is mandatory for conformance, information about “known absence
of allergies” or no information about allergies is required to be stated. Known Content
will be accompanied by the conditional list of Allergies and intolerances.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Allergy or Intolerance list Conditional
hl7ips-dataelement-28
|
|
|
| Id |
hl7ips-dataelement-28 (2017‑12‑05 18:11:15)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../Allergies/Intolerances Content Status) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
If allergies present then they shall be listed else give explicit reasons for why
none are recorded. An ordered list comprising the name, code, a description of the
Allergy/intolerance and Agent details for each Allergy/intolerance.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Allergy/Intolerance 1 … * Mandatory
hl7ips-dataelement-184
|
|
|
| Id |
hl7ips-dataelement-184 (2017‑12‑25 20:48:04)
|
| Cardinality |
1 … * Mandatory
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Mandatory) in scenario IPS Originated
|
|
|
| Description 1 … 1 Required
hl7ips-dataelement-183
|
|
|
| Id |
hl7ips-dataelement-183 (2017‑12‑25 20:47:32)
|
| Cardinality |
1 … 1 Required
|
| Description |
Textual description of the allergy or intolerance.
Derived models may choose to use distinct elements for each narrative statement or
to collect them into a single section level narrative block.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Clinical Status 1 … 1 Required
hl7ips-dataelement-186
|
|
|
| Id |
hl7ips-dataelement-186 (2017‑12‑25 20:48:51)
|
| Cardinality |
1 … 1 Required
|
| Description |
Provides the current status of the allergy or intolerance, for example, whether it
is active, in remission, resolved, and so on.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Choice list |
| Concept List |
| Concept |
Synonyms |
Description |
Assigned references |
| active |
|
|
|
| inactive |
|
|
|
| resolved |
|
|
|
|
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Onset date 1 … 1 Required
hl7ips-dataelement-187
|
|
|
| Id |
hl7ips-dataelement-187 (2017‑12‑25 20:49:17)
|
| Cardinality |
1 … 1 Required
|
| Description |
It shall be provided with the highest known precision, at least year
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Date/time |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| End Date Conditional
hl7ips-dataelement-188
|
|
|
| Id |
hl7ips-dataelement-188 (2017‑12‑25 20:49:59)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 1 … 1 Required |
if clinical status non-active |
| 0 … 0 Not present |
otherwise |
|
|
| Description |
If Clinical Status is non-active then an exception can be raised to indicate inconsistency.
It shall be provided with the highest known precision, at least year.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Date/time |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Criticality 0 … 1
hl7ips-dataelement-189
|
|
|
| Id |
hl7ips-dataelement-189 (2017‑12‑25 20:51:19)
|
| Cardinality |
0 … 1
|
| Description |
This attribute represents the gravity of the potential risk for future life-threatening
adverse reactions when exposed to a substance known to cause an adverse reaction in
that individual. When the ‘worst case’ result is assessed to have a life-threatening
or organ system threatening potential, it is considered to be of high criticality.
Notes: In some contexts, the severity is used as a synonym of the criticality.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Choice list |
| Concept List |
| Concept |
Synonyms |
Description |
Assigned references |
| High |
|
|
|
| Low |
|
|
|
| unable to assess criticality |
|
(exception) |
|
|
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Certainty 0 … 1
hl7ips-dataelement-190
|
|
|
| Id |
hl7ips-dataelement-190 (2017‑12‑25 20:52:37)
|
| Cardinality |
0 … 1
|
| Description |
Assertion about certainty associated with the propensity, or potential risk, of a
reaction to the identified substance
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Choice list |
| Concept List |
| Concept |
Synonyms |
Description |
Assigned references |
| Provisional |
|
This is a tentative diagnosis - still a candidate that is under consideration
|
|
| Differential |
|
One of a set of potential (and typically mutually exclusive) diagnoses asserted to
further guide the diagnostic process and preliminary treatment
|
|
| Confirmed |
|
A high level of certainty about the propensity for a reaction to the identified substance,
which may include clinical evidence by testing or re-challenge
|
|
| Refuted |
|
A propensity for a reaction to the identified substance has been disproven with a
high level of clinical certainty, which may include testing or re-challenge, and is
refuted
|
|
|
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Type of propensity 0 … 1 Required
hl7ips-dataelement-191
|
|
|
| Id |
hl7ips-dataelement-191 (2017‑12‑25 20:53:34)
|
| Cardinality |
0 … 1 Required
|
| Description |
Type of allergy or intolerance. |
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Choice list |
| Concept List |
| Concept |
Synonyms |
Description |
Assigned references |
| Allergy |
|
|
|
| Intolerance |
|
|
|
| propensity to adverse reaction |
allergy or intolerance
|
|
|
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Diagnosis 0 … 1
hl7ips-dataelement-185
|
|
|
| Id |
hl7ips-dataelement-185 (2017‑12‑25 20:48:27)
|
| Cardinality |
0 … 1
|
| Description |
A code indicating the type of reaction and the agent; an alternative option for describing
an allergy to the agent. Described with Textual information if coded data are unavailable.
Example: lactose intolerance
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Reaction 0 … * Required
hl7ips-dataelement-192
|
|
|
| Id |
hl7ips-dataelement-192 (2017‑12‑25 20:55:23)
|
| Cardinality |
0 … * Required
|
| Description |
A Label Concept recognising that other data concerning the reaction may be made available
in later versions of this standard.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
|
|
|
| Manifestation of the reaction 0 … 1 Required
hl7ips-dataelement-193
|
|
|
| Id |
hl7ips-dataelement-193 (2017‑12‑25 20:55:47)
|
| Cardinality |
0 … 1 Required
|
| Description |
Description of the clinical manifestation of the allergic reaction. Example: anaphylactic
shock, angioedema (the clinical manifestation also gives information about the severity
of the observed reaction).
Textual information if coded/quantified data are not available. This is typically
a more complex structure than simple text.
Example: “intestinal discomfort” is the manifestation of the reaction.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Severity 0 … 1 Required
hl7ips-dataelement-194
|
|
|
| Id |
hl7ips-dataelement-194 (2017‑12‑25 20:56:16)
|
| Cardinality |
0 … 1 Required
|
| Description |
Coded element that described the subjective assessment of the severity of the condition
as evaluated by the clinician, in the case of an allergy it is used as attribute of
a manifestation of a reaction. For example, a person may have a severe rash as reaction,
that it is not however critical.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Agent 1 … 1 Required
hl7ips-dataelement-173
|
|
|
| Id |
hl7ips-dataelement-173 (2017‑12‑25 09:43:42)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Agent code 1 … 1 Required
hl7ips-dataelement-196
|
|
|
| Id |
hl7ips-dataelement-196 (2017‑12‑25 20:56:54)
|
| Cardinality |
1 … 1 Required
|
| Description |
A specific allergen or other agent/substance to which the patient has an adverse reaction
propensity. This will be taken from a list of agents and the associated code from
a value set.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Category 0 … 1
hl7ips-dataelement-195
|
|
|
| Id |
hl7ips-dataelement-195 (2017‑12‑25 20:56:33)
|
| Cardinality |
0 … 1
|
| Description |
Allergy substance category |
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Choice list |
| Concept List |
| Concept |
Synonyms |
Description |
Assigned references |
| Food |
|
|
|
| Medication |
|
|
|
| Environment |
|
|
|
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Functional Status 0 … 1
hl7ips-dataelement-10
|
|
|
| Id |
hl7ips-dataelement-10 (2017‑12‑05 17:43:38)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Disabilities List Conditional
hl7ips-dataelement-156
|
|
|
| Id |
hl7ips-dataelement-156 (2017‑12‑24 16:24:25)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(../Functional Assessments List) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Disability 1 … * Required
hl7ips-dataelement-29
|
|
|
| Id |
hl7ips-dataelement-29 (2017‑12‑05 18:12:06)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Description 1 … 1 Required
hl7ips-dataelement-197
|
|
|
| Id |
hl7ips-dataelement-197 (2017‑12‑25 20:57:48)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Disability Code 0 … 1
hl7ips-dataelement-198
|
|
|
| Id |
hl7ips-dataelement-198 (2017‑12‑25 20:58:16)
|
| Cardinality |
0 … 1
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Onset date 0 … 1
hl7ips-dataelement-199
|
|
|
| Id |
hl7ips-dataelement-199 (2017‑12‑25 20:58:37)
|
| Cardinality |
0 … 1
|
| Value Domain |
Date/time |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Functional Assessments List Conditional
hl7ips-dataelement-30
|
|
|
| Id |
hl7ips-dataelement-30 (2017‑12‑05 18:12:34)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(../Disabilities List) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Functional Assessment 1 … * Required
hl7ips-dataelement-201
|
|
|
| Id |
hl7ips-dataelement-201 (2017‑12‑25 20:59:15)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Description 1 … 1 Required
hl7ips-dataelement-137
|
|
|
| Id |
hl7ips-dataelement-137 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Description |
Textual description of the functional assessment.
Derived models may choose to use distinct elements for each narrative statement or
to collect them into a single section level narrative block
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Date of assessment 0 … 1 Required
hl7ips-dataelement-204
|
|
|
| Id |
hl7ips-dataelement-204 (2017‑12‑30 15:35:22)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Type 0 … 1 Required
hl7ips-dataelement-205
|
|
|
| Id |
hl7ips-dataelement-205 (2017‑12‑30 15:35:55)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Result Conditional
hl7ips-dataelement-206
|
|
|
| Id |
hl7ips-dataelement-206 (2017‑12‑30 15:36:49)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 1 … 1 Required |
otherwise |
| 0 … 0 Not present |
IF exists(../Functional Assessment) |
|
|
|
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Functional Assessment Conditional
hl7ips-dataelement-21
|
|
|
| Id |
hl7ips-dataelement-21 (2017‑12‑05 17:51:41)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
IF exists(../Result) |
| 1 … 1 Required |
otherwise |
|
|
| Concept references |
hl7ips-dataelement-201 (2017‑12‑25 20:59:15)
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| History of Past Illness 0 … 1
hl7ips-dataelement-11
|
|
|
| Id |
hl7ips-dataelement-11 (2017‑12‑05 17:45:27)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Past illness content status Conditional
hl7ips-dataelement-208
|
|
|
| Id |
hl7ips-dataelement-208 (2017‑12‑30 15:38:01)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Past health conditions and problems]) |
| 1 … 1 Required |
otherwise |
|
|
 |
There is an open issue with this item:
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Past health conditions and problems list Conditional
hl7ips-dataelement-31
|
|
|
| Id |
hl7ips-dataelement-31 (2017‑12‑19 11:38:51)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Past illness content status]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Health condition / Problem 1 … * Required
hl7ips-dataelement-209
|
|
|
| Id |
hl7ips-dataelement-209 (2017‑12‑30 15:43:06)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:observation 0 … * Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:observation 0 … * Required
|
|
|
| Problem Type 0 … 1 Required
hl7ips-dataelement-210
|
|
|
| Id |
hl7ips-dataelement-210 (2017‑12‑30 15:43:52)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:code 1 … 1 Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:code 1 … 1 Required
|
|
|
| Description 1 … 1 Required
hl7ips-dataelement-35
|
|
|
| Id |
hl7ips-dataelement-35 (2017‑12‑19 11:42:38)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Diagnosis 1 … 1 Required
hl7ips-dataelement-36
|
|
|
| Id |
hl7ips-dataelement-36 (2017‑12‑19 11:43:56)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:value 1 … 1 Mandatory
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:value 1 … 1 Mandatory
|
|
|
| Severity 0 … 1
hl7ips-dataelement-136
|
|
|
| Id |
hl7ips-dataelement-136 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1
|
| Concept references |
hl7ips-dataelement-194 (2017‑12‑25 20:56:16)
|
| Description |
Coded element that described the subjective assessment of the severity of the condition
as evaluated by the clinician, in the case of an allergy it is used as attribute of
a manifestation of a reaction. For example, a person may have a severe rash as reaction,
that it is not however critical.
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Value Domain |
Code |
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:entryRelationship 0 … 1 Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:entryRelationship 0 … 1 Required
|
|
|
| Onset Date 1 … 1 Required
hl7ips-dataelement-32
|
|
|
| Id |
hl7ips-dataelement-32 (2017‑12‑19 11:39:44)
|
| Cardinality |
1 … 1 Required
|
| Description |
Date of the first observation of adverse reactions
|
| Relationship |
|
| Source |
SPECIFIC GUIDELINES FOR ELECTRONIC EXCHANGE OF HEALTH DATA UNDER THE CROSS-BORDER
DIRECTIVE 2011/24/EU
RELEASE 2 PATIENT SUMMARY FOR UNSCHEDULED CARE
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:low 1 … 1 Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:low 1 … 1 Required
|
|
|
| Resolution 0 … 1
hl7ips-dataelement-33
|
|
|
| Id |
hl7ips-dataelement-33 (2017‑12‑19 11:40:58)
|
| Cardinality |
0 … 1
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Date resolved Conditional
hl7ips-dataelement-34
|
|
|
| Id |
hl7ips-dataelement-34 (2017‑12‑19 11:41:41)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 1 … 1 Required |
IF status non-active |
| 0 … 0 Not present |
otherwise |
|
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:high 0 … Conditional
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:high 0 … Conditional
|
|
|
| Specialist Contact 0 … *
hl7ips-dataelement-124
|
|
|
| Id |
hl7ips-dataelement-124 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … *
|
| Data Type |
Healthcare Provider |
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 3 times |
| |
This concept is used in transaction IPS Created (0 … *) in scenario IPS Originated
|
|
|
| History of Pregnancy 0 … 1
hl7ips-dataelement-12
|
|
|
| Id |
hl7ips-dataelement-12 (2017‑12‑05 17:45:45)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Status of pregnancy 1 … 1 Required
hl7ips-dataelement-37
|
|
|
| Id |
hl7ips-dataelement-37 (2017‑12‑19 11:44:59)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Pregnancy Description Conditional
hl7ips-dataelement-225
|
|
|
| Id |
hl7ips-dataelement-225 (2018‑07‑02 13:40:29)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(../[Structured Description]) |
| 1 … 1 Required |
otherwise |
|
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Structured Description Conditional
hl7ips-dataelement-168
|
|
|
| Id |
hl7ips-dataelement-168 (2017‑12‑25 09:39:11)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(../[Pregnancy Description]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Date of Observation 1 … 1 Required
hl7ips-dataelement-211
|
|
|
| Id |
hl7ips-dataelement-211 (2017‑12‑31 12:55:02)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Pregnancy State 1 … 1 Required
hl7ips-dataelement-212
|
|
|
| Id |
hl7ips-dataelement-212 (2017‑12‑31 12:55:33)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Expected delivery date Conditional
hl7ips-dataelement-213
|
|
|
| Id |
hl7ips-dataelement-213 (2017‑12‑31 12:56:56)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 1 … 1 Required |
IF pregnant |
| 0 … 0 Not present |
otherwise |
|
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Specialist Contact 0 … *
hl7ips-dataelement-200
|
|
|
|
|
| Previous Pregnancies 0 … 1
hl7ips-dataelement-38
|
|
|
| Id |
hl7ips-dataelement-38 (2017‑12‑19 11:46:37)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Previous Pregnancies Description Conditional
hl7ips-dataelement-39
|
|
|
| Id |
hl7ips-dataelement-39 (2017‑12‑19 11:47:19)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(.../[Previous Pregnancy List]) OR exists(../[Summary Metric]) |
| 1 … 1 Required |
otherwise |
|
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Previous Pregnancies List Conditional
hl7ips-dataelement-1
|
|
|
| Id |
hl7ips-dataelement-1 (2017‑12‑05 17:34:58)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(.../[Previous Pregnancy Description]) OR exists(../[Summary Metric]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Previous Pregnancy 0 … * Required
hl7ips-dataelement-40
|
|
|
| Id |
hl7ips-dataelement-40 (2017‑12‑19 11:47:58)
|
| Cardinality |
0 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
|
|
|
| Outcome date 0 … 1 Required
hl7ips-dataelement-41
|
|
|
| Id |
hl7ips-dataelement-41 (2017‑12‑19 11:48:37)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least year |
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Outcome 0 … 1 Required
hl7ips-dataelement-42
|
|
|
| Id |
hl7ips-dataelement-42 (2017‑12‑19 11:49:16)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Text |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Summary Metric Conditional
hl7ips-dataelement-214
|
|
|
| Id |
hl7ips-dataelement-214 (2017‑12‑31 14:42:10)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
IF exists(.../[Previous Pregnancy List]) OR exists(../[[Previous Pregnancy Description]) |
| 1 … 1 Required |
otherwise |
|
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Specialist Contact 0 … *
hl7ips-dataelement-125
|
|
|
|
|
| History of Procedures 0 … 1 Required
hl7ips-dataelement-13
|
|
|
| Id |
hl7ips-dataelement-13 (2017‑12‑05 17:46:12)
|
| Cardinality |
0 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Procedures Content Status Conditional
hl7ips-dataelement-44
|
|
|
| Id |
hl7ips-dataelement-44 (2017‑12‑19 11:50:02)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Procedure list]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
History of procedures informing whether there is no information about procedures or
no known procedure
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:code 1 … 1 Required
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:code 1 … 1 Required
|
|
|
| Procedure list Conditional
hl7ips-dataelement-43
|
|
|
| Id |
hl7ips-dataelement-43 (2017‑12‑19 11:49:40)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Procedures Content Status]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
A list of procedures performed on the subject of care |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Procedure 1 … * Required
hl7ips-dataelement-47
|
|
|
| Id |
hl7ips-dataelement-47 (2017‑12‑19 11:52:26)
|
| Cardinality |
1 … * Required
|
| Description |
Each member of the list describes the type of procedure and identifies the actual
procedure performed and when it happened.
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:procedure 0 … *
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:procedure 0 … *
|
|
|
| Procedure code 1 … 1 Required
hl7ips-dataelement-49
|
|
|
| Id |
hl7ips-dataelement-49 (2017‑12‑19 11:55:01)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:code 1 … 1 Required
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:code 1 … 1 Required
|
|
|
| Procedure description 0 … 1 Required
hl7ips-dataelement-51
|
|
|
| Id |
hl7ips-dataelement-51 (2017‑12‑19 11:57:05)
|
| Cardinality |
0 … 1 Required
|
| Description |
Textual description of the procedure.
Derived models may choose to use distinct elements for each narrative statement or
to collect them into a single section level narrative block.
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Body site 0 … *
hl7ips-dataelement-216
|
|
|
| Id |
hl7ips-dataelement-216 (2017‑12‑31 15:07:47)
|
| Cardinality |
0 … *
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … *) in scenario IPS Originated
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:targetSiteCode 0 … *
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:targetSiteCode 0 … *
|
|
|
| Procedure date 1 … 1 Required
hl7ips-dataelement-48
|
|
|
| Id |
hl7ips-dataelement-48 (2017‑12‑19 11:53:58)
|
| Cardinality |
1 … 1 Required
|
| Description |
Period
or Date Time
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:effectiveTime 0 … 1
This concept is represented by template IPS Procedure Entry (versie 2017‑03‑27) hl7:effectiveTime 0 … 1
|
|
|
| Immunizations 0 … 1 Required
hl7ips-dataelement-14
|
|
|
| Id |
hl7ips-dataelement-14 (2017‑12‑05 17:46:44)
|
| Cardinality |
0 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Immunizations Content Status Conditional
hl7ips-dataelement-46
|
|
|
| Id |
hl7ips-dataelement-46 (2017‑12‑19 11:51:17)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Immunizations list]) |
| 1 … 1 Required |
otherwise |
|
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Immunizations list Conditional
hl7ips-dataelement-50
|
|
|
| Id |
hl7ips-dataelement-50 (2017‑12‑19 11:57:02)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Immunization Content Status]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Immunization 1 … * Required
hl7ips-dataelement-45
|
|
|
| Id |
hl7ips-dataelement-45 (2017‑12‑19 11:50:52)
|
| Cardinality |
1 … * Required
|
| Description |
A container for information related to information of
the vaccine and its administration.
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Immunization (versie 2017‑03‑08) hl7:substanceAdministration 0 … *
This concept is represented by template IPS Immunization (versie 2017‑03‑08) hl7:substanceAdministration 0 … *
|
|
|
| Vaccine for type of disease 1 … * Required
hl7ips-dataelement-52
|
|
|
| Id |
hl7ips-dataelement-52 (2017‑12‑19 12:00:26)
|
| Cardinality |
1 … * Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Target disease list 0 … 1
hl7ips-dataelement-181
|
|
|
| Id |
hl7ips-dataelement-181 (2017‑12‑25 18:49:54)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Target disease 1 … * Required
hl7ips-dataelement-207
|
|
|
| Id |
hl7ips-dataelement-207 (2017‑12‑30 15:37:08)
|
| Cardinality |
1 … * Required
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Date of Immunization 1 … 1 Required
hl7ips-dataelement-53
|
|
|
| Id |
hl7ips-dataelement-53 (2017‑12‑19 12:02:48)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Immunization (versie 2017‑03‑08) hl7:effectiveTime 1 … 1
This concept is represented by template IPS Immunization (versie 2017‑03‑08) hl7:effectiveTime 1 … 1
|
|
|
| Product Administered 0 … 1
hl7ips-dataelement-54
|
|
|
| Id |
hl7ips-dataelement-54 (2017‑12‑19 12:03:42)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Brand name 0 … 1 Required
hl7ips-dataelement-55
|
|
|
| Id |
hl7ips-dataelement-55 (2017‑12‑19 12:04:14)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
String |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Product Administration Process 0 … 1 Required
hl7ips-dataelement-215
|
|
|
| Id |
hl7ips-dataelement-215 (2017‑12‑31 14:42:35)
|
| Cardinality |
0 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Immunization (versie 2017‑03‑08) hl7:substanceAdministration 0 … *
This concept is represented by template IPS Immunization (versie 2017‑03‑08) hl7:substanceAdministration 0 … *
|
|
|
| Performer 0 … *
hl7ips-dataelement-56
|
|
|
|
|
| Route of administration 0 … 1
hl7ips-dataelement-217
|
|
|
| Id |
hl7ips-dataelement-217 (2017‑12‑31 17:22:00)
|
| Cardinality |
0 … 1
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited once |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Medical Devices 0 … 1 Required
hl7ips-dataelement-15
|
|
|
| Id |
hl7ips-dataelement-15 (2017‑12‑05 17:47:08)
|
| Cardinality |
0 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Device content Status Conditional
hl7ips-dataelement-218
|
|
|
| Id |
hl7ips-dataelement-218 (2017‑12‑31 17:23:38)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Device List]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
Records
whether there is no information about devices or no known devices
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:code 1 … 1 Required
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:code 1 … 1 Required
|
|
|
| Device List Conditional
hl7ips-dataelement-219
|
|
|
| Id |
hl7ips-dataelement-219 (2017‑12‑31 17:24:54)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Device content Status]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Device 1 … * Required
hl7ips-dataelement-57
|
|
|
| Id |
hl7ips-dataelement-57 (2017‑12‑19 12:06:23)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:participant 1 … * Required
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:participant 1 … * Required
|
|
|
| Device Type 1 … * Required
hl7ips-dataelement-58
|
|
|
| Id |
hl7ips-dataelement-58 (2017‑12‑19 12:07:12)
|
| Cardinality |
1 … * Required
|
| Description |
Category of the device |
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:code 1 … 1 Required
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:code 1 … 1 Required
|
|
|
| Device Identifier 0 … * Required
hl7ips-dataelement-60
|
|
|
| Id |
hl7ips-dataelement-60 (2017‑12‑19 12:08:29)
|
| Cardinality |
0 … * Required
|
| Description |
Note, this was not part of the eHN dataset; the device identifier (e.g. UDI) has been
added in the HL7 IPS as optional data.
Unique and normalized identifier of the device
|
| Value Domain |
Identifier |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:id 0 … * Required
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:id 0 … * Required
|
|
|
| Use start date 1 … 1 Required
hl7ips-dataelement-59
|
|
|
| Id |
hl7ips-dataelement-59 (2017‑12‑19 12:08:24)
|
| Cardinality |
1 … 1 Required
|
| Description |
Date when the device was implantable to the patient or the external device was first
in use. This field may contain only the year if the day and month are not available
(ex: 01/01/2017).
|
| Value Domain |
Date/time |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:low 1 … 1 Required
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:low 1 … 1 Required
|
|
|
| Use end date 0 … 1
hl7ips-dataelement-150
|
|
|
| Id |
hl7ips-dataelement-150 (2017‑12‑24 16:16:03)
|
| Cardinality |
0 … 1
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:high 0 … Conditional
This concept is represented by template IPS Medical Device (versie 2017‑04‑11) hl7:high 0 … Conditional
|
|
|
| Medication Summary 1 … 1 Required
hl7ips-dataelement-16
|
|
|
| Id |
hl7ips-dataelement-16 (2017‑12‑05 17:47:45)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Medication Summary content status Conditional
hl7ips-dataelement-220
|
|
|
| Id |
hl7ips-dataelement-220 (2017‑12‑31 17:30:40)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[List of current medication]) |
| 1 … 1 Required |
otherwise |
|
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| List of medication Conditional
hl7ips-dataelement-61
|
|
|
| Id |
hl7ips-dataelement-61 (2017‑12‑19 12:38:39)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Medication Summary content status]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Medication 1 … * Required
hl7ips-dataelement-104
|
|
|
| Id |
hl7ips-dataelement-104 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Medication Statement (versie 2016‑11‑11) hl7:substanceAdministration 0 … * Required
This concept is represented by template IPS Medication Statement (versie 2016‑11‑11) hl7:substanceAdministration 0 … * Required
|
|
|
| Reason 0 … 1
hl7ips-dataelement-226
|
|
|
|
|
| Medicinal Product 1 … 1 Required
hl7ips-dataelement-2
|
|
|
| Id |
hl7ips-dataelement-2 (2017‑12‑05 17:35:02)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Product Code 0 … *
hl7ips-dataelement-105
|
|
|
| Id |
hl7ips-dataelement-105 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … *
|
| Synonym |
Medicinal product Identifier
|
| Description |
A code identifying the medicine. |
| Comment |
To be clarified if at this level we need to distiguish among the different types of
"products" : e.g. packaged products; medicinal product; class of products; pharmaceutical
products;...
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … *) in scenario IPS Originated
|
|
|
| Product Common Name (and Strength) 0 … 1 Required
hl7ips-dataelement-171
|
|
|
| Id |
hl7ips-dataelement-171 (2017‑12‑25 09:41:16)
|
| Cardinality |
0 … 1 Required
|
| Data Type |
Healthcare Provider |
|
| Value Domain |
String |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Pharmaceutical dose form 1 … 1 Required
hl7ips-dataelement-227
|
|
|
| Id |
hl7ips-dataelement-227 (2018‑07‑02 15:33:59)
|
| Cardinality |
1 … 1 Required
|
| Description |
Physical manifestation of a Medicinal Product that contains the active ingredient(s)
and/or inactive ingredient(s)
that are intended to be delivered to the patient
NOTE 1 Dose form, dosage form and pharmaceutical dose form are synonymous.
NOTE 2 “Pharmaceutical dose form” can refer to the administered dose form or the manufactured
dose form.
|
| Source |
EN-ISO IDMP 11615 |
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Brand Name 0 … 1
hl7ips-dataelement-117
|
|
|
| Id |
hl7ips-dataelement-117 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1
|
| Value Domain |
String |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Active ingredient List 1 … 1 Required
hl7ips-dataelement-170
|
|
|
| Id |
hl7ips-dataelement-170 (2017‑12‑25 09:40:43)
|
| Cardinality |
1 … 1 Required
|
| Source |
CEN/TC 251 prEN 17269:2018 Health informatics —
The Patient Summary for Unscheduled Cross-border Care
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Active Ingredient 1 … 1 Required
hl7ips-dataelement-129
|
|
|
| Id |
hl7ips-dataelement-129 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Substance code 1 … 1 Required
hl7ips-dataelement-132
|
|
|
| Id |
hl7ips-dataelement-132 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Strength 1 … 1 Required
hl7ips-dataelement-133
|
|
|
| Id |
hl7ips-dataelement-133 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Quantity |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Administration Instruction 1 … 1 Required
hl7ips-dataelement-222
|
|
|
| Id |
hl7ips-dataelement-222 (2017‑12‑31 17:45:07)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Instruction 0 … 1
hl7ips-dataelement-228
|
|
|
| Id |
hl7ips-dataelement-228 (2018‑07‑02 15:37:29)
|
| Cardinality |
0 … 1
|
| Value Domain |
Text |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Period of Medication Use 1 … 1 Required
hl7ips-dataelement-103
|
|
|
| Id |
hl7ips-dataelement-103 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Description |
This information may be expressed using start and end date times OR indicating the
duration. The first is used to indicate a specified interval (e.g. from March 15th,
2017); the latter for indicating a 'floating' period (e.g. 2 weeks). In case of unbounded
period (continuous therapy) the end element will be valued with an exceptional value.
|
| Value Domain |
Duration |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template UV Use Period (versie 2017‑05‑02) hl7:effectiveTime[hl7:width] 0 … Conditional
This concept is represented by template UV Use Period (versie 2017‑05‑02) hl7:effectiveTime[hl7:low | hl7:high] 0 … Conditional
This concept is represented by template UV Use Period (versie 2017‑05‑02) hl7:effectiveTime[hl7:width] 0 … Conditional
This concept is represented by template UV Use Period (versie 2017‑05‑02) hl7:effectiveTime[hl7:low | hl7:high] 0 … Conditional
|
|
|
| Route of administration 0 … 1
hl7ips-dataelement-102
|
|
|
|
|
| Dose Instruction 1 … 1 Required
hl7ips-dataelement-119
|
|
|
| Id |
hl7ips-dataelement-119 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Number of units per intake 1 … 1 Required
hl7ips-dataelement-223
|
|
|
| Id |
hl7ips-dataelement-223 (2017‑12‑31 17:49:23)
|
| Cardinality |
1 … 1 Required
|
| Operationalization |
Range or Quantity |
| Value Domain |
Quantity |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Frequency of intake 1 … 1 Required
hl7ips-dataelement-224
|
|
|
| Id |
hl7ips-dataelement-224 (2017‑12‑31 17:50:09)
|
| Cardinality |
1 … 1 Required
|
| Data Type |
General Time Specification
|
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Plan Of Care 0 … 1
hl7ips-dataelement-17
|
|
|
| Id |
hl7ips-dataelement-17 (2017‑12‑05 17:48:20)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Plan Description Conditional
hl7ips-dataelement-110
|
|
|
| Id |
hl7ips-dataelement-110 (2017‑12‑19 12:39:26)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
exists(../[Plan Description list]) |
| 1 … 1 Required |
otherwise |
|
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Plan Description list Conditional
hl7ips-dataelement-134
|
|
|
| Id |
hl7ips-dataelement-134 (2017‑12‑19 12:39:26)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
exists(../[Plan Description]) |
| 1 … 1 Required |
otherwise |
|
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Plan 1 … * Required
hl7ips-dataelement-114
|
|
|
| Id |
hl7ips-dataelement-114 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Plan Type 0 … 1 Required
hl7ips-dataelement-108
|
|
|
| Id |
hl7ips-dataelement-108 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Plan Date 0 … 1 Required
hl7ips-dataelement-107
|
|
|
| Id |
hl7ips-dataelement-107 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Recommendations list Conditional
hl7ips-dataelement-109
|
|
|
| Id |
hl7ips-dataelement-109 (2017‑12‑19 12:39:26)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
exists(../[Extended Plan]) |
| 1 … 1 Required |
otherwise |
|
|
| Synonym |
Core Care Plan
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Recommendation for treatment 1 … 1 Required
hl7ips-dataelement-113
|
|
|
| Id |
hl7ips-dataelement-113 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Identifier |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Given Recommendations date 0 … 1 Required
hl7ips-dataelement-111
|
|
|
| Id |
hl7ips-dataelement-111 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Date/time |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|
| Applicable dates 0 … 1 Required
hl7ips-dataelement-112
|
|
|
|
|
| Extended Plan Conditional
hl7ips-dataelement-116
|
|
|
| Id |
hl7ips-dataelement-116 (2017‑12‑19 12:39:26)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 1 |
exists(../[Recommendations list]) |
| 1 … 1 Required |
otherwise |
|
|
| Synonym |
trade name
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Problems 1 … 1 Required
hl7ips-dataelement-18
|
|
|
| Id |
hl7ips-dataelement-18 (2017‑12‑05 17:48:39)
|
| Cardinality |
1 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problems Section (versie 2017‑02‑15) hl7:section 1 … 1 Mandatory
This concept is represented by template IPS Problems Section (versie 2017‑02‑15) hl7:section 1 … 1 Mandatory
|
|
|
| Problem content status Conditional
hl7ips-dataelement-115
|
|
|
| Id |
hl7ips-dataelement-115 (2017‑12‑19 12:39:26)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Problem list] |
| 1 … 1 Required |
otherwise |
|
|
| Description |
The
patient has had no previous problems, or the problem information is unknown
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:value 1 … 1 Mandatory
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:value 1 … 1 Mandatory
|
|
|
| Problem list Conditional
hl7ips-dataelement-139
|
|
|
| Id |
hl7ips-dataelement-139 (2017‑12‑24 15:49:09)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Problem content status]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
The
problem list comprises members that are current, either because they are
active, unresolved or of concern and being monitored.
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Problems Section (versie 2017‑02‑15) hl7:entry 1 … * Required
This concept is represented by template IPS Problems Section (versie 2017‑02‑15) hl7:entry 1 … * Required
|
|
|
| Problem 1 … * Required
hl7ips-dataelement-140
|
|
|
| Id |
hl7ips-dataelement-140 (2017‑12‑24 15:49:52)
|
| Cardinality |
1 … * Required
|
| Description |
One
or more problems are listed; each comprising the same structure describing the
nature of the problem and its date of onset.
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:observation 0 … * Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:observation 0 … * Required
|
|
|
| Problem type 0 … 1 Required
hl7ips-dataelement-101
|
|
|
| Id |
hl7ips-dataelement-101 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:code 1 … 1 Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:code 1 … 1 Required
|
|
|
| Description 1 … 1 Required
hl7ips-dataelement-130
|
|
|
| Id |
hl7ips-dataelement-130 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problems Section (versie 2017‑02‑15) hl7:text 1 … 1 Mandatory
This concept is represented by template IPS Problems Section (versie 2017‑02‑15) hl7:text 1 … 1 Mandatory
|
|
|
| Diagnosis 1 … 1 Required
hl7ips-dataelement-131
|
|
|
| Id |
hl7ips-dataelement-131 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Description |
Label used to describe a problem; usually coded.
|
| Value Domain |
Code |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:value 1 … 1 Mandatory
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:value 1 … 1 Mandatory
|
|
|
| Severity 0 … 1 Required
hl7ips-dataelement-128
|
|
|
| Id |
hl7ips-dataelement-128 (2017‑12‑19 12:39:26)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Code |
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:entryRelationship 0 … 1 Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:entryRelationship 0 … 1 Required
|
|
|
| Onset date 1 … 1 Required
hl7ips-dataelement-127
|
|
|
| Id |
hl7ips-dataelement-127 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Date/time |
| Property |
| Timestamp precision |
| at least day, month and year |
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:low 1 … 1 Required
This concept is represented by template IPS Problem Entry (versie 2017‑02‑15) hl7:low 1 … 1 Required
|
|
|
| Specialist Contact 0 … 1
hl7ips-dataelement-25
|
|
|
|
|
| Results 0 … 1 Required
hl7ips-dataelement-19
|
|
|
| Id |
hl7ips-dataelement-19 (2017‑12‑05 17:49:04)
|
| Cardinality |
0 … 1 Required
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Results Section (versie 2017‑04‑30) hl7:section 0 … *
This concept is represented by template IPS Results Section (versie 2017‑04‑30) hl7:section 0 … *
|
|
|
| Observation Results Content Status Conditional
hl7ips-dataelement-141
|
|
|
| Id |
hl7ips-dataelement-141 (2017‑12‑24 16:04:33)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Observation results list]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
Statement
about presence/absence of content.
|
| Value Domain |
Code |
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
|
|
|
| Observations results list Conditional
hl7ips-dataelement-126
|
|
|
| Id |
hl7ips-dataelement-126 (2017‑12‑19 12:39:26)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Observation results Content Status]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
A
conditional list of all observation results pertaining to the subject of care’s
health condition
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Results Section (versie 2017‑04‑30) hl7:entry 1 … * Mandatory
This concept is represented by template IPS Results Section (versie 2017‑04‑30) hl7:entry 1 … * Mandatory
|
|
|
| Observation Result 1 … * Required
hl7ips-dataelement-106
|
|
|
| Id |
hl7ips-dataelement-106 (2017‑12‑19 12:39:26)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:organizer 0 … *
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:organizer 0 … *
|
|
|
| Date of observation 1 … 1 Required
hl7ips-dataelement-143
|
|
|
| Id |
hl7ips-dataelement-143 (2017‑12‑24 16:11:12)
|
| Cardinality |
1 … 1 Required
|
| Operationalization |
Date Time or Period |
| Value Domain |
Duration |
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Result Observation (versie 2017‑03‑02) hl7:effectiveTime 1 … 1 Required
This concept is represented by template IPS Result Observation (versie 2017‑03‑02) hl7:effectiveTime 1 … 1 Required
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:effectiveTime 0 … 1
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:effectiveTime 0 … 1
|
|
|
| Observation Type 1 … 1 Required
hl7ips-dataelement-144
|
|
|
| Id |
hl7ips-dataelement-144 (2017‑12‑24 16:11:40)
|
| Cardinality |
1 … 1 Required
|
| Description |
The list contains members representing the types of results.
Note: the eHN give only two examples (non-exhaustive) and these may be
represented in a value set with these two types included:
- Diagnostic results
- Physical findings
|
| Value Domain |
Code |
| Used by
|
one transaction, 2 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:code 1 … 1 Required
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:code 1 … 1 Required
|
|
|
| Result Description 1 … * Required
hl7ips-dataelement-142
|
|
|
| Id |
hl7ips-dataelement-142 (2017‑12‑24 16:10:43)
|
| Cardinality |
1 … * Required
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
This concept is represented by template IPS Results Section (versie 2017‑04‑30) hl7:text 1 … 1 Mandatory
This concept is represented by template IPS Results Section (versie 2017‑04‑30) hl7:text 1 … 1 Mandatory
|
|
|
| Value Conditional
hl7ips-dataelement-145
|
|
|
| Id |
hl7ips-dataelement-145 (2017‑12‑24 16:11:56)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../[Observation Result]) |
| 1 … 1 Required |
otherwise |
|
|
| Description |
The measurement value and details about how the tests
were done to get the result values.
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Conditional) in scenario IPS Originated
This concept is represented by template IPS Result Observation (versie 2017‑03‑02) hl7:value[@xsi:type='CE.IPS'] 0 … 1 Required
This concept is represented by template IPS Result Observation (versie 2017‑03‑02) hl7:value[@xsi:type='CE.IPS'] 0 … 1 Required
|
|
|
| Observation Result Conditional
hl7ips-dataelement-23
|
|
|
| Id |
hl7ips-dataelement-23 (2017‑12‑05 17:55:42)
|
| Cardinality |
Conditional
| Card/Conf |
Condition |
| 0 … 0 Not present |
exists(../Value) |
| 1 … * Required |
otherwise |
|
|
| Concept references |
hl7ips-dataelement-106 (2017‑12‑19 12:39:26)
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Conditional) in scenario IPS Originated
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:component 0 … *
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:component 0 … *
|
|
|
| Performer 0 … * Required
hl7ips-dataelement-146
|
|
|
| Id |
hl7ips-dataelement-146 (2017‑12‑24 16:12:16)
|
| Cardinality |
0 … * Required
|
| Description |
Identifies
the originator/author and provides provenance information about the source of
the results data that may have not originated with the source of the whole IPS
document.
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:performer 0 … * Required
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:performer 0 … * Required
|
|
|
| Observer 0 … * Required
hl7ips-dataelement-177
|
|
|
| Id |
hl7ips-dataelement-177 (2017‑12‑25 09:47:03)
|
| Cardinality |
0 … * Required
|
| Value Domain |
Collection of data |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … * Required) in scenario IPS Originated
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:author 0 … * Required
This concept is represented by template IPS Result Organizer (versie 2017‑03‑02) hl7:author 0 … * Required
|
|
|
| Social History 0 … 1
hl7ips-dataelement-20
|
|
|
| Id |
hl7ips-dataelement-20 (2017‑12‑05 17:49:22)
|
| Cardinality |
0 … 1
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1) in scenario IPS Originated
|
|
|
| Life Style Factor list 1 … 1 Required
hl7ips-dataelement-147
|
|
|
| Id |
hl7ips-dataelement-147 (2017‑12‑24 16:14:03)
|
| Cardinality |
1 … 1 Required
|
| Description |
An
open-ended list of composite objects that describes the past and current habits
of the patient with respect to a particular life style observation.
If this IPS Section is present then the list shall be
non-empty.
Composite
object describing the name of the lifestyle factor and descriptive text or
structured codes providing more details, with ranges and amounts when
applicable; Textual information if coded/quantified data are not available.
|
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Life Style Factor 1 … * Required
hl7ips-dataelement-148
|
|
|
| Id |
hl7ips-dataelement-148 (2017‑12‑24 16:14:36)
|
| Cardinality |
1 … * Required
|
| Used by
|
one transaction, 0 templates, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … * Required) in scenario IPS Originated
|
|
|
| Description 1 … 1 Required
hl7ips-dataelement-149
|
|
|
| Id |
hl7ips-dataelement-149 (2017‑12‑24 16:15:34)
|
| Cardinality |
1 … 1 Required
|
| Value Domain |
Text |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (1 … 1 Required) in scenario IPS Originated
|
|
|
| Life Style Factor 0 … *
hl7ips-dataelement-176
|
|
|
|
|
| Reference date range 0 … 1 Required
hl7ips-dataelement-151
|
|
|
| Id |
hl7ips-dataelement-151 (2017‑12‑24 16:16:19)
|
| Cardinality |
0 … 1 Required
|
| Value Domain |
Duration |
| Used by
|
one transaction, one template, inherited 0 times |
| |
This concept is used in transaction IPS Created (0 … 1 Required) in scenario IPS Originated
|
|
|