Healthcare Exchange Standards

JUNE 25, 2018

Discussions at FHIR DevDays raised this question of a basic way to leverage FHIR API capability to enable the Patient beyond the limited Apps their provider has approved. If a healthcare provider offers a FHIR API (e.g. argonaut) -- meeting the Meaningful Use "API" requirement. Proposed quick-and-dirty solution?

FHIR 55

FHIR Meaningful Use 55

Health Blawg

APRIL 30, 2018

Aprima belongs to CommonWell, has done some FHIR development, and Michael would like to see Congress condition Medicare reimbursement on real interoperability. Comments […] article in more detail was originally published. Join the conversation on Twitter at #HarlowOnHC. David Harlow. The Harlow Group LLC.

EHR 60

EHR Interoperability Life Science FHIR 60

Health Blawg

APRIL 30, 2018

Aprima belongs to CommonWell, has done some FHIR development, and Michael would like to see Congress condition Medicare reimbursement on real interoperability. Comments […] article in more detail was originally published. Join the conversation on Twitter at #HarlowOnHC. David Harlow. The Harlow Group LLC.

EHR 60

EHR Interoperability Life Science FHIR 60

Healthcare Exchange Standards

DECEMBER 30, 2017

I have written articles about each of these transitions and more. The good news is that FHIR has a Document model, and the FHIR Document model has a directly convertible data model A FHIR Document travels an HIE easily CDA will fade, but never disappear. The good news is that FHIR is a fantastic API for consuming data.

HIE 40

HIE FHIR Meaningful Use Leadership 40