BlueButton On FHIR Presentation to Attachments Work Group at HL7 Meeting Jan 2016
•
3 likes•1,374 views
The document discusses the BlueButton vision of enabling beneficiaries to connect their healthcare data to trusted applications and services through standards-based APIs. It proposes using the POET (Pre-Oauth Entity Trust) API to leverage existing Direct Trust networks to validate the trustworthiness of third-party applications requesting access to healthcare data APIs like FHIR. The document also outlines plans to develop and prototype a BlueButtonOnFHIR API to include patient profiles and ExplanationOfBenefit resources at an upcoming FHIR code-a-thon event.
Recommended
Recommended
More Related Content
What's hot
What's hot (15)
Similar to BlueButton On FHIR Presentation to Attachments Work Group at HL7 Meeting Jan 2016
Similar to BlueButton On FHIR Presentation to Attachments Work Group at HL7 Meeting Jan 2016 (20)
More from Mark Scrimshire
More from Mark Scrimshire (17)
Recently uploaded
Recently uploaded (20)
BlueButton On FHIR Presentation to Attachments Work Group at HL7 Meeting Jan 2016
- 1. H7 WGM BlueButton On FHIR Mark Scrimshire Entrepreneur-In-Residence, HHS/CMS Jan 2016
- 2. @ekivemark Disclaimer The views expressed in this presentation are my own and should not be construed as an official position of the US Department of Health and Human Services or the Centers for Medicare & Medicaid Services. 2
- 3. @ekivemarkhttps://github.com/ekivemark/poet BlueButton Vision “Build a Developer-friendly, Standards-based data API that enables beneficiaries to connect their data to the applications, services and research programs they trust”
- 4. @ekivemarkhttps://github.com/ekivemark/poet BUT… Who does a publisher trust to consume them? APIs are spreading like wildfire
- 5. @ekivemarkhttps://github.com/ekivemark/poet OAuth is proven at scale@ekivemark
- 6. @ekivemarkhttps://github.com/ekivemark/poet But OAuth still doesn’t answer: “Who do you trust?” http://www.hhs.gov/idealab/2015/11/19/trusting-health-apis/
- 7. @ekivemarkhttps://github.com/ekivemark/poet Do we want another Bureaucracy to determine Trust?
- 8. @ekivemarkhttps://github.com/ekivemark/poet Healthcare already has established Networks of Trust
- 9. @ekivemarkhttps://github.com/ekivemark/poet POET Pre Oauth Entity Trust api A Secure open source Trust Validation API that leverages Direct Trust Bundle administration functions to provide a basis for trusting 3rd Party Applications requesting access to Health Data APIs, such as FHIR https://github.com/ekivemark/poet
- 10. BlueButton On FHIR Beneficiary (Patient) OAuth2 POET API Contract (Consent) Explanation Of Benefit 3rd Party Apps 3rd Party Apps 3rd Party Apps
- 11. Patient focused Self-contained Include reference Identifiers Include patient profile subset EOB = Adjudicated claim One claim = One EOB EOB has a GUID The EOB @ekivemark 1 2 3 4 5 6 7
- 12. A New FHIR EOB Resource What is it? @ekivemark
- 14. Follow our progress, join us and contribute • BlueButton Text to JSON Converter: • https://github.com/ekivemark/python-bluebutton • BlueButton On FHIR • https://github.com/ekivemark/BlueButtonFHIR_API • HL7 - FHIR • http://www.hl7.org/implement/standards/fhir/http.html • HL7 - WIKI • http://hl7-fhir.github.io/index.html • HAPI Server: • https://github.com/jamesagnew/hapi-fhir @ekivemark
- 15. FHIR Code-a-Thon • April 1-2, 2016 • US Department of Health and Human Services, Washington, DC • Pre-event to #HealthDataPalooza (May 8-11) • Prototype BlueButtonOnFHIR API • Patient Profile • ExplanationOfBenefit Profile