Skip to policy
HUVA
PrivacyTermsSecurityBAAResponsibilities
HUVER, INC. / HUVA

HUVA Business Associate Agreement

The agreement for authorized handling of protected health information on behalf of a healthcare organization.

Effective on recorded acceptance Version 2026-11-05.1

Download this versionPermanent document link

At a glance

  • An authorized representative accepts for the named organization through the designated BAA acceptance process.
  • An individual or team member's acknowledgment does not execute an organization BAA.
  • Execution does not activate PHI processing or establish EHR access rights; implementation conditions still apply.
On this page
  1. About this document
  2. 1. Definitions
  3. 2. Permitted Uses and Disclosures
  4. 3. Safeguards and Security Controls
  5. 4. Reporting and Breach Response
  6. 5. Subcontractors
  7. 6. Individual Rights and Regulatory Support
  8. 7. Covered Entity Responsibilities
  9. 8. Remote and Cross Border Access
  10. 9. Term, Termination, and Return or Destruction
  11. 10. Miscellaneous
  12. Electronic execution
  13. Exhibit A – Covered Services
  14. Exhibit B – Pre-Implementation Conditions

About this document

This Business Associate Agreement ("BAA") is between the organization identified by its full legal name in the electronic BAA acceptance record or in a separately executed agreement ("Covered Entity") and Huver, Inc., a Delaware corporation with its business address at 1111B South Governors Avenue, STE 34419, Dover, DE 19904, United States ("Business Associate" or "HUVER"). Covered Entity and Business Associate are each a "Party" and collectively the "Parties."

HUVER offers this BAA for electronic acceptance and agrees to be bound when an authorized representative of Covered Entity accepts it through HUVA's designated BAA acceptance process. The representative must provide Covered Entity's full legal name and their typed name, confirm their authority to bind Covered Entity, and submit the acceptance. The "Effective Date" is the acceptance timestamp recorded by HUVA for the successful acceptance of this version, unless the Parties specify another effective date in a separately executed agreement. The account acceptance record identifies Covered Entity, the representative and their stated capacity and authority, this BAA version, and the acceptance timestamp. Acknowledgment by an individual or organization member who does not have signing authority does not execute this BAA or bind an organization.

If the Parties already have a separately signed BAA in force, that agreement continues to govern unless both Parties amend or replace it in accordance with its terms. Publication or acknowledgment of this BAA does not by itself amend or replace such an agreement.

This BAA supplements and is incorporated into each master services agreement, accepted Order Form, statement of work, the applicable HUVA Platform Terms of Use, or other written arrangement between the Parties under which Business Associate provides services that involve the creation, receipt, maintenance, or transmission of PHI on behalf of Covered Entity (collectively, the "Underlying Agreement"). This BAA does not independently order, authorize, or activate any Service, permit PHI in HUVA Chat, or grant access to an EHR or another third-party system. Exhibit B's pre-implementation conditions continue to apply.

1. Definitions

1.1 Catch-All Definition. Capitalized terms used but not otherwise defined in this BAA have the meanings assigned to them under the HIPAA Rules.

1.2 “Applicable Law” means all federal, state, and other laws, rules, regulations, and binding governmental requirements applicable to a Party’s performance under this BAA, including the HIPAA Rules.

1.3 “AI Model” means any machine-learning, generative artificial intelligence, or automated speech-recognition model used by Business Associate or a Subcontractor to provide the Services.

1.4 “HIPAA Rules” means the Privacy, Security, Breach Notification, and Enforcement Rules at 45 C.F.R. Parts 160 and 164, as amended.

1.5 “Material Security Incident” means a Security Incident that results in, or is reasonably suspected to involve, unauthorized access to, acquisition, Use, Disclosure, modification, destruction, or material unavailability of PHI, or a material compromise of systems used to process PHI.

1.6 “PHI-Derived Data” means any transcript, summary, draft note, prompt, model input or output, coding suggestion, embedding, index, or other data created from or containing PHI through the Services, but only to the extent such data constitutes PHI under the HIPAA Rules. PHI-Derived Data does not include information that has been de-identified in accordance with 45 C.F.R. § 164.514.

1.7 “Services” means the services provided or to be provided by Business Associate to Covered Entity under one or more Underlying Agreements, solely to the extent Business Associate creates, receives, maintains, or transmits PHI on behalf of Covered Entity in connection with those services. This BAA does not itself order, authorize, or activate any service or grant Business Associate any right to access an EHR or other third-party system. The scope, functionality, and activation of each service are governed by the applicable Underlying Agreement.

