SUNDAY · 07 JUNE 2026

Product methodology

Anesthesia Outcomes Shadow Registry

Source contract, normalization path, entity-graph join, refresh posture, and publication limits for this Branmoor product.

Status

In service. This product has a functional preview or paid engagement surface in the current site. The full licensed product may still include private exports, alerts, APIs, or buyer-specific diligence that are not exposed publicly.

Distribution Scope

Nationwide; TN ASC layer; Nashville ASC/anesthesia watch

Product Question

Aggregates anesthesia outcome and malpractice/procedure-risk signals.

Primary Sources

  • CMS Medicare and Medicaid claims — Anesthesia procedure volume, complications, comorbidity
  • NPDB malpractice query data (provider self-query where disclosed) — Claims and licensure actions
  • State malpractice disclosure (where public) — Provider-level claims history
  • Hospital quality reports and accreditation databases — Facility safety and surgical outcome data
  • FDA MAUDE — Anesthesia equipment-related adverse events

Entity-Graph Join

ASC/hospital `ccn`, clinician `npi`, device IDs, procedure codes.

Publication Rule

Branmoor does not treat raw public records as the product. A surface is publishable only when the source record is dated, normalized, source-linked, and joined to the relevant Branmoor entity identifiers with enough confidence to state the limits of the result.

Current Methodology Note

v1 surfaces every Medicare-certified Ambulatory Surgical Center with the CMS-published anesthesia-adjacent quality measures: patient burns, falls, wrong-site events, normothermia outcomes, and risk-standardized post-procedure hospital-visit rates. The paid Shadow Registry layer attributes the anesthesia-specific component using NPDB cross-reference, state malpractice disclosure (where public), CMS Medicare claims, and FDA MAUDE for anesthesia equipment.

Limits

Coverage follows the underlying source. Missing state portals, gated APIs, PDF-only filings, suppressed fields, lagged agency refreshes, and entity-name ambiguity can all limit product completeness. Pending products are not marketed as live until those limits are documented on the product surface.

‹ Anesthesia Outcomes Shadow Registry  ·  All products