Hospital & Unit Operations
K

Kontakt.io

Kontakt.io sells a care operations platform that connects room level location data with hospital records and work queues, used by more than 200 hospitals including Beth Israel Lahey Health, Sentara, Kaweah Health, Mercy Health and Northeast Georgia Health System. Bluetooth tags and badges travel with patients, staff and equipment, and the cloud Location Engine combines their signals with infrared room sensors to place each one in a room. Floor plans and room status give bed managers, nurses and transport teams a shared view. The Epic integration, available in the Toolbox on Epic Showroom, ties a wristband tag to a patient at registration, shows the patient's location in Unit Manager and Storyboard and logs location events for surgical case tracking.

Patient Flow Agent, launched in January 2026, uses EHR events and location data to forecast census and pending discharges, brings stalled steps to staff attention and moves services such as transport or imaging up a queue, following each hospital's own playbook. Access Agent uses room sensors and Epic schedules to raise outpatient room use, and Patient Journey Analytics shows where delays built up during a stay. Staff Safe sends safety alerts, Asset Tracker finds equipment and manages unit inventory, and a wayfinding kit embeds in apps such as MyChart.

HCA Healthcare deployed the platform across 186 hospitals in nine months, before the agent's launch. The New York company began in 2013, and Philipp von Gilsa is chief executive.

AI Health Index verifiedNovember 20, 2026
Compare Kontakt.io with other vendors
Founded
2013
Headquarters
New York, New York, United States
Website
kontakt.io/
Categories
hospital-operations
Indexed Products
Care Orchestration Platform, Patient Flow Agent, Patient Journey Analytics, Kio Cloud, Staff Safe, Asset Tracker
Buyer Segments
Hospital operations teams, Health systems, Outpatient clinics, Clinical engineering teams
Assessment

Capability Axes

An AI Health Index grade measures what a buyer can verify from public sources on the date shown. It is not a rating of how good the product is. A vendor can build an excellent system and grade low on an axis because it publishes nothing an outsider can check. How grades read

AI Capability
AA on AI CentralityThe artificial intelligence is the product. Remove the model and there is nothing left to sell.
Vendor Published

The Location Engine learns to place tagged people and equipment on a map of rooms using wireless readings and infrared reference signals. That learned location estimate feeds room occupancy, asset tracking and alerts. Patient Flow Agent combines the event stream with EHR information to forecast census, identify pending discharges and surface delays that staff can address. An RFID or Bluetooth tag by itself supplies a signal. The intelligence here is in assigning noisy signals to a room and combining a stream of locations with orders, staffing or transport events to support decisions about hospital capacity.

BB on Autonomy and Oversight ModelThe oversight structure is described and one part is missing, commonly the threshold at which the system stops or what happens after it is wrong.
Vendor Published

Patient Flow Agent can prioritize work for transport or ancillary services, flag a delayed discharge step and surface a recommendation to the team managing beds, and the hospital's configured playbook sets which intervention fits at patient, unit or hospital level. A unit can use the same forecast to prompt a review or to update a work queue on its own, while clinicians and operational staff keep the care and discharge decisions. Automated operational actions are offered without one approval policy covering every action a hospital can configure.

BB on Model and Technology TransparencyThe approach or the suppliers are named without the version and update discipline behind them. Naming a supplier is the entry to this band both here and on Model Supply Chain Disclosure, which ask different questions of the same disclosure: who receives the data, and what produces the output.
Vendor Published

The Location Engine assigns a tag to a room on a matrix rather than reporting a point on a map. A reference architecture explains how particle filtering, unsupervised learning and infrared reference readings drive its predictions, and how a window of observations trades speed against confidence that a tag is in the right room, which matters where adjacent rooms pick up overlapping signals. Patient Flow Agent's documentation names its inputs and workflow actions, with less on how the census and discharge forecasts are trained and calibrated.

BB on Model Supply Chain DisclosureSubstantial partial disclosure, or a chain that is structurally short: an in house build, a cleared model that cannot be quietly swapped, or a deployment where the transfer does not occur at all. Naming the model provider exits the band below into this one; the axis rises from here on the completeness of the party list and on the terms that govern data once it arrives.
Vendor Published

Kontakt.io builds its own Location Engine and the device specific signal models that estimate room occupancy and tag location, fed by readings from tags, access points and optional infrared room sensors, with no third party inference service in that path. Patient Flow Agent combines that location output with EHR events, and the models or outside providers behind its forecasting and agent functions are not named, so the in house build is clear for location and less so for the agent.

