Difference between revisions of "Direct Project (MU3))"
From OpenEMR Project Wiki
(Notes and progress of the Direct Project) |
|||
| Line 10: | Line 10: | ||
* Send payload to ETT is encrypted using the ETT’s Public Key and signed using OpenEMR’s Private Key. | * Send payload to ETT is encrypted using the ETT’s Public Key and signed using OpenEMR’s Private Key. | ||
* verifies the identified health information is successfully transmitted to a third party using Direct, in accordance with the standard specified at § 170.202(a)(2), and using the RFC-5751 “wrapped” message format. | * verifies the identified health information is successfully transmitted to a third party using Direct, in accordance with the standard specified at § 170.202(a)(2), and using the RFC-5751 “wrapped” message format. | ||
* Must meet 170.202(a)(2) standard which is the applicability statement for secure health transport | * Must meet 170.202(a)(2) standard which is the applicability statement for secure health transport which can be found here: https://wiki.directproject.org/w/images/e/e6/Applicability_Statement_for_Secure_Health_Transport_v1.2.pdf | ||
(h)(1)(i) - Receive | |||
Required Enhanced Testing | |||
* We have to certify sending and receiving from three unrelated HISPs. | |||
Note the documentation for the Direct service that was originally built and certified for MU2 is here: | Note the documentation for the Direct service that was originally built and certified for MU2 is here: | ||
Revision as of 19:54, 13 January 2022
Notes and documentation on the Direct Project goes here.
For MU3 we need to meet the following testing criteria:
(h)(1)(i) - Send Discover Certificates
- DNS discovery of address-bound and domain-bound certificates
- LDAP discovery of address-bound and domain-bound certificates
- Registration of Direct email address using the ETT (Edge Testing Tool)
- Send payload to ETT is encrypted using the ETT’s Public Key and signed using OpenEMR’s Private Key.
- verifies the identified health information is successfully transmitted to a third party using Direct, in accordance with the standard specified at § 170.202(a)(2), and using the RFC-5751 “wrapped” message format.
- Must meet 170.202(a)(2) standard which is the applicability statement for secure health transport which can be found here: https://wiki.directproject.org/w/images/e/e6/Applicability_Statement_for_Secure_Health_Transport_v1.2.pdf
(h)(1)(i) - Receive
Required Enhanced Testing
- We have to certify sending and receiving from three unrelated HISPs.
Note the documentation for the Direct service that was originally built and certified for MU2 is here: https://www.open-emr.org/wiki/index.php/Direct
The ONC (h)(1) criteria site is here: https://www.healthit.gov/test-method/direct-project
Certification of (h)(1) requires also certification of (b)(1) which is the Transitions of Care: https://www.healthit.gov/test-method/transitions-care
