AlertWatch:OB

The mechanism is a maternal early warning score grounded in national obstetric standards, a proprietary filtering layer over the resulting alerts, and real time integration and display of several hundred data elements. Nothing retrieved describes machine learning. The grade describes mechanism, not quality.

Credit is due for honest non inflation, and it is rare in this lane. The company describes itself as clinical decision support software rather than reaching for the AI label, in a category where nearly every competitor does the opposite. Elaborate and Candid Health earn the same credit for the same reason.

What the product actually contributes is information architecture and alert discipline, which is a legitimate and, on this record, deliberately chosen engineering position.

No autonomous action. The system scores, alerts and pages, and clinicians decide. There is no low risk or de escalation output of the kind that creates the invisible failure mode on CLEW, Etiometry and Healthplus.ai.

The sharpest question on this record is the filter, and it is a new form of an old pattern. Proprietary filtering to prevent alarm fatigue necessarily means the system is deciding which alerts a clinician does not see. That is a suppression decision, and it belongs in the same family as Affineon auto handling normal labs and CLEW labelling patients low risk: something is being removed from human attention, and the removal is invisible to the person it is removed from. The difference is that here the suppression is the headline feature rather than a side effect.

Ask directly what the filter suppresses, on what criteria, and what proportion of suppressed alerts preceded a deterioration. Held at B rather than C because the alerting logic itself is grounded in published national standards, the filter reduces alert volume rather than removing a patient from monitoring, and clinicians retain the underlying data display.

The clinical grounding is traceable and that is credited. The score is stated to be based on national obstetric standards, and the postpartum hemorrhage assessment is explicitly tied to ACOG risk criteria, so a clinician can locate the underlying clinical logic in published guidance.

The problem is that the two elements which differentiate the product are both described as proprietary and neither is specified. The maternal early warning score is a proprietary modification of the standards, and the alert filtering is proprietary. The filtering matters most, because reducing alarm fatigue without missing deterioration is the product claim itself, and nothing published describes what the filter suppresses, on what basis, or how often.

No operating characteristics, sensitivity, specificity or positive predictive value are published for either the score or the filter.

Nothing identifies any party in the chain: no model or model family, no hosting arrangement and no sub processor list was located in two passes, and no privacy policy, retention period or training use disclosure was found. What changes this record is corporate rather than technical.

The acquirer describes the platform as displaying and analysing inpatient vital signs, record system data, laboratory systems and its own medical grade wearables together, presented as clinical intelligence across care settings and acuity levels, so obstetric monitoring data now sits inside a platform built to combine with wearable data rather than merely alongside it.

The reach also extends past discharge, since the combined offering spans in hospital monitoring through to care at home and the acquirer's wearable is designed for continuous capture over weeks. A hospital that bought a labour and delivery decision support tool now owns a component of a platform whose design horizon runs from the delivery room into the patient's house. That is a coherent product strategy and it changes what a buyer is agreeing to.

Establish whether obstetric data is used only within the labour and delivery module, what would be required before it flowed into the wider platform, whether that boundary is contractual or a configuration setting, and who decides. Establish retention too, since a birth generates a dense record with the long medico legal horizon that applies across this specialty.

Usage volume is documented, clinical outcome evidence is not. More than 10,000 births assisted at commercial launch in January 2020, rising to more than 15,000 in later reporting, with early sites at the University of Michigan, University of Tennessee and University of Vermont.

The company's research page lists a study evaluating AlertWatch:OB alongside Maternal Early Warning Criteria for detecting severely morbid postpartum hemorrhage, and a 2019 SOAP conference abstract reporting a provider survey in which most respondents felt the system improved safety, communication and response time. Findings from the former were not retrievable, and the latter measures perception rather than outcome. The comparative data from AlertWatch:OR covering more than 17,000 surgeries was a 2014 conference presentation on a different product.

Independent context belongs on this record, because it applies to the whole approach rather than to this vendor alone. A 2025 systematic review appraising modified obstetric early warning scores against PROBAST and TRIPOD found them methodologically weak and at high risk of bias, with several developed by clinical consensus rather than statistically. An earlier systematic review found obstetric early warning systems achieve high sensitivity and specificity but a low median positive predictive value of around 41 percent. Separately, a University of Chicago cohort of 19,611 obstetric patients found a deterioration rate of 0.2 percent, which is why positive predictive value is low across every score in this space.

