Maximus FHIR API
ONC §170.315(g)(10)

API terms and conditions

The terms, conditions, fees and limitations that apply to the Maximus FHIR API, disclosed under 45 CFR 170.404(a)(2).

These terms govern access to and use of the Maximus EHR standardized FHIR API, certified to ONC criterion §170.315(g)(10). They are published in satisfaction of the API Conditions and Maintenance of Certification at 45 CFR 170.404(a)(2), which requires that all terms, conditions, fees and limitations applying to the API be publicly and transparently disclosed.

1. Access

  • This documentation is published at https://documents.maximus.care and is freely and publicly accessible. No account, registration, fee, agreement or non-disclosure obligation is required to read it.
  • Applications must be registered before they can obtain an access token.
  • Registration is open to any developer. It is reviewed for security and technical completeness, not for competitive position, business model or whether the application competes with Maximus.
  • Maximus will not refuse registration, or impose delay, on grounds unrelated to security, technical conformance or legal obligation.

2. Fees

No fee is charged for any of the following:

  • Reading this documentation.
  • Registering an application.
  • Obtaining or refreshing access tokens.
  • Calling the certified API capabilities described in these pages, including those listed as additional data in US Core and USCDI support.
  • Patient-directed access to a patient's own electronic health information.

This disclosure covers the certified API capabilities described in this documentation. Should a fee permitted under 45 CFR 170.404(a)(2) ever apply to any capability, it will be disclosed here in full, including how it is calculated, before it takes effect.

3. Permitted use

A registered application may:

  • Read electronic health information on behalf of a patient who has authorized it.
  • Read electronic health information on behalf of an authorized provider user, within that user's own permissions.
  • Perform population-level export where a system/ scope has been granted for that purpose.

4. Prohibited use

An application must not:

  • Access data beyond the scope the user authorized, or attempt to circumvent scope or patient context enforcement.
  • Share, sell or transfer access tokens, refresh tokens or client credentials to any other party.
  • Misrepresent its identity, its developer or its purpose to users or to Maximus.
  • Probe, scan or test the security of the API outside a written authorization to do so.
  • Use the API in a way that degrades service for other users, including excessive request rates.
  • Retain patient data beyond what its disclosed purpose requires, or use it for a purpose the user was not told about.

5. Developer responsibilities

  • Safeguard credentials. Client secrets and refresh tokens must be stored securely and never embedded in a public client or committed to source control.
  • Apply the law. Developers are independently responsible for their obligations under HIPAA and any other applicable law. Acting as a business associate, where that applies, requires an appropriate agreement.
  • Be transparent with users. Tell users what data the application collects, why, and with whom it is shared, before they authorize it.
  • Report incidents. Notify Maximus promptly of any suspected compromise of credentials or patient data.
  • Request the minimum. Request the narrowest scopes that meet the need.

6. Service levels and limitations

LimitationDetail
Read-onlyThe API supports read and search. It does not support create, update or delete.
Formatapplication/fhir+json only. XML is not supported.
Rate limitingRequests may be rate limited to protect service availability. Limits are applied per client; a limited request returns 429.
AvailabilityThe API is provided without a specific uptime commitment unless one is separately agreed in writing. Planned maintenance is notified to registered technical contacts.
Reference resolution_include and _revinclude are not supported.

7. Changes to the API

  • Maximus may change the API to maintain certification, correct defects or address security issues.
  • Breaking changes will be notified in advance to registered technical contacts wherever practicable, except where a security issue requires immediate action.
  • This documentation is the authoritative description of the API. The date at the top of each page records when it was last revised.

8. Suspension

Maximus may suspend or revoke an application's access where there is a credible security concern, a breach of these terms, or a legal requirement to do so. Where access is suspended, Maximus will state the reason to the registered technical contact and, where the cause can be remedied, what remedy is required. Suspension will not be used to disadvantage a competing application.

9. No information blocking

Maximus does not engage in practices that constitute information blocking under section 3022 of the Public Health Service Act. These terms are not intended to and must not be read to restrict, discourage or delay the access, exchange or use of electronic health information except where required or permitted by law.

10. Contact

Questions about these terms, about registration, or about the API should be directed through the registration and contact form.

Document status

Last revised 18 November 2026. Where these terms and the Maximus EHR certification listing on the ONC Certified Health IT Product List differ, the CHPL listing governs.

Last updated 18 November 2026

Maximus EHR — documentation published for the ONC Health IT Certification Program.

See the API terms and conditions. Where this documentation and the Maximus EHR listing on the ONC Certified Health IT Product List differ, the CHPL listing governs.

© 2026 MaxRemind Inc. All rights reserved.