Enterprise document vault
The record of what happened, kept safe and found in seconds.
Claims, contracts, correspondence, compliance files. In a regulated operation the document is the proof, and losing track of it shows up as a denied claim, a failed audit, or an afternoon spent hunting.
The vault brings those records in and files each one by line of business and document type. It holds every record for exactly as long as the rules require, then hands it back in seconds with a record of who looked.
A sketch on made-up records. The real system is shown in a scheduled demo.
What it does
- Capture and classificationPaper, scans and digital files come in through one door. Each lands in the right folder, under the right document type, visible only to the people cleared to see it.
- Retention and legal holdEvery record carries its retention rule. A hold freezes what must not move; expiry clears what must not linger. Both leave a trail.
- Audit-ready accessSearch by what you know, open the record, and show who viewed, changed or exported it, and when.
Where it fits
- Moving off an aging repositoryYears of scanned records come across and land in the right folders. Anything that can't be matched waits in its own folder for a person to sort, inside the same line of business.
- The audit requestAn auditor asks who opened a file and when. You open the record and show them.
- The legal holdLegal says a set of records can't be touched. A hold goes on, with who placed it on the record, and stays until it's released.
- Work that travels with the recordQueues, forms and routing sit on top of the vault, so a work item and its document move together.
Call center forecasting
How many calls, how many people, every 15 minutes.
Staff a call center to an average and you're wrong all day: too many people in the lull, not enough in the rush.
It forecasts calls for all 96 intervals of the day and converts them to the staff you need after handle time, breaks and shrinkage. Then it lines that up against who's on the schedule, so you see the gaps before the phones do.
A sketch on made-up numbers, with real Erlang math. The real system is shown in a scheduled demo.
What it does
- Forecast by the intervalEvery 15-minute interval gets its own call forecast, built from your own history.
- Schedule against the needRequired staff against scheduled staff, interval by interval, with lunches and breaks counted.
- Ask what ifMove volume, handle time or shrinkage and see what it does to staffing before you commit.
Where it fits
- The storm dayOne bad day can poison next month's forecast. The detector spots it, so it gets handled as what it was.
- Service level before the day startsSee the service level the schedule will buy you, using the Erlang math call centers already trust.
- Budget seasonAsk what 20 percent more calls would take in people before anyone signs a budget.
Eligibility screening
Ask the patient once. The state's forms fill themselves.
A patient who may qualify for coverage gets the same questions more than once, then a stack of state forms. Every gap in that paperwork can cost the patient the coverage and the hospital the payment.
The screening starts from what the hospital already has, the ID and the face sheet, and asks the rest. It checks eligibility and carries the answers onto the state's forms, ready to print.
A sketch with a made-up patient. The real system is shown in a scheduled demo.
Start from what the hospital already has.
How many people live in the home?
Is anyone in the home working?
Is the patient on Medicare?
What it does
- Start from what you haveThe ID and the face sheet fill in what they can, so nobody retypes a name.
- One set of answersThe same answers carry onto the state's forms, ready to print.
- The right rep for the accountEach account goes to a rep by hospital, then by the patient's last name.
Where it fits
- Several hospitals, one screeningThe screening stays the same at every hospital. The face sheet and the rep split get set for each one.
- Patients on MedicareThey take a different state form. The screening fills that one too.
- Reading the payer's answerThe payer's electronic response comes back as plain words a rep can act on.
Tell us about the work you're responsible for.
One email starts the conversation. We read every one.