1.8 “EHR” means an electronic health record or electronic medical record system, including eClinicalWorks (“eCW”), used by Covered Entity in connection with the Services.

2. Permitted Uses and Disclosures

2.1 Business Associate may Use or Disclose PHI only as necessary to perform the Services, as permitted by this BAA, to comply with Covered Entity’s lawful and documented instructions, or as Required by Law. Business Associate shall not Use or Disclose PHI in a manner that would violate the Privacy Rule under Subpart E of 45 C.F.R. Part 164 if done by Covered Entity, except as expressly permitted for a Business Associate under the HIPAA Rules.

2.2 Business Associate may Use PHI for its proper management and administration or to carry out its legal responsibilities. Business Associate may Disclose PHI for those purposes only if the Disclosure is Required by Law or Business Associate obtains reasonable assurances from the recipient that the PHI will remain confidential, will be Used or further Disclosed only as Required by Law or for the purpose for which it was Disclosed, and that the recipient will notify Business Associate of any breach of confidentiality of which it becomes aware.

2.3 Business Associate shall make reasonable efforts to limit its Uses, Disclosures, and requests for PHI to the Minimum Necessary to accomplish the intended purpose, to the extent the Minimum Necessary standard applies. Business Associate shall comply with Covered Entity’s written Minimum Necessary instructions that are communicated to Business Associate and reasonably applicable to the Services.

2.4 Business Associate shall not sell PHI or Use or Disclose PHI for marketing, advertising, fundraising, or any purpose not expressly permitted by this BAA. Business Associate shall not Use PHI or PHI-Derived Data to train, fine-tune, evaluate, or improve a general-purpose, shared, or cross-customer AI Model. Any customer-dedicated training or tuning requires Covered Entity’s prior written authorization and must be performed solely to provide the Services to Covered Entity.

2.5 Business Associate may de-identify PHI only with Covered Entity’s prior written authorization and in accordance with the HIPAA Rules, and shall not re-identify or permit re-identification except as expressly authorized in writing and permitted by Applicable Law.

2.6 Business Associate may disclose PHI to a Subcontractor or other third-party service provider only as permitted by this BAA and the applicable Underlying Agreement and, where required by the HIPAA Rules, pursuant to an applicable written business associate agreement. Before permitting such provider to process PHI, Business Associate shall reasonably verify that the provider and service used are within the scope of the applicable business associate agreement and are configured consistently with the retention, data-use, and other material processing conditions agreed by the Parties. Business Associate shall maintain current records of the applicable providers and services and shall make information reasonably necessary to confirm compliance with this Section available to Covered Entity upon reasonable request.

2.7 Business Associate shall not permit a Subcontractor to Use PHI or PHI-Derived Data for the Subcontractor’s own model training, product improvement, benchmarking, advertising, or any purpose other than providing the approved Services.

2.8 To the extent the Services generate clinical, coding, or other patient-care-related output, such output shall be treated as draft assistance and shall not be incorporated into Covered Entity’s legal medical record or submitted for billing unless reviewed and approved by appropriately qualified Covered Entity personnel. Business Associate shall maintain reasonable controls designed to support such review and approval. Covered Entity remains responsible for clinical judgment, diagnosis, coding, patient care, and final record content.

2.9 To the extent a Service may modify data in an EHR or other clinical system before final user confirmation, Business Associate shall maintain reasonable controls designed to limit the modification to fields approved by Covered Entity; require initiation or confirmation by an authorized user; verify the applicable patient and encounter; and record the material action in an audit log. The applicable functionality and controls shall be described in the applicable Underlying Agreement or implementation schedule.

2.10 To the extent a Service permits the transfer of draft content to an EHR or the finalization of a clinical record, Business Associate shall maintain reasonable controls designed to require an authorized Covered Entity user to review the draft, verify the resulting entry, and separately authorize any finalization action. The applicable roles, authorization, failure-handling, and audit requirements shall be described in the applicable Underlying Agreement or implementation schedule.

