Developers
FHIR API Terms of Use
Last updated: November 19, 2026
These terms govern access to and use of the ReasonEMR certified HL7® FHIR® application programming interface (the “API”), provided by ReasonWorks AI Inc. (“ReasonEMR”, “we”). Technical documentation is available on our developer page. Clinics that subscribe to ReasonEMR are also bound by our Terms of Service.
1. Definitions
- API User — a person or organization that accesses the API, including app developers, patients and their authorized representatives, and clinics.
- Clinic — a ReasonEMR customer whose health information is made available through the API (an “API Information Source”).
- App — any software that connects to the API.
2. Fees
Access to the API is free of charge. ReasonEMR does not charge patients, app developers, or clinics any fee to read this documentation, register an App, discover service base URLs, use dynamic client registration, or use the API in production. If this ever changes, any fee will be published here in advance, in plain language, and applied uniformly.
3. Registration
- Apps may register themselves using OAuth 2.0 Dynamic Client Registration, or be registered by a Clinic administrator in ReasonEMR (Settings → API / Apps).
- Where we verify an API User's authenticity, we do so using objective criteria applied the same way to every API User, and complete verification within 10 business days of a request. Once verified, we register and enable the App for production use within 5 business days.
- You must provide accurate registration information (including your App's name and redirect URIs) and keep client credentials confidential. Each set of credentials is for a single App.
4. Patient-directed apps
Patients have the right to use the App of their choice to access their own health information. When a patient authorizes an App, the patient decides which data to share and may revoke access at any time in the patient portal (Settings → Connected apps). ReasonEMR does not require a business associate agreement, and does not perform security vetting, as a condition of a patient connecting an App of their choice, except as needed to protect the security of ReasonEMR systems or as required by law.
5. Clinician and population-health apps
Apps that access data on behalf of a Clinic (for example, EHR launch or bulk data export) require that Clinic's authorization. Where your App will create, receive, maintain, or transmit protected health information on a Clinic's behalf, you are responsible for any business associate agreement HIPAA requires between you and that Clinic.
6. Your obligations
- Comply with all applicable laws, including, as applicable, HIPAA, the FTC Act, and the FTC Health Breach Notification Rule.
- Publish a privacy policy, in plain language, that explains what data your App collects, how it is used, and whether it is shared or sold — and follow it.
- Access only the data the user or Clinic authorized, using the scopes granted, and protect data in transit and at rest with reasonable security safeguards.
- Do not misrepresent your identity or your App, attempt to bypass authorization or security controls, or interfere with the API or place an unreasonable load on it.
- Promptly notify affected users, and us at baljinder@reasonworks.ai, of any security incident involving data obtained through the API.
7. Your rights
You keep all rights to your App and your intellectual property. ReasonEMR does not require royalties, revenue sharing, exclusivity, non-compete commitments, a license to your App, or access to your App's data as a condition of using the API, and we offer these terms on the same basis to every API User — including our own products. Subject to these terms, you may use the API to develop, market, and distribute interoperable Apps.
8. Changes to the API
We will give API Users notice and a reasonable opportunity to update their Apps before making changes that would affect them, except where an immediate change is needed to address a security threat or other urgent risk. We will make reasonable efforts to maintain compatibility.
9. Suspension
We may suspend or revoke an App's credentials if it poses a security risk to ReasonEMR, Clinics, or patients, violates the law, or materially breaches these terms. Where practicable, we will give notice and an opportunity to cure. Suspension decisions are based on objective criteria applied uniformly.
10. Support
Questions, registration requests, and incident reports: baljinder@reasonworks.ai.
11. Disclaimers and liability
The API is provided “as is”. To the maximum extent permitted by law, ReasonEMR disclaims all implied warranties and is not liable for any indirect, incidental, special, consequential, or punitive damages arising from use of the API. You are responsible for your App and for how it uses data obtained through the API.
12. Governing law
These terms are governed by the laws of the State of Texas, without regard to conflict-of-law principles. Disputes will be resolved in the state or federal courts located in Travis County, Texas.
13. Updates to these terms
We may update these terms. Material changes will be posted on this page with a new “Last updated” date before they take effect.