Skip to content
CloudSitus

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.

Get startedRead the docs

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. CloudSitus lets you build the whole pipeline while the data stays in Switzerland or the EU, and CloudSitus stores and trains on none of it.

How it works

The pipeline, end to end

  1. Step 1: Capture the encounter

    POST /v1/audio/transcriptions

    Send the recording with X-Region and X-PHI:true. It transcribes on a same-jurisdiction host — Microsoft Azure in CH, Scaleway in EU and Microsoft Azure in US — and never fails over across a border.

  2. Step 2: Read the prior records

    POST /v1/ocr

    Scanned intake forms, referrals and faxes become per-page markdown via Azure Document Intelligence (PHI-eligible), ready to fold into the model’s context.

  3. Step 3: Draft the note

    POST /v1/chat/completions

    Feed 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. Step 4: Keep the record yours

    Audit headers

    The proxy stores nothing. Each response carries x-phi-routed, x-phi-tier and x-phi-attempts — log them and your audit trail writes itself.

Built on:Speech (STT)Document OCRChat & reasoning

Why CloudSitus

What makes it compliant

01

Resident every step

Transcribe, OCR and draft all pinned to the region you choose — no silent cross-border hops.

02

Hard PHI gate

Every call is classified; PHI only ever touches verified providers, or it is refused — never a quiet fallback.

03

Not stored by CloudSitus

CloudSitus stores and trains on nothing — the encounter passes through in memory, to PHI providers whose DPA or BAA we have reviewed.

04

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.

Compliance posture

  • CH: transcription + OCR + drafting on Infomaniak and Azure (Switzerland), under reviewed nFADP/GDPR DPAs (Azure also under the Microsoft HIPAA BAA).
  • EU: Scaleway (GDPR Art. 28 DPA, zero-retention) and Azure (EU, Microsoft DPA).
  • 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.
curl
curl https://cloudsitus.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: verified

FAQ

Common questions

Medical transcriptionCompliance postureHow routing works
Does the audio or transcript get stored anywhere?
Not by CloudSitus — it is a stateless proxy. The audio goes only to PHI providers whose DPA or BAA we have reviewed, and their own terms govern any upstream retention. What you persist (the final note, the audit headers) is entirely under your control.
Can I keep the entire pipeline inside Switzerland?
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.
How do I force the note into my EHR’s schema?
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.

Prepaid credits from $10, no subscription. The residency and PHI posture is the same on your first call as in production.

Get startedSee the compliance posture

Prepaid credits from $10 · No subscription · No data retained