Blog FHIR Health Data 
Healthcare IT News - Telehealth
JULY 17, 2020
Microsoft is previewing its new Azure IoT Connector for FHIR, an API feature that enables healthcare organizations to scale secure connectivity for an array of devices streaming protected health information. WHY IT MATTERS. "Developers have to build their own secure pipelines from scratch. THE LARGER TREND. ON THE RECORD.
Health Intersections
MARCH 20, 2020
I’ve asked HL7 members to comment on the things they’re doing below (but honestly, they probably won’t have time – I’m getting this blog post out in a hurry between builds). But we’ll do the best with what we’ve got.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Society for Participatory Medicine
NOVEMBER 1, 2019
This is a cross-post from my personal blog. The organizers of the FHIR #DevDays conference next month have announced the four finalists who will come to Amsterdam to present their ideas to a panel of judges. In contrast to this, the HL7 FHIR organization said explicitly this June that #FHIR exists to serve patient needs.
Society for Participatory Medicine
APRIL 27, 2018
Live blogging notes during meeting. ” Shifting focus to “I’m a customer, and this is what I need, here are the use cases” (HL7, FHIR, et al), collective ask by customers w/one unified voice, the vendors have started leaning in. Argonaut, HL7, FHIR are toolkit. VA Lighthouse update. No rules, unconference.
Lloyd Price
JUNE 14, 2018
App Orchard, for its part, lets developers use a FHIR-based API to access an Epic development sandbox. 2018 Digital Health Prediction 2: Voice technology will be the first step to personalising pharma. Google Voice, Siri, Cortana and Alexa will finally have connectivity to raw and comprehensive up-to-date data.
E-CareManagement
MAY 17, 2023
by Vince Kuraitis , Brendan Keeler , and Jody Ranck Recent regulations have mandated the use of HL7 FHIR APIs (application programming interfaces) to share health data. APIs facilitate the sharing of health data across different devices and platforms. We recommend a more opportunistic POV.
Healthcare Exchange Standards
FEBRUARY 20, 2019
Which does not help for Data Segmentation nor Privacy. The recommendation I give here is restricted to the gross level: for Document Sharing at the XDS/XCA/DocumentReference metadata level; for FHIR REST at the returned Bundle.meta.security level, but not on each Resource in the Bundle; and for CDA at the CDA header, but not on each element.
Expert insights. Personalized for you.
197 
Let's personalize your content