Remove Health Information Remove HIE Remove Interoperability Remove mHealth
article thumbnail

Who will regulate mHealth? Patient Engagement at Crossroads; New Alliance Takes On Interoperability

Chilmark Research

Public vs. Private Oversight of Mobile Health. mHealth, known for rapid innovation and iteration, has a tendency to buck at the snail’s pace of FDA regulation. This could herald a new age of credibility for mHealth. The group’s stated purpose is to enable interoperability across the five founding members’ EHRs.

mHealth 60
article thumbnail

The The Five Biggest Areas of Opportunity for Digital Health

The Digital Health Corner

There are hospitals within the same healthcare system in many places with disparate EHRs which do not talk to each other or exchange information. Increasing healthcare consolidation of hospitals has exacerbated the problem of lack of interoperability. From a provider standpoint. Clinical trials.

Insiders

Sign Up for our Newsletter

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

article thumbnail

HIMSS or Bust

Chilmark Research

So if analytics is the engine, what is the steering wheel, what are the tires, is HIE the gas tank, or the fueling station? Looking to HIE, as we mentioned in late 2013 , we see a need to redefine this sector. Where is the next opportunity for value realization for a provider once their HIE is live?

HIE 60
article thumbnail

What is MHD beyond XDS-on-FHIR?

Healthcare Exchange Standards

Security and Privacy As with any Interoperability API dealing with Healthcare information, Security and Privacy are important. IHE doesn’t mandate a specific Security or Privacy model, as that would be Policy. But IHE does encourage the use of ATNA, and IUA.This also described on the FHIR Site on the Security page.

FHIR 40