Difference between revisions of "Consent on FHIR"
| Line 6: | Line 6: | ||
*Security WG FHIR STU3 Server http://mhs.edmondsci.com:8080/fhir-uma-client-demo/ | *Security WG FHIR STU3 Server http://mhs.edmondsci.com:8080/fhir-uma-client-demo/ | ||
*[http://gforge.hl7.org/gf/download/docmanfileversion/9385/14679/FHIR-Consent-UMA-20160919.pptx VA ONC Patient Choice Pilot FHIR Consent UMA Connectathon] | *[http://gforge.hl7.org/gf/download/docmanfileversion/9385/14679/FHIR-Consent-UMA-20160919.pptx VA ONC Patient Choice Pilot FHIR Consent UMA Connectathon] | ||
| − | * | + | *[http://gforge.hl7.org/gf/project/security/docman/Security%20Work%20Group%20Presentations%20and%20Papers/FHIR%20Connectathons/hl7cascadingoauth%201.pptx VA January 2017 San Antonio Connectathon: Cascaded Authorization FHIR Client Demonstration] |
Revision as of 18:02, 1 March 2017
Back to Security Work Group Main Page
Security WG members collaborating on ONC Patient Choice Project Mike Davis, Duane Decouteau,Mohammad Jafari, and Tony Mallia participated in the ONC Patient Choice Basic Consent Pilots at the HL7 Connectathon. Presentations, demonstration, and other material available on this page.
FHIR server with the capability to enforce patient consent via a third-party authorization server (UMA) as well as enforcing overarching organizational Security Labeling Service (SLS)/Privacy Protective Service (PPS) services. The server modifies and labels the outgoing bundles on a dynamic per-request basis based on applicable patient consents as well as the overarching SLS and PPS rules (including the high-watermark label on the bundle).
