Healthcare APIs

Healthcare APIs and webhooks

Build on RadpicsAI with REST APIs, signed webhook notifications, a FHIR R4 API and DICOMweb, so your applications reach imaging and workflow data through standard interfaces.

Book an Integration Demo Contact our team

REST APIs · Webhooks (HMAC) · FHIR R4 · DICOMweb · Single sign-on

Standards and connectivity

APIs, security and deployment

Support differs by message type and direction. Interfaces for your systems and versions are confirmed during scoping.

DICOMweb, REST APIs and webhooks

DICOMweb search and retrieve (QIDO-RS, WADO-RS)
REST APIs with token-based access through RadpicsAI single sign-on
Webhooks: signed (HMAC) event notifications to other applications

Storing studies over DICOMweb (STOW-RS) is not supported.

FHIR R4

API: Patient, Encounter, Appointment, ServiceRequest, Observation, Organization, Location
API: ImagingStudy and Practitioner (read), DiagnosticReport (read and create)
Send FHIR resources to other systems

Security

Token-based API access through RadpicsAI single sign-on
Audit trail of user and system actions
Encrypted transport (TLS) for HL7 MLLP and DICOM links

Deployment

Cloud-hosted integration services
Hybrid: on-site gateway with RadpicsAI cloud
Fully on-premises deployment

Use cases

Where teams use the APIs

AI applications in clinical workflows

Hospitals · AI and analytics vendors

The gap: Each AI pilot needs its own route to images and a way back into the reporting workflow.
How MiddleOffice helps: Studies are routed to the application by rule or retrieved through DICOMweb, and its output can be written back as a DiagnosticReport through the FHIR API. MiddleOffice moves the data; it does not analyse images.

Relies on

DICOM send by rule
DICOMweb search and retrieve
FHIR DiagnosticReport create

Legacy HIS/EHR to modern applications

Hospitals · Healthcare SaaS companies

The gap: A new application needs patient and order data held in an older HIS that only speaks HL7 v2.
How MiddleOffice helps: MiddleOffice receives the HL7 v2 messages and exposes the data through a FHIR R4 API the new application can use.

Relies on

HL7 v2 receive
FHIR R4 API
Push FHIR resources to other systems

FAQ

Frequently asked questions

How do applications authenticate?

API access is token-based, through RadpicsAI single sign-on.

What do webhooks send?

Webhooks send signed (HMAC) event notifications to other applications.

Can we connect AI applications?

Yes. Studies can be routed to an application by rule or retrieved through DICOMweb, and results can be written back as a DiagnosticReport through the FHIR API. MiddleOffice moves data between systems; it does not analyse images.

Can MiddleOffice run on premises?

Yes. Cloud-hosted, hybrid (an on-site gateway connected to RadpicsAI cloud) and fully on-premises deployments are available. We agree which components run where during scoping.

Build on RadpicsAI

Tell us what your application needs to read or write, and we will confirm the APIs for your deployment.