Difference between revisions of "Patient Care Coordination"

From IHE Wiki
Jump to navigation Jump to search
Line 36: Line 36:
 
====* [[ITI,_PCC_%26_QRPH_Meetings|ITI, PCC & QRPH Development Cycle Meetings]]====
 
====* [[ITI,_PCC_%26_QRPH_Meetings|ITI, PCC & QRPH Development Cycle Meetings]]====
  
== Committee Activities for 2014-2015 Cycle ==
+
== Committee Activities for 2015-2016 Cycle ==
  
 
=== Current Work ===
 
=== Current Work ===
  
  
* '''Remote Patient Monitoring (RPM)''' Describes a set of standardized means to deliver patient health measurements and monitoring data in a remote setting to a health care provider. This is a joint effort between the Patient Care Device (PCD) and PCC domains.
+
* '''Dynamic Care Planning (DCP)'''
 
+
* '''Bed Management Profile (BED)'''
* '''Clinical Mapping (CMAP)''' supports the needs of systems to translate codes from one terminology to another to support exchange of information between different systems. This is a joint effort between the Patient Care Device (PCD) and PCC domains.
+
* '''Cross Enterprise Cardiovascular Heart Team Workflow Definition (XCHT-WD)'''
 
 
* '''Guideline Appropriate Ordering (GAO)''' supports use cases where the use of CDS to evaluate an order for appropriateness to guidelines must be demonstrated and communicated in an order.
 
 
 
* '''RECON on FHIR''' This is an addition to the RECON profile to include FHIR as a standard to implement against.
 
 
 
* '''Workflow Definition''' This is an appendix to the technical framework, providing specific guidance and tool usage to implement workflow profiles utilizing the BPMN standard.
 
 
 
* '''Data Access Framework (DAF)''' This is a US national extension to the PCC Technical Framework, providing specific guidance as required by the US ONC.
 
  
 
== Committee Activities in Prior Years ==
 
== Committee Activities in Prior Years ==

Revision as of 14:05, 2 August 2016

IHE Patient Care Coordination (PCC) domain was established in July 2005 to deal with integration issues that cross providers, patient problems or time. It deals with general clinical care aspects such as document exchange, order processing, and coordination with other specialty domains. PCC also addresses workflows that are common to multiple specialty areas and the integration needs of specialty areas that do not have a separate domain within IHE.

PCC Vision

The vision of Patient Care Coordination is to continually improve patient outcomes through the use of technology connecting patients and their care providers across healthcare disciplines and care paths.

PCC Mission

The mission of Patient Care Coordination is to develop and maintain interoperability profiles to support coordination of care for patients where care crosses providers, patient conditions and health concerns, or time.


The Patient Care Coordination Domain is sponsored by:

HIMSS the Health Information Management Systems Society
ACP the American College of Physicians
Quick Links

Upcoming Events

A schedule of upcoming PCC activities can be found here

* Domain News Announcements

* ITI, PCC & QRPH Development Cycle Meetings

Committee Activities for 2015-2016 Cycle

Current Work

  • Dynamic Care Planning (DCP)
  • Bed Management Profile (BED)
  • Cross Enterprise Cardiovascular Heart Team Workflow Definition (XCHT-WD)

Committee Activities in Prior Years

Participation

As a Clinician / Patient Advocate

Get involved in the planning committee. This is where the clinical problems are discussed and prioritized. The planning committee is an open group and is interested in having your input! Bring us your interoperability problems! You can also help by participating in the himss showcase scenario definitions.

You can do this by:

  1. Send us a note at ihe@himss.org saying you’re interested so we can get you on the list-serves.
  2. Come to face to face meetings, and attend the telephone conferences.
  3. Submit your profile proposals by:
    • Fill out this PCC Profile Proposal Template.
    • Submit the propsal draft to us.
    • Attend the October planning meeting to help clarify and prioritize your proposal
    • Follow up by submitting a formal proposal
    • Attend the joint planning/technical meeting to explain your idea to the technical committee
    • Any additional resources you can provide toward the problem will help prioritize getting your proposal solidified more quickly.

As a Hospital Administrator

In addition to getting involved in the planning committee, hold your vendor accountable. Put a statement in your rfp that indicates you want the vendor to support the actor in the profile you desire.

As an Implementer

Get involved in the Technical Committee. Help make sure profiles are feasible and will work for you. Implement the profile, and come experience the Connectathon - send us a note at ihe@himss.org saying you’re interested so we can get you on the list-serves.

Demonstrations & Presentations

Date Location Event Details
2010 Atlanta, GA HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2009 Burlington, VT Vermont Information Technology Leaders Vermont Infomation Technology Leaders (VITL) Summit
2009 Atlanta, GA Public Health Information Network Public Health Information Network (PHIN) Conference
2009 Chicago, IL HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2008 Atlanta, GA Public Health Information Network Public Health Information Network (PHIN) Conference
2008 Orlando, FL HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2007.02.25-2006-03.01 New Orleans, LA HIMSS Interoperability Showcase HIMSS Interoperability Showcase

See Also

This page is based on the Domain Template.