This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "HIMSS 2017 Patient Choice"

From HL7Wiki
Jump to navigation Jump to search
Line 35: Line 35:
 
== SAMHSA Consent2Share ==
 
== SAMHSA Consent2Share ==
 
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/C2S%20Wetherby_1.pdf Consent2Share overview]
 
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/C2S%20Wetherby_1.pdf Consent2Share overview]
 +
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/Consent2Share_FAQs.docx Consent2Share FAQs]
 
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/C2SArchitectureDocument.pdf Consent2Share Architecture Document]
 
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/C2SArchitectureDocument.pdf Consent2Share Architecture Document]
 +
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/HIMSS%202017%20Patient%20Choice%20Overview.pptx HIMSS 2017 Patient Choice Overview]
 +
 
[[File:Consent2Share_Architecture.png|400px|thumb|left|Consent2Share Architecture]]  
 
[[File:Consent2Share_Architecture.png|400px|thumb|left|Consent2Share Architecture]]  
 
[[File:SAMHSA HIMSS 2017 Flows.png|400px|thumb|left|SAMHSA HIMSS 2017 Patient Choice on FHIR C2S Flow]]
 
[[File:SAMHSA HIMSS 2017 Flows.png|400px|thumb|left|SAMHSA HIMSS 2017 Patient Choice on FHIR C2S Flow]]

Revision as of 21:37, 8 June 2017

Back to Security Main Page

HIMSS 2017 Orlando Top Story

  • FHA’s Patient Choice Demonstrations at HIMSS 2017 captures attention. With a storyline based on ONC Patient Choice pilots, teams from the Veteran Health Administration (VHA or VA), Michigan Health Information Network Shared Services (MiHIN) and the Substance Abuse and Mental Health Administration] (SAMHSA) successfully demonstrated emerging technology and standards applied to meaningful patient choice for the use and disclosure of their own health information. 
  • Sponsors included the HHS National Privacy Office, Health Level 7 with support from the USPS, and Patient Privacy Rights.
  • In the demonstration, Alice, a fictional disabled veteran, enables her treatment and research providers to apply and comply with laws for specially protected information such as 42 CFR Part 2 and Title 38 Section 7332. 
  • MiHIN mediates coordination of Alice’s community based behavioral health through the VA Choice Program with her VA providers, facilitated by SAMHSA’s Consent2Share consent directive platform.  MiHIN uses HL7 Security Label “Privacy Tags” with an innovative internal rules engine approach to enforce Alice’s consents. 
  • Next, Alice’s participation in the Veterans4Research Program[1] is facilitated by a FHIR Research Informed Consent. VA uses a newly proposed Patient/Provider Centered Consent approach to authorization to enable Alice’s enforcement of her VA privacy preferences using her own HL7 FHIR and OAuth 2.0 equipped Authorization server.
  • To assure that Alice’s providers have confidence in the trustworthiness of her research data, FHIR Provenance is used to track its lifecycle.
  • The FHA Interoperability Showcase reported record traffic this year through the FH A vignette and other FHR stations. [HIMSS had 42,000 attendees at the showcase this year.  Of those 7,500 visited the Interoperability showcase.  That is a 4,000 person increase from last year’s numbers for interop showcase visitors.] Many reported to have been directed to these demonstrations. 
  • The vignettes ran seamlessly and seemed to catch the viewers’ imagination.  The discussions led to multiple deeper dives among interested parties while those who just wanted to get an overview were satisfied with the high level walk-throughs.
  • Components of this demonstration are in production or being piloted by the participating organizations, and their architects and developers, as well as those involved with development of these standards, were be on hand to answer audience questions. Participating teams were already brain-storming on HIMSS v-next based on the ONC Patient Research Choice Technical Project. 

[1] Modeled after but not affiliated with the Veteran Administration’s Million Veteran Program.

Presentations, Use Case, Technical Documentation

HIMSS 2017 Technical Presentations

Cascading OAuth Sequence Diagram
HIMSS Research Patient Choice with Provenance Demonstration

Provenance is critical to Research. The data flows from clinical care in translational Clinical Trials, and then through multiple paths for secondary research use. In a Learning Health System the secondary research findings should feed back into the initial clinical trial and should lead the patient to other beneficial clinical trials as part of precision medicine. Additionally, patient generated health data should be flowing into the research pipeline. These multiple data sources need to be tracked so that automated integration into research records can be done based on confidence metrics derived from provenance.

SAMHSA Consent2Share

Consent2Share Architecture
SAMHSA HIMSS 2017 Patient Choice on FHIR C2S Flow