No privacy policy, data processing statement, retention period or training use disclosure was located. The question the earlier assessment raised about the ownership change is now answered, and the answer is broader than the question.

The acquirer describes the platform as displaying and analysing data from inpatient vital signs, the record system, laboratory systems and its own medical grade wearables together, presented as clinical intelligence across care settings and acuity levels. So obstetric monitoring data does sit inside a platform built to combine with wearable data rather than alongside it.

The reach also extends past discharge. The combined offering is described as spanning in hospital monitoring through to care at home, and the acquirer's wearable is designed for continuous vital sign capture over a period of weeks. A hospital that bought a labour and delivery decision support tool now owns a component of a platform whose design horizon runs from the delivery room into the patient's house.

That is a coherent product strategy and it changes what a buyer is agreeing to. Establish whether obstetric data is used only within the labour and delivery module, what would be required before it flowed into the wider platform, whether that is a contractual boundary or a configuration setting, and who decides.

And establish the retention position for continuous monitoring data specifically, since a birth generates a dense record with the same long medico legal horizon that applies across this specialty.

No public statement on business associate agreements, execution terms or subprocessor disclosure was located. Named academic health system deployments mean agreements exist, and the contracting question the earlier assessment raised turns out to be larger than a change of name.

The chain has at least three commercial parties and possibly four. The product was acquired in 2022 and now sits inside the acquirer's monitoring portfolio. Distribution to United States hospitals runs through a major device manufacturer's patient monitoring business under a separate partnership. The acquirer has also announced a partnership with a clinical monitoring services provider for end to end continuous monitoring.

So a hospital may be introduced to the product by one company, contract with another, have its data processed by a third, and have monitoring performed by a fourth. This index has recorded the same shape in other categories, and the instruction is the same: establish which entity is the business associate, which is a distributor with no processing role, and whether the agreement you signed names the party that actually holds your data.

Two further scope questions follow. Continuous device output attributable to a patient is protected health information, so confirm the agreement covers the monitoring feed and not only record system integration. And where the platform extends to home monitoring on a wearable, establish whether that is inside the same agreement or requires its own.

Ask for the entity list, the processing party, and the scope across settings.

A second pass again located no attestation, trust centre or report request path. The framing recorded elsewhere in this category holds and applies with force here: clearance is a safety and effectiveness determination and is not an information security attestation. Four clearances across the operating room, intensive care and labour and delivery establish that the models were reviewed, not that the estate was examined.

Two things define what an examination would need to cover.

The first is the same architecture this index has identified across this lane. The platform draws inpatient vital signs alongside record system and laboratory data, so it reaches the clinical device network as well as the enterprise network. Hospitals segment those deliberately, and a vendor bridging them is the thing to examine.

The second is the corporate chain, which changes who a buyer should be asking rather than what. The product is owned by one company, distributed by another, and a monitoring services partner has been announced by the owner. A security questionnaire sent to the distributor will not describe the environment where the data actually sits. Direct the request to the entity that processes, and ask whether its attestation scope covers the acquired product specifically, since an acquired platform is frequently outside the acquirer's existing boundary until it is integrated.

That last point is worth pressing given the acquisition is several years old and integration with the acquirer's wearable platform is described as complete.

Ask which report is held, by which entity, and whether this product is inside its scope.

Genuine and repeated clearance history across three products: AlertWatch:OR cleared in 2014 for the operating room, AlertWatch:AC for acute care, and AlertWatch:OB, which the company describes as the first and only FDA 510(k) cleared software system dedicated solely to maternal safety in labor and delivery. That is a specific and checkable competitive claim rather than a vague one, and clearing a dedicated maternal safety indication is not trivial.

Held at B rather than A because no clearance numbers, indications for use text or performance basis were retrieved for the OB product, so the scope of what was actually cleared could not be read directly, and because no recent regulatory activity was identified. Per this index's standing method, the 510(k) summary should be pulled and read on the refresh pass, since the device description and indications routinely differ from marketing in ways that matter.

