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 48: Line 48:
  
 
==Issues/Hot Topics==
 
==Issues/Hot Topics==
 +
<!--
 
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])
 
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])
 
+
-->
 +
* Our issues tracking [http://gforge.hl7.org/gf/project/ GForge] repository.
  
 
==Project Documents==
 
==Project Documents==

Revision as of 00:24, 19 November 2012

Project Information

Overiew

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, coauthoring plan elements as the team observes. 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 care plan actions.

Project Facilitators

  • Enrique Meneses, Healthcare Solutions Architect, Careflow Solutions
  • Jon Farmer, Product Manager, Thrays


Project Scope Statement

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

Related Discussions Listserv

Please join the discussion at the listsev for our co-sponsors:

Manage your listserv subscriptions here.

Meeting Information TBD

Status

  • The current effort is to advance both the Care Plan Domain Analysis Model (DAM) and the CSS operation set.
  • Current effort occurring as part of Patient Care bi-weekly Care Plan modeling meetings
  • Soliciting input on weekly day/times for SOA services specification meeting Doodle Poll here


Issues/Hot Topics

  • Our issues tracking GForge repository.

Project Documents


Categorization