2.11 To the extent the Services include automated administrative transactions, Business Associate may process routine appointment lookup, creation, modification, cancellation, and confirmation without case-by-case human approval only within written rules approved by Covered Entity. Business Associate shall route patient-match uncertainty, clinical content, rule conflicts, failed or duplicate transactions, and other agreed exceptions to authorized Covered Entity personnel and shall maintain audit records of material actions. Patient communications, including any recording or transcription, may be performed only through the channels, templates, caller-identification settings, and notice or consent conditions approved by Covered Entity. Covered Entity remains responsible for its administrative rules and patient-facing instructions.

2.12 Business Associate shall not transmit PHI to any public, unauthenticated, preview, beta, or other service that is not approved and appropriately covered for PHI processing under this BAA, the applicable Underlying Agreement, and the HIPAA Rules. Business Associate shall maintain reasonable measures designed to detect, block, or redact PHI before transmission to any such service.

3. Safeguards and Security Controls

3.1 Business Associate shall implement and maintain appropriate safeguards to prevent Use or Disclosure of PHI other than as provided for by this BAA and shall comply with the applicable requirements of Subpart C of 45 C.F.R. Part 164 with respect to ePHI. Without limiting the foregoing, Business Associate shall:

  • conduct and document an accurate and thorough risk analysis and maintain a risk management process;
  • maintain access controls that include unique user identification, least privilege, role-based and tenant-scoped access, and risk-appropriate multi-factor authentication;
  • implement encryption for ePHI in transit over open networks and at rest where reasonable and appropriate under the HIPAA Rules, or document and implement an equivalent reasonable and appropriate alternative measure;
  • maintain audit controls sufficient to record and examine material access to and actions involving Covered Entity PHI;
  • maintain policies and procedures for incident response, vulnerability and patch management, secure development and change management, workforce training and sanctions, contingency planning, backup and disaster recovery, and emergency operations; and
  • review and update safeguards in response to changes in risks, technology, law, and the Services.

3.2 Where the Services integrate with an EHR or use a browser extension, paired device, or similar access method, Business Associate shall maintain reasonable controls designed to bind the active user, Covered Entity, patient, and encounter; prevent cross-tenant access; limit persistent local storage; protect pairing credentials and tokens; record material access, modification, transfer, and finalization events; and fail safely when patient, encounter, authorization, or transaction-result validation is not established.

4. Reporting and Breach Response

4.1 Business Associate shall report to Covered Entity any Use or Disclosure of PHI not permitted by this BAA, any Security Incident as addressed in Section 4.4, and any Breach of Unsecured PHI. Business Associate shall provide initial notice of a Material Security Incident without unreasonable delay and in no event later than twenty-four (24) hours after discovery. The initial notice shall be based on then-known facts and shall not be delayed pending completion of a legal Breach determination or forensic investigation. For a Breach of Unsecured PHI, Business Associate shall provide the notice required by 45 C.F.R. § 164.410 without unreasonable delay and in no event later than sixty (60) calendar days after discovery.

4.2 The initial notice shall include, to the extent known, the date and nature of the incident; affected Services, systems, and Covered Entity environment; categories of PHI involved; containment and mitigation measures; and Business Associate’s incident contact.

4.3 Business Associate shall supplement the initial notice promptly as information becomes available and, for a Breach of Unsecured PHI, shall provide the information required by 45 C.F.R. § 164.410(c), to the extent available. Business Associate shall preserve relevant evidence, investigate the incident, mitigate harmful effects to the extent practicable, and reasonably cooperate with Covered Entity in its investigation, risk assessment, remediation, and legally required notifications.

4.4 Business Associate shall not notify Individuals, the Secretary, the media, or other third parties concerning an incident without Covered Entity’s prior written direction, unless Required by Law. Routine unsuccessful Security Incidents that do not result in unauthorized access, Use, Disclosure, modification, destruction, or material unavailability of PHI may be documented and reported in the aggregate upon request or as otherwise agreed by the Parties. Nothing in this Section limits Business Associate’s obligation to report a Material Security Incident or Breach.

5. Subcontractors

5.1 Business Associate shall ensure that each Subcontractor that creates, receives, maintains, or transmits PHI on behalf of Business Associate agrees in writing to the same restrictions, conditions, and requirements that apply to Business Associate with respect to such PHI, including compliance with the applicable requirements of the Security Rule. Business Associate shall require each such Subcontractor to report Security Incidents and Breaches in a time and manner sufficient to enable Business Associate to comply with Section 4.