CC on Clinical and Operational EvidenceNamed customers, or vendor reported percentages with no method, denominator or reference standard. Scale of use is recorded here and is not treated as evidence of benefit.
Vendor Published

HCA Healthcare's rollout across 186 hospitals in nine months shows the wider operations platform running at network scale, and Riverside Healthcare uses the location system for asset tracking and elopement workflows. Northeast Georgia Health System's chief information officer and Holyoke Medical Center's director of information systems speak to its use in the emergency room and elsewhere.

The homepage lists headline results, among them a 15% cut in length of stay, 20% fewer emergency department boarding hours and 30% fewer missed rounds, with no customer, period or method attached. Patient Flow Agent's discharge and savings example, $4 million a year for a 200 bed hospital, is hypothetical.

BB on AI Safety and PHI StewardshipCategorical commitments are published, such as no training on customer data, without the retention schedule behind them.
Vendor Published

The hosted service keeps customer data, which can include protected health information, logically segregated with role based access, and the security policy covers encryption, logging and retention controls. Inside the workflow a location event can update Epic where staff already work, and administrators set the conditions for automated actions, which matters because a wrong tag assignment can put the wrong location in a work queue. Safeguards specific to the forecast and the agent, such as how often the system flags low confidence or how wrong prioritization is audited, get less detail.

Regulatory and Compliance
BB on HIPAA and BAA PostureBusiness associate status is stated and supported by a substantive privacy document, with the agreement or its scope not fully published. For a vendor outside the United States, an equivalent regime documented to this depth grades here. A vendor whose product does not process protected health information grades here too when it says so plainly and explains the scope, with a service privacy document behind it: stating a position a buyer can rely on is the posture this axis grades, and the band above is closed to it because there is no agreement to publish.
Vendor Published

The security policy says Kontakt.io signs business associate agreements with healthcare customers where required, separates protected health information from other customer data, logs access and sets out how retention and security incidents are handled, and the homepage carries a 2026 HIPAA badge from A-LIGN. The Epic connection associates a tag with a patient, so movement events attach to an identifiable record. The agreement itself is not reproduced, and nothing in the policy covers EHR data used for forecasting, its retention or any downstream processor.

BB on Security Certifications and Trust CenterA recognized certification is named in the vendor own material without the artifact, or with a scope or renewal question the buyer has to raise. A recognized certification here is an audit of how the vendor operates security, such as SOC 2, HITRUST or ISO/IEC 27001. A certification has a scope and a clock, and both are part of this grade. A certification the vendor attaches to its data center, hosting facility or cloud provider, rather than presenting as its own, is the host's and does not count here.
Vendor Published

Kontakt.io holds a SOC 2 Type II report audited by A-LIGN, shown with a 2026 HIPAA badge on its homepage, and describes independent penetration testing, encrypted backups, administrative multifactor authentication, access logs for users and privileged accounts, operational monitoring and separate permissions for integrations. Those controls span location equipment in each hospital and a central cloud service. The auditor's report, the examination period and whether its boundary includes Patient Flow Agent and the other agents are not public.

CC on FDA and Regulatory StatusNo device claim is made and the product is scoped accordingly. Most administrative and operational products sit here and are not penalized for it, because this axis grades the appropriateness of the positioning rather than possession of a clearance. A stated limit on use, such as research use only or a clause that the product gives no medical advice, beside marketing that sells the product for clinical decisions also sits here, with both quoted, because the buyer has to ask which one governs.
Vendor Published

Patient Flow Agent forecasts bed demand and flags barriers such as a pending transport or an ancillary service holding up discharge, and staff act on the alert through operational queues and existing EHR workflows. Patient tracking records where a tagged patient is in the facility. The product is sold for operational coordination and capacity planning, including the order in which services are scheduled, while the decision to discharge stays with care teams. No FDA clearance or device pathway is claimed for the agent, and the hardware's FCC, UKCA, RoHS and UL marks cover other requirements.

CC on AI Governance and Bias DisclosureResponsible artificial intelligence is committed to in policy language with no evaluation behind it. Most of the index sits here.
Vendor Published

Hospitals tailor agent responses to local playbooks and tune how the Location Engine trades reporting speed against room confidence, which gives administrators control over expected behavior in each facility. Patient Journey Analytics rebuilds how long each step took from timestamped operational and EHR events.

No formal governance framework covers the models, and no forecast performance is broken out by patient population, so whether a discharge estimate holds as well on units with a different case mix, or for patients going to different destinations, is not shown.

