FHIR and the future of healthcare
•Descargar como PPTX, PDF•
2 recomendaciones•5,077 vistas
HL7 FHIR is the upcoming standard for exchange of healthcare related information and building healthcare API's. This talk is about what standards need to do to remain relevant in an age where everyone builds one-off API's for their apps and cloud services.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (17)
Más de Ewout Kramer
Más de Ewout Kramer (13)
Último
Último (20)
FHIR and the future of healthcare
- 1. FHIR and the future of healthcare HL7 Policy Summit – Paris – May 2015 Ewout Kramer Furore
- 2. Warning If we want FHIR to be part of the future of healthcare We need to change our attitude
- 5. Your “Mobile” device becomes the Big Aggregator of data and functionality
- 6. Personal Health Record Patient Portal
- 7. 2012 The rise of the API 2015
- 8. Standardization? Q: How can these bits of software work together without “standardization”? A: No standardization…The biggest player gets adopted. Every one adapts to what they do!
- 9. So what about HL7 & FHIR? • With FHIR, HL7 joins the ranks of the API troopers. • But other than Twitter, Facebook etc. HL7 has no “services” or “functionality” to offer • FHIR is just a set of flexible standardized models and best-practices that others can use to create healthcare API’s
- 10. Who, Others? “Communicate first, standardize later” “Standardize first, communicate later”CHAOS? “He who ships code, wins”
- 11. Universal interoperability is a Myth
- 12. What can we do for the future of healthcare? • Produce basic building blocks everyone needs. Quickly! • Cooperate with your region/countries biggest players to get them adopted • Open up a FHIR registry to promote reusable profiles, patterns & practices. • Let everyone publish their specialized “dialect” of FHIR • Re-integrate when need arises (= there’s interest and money) • Let’s not be in the way. Be humble. Facilitate.
- 13. Questions?
Notas del editor
- Not much different from what we currently require our doctors and patients to do: juggle with logins and multiple websites to get or store our information
- The big aggregator – the extreme case is Apple HealthKit
- Apple is just following the trend here….
- “API” was a low-level term, but now it is about how a larger part of patient/client facing software is depending on how business start to expose their data and processes to client-facing software so it can be integrated in a larger whole. Again: Don’t expect you or your portal to be the center of the world, be humble
- So far I have been talking about integration…..but does that necessarily mean standardization too? Apps are written by smaller companies who very precisely chose in which API partners, which connections to invest. Only if you are a market-leader or have innovative solutions behind your API, you’ll get adopted
- Now I hear you say: well this is all about today newest and hottest, mobile. But we need to realize that although the conventional markets stay, a larger and larger part will be about these consumer facing devices and software, the rest just operates in the background. And HL7 really needed to get back into that part of the market. We need these others to make FHIR popular. App developers will communicate with innovative health solution providers and the big EHR vendors and only then realize that they are using a standardized API called FHIR.
- These vendors (and the hipster connecting to them) have only one need: communication. We have to enable them to produce software that enables better healthcare. We just should not be in the way. We may have focused on the inherent value of standardization and universal semantic operability.
- FHIR standardizes “the 80%”, but embraces adaption so there’s 20% that can be used to invent your own models and functionality Premise seems to be that all communication needs to be standardized or put into a framework before communication can be successful. I think that we just have to focus on enabling the software vendors to search each group. Even if that means they’ll all be talking dialects What language need to be standardized, depends on the context of communication. Within colleagues (in outside the same hospital), with other specialties, with the patient. Each has a bit of shared language, and “specialized” terms – we call it “jargon”.
- This means you accommodate for questions like “Where can I find a doctor specializing in X in my neighbourhood”, “Which patients will show up at my desk tomorrow”, “Is this medication safe to take for me?”. That’s fundamentally different from exchanging documents, aka “modern versions of the fax”.