Hospital & Unit Operations
C

CalmWave

CalmWave combines bedside monitor signals, medications and EHR activity to help hospital teams manage alarm burden and understand patient changes. Its machine learning system proposes alarm thresholds with supporting data, while nurses retain control of the bedside monitor and can reject recommendations. Clinical safety gates and physician orders constrain when an adjustment can be suggested.

Operational views extend to device performance and hospital activity. Wellstar Kennestone's CCU provides a named deployment for the alarm workflow. The newer Tessera service offers early access to queries across deidentified clinical data for research. The two offerings serve different tasks: bedside operational support and aggregate data exploration.

AI Health Index verifiedOctober 14, 2026
Compare CalmWave with other vendors
Founded
—
Headquarters
Seattle, Washington, US
Website
calmwave.com/
Categories
hospital-operations
Indexed Products
CalmWave Operations Platform, CalmWave Optimized recommendations, Tessera (early access)
Buyer Segments
Hospital operations leaders, Critical care nursing teams, 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
BB on AI CentralityThe model is the engine of a core module. The platform carries other value, but this capability does not exist without it.
Vendor Published

Machine learning drives alarm optimization and patient specific recommendations. The platform also combines monitor, medication and EHR data for operational analysis, giving hospitals a shared view beyond the recommendation engine.

AA on Autonomy and Oversight ModelWhat the system may do and what it may not do are both published, with escalation thresholds, override paths and the conditions that route a case to a person.
Vendor Published

Recommendations require stable vitals, no recent intervention, no threshold change for three hours and repeated alarms without instability. Nurses review the rationale, adjust monitors manually, or reject with a reason. Physician orders bound permitted changes.

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

Transparent AI uses machine learning with structured vital signs, medication, staffing and EHR activity. Recommendations expose their rationale and apply clinical safety gates. Model identifiers, training dataset composition and version change history remain unspecified.

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

CalmWave runs its own Transparent AI algorithms on Oracle infrastructure. That identifies the core model development path. Tessera's language model layer and the complete provider inventory, retention terms and training rights remain unspecified.

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

Wellstar Kennestone's CCU account describes a six week rollout and a reduction from 68 to 36 alarms per hour. The account lacks a dated measurement period, patient denominator and controlled comparison, limiting interpretation of the reported benefit.

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

Training uses deidentified protected information, with identity restored only within hospital environments. Recommendation and incident logs support review. Model retention deadlines and a detailed AI safety event response process remain unspecified.

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

HIPAA controls accompany a marketplace service agreement with data protection terms, restricted data use and incident notification duties. A readable BAA with its applicable tier and obligations for PHI subcontractors is not established.

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

The trust center identifies SOC 2 Type II and lists the report behind an access request. Annual independent auditing is asserted. The audit artifact, covered period and detailed scope remain unverified.

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.
Vendor Published

The product supports alarm configuration and hospital operations, leaving bedside changes to clinicians. Its stated scope excludes curing, mitigating, treating or preventing disease. This positioning does not establish clearance for autonomous diagnosis or treatment.

BB on AI Governance and Bias DisclosureA governance framework with named process behind it, such as certification to an artificial intelligence management standard, or material written for a customer own review committee to evaluate the product with. A framework covering the vendor whole portfolio counts when its scope reaches this product; what it cannot supply is the product specific evaluation the band above asks for. Published results within the one group where the performance of this product is most at risk also sit here: evaluation on the question this axis asks, short of the comparison across groups the band above requires. A medical device clearance or certification, and the quality system behind it, does not reach this band on its own; it is graded under regulatory status. A regulator reviewed plan governing how the model may change does reach it.
Vendor Published

Medical, nursing and ICU leaders review models before deployment. Quarterly audits address accuracy, bias and drift, with technical and clinical review. Comparative subgroup results and an independent model behavior audit remain unspecified.

BB on AI Liability and RecourseA published falsifiable commitment, or a real correction route the affected person can exercise against the vendor. A published error rate with its method and denominator grades here. A statutory right that runs to the covered entity rather than to the vendor does not reach this band on its own: every other route here asks something of the vendor, and being located in a particular jurisdiction is not conduct.
Vendor Published

The marketplace service agreement provides correction and refund remedies for material product nonconformance. These create a vendor remedy route, but do not expressly guarantee individual alarm recommendations or compensate for clinical consequences.

Integration and Deployment
BB on EHR and Interoperability DepthNamed systems with read access or one directional writing, or standards support with named deployments behind it.
Vendor Published

Wellstar's deployment combines live Philips IntelliBridge and Epic data, including medication administration and vital signs. Nurses change bedside monitor settings themselves. The named connection establishes production data intake without demonstrating bidirectional EHR writing.

CC on Deployment Model and Data ResidencyA single hosted option with location implied rather than committed.
Vendor Published

The service runs on Oracle Cloud Infrastructure following a migration from its earlier hosting arrangement. A marketplace subscription remains available. Committed processing regions, tenant isolation and cross border data handling are unspecified.

Commercial
AA on Commercial TransparencyPublished tiers with figures, a stated unit of charge, and a route to start without a sales conversation.
Vendor Published

The marketplace contract costs $7,152 per ICU bed for 12 months and includes a purchase route. This establishes the standard alarm management subscription; Tessera's early access data service has separate, unspecified commercial terms.

BB on Setting and Specialty CoverageCoverage is named with validation behind part of it.
Vendor Published

Critical care deployment at Wellstar Kennestone supports the alarm management use case. Broader positioning covers patient flow, discharge readiness and hospital operations, with less validation for those uses than for the CCU workflow.

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
$7,152 per ICU bed per year
$7,152 baseline
Annual subscription per ICU bed through AWS Marketplace. HIPAA controls claimed; readable BAA and tier unspecified. Implementation and onsite support described; separate fee unspecified. Vendor Published

The standard contract runs for 12 months. Tessera early access pricing is unspecified.