This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Consent on FHIR"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
| − | [http://wiki.hl7.org/index.php?title=File:Comparison_of_Smart_on_FHIR_and_UMA_OAuth_2.0.jpg | + | [http://wiki.hl7.org/index.php?title=File:Comparison_of_Smart_on_FHIR_and_UMA_OAuth_2.0.jpg Comparison of Smart on FHIR and UMA OAuth 2.0] |
| − | Comparison of Smart on FHIR and UMA OAuth 2.0] | ||
Revision as of 16:06, 4 October 2016
Back to Security Work Group Main 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).
- Security WG FHIR STU3 Server http://mhs.edmondsci.com:8080/fhir-uma-client-demo/
- VA ONC Patient Choice Pilot FHIR Consent UMA Connectathon
