Can AI agents automate WebMed?
WebMed · saas · healthcareclinical
WebMed is a distinct product from CGM Journal and is scored separately. It is a cloud-hosted Norwegian electronic patient record with a first-party SMART on FHIR integration framework for approved third-party applications. WebMed states that SMART apps receive only pseudonymised identifiers for the patient, clinician and practice, not clinical journal data. Medbric and Noteless run as launched SMART apps inside the EPR, and generated notes can be saved back to the patient journal through the governed workflow. Beyond that narrow developer surface, WebMed has broad packaged integrations with Helsenorge patient services, laboratory ordering systems across Norwegian health regions, Fürst services, EKG, spirometry and ambulatory blood-pressure devices, a LIMS bridge, electronic messaging, payments, SMS, telephony and knowledge support. This is strong ecosystem automation but not a general read-write FHIR server or public clinical API. Public documentation does not define scopes, endpoint schemas, app registration, audit events, bulk data access or an SDK. Patient data, note creation, medication, orders, billing and communication remain high-impact clinical actions requiring approved apps, least privilege, auditability and human clinical accountability. No product-specific first-party MCP, general CLI, repeatable visual RPA result or computer-use result was established.
Best path today: api · Overall automatability: 4/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | smart-on-fhir-app-launch coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | unknown | verdict: unknown |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | yes | smart-on-fhir-frameworkapproved-smart-appslims-bridgedevice-integrations webhooks: unknown |
| Data access | export: approved-note-writeback, electronic-messages, laboratory-orders, clinical-reports · import: approved-note-writeback, laboratory-results, device-measurements, electronic-messages, migrated-journal-data | |
| RPA / UI automation | unknown | windows-clickonceremote-application No repeatable UI probe was run. Approved SMART apps and contracted clinical, laboratory, device and national-service integrations are safer semantic paths than visual control. WebMed's public SMART description explicitly withholds clinical journal data from third-party apps, and all patient-affecting writes require an exact, clinically governed workflow.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 4 | — | — | — | — | — | 4 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-08-17 |
platforms | declared | source | 2026-08-17 |
license | declared | source | 2026-08-17 |
modalities.api.exists | declared | source | 2026-08-17 |
modalities.api.kinds[0] | declared | source | 2026-08-17 |
modalities.api.coverage | declared | source | 2026-08-17 |
modalities.integrations | declared | source | 2026-08-17 |
modalities.extensibility.scripting | declared | source | 2026-08-17 |
modalities.data_access.export | declared | source | 2026-08-17 |
modalities.data_access.import | declared | source | 2026-08-17 |
verdict.scores.api | declared | source | 2026-08-17 |
freshness.watch[0].url | declared | source | 2026-08-17 |
freshness.watch[1].url | declared | source | 2026-08-17 |
freshness.watch[2].url | declared | source | 2026-08-17 |
Last verified 2026-08-17 · volatility high · JSON record