By Mark Scrimshire – The hottest topic in Healthcare interoperability right now is FHIR (pronounced “Fire”) – HL7’s Fast Health Interoperability Resource framework. FHIR has caught the imagination and attention of developers across the Healthcare world by offering a developer-friendly Application Programming Interface (API) and a rich set of simple, but flexible standard data formats.
Read More
By John Halamka MD – In many previous posts, I’ve written about the importance of enabling infrastructure to accelerate interoperability. The standards are not the rate limiting step, but the lack of a provider directory, patient identifier, and consent registry are.
By John Halamka, MD Twitter: @jhalamka As I travel across the country and listen to CIOs struggling with mandates from Meaningful Use to ICD-10 to…
The purpose of the Argonaut Project to rapidly develop a first-generation FHIR-based API to enable expanded information sharing of electronic health records and other health…
The purpose of the Argonaut Project to rapidly develop a first-generation FHIR-based API to enable expanded information sharing of electronic health records and other health information technology based on Internet standards and architectural patterns.
To the extent that query capabilities are included in MU Stage 3, we are at an awkward moment in standards development: Older standards such as XDS/XCA are mature but inherently limited, whereas newer API-based standards are not yet ready for large-scale adoption.