Know what a change will do before you roll it out.

Omelvian forecasts every department's weekly numbers, tests changes against those forecasts, and counts the money a change actually saved, so the next decision starts from evidence.

Talk to us Sign in

A forecast, a test, and what the change saved An illustration. A department's weekly overtime cost runs along for thirty weeks, then a forecast continues it with a shaded 80% range. Three weeks in, a test begins: where the change is made, cost falls below the forecast, and the gap between the two lines is what the change saved. Today Overtime cost, each week Forecast 80% range With the change The gap is the saving
An illustration with made-up numbers, drawn the way Omelvian draws its own charts.

One loop, turned every week

Each turn leaves the hospital with better forecasts and a clearer record of which changes paid off.

  1. Predict

    Each department's weekly visits, claims, hours and costs are forecast for the next 13 weeks, with a range that has been checked against what really happened. If no model beats a simple one, Omelvian uses the simple one and says so.

  2. Test

    When a forecast shows a problem coming, or the data points to a better way of working, plan a test: a staggered rollout across departments, sized from your own history, with the aim written down before it starts.

  3. Compare

    As the weeks arrive, each test is read against what was expected without the change. It finishes as met the aim, fell short, no clear change, or stopped early because something got worse.

  4. Count the savings

    Changes that worked are valued in dollars a year, cautiously, with the assumptions shown. Every forecast is also kept as it was shown and scored later, so you can see the track record.

From everyday events to evidence

Built for the size of a real hospital: a handful of departments or teams, not millions of website visitors.

Inside the hospital

  1. Things happen

    Visits, claims, shifts and overtime, and clicks in the EHR: alerts fired, inbox messages, orders.

  2. Counted into totals

    Your team adds them up per department or team, by day or by week. Only the totals are sent, and Omelvian hides any group too small to share safely.

Only totals cross this line

In Omelvian

  1. Forecast

    Each team's next 13 weeks, with a checked range: what to expect if nothing changes.

  2. Test

    The change starts in some teams first. The teams still waiting give the comparison.

  3. Evidence

    What the change did, in plain words and dollars, kept and scored so the next decision is better.

Use cases

A few of the questions Omelvian is built to answer.

Omelvian is built for hospitals first. The same method could apply wherever real-world events are counted, such as hotels and resorts. Tell us about yours.

Who it's for

Hospital finance leaders
Forecasts of collections, denials, labour hours and costs by department, totals that add up to the hospital, and savings counted only from tested changes.
Operations and clinical informatics
Early warning when access, cancellations or inbox load drift, and a way to A/B test EHR and workflow changes, where the hospital controls who gets the change, before rolling them out everywhere.
Technology companies and hospital leaders running proofs of concept
Independent measurement of whether a new product made a difference: a pre-registered test with a comparison group, designed to be read from the hospital's own numbers rather than the vendor's.
Investors
A company built on evidence: every number comes from tested code, every forecast is scored against what happened, and the record is kept for the hospital to check.

How your data is handled

Today the app runs only on made-up data from generated test hospitals, so you can try every feature without sharing anything. Accounts for a hospital's own totals come after legal and security review.

Talk to us

Tell us a little about your organisation and what you would like to measure, and we will get back to you.

Please do not include information about patients or individual staff. The form is run by Tally, which passes your message to us by email. See the privacy note.