Infrastructure for Mortality Risk Prediction
ML model that predicts risk of in-hospital mortality or 30/90-day post-discharge mortality, supporting goals-of-care discussions and palliative care referrals.
Analysis based on CMC Framework: 730 capabilities, 560+ vendors, 7 industries.
Key Finding
Mortality Risk Prediction requires CMC Level 3 Formality for successful deployment. The typical quality & patient safety organization in Healthcare faces gaps in 2 of 6 infrastructure dimensions.
Structural Coherence Requirements
The structural coherence levels needed to deploy this capability.
Requirements are analytical estimates based on infrastructure analysis. Actual needs may vary by vendor and implementation.
Why These Levels
The reasoning behind each dimension requirement.
Mortality risk prediction requires explicit, findable documentation of trigger thresholds for palliative care referrals, goals-of-care conversation protocols, and code status documentation requirements. TJC and CMS conditions of participation formalize advance directive policies. The ML model needs clearly documented criteria for when a mortality risk score triggers a palliative care consult vs. a physician notification vs. a care plan update—these clinical decision rules must be findable and current, not residing in individual physicians' judgment.
Mortality risk prediction requires systematic capture of frailty assessments, functional status scores, advance directive status, code status, prior utilization patterns, and vital signs across encounters via structured EHR templates. Regulatory requirements for advance directive documentation and structured discharge summaries enforce baseline systematic capture. The model needs longitudinal patient data captured consistently across inpatient, outpatient, and ED encounters to compute 30/90-day post-discharge mortality risk.
Mortality prediction requires consistent schema across all clinical records: ICD-10 diagnosis codes, CCI comorbidity index components, functional status assessments (Katz, Barthel), vital sign trends, and lab values must share uniform field definitions. The model computes survival probability from structured feature vectors assembled from these consistently defined data elements. Without consistent schema, comorbidity burden calculations produce incomparable risk scores across patient populations.
Mortality risk prediction requires API access to EHR clinical data, prior utilization records, advance directive repositories, and palliative care consultation workflows. The model must surface risk scores in the attending physician's EHR workflow and trigger palliative care team worklists—not in a standalone analytics portal. API access to EHR and care management systems enables the model's output to reach clinicians at point of care during rounds.
Mortality risk model maintenance follows a periodic review cadence aligned with annual CMS reporting requirements and major clinical guideline updates. The model's risk factors—diagnosis weights, frailty indicators, utilization patterns—evolve slowly enough that scheduled annual or semi-annual recalibration is operationally acceptable for this capability. Unlike sepsis or ADE detection, mortality prediction supports longer-horizon care planning rather than immediate clinical response, reducing the urgency of real-time model currency.
Mortality risk prediction is primarily bounded to EHR-resident clinical data: diagnoses, labs, vitals, functional status, and advance directives. Point-to-point integrations between the EHR and palliative care consultation system, plus a link to the advance directive registry, are sufficient for the core workflow. Population-level mortality trending requires only EHR data extraction. Full API-based multi-system integration isn't required because the capability doesn't depend on real-time cross-system context assembly.
What Must Be In Place
Concrete structural preconditions — what must exist before this capability operates reliably.
Primary Structural Lever
How explicitly business rules and processes are documented
The structural lever that most constrains deployment of this capability.
How explicitly business rules and processes are documented
- Formal clinical criteria defining mortality risk stratification thresholds for goals-of-care trigger points and palliative care referral indications, codified as operational clinical standards
Whether operational knowledge is systematically recorded
- Systematic capture of vital status outcomes, discharge disposition records, 30-day and 90-day post-discharge mortality events linked back to index encounter records
How data is organized into queryable, relational formats
- Validated schema linking clinical features — diagnosis codes, severity scores, functional status, and advance directive status — to mortality outcome labels in a consistent analytical structure
Whether systems expose data through programmatic interfaces
- Self-service query access to mortality prediction scores for care teams with role-based controls ensuring palliative care specialists and attending physicians can retrieve risk context at point of care
How frequently and reliably information is kept current
- Periodic validation of model outputs against mortality outcome registries with structured review of calibration drift by clinical service line and patient population subgroup
Common Misdiagnosis
Clinical teams deploy mortality prediction models without establishing formal criteria for which risk thresholds should trigger goals-of-care conversations, resulting in alert fatigue when scores surface without defined clinical response pathways.
Recommended Sequence
Start with formalising clinical response thresholds and referral criteria before systematic outcome capture, since mortality prediction without defined action thresholds produces scores that clinicians cannot operationalise into care decisions.
Gap from Quality & Patient Safety Capacity Profile
How the typical quality & patient safety function compares to what this capability requires.
More in Quality & Patient Safety
Frequently Asked Questions
What infrastructure does Mortality Risk Prediction need?
Mortality Risk Prediction requires the following CMC levels: Formality L3, Capture L3, Structure L3, Accessibility L3, Maintenance L2, Integration L2. These represent minimum organizational infrastructure for successful deployment.
Which industries are ready for Mortality Risk Prediction?
Based on CMC analysis, the typical Healthcare quality & patient safety organization is not structurally blocked from deploying Mortality Risk Prediction. 2 dimensions require work.
Ready to Deploy Mortality Risk Prediction?
Check what your infrastructure can support. Add to your path and build your roadmap.