Difference between revisions of "Care Coordination Capabilities"
| Line 49: | Line 49: | ||
| | | | ||
<nowiki>[</nowiki>'''Mandatory] '''<nowiki>Outputs [include both mandatory and optional]</nowiki> | <nowiki>[</nowiki>'''Mandatory] '''<nowiki>Outputs [include both mandatory and optional]</nowiki> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
Revision as of 18:53, 26 February 2013
Contents
Care Collaboration
Care Observations
Care Planning
Care Plan Implementation
Care Plan Review
Template for Capability Details
Please copy and paste the following wiki markup when adding new capabilities.
|
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. |
|
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 the Implementer |
|
|
Aspects Left to OMG to Specify |
Enumeration of aspects left to the technical specification [may be null]
|
|
Miscellaneous Notes |
|
|
Outstanding Issues |
|
