Multi-factor authentication
The factors, use cases and controls through which this Health IT Module authenticates a user's identity through multiple elements.
| Field | Value |
|---|---|
| Product name | Maximus |
| Product version | 1.0 |
| Developer | MaxRemind Inc. |
| Certification number | 15.05.05.3173.MAXR.01.00.1.231031 |
| Criterion | §170.315(d)(13) Multi-factor authentication |
| Date created | 20 September 2023 |
| Date updated | 16 November 2026 |
1. Purpose and scope
This document is the disclosure required by ONC certification criterion §170.315(d)(13), Multi-factor authentication. That criterion asks the health IT developer to describe the use case or use cases in which the Health IT Module supports authentication of a user's identity through multiple elements, using industry-recognized standards.
It states which factors Maximus EHR supports, the use cases in which multi-factor authentication applies, the controls that protect it, and the standard the design is written against.
2. Summary
| Supported | Yes — Maximus EHR supports multi-factor authentication. |
| Factors | Something the user knows (password), plus a one-time passcode delivered out-of-band to something the user has. |
| Channels | Registered email address, or SMS to a registered cell phone. Selected per user. |
| Use cases | Interactive user sign-in, and password reset. |
| Scope | Any Maximus EHR user account. Enabled per user by a practice administrator. |
| Standard | Written against NIST SP 800-63B, Digital Identity Guidelines. |
3. Authentication factors
Authentication combines a knowledge factor with a possession factor. The knowledge factor is the account password. The possession factor is a one-time passcode delivered out-of-band on a channel registered to the user in advance, proving control of that channel.
| Channel | Delivery | Requires |
|---|---|---|
| A one-time passcode is sent to the user's registered email address. | An email address recorded against the user account. | |
| Cell phone (SMS) | A one-time passcode is sent by SMS to the user's registered mobile number. | A cell phone number recorded against the user account. The administration screen refuses to save this option without one. |
A user has exactly one channel selected at a time. It is recorded against the user account and is chosen by the administrator who enables the feature.
4. Use cases
Multi-factor authentication applies in the following use cases.
Interactive user sign-in
| Who it applies to | Any Maximus EHR user for whom an administrator has enabled multi-factor authentication. |
| What happens | After the username and password are accepted, the session is not issued. A one-time passcode is sent by the user's chosen channel and must be presented before access is granted. |
| What it proves | Something the user knows (password) and something the user has (control of the registered email account or mobile number). |
Password reset
| Who it applies to | Any user initiating a password reset. |
| What happens | A one-time passcode is sent to the registered channel and must be presented before a new password can be set. A reset cannot be completed from knowledge of the account identifier alone. |
| What it proves | Control of the registered channel, before any credential change is permitted. |
5. Enabling multi-factor authentication
Multi-factor authentication is configured per user by a practice administrator. It is not self-service, so a user cannot disable their own second factor.
- Sign in to Maximus EHR with an administrator account.
- From the side menu, open Admin Setting, then User Settings.
- Select Users to list the practice's user accounts.
- Open the user and choose Edit.
- Set Multifactor Authentication to Enable.
- Choose the Multifactor Auth Type — Email or Cell Phone.
- Save. The setting takes effect at the user's next sign-in.
6. The authentication sequence
The order matters: the session is never issued on the password alone.
1. User submits username and password
|
2. Credentials verified
|
3. An INTERMEDIATE token is issued. It carries no application
authority - it only records that the password step passed and
identifies the passcode awaiting verification.
|
4. A one-time passcode is generated and sent on the user's
registered channel (email or SMS)
|
5. User submits the passcode
|
6. Passcode checked: correct, unexpired, unused, within the
attempt limit
|
7. Full session token issued -> access granted
If step 6 fails, no session token is issued. The intermediate token cannot be used to reach patient data, and it expires on its own schedule whether or not the passcode is ever presented.
7. Security controls
The following controls apply to every one-time passcode, in both use cases.
| Control | Behaviour |
|---|---|
| Passcode generation | Six numeric digits, drawn from a cryptographically secure random source |
| Passcode lifetime | 5 minutes from issue, re-checked on every verification attempt |
| Verification attempts | 5 per passcode, after which it is rejected and a new one must be requested |
| Request rate limit | 5 passcode requests per user, per use case, per 5-minute window |
| Single use | A verified passcode is marked used and cannot be presented again |
| Session gating | Between password acceptance and passcode verification the user holds only a short-lived intermediate token that carries no application authority. Default lifetime 10 minutes, configurable. |
| Transport | All authentication traffic is carried over TLS 1.2 or above; earlier versions are refused at the handshake |
8. Audit
Every passcode issued is recorded, whether or not it is ever presented. It supports after-the-fact review of who was challenged, when, by which channel, and what happened. Each entry holds:
- Which user the passcode was issued to
- Which use case it belonged to — sign-in, or password reset
- Which channel it was sent by, and the destination it was sent to
- The source address the request came from
- When it was issued, and when it ceased to be valid
- How many verification attempts were made against it
- Whether it was successfully presented, and when
- The practice the user belongs to
Records are retained in line with Maximus EHR's HIPAA retention obligations.
9. Standards referenced
| Standard | Specification |
|---|---|
| NIST SP 800-63B, Digital Identity Guidelines — Authentication and Lifecycle Management | https://pages.nist.gov/800-63-3/sp800-63b.html |
| NIST SP 800-63-3, Digital Identity Guidelines | https://pages.nist.gov/800-63-3/sp800-63-3.html |
How each applies:
- NIST SP 800-63B, Digital Identity Guidelines — Authentication and Lifecycle Management — The industry-recognized standard this design is written against. It defines the out-of-band authenticator pattern used here, and the controls in §5 follow its guidance on passcode lifetime, retry limits and rate limiting.
- NIST SP 800-63-3, Digital Identity Guidelines — The parent publication, which defines the authenticator assurance levels referenced above.
10. Contact
Questions about this disclosure should be directed to MaxRemind Inc. through the contact route given on the Maximus EHR certification page.