Health Care Profile Sandbox: Difference between revisions
Jump to navigation
Jump to search
| (8 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
==Context== | ==Context== | ||
*As a part of the creation of a set of [[Identity Ecosystem]]s this sandbox is targeted to apply to any deployment that handles EHI. | * On Monday, 2020-03-09 the OMB released the [https://www.healthit.gov/curesrule/ ONC’s Cures Act Final Rule supports seamless and secure access, exchange, and use of electronic health information.] | ||
* | * On Tuesday, 2020-03-10 the New York Time pointed out that with the great power that this act unleashes comes great responsibility to protect privacy when the [https://www.nytimes.com/2020/03/09/business/medical-app-patients-data-privacy.html New Data Rules Empower Patients, but Risk Privacy.] | ||
* As a part of the creation of a set of [[Identity Ecosystem]]s this sandbox is targeted to apply to any deployment that handles EHI so that patient can see the PHI without releasing it elsewhere. | |||
* First to show feasibility of the proposed system, and then to show conformance by vendors and providers the other parts will need to be available. | |||
==Problems== | ==Problems== | ||
* There are a large number of working parts for a successful US Healthcare Ecosystem. | |||
* In order for vendors and providers to test both their software and their implementations there needs to be a full functional test environment. | |||
* There are some question about how users will interact with the systems. It is very difficult to test the user acceptance without a system that is functionally complete. | |||
==Solutions== | ==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== | ==References== | ||
Latest revision as of 16:20, 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
- On Monday, 2020-03-09 the OMB released the ONC’s Cures Act Final Rule supports seamless and secure access, exchange, and use of electronic health information.
- On Tuesday, 2020-03-10 the New York Time pointed out that with the great power that this act unleashes comes great responsibility to protect privacy when the New Data Rules Empower Patients, but Risk Privacy.
- As a part of the creation of a set of Identity Ecosystems this sandbox is targeted to apply to any deployment that handles EHI so that patient can see the PHI without releasing it elsewhere.
- First to show feasibility of the proposed system, and then to show conformance by vendors and providers the other parts will need to be available.
Problems
- There are a large number of working parts for a successful US Healthcare Ecosystem.
- In order for vendors and providers to test both their software and their implementations there needs to be a full functional test environment.
- There are some question about how users will interact with the systems. It is very difficult to test the user acceptance without a system that is functionally complete.
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.