Difference between revisions of "Care Coordination Capabilities"
Jfarmerwiki (talk | contribs) |
Jfarmerwiki (talk | contribs) |
||
Line 1,477: | Line 1,477: | ||
=<span style="color:blue">Cross-Plan Reconciliation Capability Set</span>= | =<span style="color:blue">Cross-Plan Reconciliation Capability Set</span>= | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==<span style="color:blue">Detect Redundancy Capability</span>== | ==<span style="color:blue">Detect Redundancy Capability</span>== | ||
{| class="wikitable" | {| class="wikitable" |
Revision as of 22:15, 28 February 2013
Contents
- 1 Business Purpose of the Specification
- 2 Business Capabilities
- 3 Care Collaboration - Build "Social" Network Capability Set
- 4 Care Collaboration - Team Conversation Capability Set
- 5 Care Collaboration - Participant Availability Capability Set
- 6 Care Collaboration - Semantic Tagging Capability
- 7 Care Observations and Assessment Capability Set
- 8 Care Planning - Plan Life Cycle Capability Set
- 9 Clinical Evaluation of Plan Items
- 10 Recommend Plan Template Capability
- 11 Care Plan Implementation Capability Set
- 12 Care Review Capability Set
- 13 Cross-Plan Reconciliation Capability Set
- 14 Documentation Template for Capability Details
Business Purpose of the Specification
Presently in the Health Care industry, a patient may be under concurrent treatment by a variety of physicians and specialists, and each of these maintains a “plan” that suits their perspectives, purposes, and time horizons. Without mechanism to positively coordinate these plans, gaps and overlaps emerge, leading to compromised quality and efficiency of care. These stakes are especially high in cases of chronic conditions (or multiple chronic conditions, such as Diabetes plus Cardiovascular disease).
The purpose of the HSSP Care Coordination Service (CCS) is to support collaborative planning and execution of operational health care around a “coordinating” care plan that is live and shared among a multi-disciplinary care team. The care team may be dynamically managed to consist of members from either the same or different organizations (e.g. primary care clinic, home care, allied health professionals, hospital, skilled nursing facility, etc.)
There exist standards from HL7 and IHE by which specialty or episodic “plans of care” may be replicated as CDA documents or sections therein, but there is no standard structure or service that unifies them or directly supports the actual reconciliation, consolidation, and true “sharing” of the “cleaned-up” or reorganized plan.
As regards this sharing, the CCS will allow changes made or proposed by one participant to be immediately viewable by all, and will even support concurrent editing by multiple authors. With that foundation, the CCS allows a primary provider (for example) to raise a controlled discussion around a specified topic or for the case as a whole. Even a Clinical Decision Support System may participate as a first-class team member, contributing to discussions or raising new discussions.
The CCS should allow for greatly increased manageability of care plans than we now see in practice.
Business Capabilities
What are capabilities
Capabilities express "abilit[ies] that an organization, person or system possesses" [1]. Capabilities are independent of business process and business rules; capabilities express the "what" rather than the "how".
Business capabilities may outlive specific technical specifications or implementations that realize business processes. They may be represented in HL7 V2, V3 or V10 but they will endure and continue to represent what the business does and describe what services in technology X will need to perform.
The Care Coordination Service (CCS) capabilities comprise the core of the normative content specified by the HL7 SOA CCS Service Functional Model (SFM) as specified in the Health Services Specification Program (HSSP).
Capabilities may naturally fall into logical groupings which we'll also represent as UML interfaces in the informative part of the HL7 SOA SFM.
As a general rule the capabilities are independent from organizational policies and business rules. This decoupling will allow the CCS capabilities to be combined to support various business processes and organizational policies. This is key for realizing care coordination services through the continuum of care.
The road ahead:
- May 2013 - Complete HL7 comments only draft
- September 2013 - Complete draft standard for trial use (HL7 DSTU)for CCS service functional model
- 2014 - OMG technical specification work
The Problem
CCS Solution Overview
Complementary Efforts
Care Collaboration - Build "Social" Network Capability Set
Invite to Collaboration Participants
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
An invitation is a request from one individual to another to participate as collaborators in care coordination activities. Participants join the the Care Team via an invitation based process which helps to organically grow the patient's care network just as it does in the "real world".
- A patient can directly invite providers and care givers to join his or her care team (as the patient is the first member of the care team).
- An invitations may be sent from an any existing care team participant to new care team member.
- The patient's delegated steward of their care plan, licensed independent practitioner (LIP) (e.g. PCP or other professional care plan facilitators such as a nurse case manager) will typically serve as the "seed" of the collaboration tree as they invite other providers to collaborate in care coordination.
Policies and rules regarding who is entitled to receive invitations and receive access to collaborate on patient care will continue to be dictated by existing processes (e.g. policies that allow a provider to fax clinical information to a specialist or have a phone conversation about my health conditions).
Precondition |
The invitation placer must be an existing member of the patient's care team. This may include the following roles as defined in the HL7 Care Plan model:
|
Inputs |
|
Outputs |
none |
Postconditions |
New collaborator receives a secure message with request for collaboration |
Exception Conditions |
New collaborator not vetted by external policy checks |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Respond to Collaboration Invitation
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
A collaboration invitation recipient may respond as follows:
- Accept request for collaboration
- Delegate request for collaboration to another participant
- Reject request for collaboration
Preconditions |
Collaboration invitation has been initiated by an activated member of the care team and received in the form of a secure message containing a unique invitation token. |
Inputs |
|
Outputs |
none |
Postconditions |
Invited participant becomes a new member of the care team with access to patient care context. |
Exception Conditions |
|
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Find All Collaboration Participant Relationships
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
Collaboration participant relationships represent a mini-community of individuals working towards the patient's health goals. The relationships are a network or social graph used to support collaboration in care coordination activities. This capability supports awareness of the patient's circle of care and the relationships between individuals.
These relationships grow organically as the care team sends invitations to collaborate on care coordination activities. For example, an invitation from a licensed independent practitioner (LIP) to a cardiologist results in two new relationship links from the new provider to the patient and between the existing and new providers.
Preconditions |
none |
Inputs |
Patient role and Person information |
Outputs |
Persons, the roles they are playing and links based on their role relationships. |
Postconditions |
none |
Exception Conditions |
none |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Collaboration - Team Conversation Capability Set
Care Team Chat Conversation Thread
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
Conversation is the heart of collaboration. Any member of the care team may initiate a conversation with a different member of the care team at any time. By default the conversation is private to the participants involved. Organizational policies and business rules engines may determine if a conversation is visible beyond the direct participants (as a principle CCS delegates to external policy checks).
The CCS conversation model captures both the free form text content of business interactions but it can also link to the semantic structured context pertaining to the conversation.
A conversation may simply consist of free text such as a questions from a patient to his or her provider. A conversation may also pertain to a some aspect of the care plan such as: a communication about a specific health goal, health concern, health risk, intervention outcome, associated plan and goal reviews or some diagnostic observation about the patient. The semantic links put the conversation in context.
Conversations will naturally form threads containing multiple communications about some topic.
Care team communications may also have optional multimedia support (attached photograph of video clip)
Preconditions |
The receiving individual is in an active care team member for the associated patient. |
Inputs |
|
Outputs |
none |
Postconditions |
none |
Exception Conditions |
none |
Included in Profiles |
edit here |
Outstanding Issues |
|
Invite New Conversation Participants
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
An invitation may be sent by a conversation participant to a member who was not involved in the original thread. The invitation enables the new participant to follow the existing conversation thread and also respond to specific communication entries.
Preconditions |
|
Inputs |
|
Outputs |
none |
Postconditions |
New collaborator receives a secure message with request to join existing conversation |
Exception Conditions |
none |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Respond to Conversation Invitation
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
A conversation invitation recipient may respond as follows:
- Accept to join conversation
- Delegate conversation request
- Reject conversation request
Preconditions |
There is a pending invitation to join a conversation |
Inputs |
|
Outputs |
none |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Find All Conversation Participants
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
This capability identifies participants involved in a specific conversation thread.
Preconditions |
none |
Inputs |
Patient role and Person information |
Outputs |
Persons, the roles they are playing and links based on their role relationships. |
Postconditions |
none |
Exception Conditions |
none |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Collaboration - Participant Availability Capability Set
Indicate Personal Availability for Collaboration
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Find Participant Availability for Collaboration
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Collaboration - Semantic Tagging Capability
Tag Collaborative Content
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Observations and Assessment Capability Set
Capture Subjective and Objective Patient Observations
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Capture Causative or Interpretative Observation Links
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Replace Prior Observations
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Specify Assessment Scales to Guide Observation Process
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Planning - Plan Life Cycle Capability Set
Establish Plan Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Revise Plan Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Retire Plan Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Clinical Evaluation of Plan Items
Check Clinical Appropriateness Capability
Given a health concerns, goals and risks and existing plan actions are the interventions appropriate
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Recommend Plan Template Capability
Given a health concerns, goals and risks and barriers recommend a Plan template
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Plan Implementation Capability Set
Track Execution Status Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Request Resource Allocation Capability
- Human Resources, Rooms, and Materials
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Request Service Allocation Capability
Assign Resource Capability
- Human Resources, Rooms, and Materials
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Care Review Capability Set
Acceptance Review Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Activity Outcome Review Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Goal Review Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Plan Review Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
<<Insert Capability Description Here>>
Preconditions |
edit here |
Inputs |
edit here |
Outputs |
edit here |
Postconditions |
edit here |
Exception Conditions |
edit here |
Included in Profiles |
edit here |
Outstanding Issues |
edit here |
Cross-Plan Reconciliation Capability Set
Detect Redundancy Capability
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
Given a set of plans or plan items, report items suspected as being redundant. The plans or plan items of concern could be at different levels or at the same level. For example, two "plans of care" are including medication for the same period for the same condition. As another example, a "care plan" and a "plan of care" show the same type of redundancy, but the POC has not been included under the CP.
Inputs |
Selections of the content to be considered (plan items or entire plans) |
|
Outputs |
Zero or more Sets of PlanItems that are suspected as being redundant. | |
Postconditions |
A record of these results is posted so that they be collaboratively reviewed. (Issue - should results be kept available through the CCS? or should they be posted as communicaton on a topic?) | |
Exception Conditions |
edit here | |
Included in Profiles |
edit here | |
Outstanding Issues |
edit here |
Documentation Template for Capability Details
The following template captures the level of detail required for the HL7 SOA HSSP Service Functional Model specification. The details make up section 5 of of the SFM boiler plate template which captures the "Detailed Functional Model for each Interface".
Please include at a minimum the mandatory fields when describing new capabilities.
Capability Status |
2-26-2012 |
Proposed |
Link of reviewers doodle poll when approved |
Name |
[Mandatory] A business-friendly name describing the context of the motivating scenario, and is unique within this Functional Model (e.g., “Find a Person” vs. FindPerson)
|
Description |
[Mandatory] High-level [functional] description of the expected behavior
|
Preconditions |
[Mandatory] Business Pre-conditions [may be null], i.e. what conditions must have been satisfied before the action can be requested or carried out |
Inputs |
[Mandatory] Inputs [include both mandatory and optional] |
Outputs |
[Mandatory] Outputs [include both mandatory and optional] |
Postconditions |
[Optional] Business Post-conditions, i.e. what conditions will result from the action being carried out. |
Exception Conditions |
[Mandatory] Business Exception Conditions [may be null] |
Part of Profiles |
[Optional] Specify service functional profiles which include the capability. Please specify if it is required or optional for profile conformance.
|
Aspects Left to OMG to Specify |
[Optional] Enumeration of aspects left to the technical specification [may be null] |
Outstanding Issues |
[Optional]If no issues but expect some while the capability is being worked out by the team |