Health Care Native App Example

From MgmtWiki
Revision as of 18:30, 25 May 2019 by Tom (talk | contribs) (Context)

Jump to: navigation, search

Full Title or Meme

Best Practice example of a Native Application designed for a modern Smart Phone.


Matching health care records and interoperability have been a great pain points to date with one of the primary barriers being the lack of a


In the absence of a single payer health care network, the US is blessed with a plethora of solutions, but plagued with the resultant lack of interoperability.


Information Sharing

It is generally agreed that it is better for doctors to have a full set of patient health histories to enable adequate care, especially in life-or-death emergency cases.

FHIR, pronounced 'fire' is working on Information Sharing APIs, but has not yet dealt with Federated Trust.

Federated Trust Anchor

  • It is likely that a single anchor for a country's health ecosystem is required where any patient or provider can learn the status of any Web Site by providing metadata about the entity that operates the Web Site from a Federation Trust Registry.
  • It is likely that the entity operating the Web Site will not be the health service Provider, and so a "On-behalf-of" Identifier is likely to be required as well.

Patient's Rights

Deborah C. Peel, MD Founder and President Patient Privacy Rights

Patient Experience

The best Patient Experience will not be delivered by focusing on Patient's legal rights.

Emergency Contact Example

. See an evolving example of this use case at