Clinic-controlled by design

Security and data handling

A plain-language map of what stays inside the clinic, what limited business information may leave, and how LocalChart works when an encounter is not recorded.

LocalChart clinic host and client network Two provider iPads, a front desk computer, and a clinician laptop connect through the clinic network to one clinic-owned Windows host. A named clinic administrator may connect through a revocable private route. Only account, licensing, subscription, and clinic-address information goes to the PHI-free internet service. CLINIC-CONTROLLED PRIVATE NETWORK Authorized browser devices connect to one clinic-owned LocalChart workstation. OUTSIDE THE CLINIC Only clinic-approved access. Provider iPadExam room 1 Provider iPadExam room 2 Front deskSchedule · intake · records Clinician laptopReview · reports · history Clinic Wi-Fi 6or Ethernet CLINIC-OWNED WINDOWS HOST LocalChart home base App · local AI · workflow health Encrypted LocalChart vault Charts · audio · transcripts · reports Memory · schedules · audit · backups Recovery stays under clinic control Clinic owner oradministrator Named account · approved device Private encrypted route Clinic controlled and revocable PHI-free internet service Accounts · licenses · subscriptions Staff membership · clinic web address NO PATIENT INFORMATION Account status only If a recording transfer is interrupted, that iPad may keep a temporary encrypted recovery copy until the clinic host confirms safe receipt. Clinic connection Private remote route PHI-free account traffic Encrypted on clinic host
Clinic devices

iPad, Mac, and Windows browsers

Authorized staff open the clinic's secure LocalChart address. Client devices do not carry a separate model or record store.

Clinic home base

One clinic-owned Windows host

The application, encrypted clinical records, local transcription, drafting, recovery, and backups stay under clinic control.

Approved remote access

Named, revocable administrator access

The clinic controls who may connect remotely and can revoke the private route.

Limited internet boundary

PHI-free business services only

Account, license, subscription, and clinic-address metadata may leave the clinic. No patient information belongs in this path.

One clinic host, many authorized clients. The workstation stores and processes the clinical record. Clinic devices open LocalChart through secure browser connections; the separate internet service coordinates accounts and licensing without receiving patient information.
Inside the clinic

Clinical records stay on the LocalChart host

Patient profiles, schedules, recordings, transcripts, drafts, approved reports, audit evidence, backups, and recovery artifacts are stored on clinic-controlled systems according to the clinic's configuration.

Outside the clinic

Business services stay PHI-free

Clinic identity, staff account membership, licensing, installation status, subscription references, and security events may be handled by the account service. It is not intended to receive patient names, appointments, recordings, transcripts, or reports.

Support boundary

Use fake or redacted evidence

Normal support should use PHI-free diagnostics and fictional examples. Remote access is clinic-controlled and revocable; it is not standing vendor access to patient records.

Data custody without forced replacement

The clinic day stays familiar. The data boundary changes.

LocalChart keeps the clinical core under clinic control and can also operate as a documentation layer beside an existing EMR. The clinic can retain original sources and a readable longitudinal archive while sending only the clinician-approved document into another system.

The same clinic day includes schedules, patient history, visit notes, referrals, audio, and personal context. A typical vendor-hosted cloud EMR path sends patient data across the public internet to vendor-controlled records, AI, backups, logs, accounts, and support. The LocalChart path keeps the clinical core, transcription, encrypted records, patient continuity, schedules, backups, recovery, and clinician review within a clinic-controlled boundary. Only PHI-free account information uses the internet service.
Clinic-owned custody reduces lock-in. LocalChart keeps the working clinical record and recovery path with the clinic instead of making continued access depend on one hosted vendor platform.Open full-size comparison
Keep your EMR and own your documentation. Patient conversation, clinician dictation, typed rough notes, photographed handwriting, and imported records enter a clinic-owned LocalChart documentation layer. Original sources remain attached, transcription and OCR run locally, the clinician reviews and approves, and an encrypted clinic-owned longitudinal record is retained. Only the clinician-approved document is sent to the existing EMR for scheduling, billing, claims, and its approved note. Raw audio, personal context, and source files stay local.
LocalChart can complement an existing EMR. Keep the payer-connected system the clinic already uses while preserving source material, local drafting, review, backups, and a readable documentation archive under clinic control.Open full-size documentation layer

Cloud architecture, contract terms, export rights, and data-custody rules vary by vendor. Clinics should review each vendor's terms. LocalChart's intended distinction is a clinic-controlled clinical workspace with a PHI-free account-service boundary and a clinician-approved handoff to an existing EMR when required.

Local AI, not a cloud clinical-drafting service

LocalChart's supported transcription and language-model workflow runs on the clinic host. Clinical recordings, transcripts, prompts, and draft notes are not sent to a cloud LLM for drafting. Optional PHI-free services for accounts, licensing, and route coordination remain outside the clinical data path.

Recording is optional

A clinic may use encounter recording only after following its consent and authorization requirements. If consent is not obtained, do not record the conversation. LocalChart still supports provider dictation: the clinician dictates their own clinical summary, LocalChart transcribes it, and the normal drafting, review, record, and export workflow continues.

Encryption, exports, and backups

LocalChart protects supported stored artifacts and provides authorized in-app reading, export, backup, and staged recovery. Clinics should not depend on navigating encrypted application files directly. Export and recovery tools are the supported way to keep records usable and auditable.

Layered safeguards

LocalChart combines private HTTPS access, named profiles and role boundaries, device identity, protected storage, audit and recovery evidence, exact runtime and model identification, bounded document processing, dependency review, and release rollback. Imported files, OCR text, recordings, and model output are treated as untrusted inputs rather than instructions with authority.

AI safety and security testing

Separate security gates exercise prompt injection, attempted instruction and prompt extraction, data leakage, malicious document and OCR content, adversarial audio, cross-patient isolation, resource exhaustion, and runtime containment. These controls reduce risk; no software or model can promise immunity from every attack.

Clinicians remain the final authority

Audio and source records preserve provenance. Transcripts, extracted facts, summaries, and generated notes remain drafts until an authorized clinician reviews and approves them. LocalChart does not silently finalize clinical output.

Subscription continuity

Billing or licensing status may pause creation of new work. Authorized staff retain access to existing clinic records, exports, backups, audit history, and recovery.

What local hosting does not solve by itself

Local hosting does not automatically satisfy HIPAA, state recording laws, professional-board rules, payer requirements, or clinic policy. Each clinic still needs appropriate risk analysis, workforce practices, device and network security, consent procedures, retention rules, and legal review.

Report a concern

Contact support@localchart.app with a PHI-free description. Do not email patient information, credentials, or backup files.