Ambient clinical notes
The encounter is written as it happens, in the note format your service already uses, and it arrives in the chart structured rather than pasted.
Seamless EHR integration
Built to work acrossevery EHR you run.
Primum reaches more than fifteen EHR and practice management systems — on desk, on mobile and over the phone line — and fits the way your clinicians already document. There is nothing to migrate and no second chart to keep.
- + 7 more
Introducing
Primum Connect
A plug-and-play module that drops ambient documentation into any EHR that can render a web view — and writes back through whatever that EHR exposes underneath.
Fast time to value
Connect is a module, not a project. It goes in against your existing interface engine and your existing identity provider, with no engineering quarter booked on your side.
Future-proof
Vendor upgrades land underneath you. Connect absorbs them, so a version bump in your EHR is our problem to keep working rather than yours to re-test.
Embedded, not bolted on
It renders inside the chart as an iframe or a SMART app, under the session your clinician is already signed into. Nobody learns a second window.
Once the connection is live
Everything Primum does, from inside your EHR
Nothing here is a separate product a clinician has to go and open. It is the chart they were already in, with the documentation already done by the time they leave it.
Coding suggestions
ICD-10 and procedure codes surfaced live against what was actually said and documented, with the line of the note each one came from attached.
Documentation nudges
Gaps, missing laterality and unresolved problems flagged while the encounter is still open — not in a coding query three weeks later.
Seventeen specialties
Each one carrying its own red flags, preparation instructions and required fields, so the same connection behaves differently in dermatology than in cardiology.
60+ languages
Detected mid-sentence rather than menu-picked, and the note still lands in the chart in English while the patient is spoken to in theirs.
Your templates, your rules
Note styles, field mappings, slot types and escalation thresholds are configuration rather than a fork. Changing one does not mean a release.
What lands in the chart
Deep EHR integration for smarter clinical documentation
Structured notes pushed straight into your EHR, saving clinicians time and making sure the detail that matters is captured where the next person will actually look for it.
Context-aware documentation
Pulls history, active problems and the last visit out of the chart before the encounter starts, so the note is written against the record rather than from a blank page.
Clinical notes exported in seconds
The finished note lands in your own EHR template, in your own field order, on one press. No copy-paste, no second window, and no charts left open at the end of clinic.
Structured data pushed instantly
Vitals, diagnoses, orders and patient instructions arrive as discrete coded fields on the flowsheet and the chart — not as a PDF stapled to the encounter.
The estate
One layer, normalising all of them
Every platform below lands on the same layer, which is why a second integration costs a fraction of the first — and why a workflow built against one clinic's EHR runs against the next one's without being rewritten.
Live protocols on the diagram: FHIR · OAuth 2.0 · HL7 v2 · SMART. Your system not here? Tell us what you run.
How we get in
Three routes, and we will take whichever one you have
Most estates are a mix: a modern FHIR endpoint on one system, a decade-old interface engine on the next, and one vendor who will not open anything at all. All three are survivable.
Native API, both directions
Where the vendor exposes one, we use it. Read the chart, reason over it, write the result back into discrete fields with the write attributed to the signing clinician.
- FHIR R4
- HL7 v2
- SMART on FHIR
Through the interface engine
ADT, ORM, ORU and SIU over your existing engine, in the message formats it already speaks. Nothing new is introduced into the estate to carry it.
- ADT
- ORU
- SIU
Driven as a session
Where there is no interface to use, Primum drives the application the way a person does — under a named service account, rate-limited, and with every action logged. Slow to build, but it means a closed vendor is not a closed door.
- Named account
- Full audit
Privacy & security
The six questions every security review opens with, answered before you have to ask them.
- No audio retained by default. Clinicians opt in per encounter.
- SSO, SAML and SCIM provisioning against your identity provider.
- SMART on FHIR login, so the chart's session is the only session.
- Nothing you send trains a model — ours or a third party's.
- Retention set by you, per data class, and enforced on our side.
- GDPR-first and HIPAA-ready, on sovereign EU tenancy with an Article 28 DPA.
The full detail is in the privacy policy and the data processing addendum.
Tell us what you run, and we will show you it working
Name the EHR, the interface engine and the one system everybody warned you about. We will come back with what the connection looks like against your estate — including the parts we cannot reach.