No subgroup performance, calibration or fairness analysis is published, in the clinical domain where that gap costs most. The company's own framing invokes the disparity directly, citing a US maternal death rate roughly three times that of other industrialised countries and 70 near misses for every death, and arguing that many could have been prevented by a timelier response.

Timeliness of response is exactly where the documented racial disparity in US maternal mortality operates, so a product aimed at that mechanism has both the clearest opportunity to reduce it and the clearest obligation to measure whether it does. Nothing published addresses it.

The independent systematic review evidence that modified obstetric early warning scores are methodologically weak and frequently consensus derived sharpens the point, because a score built on expert consensus inherits whatever the consensus encodes. Same ask as PeriGen and Birth Model: publish subgroup performance, and better, subgroup outcomes.

The published parts of this product are the parts borrowed from public guidance, and the two elements that differentiate it are both described as proprietary and neither is specified. The score is stated to be based on national obstetric standards and the haemorrhage assessment is tied to published risk criteria, so a clinician can locate the underlying clinical logic in guidance anyone can read, and that is genuine traceability.

What is not published is the proprietary modification of those standards, and the proprietary alert filtering. The filtering is the one that matters, because reducing alarm burden without missing deterioration is the product claim itself, and a filter is a decision about what a clinician never sees. Nothing published describes what it suppresses, on what basis, or how often, so a unit cannot audit the alerts that did not arrive and the failure mode leaves no artefact by construction.

No sensitivity, specificity or positive predictive value is published for either the score or the filter, and no warranty, indemnity or remediation commitment was located. The setting raises the stakes: maternal deterioration is rapid, the events that matter are rare, and a suppressed alert in an obstetric unit has a short window before it becomes irreversible. Ask what the filter suppresses and on what rule, the proportion of generated alerts it removes, and the false negative rate against a chart review sample.

Ingests broadly rather than from a single source, integrating hundreds of data elements across physiological monitors, the EMR, laboratory systems and medical history, which is what allows the postpartum hemorrhage assessment to check blood availability and intravenous access alongside vital signs.

Distribution and integration have run partly through Clinical Computer Systems, maker of the OBIX electronic fetal monitoring platform, as both reseller and co marketing partner, which is a practical route into labor and delivery units already running that system. Held at B because no EHR vendor is named, no marketplace listing or partner certification was located, and no FHIR or SMART on FHIR capability is described.

The issue here is currency rather than absence, and it is stated plainly because a buyer needs to know.

Named early sites are the University of Michigan, University of Tennessee and University of Vermont, and usage was reported at more than 15,000 births, but that reporting dates from 2020 and no current deployment, customer count or installed base was identified. AlertWatch was acquired by BioIntelliSense in 2022, whose stated direction combines the AlertWatch display and analysis layer with its own medical grade wearables across care settings, and it was not possible to verify from public sources whether AlertWatch:OB remains actively sold and developed as a standalone obstetric product.

No implementation timeline, hosting architecture or data residency commitment is published. Establish current product status and roadmap directly before evaluating.

No pricing published at any level: no rate card, no unit of pricing such as per delivery or per labor and delivery bed, no band, and no implementation fee. Distribution through a reseller adds a question a buyer should raise early, since a product bought through the OBIX channel may carry different commercial terms from one bought direct, and the 2022 change of ownership makes it worth confirming who the contracting party now is.

Obstetric only, but the span within obstetrics is the widest in this category and it is the right axis to compare on. Coverage runs from triage through labor and delivery into operating rooms and post anesthesia care units and onward through the postpartum period, which matters because a substantial share of severe maternal morbidity and mortality occurs after delivery rather than during it, and postpartum is precisely where continuous attention lapses as the focus shifts to the newborn.

The clean contrast with PeriGen is on what is monitored rather than on quality. AlertWatch monitors the mother across the whole perioperative and postpartum journey and does not address the fetal signal at all, while PeriGen monitors both mother and fetus but is centred on the intrapartum period.

Held at B because the specialty is singular and no gestational age or population limits were retrieved.