Unomed Medical API
Imaging, secure messaging, ICD-10 and the AI blocks from Unomed are also available as an API. You call them from your own system and show the result in your own interface.
Authorization: Bearer <token>
Content-Type: application/json
{
"text": "Gonarthrose links, zunehmend",
"system": "icd-10-gm",
"max": 3
}{
"candidates": [
{ "code": "M17.1", "score": 0.94,
"text": "Sonstige primäre Gonarthrose" },
{ "code": "M17.9", "score": 0.41,
"text": "Gonarthrose, nicht näher bezeichnet" }
],
"requestId": "req_8f2c1a",
"region": "ch"
}An excerpt. The full reference and an OpenAPI file come with your access.
What you can build in
Every area works on its own. You wire in what your product is missing and leave the rest out.
Receive, store and retrieve studies, and generate a viewer link you embed in your own interface. Over DICOMweb, the language your modalities and your PACS already speak.
Messages, documents and whole imaging studies to referrers or to patients, triggered from your application. Anyone without an account gets a guest link in the browser.
A referral goes in as a PDF, clean fields come out. And from a report text, ICD-10 suggestions with the passage they rest on, rather than a number with no origin.
Dictation and consultations as text, and from that a draft report in the shape your speciality expects. Summarising and translating are part of it.
Not every area fits every product. Tell us what you have in mind and we will tell you what already works today and what does not.
How it works
Three steps and nothing surprising in between. Anyone who has connected a REST API before knows every one of them.
No call changes anything in your system. We return a result, and what happens to it is your application's decision.
One key per application, OAuth 2.0 client credentials. Plus a test environment with invented patient data, so you can finish building before the first real document moves.
REST over HTTPS, JSON in and out, described in an OpenAPI file. Anything that takes longer, a large study for instance, runs as a job with an id and reports back over a webhook.
Structured JSON, as FHIR R4 or HL7 v2 on request, images as DICOM. Every call is in the log with its time, its key and its result.
Formats and standards
Who it is for
The API is meant for anyone who has their own interface and intends to keep it.
Offer imaging, coding or dictation inside your own product without building them yourself. Your customers see your software, not ours.
Extend your own applications with the blocks the house is missing. Connected to what already runs, instead of yet another system beside it.
Build a product without first building a PACS, a messenger and a coding aid. You start with your idea, not with the foundation underneath it.
Control
The same rules as everywhere else in the suite, except that here the sender is your application and not a practice.
We return a result and nothing else. Whether anyone sees it, checks it or accepts it is governed by your interface.
Calls and storage stay in certified Swiss data centres, compliant with the Swiss FADP and the GDPR.
What you send serves the call and nothing after it. None of it goes into training.
Separate tenants, keys you can revoke at any time, and every call stays traceable with its time and its result.
The Medical API is included from the Flows Praxis plan upwards. If you only want the interface and build no workflows in the builder, we will quote a separate rate. Tell us the volume you expect and we will work it out.
Yes. Access includes a test environment with invented patient data. You can build and experiment there for as long as you like, with no real data involved.
Billing follows usage, with a ceiling you set yourself. The production rate depends on volume, which is why it is not on this page. Ask us and you get a figure instead of a range.
Yes. The API appears nowhere in your interface, and whether you name Unomed as the foundation is your decision. How the embedded viewer looks is something we agree with you.
The version is in the path. Anything that changes arrives as a new version, and the old one keeps running until we announce its end with notice.
The API returns suggestions, drafts and transcripts, not diagnoses. The clinical check stays with the person who signs, and your application has to make room for that.
Getting started
A few sentences about your product and about what is missing in it. We will tell you which areas of the API fit, what they cost and how quickly you can start testing.
