Patient Care Coordination

From IHE Wiki
Jump to navigation Jump to search

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 manages the PCC Profiles and the PCC Technical Framework.

The Patient Care Coordination Domain is sponsored by:

HIMSS
Health Information Management Systems Society
ACP
American College of Physicians

2007-2008 Season

Patient Care Coordination Profiles


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 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 template.
    • Submit the propsal draft to us.
    • Attend the november planning meeting to help clarify and prioritize your proposal
    • Follow up by submitting a the 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 saying you’re interested so we can get you on the list-serves.

Roadmap

Legend

Priority:
H
Essential Now
M
Essential Future
L
Nice to Have

Prerequisites: List of applicable standards

Coordination: Other domains to coordinate efforts with.

Strategy:
CP
Develop Content Profile
IP
Develop Integration Profile
Res
Research Applicable Standards
Promote
Promote Applicable Standards Development Efforts

Year: Earliest Opportunity given prerequisites, priority and skills.

Roadmap

Topic Pri Standards/Prerequesites Coord Strategy Year
Referral/Transfer of Care
Discharge Packaging (Discharge to Sub-Acute Nursing Facility/Extended Care Facility/Home Health) H XDS-MS Linking w other clinical reports CP, IP 2008
Find Provider for Referral L Unknown Finance Research 2007
Referral Notification/Authorization (payer focused) L X12-837

HL7 V3

Finance Research 2007
Transfer of Care workflow Initiate/accept/reject/follow-up M HL7 V3 HL7 Care Transfer Messages IP 2007

Document Types

  • History and Physical
  • Operative Notes
  • Discharge/Transfer Summaries
  • Progress Notes
  • Nursing Notes
  • Flow Sheets
  • Radiology Report
  • Cardiology Report
  • Generic data dumps
  • Consultants Report
  • ED Triage Surveillance Report
  • ED Encounter Report

M,H

  • CDA Release 2.0
  • LOINC
  • JCAHO (US)
  • CCR (General, discipline-focused)
Lab/Path (IHE Europe)

Radiology Cardiology

Research CP 2006 - 2007
Orders between Providers / Ancillary Services H HL7 V3

HL7 V2 ORU

ITI

Lab Radiology

Promote/ Adapt Existing IPs 2006
Order Sets and Care Plans L XDS Non-Patient Documents

HL7 Templates [Orders/Obs] HL7 Patient Care HL7 EHR Order Sets [Rad/Labs, Unified terminology/code systems]

ITI

Quality

Promote 2008
Pay for Performance Data Aggregation M Order Sets and Care Plans

HL7 Templates HL7 Orders and Observations Minimum Data Sets Doc-IT

Quality Research 2008
Query for Medication List from Multiple Providers H HL7 V3

RxHub JCAHO Med Reconciliation

Research 2007
Public Health Registries & Surveillance H XDS-MS w immunization structure Quality Refer to Quality Domain ?
Capture of Clinical Research Data within an EHR

ability to display Case Report Form for data capture retrieve info from EHR system (Note: Form definition work to be undertaken by CDISK in 2006 independent of ITI RFD profile work)

CDISC’s ODM

HL7’s CDA eDCI HL7 CCOW SAFE (Digital Signature) Clinical Trial Care Report Forms

ITI CP (Clinical Trial Data Capture profile)

IP Referred to ITI domain (Retrieve Form for Display)

2006+
Emergency Medical Services (EMS) to Emergency Dept Data Transfer M Data Elements for Emergency Department Systems (DEEDS) v1.0

CDA/CRS (CCR) National Emergency Medical Services Information System (NEMSIS) v2.2

CP 2007
#4 Self-referred ED Event (no pre-announcement of pt arrival) H Data Elements for Emergency Department Systems (DEEDS) v1.0

CDA/CRS (CCR) Pt consent/granting role-based access controls

ITI CP 2006
ED to Surveillance Regsitry H 2007
ED to PCP transfer M XDS-MSCDA R2 2007
#7 Document Section Encoding

Pediatrics (Immunizations, Growth charts) Public Health Survelliance (Immunizations, etc) Chronic Disease Mgmt Revised to: Immunization, Vital Signs, and Laboratories

CCR

CDA R2 HL7 V3 Clinical Statement Model HL7 V3 Patient Care Structures HL7 V3 Pharmacy LOINC JCAHO

CP 2006
Patient Selection Query
  • Clinical trial qualifications
  • Transfer to ECF assessment
  • Chronic disease mgmt candidate
  • Disease survelliance candidate
HL7 V3 Care Record Query 2007
Cardiac electrophysiology admission discharge summary for the referring cardiologist (from Harry Solomon) XDS-MSCDA R2 / CRS CARD Refer to Cardio domain 2007

Demonstrations & Presentations

Date Location Event Details
2007.02.25-2006-03.01 New Orleans, LA HIMSS 2007 HIMSS Interoperability Showcase

See Also

Committees


This page is based on the Domain Template.