Difference between revisions of "Care Coordination Capabilities"
| Line 131: | Line 131: | ||
=<span style="color:blue">Care Planning - Plan Life Cycle Capability Set</span>= | =<span style="color:blue">Care Planning - Plan Life Cycle Capability Set</span>= | ||
| − | ==Establish Plan== | + | ==Establish Plan Capability == |
| − | ==Revise Plan== | + | ==Revise Plan Capability == |
| − | ==Retire Plan== | + | ==Retire Plan Capability == |
=<span style="color:blue">Care Planning - </span>= | =<span style="color:blue">Care Planning - </span>= | ||
Revision as of 21:07, 26 February 2013
Contents
- 1 Capabilities
- 2 Care Collaboration - Build "Social" Network Capability Set
- 3 Care Collaboration - Team Conversation Capability Set
- 4 Care Collaboration - Participant Availability Capability Set
- 5 Care Collaboration - Semantic Tagging Capability
- 6 Care Observations and Assessment Capability Set
- 7 Care Planning - Plan Life Cycle Capability Set
- 8 Care Planning -
- 9 Care Plan Implementation Capability Set
- 10 Care Review Capability Set
- 11 Template for Capability Details
Capabilities
Capabilities express "abilit[ies] that an organization, person or system possesses" [1]. Capabilities are independent of business process and they express the "what" rather than the "how".
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 what services in technology X will need to perform.
Capabilities may be aggregated into logical groupings which may map to interfaces but they will simply be represented here as logical capability sets.
The Care Coordination capabilities comprise the core of the normative content specified in by the CCS HSSP Service Functional Model 2.
Care Collaboration - Build "Social" Network Capability Set
Invite to Collaborate
Respond to Collaboration Invitation
Find All Collaboration Participants
Care Collaboration - Team Conversation Capability Set
Care Team Chat Communications
Invite New Conversation Participants
Respond to Conversation Invitation
Find All Conversation Participants
Care Collaboration - Participant Availability Capability Set
Indicate Personal Availability for Collaboration
Find Participant Availability for Collaboration
Care Collaboration - Semantic Tagging Capability
Tag Collaborative Content
Care Observations and Assessment Capability Set
Capture Subjective and Objective Patient Observations
|
Capability Status |
2-26-2012 |
Proposed |
Reviewers Here |
|
Description |
|
|
Precondition |
|
|
Inputs |
|
|
Outputs |
|
|
Postconditions |
|
|
Business Exception Conditions |
|
|
Relationship to Levels of Conformance (or Other Patterns) |
|
|
Aspects Left to OMG to Specify |
|
|
Notes |
|
|
Outstanding Issues |
|
Capture Causative or Interpretative Observation Links
Replace Prior Observations
Specify Assessment Scales to Guide Observation Process
Care Planning - Plan Life Cycle Capability Set
Establish Plan Capability
Revise Plan Capability
Retire Plan Capability
Care Planning -
Care Plan Implementation Capability Set
Care Review Capability Set
Acceptance Review Capability
Activity Outcome Review Capability
Goal Review Capability
Plan Review Capability
Template for Capability Details
Please copy and paste the following wiki markup when adding 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 |
|
Precondition |
[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. |
|
Business Exception Conditions |
[Mandatory] Business Exception Conditions [may be null] |
|
Relationship to Levels of Conformance (or Other Patterns) |
[Optional] Relationship to levels of conformance (or other patterns)
|
|
Aspects Left to OMG to Specify |
Enumeration of aspects left to the technical specification [may be null]
|
|
Notes |
|
|
Outstanding Issues |
|
