This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Coordination of Care Services Specification Project"

From HL7Wiki
Jump to navigation Jump to search
Line 25: Line 25:
* [ Business Scenarios]
* [ Business Scenarios]
* [ Business Capabilities]
* [ Business Capabilities]
* [ Functional profiles (to be reworked based on the capabilities list)]
* [ Functional profiles (needs wordsmithing - be our guest)]
* Please also reiew Functional scope, Reason why service is needed, Rationale for creating the specification, and Vendor_Viewpoint
* [[File:CCS_SFM_2013_03_13_Functional_scope_-_Reason_why_needed_-_Rationale_for_creating_the_spec_-_Vendor_Viewpont.doc]]  
* [ Why rejecting BPM and Deferring OMG CMMN]
* [ Why rejecting BPM and Deferring OMG CMMN]

Revision as of 17:13, 14 March 2013

Project Information


The Care Coordination service is a standards development/specification effort being undertaken by HL7 to be followed by SOA specification work at the OMG. This project falls under the Healthcare Services Specification Program (HSSP) and will be done in collaboration with the HL7 Patient Care and HL7 Clinical Decision Support work groups.

The objective is to provide SOA capabilities to support patient care coordination across the continuum. The viewpoint of these capabilities is the patient as he or she crosses care settings and interacts with care givers with different focus and specialties. The context is episodes of care spanning multiple organizations, the interactions at the boundaries of care transitions, and the subset of information necessary and sufficient to support these interactions.

The CCS will support shared and coordinated care plans. The CCS will support multidisciplinary care team members to communicate changes resulting from care plan interventions and collaborate in removing barriers to care. The CCS will provide on demand synchronization of information to keep the virtual care team on the same page and prevent having the patient fall through the cracks of the silos of care.

Care Team members will collaborate around these shared plans, each contributing or reviewing items as local procedures and policies may dicate. Structurally, the shared Care Plan will serve to coordinate specialty care plans, and will have the ability to seamlessly navigate to them without requiring physical centralization of data storage.

Automated Clinical Decision Support systems will be first class participants in proposing and evaluating care plan actions.


  • Currently defining Care Coordination Service (CCS) Functional Model (SFM) <== we are here
    • Initial draft planned for March 17th, 2013
  • CCS SFM Comments ballot for May, 2013
  • CCS SFM DSTU ballot September 2013
  • OMG technical specification work - 2014

Service Functional Model (SFM)

We are developing the Service Functional Model (SFM) text on Wiki pages - we invite your participation:

Domain Model Dependencies

The Care Coordination Service SFM is defined in terms of models from the HL7 Patient Care workgroup. Of special importance is the care plan initiative which is defining a model to support collaborative care planning Care Plan Initiative Project. As a rule CCS will leverage standard domain models and not define new domain semantic content. The following power point provides an overview of the Care Plan domain analysis model.

Project Facilitators

Project Scope Statement

Link to project scope statement and details from Project Insight Searchable Database

Related Discussions Listserv

Manage your listserv subscriptions here.

Read Listserv Messages

Sign up here:

Complementary Efforts

Meeting Information

Weekly Meeting Time: Every Tuesday at 5 PM US ET

**Meeting date/time poll (closed)

Meeting URL

Meeting Number

195 053 369

USA Call-in number


Participant access code

071 582

Issues/Hot Topics

  • CCS issues tracking at GForge repository.

Project Documents