Business Associate Agreement
This is the agreement Oraform signs with every practice in the United States before any patient information is collected. A practice signs it in the Oraform dashboard; this page is the same text, so it can be read and reviewed before anyone signs anything.
Practices outside the United States are covered by a Data Processing Agreement instead. See also who can process information on our behalf and how patient data is protected.
Version 1.3
1. Parties, purpose and definitions
This Business Associate Agreement ("Agreement") is entered into between the healthcare practice that signs it in the Oraform dashboard ("Covered Entity") and Kliir Solutions Inc., doing business as Oraform ("Business Associate"), effective on the date the Covered Entity signs it ("Effective Date").
Business Associate provides Covered Entity with a hosted patient-forms service: building digital versions of the practice's forms, collecting patient answers, signatures and uploaded files, and making submissions available to practice staff (the "Services"). Providing the Services requires Business Associate to create, receive, maintain or transmit Protected Health Information on Covered Entity's behalf. This Agreement sets out how that PHI is protected, as required by HIPAA.
Definitions. Capitalized terms not defined here have the meanings in 45 C.F.R. Parts 160 and 164.
- HIPAA means the Health Insurance Portability and Accountability Act of 1996, the HITECH Act, and their implementing regulations, including the Privacy, Security, Breach Notification and Enforcement Rules, as amended.
- PHI means Protected Health Information (45 C.F.R. 160.103) that Business Associate creates, receives, maintains or transmits for or on behalf of Covered Entity, including electronic PHI.
- Breach, Security Incident, Unsecured PHI, Individual, Subcontractor and Required by Law have the meanings in 45 C.F.R. 164.402, 164.304 and 160.103.
- Master Agreement means the agreement under which Covered Entity subscribes to the Services.
2. Permitted uses and disclosures of PHI
Business Associate may use and disclose PHI only as follows:
- To perform the Services for Covered Entity under the Master Agreement and this Agreement.
- For Business Associate's proper management and administration, or to carry out its legal responsibilities, provided that any disclosure is Required by Law or Business Associate obtains reasonable written assurance that the recipient will keep the PHI confidential, use it only for the purpose disclosed, and report any breach of confidentiality.
- As Required by Law.
Business Associate will not:
- Use or disclose PHI in any manner that would violate the Privacy Rule if done by Covered Entity.
- Sell PHI, or use or disclose PHI for marketing or advertising.
- Provide data aggregation services for Covered Entity, or combine its PHI with other customers' data, unless Covered Entity separately agrees in writing.
- Use PHI to train artificial-intelligence models. Any AI processing of PHI (for example, reading an insurance card the patient uploads) occurs only through a Subcontractor covered by a business associate agreement, only to deliver the feature to Covered Entity, and only when Covered Entity has that feature turned on.
Business Associate will limit its uses, disclosures and requests of PHI to the minimum necessary to accomplish the intended purpose.
3. Business Associate obligations and safeguards
Business Associate will comply with the HIPAA Security Rule (45 C.F.R. Part 164, Subpart C) for electronic PHI and use appropriate administrative, physical and technical safeguards to prevent any use or disclosure not permitted by this Agreement. Without limiting that duty, Business Associate currently maintains:
- Encryption: PHI encrypted in transit (TLS 1.2 or higher) and at rest, using customer-managed encryption keys.
- Hosting: PHI stored and processed in the United States, on infrastructure provided by a Subcontractor that has signed a business associate agreement with Business Associate.
- Access controls: unique user accounts; two-factor authentication required by the Services for every member of Covered Entity's staff before any access to PHI, with no exemption by role; role-based permissions; and least-privilege access for Business Associate personnel, who reach internal administrative systems only through Business Associate's Google Workspace single sign-on, restricted to verified accounts on Business Associate's own domain that hold an explicitly granted administrative role.
- Audit logs: records of access to and changes to PHI, retained for at least six years.
- Patient email: Business Associate sends patients a limited set of emails on Covered Entity's behalf: links to resume an unfinished form, reminders to complete a form, replies and confirmations for inquiries a patient sends Covered Entity, and, where Covered Entity enables them, review requests. Resume links, reminders, inquiry emails and review requests are all sent through Google Workspace. Service follow-ups, where Covered Entity turns them on, are to be sent through Amazon Web Services (Amazon SES); that capability is contracted but is not yet in use and has carried no patient email. Both providers are covered by business associate agreements with Business Associate. They contain Covered Entity's name and a link, and never contain form answers or other health information. A resume link alone reveals no answers: before saved answers are shown, the patient must confirm a detail Covered Entity chooses (date of birth, the last four digits of their phone number, or postal code). Five incorrect attempts lock the saved form, revoke the link and delete the saved copy. Where a saved form contains none of those details, a patient continuing on the same device may not be asked to confirm one. Covered Entity may switch patient email off at any time.
- Unfinished forms: a form a patient starts but does not submit is marked abandoned after a period of inactivity Covered Entity sets, 48 hours by default. Where a form is still in progress seven days after the patient's last activity, its answers and any files the patient uploaded are permanently deleted at that point. Answers on a form already marked abandoned are permanently deleted once the retention period Covered Entity has configured for unfinished forms has passed, measured from the patient's last activity; where Covered Entity has configured no such period, they are retained until Covered Entity or Business Associate deletes them. Deletion removes the stored answers and the uploaded files and runs on an hourly job, so it takes effect within approximately one hour of the applicable period elapsing.
- Workforce: HIPAA training for personnel with access to PHI, and sanctions for violations.
Business Associate will make its internal practices, books and records relating to PHI available to the Secretary of Health and Human Services for purposes of determining compliance with HIPAA.
To the extent Business Associate carries out any of Covered Entity's obligations under the Privacy Rule, it will comply with the requirements of the Privacy Rule that apply to Covered Entity in performing them.
4. Breach and incident reporting
Business Associate will report to Covered Entity:
- Breach of Unsecured PHI: without unreasonable delay and no later than 10 business days after discovery (never later than 60 calendar days). The report will include the Individuals affected (where known), what happened, dates, the PHI involved, steps taken, and the information Covered Entity needs for notices under 45 C.F.R. 164.404.
- Use or disclosure not permitted by this Agreement: without unreasonable delay after discovery, describing what happened and the steps taken.
- Successful Security Incident: without unreasonable delay after discovery, describing what happened and the steps taken.
- Unsuccessful Security Incidents (pings, port scans, blocked log-in attempts, denial-of-service attempts that do not result in unauthorized access): notice is given by this clause, and no further report is required.
A Breach is treated as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to Business Associate. Business Associate will mitigate, to the extent practicable, any harmful effect of an unpermitted use or disclosure known to it. Covered Entity decides whether and how to notify Individuals, regulators and the media.
Reports go to the account owner's email address on file.
5. Subcontractors and individual rights
Subcontractors. Business Associate will ensure that any Subcontractor that creates, receives, maintains or transmits PHI on its behalf agrees in writing to the same restrictions, conditions and requirements that apply to Business Associate under this Agreement (45 C.F.R. 164.502(e)(1)(ii) and 164.308(b)). Current Subcontractors that may handle PHI:
- Google LLC (Google Cloud): hosting, database, file storage and encryption keys; AI processing only when a feature that uses it is turned on. Business associate agreement signed.
- Google LLC (Google Workspace): all patient email Business Associate sends today: reminders, resume links, inquiry replies and confirmations, and review requests. Business associate agreement accepted 14 November 2026. In use for patient email from 13 November 2026.
- Amazon Web Services, Inc. (Amazon SES): patient service follow-up emails, intended to be sent only where Covered Entity turns that feature on. Business associate agreement in place (AWS Organizations BAA, active 7 November 2026). Not in use: sending is switched off in the Amazon SES configuration itself and no sending credentials are deployed, so it has received no PHI. It will not receive PHI until Covered Entity is given the notice described below.
Business Associate will keep this list current in the dashboard and give Covered Entity at least 30 days' notice before adding a Subcontractor that will handle PHI, or before bringing a listed Subcontractor into use for the first time. Payment processing (Stripe) does not receive PHI.
Individual rights. Within 10 business days of Covered Entity's request, Business Associate will:
- Access (164.524): make PHI in a Designated Record Set available to Covered Entity, including in electronic form (the dashboard export provides PDF and Excel/XLSX).
- Amendment (164.526): make amendments to PHI that Covered Entity directs.
- Accounting of disclosures (164.528): provide the information Covered Entity needs to respond to a request for an accounting, and document disclosures as needed to do so.
If an Individual contacts Business Associate directly with such a request, Business Associate will forward it to Covered Entity within 5 business days and will not respond on Covered Entity's behalf unless directed.
6. Covered Entity obligations
Covered Entity will:
- Notify Business Associate of any limitation in its notice of privacy practices, any change in or revocation of an Individual's permission, and any restriction it has agreed to under 45 C.F.R. 164.522, to the extent it affects Business Associate's use or disclosure of PHI.
- Not ask Business Associate to use or disclose PHI in any manner that would not be permitted under the Privacy Rule if done by Covered Entity.
- Be responsible for the content of its forms, for obtaining any consents or authorizations its patients must give, and for its staff's use of their dashboard accounts, including keeping credentials and second factors secure and removing staff who leave.
- Use the Services' configuration (form content, reminder settings, identity check type, timezone) in a way consistent with its own HIPAA obligations.
7. Term, termination, return or destruction of PHI
Term. This Agreement starts on the Effective Date and continues while Business Associate holds PHI on Covered Entity's behalf.
Termination for breach. If either party knows of a pattern of activity or practice of the other that is a material breach of this Agreement, it will give written notice and 30 days to cure. If the breach is not cured, the non-breaching party may terminate this Agreement and the Master Agreement.
Effect of non-payment. Suspension of the Services for non-payment under the Master Agreement does not end this Agreement or Business Associate's obligations to protect PHI. While suspended, Covered Entity keeps read-only access to view and export its data.
Return or destruction. When the Master Agreement ends:
- Covered Entity has 90 days to export its PHI through the dashboard (PDF and Excel/XLSX), and Business Associate will send a final notice before the period ends.
- At the end of that period, Business Associate will destroy all PHI it holds, including copies held by Subcontractors, and confirm destruction in writing on request.
- Encrypted backups are destroyed on their normal rotation. Cloud SQL keeps the 30 most recent daily automated backups and 7 days of write-ahead logs for point-in-time recovery, both in the same region and under the same customer-managed key as the database. Database exports are held in a write-once bucket under a locked 35-day retention policy and purged at 45 days. No copy persists more than 45 days after deletion from production systems.
- If return or destruction is infeasible, Business Associate will extend this Agreement's protections to that PHI and limit further uses and disclosures to the purposes that make return or destruction infeasible.
Survival. Business Associate's obligations under this section survive termination.
8. General terms and signatures
- Amendment. The parties will amend this Agreement as needed to comply with changes in HIPAA. Business Associate may publish an updated version; Covered Entity re-signs it in the dashboard, and the prior version applies until then.
- Interpretation. Any ambiguity is resolved to permit compliance with HIPAA. If this Agreement conflicts with the Master Agreement on the handling of PHI, this Agreement controls.
- No third-party beneficiaries. Nothing in this Agreement gives any right to anyone other than the parties.
- Governing law. The laws of the Province of British Columbia and the federal laws of Canada applicable there, except to the extent preempted by HIPAA.
- Electronic signature. The parties agree this Agreement may be signed electronically in the Oraform dashboard. Business Associate records the signer's name, title, email, date and time, IP address and the version signed, and keeps a PDF copy available to both parties.
Assignment. Business Associate may assign this Agreement, together with the Master Agreement, to an affiliate or to a successor to all or substantially all of the business providing the Services, without Covered Entity's consent, by giving Covered Entity at least 30 days' written notice. The assignee must agree in writing to be bound by this Agreement and must hold PHI under safeguards at least as protective as those described here. Covered Entity may not assign this Agreement without Business Associate's prior written consent, which will not be unreasonably withheld.
Signatures. Covered Entity signs this Agreement electronically in the Oraform dashboard, and the signature record (signer's name, title, email, date and time, IP address and the version signed) forms part of this Agreement. Business Associate: Kliir Solutions Inc., doing business as Oraform, by its Founder & CEO, effective on the same date.