5.2 Before using a Subcontractor to process PHI, Business Associate shall verify that the provider and service actually used are within the scope of the applicable business associate agreement. Business Associate shall maintain current records identifying each such Subcontractor, the services it performs, and the applicable business associate agreement. Supporting technical and compliance records, including relevant service configuration and material processing conditions, may be maintained in Business Associate’s internal compliance records and need not be attached to this BAA, subject to Business Associate’s obligation to provide reasonable compliance information under Section 2.6.

5.3 If Business Associate uses an intermediary to access or operate an EHR, Business Associate shall contractually require the intermediary to represent and warrant that it has and will maintain the rights, licenses, permissions, and approvals required for the approved access method; use credentials, sessions, and tokens only within the approved scope; refrain from circumventing access controls or contractual restrictions; promptly report any suspension, revocation, or material change affecting EHR access; restrict data reuse; reasonably support investigation and correction of access, security, and scheduling errors; and return or destroy PHI, credentials, tokens, and derived data upon termination. For clarity, a business associate agreement with the intermediary does not by itself establish the intermediary’s right to access the EHR.

6. Individual Rights and Regulatory Support

6.1 Upon Covered Entity’s written request, Business Associate shall make PHI in a Designated Record Set available to Covered Entity in the form and format reasonably requested by Covered Entity as necessary to satisfy Covered Entity’s obligations under 45 C.F.R. § 164.524, no later than ten (10) business days after the request or such shorter period stated in the Underlying Agreement. If Business Associate receives a request directly from an Individual, Business Associate shall forward the request to Covered Entity within two (2) business days and shall not respond directly unless instructed by Covered Entity or Required by Law.

6.2 Upon Covered Entity’s written request, Business Associate shall make PHI in a Designated Record Set available for amendment and incorporate any amendment as directed by Covered Entity in accordance with 45 C.F.R. § 164.526. Business Associate shall also maintain and provide the information required for Covered Entity to furnish an accounting of disclosures under 45 C.F.R. § 164.528. In each case, Business Associate shall respond within ten (10) business days after the request or such shorter period stated in the Underlying Agreement.

6.3 Business Associate shall make its internal practices, books, and records relating to the Use and Disclosure of PHI received from, or created or received on behalf of, Covered Entity available to the Secretary for purposes of determining compliance with the HIPAA Rules. To the extent Business Associate carries out an obligation of Covered Entity under Subpart E of 45 C.F.R. Part 164, Business Associate shall comply with the requirements of Subpart E that apply to Covered Entity in performing that obligation.

6.4 Upon Covered Entity’s reasonable written request, not more than once per calendar year absent a Material Security Incident, Breach, material control failure, or regulatory inquiry, Business Associate shall provide reasonable evidence of compliance with this BAA. Business Associate may provide summaries or appropriately redacted materials where disclosure would reveal another customer’s information, exploitable security details, privileged material, or trade secrets, provided that the information supplied is reasonably sufficient to demonstrate compliance.

7. Covered Entity Responsibilities

7.1 Covered Entity shall notify Business Associate of (a) any limitation in Covered Entity’s notice of privacy practices, (b) any change in or revocation of an Individual’s authorization or other permission, and (c) any restriction on the Use or Disclosure of PHI to which Covered Entity has agreed under 45 C.F.R. § 164.522, in each case to the extent the matter may affect Business Associate’s Use or Disclosure of PHI. Covered Entity shall identify the information maintained by Business Associate that is included in a Designated Record Set or the legal medical record and shall provide instructions reasonably necessary for Business Associate to support Individual rights.

7.2 Covered Entity shall not request Business Associate to Use or Disclose PHI in a manner that would violate the HIPAA Rules if done by Covered Entity, except as expressly permitted for a Business Associate under this BAA. Covered Entity is responsible for providing required patient notices and obtaining applicable consents or authorizations; authorizing and revoking workforce access; protecting its managed devices, networks, browsers, and exports; reviewing and approving clinical AI-assisted output; confirming the patient and encounter before authorizing an EHR modification or record-finalization action; approving administrative automation rules and exception paths; and confirming that it has contractual authority to permit each EHR access method and credential used for the Services. Covered Entity shall not instruct Business Associate to bypass authentication, access controls, technical restrictions, or third-party contractual limitations.

