Back To Index  <<  Back To Scenarios

draft Scenario IPS Originated 2.16.840.1.113883.3.1937.777.13.3.1

Name Details [‑]
draft IPS Originated
hl7ips-scenario-1
Version / effective date 2017‑04‑07 11:10:54
draft doublearrow Group
hl7ips-transaction-1link
Version / effective date 2017‑04‑07 11:10:54    
You need SVG support in your browser for this image
draft rotate IPS Created
hl7ips-transaction-2link
Version / effective date 2017‑04‑07 11:10:54    
Label hl7ips1
Actor
Sender (organization) IPS Creator
Associations
Contained concepts
Concept Card/Conf Id
folder Patient Attributes
1 … 1 Required
hl7ips-dataelement-2.1link
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
treetree draft  Patient's Name
1 … * Required
hl7ips-dataelement-3link
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. It requires family and given name components.
treetree folder Patient’s address and telecom
0 … * Required
hl7ips-dataelement-155link
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.
treeblank treetree draft  Address
0 … * Required
hl7ips-dataelement-162link
treeblank treetree draft  Telecoms
0 … * Required
hl7ips-dataelement-100link
treetree draft  Administrative Gender
0 … 1 Required
hl7ips-dataelement-4link
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’
treetree draft  Date of Birth
1 … 1 Required
hl7ips-dataelement-5link
treetree draft  Patient’s preferred language
0 … 1
hl7ips-dataelement-135link
treetree folder Healthcare related Identifiers
0 … * Required
hl7ips-dataelement-202link
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.
treeblank treetree draft  Patient Identifier
0 … * Required
hl7ips-dataelement-6link
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.
treetree folder Insurance Information
0 … *
hl7ips-dataelement-203link
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.
treeblank treetree draft  Insurance identifier
0 … * Required
hl7ips-dataelement-7link
folder Patient’s Address Book
0 … 1 Required
hl7ips-dataelement-154link
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.
treetree folder Preferred Healthcare providers
0 … 1 Required
hl7ips-dataelement-163link
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.
treeblank treetree folder Healthcare Provider (person)
0 … * Conditional
hl7ips-dataelement-165link
Card/Conf Condition
0 … * exist(Healthcare Provider (organisation))
1 … * Required otherwise
treeblank treeblank treetree draft  Name
1 … * Required
hl7ips-dataelement-121link
It requires family and given name components.
treeblank treeblank treetree draft  Telecoms
0 … * Required
hl7ips-dataelement-169link
treeblank treetree folder Healthcare Provider (organisation)
0 … * Conditional
hl7ips-dataelement-166link
Card/Conf Condition
0 … * exist(Healthcare Provider (person))
1 … * Required otherwise
treeblank treeblank treetree draft  Organisation’s Name
1 … * Required
hl7ips-dataelement-172link
treeblank treeblank treetree draft  Telecoms
0 … * Required
hl7ips-dataelement-174link
treetree folder Other's Contacts’ Details
0 … 1
hl7ips-dataelement-164link
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).
treeblank treetree folder Contact
1 … * Required
hl7ips-dataelement-167link
treeblank treeblank treetree draft  Role
0 … 1 Required
hl7ips-dataelement-175link
treeblank treeblank treetree draft  Name
1 … * Required
hl7ips-dataelement-157link
It requires family and given name components.
treeblank treeblank treetree draft  Address
0 … *
hl7ips-dataelement-120link
Address
treeblank treeblank treetree draft  Telecoms
0 … * Required
hl7ips-dataelement-122link
folder Advance Directives
0 … 1
hl7ips-dataelement-8link
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
treetree folder Advance Directives
1 … 1 Required
hl7ips-dataelement-24link
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
treeblank treetree folder Advance Directive
1 … * Required
hl7ips-dataelement-179link
treeblank treeblank treetree folder Person authorising Directive
0 … 1 Required
hl7ips-dataelement-22link
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.
treeblank treeblank treeblank treetree draft  Name
0 … * Required
hl7ips-dataelement-118link
It requires family and given name components.
treeblank treeblank treeblank treetree draft  Telecoms
0 … * Required
hl7ips-dataelement-178link
treeblank treeblank treetree draft  Directive category
0 … *
hl7ips-dataelement-180link
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.
treeblank treeblank treetree draft  Description
0 … * Conditional
hl7ips-dataelement-26link
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.
Card/Conf Condition
0 … * exist(../Reference to Legal Document)
1 … * Required otherwise
treeblank treeblank treetree draft  Reference to Legal Document
0 … * Conditional
hl7ips-dataelement-27link
The Directives may take the form of a reference to a legal document (e.g. Living Will) or an external textual description.
Card/Conf Condition
0 … * exists(../Description)
1 … * Required otherwise
folder Allergies and Intolerances
1 … 1 Required
hl7ips-dataelement-9link
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.
treetree draft  Allergies/Intolerances Content Status
0 … 1 Conditional
hl7ips-dataelement-182link
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.
Card/Conf Condition
0 … 0 Not present exists(../Allergy or Intolerance list)
1 … 1 Required otherwise
treetree folder Allergy or Intolerance list
0 … 1 Conditional
hl7ips-dataelement-28link
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.
Card/Conf Condition
0 … 0 Not present exists(../Allergies/Intolerances Content Status)
1 … 1 Required otherwise
treeblank treetree folder Allergy/Intolerance
1 … * Mandatory
hl7ips-dataelement-184link
treeblank treeblank treetree draft  Description
1 … 1 Required
hl7ips-dataelement-183link
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.
treeblank treeblank treetree draft  Clinical Status
1 … 1 Required
hl7ips-dataelement-186link
Provides the current status of the allergy or intolerance, for example, whether it is active, in remission, resolved, and so on.
treeblank treeblank treetree draft  Onset date
1 … 1 Required
hl7ips-dataelement-187link
It shall be provided with the highest known precision, at least year
treeblank treeblank treetree draft  End Date
0 … 1 Conditional
hl7ips-dataelement-188link
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.
Card/Conf Condition
1 … 1 Required if clinical status non-active
0 … 0 Not present otherwise
treeblank treeblank treetree draft  Criticality
0 … 1
hl7ips-dataelement-189link
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.
treeblank treeblank treetree draft  Certainty
0 … 1
hl7ips-dataelement-190link
Assertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance
treeblank treeblank treetree draft  Type of propensity
0 … 1 Required
hl7ips-dataelement-191link
Type of allergy or intolerance.
treeblank treeblank treetree draft  Diagnosis
0 … 1
hl7ips-dataelement-185link
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
treeblank treeblank treetree folder Reaction
0 … * Required
hl7ips-dataelement-192link
A Label Concept recognising that other data concerning the reaction may be made available in later versions of this standard.
treeblank treeblank treeblank treetree draft  Manifestation of the reaction
0 … 1 Required
hl7ips-dataelement-193link
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.
treeblank treeblank treeblank treetree draft  Severity
0 … 1 Required
hl7ips-dataelement-194link
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.
treeblank treeblank treetree folder Agent
1 … 1 Required
hl7ips-dataelement-173link
treeblank treeblank treeblank treetree draft  Agent code
1 … 1 Required
hl7ips-dataelement-196link
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.
treeblank treeblank treeblank treetree draft  Category
0 … 1
hl7ips-dataelement-195link
Allergy substance category
folder Functional Status
0 … 1
hl7ips-dataelement-10link
treetree folder Disabilities List
0 … 1 Conditional
hl7ips-dataelement-156link
Card/Conf Condition
0 … 1 IF exists(../Functional Assessments List)
1 … 1 Required otherwise
treeblank treetree folder Disability
1 … * Required
hl7ips-dataelement-29link
treeblank treeblank treetree draft  Description
1 … 1 Required
hl7ips-dataelement-197link
treeblank treeblank treetree draft  Disability Code
0 … 1
hl7ips-dataelement-198link
treeblank treeblank treetree draft  Onset date
0 … 1
hl7ips-dataelement-199link
treetree folder Functional Assessments List
0 … 1 Conditional
hl7ips-dataelement-30link
Card/Conf Condition
0 … 1 IF exists(../Disabilities List)
1 … 1 Required otherwise
treeblank treetree folder Functional Assessment
1 … * Required
hl7ips-dataelement-201link
treeblank treeblank treetree draft  Description
1 … 1 Required
hl7ips-dataelement-137link
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
treeblank treeblank treetree draft  Date of assessment
0 … 1 Required
hl7ips-dataelement-204link
treeblank treeblank treetree draft  Type
0 … 1 Required
hl7ips-dataelement-205link
treeblank treeblank treetree draft  Result
0 … 1 Conditional
hl7ips-dataelement-206link
Card/Conf Condition
1 … 1 Required otherwise
0 … 0 Not present IF exists(../Functional Assessment)
treeblank treeblank treetree folder Functional Assessment
0 … 1 Conditional
hl7ips-dataelement-21link
Card/Conf Condition
0 … 0 Not present IF exists(../Result)
1 … 1 Required otherwise
folder History of Past Illness
0 … 1
hl7ips-dataelement-11link
treetree draft  Past illness content status
0 … 1 Conditional
hl7ips-dataelement-208link
Card/Conf Condition
0 … 0 Not present exists(../[Past health conditions and problems])
1 … 1 Required otherwise
treetree folder Past health conditions and problems list
0 … 1 Conditional
hl7ips-dataelement-31link
Card/Conf Condition
0 … 0 Not present exists(../[Past illness content status])
1 … 1 Required otherwise
treeblank treetree folder Health condition / Problem
1 … * Required
hl7ips-dataelement-209link
treeblank treeblank treetree draft  Problem Type
0 … 1 Required
hl7ips-dataelement-210link
treeblank treeblank treetree draft  Description
1 … 1 Required
hl7ips-dataelement-35link
treeblank treeblank treetree draft  Diagnosis
1 … 1 Required
hl7ips-dataelement-36link
treeblank treeblank treetree draft  Severity
0 … 1
hl7ips-dataelement-136link
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.
treeblank treeblank treetree draft  Onset Date
1 … 1 Required
hl7ips-dataelement-32link
Date of the first observation of adverse reactions
treeblank treeblank treetree draft  Resolution
0 … 1
hl7ips-dataelement-33link
treeblank treeblank treetree draft  Date resolved
0 … 1 Conditional
hl7ips-dataelement-34link
Card/Conf Condition
1 … 1 Required IF status non-active
0 … 0 Not present otherwise
treeblank treeblank treetree draft  Specialist Contact
0 … *
hl7ips-dataelement-124link
folder History of Pregnancy
0 … 1
hl7ips-dataelement-12link
treetree folder Status of pregnancy
1 … 1 Required
hl7ips-dataelement-37link
treeblank treetree draft  Pregnancy Description
0 … 1 Conditional
hl7ips-dataelement-225link
Card/Conf Condition
0 … 1 IF exists(../[Structured Description])
1 … 1 Required otherwise
treeblank treetree folder Structured Description
0 … 1 Conditional
hl7ips-dataelement-168link
Card/Conf Condition
0 … 1 IF exists(../[Pregnancy Description])
1 … 1 Required otherwise
treeblank treeblank treetree draft  Date of Observation
1 … 1 Required
hl7ips-dataelement-211link
treeblank treeblank treetree draft  Pregnancy State
1 … 1 Required
hl7ips-dataelement-212link
treeblank treeblank treetree draft  Expected delivery date
0 … 1 Conditional
hl7ips-dataelement-213link
Card/Conf Condition
1 … 1 Required IF pregnant
0 … 0 Not present otherwise
treeblank treetree draft  Specialist Contact
0 … *
hl7ips-dataelement-200link
treetree folder Previous Pregnancies
0 … 1
hl7ips-dataelement-38link
treeblank treetree draft  Previous Pregnancies Description
0 … 1 Conditional
hl7ips-dataelement-39link
Card/Conf Condition
0 … 1 IF exists(.../[Previous Pregnancy List]) OR exists(../[Summary Metric])
1 … 1 Required otherwise
treeblank treetree folder Previous Pregnancies List
0 … 1 Conditional
hl7ips-dataelement-1link
Card/Conf Condition
0 … 1 IF exists(.../[Previous Pregnancy Description]) OR exists(../[Summary Metric])
1 … 1 Required otherwise
treeblank treeblank treetree folder Previous Pregnancy
0 … * Required
hl7ips-dataelement-40link
treeblank treeblank treeblank treetree draft  Outcome date
0 … 1 Required
hl7ips-dataelement-41link
treeblank treeblank treeblank treetree draft  Outcome
0 … 1 Required
hl7ips-dataelement-42link
treeblank treetree draft  Summary Metric
0 … 1 Conditional
hl7ips-dataelement-214link
Card/Conf Condition
0 … 1 IF exists(.../[Previous Pregnancy List]) OR exists(../[[Previous Pregnancy Description])
1 … 1 Required otherwise
treeblank treetree draft  Specialist Contact
0 … *
hl7ips-dataelement-125link
folder History of Procedures
0 … 1 Required
hl7ips-dataelement-13link
treetree draft  Procedures Content Status
0 … 1 Conditional
hl7ips-dataelement-44link
History of procedures informing whether there is no information about procedures or no known procedure 
Card/Conf Condition
0 … 0 Not present exists(../[Procedure list])
1 … 1 Required otherwise
treetree folder Procedure list
0 … 1 Conditional
hl7ips-dataelement-43link
A list of procedures performed on the subject of care
Card/Conf Condition
0 … 0 Not present exists(../[Procedures Content Status])
1 … 1 Required otherwise
treeblank treetree folder Procedure
1 … * Required
hl7ips-dataelement-47link
Each member of the list describes the type of procedure and identifies the actual procedure performed and when it happened.
treeblank treeblank treetree draft  Procedure code
1 … 1 Required
hl7ips-dataelement-49link
treeblank treeblank treetree draft  Procedure description
0 … 1 Required
hl7ips-dataelement-51link
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.

treeblank treeblank treetree draft  Body site
0 … *
hl7ips-dataelement-216link
treeblank treeblank treetree draft  Procedure date
1 … 1 Required
hl7ips-dataelement-48link
Period or Date Time
folder Immunizations
0 … 1 Required
hl7ips-dataelement-14link
treetree draft  Immunizations Content Status
0 … 1 Conditional
hl7ips-dataelement-46link
Card/Conf Condition
0 … 0 Not present exists(../[Immunizations list])
1 … 1 Required otherwise
treetree folder Immunizations list
0 … 1 Conditional
hl7ips-dataelement-50link
Card/Conf Condition
0 … 0 Not present exists(../[Immunization Content Status])
1 … 1 Required otherwise
treeblank treetree folder Immunization
1 … * Required
hl7ips-dataelement-45link

A container for information related to information of the vaccine and its administration.

treeblank treeblank treetree draft  Vaccine for type of disease
1 … * Required
hl7ips-dataelement-52link
treeblank treeblank treetree folder Target disease list
0 … 1
hl7ips-dataelement-181link
treeblank treeblank treeblank treetree draft  Target disease
1 … * Required
hl7ips-dataelement-207link
treeblank treeblank treetree draft  Date of Immunization
1 … 1 Required
hl7ips-dataelement-53link
treeblank treeblank treetree folder Product Administered
0 … 1
hl7ips-dataelement-54link
treeblank treeblank treeblank treetree draft  Brand name
0 … 1 Required
hl7ips-dataelement-55link
treeblank treeblank treetree folder Product Administration Process
0 … 1 Required
hl7ips-dataelement-215link
treeblank treeblank treeblank treetree draft  Performer
0 … *
hl7ips-dataelement-56link
treeblank treeblank treeblank treetree draft  Route of administration
0 … 1
hl7ips-dataelement-217link
folder Medical Devices
0 … 1 Required
hl7ips-dataelement-15link
treetree draft  Device content Status
0 … 1 Conditional
hl7ips-dataelement-218link

Records whether there is no information about devices or no known devices

Card/Conf Condition
0 … 0 Not present exists(../[Device List])
1 … 1 Required otherwise
treetree folder Device List
0 … 1 Conditional
hl7ips-dataelement-219link
Card/Conf Condition
0 … 0 Not present exists(../[Device content Status])
1 … 1 Required otherwise
treeblank treetree folder Device
1 … * Required
hl7ips-dataelement-57link
treeblank treeblank treetree draft  Device Type
1 … * Required
hl7ips-dataelement-58link
Category of the device
treeblank treeblank treetree draft  Device Identifier
0 … * Required
hl7ips-dataelement-60link
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
treeblank treeblank treetree draft  Use start date
1 … 1 Required
hl7ips-dataelement-59link
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). 
treeblank treeblank treetree draft  Use end date
0 … 1
hl7ips-dataelement-150link
folder Medication Summary
1 … 1 Required
hl7ips-dataelement-16link
treetree draft  Medication Summary content status
0 … 1 Conditional
hl7ips-dataelement-220link
Card/Conf Condition
0 … 0 Not present exists(../[List of current medication])
1 … 1 Required otherwise
treetree folder List of medication
0 … 1 Conditional
hl7ips-dataelement-61link
Card/Conf Condition
0 … 0 Not present exists(../[Medication Summary content status])
1 … 1 Required otherwise
treeblank treetree folder Medication
1 … * Required
hl7ips-dataelement-104link
treeblank treeblank treetree draft  Reason
0 … 1
hl7ips-dataelement-226link
treeblank treeblank treetree folder Medicinal Product
1 … 1 Required
hl7ips-dataelement-2link
treeblank treeblank treeblank treetree draft  Product Code
0 … *
hl7ips-dataelement-105link
A code identifying the medicine. 
treeblank treeblank treeblank treetree draft  Product Common Name (and Strength)
0 … 1 Required
hl7ips-dataelement-171link
treeblank treeblank treeblank treetree draft  Pharmaceutical dose form
1 … 1 Required
hl7ips-dataelement-227link
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.
treeblank treeblank treeblank treetree draft  Brand Name
0 … 1
hl7ips-dataelement-117link
treeblank treeblank treeblank treetree folder Active ingredient List
1 … 1 Required
hl7ips-dataelement-170link
treeblank treeblank treeblank treeblank treetree folder Active Ingredient
1 … 1 Required
hl7ips-dataelement-129link
treeblank treeblank treeblank treeblank treeblank treetree draft  Substance code
1 … 1 Required
hl7ips-dataelement-132link
treeblank treeblank treeblank treeblank treeblank treetree draft  Strength
1 … 1 Required
hl7ips-dataelement-133link
treeblank treeblank treetree folder Administration Instruction
1 … 1 Required
hl7ips-dataelement-222link
treeblank treeblank treeblank treetree draft  Instruction
0 … 1
hl7ips-dataelement-228link
treeblank treeblank treeblank treetree draft  Period of Medication Use
1 … 1 Required
hl7ips-dataelement-103link
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.
treeblank treeblank treeblank treetree draft  Route of administration
0 … 1
hl7ips-dataelement-102link
treeblank treeblank treeblank treetree folder Dose Instruction
1 … 1 Required
hl7ips-dataelement-119link
treeblank treeblank treeblank treeblank treetree draft  Number of units per intake
1 … 1 Required
hl7ips-dataelement-223link
Range or Quantity
treeblank treeblank treeblank treeblank treetree draft  Frequency of intake
1 … 1 Required
hl7ips-dataelement-224link
folder Plan Of Care
0 … 1
hl7ips-dataelement-17link
treetree draft  Plan Description
0 … 1 Conditional
hl7ips-dataelement-110link
Card/Conf Condition
0 … 1 exists(../[Plan Description list])
1 … 1 Required otherwise
treetree folder Plan Description list
0 … 1 Conditional
hl7ips-dataelement-134link
Card/Conf Condition
0 … 1 exists(../[Plan Description])
1 … 1 Required otherwise
treeblank treetree folder Plan
1 … * Required
hl7ips-dataelement-114link
treeblank treeblank treetree draft  Plan Type
0 … 1 Required
hl7ips-dataelement-108link
treeblank treeblank treetree draft  Plan Date
0 … 1 Required
hl7ips-dataelement-107link
treeblank treetree folder Recommendations list
0 … 1 Conditional
hl7ips-dataelement-109link
Card/Conf Condition
0 … 1 exists(../[Extended Plan])
1 … 1 Required otherwise
treeblank treeblank treetree draft  Recommendation for treatment
1 … 1 Required
hl7ips-dataelement-113link
treeblank treeblank treetree draft  Given Recommendations date
0 … 1 Required
hl7ips-dataelement-111link
treeblank treeblank treetree draft  Applicable dates
0 … 1 Required
hl7ips-dataelement-112link
treeblank treetree draft  Extended Plan
0 … 1 Conditional
hl7ips-dataelement-116link
Card/Conf Condition
0 … 1 exists(../[Recommendations list])
1 … 1 Required otherwise
folder Problems
1 … 1 Required
hl7ips-dataelement-18link
treetree draft  Problem content status
0 … 1 Conditional
hl7ips-dataelement-115link
The patient has had no previous problems, or the problem information is unknown
Card/Conf Condition
0 … 0 Not present exists(../[Problem list]
1 … 1 Required otherwise
treetree folder Problem list
0 … 1 Conditional
hl7ips-dataelement-139link

The problem list comprises members that are current, either because they are active, unresolved or of concern and being monitored.

Card/Conf Condition
0 … 0 Not present exists(../[Problem content status])
1 … 1 Required otherwise
treeblank treetree folder Problem
1 … * Required
hl7ips-dataelement-140link

One or more problems are listed; each comprising the same structure describing the nature of the problem and its date of onset.

treeblank treeblank treetree draft  Problem type
0 … 1 Required
hl7ips-dataelement-101link
treeblank treeblank treetree draft  Description
1 … 1 Required
hl7ips-dataelement-130link
treeblank treeblank treetree draft  Diagnosis
1 … 1 Required
hl7ips-dataelement-131link

Label used to describe a problem; usually coded.
treeblank treeblank treetree draft  Severity
0 … 1 Required
hl7ips-dataelement-128link
treeblank treeblank treetree draft  Onset date
1 … 1 Required
hl7ips-dataelement-127link
treeblank treeblank treetree draft  Specialist Contact
0 … 1
hl7ips-dataelement-25link
folder Results
0 … 1 Required
hl7ips-dataelement-19link
treetree draft  Observation Results Content Status
0 … 1 Conditional
hl7ips-dataelement-141link

Statement about presence/absence of content.

Card/Conf Condition
0 … 0 Not present exists(../[Observation results list])
1 … 1 Required otherwise
treetree folder Observations results list
0 … 1 Conditional
hl7ips-dataelement-126link
A conditional list of all observation results pertaining to the subject of care’s health condition
Card/Conf Condition
0 … 0 Not present exists(../[Observation results Content Status])
1 … 1 Required otherwise
treeblank treetree folder Observation Result
1 … * Required
hl7ips-dataelement-106link
treeblank treeblank treetree draft  Date of observation
1 … 1 Required
hl7ips-dataelement-143link
Date Time or Period
treeblank treeblank treetree draft  Observation Type
1 … 1 Required
hl7ips-dataelement-144link

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
treeblank treeblank treetree draft  Result Description
1 … * Required
hl7ips-dataelement-142link
treeblank treeblank treetree draft  Value
0 … 1 Conditional
hl7ips-dataelement-145link

The measurement value and details about how the tests were done to get the result values.

Card/Conf Condition
0 … 0 Not present exists(../[Observation Result])
1 … 1 Required otherwise
treeblank treeblank treetree folder Observation Result
0 … * Conditional
hl7ips-dataelement-23link
Card/Conf Condition
0 … 0 Not present exists(../Value)
1 … * Required otherwise
treeblank treeblank treetree draft  Performer
0 … * Required
hl7ips-dataelement-146link

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. 

treeblank treeblank treetree draft  Observer
0 … * Required
hl7ips-dataelement-177link
folder Social History
0 … 1
hl7ips-dataelement-20link
treetree folder Life Style Factor list
1 … 1 Required
hl7ips-dataelement-147link

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. 


treeblank treetree folder Life Style Factor
1 … * Required
hl7ips-dataelement-148link
treeblank treeblank treetree draft  Description
1 … 1 Required
hl7ips-dataelement-149link
treeblank treeblank treetree folder Life Style Factor
0 … *
hl7ips-dataelement-176link
treeblank treeblank treetree draft  Reference date range
0 … 1 Required
hl7ips-dataelement-151link