HUVA EHR Push BETA Privacy Policy

Last updated: August 15, 2026

HUVA EHR Push BETA helps a clinician move a reviewed HUVA Scribe note into the eClinicalWorks sandbox Progress Note that the clinician has already opened.

Data processed

The extension processes the reviewed Chief Complaint, HPI, Medical History, Physical Examination, Assessment, Treatment Plan, and Visit Code. Clinical note text is sensitive health information even though the transfer contract intentionally excludes patient name, date of birth, medical-record number, account ID, encounter ID, and note ID.

The extension also processes the minimum page structure required to find supported controls and field-level completion or failure states. Diagnostics include allowlisted statuses, lifecycle stages, and bounded structural counts. They exclude clinical text, raw HTML, URLs, transfer IDs, and patient identifiers.

Purpose and use

Data is used only to import a clinician-confirmed HUVA note, let the clinician review or edit it, write supported fields to the open eCW sandbox Progress Note, show a verification checklist, and perform Lock only after separate physician confirmation.

Semantic mapping and readback verification occur locally in Chrome. Chrome's on-device Prompt API may assist with bounded candidate ranking when it is already available; deterministic mapping is used otherwise. The extension does not send note content to an external AI, analytics, advertising, or HUVA-operated extension backend.

HUVA EHR Push BETA does not use clinical or browsing data for advertising, credit decisions, data brokerage, or unrelated purposes, and it does not sell user data.

The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Storage, sharing, and retention

Reviewed note fields are stored only in Chrome storage.session for the active browser session and expire after 30 minutes. The user can clear them immediately. A minimal no-retry guard may retain an extension-generated random transfer ID, timestamp, schema version, and outcome reason in session storage; it contains no note text or patient identity.

The extension does not use Chrome local or sync storage for clinical data and does not share extension data with third parties. Data is read from and written to the HUVA and eCW pages selected by the clinician because that movement is the user-requested feature.

Permissions

• activeTab and scripting connect packaged extension code to the active, user-selected HUVA or eCW tab.
• sidePanel provides import, review, push, checklist, and Lock controls.
• storage holds the expiring reviewed transfer and note-text-free safety state in session storage.
• HUVA host access reads the confirmed note selected by the clinician.
• sandbox.eclinicalweb.com access writes and verifies only supported sandbox Progress Note fields and the reviewed five-digit Visit CPT.

The Chrome Web Store build has no downloads permission, localhost access, external network endpoint, remote executable code, development QA controller, credential automation, or production eCW host permission.

User choices and security

The clinician chooses the HUVA note and eCW Progress Note, reviews imported fields, confirms Push, checks every result, and separately confirms Lock. Existing destination content is not overwritten. An uncertain write cannot be automatically retried.

The extension runs as a Manifest V3 extension and uses packaged code only. Access is restricted to HTTPS HUVA pages and the eCW sandbox host declared in the manifest.

Contact and policy updates

Questions, deletion requests, or privacy concerns can be sent through the support contact published on huva.health. Material policy changes will be reflected on the public policy page and in the Chrome Web Store disclosure before changed data practices are released.