7.3 Covered Entity’s responsibilities do not relieve Business Associate of its obligation to implement the access, tenant, workflow, integrity, and audit controls expressly required by this BAA. Business Associate shall not bypass or circumvent authentication, access controls, technical restrictions, or contractual access limitations applicable to an EHR access method, credential, session, or token, and shall use such access only within the scope authorized under the applicable Underlying Agreement and documented implementation arrangements.

8. Remote and Cross Border Access

8.1 Before permitting routine workforce access to Covered Entity PHI from outside the United States, Business Associate shall identify the applicable countries, legal entities, personnel roles, business need, and material safeguards in Exhibit B or the applicable written implementation arrangements. Such access must be permitted by the Underlying Agreement, applicable EHR terms, and Applicable Law and shall be limited to authorized personnel using least privilege, multi-factor authentication, logging, training, confidentiality obligations, and controls against unauthorized local storage. If the personnel are employed or engaged by a legal entity other than Business Associate, Business Associate shall determine whether that entity is a Subcontractor and, where the entity creates, receives, maintains, or transmits PHI, shall enter into an applicable written business associate agreement before access. Compliance with this Section does not independently authorize access prohibited by an EHR agreement, customer document, or Applicable Law.

9. Term, Termination, and Return or Destruction

9.1 This BAA takes effect on the Effective Date and continues for so long as any Underlying Agreement involving Business Associate’s creation, receipt, maintenance, or transmission of PHI on behalf of Covered Entity remains in effect, unless earlier terminated for cause.

9.2 If Covered Entity determines that Business Associate has breached a material term of this BAA, and Business Associate fails to cure within thirty (30) days after written notice from Covered Entity of the breach, Covered Entity may suspend the affected PHI processing or terminate this BAA and the affected Services. Immediate termination may occur if cure is not possible or the breach presents an imminent material risk to PHI or patient safety. If neither cure nor termination is feasible, Covered Entity may report the violation to the Secretary as required by the HIPAA Rules.

9.3 Upon termination and subject to Section 9.5, Business Associate shall, if feasible, return or destroy all PHI and PHI-Derived Data received from, or created, maintained, or received on behalf of, Covered Entity. At Covered Entity’s written election and before destruction, Business Associate shall make such information available for download or deliver it in a mutually agreed, commonly used, machine-readable format during a thirty (30)-day export period, unless the Underlying Agreement states another period.

9.4 Following the export period, Business Associate shall complete the return or destruction of remaining PHI and PHI-Derived Data in accordance with the applicable retention and deletion periods agreed in Exhibit B or the Underlying Agreement. Business Associate shall address active and readily accessible systems, logs containing PHI, caches, temporary files, development and test environments, Subcontractor copies, and protected backups subject to documented rotation. Business Associate shall require corresponding return or destruction by its Subcontractors and shall provide Covered Entity with written certification upon completion.

9.5 If return or destruction is not feasible, prohibited by law, or subject to a valid legal hold, Business Associate shall notify Covered Entity in writing of the basis for continued retention, the affected information categories and systems or media, and the anticipated retention period. Business Associate shall retain only the Minimum Necessary information, continue to protect it under this BAA, and shall not Use or Disclose it except for the purpose that makes return or destruction infeasible or as Required by Law. Business Associate shall destroy the retained information promptly when the basis for continued retention no longer applies.

9.6 Restrictions on PHI, reporting, regulatory support, and return or destruction survive for as long as Business Associate retains PHI.

10. Miscellaneous

10.1 If this BAA conflicts with an Underlying Agreement concerning the Use, Disclosure, safeguarding, return, or destruction of PHI, this BAA controls. The applicable Underlying Agreement governs commercial terms and the scope, functionality, and activation of the Services unless it expressly states otherwise.

10.2 A reference in this BAA to a provision of the HIPAA Rules means that provision as in effect or as amended and for which compliance is required.

10.3 The Parties shall amend this BAA as reasonably necessary to comply with changes in Applicable Law. No amendment is effective unless it is in writing and signed by authorized representatives of both Parties, except to the extent an Underlying Agreement provides an objective process for implementing a legally required update.

10.4 Any ambiguity shall be interpreted to permit compliance with the HIPAA Rules.

10.5 The Parties are independent contractors and no third-party beneficiary rights are created except as required by law.

10.6 This BAA may be executed in counterparts and by electronic signature.

