Healthcare OpenID: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
==Full Title== | ==Full Title== | ||
The OpenID Foundation has a working group, HEART, which is creating specifications for the use of OpenID within the US Healthcare ecosystem. | The OpenID Foundation has a working group, HEART, which is creating specifications for the use of OpenID and related specifications within the US Healthcare ecosystem. | ||
==Context== | ==Context== | ||
The following Implementer’s Drafts of Four HEART Specifications have been approved as of March 12, 2019. The four specifications that were approved are: | The following Implementer’s Drafts of Four HEART Specifications have been approved as of March 12, 2019. The four specifications that were approved are: | ||
Revision as of 17:25, 14 March 2020
Full Title
The OpenID Foundation has a working group, HEART, which is creating specifications for the use of OpenID and related specifications within the US Healthcare ecosystem.
Context
The following Implementer’s Drafts of Four HEART Specifications have been approved as of March 12, 2019. The four specifications that were approved are:
- [ http://openid.net/specs/openid-heart-oauth2-1_0.htmlHealth Relationship Trust Profile for OAuth 2.0]
- Health Relationship Trust Profile for Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 Scopes
- Health Relationship Trust Profile for User-Managed Access 2.0 Health Relationship Trust Profile for User-Managed Access 2.0
- Health Relationship Trust Profile for Fast Healthcare Interoperability Resources (FHIR) UMA 2 Resources
A complete list of HEART specifications produced (including previous Implementer’s Drafts) can be found in the group’s BitBucket repository.
Problems
- The documents are written in the language of OpenID rather than in the terms of the US Healthcare ecosystem.
Solutions
- Bring up a GitHub repository and deprecate the bitbucket repository.