View source for HIMSS 2017 Patient Choice

[[Security|Back to Security Main Page]]
== HIMSS 2017 Orlando Top Story ==
[[File:Alice's Graphic.jpg|frame|Veteran Alice HIMSS 2017 Patient Choice Hero]]

*FHA’s Patient Choice Demonstrations at HIMSS 2017 captures attention.  With a storyline based on ONC Patient Choice pilots, teams from the [https://www.va.gov/health/ Veteran Health Administration ](VHA or VA), [https://mihin.org/  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 [https://www.research.va.gov/MVP/  Million Veteran Program].
==Veteran Alice's Story==
*Alice is a Veteran and lives in Michigan. After a tour in Afghanistan, Alice is diagnosed with post-traumatic stress and substance abuse disorders in part due to combat. Alice receives treatment from the U.S. Department of Veterans Affairs (VA) and her Michigan community mental health clinic through the Veteran’s Choice Program. Alice consents to share her specially protected health information between the VA and the community mental health clinic for care coordination. 
*To do so, Alice logs on to Consent2Share. She wants to provide authorization (1) for the VA to share her substance abuse treatment records with the community mental health clinic, and (2) to share all of her information from her community mental health clinic with the VA.
She wants her mental health clinic to have a good understanding of her substance abuse treatment. Using the “Add Providers” feature, Alice adds both providers to her Consent2Share account. She can also select behavioral health information that she does not want the community mental health clinic to view.
*Alice chooses to create two consents for the purpose of treatment. In the first consent, she wants to share only her VA substance abuse records with the local mental health clinic. Next, she creates a consent for her mental health clinic to share all of her mental health information with the VA. Alice verifies the information she has entered. 
Now, Alice wants to review her consents. To do so, she selects “Try My Policy” and reviews her choices. After she reviews her choices, she can sign the consent electronically online using Consent2Share. Once she signs the consent, she can view it online and download it as a PDF file.
*As a native Spanish speaker, Alice can also choose to use the Consent2Share Spanish translation. This option allows her to create and manage her consents in the language with which she is comfortable, without sacrificing any features or functionality.
From a technical perspective, there are two key steps:
*First, the VA electronically stores Alice’s substance abuse treatment records in their health information exchange or HIE
*Second, after Alice provides her written consent online using Consent2Share, the local mental health clinic can electronically retrieve Alice’s substance abuse treatment records from the VA’s HIE
*Using the Consent2Share application, Alice is able to visit her local mental health clinic and ensure that her substance abuse treatment will continue uninterrupted.

== Presentations, Use Case, Technical Documentation == 
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/HIMSS%202017%20Consent%20on%20FHIR%20Vignette%20Playbook%206%20wiki.docx HIMSS 2017 Consent on FHIR Vignette Playbook]
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/Patient%20Choice%20HIMSS%20Basic%20%20Research%20Vignette%20FHA%208.pptx HIMSS Patient Choice Basic and Research Vignette]

== Previous Demonstations upon which the HIMSS 2017 Demonstration builds ==
=September 2016 FHIR Connectathon=
*[https://www.youtube.com/watch?v=VbTxBqYyQtg Enforcing FHIR Consents using a Third-Party Authorization Server] demonstrated at the HL7 September 2016 FHIR Connectathon shows an environment where a FHIR OAuth server and the HL7 Healthcare Privacy and Security Classification System for security labels and data segmentation.

== HIMSS 2017 Technical Presentations ==
*[https://www.youtube.com/watch?v=Sj0ZOi1AxhY HL7 Cascading UMA OAuth video - Duane Decouteau]
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/hl7cascadingoauth%20%20Duane.pptx Cascading OAuth and Patient Right of Access]
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/FHIR-OAuth-Consent-Cascade%20w%20animation.pptx  Animated Cascading OAuth Flows]
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/Cascaded%20Authorization%20Sequence-20170110.docx  Cascaded Authorization Detailed Flows]
*[http://va.edmondsci.com:8080/ehtac/sof/test.html HCS on FHIR Demo Mohammad Jafari] 
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/Cascading%20OAuth%20for%20Patient%20Consent%20and%20Patient%20Right%20of%20Access%20Use%20Cases%20-%20wiki.pdf Cascading OAuth for Patient Consent and Patient Right of Access Use Cases]
*[http://himss.edmondsci.com:8080/fhir-uma-client-demo/ Cascading UMA/Oauth Demonstration]
*[http://va.edmondsci.com:8080/ehtac/sof/test.html Privacy on FHIR HIMSS 2015 Demonstratrion]
[[File:Cascading_OAuth_Sequence_Diagram.png|600px|thumb|center|Cascading OAuth Sequence Diagram]]

== HIMSS 2017 Research Patient Choice ==
[[File:Research_Patient_Choice_with_Provenance_demonstation.png|400px|thumb|left|HIMSS Research Patient Choice with Provenance Demonstration]]

*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/Patient%20Choice%20Demo-Duane.pptx Patient Choice Demo - Provenance for Research]
*[http://himss.edmondsci.com:8080/himss-research-ui-ui-1.0-SNAPSHOT/ HIMSS Research Provenance Demonstation]
*[http://gforge.hl7.org/gf/project/security/docman/Security%20ONC%20projects/HIMSS%202017/Duane%20himssresearchflows.pptx HIMSS Research Data Flows]
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 ==
*[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]
[[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]]
























































===[[Consent on FHIR]]===
For previous HIMSS and other collaboration demonstrations and videos

[[Security|Back to Security Main Page]]