Maximus EHR documentation
Documentation published for the ONC Health IT Certification Program.
This site publishes the technical documentation for Maximus EHR, certified under the ONC Health IT Certification Program. Everything here is freely and publicly accessible: no account, registration, fee or agreement is required to read it.
Documents
FHIR API documentation
§170.315(g)(10)Standardized API for patient and population services. Syntax, scopes, authorization, resource reference and terms, for developers building applications against Maximus EHR.
For: Application developers
Read the API documentation →Application access
§170.315(g)(7), (g)(9)How an application obtains an identifier for a single patient, and how it requests all of that patient's data as a summary record, for a date range. Both are served by the same FHIR API.
For: Application developers and certification reviewers
Read the application access documentation →Electronic Health Information export
§170.315(b)(10)The format and structure of the EHI export: the archive layout, the CSV conventions, how the files relate, and the full column reference.
For: Data engineers receiving an export
Read the export documentation →Multi-factor authentication
§170.315(d)(13)The factors, use cases and controls through which Maximus EHR authenticates a user's identity through multiple elements.
For: Practice administrators and security reviewers
Read the authentication disclosure →Certification
| Item | Value |
|---|---|
| Developer | MaxRemind Inc. |
| Product | Maximus EHR |
| Product version | 1.0 |
| Certification number | 15.05.05.3173.MAXR.01.00.1.231031 |
| Certification body | SLI Compliance |
Where this documentation and the Maximus EHR listing on the ONC Certified Health IT Product List differ, the CHPL listing governs.
Getting access
Reading this documentation requires nothing. To call the API, an application must first be registered with the authorization server — submit the access request form. Registration is free and is reviewed for security and technical completeness only.
Questions about anything published here can be sent through the contact form.