VigiLanz

The company's own product page describes the engine as flexible, rule based AI, and that phrase is the finding. A rules engine and a learned model are different things, and joining the two terms produces language that reads as artificial intelligence to a buyer while describing configurable rules to an engineer. Independent product listings describe the same platform plainly as a configurable rule based engine converting record data into alerts.

A separate third party listicle attributes natural language processing and machine learning for adverse reaction detection to the product, and that claim was not corroborated anywhere in the vendor's own material and is not graded on. As with its principal competitor the genuine model reaching clinicians through this product is licensed rather than built, following the October 2025 collaboration bringing an external precision dosing engine into these workflows. Graded on the mechanism, and the direct competitor is graded higher on transparency for describing the same architecture without the label.

Alerts reach a pharmacist who reviews and intervenes, with the platform never acting on an order. Rules are customer configurable, so the institution controls what fires, and the company frames the goal as helping teams focus on preventing harm instead of reviewing endless records, which is an explicit statement that the product exists to triage attention.

That framing makes the missing measurement conspicuous: retrieval located no alert burden per patient day, no override rate and no proportion of alerts resulting in a pharmacist intervention. A surveillance product's entire value proposition is that it directs scarce pharmacist time at the right patients, and no vendor in this segment publishes the number that would demonstrate it. Delivery of alerts directly into the record system is a genuine workflow credit, since an alert a pharmacist must leave their system to see is an alert that competes for attention it may not win.

The underlying architecture is inspectable in the way all rules engines are, since a hospital configuring its own alert criteria can read every criterion behind every alert, and that structural advantage is real. What holds this a grade below its direct competitor is the labelling rather than the architecture.

Describing configurable rules as rule based AI and the platform as artificial intelligence powered surveillance gives a reader a materially less accurate picture of the mechanism than a competitor that describes the same design without reaching for the term. Retrieval located no technical documentation, no description of the shipped rule library, no validation methodology for supplied rules and no account of how the external dosing engine now integrated into these workflows behaves. A buyer should ask directly which components learn from data and which evaluate rules, and expect a specific answer.

The company cites eight consecutive years as the top ranked pharmacy surveillance solution in one analyst firm's rankings, which is a genuine market signal about customer satisfaction and is not evidence of clinical benefit, and any buyer relying on it should check the current listing directly since analyst rankings carry qualifying conditions about sample size and product scope that vendor citations rarely reproduce.

Retrieval located no peer reviewed outcome study, no controlled evaluation, no published alert validity data and no measurement of adverse drug events avoided. Twenty five years in market across acute, post acute and ambulatory settings is a substantial operational track record, and this index treats market longevity and clinical evidence as separate questions by standing practice. The parent's scale in healthcare data makes the absence of published outcome analysis more notable rather than less.

The platform ingests near real time data regardless of record system from acute, ambulatory and other care settings, spanning admission feeds, medication administration records, laboratory results, microbiology and medication history, which is among the broadest continuous clinical data footprints in this category.

The parent operates at national data scale across hundreds of thousands of clinical facilities, which makes the secondary use question concrete: a hospital should establish in writing whether its surveillance data remains scoped to its own alerting or contributes to the parent's wider analytics and life sciences offerings, particularly since the acquisition rationale explicitly cited enriching the parent's life sciences portfolio and increasing its clinical data connectivity. Retrieval located no retention schedule, no de identification statement and no product level data use description.

Retrieval located no product level privacy rule statement, no business associate agreement terms, no execution path and no compliance page for this platform. Scope is stated plainly because it affects how this grade should be read: the assessment was scoped to the product's own material, and the parent is a large national healthcare data company whose corporate compliance documentation was not retrieved in this pass, so this describes what a buyer researching the product finds rather than what the organisation holds.

Of the axes on this record it is the one most likely to move on further retrieval. A hospital evaluating the platform should ask for the corporate compliance package by name rather than relying on the product pages, which say nothing on the subject.

