Business Associate Agreement
Version 2026-11-13-v1 · Last updated November 13, 2026
At a glance
This summary is for convenience. The numbered sections below are the agreement.
- Your clients' records belong to your practice. CoralEHR uses them only to run the service for you.
- We never sell client information, use it for advertising, or use it to train AI models.
- Records are encrypted in transit and at rest, and hosted on AWS in the United States.
- Every vendor that handles client information for us is named in Schedule A and has signed its own agreement with us.
- If something goes wrong, we tell you within 72 hours.
- If you leave, you can export your records, and we then delete them.
1. Parties and purpose
1.1 Parties. This Business Associate Agreement ("Agreement") is between the practice named on the signature page ("Practice"), a covered entity, and Simplest Healthcare Inc., a Delaware corporation doing business as CoralEHR ("CoralEHR"), its business associate.
1.2 Services. CoralEHR provides the Practice with an electronic health record and practice management service: clinical notes and documents, scheduling, a client portal, secure messaging, telehealth, billing, and optional AI features (the "Services"). To provide them, CoralEHR creates, receives, maintains and transmits Protected Health Information ("PHI") on the Practice's behalf.
1.3 Purpose. This Agreement sets out how CoralEHR protects that PHI, as required by HIPAA and its regulations at 45 CFR Parts 160 and 164, the HITECH Act, and, for substance use disorder records, 42 CFR Part 2. It forms part of the CoralEHR Terms of Service, takes effect when the Practice signs it (the "Effective Date"), and replaces any earlier business associate agreement between the parties.
1.4 Ownership. As between the parties, the Practice owns its client records.
2. Definitions
2.1 HIPAA terms. Breach, Designated Record Set, Individual, Protected Health Information, Required by Law, Secretary, Security Incident, Subcontractor and Unsecured PHI have the meanings given in the HIPAA Rules.
2.2 HIPAA Rules. The Privacy, Security, Breach Notification and Enforcement Rules at 45 CFR Parts 160 and 164, as amended.
2.3 PHI. In this Agreement, PHI means only the PHI that CoralEHR handles on the Practice's behalf.
2.4 Subprocessor. A Subcontractor of CoralEHR that handles PHI.
3. How CoralEHR may use PHI
3.1 Providing the Services. CoralEHR may use and disclose PHI only as needed to provide the Services, as the Practice directs, or as Required by Law. CoralEHR will not use or disclose PHI in any way that would violate the HIPAA Rules if done by the Practice, except as section 3.2 allows.
3.2 Running CoralEHR. CoralEHR may use PHI for its own proper management and administration and to meet its legal responsibilities. It may disclose PHI for those purposes only if the disclosure is Required by Law, or if the recipient agrees in writing to keep the PHI confidential, use it only for the stated purpose, and tell CoralEHR of any breach of confidentiality.
3.3 Minimum necessary. CoralEHR will use, disclose and request only the minimum PHI needed for the purpose.
3.4 What CoralEHR will not do. CoralEHR will not:
- • sell PHI;
- • use or disclose PHI for marketing or advertising;
- • use PHI to train AI models, or allow a Subprocessor to do so;
- • de-identify PHI for its own use without the Practice's written permission.
4. CoralEHR's commitments
4.1 Compliance. CoralEHR will comply with the HIPAA Rules that apply to business associates. Where CoralEHR carries out one of the Practice's obligations under the Privacy Rule, it will meet the requirements that apply to the Practice.
4.2 Safeguards. CoralEHR will maintain administrative, physical and technical safeguards that meet the HIPAA Security Rule (45 CFR Part 164, Subpart C) and prevent any use or disclosure of PHI that this Agreement does not permit. Today these include:
| Safeguard | What CoralEHR does |
|---|---|
| Encryption | PHI is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256). |
| Hosting | PHI is stored in AWS data centers in the United States: Northern Virginia, with encrypted backups in Oregon. Only HIPAA-eligible AWS services are used, under a business associate agreement with AWS. |
| Access | Each member sees only what their role needs. Two-step sign-in is available to every member, and the Practice owner can require it. Members are signed out when idle. |
| Audit trail | Access to client records and changes to them are logged. Logs are kept for six years. |
| Backups | Encrypted backups are taken daily, with a copy in a second US region. |
| Telehealth | Video sessions are encrypted. Sessions are recorded only if the Practice turns on session recordings for supervision. Recordings are stored encrypted and deleted after the period the Practice sets. |
| People | CoralEHR has a designated security officer, trains its workforce on HIPAA, and limits staff access to PHI to what supporting the Practice requires. |
CoralEHR may improve these measures over time and will not reduce the overall level of protection.
4.3 Client rights. The Practice can view and correct its records directly in CoralEHR. Where the Practice needs CoralEHR's help to respond to an Individual, CoralEHR will:
- • make PHI in a Designated Record Set available within 15 business days (45 CFR § 164.524);
- • make PHI available for amendment, and incorporate amendments, within 15 business days (45 CFR § 164.526);
- • provide the information needed for an accounting of disclosures within 30 days (45 CFR § 164.528).
If an Individual sends a request to CoralEHR directly, CoralEHR will refer them to the Practice.
4.4 Government access. CoralEHR will make its internal practices, books and records relating to PHI available to the Secretary of the U.S. Department of Health and Human Services to determine compliance with the HIPAA Rules.
4.5 Mitigation. CoralEHR will mitigate, as far as practicable, any harmful effect of a use or disclosure of PHI that violates this Agreement.
5. Incident and breach reporting
5.1 What CoralEHR reports, and when. CoralEHR will notify the Practice without unreasonable delay, and no later than 72 hours after discovering:
- • any use or disclosure of PHI that this Agreement does not permit;
- • any successful Security Incident affecting PHI;
- • any Breach of Unsecured PHI.
5.2 What the notice contains. The first notice gives what is known at the time. CoralEHR will complete it without unreasonable delay, and within 30 days of discovery, with:
- • what happened and when;
- • the types of PHI involved;
- • each Individual affected, to the extent possible;
- • what CoralEHR has done to contain the incident and prevent a repeat;
- • what the Practice or its clients can do to protect themselves.
5.3 Working together. CoralEHR will cooperate with the Practice's investigation and give the Practice the information and reasonable help it needs to meet its own notification duties under 45 CFR §§ 164.404 to 164.408 and state law.
5.4 Blocked attempts. Attempts that are blocked, such as pings, port scans and failed sign-ins, happen constantly on any internet service. This section is the Practice's notice of them. CoralEHR will provide a summary on request.
5.5 How notice is given. By email to the Practice owner's address on the account.
6. Substance use disorder records
6.1 Qualified service organization. If the Practice is a program covered by 42 CFR Part 2, or PHI includes records protected by Part 2 ("Part 2 Records"), CoralEHR acts as the Practice's qualified service organization. CoralEHR:
- • acknowledges that in receiving, storing, processing or otherwise dealing with Part 2 Records, it is fully bound by 42 CFR Part 2;
- • will, if necessary, resist in judicial proceedings any effort to obtain access to Part 2 Records, except as Part 2 permits;
- • will not use or disclose Part 2 Records in any civil, criminal, administrative or legislative proceeding against a client without the client's written consent or a court order that meets Part 2;
- • will use and redisclose Part 2 Records only as needed to provide the Services and as Part 2 permits, and will hold its Subprocessors to the same terms.
6.2 Breach reporting. Section 5 applies to Part 2 Records in the same way.
7. Subprocessors
7.1 Who they are. CoralEHR uses the Subprocessors named in Schedule A to help provide the Services. Each one has signed a business associate agreement with CoralEHR that holds it to the same restrictions and conditions that apply to CoralEHR under this Agreement.
7.2 Changes. CoralEHR will give the Practice at least 30 days' notice by email before a new Subprocessor starts handling PHI. The current list is published at coralehr.com/baa.
7.3 Responsibility. CoralEHR remains responsible to the Practice for how its Subprocessors handle PHI.
7.4 AI features. AI features are optional. The Practice owner can turn them off for the whole practice in settings, and no PHI is then sent to the AI Subprocessors in Schedule A.
8. The Practice's commitments
The Practice will:
- • use the Services in line with the HIPAA Rules and obtain any consent its use requires, including client consent to recording or AI-assisted note-taking where the law requires it;
- • tell CoralEHR about any limit in its notice of privacy practices, any change to or withdrawal of a client's permission, and any restriction it has agreed to under 45 CFR § 164.522, where these affect how CoralEHR handles PHI;
- • not ask CoralEHR to use or disclose PHI in a way that would violate the HIPAA Rules if done by the Practice;
- • give each member their own sign-in, remove access promptly when someone leaves, and tell CoralEHR promptly at support@coralehr.com if it suspects unauthorized access.
9. Term and termination
9.1 Term. This Agreement starts on the Effective Date and continues for as long as the Practice uses the Services.
9.2 Ending for cause. If either party materially breaches this Agreement, the other may give written notice of the breach. If the breach is not cured within 30 days, or cannot be cured, the other party may end this Agreement and the Practice's subscription immediately by written notice.
9.3 Export and deletion. For 60 days after termination, the Practice may export its records as described in the Terms of Service. CoralEHR will delete the Practice's PHI from its active systems within 90 days after termination, and will confirm deletion in writing on request.
9.4 Backups and logs. Encrypted backups and audit logs cannot be edited to remove one practice's data. CoralEHR will keep protecting them under this Agreement, use them only to restore the service or meet a legal duty, and delete them on their fixed schedule, no later than six years after they were created.
9.5 Survival. Sections 3 to 6, 9.3 and 9.4 continue to apply for as long as CoralEHR holds any of the Practice's PHI.
10. General
10.1 Changes. The parties will amend this Agreement as needed to keep it compliant with the HIPAA Rules and other applicable law. CoralEHR will give the Practice at least 30 days' notice of a new version. Any other change needs both parties' written agreement, which may be electronic.
10.2 Interpretation. Any ambiguity is resolved in favor of compliance with the HIPAA Rules. A reference to a regulation means that regulation as amended. If this Agreement and the Terms of Service conflict on the handling of PHI, this Agreement controls.
10.3 Stricter state law. Where a state law protects client information more strictly than HIPAA, CoralEHR will follow the stricter rule that applies to it.
10.4 No third-party rights. This Agreement gives rights only to the Practice and CoralEHR, and binds their successors.
10.5 Governing law. California law governs this Agreement, except where federal law applies.
10.6 Notices. Notices to CoralEHR go to support@coralehr.com, with a copy to Simplest Healthcare Inc., 2261 Market Street STE 85566, San Francisco, CA 94114. Notices to the Practice go to the Practice owner's email address on the account.
10.7 Electronic signature. The Practice signs this Agreement electronically in CoralEHR by typing the signer's name. That is a valid signature under the federal E-SIGN Act (15 U.S.C. § 7001) and state electronic transactions laws. The signer confirms that they are authorized to sign for the Practice. CoralEHR gives the Practice a signed copy.
Schedule A: Subprocessors and service providers
Subprocessors that handle PHI. Each has a business associate agreement with CoralEHR.
| Subprocessor | What it does | PHI it handles |
|---|---|---|
| Amazon Web Services, Inc. | Hosting, database, file storage, backups, email delivery, telehealth video (Amazon Chime SDK) and security monitoring, in the United States | All PHI in the Services |
| Deepgram, Inc. | Speech-to-text for dictation and the AI note taker | Session audio and dictated speech, with client names as spelling hints. Deepgram does not keep audio or transcripts after processing and does not use them to train models. |
| Anthropic, PBC | AI assistant, note drafting and tidy-up | The chart text and transcript a member is working with. Processed in the United States and not used to train models. |
Service providers that receive no PHI. Listed for transparency.
| Provider | What it does | What it receives |
|---|---|---|
| Stripe, Inc. | Card payments, for practices that take payments through CoralEHR | From CoralEHR: the payment amount, the Practice's card-statement name, and anonymous reference numbers for the invoice, client and practice that mean nothing outside CoralEHR. Clients enter their payment details on Stripe's own secure page. Stripe acts as a payment processor, which HIPAA does not treat as a business associate (Social Security Act § 1179). |
| Cloudflare, Inc. | Checks that visitors to a public booking page are people, not bots | Standard browser signals, such as IP address. No client record. |
| Sentry (Functional Software, Inc.) | App crash and error reporting | Technical error reports: the type of error and where in the app it happened. User details, request data and free text are removed before a report is sent. No client record. |
Signatures
Simplest Healthcare Inc., doing business as CoralEHR
2261 Market Street STE 85566, San Francisco, CA 94114
Notices: support@coralehr.com
Signed by Arhaan Gupta, Co-founder and Chief Executive Officer, on 2026-11-13
Practice
Practices sign this agreement inside CoralEHR.