Difference between revisions of "201809 VA Closed-Loop Referrals"

From HL7Wiki
Jump to navigation Jump to search
Line 13: Line 13:
 
The U.S. Veterans Health Administration (VHA) seeks to achieve seamless care for Veterans across the continuum of care that increasingly includes healthcare services outside of VHA at community care providers. Estimates indicate that 30% of Veteran healthcare occurs outside of the VHA network and 60% of Veterans receive part of their care from community providers. Improving standards and interoperability for closed-loop referrals between VHA and community providers is an essential capability required to achieve seamless care. Although this requirement is certainly not limited to VHA and its community providers, the use cases and clinical data examples featured in this connectathon track will emphasize healthcare for Veterans.
 
The U.S. Veterans Health Administration (VHA) seeks to achieve seamless care for Veterans across the continuum of care that increasingly includes healthcare services outside of VHA at community care providers. Estimates indicate that 30% of Veteran healthcare occurs outside of the VHA network and 60% of Veterans receive part of their care from community providers. Improving standards and interoperability for closed-loop referrals between VHA and community providers is an essential capability required to achieve seamless care. Although this requirement is certainly not limited to VHA and its community providers, the use cases and clinical data examples featured in this connectathon track will emphasize healthcare for Veterans.
  
The U.S. Office of the National Coordinator for Health Information Technology (ONC) organized the [https://oncprojectracking.healthit.gov/wiki/display/TechLab360X/360X+Implementation+Guide 360Exchange (360X) Project] to accelerate interoperable health care data exchange in heterogeneous EHRT environments. In particular, the 360X Project seeks to enable providers to exchange the following types of clinical information from within their EHRT workflow, regardless of the EHRT used:
+
The U.S. Office of the National Coordinator for Health Information Technology (ONC) organized the [https://oncprojectracking.healthit.gov/wiki/display/TechLab360X/360X+Implementation+Guide 360Exchange (360X) Project] to accelerate interoperable health care data exchange in heterogeneous EHR technology environments. In particular, the 360X Project seeks to enable providers to exchange the following types of clinical information from within their EHR workflow, regardless of the EHRT used:
  
 
* Referral requests containing relevant patient clinical information
 
* Referral requests containing relevant patient clinical information
 
* Result of referral containing relevant patient clinical information
 
* Result of referral containing relevant patient clinical information
  
Whereas the 360X Project emphasized C-CDA content and Direct transport infrastructure, this connectathon track focuses on fulfilling these requirements using FHIR resources, REST architecture for transport, and OAuth2 for security.
+
Whereas the 360X Project emphasized C-CDA content and Direct transport infrastructure, this connectathon track focuses on fulfilling these requirements using FHIR resources, REST architecture for transport, and OAuth2 for security. The primary FHIR version for this track is STU3. However, extra credit will be awarded to participants that can demonstrate conversion between DSTU2 and STU3 to enable transport to/from referral participants that can support only FHIR DSTU2 endpoints.
  
 
==Proposed Track Leads==
 
==Proposed Track Leads==
Line 33: Line 33:
  
 
==Roles==
 
==Roles==
 +
 +
===Referral Initiator===
 +
 +
 +
===Referral Recipient===
 +
 +
 +
===Community Care Coordinator===
 +
  
 
===FHIR Data Server===
 
===FHIR Data Server===
A FHIR server (version 3.0) should support the following resources for closed-loop referral workflow, in addition to core clinical data (Patient, Observation, etc):
+
A FHIR server (version 3.0) should support the following resources for closed-loop referral workflow:
 
* [http://hl7.org/fhir/referralrequest.html ReferralRequest]
 
* [http://hl7.org/fhir/referralrequest.html ReferralRequest]
 
* [http://hl7.org/fhir/subscription.html Subscription]
 
* [http://hl7.org/fhir/subscription.html Subscription]
 +
* Clinical data including, but not limited to: Patient, Observation, Procedure, MedicationRequest, ProcedureRequest, etc.
  
 
Optional Resources:
 
Optional Resources:
 
* [http://hl7.org/fhir/appointment.html Appointment]
 
* [http://hl7.org/fhir/appointment.html Appointment]
 +
* Practitioner, PractitionerRole and Organization
  
A FHIR server is available for testing with sample data that represent one or more care plan scenarios.
+
A FHIR server is available for testing with synthetic sample data that illustrates Veteran scenarios:
 
* HSPC sandbox server (FHIR 3.0.1) at '''Endpoint TBD'''
 
* HSPC sandbox server (FHIR 3.0.1) at '''Endpoint TBD'''
 
===FHIR Knowledge Asset Server===
 
A FHIR server (version 3.0) should support the following resources for knowledge-based care management:
 
* PlanDefinition, ActivityDefinition, Library
 
 
  
 
==Scenarios==
 
==Scenarios==

Revision as of 17:39, 6 August 2018

Return to September 2018 FHIR Connectathon 19 home page

VA Closed-Loop Referrals

Submitting WG/Project/Implementer Group

Justification

The U.S. Veterans Health Administration (VHA) seeks to achieve seamless care for Veterans across the continuum of care that increasingly includes healthcare services outside of VHA at community care providers. Estimates indicate that 30% of Veteran healthcare occurs outside of the VHA network and 60% of Veterans receive part of their care from community providers. Improving standards and interoperability for closed-loop referrals between VHA and community providers is an essential capability required to achieve seamless care. Although this requirement is certainly not limited to VHA and its community providers, the use cases and clinical data examples featured in this connectathon track will emphasize healthcare for Veterans.

The U.S. Office of the National Coordinator for Health Information Technology (ONC) organized the 360Exchange (360X) Project to accelerate interoperable health care data exchange in heterogeneous EHR technology environments. In particular, the 360X Project seeks to enable providers to exchange the following types of clinical information from within their EHR workflow, regardless of the EHRT used:

  • Referral requests containing relevant patient clinical information
  • Result of referral containing relevant patient clinical information

Whereas the 360X Project emphasized C-CDA content and Direct transport infrastructure, this connectathon track focuses on fulfilling these requirements using FHIR resources, REST architecture for transport, and OAuth2 for security. The primary FHIR version for this track is STU3. However, extra credit will be awarded to participants that can demonstrate conversion between DSTU2 and STU3 to enable transport to/from referral participants that can support only FHIR DSTU2 endpoints.

Proposed Track Leads

??

Expected participants

The following organizations have indicated an interest in participating in this track:

  • Veterans Health Administration (VHA)
  • Allscripts
  • InterSystems
  • Perspecta
  • Your organization here!

Roles

Referral Initiator

Referral Recipient

Community Care Coordinator

FHIR Data Server

A FHIR server (version 3.0) should support the following resources for closed-loop referral workflow:

  • ReferralRequest
  • Subscription
  • Clinical data including, but not limited to: Patient, Observation, Procedure, MedicationRequest, ProcedureRequest, etc.

Optional Resources:

  • Appointment
  • Practitioner, PractitionerRole and Organization

A FHIR server is available for testing with synthetic sample data that illustrates Veteran scenarios:

  • HSPC sandbox server (FHIR 3.0.1) at Endpoint TBD

Scenarios

The following two scenarios are included from the ONC 36X Project Referral Workflow as an illustration of referral state transitions. The first diagram shows state transitions from the point of view (POV) of the referral initiator, and the second diagram from the point of view of the referral recipient.

Referral initiator
Referral recipient