{
 "categories": [
  "ehr",
  "healthcare",
  "public-sector"
 ],
 "deployment": "web",
 "evidence": [
  {
   "date": "2026-10-16",
   "fact": "homepage",
   "note": "Opened as the current Esko APTJ product page.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "name",
   "note": "Esko Systems presents Esko APTJ as the asiakas- ja potilastietoj\u00e4rjestelm\u00e4 for primary care, specialised care, and social care.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "vendor",
   "note": "The product page is published by Esko Systems Oy, with the company address and business ID 3104530-8.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "license",
   "note": "The page presents Esko APTJ as Esko Systems Oy's product and asks organisations to contact the company. It is not offered as a free public service.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "deployment",
   "note": "The 24 August 2023 vendor post describes the integration platform and says solutions can also be delivered as containers. It does not state a hosted tenant or an on-prem install, so deployment is web.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "platforms[0]",
   "note": "The opened product and integration pages do not document an iOS or Android app. The public client surface used here is web.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "status",
   "note": "The product page presents Esko APTJ as the current customer and patient information system.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.exists",
   "note": "Esko Systems says it built a standards-based integration solution that carries Esko traffic to other systems in the APTJ ecosystem, on IRIS for Health.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.kinds[0]",
   "note": "The post says the integrations are based on an extensible FHIR data store.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.kinds[1]",
   "note": "The same post says the integrations are based on HL7 messages.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.kinds[2]",
   "note": "The post says the architecture includes comprehensive OpenAPI descriptions. The opened pages do not link an OpenAPI document.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.auth[0]",
   "note": "The vendor states that desktop integrations are based on SmartOnFHIR.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.coverage",
   "note": "The FHIR Demo 2025 page says SMART App Launch is in production with partner suppliers, including Una Lomake, and that Esko's own module is launched the same way. It says the FHIR resources Esko currently produces and uses are Patient and Organization. Other resources are listed as in development. Coverage is partial.",
   "source": "https://fhir.fi/en/demo2025/esko/",
   "tier": "community"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.docs",
   "note": "Opened as the public FHIR Demo 2025 description of Esko's live and in-development resources. It names no base URL.",
   "source": "https://fhir.fi/en/demo2025/esko/",
   "tier": "community"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.api",
   "note": "Production SMART App Launch and two named live FHIR resources are a usable but narrow path. Missing base URL, token endpoint, and OpenAPI document keep the score at 4.",
   "source": "https://fhir.fi/en/demo2025/esko/",
   "tier": "community"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Esko APTJ product page.",
   "source": "https://eskosystems.fi/tuoteperhe/aptj/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the 24 August 2023 vendor post on FHIR, HL7, OpenAPI, and SmartOnFHIR.",
   "source": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the FHIR Demo 2025 Esko page, including the production and in-development resource lists.",
   "source": "https://fhir.fi/en/demo2025/esko/",
   "tier": "community"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-16",
  "volatility": "medium",
  "watch": [
   {
    "type": "product",
    "url": "https://eskosystems.fi/tuoteperhe/aptj/"
   },
   {
    "type": "docs",
    "url": "https://eskosystems.fi/blogi-modernit-teknologiat-ja-rajapinnat-eskossa/"
   },
   {
    "type": "docs",
    "url": "https://fhir.fi/en/demo2025/esko/"
   }
  ]
 },
 "homepage": "https://eskosystems.fi/tuoteperhe/aptj/",
 "id": "esko-aptj",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "SmartOnFHIR"
   ],
   "coverage": "partial",
   "docs": "https://fhir.fi/en/demo2025/esko/",
   "exists": true,
   "kinds": [
    "fhir",
    "hl7",
    "openapi"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "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. The opened pages describe Esko APTJ and its integration platform. They do not document a browser application that this record can score as RPA. The machine path is the FHIR, HL7, OpenAPI, and SmartOnFHIR surface.\n",
   "ui_stack": [],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Esko APTJ",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Esko Systems",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 4,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 4,
   "rpa": null
  },
  "search": {
   "description": "Esko documents FHIR, HL7, OpenAPI, and SmartOnFHIR. The 2025 FHIR demo names production SMART App Launch and live Patient and Organization resources.",
   "title": "Esko APTJ is automatable through FHIR and SMART"
  },
  "summary": "Esko APTJ is automatable as Esko Systems' Finnish customer and patient information system for primary care, specialised care, and social care, not as Apotti, Kanta, or Omaolo. The best path is the integration surface the vendor describes on InterSystems IRIS for Health: an extensible FHIR store, HL7 messages, OpenAPI descriptions, and SmartOnFHIR for desktop integrations. The HL7 Finland FHIR Demo 2025 page states that SMART App Launch is in production with partner modules, including Una Lomake, and with Esko's own module. It states that the FHIR resources Esko currently produces and uses are Patient and Organization, including for HL7v2 messages. Appointment, Encounter, and other resources are listed as active development. The opened pages do not publish a base URL, an OpenAPI document, or a token endpoint. First-party MCP ownership is not established. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 4 because production SMART and two live FHIR resources are named and the public description remains a demo, not a callable catalogue.\n"
 }
}