Difference between revisions of "Coordination of Care Services Specification Project"
Jfarmerwiki (talk | contribs) |
Jfarmerwiki (talk | contribs) |
||
| Line 21: | Line 21: | ||
==<span style="color:blue">Service Functional Model (SFM)</span>== | ==<span style="color:blue">Service Functional Model (SFM)</span>== | ||
| − | We are developing the Service Functional Model (SFM) text on Wiki pages | + | We are developing the Service Functional Model (SFM) text on Wiki pages. Most items are ready for review now as shown below. |
| + | |||
| + | * We can receive and apply content changes to any or all items up until Midnight Friday. | ||
| + | * From that point on, we wish to receive only wordsmithing improvements and only by email to both of us (the wiki posts will be obsolete). | ||
| + | |||
| + | If your edits are wordsmithing, then please feel free to edit directly, but if you would like changes to content, please send your thoughts to Jon Farmer <jon.farmer@thrasys.com> or Enrique Meneses <enrique@careflow.com>. For each item see the initials to know to whom you should send edits (if not editing directly). | ||
Status: | Status: | ||
| − | |||
Items written and posted ready now for your review! | Items written and posted ready now for your review! | ||
Revision as of 18:35, 14 March 2013
Contents
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, 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.
Status
- 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. Most items are ready for review now as shown below.
- We can receive and apply content changes to any or all items up until Midnight Friday.
- From that point on, we wish to receive only wordsmithing improvements and only by email to both of us (the wiki posts will be obsolete).
If your edits are wordsmithing, then please feel free to edit directly, but if you would like changes to content, please send your thoughts to Jon Farmer <jon.farmer@thrasys.com> or Enrique Meneses <enrique@careflow.com>. For each item see the initials to know to whom you should send edits (if not editing directly).
Status:
Items written and posted ready now for your review!
- JF - How SFM will refer to users
- JF - Business Scenarios
- JF - Functional profiles (needs wordsmithing - be our guest)
- JF - File:CCS SFM 2013 03 13 Functional scope - Reason why needed - Rationale for creating the spec - Vendor Viewpont.doc
- EM - Why rejecting BPM and Deferring OMG CMMN
Items already posted but still to receive some new content
- EM - Business Capabilities (Targeting Friday Noon US EDT)
Still to be posted:
- JF - Cross reference of functional profiles against EHR SFM requirements relating to care plans (Targeting Thursday 4:30 US EDT)
- EM - Section 4 summary of service interfaces (targeting Friday Noon US EDT)
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
- Enrique Meneses, Healthcare Solutions Architect, Careflow Solutions
- Jon Farmer, Product Manager, Thrasys
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 |
https://meetings.webex.com/collabs/#/meetings/detail?uuid=M4T1NA5U0J86NDDWK7B6L0034Q-3MNZ |
|
Meeting Number |
195 053 369 |
|
USA Call-in number |
770-657-9270 |
|
Participant access code |
071 582 |
Issues/Hot Topics
- CCS issues tracking at GForge repository.
