This EHR Module is ONC 2015 Edition Cures compliant and has been certified by Leidos Labs, an ONC-ACB, in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.
Leidos Labs is pleased to announce that Health IT Harvest version 12 attained 2015 Edition Health IT Modular Certification from the Leidos Labs ONC Health IT Certification Program. Certification was granted based on rigorous and thorough testing by Leidos Labs, an Accredited Test Lab (ATL), against the following ONC Approved Test Procedures:
||Orchard Software Corporation
||May 31, 2022
||Harvest version 12
||2015 Edition Modular Health IT Certification
|Certification Criteria tested
||170.315(d) Privacy and Security
170.315(d)(1) Authentication, access control, and authorization
170.315(d)(2)_C Auditable events and tamper-resistance
170.315(d)(3)_C Audit reports
170.315(d)(7) End-user device encryption
170.315(d)(12)_C Encrypt authentication credentials
170.315(d)(13)_C Multi-factor authentication
170.315(f) Public Health
170.315(f)(3) Transmission to public health agencies – reportable labs
170.315(g) Design and Performance
170.315(g)(4) Quality Management System
170.315(g)(5) Accessibility-centered design
|Additional Software Required for Use
||Annual support contract fee, additional per interface fee if certified interfaces were not implemented during original installation/implementation of LIS.
|Limitations (Contractual/Business Practices)
Limitations of a contractual nature (including developer policies and other business practices) that a user may encounter:
|in the implementation or use of the capability: Failure to maintain support contract would result in ending maintenance/support for the products. Any interruption to the functionality would not be addressed until client became current on support.
|>in connection with the data generated in the course of using the capability: None
Limitations of a technical, technological or practical nature that a user may encounter that could:
|> prevent or impair the successful implementation, configuration, customization, maintenance, support or use of the capability: Lack of a functioning interface with an EHR or other Health IT would prevent transfer of data via HL7 messaging. Clients are instructed to make sure the necessary details for any interface with another vendor are worked out prior to implementation.
|> prevent or limit the use, exchange, or portability of any data generated in the course of using the capability: None