Difference between revisions of "Health Care Digital Identity"
From MgmtWiki
(→Context) |
|||
| Line 9: | Line 9: | ||
#) Once a patient is identified at one organization, how do we cross-facility match a patient to their records? | #) Once a patient is identified at one organization, how do we cross-facility match a patient to their records? | ||
#) What does a consumer-directed, electronic federated consent approach look like? | #) What does a consumer-directed, electronic federated consent approach look like? | ||
| + | |||
| + | ==Solutions== | ||
| + | ===Identification of individuals with mobile devices=== | ||
| + | ===Secure Authentication with Open Standards=== | ||
| + | ===Cross-facility matching of individuals=== | ||
| + | ===Electronic Federated Consent=== | ||
==References== | ==References== | ||
| − | *[https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf | + | *[https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf ONC for Health IT Draft Trust Exchange Framework] |
Revision as of 13:49, 8 April 2019
Contents
Full Title
A means for creating Identifiers and references to Electronic Health Records for people seeking health care in the US.
Context
On March 4, CMS and ONC published two proposed rules in the Federal Register which requires the use of application programming interfaces (APIs) built with Fast Healthcare Interoperability Resources (FHIR) to share both clinical and claims data with consumers, third-party applications, and others within the health care ecosystem. In order to do so, there is a need to solve for at least four specific
Problems
- ) How do we identify unique users across systems using person-centric mobile technologies?
- ) How do we securely authenticate individuals across systems using modern, open standards?
- ) Once a patient is identified at one organization, how do we cross-facility match a patient to their records?
- ) What does a consumer-directed, electronic federated consent approach look like?
