Health Care Profile Sandbox: Difference between revisions
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
# Destination EHR that can accept an identifier token from a patient on a validated smart phone | # Destination EHR that can accept an identifier token from a patient on a validated smart phone | ||
# Medical record locator server (lower priority) | # Medical record locator server (lower priority) | ||
It will also be | It will also be necessary for some vendors to supply smartphone native apps and other services to validate the sandbox before it is opened for general use. | ||
==References== | ==References== |
Revision as of 00:05, 10 March 2020
Full Title or Meme
This Health Care Profile Sandbox details a test suite that will allow developers of code and user experience to assure the compliance of their products to the Health Care Profile of the basic framework
Context
- As a part of the creation of a set of Identity Ecosystems this sandbox is targeted to apply to any deployment that handles EHI.
- this is a place holder.
Problems
this is a place holder.
Solutions
The following services are needed for a fully complete test profile.
- Trustregisty - which will have certificates for all part of the sandbox and for any incoming test service
- Source EHR with a set of test patients and the ability to issue medical record locators for those patients.
- Credential Service Provider - which will accept requests from smartphone for validation as conformant for both IAL2 and AAL2
- Destination EHR that can accept an identifier token from a patient on a validated smart phone
- Medical record locator server (lower priority)
It will also be necessary for some vendors to supply smartphone native apps and other services to validate the sandbox before it is opened for general use.
References
- The page Health Care Profile contains the details that will allow developers of code and user experience to create compliant products to the framework.