Skip to main content
Once you’re set up, the main question is which workflow answers your question. This page is a quick decision guide.

​
The common starting point

Almost every task begins the same way: search for the procedure, condition, or DRG you care about. The Entity Resolver turns that free-text term into the standardized ID the other workflows need. You rarely have those IDs up front, so resolving first is the prerequisite step.

​
Choosing a workflow

Your questionUse
”What does a typical case for this procedure look like?”Dashboard
”How have revenue, cost, margin, or outcomes trended over a period?”Analytics
”What is a future/hypothetical case likely to cost, earn, or take?”Predictions
”How would a price or discount change affect revenue?”Simulation
Dashboard vs. Analytics: the Dashboard answers “what is the shape of this one item right now?” with a quick distribution. Analytics answers “how does a metric behave across a date range, broken down by surgeon, payor, provider, or client?”

​
A typical user journey

1

Resolve

Search for and select your procedure / condition / DRG.
2

Understand the shape

Open the Dashboard to see the high-level distribution.
3

Dig into the numbers

Use Analytics to break a metric down over time and by dimension.
4

Look forward

Use Predictions to estimate a metric for a hypothetical case profile.
5

Test a change

Use Simulation to model the revenue impact of a pricing or discount change.

​
Tips for interpreting outputs

  • Mind the metric vocabulary. The same idea can be named differently in different workflows — for example, billed revenue is called revenue in Analytics and the Dashboard, but price in Predictions. Each workflow page lists its exact metrics.
  • Hospital-only metrics (hospital revenue, profit, margin) exclude certain bill types and professional fees and do not apply to insurance/payor organizations.
  • Predictions are estimates, presented with confidence and prediction-interval context — read them as ranges, not single guaranteed numbers.
  • Everything is scoped to your organization. You are never seeing another organization’s data.

Browse the workflows

Start with the Entity Resolver, the prerequisite for the rest.