Resident every step
Transcribe, OCR and draft all pinned to the region you choose — no silent cross-border hops.
Solution · Clinical documentation
Ambient notes, in your jurisdiction.
Turn a recorded encounter and the patient’s prior records into a structured note — transcription, OCR and drafting on one PHI-gated, region-resident API.
The problem
Why this is hard
Documentation is where clinician time goes and where the data is most sensitive. An ambient scribe has to transcribe the visit, read prior records, and draft a note — every step touching protected health information. Most AI APIs either won’t take PHI under contract or quietly route it out of your jurisdiction. phi-cloud lets you build the whole pipeline while the data stays in Switzerland or the EU and never trains a model.
How it works
The pipeline, end to end
- 1
Capture the encounter
POST /v1/audio/transcriptionsSend the recording with X-Region and X-PHI:true. It transcribes on a same-jurisdiction Whisper host — Azure Speech in CH, Scaleway/Voxtral in the EU — and never fails over across a border.
- 2
Read the prior records
POST /v1/ocrScanned intake forms, referrals and faxes become per-page markdown via Azure Document Intelligence (PHI-eligible), ready to fold into the model’s context.
- 3
Draft the note
POST /v1/chat/completionsFeed the transcript plus extracted history to a resident chat model and ask for a structured SOAP note. Use JSON mode / tools to lock the shape your EHR expects.
- 4
Keep the record yours
Audit headersThe proxy stores nothing. Each response carries x-phi-routed, x-phi-tier and x-phi-attempts — log them and your audit trail writes itself.
Why phi-cloud
What makes it compliant
Hard PHI gate
Every call is classified; PHI only ever touches verified providers, or it is refused — never a quiet fallback.
Never trained on
Neither phi-cloud nor the PHI providers retain or train on the encounter. It is processed and discarded.
Drop-in OpenAI shape
Standard SDKs. The whole pipeline is three familiar endpoints plus two headers.
In code
A representative call
The drafting step: transcript and history in, a structured note out — pinned to Switzerland under the PHI gate.
curl
curl https://phi-cloud.com/api/v1/chat/completions \
-H "Authorization: Bearer $PHI_API_KEY" \
-H "X-Region: CH" -H "X-PHI: true" \
-d '{
"model": "gemma-4",
"response_format": {"type": "json_object"},
"messages": [
{"role":"system","content":"Draft a SOAP note as JSON."},
{"role":"user","content":"Transcript: ... Prior records: ..."}
]
}'response
x-phi-routed: infomaniak-gemma-4-31b/CH/phi
x-phi-tier: phi
x-phi-usage: verifiedCompliance posture
- CH: transcription + OCR + drafting on Infomaniak and Azure (Switzerland), nFADP/GDPR + HIPAA BAA verified.
- EU: Scaleway and Azure (EU), GDPR Art. 28 DPA, zero-retention.
- No prompt, transcript or document is logged or persisted by the proxy.
- Audit headers on every response give you a per-call record of where PHI was processed.
FAQ
Common questions
Not by phi-cloud — it is a stateless proxy. The PHI-eligible providers process the audio under zero-retention / no-training terms. What you persist (the final note, the audit headers) is entirely under your control.
Yes. Pin X-Region: CH on every call. Transcription and OCR resolve to Swiss-jurisdiction Azure, and drafting to Infomaniak. Nothing crosses a border; speech and OCR have no cross-border failover by design.
Use response_format JSON mode or tool calling on the chat step — both pass through to the model. You get a structured object back instead of free text.
Ready when you are
Build clinical documentation on a gateway that survives the audit.
Free to test. Prepaid credits when you go live. The residency and PHI posture is the same in production.
Free to test · Prepaid credits, no subscription · No data retained