Difference between revisions of "Patient Care Coordination"

From IHE Wiki
Jump to navigation Jump to search
(25 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
|}
 
|}
 
'''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.
 
'''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:
 
The Patient Care Coordination Domain is sponsored by:
Line 15: Line 22:
 
* [[Patient Care Coordination Technical Framework| PCC Technical Framework]]
 
* [[Patient Care Coordination Technical Framework| PCC Technical Framework]]
 
* [[Nursing Subcommittee Proposal]]
 
* [[Nursing Subcommittee Proposal]]
* [[PCC Roadmap | Roadmap]]
+
* [[PCC Roadmap | Roadmap and Strategic Goals]]
 
* [[PCC Development Timeline | Development Timeline]]
 
* [[PCC Development Timeline | Development Timeline]]
 
* [[PCC Change Proposals | Change Proposals]]
 
* [[PCC Change Proposals | Change Proposals]]
 
** [[PCC_Change_Proposal_Tracking | CP Tracking]]
 
** [[PCC_Change_Proposal_Tracking | CP Tracking]]
* [http://www3.rsna.org/calendar/index.cfm?ACTION=PRINTGROUP&start_date={ts%20'2007-12-01%2000:00:00'}&end_date={ts%20'2009-10-09%2023:59:59'}&mg_id=1&GroupCntr=0,108 RSNA Calendar]
 
 
* [[PCC Face to Face Agendas and Minutes]]
 
* [[PCC Face to Face Agendas and Minutes]]
 
* [[PCC_HowToUploadToFtpSite | How to use the FTP site]]
 
* [[PCC_HowToUploadToFtpSite | How to use the FTP site]]
Line 25: Line 31:
  
 
== Upcoming Events ==
 
== Upcoming Events ==
A detailed event calendar for the IT Infrastructure Committees can be found [http://www.ihe.net/calendar/|on the master IHE.net calendar.]
+
A schedule of upcoming PCC activities can be found [http://wiki.ihe.net/index.php?title=ITI,_PCC_%26_QRPH_Meetings here]
  
 
====*  [[Domain_News_Announcements|Domain News Announcements]]====
 
====*  [[Domain_News_Announcements|Domain News Announcements]]====
 
====* [[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 2010-2011 Cycle ==
+
== Committee Activities for 2017-2018 Cycle ==
 +
 
 +
=== Current Work ===
  
=== Important Dates ===
 
* Feb 1st-4th, 2010: Tech Committee face to face - Review completion of Volume 1 work
 
* Apr 26th-29th, 2010: Tech Committee face to face - Review completion of Volume 2 work, publish for Public Comment
 
* June 1st-July 1st, 2010: Public comment period
 
* July 12th-July 15th, 2010: Tech Committee face to face - Review public comments, publish for Trial Implementation
 
  
=== Current Profile Work ===
+
* '''[[Care Team Management]]'''
* Nursing e-Summary (Nursing Subcommittee)
+
* '''[[Patient Registration Content]]'''
* Newborn Discharge Summary (NDS)
+
* '''[[Discharge to EMS Transport]]'''
* Postpartum Visit Summary (PPVS)
+
* '''[[Patient Centric Data Element Location Services (QED on FHIR)]]'''
* Antepartum Record (APR)/Labor and Delivery Record (LDR) (continuation of work from previous years
+
* '''[[360x Closed Loop Referral]]'''
* Patient Centered Coordination Plan (PCCP)
+
* '''[[Point of Care Medical Device Tracking]]'''
 +
* '''[[Remote Patient Monitoring (RPM) Update]]'''
  
 
== Committee Activities in Prior Years ==
 
== Committee Activities in Prior Years ==
 +
* [[PCC Committee Activities in 2016-2017]]
 +
* [[PCC Committee Activities in 2015-2016]]
 +
* [[PCC Committee Activities in 2014-2015]]
 +
* [[PCC Committee Activities in 2013-2014]]
 +
* [[PCC Committee Activities in 2012-2013]]
 +
* [[PCC Committee Activities in 2011-2012]]
 +
* [[PCC Committee Activities in 2010-2011]]
 
* [[PCC Committee Activities in 2009-2010]]
 
* [[PCC Committee Activities in 2009-2010]]
 
* [[PCC Committee Activities in 2008-2009]]
 
* [[PCC Committee Activities in 2008-2009]]
Line 80: Line 91:
 
! Event
 
! Event
 
! Details
 
! Details
 +
|-
 +
| 2016
 +
| Las Vegas, NV
 +
| [http://www.interoperabilityshowcase.org HIMSS Interoperability Showcase]
 +
| HIMSS Interoperability Showcase
 +
|-
 +
| 2015
 +
| Chicago, IL
 +
| [http://www.interoperabilityshowcase.org HIMSS Interoperability Showcase]
 +
| HIMSS Interoperability Showcase
 +
|-
 +
| 2014
 +
| Orlando, FL
 +
| [http://www.interoperabilityshowcase.org HIMSS Interoperability Showcase]
 +
| HIMSS Interoperability Showcase
 +
|-
 +
| 2013
 +
| New Orleans, LA
 +
| [http://www.interoperabilityshowcase.org HIMSS Interoperability Showcase]
 +
| HIMSS Interoperability Showcase
 +
|-
 +
| 2012
 +
| Las Vegas, NV
 +
| [http://www.interoperabilityshowcase.org HIMSS Interoperability Showcase]
 +
| HIMSS Interoperability Showcase
 +
|-
 +
| 2011
 +
| Orlando, FL
 +
| [http://www.interoperabilityshowcase.org HIMSS Interoperability Showcase]
 +
| HIMSS Interoperability Showcase
 
|-
 
|-
 
| 2010
 
| 2010

Revision as of 11:37, 30 January 2017

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 2017-2018 Cycle

Current Work

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
2016 Las Vegas, NV HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2015 Chicago, IL HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2014 Orlando, FL HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2013 New Orleans, LA HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2012 Las Vegas, NV HIMSS Interoperability Showcase HIMSS Interoperability Showcase
2011 Orlando, FL HIMSS Interoperability Showcase HIMSS Interoperability Showcase
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.