CC on AI Liability and RecourseMechanisms exist that let someone challenge an output, such as audit trails, source traceability or review before commit, with nothing standing behind the output and no route for the harmed party.
Vendor Published

The service terms set an uptime target with a remedy tied to availability, disclaim the accuracy and completeness of analytics, and cap ordinary contractual liability. Hospital staff can remove a tag association in Epic when a patient leaves a tracked area, and the system reminds staff when an associated device is no longer in the room with the patient, which keeps location data current. No commitment covers correcting an AI error, and Kontakt.io takes no responsibility for losses from a wrong capacity forecast or patient flow recommendation.

Integration and Deployment
AA on EHR and Interoperability DepthNamed bidirectional integrations with major record systems, verifiable in marketplace listings or integration documentation, with evidence the connection runs in production.
Vendor Published

The Epic RTLS integration, available in the Toolbox on Epic Showroom, lets staff link a tag to a patient in Hyperspace or Welcome during admission or registration, then updates Epic patient lists, Unit Manager, Unit Map and Storyboard as the patient moves; surgical case tracking records receive events from location changes, and the system reminds staff to remove an association once the tag leaves the patient.

Epic supplies the patient association and receives location events back, and staff and medical device locations flow into Epic the same way. Access Agent reads Epic schedule templates and live appointment messages, and the wayfinding kit embeds in MyChart.

BB on Deployment Model and Data ResidencyOptions and residency are stated with isolation or the processing path left open.
Vendor Published

Kio Cloud production systems run on AWS, and the service documentation names United States and United Kingdom account regions with separate endpoints for hospital teams. Tags, sensors and gateways on site report over Wi-Fi to the regional cloud, where location and occupancy are computed, and installers configure devices on site but still connect to Kio Cloud for inventory and settings. Where backups are kept, and whether Patient Flow Agent's inference and support work stay within the same regions, are not stated.

Commercial
BB on Commercial TransparencyA price or a pricing basis is published without full tiers, so a buyer can size the cost before making contact.
Vendor Published

Pricing runs per bed or per room, with hardware, software and services bundled around the installation; the room basis fits outpatient space, where the work centers on appointment and exam room use. A hospital can size a quote against the units it plans to equip, and an ROI calculator on the site estimates the return. No rate per bed or room, contract minimum or separate fee for Patient Flow Agent is shown, and those charges and the implementation scope are set in the order.

AA on Setting and Specialty CoverageWhere the product is validated to operate is named and supported, settings and specialties both, whether the coverage is broad or deliberately narrow.
Vendor Published

The platform serves hospital units that locate equipment, coordinate surgery, track discharge progress or answer staff safety alerts, on one room map across inpatient wards, emergency departments, operating rooms and storage, and Northeast Georgia Health System uses it in the emergency room among other settings. Access Agent and KIO Clinic cover outpatient exam rooms, using actual appointment and room occupancy patterns to shape schedules, and NHS hospitals appear among its users. HCA's rollout across 186 hospitals shows the network scale, and the coverage is operational: the same technology serves each department where location, capacity and handoffs drive how work moves.

Alternatives

Alternatives to Kontakt.io

Other products that do the same kind of work as Kontakt.io, and what each one does.

Cognosos, based in Atlanta, sells a real time location system for hospitals built around LocationAI, a machine learning engine that places tagged equipment at room level by comparing Bluetooth signals against a reference map learned at installation.

Apella makes ambient computer vision software for operating rooms and other procedure areas.

Aimbient, known until July 2026 as Surgical Safety Technologies and the maker of the OR Black Box, sells the Aimbient Suite: room cameras, operative video, audio and device telemetry captured from every procedure, read by more than 25 purpose built AI models that turn the recording into…

Opmed sells an AI platform for hospital operations and scheduling, built first for the operating room.

VitVio sells Vetro, operating room software built on what it calls a 3D Spatial Context Engine.

LiveData, based in Cambridge, Massachusetts, sells perioperative workflow and surgical capacity software to hospitals and ambulatory surgery centers.

Commercial

Pricing

Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.

Entry Price Pricing Basis BAA Tier Implementation Source
Quote based
Per bed or per room, with hardware, software and services bundled BAA with healthcare customers where required Bundled into the quoted scope Vendor Published

Pricing is per bed or per room with hardware, software and services bundled. No rate is shown, Patient Flow Agent charges are set in the order, and an ROI calculator on the site estimates the return.