Standard Category Integration
Paradigm Product Name Activities and
Ballot Topics
Health Information Exchange Standards PC Workgroup
Organisation
Patient Care WG work Mission & Charter
Health Information Exchange Standards PC Workgroup
Organisation
Project Matrix Three year Work Plan
Project Review and Cleanup
Every WGM
Health Information Exchange Standards PC Workgroup
Organisation
SWOT analysis SWOT Analysis
Health Information Exchange Standards PC Workgroup
Organisation
Decision Making
Policies
DMP
Health Information
Exchange
Standards
Messaging V3: Care Provision Care Provision D-MIM
Health Information
Exchange
Standards
Messaging V3: Care Provision Care Statement Topic
Health Information Exchange Standards Messaging V3: Care Provision Care Record Topic
Care Record Query Topic
Care Transfer Topic
Health Information
Exchange
Standards
Messaging V3: Care Provision Care Structures Topic
Health Information Exchange Standards Messaging V3: Care Provision Care Structures to move to
Concern Topic work Jan 2012,
ballot May 2012
Vitals Observations Topic
Jan2012, ballot May 2012
Statementcollector Topic and
link to problem list Jan 2012,
ballot May 2012
Health Information
Exchange
Standards
Messaging V3: Care Provision Care Plan Topic
Health Information Exchange Standards Messaging V3: Care Provision Allergies, Intolerance and
Adverse Reaction Topic
Health Information
Exchange
Standards
Messaging V3: Care Provision Health Concern Topic
Health Information
Exchange
Standards
Messaging V3: Care Provision Assessment Scales Topic
Health Information
Exchange
Standards
Messaging V3: Care Provision Concern Tracking Topic
Clinical Content
Specification
several V3: Care Provision Detailed Clinical Models Topic
Health Information Exchange Standards Messaging V2: Chapter 11 and 12
of V2 Patient Care
Australian input, and from other
users sought
Health Information Exchange Standards SOA Patient Care materials
as SOA payload
new topic / needs project scope
statement, define the services
that exist, their functionalities,
and perhaps create an
implementation guide
Clinical Content Specification Clinical
Content
Including PC materials
into template registry
Register PC template instances,
and determine what our
requirements are
Vocabulary HL7Messaging Concern Class CONC is now effective part of
RIM we have to clear up of all R-
MIMs and texts.
Health Information Exchange Standards Messaging R2 datatypes Update all CP materials to R2
datatypes, current RIM, current
vocab, conduction control etc.
Clinical Content Specification Messaging Problem / Diagnosis
model
Problem / Diagnosis topic
Fit with concern model
Health Information
Exchange
Standards
Messaging Cared Entity CMET Care Structure Cared Entity
Health Information Exchange Standards Messaging Care Provision /
Encounter consistency
D-MIM level and R-MIMS
Care Coordination SOA Care Coordination
Joint with PI #Status Type (Normative,
ANSI/ISO)
Releases
None Normative -
Balloting Update of WG
Mission statement
and Charter
on Website PC
None Reviewed
Sept 2012
Update each
WGM Clearing up existing
materials of PC WG
This document
None Finished &
accepted in
Rio de Janeiro
May 2010
Reconfirmed
May 2011
None Draft finished
in Orlando
May 2011:
Vote Sept
2011
on Website PC 284Normative Normative HL7 CP, R1 July 2007
284Normative Normative HL7 CP, R1 July 2007
284
New number
to be
assigned
New project
scope
Normative Normative HL7 CP, R1 July 2007
284 New project
scope statement Different
topics DSTU - Test
Period till
2011
Core part of first
DSTU package Care
Provision
HL7 CP, R1 July 2007
284DSTU - Test
Period till
2011Core part of first
DSTU package Care
Provision
HL7 CP, R1 July 2007
651Informative -
Preparing for
Ballot Draft
Continuation of work
2009-2011
Draft 2007
174DSTU -
Reconcile
DSTU, R2, Sept 2009
666DSTU -
Reconcile
DSTU, Sept 2009
664DSTU -
Reconcile
DSTU, Jan 2009
284DSTU - Test
Period till
2011Core part of first
DSTU package Care
Provision
HL7 CP, R1 July 2007
320Publication of
n1 and n2
PSS required
PSS required on wiki a as
047
on wiki as 45 Needs PSS
Discuss with devices Check with clinical statement
Needs Discussion with other groups
Patient
Admin
Normative
PSS required
Summary
In minutes of Atlanta 2009 WGM
Has been reviewed in Sept 2011, no change required reviews Jan 2012, no change required
Sep-12 Accepted in WGM Sept 2011
Became normative in Sept 2012
Became normative in Sept 2012
Became normative in Sept 2012
Postpone untill after D-MIM and R-MIM ballot
Care Structures:
A_CareStatement(REPC_RM000100UV01)
A_ConcernList(REPC_RM000410UV01)
A_ConcernTracking(REPC_RM000300UV01)
A_ObservationVitalSigns(REPC_RM000130UV01)
A_StatementCollector(REPC_RM000400UV01)
R_CaredEntity(REPC_RM000700UV01)
Care Plan continue
Allergies & Intolerances continue
informative ballot Sept 2012 or Jan 2013
Reinstalled as action item, Kevin leading, and harmonizing with concern and concern tracker
This topic covers all interactions related to health concerns, including:
* Recording health concerns for a patient
Assessment Scales REPC_RM000125UV
Documentation etc ready and to move to publication
Needs a separate Topic as such from Care Structures Could be part of a larger Health Concern Topics
2012 decided to not move the remaining 3 DCM examples further. PC will create new PSS for methodology and design patterns
Existing materials, need to continue maintenance of it. Heading to a version 2.8 publication
ask MnM / TSC for guidance Needs to be published
Description (link)
includes electronic polling
The Care Structures Topic defines the many UML class diagrams, called Care Structures, which model the information pertinent to the ongoing provision of care. These are described as local CMET's which are local to the Care Provision Domain.
The Clinical Statement Pattern is renamed the Care Statement Structure in this Care Structure Topic
in order to emphasize that Care may apply to medical devices, facilities, and environmental sites as
well as patients. In that sense, the vocabulary used to support Care Statements is more extensive than
the vocabulary used to support simply the care of patients. These extensions will be documented by a
gradual increase in the number and variety of HL7 vocabulary value sets.
The intention is that a care statement instance may be added by itself to the Care Provision Act at
creation of the RMIM or added at run-time execution of an application in order to support the variability
of extent and detail described in the clinical statement definition above. Of course, the care statement
may be added to the Care Provision Act along with adding the other structures of the Care Provision The purpose of the care plan is: - To define the management action plans for the various conditions
identified for the target of care - To organize a plan and check for completion by all individual
professions - To communicate explicitly by documenting and planning actions and goals - To permit
the monitoring and flagging of unperformed activities and unmet goals for later follow up Generally a
care plan greatly aids the team in understanding and coordinating the actions that need to be
performed for the person.
Allergy and Intolerance observations are some of the most commonly recorded, reviewed and
transmitted information in the medical record. Clinicians record allergies and intolerances as a way to
remind themselves and other providers to avoid giving substances that are known to potentially cause
harm or discomfort to the patient. The process of identifying known adverse reactions and the believed
causes for them is a critical element of good clinical practice and is essential for safety and quality
(Nehta).
Knowledge and awareness of a patient's adverse reactions to agents/substances is essential for quality
of patient care and for patient safety. These adverse reactions can lead to the identification and
recording of one of two clinical concerns, namely: Allergy Concern, and Non-Allergy Intolerance
Concern. Allergy Concern An allergy is an acquired sensitivity to an agent/substance (allergen) that
causes the patient's immune system to 'hyper' react after exposure to that agent/substance. Non-
Allergy Intolerance A non-allergy intolerance indicates the potential for a response to an
agent/substance that is harmful or undesirable but is rarely life-threatening and is not mediated by the
Kevin will create a new 2012 PSS for this
The aim of this release is to provide a generic template based on the clinical statement pattern for use
with almost all scores systems and assessment scales. Therefore, it provides a framework for use in
messages and documents. This chapter is balloted as a first DSTU to collect comments from the
membership.
Kevin suggest making more relationships explicit. This can be handled as a change request.
Business Case (Intended Use, Customers)Benefits Implementations/
Case Studies
(Actual users)
Resources-Work
Groups
Resources-
Education
Provider: Healthcare Institutions (hospitals, long term care, home care, mental health)Patient Care Patient Care Patient Care Patient Care
Provider: Healthcare
Institutions (hospitals,
long term care, home
care, mental health)
Nictiz, Ontario, IHE Patient Care
Nictiz, Ontario, IHE Patient Care
Nictiz, Ontario, IHE Patient Care
Patient Care
Patient Care
Patient Care Patient Care
Patient Care Patient Care Patient Care Patient Care
Resources (Presentations)Relationship to/ Dependencies on other standards
RIM
HDF and other methodology Clinical Statement Pattern
Action needed
Done in Kyoto 2009
Revision May 2012
Review 2012 January
Review Sept 2014, or if needed
1. Update D-MIM with respect to class code change for Concern and Clinical Statement and R2 datatypes
2. Make text consistent with 1.
3. Revisit the informative texts for use cases and storyboards.
4. Work on the evaluation comments from approved 2010 evaluation
5. Break down in publishing components
6. Write and approve PSS in Sept 2011
7. Prepare for normative ballot early Nov 2011 for Jan 2012 ballot 7. Think of release policy around DIM, topics and new added items Update with concern class
Keep consistent with CS pattern
Normative January 2011
1. Update D-MIM with respect to class code change for Concern and Clinical Statement and R2 datatypes
2. Make text consistent with 1.
3. Revisit the informative texts for use cases and storyboards.
4. Work on the evaluation comments from approved 2010 evaluation
5. Break down in publishing components
6. Write and approve PSS in Sept 2011
7. Prepare for normative ballot early Nov 2011 for Jan 2012 ballot
7. Think of release policy around DIM, topics and new added items
8. Consider to de-abstract from message to a Transfer topic, Refer, admit, transfer, discharge?
1. remove now obsolete old assessment scale component
REPC_RM000120UV01
2. Include the new REPC_RM000125UV and narratives and dynamic model into NE 2012
3. Sort out figure formats and publishing formats.
Split each subject into a separate and manageable Topic Prepare PSS for each
Formalities for ballot
Prepare updates with R2 data types, CS, CONC
Deadline to DSTU ballot is Sept 2012
Normative is Sept 2013
2. Submit in Sept 2011 for DSTU extension approval for september??
3. Ballot normative Sept 2012
1. Sort out the materials, including Scope Statement, check with Canada
2. Submit to Don Lloyd
3. request to publish as DSTU NE 2011
4. Go to normative Sept 2012
1) Finish the work from the ballot resolution on the Assessment Scales topic and have it published as DSTU.
1. Sort out the materials
2. Submit to Don Lloyd
3. have published as DSTU.
To become a Topic on its own
Ongoing maintenance at this stage
Waiting for Registry to be opened Further discussions in Sept 2011 WGM