§170.315(g)(5) Accessibility-Centered Design

Mirth® Connect by NextGen Healthcare User Guide

§170.315(d)(13) Multi-Factor Authentication

(d)(13) Multi-factor authentication requires that the system mandates access with multi-factor authentication. Required Extensions Multi-Factor Authentication Features that Support the Certification Multi-Factor Authentication Extension Required Actions Using the Mirth® Connect Multi-Factor Authentication Extension with Duo or TOTP, set up all users to be required to use the selected authentication method. Parent topic: Cures Certification

Mirth® Connect by NextGen Healthcare User Guide

§170.315(d)(7) End-User Device Encryption

(d)(7) End-user device encryption ensures that data is not stored in an non-secure manner on local devices. Required Extensions None Features that Support the Certification Mirth® Connect does not store message information in local cache. Required Actions None Parent topic: Cures Certification

Mirth® Connect by NextGen Healthcare User Guide

§170.315(d)(12) Encrypt Authentication Credentials

(d)(12) Encrypt authentication credentials requires encryption of stored authentication credentials. Required Extensions None Features that Support the Certification SHA256 is the default algorithm used by Mirth® Connect by NextGen Healthcare that creates salted hash values for user passwords. This value is stored in the database, not the user password. SHA256 is approved for Cures, as are SHA384 and SHA512. If a different algorithm is desired, the mirth.properties file can be modified using the digest.algorithm property. For example: digest.algorithm = SHA384 Required Actions None Parent topic: Cures Certification

Mirth® Connect by NextGen Healthcare User Guide

§170.315(d)(9) Trusted Connection

(d)(9) Trusted connection requires the ability to encrypt messages and send through a trusted connection. Required Extensions SSL Manager Features that Support the Certification The SSL Manager extension provides options that ensure encryption and connectivity validation through the use of SSL certificates. Required Actions In your Mirth® Connect channels, enable SSL to establish trusted connections between endpoints. Parent topic: Cures Certification

Mirth® Connect by NextGen Healthcare User Guide

§170.315(d)(1) Authentication, Access Control, Authorization

Cures criteria for §170.315(d)(1) Authentication, Access Control, Authorization. (d)(1) Authentication, Access Control, and Authorization includes limiting access by user name and password, ensuring unique user IDs, and enabling role-based access control. Required Extensions Role-Based Access Control Features that Support the Certification Use of the Role-Based Access Control Extension Validation of username and passwords Prevention of duplicate usernames Creation of user roles that limit/enable viewing and managing different areas of the application Disable user accounts as needed Required Actions Administrator needs to maintain/update valid/invalid users Administrator needs to create roles and assign them to each user based on company’s policies Parent topic: Cures Certification

Mirth® Connect by NextGen Healthcare User Guide

§170.315(g)(4) Quality Management System

Cures criteria for §170.315(g)(4) Quality Management System (g)(4) Quality Management System (QMS) is a set of policies, processes, and procedures required for planning and executing in the core business area of an organization (that is, areas that can impact the organization’s ability to meet customer requirements). All certified products are required to adhere to this requirement. Mirth® Connect uses CFR 21 Part 820, a recognized federal government QMS, in the development, testing, implementation, and maintenance for all certified criteria. Mirth® Connect is certified to meet the (g)(4) Quality Management System requirement. Parent topic: Cures Certification

§170.315(g)(5) Accessibility-Centered Design

Recommendations

§170.315(d)(13) Multi-Factor Authentication

§170.315(d)(7) End-User Device Encryption

§170.315(d)(12) Encrypt Authentication Credentials

§170.315(d)(9) Trusted Connection

§170.315(d)(1) Authentication, Access Control, Authorization

§170.315(g)(4) Quality Management System

§170.315(d)(13) Multi-Factor Authentication

§170.315(d)(7) End-User Device Encryption

§170.315(d)(12) Encrypt Authentication Credentials

§170.315(d)(9) Trusted Connection

§170.315(d)(1) Authentication, Access Control, Authorization

§170.315(g)(4) Quality Management System