Costs and Limitations
Nexus EHR Certification Information
Nexus EHR is ONC 2015 Edition (Cures Update) certified EHR. It has been certified by Drummond Group, an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of the U.S. Department of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.
Certified Version: Nexus EHR V 7.3
Certificate ID.: 15.04.04.2989.Nexu.07.03.1.221227
Date Certified: 12/27/2022
Effective Date: 2015 Edition (Cures Update)
Modules Tested: 170.315 (a) (1-5, 9, 12, 14); (b)(1-3, 10); (c)(1-3); (d)(1-9, 12, 13); (e)(1, 3); (f)(1,2,5); (g) (2-7,9,10);
Clinical Quality Measures tested:22v5; 50v5; 68v6; 69v5; 117v5; 123v5; 124v5; 125v5; 127v5; 130v5; 138v5; 139v5; 144v5; 147v6; 149v5; 156v5; 157v5; 165v5; 166v6; 167v5;
Additional software used: MedlinePlus Connect (included in base product price), NewCropRx (included in base product price), EMR Direct interoperability Engine (add on module), Dynamed Plus by EBSCO Host (add on module)
Nexus EHR Costs and Limitations
Click here to know Costs and limitations of our certified functionality.
Supported Use Cases for Multi-Factor Authentication (MFA)
Nexus EHR supports following use cases for multi-factor authentication –
- Login to Nexus EHR
MFA option for this use case is optional. Customer may request to turn on authentication 2FA, in which case an access code is generated by system and sent to user. User is required to use the access code along with credentials to complete the login process.
- Electronic Prescription of Controlled Substances (EPCS)
All users that need to prescribe controlled substances will undergo identity proofing for the access of module. After this user has choice to use mobile based push access token or recieve access code on their mobile. Users can also use a hardware token for 2FA.
