Remove Document Remove FHIR Remove Interoperability Remove Meaningful Use
article thumbnail

Finding the future of interoperability with Redox: Part 3 – How Carequality can solve disconnected data for digital health

Redox

In the first two posts, I covered how Redox is overcoming current limitations with bulk FHIR and translating data between HL7 ® v2 and HL7 ® FHIR ®. The caveats: Any new clinical documentation must go into the member healthcare organization’s system for querying by other network participants. Let’s dive in.

article thumbnail

What is MHD beyond XDS-on-FHIR?

Healthcare Exchange Standards

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
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

HIE Future is Bright - stepping into 2018

Healthcare Exchange Standards

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
article thumbnail

Review of Mobile Devices and Health by Ida Sim in the NEJM

mHealth Insight

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.