Retrieval located no service organisation controls report, no HITRUST certification, no ISO 27001, no trust centre, no penetration testing cadence and no vulnerability disclosure programme in the product's own material. The same scope caveat applies as for the privacy axis: this was assessed at product level and the parent's corporate attestations were not retrieved, so the grade reflects what is discoverable by someone researching this platform rather than a conclusion about the organisation's security posture.

The contrast with the direct competitor is the useful observation, since that product names health information technology certification and third party vulnerability assessment on the page a buyer actually reads. Publishing at product level rather than burying attestations at corporate level is a small change with a large effect on procurement.

No device clearance was located and none would be expected for rules based surveillance alerting, which falls within the statutory exclusion for non device clinical decision support because a clinician can inspect the criteria that produced the alert. That reviewability argument is stronger for a configurable rules engine than for almost anything else in this category, and it is worth stating in the vendor's favour.

The complication arrives with the external precision dosing engine now integrated into these workflows, since computing an insulin or antibiotic dose is a different regulatory act from raising an alert, and the products in this category that compute doses hold device clearance. Which entity carries regulatory responsibility for that integrated component, and on what basis, is not addressed publicly by either party to the collaboration.

Retrieval located no performance reporting by patient characteristic, no bias assessment, no rule validation methodology and no post deployment monitoring statement. The governance exposure in configurable rules deserves stating because it is easy to assume that transparency removes it. Rules encode thresholds, and thresholds drawn from one population applied to another produce systematically different alerting, with no drift detection concept anywhere in this segment.

A rule that has become wrong as resistance patterns, formularies or practice changed simply keeps firing, carrying the authority of the institution that wrote it, and the products best placed to detect that are the surveillance platforms themselves. Nothing published describes tooling for identifying rules that fire frequently without ever changing care, which is the single most useful governance feature this segment could build.

Interoperability is the platform's core competence rather than an add on. It ingests near real time clinical data regardless of which record system a hospital runs, spanning admission feeds, medication administration records, laboratory results, microbiology and medication history across acute, ambulatory and other settings, with data described as pre mapped so clinical criteria can be applied without a hospital building the mappings itself.

Alerts are returned directly into the record system for faster acknowledgement rather than requiring clinicians to work in a separate application, and third party listings report support for the FHIR standard alongside the external precision dosing integration.

Held at B because no named marketplace certification, published conformance statement or interface documentation was located, and because the integration claims come largely from the vendor and from secondary listings rather than from technical material.

Delivery is cloud based software as a service, now positioned within the parent's wider provider cloud platform, serving acute, post acute and ambulatory facilities. Retrieval located no named hosting provider, no cloud region, no data residency commitment and no description of degraded behaviour when feeds are interrupted, which matters for a system whose value is continuous monitoring rather than periodic reporting.

The 2024 acquisition adds a practical question for existing customers: whether the platform continues to run on its original infrastructure or is being consolidated into the parent's, and what that means for interface stability, since a surveillance platform's data feeds are among the more fragile integrations in a hospital estate.

No price, unit, pricing basis or contract shape was located in the vendor's own material. A third party software directory describes a tiered enterprise model differentiated by facility type and size with a one time implementation fee and an annual licence, which is plausible and is not relied upon here, since directory listings of this kind are frequently machine generated and this index does not grade on sources it cannot attribute.

The commercial questions to raise directly are the tier structure, whether pricing scales by facility, bed or covered setting, what the implementation fee covers, and how the externally supplied precision dosing capability is licensed, since that component comes from a separate company and a hospital should know whether it is included, priced separately, or contracted with a third party.

Setting coverage is the broadest in the surveillance segment, spanning acute, post acute and ambulatory care, which is wider than its principal competitor's essentially inpatient footprint and reflects a data ingestion architecture built to be record system agnostic.

Functional coverage spans pharmacy surveillance, infection prevention and control, antimicrobial stewardship, quality and performance improvement and patient safety event reporting, with specific capabilities for intravenous to oral conversion opportunities, transitions of care and antibiogram trending.

Held at B because coverage is United States only, because the module structure means a buyer's actual coverage depends on which tier is purchased rather than on the platform's full capability, and because ambulatory and post acute deployment is described more thoroughly in marketing than it is evidenced in named customers.