{
 "categories": [
  "healthcare",
  "clinical",
  "ehr",
  "public-sector"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-08-28",
   "fact": "homepage",
   "note": "Pridok presents a 100 percent web-based electronic patient record used in a browser, with vendor-stated figures of 13 million journals, 1,150 GPs, 600 private-practice doctors and 40 municipalities.",
   "source": "https://pridok.no/",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "deployment",
   "note": "The price page states Pridok EPJ is web-based like online banking, needs only a browser, and has no customer server or backup costs.",
   "source": "https://pridok.no/priser/",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "platforms",
   "note": "The product page states the only client requirement is a web browser, on any device, at any time.",
   "source": "https://pridok.no/",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "license",
   "note": "Pridok publishes commercial monthly licence prices for GPs, contract specialists and other clinicians, plus conversion and startup fees.",
   "source": "https://pridok.no/priser/",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.api.exists",
   "note": "Leyr's Pridok setup guide, reviewed 12 February 2026, states that Pridok supports API versions V1, V2 and V3 on different endpoints and that Leyr selects the version during clinic setup.",
   "source": "https://docs.leyr.io/product/ehrs-setup/pridok",
   "tier": "community"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.api.kinds[0]",
   "note": "Leyr's Pridok product page documents HTTP integration for appointments, patients, care units, resources, services and time slots through its developer portal.",
   "source": "https://leyr.io/ehrs/pridok",
   "tier": "community"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.api.coverage",
   "note": "Leyr labels the Pridok connector a pilot, requires manual verification, and does not publish a first-party Pridok endpoint or authentication catalogue.",
   "source": "https://docs.leyr.io/product/ehrs-setup/pridok",
   "tier": "community"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Pridok help documents in-product AI integrations with Medbric, Journalia, Noteless, Stenoly and Midlaier that open in a browser tab and send generated text back into the daily note.",
   "source": "https://hjelp.pridok.no/nb/articles/10485771-hvordan-aktivere-og-bruke-ai-integrasjon-med-pridok",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "The Integrations collection lists Persontjenesten, Altinn access, HP Link test patients, electronic death certificates, Unisoft Triage, payment providers and NHN membership setup.",
   "source": "https://hjelp.pridok.no/nb/collections/11529026-integrasjoner",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.data_access.import",
   "note": "The Medbric guide shows a Save in Pridok action that appends generated daily-note text and records the source in revision history.",
   "source": "https://hjelp.pridok.no/nb/articles/10449901-medbric-brukerveiledning",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://pridok.no/llms.txt returned 404 on 2026-08-28.",
   "source": "https://pridok.no/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-08-28",
   "fact": "verdict.scores.api",
   "note": "The only public programmatic path is a third-party pilot plus partner note writeback. There is no first-party auth model, sandbox or general journal CRUD catalogue, so the path stays in the narrow-and-gated band.",
   "source": "https://docs.leyr.io/product/ehrs-setup/pridok",
   "tier": "community"
  },
  {
   "date": "2026-08-28",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as Pridok's current Integrations help collection.",
   "source": "https://hjelp.pridok.no/nb/collections/11529026-integrasjoner",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current AI-integration activation article.",
   "source": "https://hjelp.pridok.no/nb/articles/10485771-hvordan-aktivere-og-bruke-ai-integrasjon-med-pridok",
   "tier": "declared"
  },
  {
   "date": "2026-08-28",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as Leyr's current Pridok API version and credential setup page.",
   "source": "https://docs.leyr.io/product/ehrs-setup/pridok",
   "tier": "community"
  }
 ],
 "freshness": {
  "last_verified": "2026-08-28",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://hjelp.pridok.no/nb/collections/11529026-integrasjoner"
   },
   {
    "type": "docs",
    "url": "https://hjelp.pridok.no/nb/articles/10485771-hvordan-aktivere-og-bruke-ai-integrasjon-med-pridok"
   },
   {
    "type": "api",
    "url": "https://docs.leyr.io/product/ehrs-setup/pridok"
   }
  ]
 },
 "homepage": "https://pridok.no/",
 "id": "pridok",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [],
   "coverage": "partial",
   "docs": null,
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [],
   "import": [
    "ai-generated-daily-notes",
    "national-person-register-data"
   ]
  },
  "extensibility": {
   "scripting": [
    "partner-ai-note-writeback",
    "national-health-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. Partner AI note writeback and national-service setup are the documented automation surfaces. Visual control of a clinical journal is not a substitute for a governed integration.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Pridok EPJ",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "webmed-cgm-journal",
   "cgm-journal",
   "dips"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Pridok",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 3,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 3,
   "rpa": null
  },
  "summary": "The best evidenced automation path for Pridok EPJ is a partner-gated programmatic surface, not a first-party developer catalog. A third-party integration platform documents that Pridok exposes API versions V1, V2 and V3, selected per clinic, and that production use needs a Care Unit ID plus manual verification. That path is still a pilot and does not publish first-party authentication, scopes or an endpoint catalogue. Pridok's own help center documents in-product AI integrations with Medbric, Journalia, Noteless, Stenoly and Midlaier that can append generated text to the daily note after a clinic contract and manager approval. The same help collection covers national-service setup for Persontjenesten, Altinn/HelseID delegation, HP Link test patients and related NHN services. Those are packaged clinic integrations, not a general read-write journal API. Vendor pages present a browser-only commercial EPJ and do not publish MCP, CLI, SDK or iPaaS connectors. No computer-use probe was run. Clinical safety, health-data law and human review still govern every write.\n"
 }
}