10.7 Notices. Notices shall be sent to the contacts identified in the applicable Underlying Agreement, the account acceptance record, or a written implementation schedule, as updated by written notice. HUVER's legal, privacy, and security contact is issong@huver.ai, and its business address is 1111B South Governors Avenue, STE 34419, Dover, DE 19904, United States. Covered Entity shall designate an incident contact before production PHI processing begins and keep that contact current. Section 4 notices may be sent by email to the designated incident contact and are effective upon transmission. The designation of an email contact does not represent that a continuously staffed support desk is available and does not modify or extend any reporting deadline in Section 4. Ordinary email should not contain PHI; the Parties shall arrange an approved secure channel for any necessary patient-level information.

10.8 This BAA and the applicable provisions of the Underlying Agreements constitute the Parties’ entire agreement concerning Business Associate’s processing of PHI on Covered Entity’s behalf, subject to the provision above preserving a separately signed BAA already in force unless mutually amended or replaced in accordance with its terms.

Electronic execution

HUVER's offer and Covered Entity's electronic acceptance are recorded as described above. No additional handwritten signature is required for that electronic acceptance. A copy of this BAA together with the associated account acceptance record identifies the contract and the accepting organization. If the Parties execute a separate written agreement instead, that agreement must identify the Parties and be signed by their authorized representatives. A general signup acknowledgment, by itself, is not an organizational signature.

Exhibit A – Covered Services

This Exhibit identifies the Services ordered under the applicable Underlying Agreement that involve Business Associate’s creation, receipt, maintenance, or transmission of PHI on behalf of Covered Entity. It does not independently order, authorize, or activate any Service or grant Business Associate any right to access an EHR or other third-party system. The scope, functionality, and activation of each Service are governed by the applicable Underlying Agreement.

ItemApplicable value or reference
Applicable Underlying AgreementThe HUVA Platform Terms of Use accepted for Covered Entity and the accepted Order Form, subscription confirmation, master services agreement, statement of work, or other applicable written service arrangement, as identified in the organization's contract and account records.
Covered EntityThe full legal organization name identified in the electronic BAA acceptance record or the separately executed agreement.
PHI-enabled ServicesOnly the HUVA Work (including Front Desk) and HUVA Scribe (including Scribe Lite) Services and functions that Covered Entity has ordered and that are approved and enabled under the applicable Underlying Agreement and written implementation arrangements. HUVA Chat, public website and marketing forms, ordinary email, and other unapproved environments are excluded.
Permitted purposeProvision of the Services described in the applicable Underlying Agreement.
Authoritative medical record systemThe clinic-configured EHR or other medical record system designated by Covered Entity in the applicable written implementation arrangements. HUVA is not designated as the authoritative medical record merely by execution of this BAA.
Service-specific scheduleThe applicable written retention, export, return, deletion, security, and implementation schedules or arrangements agreed for the ordered and enabled Services, as referenced in the Underlying Agreement and confirmed under Exhibit B.

Any service or function not identified in the applicable Underlying Agreement is outside the authorized scope of the Services unless added by a written amendment, Order Form, or SOW executed by authorized representatives of the Parties.

Exhibit B – Pre-Implementation Conditions

Before Business Associate begins processing PHI for any Service, the Parties shall confirm in writing, as applicable:

  1. the applicable Service and PHI-enabled functions authorized under the Underlying Agreement;
  2. the system designated as the authoritative medical record system;
  3. the applicable retention, export, return, and deletion requirements for PHI;
  4. the categories of Subcontractors authorized to process PHI and the existence of required business associate agreements;
  5. the applicable access controls, privacy and security contacts, and incident-reporting contacts; and
  6. any material service-specific conditions required under the Underlying Agreement or an applicable written implementation schedule.

Operational, technical, or security details not stated in this Exhibit may be maintained in the Parties’ applicable implementation records, security documentation, or internal compliance records and need not be incorporated into this BAA.

For clarity, execution of this BAA does not, by itself, authorize or activate any Service, grant access to an EHR or other third-party system, or establish that all implementation requirements have been satisfied. Production PHI processing may begin only after the applicable legal, contractual, and material implementation conditions for the relevant Service have been satisfied.

Questions about this document?

Contact Huver, Inc. using your account email or business contact information. Do not include patient records or sensitive identifiers in ordinary email.

issong@huver.ai
HUVA

A platform product of Huver, Inc.
© 2026 Huver, Inc.

Front DeskScribeHelp CenterSecurity & HIPAABAAPrivacyTermsResponsibilities