{
 "categories": [
  "healthcare",
  "public-sector"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-10",
   "fact": "homepage",
   "note": "Opened product page presents Hepro Respons as a skybasert velferdsteknologiplattform (SaaS) that combines solutions and an integrated responssenter for institutions, omsorgsboliger, and hjemmeboende.",
   "source": "https://hepro.no/merkevare/hepro-respons/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "vendor",
   "note": "The page is published by HEPRO AS and states more than 35 years of welfare-technology deliveries.",
   "source": "https://hepro.no/merkevare/hepro-respons/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "license",
   "note": "Hepro Respons is sold as a municipal/health-trust SaaS service, not a free download.",
   "source": "https://hepro.no/merkevare/hepro-respons/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "deployment",
   "note": "The page states the platform is delivered as SaaS (Software as a Service) and is open and scalable.",
   "source": "https://hepro.no/merkevare/hepro-respons/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "platforms",
   "note": "Hepro Respons App delivers alarms to staff smartphones. The administration product is described as a cloud platform. This record treats web as the established automation platform; app-store OS editions were not opened.",
   "source": "https://hepro.no/merkevare/hepro-respons/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.exists",
   "note": "Hepro states it offers many integration and service-development solutions and names Alarm API, Admin API, and VKP API as the main elements.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.coverage",
   "note": "Alarm API connects alarm senders, sensors, medication solutions, and smartphones. Admin API adds and synchronises information with surrounding systems. VKP API exchanges service-recipient data and journals alarms. Authentication, protocol kinds, and an endpoint catalogue are not published.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.docs",
   "note": "Opened as the public patient-alarm page that declares the APIs. It is a capability summary, not a self-serve reference.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Alarm API and standard protocols are named for connecting new alarm senders to the Hepro Respons platform.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "Admin API is named for administration and follow-up integrations that add and synchronise information.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.extensibility.scripting[2]",
   "note": "VKP API is named as an NHN collaboration for service-recipient data and journal write of alarms, supported for EPJs with a VKP agreement including Helseplattformen.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.extensibility.scripting[3]",
   "note": "IoT-HUB is named as Hepro's integration platform for new technology, operations monitoring, and redundancy of the patient-alarm plant.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "verdict.scores.api",
   "note": "Named Alarm, Admin, and VKP APIs exist as integration surfaces, but public authentication and endpoint documentation were not opened. That is the narrow/gated tier.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Hepro Respons product page, including SaaS delivery and named municipal stories.",
   "source": "https://hepro.no/merkevare/hepro-respons/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current patient-alarm page naming Alarm API, Admin API, VKP API, and IoT-HUB.",
   "source": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Hepro welfare-technology overview that presents Hepro Respons.",
   "source": "https://hepro.no/forside/velferdsteknologi/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-10",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://hepro.no/merkevare/hepro-respons/"
   },
   {
    "type": "docs",
    "url": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/"
   },
   {
    "type": "docs",
    "url": "https://hepro.no/forside/velferdsteknologi/"
   }
  ]
 },
 "homepage": "https://hepro.no/merkevare/hepro-respons/",
 "id": "hepro-respons",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [],
   "coverage": "partial",
   "docs": "https://hepro.no/produktkategori/velferdsteknologi/pasientvarsling/",
   "exists": true,
   "kinds": []
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [],
   "import": []
  },
  "extensibility": {
   "scripting": [
    "alarm-api",
    "admin-api",
    "vkp-api",
    "iot-hub"
   ],
   "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. Hepro Respons is a SaaS console with a staff app. The documented machine path is Hepro's declared Alarm, Admin, and VKP APIs, not browser control of an alarm console. Clinical safety and health-data law still govern every write.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Hepro Respons",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "tellu-care",
   "sensio-365",
   "dignio",
   "visma-omsorg-profil"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Hepro",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 3,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 3,
   "rpa": null
  },
  "summary": "Hepro Respons is automatable today only through vendor-declared integration APIs without a public endpoint catalogue. This record is Hepro's SaaS welfare-technology platform for institutions, care homes, and home-care users, with an integrated response centre. It is not TelluCare, Sensio 365, or Dignio. The product page states that the platform is open and scalable and can integrate existing and new solutions, including safety alarms, digital supervision, and medication dispensers. The patient-alarm category page names Alarm API (standard protocols for alarm senders), Admin API (add and synchronise information with surrounding systems), VKP API (NHN exchange of service recipients and journal write of alarms for EPJs that have a VKP agreement, including Helseplattformen), and an IoT-HUB integration platform. Public pages do not publish authentication, protocol kinds, scopes, or a self-serve developer portal. Municipal deliveries named on opened pages include Stj\u00f8rdal and Bod\u00f8. First-party MCP ownership is not established. Computer-use viability is unassessed. API scores 3 and is the best path.\n"
 }
}