Skip to policy
HUVA
PrivacyTermsSecurityBAAResponsibilities
HUVER, INC. / HUVA

HIPAA, AI, Recording, and Communication Responsibilities

Your responsibilities when using HUVA for healthcare workflows and professional research.

Effective November 5, 2026 Version 2026-11-05.1

Download this versionPermanent document link

At a glance

  • Confirm the organization, patient, encounter, and destination before record actions.
  • Obtain required recording and communication permissions separately from account acceptance.
  • Use PHI only in an approved service and review clinical AI output before use.
On this page
  1. About this document
  2. 1. Your account and organization
  3. 2. PHI and approved services
  4. 3. AI and medical records
  5. 4. Recording and patient communications
  6. 5. EHR authorization and responsibility
  7. 6. Retention, export, and support

About this document

These responsibilities apply to your use of HUVA alongside the Platform Terms, Privacy Policy, and applicable Business Associate Agreement (BAA). You can accept the required account acknowledgments without opening the document links. The links remain available for review and saving.

1. Your account and organization

Use your own authorized account. Protect your credentials and devices, keep organization and role information accurate, and promptly report access that should be removed. Confirm the organization, patient, encounter, and destination EHR before an action that affects a record. A HUVA account and the person signed in to an EHR may be different.

If you accept as an authorized organization representative, you must have authority to bind the named organization. A team member's acknowledgment or an individual's research acknowledgment does not execute an organization BAA or grant access to a clinic. Account acceptance records the documents, version, capacity, name, organization where applicable, and server time. It does not verify your professional qualifications or expand your permissions.

2. PHI and approved services

Send protected health information (PHI) only through a service and processing path approved for your organization and covered by the required agreements and implementation conditions. A BAA governs PHI protection; signing it does not purchase or activate a service or establish EHR access rights. The healthcare organization must authorize its enabled functions, administrative rules, records system, permitted recipients, and communication settings.

Do not put identifiable patient information into HUVA Chat, marketing or public website forms, general support messages, or unapproved test environments. Use synthetic data for demonstrations or tests unless the specific environment and workflow have been approved for PHI. Chat is for professional information and research, not diagnosis or clinical decision-making. Its account privacy safeguards do not turn it into a PHI-approved service.

3. AI and medical records

AI transcripts, summaries, draft notes, coding suggestions, and other clinical output can be inaccurate or incomplete. Qualified, authorized personnel must review and approve them before clinical use, billing submission, or incorporation into the legal medical record. Check the patient and encounter, review the content, confirm the result of an EHR write, and separately authorize finalization when supported. HUVA does not replace clinical judgment or provide emergency care.

Routine appointment administration may be automated within rules approved by the organization. Uncertain patient matches, clinical questions or emergencies, conflicts, failed or duplicate transactions, and other agreed exceptions require the designated staff response. A technical success message is not a substitute for the workflow's required confirmation. Do not repeatedly submit an action whose outcome is unknown.

4. Recording and patient communications

Before recording or transcribing a conversation, provide the notices and obtain the consent or other permission required for the participants and applicable location. The organization must also approve the intended calling and messaging channels, templates, caller identification, recording settings, and opt-out handling. Obtain patient permission for the actual workflow and honor changed preferences.

A browser microphone permission, account checkbox, BAA, or permitted HIPAA appointment reminder does not replace separate recording or communications requirements. Use the recording controls to stop recording; closing the Scribe Lite panel alone does not stop it. Protect paired phones and disconnect them when no longer needed. Avoid patient information in ordinary email when arranging support.

5. EHR authorization and responsibility

Use EHR credentials, sessions, APIs, browser access, and intermediaries only within the hospital's and provider's contractual and technical authority. Do not bypass authentication, access controls, or restrictions. A clinic's permission, dedicated login, or subcontractor BAA alone does not grant rights that its EHR agreement excludes. Keep Sandbox and Production connections appropriate to the intended data and workflow.

The organization remains responsible for patient care, medical-record retention, its Notice of Privacy Practices, and its staff permissions. HUVER remains responsible for its own applicable safeguards and contractual duties. These responsibilities do not transfer HUVER's duties to the user.

6. Retention, export, and support

Keep final records in the organization's designated medical-record system and follow its retention requirements. Work records and account or billing records can persist separately from temporary Scribe processing. A short cache expiration, closing a panel, or confirming a note does not mean all copies are deleted. Follow the Privacy Policy and applicable BAA for export, deletion, and required retention.

Report a suspected privacy or security issue to issong@huver.ai with the product and organization involved. Avoid including PHI in the initial message and request a secure channel when needed. HIPAA compliance is a continuing set of contractual, technical, and operational responsibilities; the HUVA compliance mark is a company statement for appropriately configured and authorized services, not an HHS certification or approval.

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