Questions, answered

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.