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 54

FHIR Meaningful Use 54

Healthcare Exchange Standards

MARCH 16, 2015

Thus it targeted use of HTTP RESTful, using JSON encoding. The Mobile Health Documents (MHD) profile was born to provide a more simple API to an XDS environment. This happened to be the same timeframe that Grahame was fanning the FHIR flames. So we joined forces and brought the concepts needed for XDS into FHIR®.

FHIR 40

FHIR Mobile Health mHealth Meaningful Use 40

Healthcare Exchange Standards

JANUARY 16, 2013

This defines the purpose of a security Audit Log, the uses of this audit log information, including how it is used to provide patients with accounting of disclosures. This specification has been leveraged by many regional initiatives including in the USA the Meaningful Use Stage 2. So far there has been little interest.

FHIR 40

FHIR EHR Meaningful Use 40

Healthcare Exchange Standards

DECEMBER 30, 2017

These historic events need to have the full context of them, which is what a Document model provides. 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.

HIE 40

HIE FHIR Meaningful Use Leadership 40

mHealth Insight

SEPTEMBER 6, 2019

Back in 2008 at 3GDoctor we started offering the ability for Patients to use their mobiles to provide their own history to Doctors prior to a documented video consult: [link]. 44 FHIR allows external third-party apps to integrate into the EHR workflow. “Digital Therapeutics and Diagnostics.

Mobile Health 48

Mobile Health mHealth EHR FHIR 48