Can AI agents automate DIPS?

DIPS AS · on-prem · healthcareehr

DIPS runs a genuinely open developer surface — the Open DIPS sandbox with synthetic patient data, subscription-key FHIR APIs and SMART on FHIR sample apps — but production access to hospital data is gated behind a DIPS partner agreement and certification with the health trusts. For agents, the FHIR API is the real path once partnered; UI-level RPA against DIPS is already proven in production by Norwegian hospitals.

Best path today: api · Overall automatability: 3/10

Modalities

ModalityStatusDetail
APIyesrestfhirsmart-on-fhiroauth2api-key
coverage: partial · docs
SDKunknown
official: unknown
MCPnone
verdict: none
Integrationsno
CLIunknown
Extensibilityno
webhooks: unknown
Data access
export: fhir-api · import: fhir-api
RPA / UI automationworkablewindows-nativeweb-domuipath
UiPath robots run in production against the DIPS journal system at Helse Vest (prostate-cancer registration across DIPS, a research DB and the Cancer Registry cut from 10 to 2 minutes per patient); DIPS Arena is a Windows client, so UI automation is desktop-stack, not web-only.
Computer useunknown
measured verdicts only — "unknown" means not yet probed by us

Scores

apimcprpacomputer useoverall
303—3

Evidence

FactTierSourceDate
modalities.api.existsdeclaredsource2026-08-15
modalities.api.authdeclaredsource2026-08-15
modalities.api.authdeclaredsource2026-08-15
modalities.api.coveragedeclaredsource2026-08-15
architecture.openehrcommunitysource2026-08-15
ecosystem.integrationsdeclaredsource2026-08-15
modalities.rpa.drivabilitydeclaredsource2026-08-15
modalities.mcp.verdictscrapedsource2026-08-15
modalities.agent_docs.llms_txtscrapedsource2026-08-15
freshness.volatilityscrapedsource2026-08-15

Last verified 2026-08-15 · volatility medium · JSON record