This wiki has undergone a migration to Confluence found Here

Care Plan Topic project

From HL7Wiki
Jump to navigation Jump to search


Care Plan has been balloted some years ago as DSTU. However, it was felt at that time that more work needed to be done in defining care plan, the components of the care plan, identifying use cases and use. The plan for 2010 is to complete the contents of Care Plan.

HL7 PC will work together with: HL7 Structured Documents WG IMIA-NI IHE For the content of this DSTU material.

Project Need

Items about Care Planning to be discussed towards a future round of DSTU include:

  • Existing RMIM: does it cover all kinds of care plans and pathways.
  • Definition of care plan
  • The overall structure that has been agreed: Care Plan -> Order set -> Clinical Statement. Discussion about this hierarchy is done in PC, O&O and CDS WG.

Project Scope

The Care Plan Topic is one of the roll outs of the Care Provision Domain Message Information Model (D-MIM). The Care Plan is a specification of the Care Statement with a focus on defined Acts in a guideline, and their transformation towards an individualized plan of care in which the selected Acts are added. The purpose of the care plan as defined upon acceptance of the DSTU materials in 2007 is: - To define the management action plans for the various conditions (for example problems, diagnosis, health concerns)identified for the target of care - To organize a plan for care and check for completion by all individual professions and/or (responsible parties (including the patient, caregiver or family) for decision making, communication, and continuity and coordination) - To communicate explicitly by documenting and planning actions and goals - To permit the monitoring, and flagging, evaluating and feedback of the status of goals, actions, and outcomes such as completed, or unperformed activities and unmet goals and/or unmet outcomes for later follow up. - Managing the risk related to effectuating the care plan, Generally a care plan greatly aids the team (responsible parties – it could be the patient caregiver/family) in understanding and coordinating the actions that need to be performed for the person. The Care Plan structure is used to define the management action plans for the various conditions identified for the target of care. It is the structure in which the care planning for all individual professions or for groups of professionals can be organized, planned and checked for completion. Communicating explicitly documented and planned actions and goals greatly aids the team in understanding and coordinating the actions that need to be performed for the person. Care plans also permit the monitoring and flagging of unperformed activities and unmet goals for later follow up.

Project Team

Primary Sponsor/Work Group is Patient Care WG

Co-sponsor Work Group(s) is Structured Documents WG

Role Name Email Notes
Project facilitator Rosemary Kennedy
Other interested parties IMIA-NI and IHE
Publishing facilitator Jean Duteau
Vocabulary facilitator Susan Matney
Modeling facilitator Jean Duteau
Domain expert representative 1 Rosemary Kennedy
Domain expert representative 2 Anneke Goossen
Data Analyst facilitator Gay Gianone
Business requirement analyst Rosemary Kennedy
Requirements process facilitator
Business requirement analyst
Requirements process facilitator Frank Oemig
Implementor Ewout Kramer

Action items

Action Description Timeline Status
Conceptuel, contextual and structural definitions of Care Plan Informative ballot january 2011 In progress.
Definitions for each part of the care plan The parts must be consistent with the structural definition of care plan Informative ballot january 2011 In progress.

Remark: The actions came from the project scope statement, but must be reviewd by William Goossen as a co-chair of Patient Care.

Project Process

  • Teleconferences on Wednesday at 4 pm Eastern time.
  • Using Tooling's telecon. Will be announced via the Patient Care mailing list.
  • Standing Agenda Items
    • Review of project plan and action items
    • Opportunity to ask questions and answers

Project Objectives and Deliverables

1. Domain analysis Model with the following deliverables (together with SD WG):

    • Definitions of Care Plan and others.
    • Work on storyboards and use cases (multiple). Emergency, Clinical hospital (discharge), Nursing home, chronic disease, primary care. Multidisciplinary. Example use cases can be: 1 chronic condition, obstetric case with transfer. After that CDA can use the work that is be done. CDS is an addition to the messages which already exist. They must be updated.
    • Dynamic model for the Care Plan Topic
    • Structural model. -> DAM (HDF within HL7)

2. R-MIM update, meeting all care plan and pathway requirements (PC WG only)

3. CDA for discharge of a nursing care plan (joint PC, SD and IHE), including a robust set of examples.

4. Work on relationship of care plan with ordering, verifying and reporting of orders

Success Criteria

Clear definitions of Care Plan and components, harmonized with CEN Contsys standard, the risk management standards, IHE profiling and IMIA NI project work. Use cases and storyboards updated Proper description how the care plan and pathways can be mapped to the Care Plan R-MIM Update of the R-MIM, if necessary to accommodate the use cases

Project Timeline

Work will be done during 2010 en 2011. Accepted as DSTU end of 2011

Project Resources

Most will be done in normal committee work time, and online via meetings, where all contributors have their normal responsibilities to develop DCM for their day job / clients / projects.

Project Budget

There will be a budget necessary for the HL7 repository

=Ballot strategy - general||

Revision of existing DSTU materials, inclusion of new scales into ballot and ongoing maintenance and new materials. Future normative will probably only possible if HL7 at large has established a repository of templates / R-MIMs.

Links to relevant documents

Templates Registry Pilot


DCM Users

DCM Annonators

DCM Liasons

DCM Developer

DCM Contributors

Collaborating with Agreement status Comments
CEN Existing
ISO Existing
OpenEHR Unknown Informal agreement on this work

Sub Projects