{
 "categories": [
  "healthcare",
  "clinical"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-08-17",
   "fact": "homepage",
   "note": "WebMed presents its product as a Norwegian cloud-based EPR for general practitioners, emergency clinics and specialists.",
   "source": "https://webmed.no/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "platforms",
   "note": "WebMed provides a Windows client and a supported Parallels portal route for macOS access.",
   "source": "https://webmed.no/wp-content/uploads/2024/11/Nytt-Oppsett-av-Parallels-WebMed-pa-Mac-OS.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "license",
   "note": "WebMed is licensed commercially per clinician with implementation, migration and separately priced optional modules.",
   "source": "https://webmed.no/priser/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.api.exists",
   "note": "WebMed offers a first-party integration framework based on SMART on FHIR for third-party applications launched inside the EPR.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.api.kinds[0]",
   "note": "Approved SMART apps receive pseudonymised launch identifiers and can participate in a governed note-generation and save-back workflow.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.api.coverage",
   "note": "WebMed explicitly says third-party SMART apps do not receive clinical journal data; public evidence covers app launch and note writeback, not a general clinical record API.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.integrations",
   "note": "WebMed names integrations with Norwegian laboratory ordering systems, laboratories, clinical devices and LIMS in addition to national and patient-dialog services.",
   "source": "https://webmed.no/funksjoner-og-egenskaper/integrasjon-mot-laboratorier/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.extensibility.scripting",
   "note": "The extensibility path consists of approved SMART apps plus contracted LIMS, device and service integrations rather than arbitrary in-tenant scripting.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.data_access.export",
   "note": "Approved workflows exchange pseudonymous launch context, generated notes, electronic messages, orders and reports; the public SMART surface does not export clinical journal data.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "modalities.data_access.import",
   "note": "WebMed imports governed note writebacks, laboratory results, instrument measurements, electronic messages and migrated source-journal data.",
   "source": "https://webmed.no/tilleggsmoduler/lims-boks-laboratory-information-management-system/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "verdict.scores.api",
   "note": "The standards-based SMART launch and controlled note writeback are meaningful, but explicit clinical-data isolation and absent public scopes, endpoints and SDK keep this below a broad API.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current SMART on FHIR integration, data-isolation and approved-app page.",
   "source": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current laboratory, ordering-system and device integration page.",
   "source": "https://webmed.no/funksjoner-og-egenskaper/integrasjon-mot-laboratorier/",
   "tier": "declared"
  },
  {
   "date": "2026-08-17",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current product package, included national integrations and commercial terms page.",
   "source": "https://webmed.no/priser/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-08-17",
  "volatility": "high",
  "watch": [
   {
    "type": "smart-framework",
    "url": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/"
   },
   {
    "type": "clinical-integrations",
    "url": "https://webmed.no/funksjoner-og-egenskaper/integrasjon-mot-laboratorier/"
   },
   {
    "type": "product-package",
    "url": "https://webmed.no/priser/"
   }
  ]
 },
 "homepage": "https://webmed.no/",
 "id": "webmed-cgm-journal",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [],
   "coverage": "partial",
   "docs": "https://webmed.no/tilleggsmoduler/ki-integrasjoner/",
   "exists": true,
   "kinds": [
    "smart-on-fhir-app-launch"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [
    "clinical-safety-not-measured",
    "remote-client-not-measured"
   ],
   "viability": "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"
   ]
  },
  "extensibility": {
   "scripting": [
    "smart-on-fhir-framework",
    "approved-smart-apps",
    "lims-bridge",
    "device-integrations"
   ],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "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.\n",
   "ui_stack": [
    "windows-clickonce",
    "remote-application"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "WebMed",
 "platforms": [
  "windows",
  "macos"
 ],
 "related": {
  "alternatives": [
   "cgm-journal",
   "dips",
   "epic-ehr"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "WebMed",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 4,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 4,
   "rpa": null
  },
  "summary": "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\u00fcrst 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.\n"
 }
}