AI that runs on the device
Speech recognition and note drafting run on the Neural Engine and GPU of your iPhone or Mac. There is no inference server, no third-party AI vendor and no cloud fallback. If a model can’t run, Care says so.
Scribed Care In development
Scribed Care records, transcribes and drafts encounter notes with AI that runs entirely on your iPhone or Mac. No cloud inference. No audio upload. Patient data stays in an encrypted vault that only you can open.
iPhone & Apple-silicon Mac · Online setup, then offline work
Test encounter · On this device
“Let’s review them together.”
The conversation stays close.
Keep the words and the draft in view.
I’d like to go over my notes from our last visit.
Let’s review them together.
Original wording remains available while notes are reviewed.
The visitor asked to review notes from the previous visit. The clinician offered to review them together.
Illustrative documentation only. The draft requires human review against its source.
Explore the transcript and note draft above.
What Care does
Everything a medical scribe does, from the recording to the reviewed note, on hardware already in your pocket.
Speech recognition and note drafting run on the Neural Engine and GPU of your iPhone or Mac. There is no inference server, no third-party AI vendor and no cloud fallback. If a model can’t run, Care says so.
Patients, recordings, transcripts and notes are stored in an encrypted database whose key is held in the device’s protected keychain and released only by Face ID, Touch ID or your passcode.
Confirm the patient and recording consent, then record. Care transcribes on the device, flags medication names against RxNorm and keeps the original transcript beside every edit.
The local assistant drafts a note from the transcript. You verify each medication, check the source and finalize. Nothing is signed off without you.
On-premises, literally
Most AI scribes stream the visit to a vendor’s cloud and a third-party model. Care runs speech recognition and note drafting on the device in your hand, so patient audio has nowhere to go.
Patient audio crosses the internet and sits on infrastructure you don’t control.
Inside your iPhone or Mac
No network needed after setup. No inference vendor in the path of PHI.
Privacy and security
Keeping data on the device is the first layer. Here’s everything else between a patient’s words and anyone who shouldn’t hear them.
Every patient, recording, transcript and note lives in an encrypted SQLCipher database. Temporary audio files are purged when the vault locks.
The vault key sits in the device’s protected keychain, bound to its passcode and this device only. It is never synced, backed up or sent anywhere.
Opening the vault takes device authentication. Leave the app and it locks; the screen is covered in the app switcher.
If a model is missing or a device runs out of memory, Care stops and tells you. It never quietly sends audio to a server instead.
No share sheet, no clipboard, no analytics, no crash reporting in the clinical path. Exports go only where you save them.
Clinical data and keys are excluded from iCloud and device backups. A passphrase-protected AES-256 vault archive is your recovery copy.
The original transcript is never overwritten. Every correction is a separate layer, hashed and traceable back to the source.
Each model file is checked against a pinned checksum before it can load, so the AI that runs is the AI we tested.
HIPAA
HIPAA compliance belongs to your practice: your risk analysis, policies, training and agreements. What an app can do is shrink the surface you have to protect. When transcription and AI never leave the device, there is no cloud processor holding your patients’ audio.
Scribed does not yet offer a business associate agreement, so the optional patient-list sync is unavailable to covered entities. Care’s on-device workflow doesn’t need it.
Security Rule technical safeguards, supported on the device
Measured, not configured
Care ships with one speech model, chosen for you: NVIDIA’s Parakeet TDT 0.6B v3, in FluidInference’s Core ML build, on iPhone and on Apple-silicon Macs alike. Core ML lets it ask for the Neural Engine. There is no model picker to get wrong.
We tested it the way a clinic would hear it: 57 mock consultations between clinicians and actors (PriMock57), plus a synthetic clinical corpus dense with drug names, doses and negation, against eight alternatives on the consultations, from Whisper tiny to WhisperKit’s large-v3-turbo, and one more, sherpa-onnx’s Parakeet v2, on the synthetic material only. Parakeet v3 was the most accurate engine among those run on every consultation, at a fifth of the memory of the GGUF build the app ran before (255 against 1,210 MiB).
Every engine we tried stumbled on medication names, and Care doesn’t pretend otherwise. A correction layer checks the transcript against RxNorm’s list of prescribable names and shows each change on a copy of the transcript: underlined, explained, one tap from reverting. Then a medication-verification step asks you to confirm every drug before a note is final.
Before anything can leave the device, an identifier model and a set of rules flag names, dates, numbers and places for your review, span by span. The review is the safeguard; the model only feeds it. Audio stays on the device.
How it works
Local AI does the typing. You check the source, verify the medications and decide when a note is final.
Sign in with your Scribed account. Care downloads and verifies its models, then creates your encrypted vault. After setup, you can work with the connection off.
Confirm the patient and their permission to record. Audio is captured and transcribed on the device, in airplane mode if you like.
Correct the transcript, draft the note with the local assistant, confirm every medication and mark the note reviewed.
Not for transcription or AI. Audio, transcripts, notes and the assistant’s output stay on the device, with no cloud fallback. Two optional features are off by default: syncing your patient list to your own Scribed workspace, and sharing a transcript after you review it and remove identifiers. You choose when, if ever, to use them.
No app can be HIPAA compliant on its own. Compliance depends on your practice’s safeguards, policies and agreements, and we won’t put a badge on it. Care is designed so that transcription and AI never put patient data in a third party’s hands: it supports your access controls and audit trail with device authentication, encryption and a local audit log. Scribed does not yet offer a business associate agreement, so cloud sync stays unavailable to covered entities.
The vault is encrypted with a key that lives only in that device’s keychain, is tied to its passcode, and is never included in iCloud or other backups. Without the device owner’s authentication, the data can’t be read. An encrypted, passphrase-protected vault archive you create is the only copy outside the device.
Care is in development for iPhone and Apple-silicon Macs. Contact us about preview availability. The development preview is for synthetic test data only and is not ready for real patient use; device, clinical and operational validation remain incomplete.
iPhone on iOS 17 or later with a Neural Engine and at least 6 GB of memory, and Apple-silicon Macs. Note drafting and Ask need at least 8 GB. Android and Intel Macs are not supported, because the speech engine runs on Apple’s Neural Engine.
Help organize encounter documentation and find information in a saved transcript, with the source available for review. It is not designed to diagnose, prescribe or take clinical actions.
Private by architecture
Get in touch about the Scribed Care development preview.
iPhone & Apple-silicon Mac · In development
For synthetic test data only. Not ready for real patient use. Device, clinical, and operational validation remain incomplete.