These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Healthcare Analytics
- Features
- Metric results
Metric results
Keep one result per approved definition and period window, with suppression and invalidity reasons.
OverviewMetric result windows×
Healthcare Analytics · Metric results
New
Metric result windows
Metric results
| Metric | Source | Period start | Period end | Dimension key | Numerator | |
|---|---|---|---|---|---|---|
| MD-2058 | OC-87385 | 12 Oct | 17 Oct | DK-764 | 660 | |
| MD-9577 | OC-36463 | 09 Oct | 17 Oct | DK-357 | 240 | |
| MD-5535 | OC-56873 | 23 Oct | 28 Oct | DK-872 | 770 | |
| MD-2968 | OC-64901 | 22 Oct | 31 Oct | DK-562 | 810 | |
| MD-9272 | OC-58296 | 18 Oct | 25 Oct | DK-403 | 220 |
6 of 6 records
DK-764Metric results · MR-51731
CalculatedMetricMD-2058
SourceOC-87385
Period start12 Oct
Period end17 Oct
Numerator660
What you can do
Store each result once, with its working
A metric result is the calculated value for one approved metric definition, one cohort and one period window. It keeps the numerator, the denominator, the value, the dimension key it was split by and the number of source rows behind it. It also points at the operation run that produced it. When a value looks wrong, the team can open the run, see the steps and check the inputs without recalculating from scratch.
How the work is organized
Observations are recorded first. Each metric observation carries the metric name, the period start and end, the numerator, denominator, unit and value, and it points at both the cohort and the source snapshot it came from. Results are then persisted once per approved definition and window with a status of Calculated, Suppressed or Invalid. A suppressed or invalid result keeps the reason, for example a denominator of zero or a cell too small to report.
- No value from a zero denominator. The calculation must suppress the result with a reason instead of writing a rate.
- The original result is kept. A recalculation adds a new result tied to its own run and leaves the earlier one in place.
- Calculation under the analyst’s control. The Outcomes Analyst runs calculation and reconciliation and can see each stored result with its reason.
The Healthcare Analytics Overview page reads these results to show KPI health, reviewed results by unit and the observed readmission-rate trend.
What to agree during setup
Agree the period windows you report, such as calendar month or rolling quarter, and how a window is named in the dimension key. Agree the minimum denominator or cell size below which a result is suppressed, and the reason text to record. Decide whether the calculation workflow is activated in the pilot or results are entered manually first. Agree who may mark a result invalid and what evidence they attach.
Check the handoff on an actual case
Calculate a monthly readmission rate for a validated cohort. Confirm that the result shows the approved definition version, the numerator and denominator, the source row count and the run. Then calculate a window where the denominator is zero. The result should be stored as Suppressed with a reason. Confirm that the overview trend does not plot it as a zero rate.
Run the same calculation again with the same operation key. The existing run should be returned and no second result written. Ask the Metric Steward to confirm, from the “Suppressed and invalid results” view, that each suppression has a reason a reviewer could accept.
What your team sees
- Metric result windows — every result with its metric, cohort, period start and end, dimension, numerator, denominator, value and status.
- Suppressed and invalid results — results that were not reported, with the recorded reason and the run that produced them.
- Published outcome cohorts — cohorts whose results have been published, with revision and exposure.
Follow the work through
- Cohort construction to validation: Build a cohort revision, load its facts and accept or reject each one.
- Run reconciliation and correction: Resolve failed runs and correct a published revision without losing the original.
Review the implementation plan and the data model before preparing your import files.
What it keeps track of
Data model- Metric results
- Calculated metric results persisted once per approved definition and window.
- Metric observations
- Observation-level metric readings tied to a snapshot and source.
- Metric definitions
- Approved metric definitions with grain, expressions and aggregation method.
- Operation runs
- Workflow execution runs with frozen revision, input hash and result identity.
Who uses it
Permissions- Outcomes Analyst
- , Metric Steward, Analytics Manager, Quality Improvement Lead.
- The Outcomes Analyst records observations and results.
- The Metric Steward checks suppressions against the definition.
- The Analytics Manager and Quality Improvement Lead read published results.
Set up Healthcare Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.