Healthcare Analytics runs outcome measurement from an approved metric definition to a published outcome rate. Its unit of work is one revision of an outcome cohort: a named, dated group of deidentified observation-level facts tied to an outcome definition, an owning organization, a responsible person and a recorded consent basis.
Outcome cohorts in one list
| Number | Name | Cohort date | Completed at | Revision | Patient count | |
|---|---|---|---|---|---|---|
| OC-58656 | October discharge cohort, Northhaven | 20 Oct | 90 | 35 | ||
| OC-38113 | September diabetes cohort, Eastgate | 11 Oct | 920 | 30 | ||
| OC-49881 | Fall screening cohort, Riverside | 27 Oct | 50 | 13 | ||
| OC-45761 | Cardiology referrals, third quarter | 19 Oct | 210 | 11 | ||
| OC-89505 | Senior outreach cohort, Westbrook | 24 Oct | 190 | 13 |
Metric Steward approves each metric definition version before results are calculated.
Every feature works on the same records. Pick one to see the screen your team works in.
Build each cohort revision from its outcome definition, owner, organization and consent basis.
Outcome cohorts
| Number | Name | Cohort date | Status | Revision | Patient count | |
|---|---|---|---|---|---|---|
| OC-51648 | October discharge cohort, Northhaven | 29 Oct | Configured | 320 | 29 | |
| OC-83754 | September diabetes cohort, Eastgate | 03 Nov | Collecting | 270 | 32 | |
| OC-91253 | Fall screening cohort, Riverside | 26 Oct | Validated | 400 | 18 | |
| OC-38903 | Cardiology referrals, third quarter | 17 Oct | Analyzed | 760 | 6 | |
| OC-26594 | Senior outreach cohort, Westbrook | 11 Oct | Published | 410 | 20 |
Load observation-level facts under a recorded consent basis and accept or reject each one.
Approval conditions
| Parent | Sequence | Description | Observed on | Patient count | Session count | |
|---|---|---|---|---|---|---|
| Cardiology referrals, third quarter | 70 | Eligible discharge with follow-up | 25 Oct | 15 | 34 | |
| Fall screening cohort, Riverside | 50 | Referral attended within window | 11 Oct | 32 | 15 | |
| September diabetes cohort, Eastgate | 10 | Screening completed after invitation | 28 Oct | 29 | 8 | |
| Senior outreach cohort, Westbrook | 60 | Emergency return after index visit | 02 Nov | 35 | 5 | |
| Cardiology referrals, third quarter | 10 | Care milestone met on schedule | 18 Oct | 27 | 37 |
Approve the numerator, denominator, grain and aggregation method before any result is calculated.
Approval waits for the metric steward
| Name | Version | Grain | Numerator expression | Denominator expression | Aggregation method | |
|---|---|---|---|---|---|---|
| Thirty-day readmission rate | Metric v1.0 | One discharge episode | Readmissions within 30 days | Eligible live discharges | Sum | |
| Post-discharge follow-up rate | Metric v1.1 | One eligible patient | Discharges with timely follow-up | All eligible discharges | Count distinct | |
| Screening completion rate | Metric v2.0 | One referral | Completed eligible screenings | Patients due for screening | Ratio of sums | |
| Median appointment wait time | Metric v2.1 | One completed visit | Attended specialist referrals | Referrals issued in period | Last as of | |
| Care plan adherence rate | Metric v3.0 | One screening invitation | Emergency returns within 72 hours | Index emergency visits | Median |
Keep one result per approved definition and period window, with suppression and invalidity reasons.
Metric results
| Metric | Source | Period start | Period end | Dimension key | Numerator | |
|---|---|---|---|---|---|---|
| Screening completion rate | Primary care visits, second quarter | 20 Oct | 25 Oct | facility:northhaven | 660 | |
| Post-discharge follow-up rate | Fall screening cohort, Riverside | 17 Oct | 25 Oct | cohort:diabetes | 240 | |
| Median appointment wait time | Postoperative follow-up, Harborview | 31 Oct | 05 Nov | age:65-plus | 770 | |
| Screening completion rate | October discharge cohort, Northhaven | 30 Oct | 08 Nov | service:cardiology | 810 | |
| Patient outreach response rate | Senior outreach cohort, Westbrook | 26 Oct | 02 Nov | period:2026-q3 | 220 |
Record independent reviewer decisions against an exact cohort revision and verify its evidence.
Action waits for the clinical reviewer
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| Cardiology referrals, third quarter | 520 | Pending | Jonas Weber | EV-2026-0418 | |
| Asthma care cohort, Oakfield | 140 | Pending | Farah Qureshi | EV-2026-0427 | |
| Senior outreach cohort, Westbrook | 300 | Pending | Leena Kapoor | EV-2026-0441 | |
| Senior outreach cohort, Westbrook | 560 | Pending | Chika Nwosu | EV-2026-0462 | |
| September diabetes cohort, Eastgate | 590 | Pending | Mateo Silva | EV-2026-0479 |
Track source freshness, field mappings and every workflow run with its numbered steps.
Source snapshots
| Name | Source system | Captured at | Coverage start | Coverage end | Record count | |
|---|---|---|---|---|---|---|
| Northhaven encounters, Oct 1-7 | Encounter registry | 27 Oct | 02 Nov | 07 Nov | 29 | |
| Eastgate referrals, Sep 1-30 | Referral management feed | 15 Oct | 22 Oct | 31 Oct | 22 | |
| Riverside screenings, third quarter | Screening camp export | 17 Oct | 22 Oct | 25 Oct | 1 | |
| Harborview discharges, October | Consent ledger | 21 Oct | 28 Oct | 02 Nov | 27 | |
| Westbrook outreach, week 40 | Appointment scheduler | 24 Oct | 01 Nov | 07 Nov | 32 |
Assign corrective work raised from published outcomes and close it with a recorded resolution.
Follow-up actions
| Title | Source | Due date | Status | Completed at | Resolution | |
|---|---|---|---|---|---|---|
| Review missing discharge dates | Asthma care cohort, Oakfield | 21 Oct | Open | Reimported corrected discharge feed | ||
| Reconcile duplicate referral events | October discharge cohort, Northhaven | 04 Nov | In progress | Excluded duplicate referral events | ||
| Confirm screening denominator | Senior outreach cohort, Westbrook | 15 Oct | Completed | 17 Oct | Updated eligibility window | |
| Audit late source feed | Postoperative follow-up, Harborview | 18 Oct | Open | Confirmed suppression threshold | ||
| Validate consent exclusions | Asthma care cohort, Oakfield | 02 Nov | In progress | Mapped missing consent states |
Cohort to published outcome rate ships ready to use. 2 steps need a named approval before the work moves on: Define metrics (Metric Steward) and Independent review (Clinical Reviewer).
Set the numerator, denominator, grain and aggregation for each measure and approve the version.
Build a cohort revision from a fresh source snapshot and its outcome definition.
Accept or reject each deidentified fact and attach the supporting evidence.
A reviewer who does not own the cohort approves the exact revision before publication.
Publish the approved results and confirm they were written before the run succeeds.
Assign corrective actions from published outcomes and close them with a resolution.
Open any outcome cohort to see its deidentified outcome facts, the roles that work on it, its process stages and its approvals on one page.
Cohort date, Revision, Patient count and Cohort exposure.
Each line is linked to this outcome cohort.
Analytics Manager, Outcomes Analyst and Clinical Reviewer, each with their own permissions.
Construct cohort, with the role that acts.
Define metrics and Independent review, with who decides.
Eastgate Community Health
| Parent | Sequence | Description |
|---|---|---|
| Cardiology referrals, third quarter | 70 | Eligible discharge with follow-up |
| Fall screening cohort, Riverside | 50 | Referral attended within window |
| September diabetes cohort, Eastgate | 10 | Screening completed after invitation |
Signed in as Metric Steward
| Decision | Approver | |
|---|---|---|
| Define metricsSet the numerator, denominator, grain and aggregation for each measure and approve the version. | Metric Steward | |
| Independent reviewA reviewer who does not own the cohort approves the exact revision before publication. | Clinical Reviewer | |
| Approve review decisions, evidence documents | Clinical Reviewer | |
| Approve metric definitions | Metric Steward |
Everyone opens Healthcare Analytics to the work that is theirs. Pick a role to see what it starts with.
Assigns cohort owners, starts publication of reviewed cohort revisions and oversees follow-up work.
This is the first screen this role sees.
Metric definitions · Analytics Manager
| Name | Version | Grain | Numerator expression | Denominator expression | Aggregation method | |
|---|---|---|---|---|---|---|
| Thirty-day readmission rate | Metric v1.0 | One discharge episode | Readmissions within 30 days | Eligible live discharges | Sum | |
| Post-discharge follow-up rate | Metric v1.1 | One eligible patient | Discharges with timely follow-up | All eligible discharges | Count distinct | |
| Screening completion rate | Metric v2.0 | One referral | Completed eligible screenings | Patients due for screening | Ratio of sums | |
| Median appointment wait time | Metric v2.1 | One completed visit | Attended specialist referrals | Referrals issued in period | Last as of | |
| Care plan adherence rate | Metric v3.0 | One screening invitation | Emergency returns within 72 hours | Index emergency visits | Median |
Builds cohort revisions, loads deidentified facts and prepares them for independent review.
This is the first screen this role sees.
Outcome cohorts · Outcomes Analyst
Records independent review decisions against an exact cohort revision and verifies supporting evidence.
This is the first screen this role sees.
Outcome cohorts · Clinical Reviewer
Maintains outcome and metric definitions and approves each definition version before results are calculated.
This is the first screen this role sees.
Metric definitions · Metric Steward
| Name | Version | Grain | Numerator expression | Denominator expression | Aggregation method | |
|---|---|---|---|---|---|---|
| Thirty-day readmission rate | Metric v1.0 | One discharge episode | Readmissions within 30 days | Eligible live discharges | Sum | |
| Post-discharge follow-up rate | Metric v1.1 | One eligible patient | Discharges with timely follow-up | All eligible discharges | Count distinct | |
| Screening completion rate | Metric v2.0 | One referral | Completed eligible screenings | Patients due for screening | Ratio of sums | |
| Median appointment wait time | Metric v2.1 | One completed visit | Attended specialist referrals | Referrals issued in period | Last as of | |
| Care plan adherence rate | Metric v3.0 | One screening invitation | Emergency returns within 72 hours | Index emergency visits | Median |
Captures source snapshots, maintains field mappings and resolves failed or unreconciled operation runs.
This is the first screen this role sees.
Operation runs · Data Engineer
Works follow-up actions raised from published outcomes and records how each one was resolved.
This is the first screen this role sees.
Follow-up actions · Quality Improvement Lead
Maintains organizations, people, user access and configuration without taking part in review decisions.
Review outcome rates, the readmission trend, review decisions, run reliability and overdue follow-up work.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Configured | 41 | ||
| Collecting | 26 | 63% | |
| Validated | 19 | 73% | |
| Analyzed | 14 | 74% |
Sample totals per stage
What value did each approved metric produce for each cohort and window, from which numerator and denominator?
How has the readmission measure moved across consecutive windows?
How do results differ across the dimensions they were split by?
How many cohorts were created each month, and at what status are they now?
Group cohorts by organization, then by status, to show where work is waiting.
How often are revisions approved, returned or rejected, and by whom?
Which results were withheld, and for what reason?
Which operations fail or need reconciliation most often?
Show each snapshot's source system, coverage window, record count and freshness status.
See how Healthcare Analytics fits your kind of team.
Measure readmissions and other outcomes across facilities with reviewed definitions and traceable rates.
Track outcomes for defined patient cohorts with recorded consent bases and period-by-period results.
Run registry measures with versioned definitions, independent review and an auditable run history.
Each stage of cohort to published outcome rate names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Prepare and review cohort to published outcome rate with Proto.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 17 tablesStart with one team and one process, then add the rest once the basics are running.
The app runs outcome measurement from an approved metric definition to a published outcome rate and its follow-up actions. Identifiable patient data, deidentification, clinical source systems and external reporting destinations stay outside it and are connections to set up. The organization decides which outcomes it measures and what each count field records; Proto prepares configuration and information for review.
Create the roles, match People to signed-in users by email and scope each person to their organizations before any review decision is recorded.
Record outcome and metric definitions with their versions, the source mappings they depend on, and the snapshot each cohort will draw on. Agree what PatientCount, SessionCount, ConversionCount, TargetCompletions and CohortExposure hold for each measure.
Run cohort construction, calculation and reconciliation, outcome-rate publication and correction on a branch, and rehearse each before release.
Pilot one outcome measure for one organization across a few monthly windows. Build, review and publish each cohort, and reconcile the published rates with the figures the team already reports.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Healthcare Analytics for your business. Pilot one outcome measure for one organization across a few monthly windows. Build, review and publish each cohort, and reconcile the published rates with the figures your team already reports before adding measures or organizations.
It is an outcome measurement system. It keeps the cohorts, deidentified facts, metric definitions, results, review decisions and follow-up actions behind each published rate. The Healthcare Analytics Overview page shows KPI health, the readmission-rate trend and the overdue follow-up queue, and you can connect a business intelligence tool for wider reporting.
It is designed for deidentified facts. Deidentification happens in your own systems before data is loaded, and each fact records its source reference and consent basis. Agree with your privacy officer what may be loaded before the pilot.
Yes. Define a readmission metric with its numerator, denominator, grain and aggregation method, and agree which cohort count fields hold index admissions and readmissions. The overview page plots the observed readmission-rate trend from the calculated results.
Two people decide. The Metric Steward approves the metric definition version, and a Clinical Reviewer who does not own the cohort approves the exact cohort revision. Only an approved revision can be published.
The correction workflow keeps the published revision, writes a successor revision and records the transition in state history. The successor needs a new review decision before it is published.
A result can be stored as suppressed or invalid with a reason. Agree your suppression threshold during setup. Calculation includes a zero-denominator guard; rehearse that a zero-denominator window is stored as suppressed before go-live.
Yes. Each facility or program is an organization with its own outcome definitions, cohorts and people. Scope access by organization during setup.
The roles are Analytics Manager, Outcomes Analyst, Clinical Reviewer, Metric Steward, Data Engineer, Quality Improvement Lead and Admin. They are set up and tested during implementation.
Ordinary manual use has no per-user charge under the platform policy. Imports, integrations, agent execution and other machine work consume prepaid credits; implementation is scoped separately. The pricing page lists the current rates.
Start free, then use Proto to change fields, steps and approvals before your team goes live.