Vidd connects to the record system you already use
The draft is published where it belongs, in the record. The integration uses the record system's own interfaces and the clinician's own access, so the access control and logging you have today still apply.
Inside the record system, or connected to it
Built into the record system
The record system vendor builds Vidd into its own product, with a two-way integration. The clinician opens Vidd from the record, and approved documents are written straight back. This is how Vidd is integrated in WebMed.
Through the record system's standard interfaces
Where the record system has open interfaces, Vidd connects to them directly. With DIPS Arena, Vidd uses HL7 FHIR R4 to read record documents and publish approved ones. No direct database access.
Record systems Vidd is integrated with
WebMed
Two-way integration built into the record system
In use by GPs
DIPS Arena
HL7 FHIR R4: patient lookup, document search, reading selected documents and publishing
In pilot at Norwegian hospitals
Other systems
Open APIs and MCP
By agreement
What happens in an integration
The clinician logs in with HelseID or the record system's own login. Vidd gets the clinician's access, not its own.
The patient is chosen from today's appointments or by search.
The source material is gathered. The conversation is recorded and transcribed, or the clinician chooses record documents from a list that shows only metadata.
The draft is written by models running on dedicated hardware, without internet access. The record documents are deleted as soon as the draft exists.
The clinician approves, and the document is published in the record system through its own interface. The document is stored there, not by Vidd.
Five things we settle with your operations organisation
The technical work is rarely what takes time. Client registration, network openings and the risk assessment set the schedule, which is why we start with them.
Client registration
Vidd is registered as a client in the record system's identity solution, with access granted for reading and publishing.
Endpoints and network
The address of the record system's API, the network openings needed, and whether traffic runs locally in the secure zone or over Norsk Helsenett.
Test environment
The integration is verified in a test environment before it goes into production.
Risk assessment
Which risk assessment and approval process applies, and who owns it. We provide the documentation.
Point of contact
One technical contact on your side and one on ours.
Do you supply a record system or clinical system?
Vidd can be the AI layer in your product. You keep the customer relationship, and Vidd carries the medical device certification and runs the models.
Questions about integration
No, not when the record system has interfaces for reading and writing documents, or already has Vidd built in. The integration uses the interfaces that exist.
HL7 FHIR R4 for record data, HelseID or the record system's own identity solution over OAuth 2.0 and OpenID Connect for login, and MCP and REST APIs for built-in integrations. Audio is streamed encrypted over WebSocket.
It depends mostly on client registration, network openings and the risk assessment in your operations organisation. We provide technical staff for a working meeting early on, so those items get started first.
On dedicated hardware in the organisation's own data centre or in Vidd's sovereign cloud in Norway. No part of the processing goes to external AI or cloud APIs.
Which record system
do you use?
Tell us what you run today, and we will tell you what it takes.