Caresyntax

Caresyntax sits close to the AI ready versus AI powered line the index uses elsewhere, and lands on the right side of it without clearing it comfortably. The substrate is operating room integration: video and audio management, device control, capture routing and EMR linked worklists, all of which are conventional OR integration functions that predate machine learning and would deliver value with none in the system. The AI runs on top, and it is genuinely substantial, since analysing video, audio, images and connected device output together is a harder multimodal problem than anything else in this category attempts. The durable asset is nonetheless the installed base and the integration work across 4,000 operating rooms, not a model. Graded B rather than C because the analytics are differentiated rather than decorative, and rather than A because a buyer purchases the platform first and the intelligence second.

Nothing in the platform acts autonomously. It surfaces information to the surgical team live during a procedure and produces analysis afterwards, with clinicians retaining every decision. What is not published is how the intraoperative layer behaves under pressure: no disclosure was located on how real time prompts are presented, whether they can be suppressed, how alert burden is managed, or what happens when the system's read of a procedure diverges from the surgeon's. Intraoperative decision support is a setting where a mistimed or unexplained prompt is itself a safety concern, and the absence of any published human factors position is the gap. Publishing the alerting and suppression design would move this to A.

The description stays at the level of proprietary software and AI applied to large volumes of video, audio, images, device, clinical and operational data. No model family, architecture or validation is disclosed, and no accuracy figure was located for any individual analytic. The multimodal claim is the one most in need of substantiation, because combining audio and video inference in an acoustically chaotic room full of equipment is materially harder than analysing an endoscopic feed alone, and nothing published describes how well it works. Naming which analytics are model driven and which are rules over device telemetry would be the most useful single disclosure.

Real operational results exist and none of them reached this assessment through the vendor. A University of Iowa deployment analysing operating room video and audio is reported to have cut turnover by roughly 10 to 15 minutes on average, enough for an additional case per room per day, and to have surfaced lapses in prophylactic patient warming associated with postoperative infection risk. A 2023 publication is reported to show cost reduction and quality of life improvement in colorectal surgery. Both reached this record through third party summaries rather than retrieved vendor or primary sources, so they are recorded as secondary sourced and warrant confirmation. Scale is substantial at more than two million procedures a year across 4,000 rooms, but the index rule that deployment volume does not substitute for evidence of benefit applies. Graded C on sourcing quality rather than on absence of results, and a retrieved primary citation would likely move this to B.

The audio capture is the part buyers underestimate. Caresyntax analyses sound from the operating room alongside video and device data, and an operating room microphone records the surgical team talking, including teaching, disagreement, error recognition and ordinary conversation that no one framed as a clinical record. That is simultaneously patient data and staff speech, and the index has treated the surveillance of named clinicians as a first order concern since the cybersecurity lane. No vendor published statement was located on audio retention, whether speech is transcribed or only analysed acoustically, who inside an institution can replay it, or whether staff consent separately from patients. The platform is described as medical grade, which is a positioning claim rather than a stewardship disclosure. Publishing the audio handling policy would move this to B and is the disclosure this vendor most needs.

No HIPAA statement, BAA template or scope description was located in retrieved vendor material, so the axis is left unrated on absence of evidence rather than graded on inference. As with Theator, this abstention is not neutral: a platform holding operating room video, audio and linked clinical records is unambiguously processing protected health information at scale, and an enterprise vendor operating in more than 4,000 rooms will have executed BAAs. The gap is that nothing is publicly documented, so scope, subprocessors and the treatment of audio in particular cannot be assessed before a sales conversation.

No SOC 2 Type II, HITRUST or ISO 27001 attestation was located and no trust center was found in retrieved material. The platform is described as medical grade and interoperable, and a Google Cloud partnership provides infrastructure assurance, but neither is an application level attestation. For a European headquartered lineage operating across international markets, an ISO 27001 certificate would be the expected artefact and its absence from public materials is notable rather than damning. Given enterprise scale and insurer investors, the likelier explanation is that certifications exist and are not published, which is itself a finding: buyers should ask rather than assume in either direction.

No FDA clearance was located for the platform and the axis is rated accordingly rather than penalized, but the position is less settled here than for the other vendors in this vein. Caresyntax describes real time clinical decision support delivered to the care team during a procedure, and clinical decision support software sits in a regulatory grey zone whose boundaries have moved recently, with the FDA signalling in January 2026 a lighter touch on digital health and CDS products. Software that informs an intraoperative decision is a different regulatory proposition from software that summarises a case afterwards. Buyers should establish which specific analytics the vendor treats as non device CDS and on what reasoning, because the answer determines who carries the risk if a prompt is wrong.

This is the most consequential row on the record and it turns on who the customer is. Caresyntax states plainly that its insights serve insurance companies seeking to understand risk and devise more tailored policies, and its investor base includes the medical liability insurers ProAssurance and Relyens. That means performance data generated from a named surgeon's operations flows toward the parties who price that surgeon's malpractice cover. The arrangement may well be aggregated and anonymised, and nothing located suggests otherwise, but nothing located confirms it either, and the disclosure a surgical department needs before signing is precisely that boundary: what leaves the institution, at what level of aggregation, and whether individual performance can be reidentified downstream. The unadjusted benchmarking problem recorded against Theator applies here too, since comparative surgeon analytics without published risk adjustment for case mix penalise whoever accepts the hardest cases. Publishing the data sharing boundary with the insurance line of business would move this to B.

Interoperability is a design principle here rather than a feature, and the vendor neutral positioning is meaningful in a market where operating room integration is dominated by device manufacturers selling into their own ecosystems. The platform integrates connected device output, controls equipment, manages video and audio routing, and links to the EMR for worklist creation, which is genuine bidirectional clinical system integration rather than an asserted connector list. What is not published is which EHR systems are supported by name, how deep the write back goes beyond worklists, and whether device coverage spans the major surgical equipment vendors or a subset. Naming supported EHRs and device manufacturers would move this to A.

The architecture is described as edge to cloud, which is the correct shape for this problem: video and audio inference has to happen close to the operating room for latency and bandwidth reasons, with aggregation and analytics in the cloud, and naming that split is more disclosure than most peers offer. A Google Cloud partnership indicates the cloud layer. What is missing is residency detail, which matters more than usual for a company operating across US and European markets, since operating room video and staff audio from an EU institution carry obligations that a US hosted analytics tier would complicate. Naming the regions and stating what stays on premise would move this to A.

No rate, unit or charging mechanism was located. Third party commentary describes an analytics as a service subscription model for the operating room, which is recorded as secondary sourced and unconfirmed. Two structural questions matter more here than the headline number. The first is what the platform costs against what it displaces, since the operational business case rests on throughput gains such as an additional case per room per day, which is a savings linked framing the index scrutinises. The second is whether the multi customer model affects pricing, specifically whether a hospital's fee is offset by the value of its data to the device manufacturer and insurance lines of business. That is a fair question to ask directly and a buyer is entitled to a plain answer.

The broadest surgical footprint in the index. Software runs in more than 4,000 operating rooms worldwide, supports over 30,000 surgical professionals and touches more than two million procedures a year, across an international rather than US only base. Because the platform instruments the room rather than a specific procedure type, coverage is not confined to endoscopic or robotic cases the way video only analytics are, which is a genuine structural advantage over the rest of this vein. The buyer set is equally broad and spans hospitals, surgeons, medical device manufacturers and insurers. The caveat that keeps this honest rather than lowering it: breadth of installation is not the same as depth of analytic coverage per specialty, and no published breakdown of which analytics are validated for which procedure types was located.