Utilization and care management applications designed around the scarcest resource in the operation, which is qualified clinical reviewer time, and most of it currently goes to gathering rather than deciding.
A nurse reviewer opens a case and then opens five other things: the criteria, the clinical record, the prior authorization history, the claim, the member coverage. None of it arrives together. The clinical judgement takes a few minutes. Everything around it takes considerably longer, and that ratio is the single largest determinant of how much review capacity a plan has and how long a determination takes.
Adding reviewers is the expensive answer. Giving the ones you have their evidence in one place is the cheap one
Utilization and care management platforms often technically support the process while actively obstructing the work: repeated entry, fragmented evidence, mandatory fields nobody uses and queues that do not reflect urgency.
Evidence Arrives in Pieces
Criteria, clinical records, authorization history, claims and coverage all live somewhere else. The reviewer becomes the integration layer.
UM and CM Do Not See Each Other
An authorization may sit in one system while an active care plan sits in another, leaving both teams without the full member context.
Documentation Burden Is Often Configured
Fields made mandatory years ago may be collected on every case even when nobody uses them today.
The Application Shapes the Decision
Criteria order, defaults, click depth and what is visible all influence judgement under time pressure.
Work Is Queued Rather Than Prioritized
Urgency, deadline and completeness may not determine which case gets opened next.
Incomplete Cases Reach Clinical Queues
A reviewer should not spend expensive clinical time discovering that the case is missing information.
Count the systems a reviewer opens to complete one case.
Measure systems opened, screens visited, identifiers re-entered and how much elapsed time was actual clinical judgement. That single observation often converts directly into a capacity discussion.
Requirements tell you the process people describe. Observation shows the process they actually perform—including workarounds, second screens, personal spreadsheets and steps everyone skips.
Step 1
Observe real cases.
Measure systems opened, re-entry, retrieval time and the clinical proportion of elapsed time.
Step 2
Separate clinical work from administrative work.
Automation belongs around judgement, not inside it.
Step 3
Assemble evidence before clinical review.
The first action should be assessment, not search.
Step 4
Audit documentation requirements.
Every mandatory field needs a current consumer—or it should be removed.
Step 5
Connect UM and CM around the member.
Make authorizations and care plans visible across both teams.
Step 6
Route by need, not queue.
Use case type, urgency, completeness, specialty and deadline.
Step 7
Design screens around the decision.
Present criteria, evidence and history together.
Step 8
Preserve point-in-time state.
An appeal should see what was known and decided at the time.
Step 9
Keep the decision with the clinician.
Automate gathering, preparing, routing and administering.
Step 10
Establish configuration ownership.
Review criteria versions, templates, routing and required fields on a cadence.
Ask which mandatory fields anybody actually uses.
Trace each required field to a report, regulatory requirement, downstream process or decision. The unused ones are a permanent tax on every case.
Assemble
Case Context Assembly
Clinical record, authorization history, claims, coverage, prior determinations and care-management activity retrieved and presented together.
Documentation Retrieval
Obtain clinical evidence from the provider or record wherever possible instead of asking reviewers to request and wait.
Intake and Classification
Receive requests across channels, classify what they need and route them to the correct queue and skill.
Completeness Assessment
Check what the case requires against what is present before clinical review begins.
Support the Decision
Criteria Presentation
Show the applicable criteria beside the evidence, with version and effective date visible.
Reviewer Workspace Design
Organize screens around the actual decision rather than around the underlying system structure.
Clinical Documentation Support
Capture rationale once and reuse it for the determination record, notification and appeal file.
Escalation and Physician Review
Carry all information already gathered into the second review without forcing duplicate work.
Coordinate and Prove
UM and CM Connection
Shared member context across authorization and care-management workflows.
Care Planning and Coordination
Assessments, care plans, tasks, outreach and outcomes connected to utilization events that should trigger them.
Point-in-Time Record
Preserve what was known, considered and decided, and by whom, at the moment of determination.
Configuration Governance
Own and review criteria versions, templates, routing, required fields and timeliness rules.
What CaliberFocus does, and does not do?
Clinical determinations stay with qualified clinicians at every confidence level. We automate assembling, preparing, routing and administering—never deciding.
Prior authorization, urgent review, concurrent review, retrospective review, appeals, case management and transitions of care may share a platform, but they should not be forced through one workflow.
| Workflow | What Is Happening | What the Application Must Do Well |
|---|---|---|
| Prior Authorization | A service is requested before delivery | Assemble evidence fast; elapsed time is the outcome |
| Urgent / Expedited Review | A determination is needed within hours | Make the clock visible and route immediately |
| Concurrent Review | A member is admitted and care is ongoing | Real-time clinical status and discharge-planning visibility |
| Retrospective Review | Care already delivered is being assessed | Complete record reconstruction |
| Appeals | A determination is being challenged | The original point-in-time record and rationale |
| Case Management | A complex member is actively managed | Longitudinal member view and care-plan continuity |
| Transitions of Care | A member is moving between settings | Timely notification from the utilization side |
The Same Member, Two Systems, Neither Aware of the Other
A member in active case management is admitted. The utilization team processes the concurrent review while the care manager may learn days later. Connecting those teams is often an integration and configuration problem rather than a platform-replacement problem.
Decomposing a review by activity shows that clinical judgement is only one part of the elapsed time—and usually not the largest part.
| Activity | What Happens | Does It Need a Clinician? |
|---|---|---|
| Locating the Case | Finding and opening the right case in the queue | No — this is queue and routing design |
| Gathering Evidence | Opening other systems for records, history, coverage and claims | No — often the largest block of time |
| Establishing Completeness | Working out whether required information is present | Rarely — requirements are knowable in advance |
| Locating Criteria | Finding the applicable criteria and version | No — it should be presented, not retrieved |
| Applying Judgement | Assessing the case against criteria | Yes — this is the clinical work |
| Documenting Rationale | Recording the basis for the determination | Partly — capture once, do not re-enter |
| Issuing and Notifying | Producing the letter and communicating outcome | No — administrative and generatable |
| Updating Downstream | Recording the outcome where other systems need it | No — manual propagation is often skipped |
Waiting for documentation, clinical review, physician review, provider response and internal information are five different states with five different owners. The first operational question is whether the case is waiting for information or waiting for a decision.
Automate Everything Except the Judgement
Seven of the eight activities above do not require a clinical licence. The clinical assessment does.
The Clock Belongs in the Interface
Show time remaining on every case and use it to drive work order before a breach occurs.
Capture Rationale Once
The decision, letter and appeal file should draw from the same record.
Never Overwrite Decision State
An appeal examines what was known at the time, not the current state.
Separate Administrative and Clinical Waiting
They have different causes, owners and remedies.
Design the Exception Path for Clinicians Too
Cases that fall outside the workflow should not disappear into email or spreadsheets.
Treat Repeated Exceptions as Process Defects
Recurring missing information is a submission or requirement problem, not permanent workload.
Feed Outcomes Back to Care Management
Authorizations, denials and admissions are signals the care team needs automatically.
The interface is making clinical decisions whether you designed it to or not.
Criteria order, defaults, click depth and evidence visibility all shape reviewer behavior under pressure. Interface design is therefore part of clinical quality.
Most of what a reviewer needs already exists somewhere in the plan or can be obtained from the provider. The problem is assembly, and today the reviewer often performs it manually.
Core Administration
Coverage, benefits, prior authorizations and claims history presented without opening the adjudication system.
Clinical Documentation Sources
Retrieve provider records and exchange data where possible instead of repeatedly requesting them.
Provider Data
Identity, participation and contact information so requests and follow-up do not stall.
Pharmacy
Medication history can add clinical signal that may not be available elsewhere as quickly.
Care Management Platform
Bring active care plans, assessments and engagement into the utilization context.
Criteria and Policy Content
Versioned, effective-dated and shown in the workspace rather than retrieved separately.
Integration principles
Retrieve rather than request. Read state, not summaries. Write outcomes everywhere they are needed. Preserve provenance. Make failed retrievals visible as owned work.
Utilization decisions are regulated, timed, appealable and examinable. The application must support consistency, traceability and qualified clinical accountability.
Clinical Governance
Appropriately licensed reviewers, effective-dated criteria, determination-consistency monitoring, defined physician-review escalation and separate monitoring of clinical workflow health.
Compliance and Timeliness
Case-specific turnaround requirements, proactive escalation, system-produced notifications, versioned appeal content and manual fallbacks for timeline risk.
Record Integrity
Preserve the point-in-time record, full audit history and effective-dated configuration changes.
Security and Access
Scope clinical access by role and assignment, apply tighter rules to sensitive conditions, and audit delegated-entity access.
Look at determination variation between reviewers before you conclude it is clinical.
Different evidence, criteria versions, time pressure and screens can produce different decisions from equally competent clinicians. That may be an application problem wearing clinical clothing.
Case volume and turnaround do not show how much qualified clinical capacity is being consumed by work that does not require a clinician.
| Category | What We Measure | Why It Matters |
|---|---|---|
| Clinical Time Ratio | Reviewer time spent on judgement versus retrieval, entry and navigation | The capacity measure that funds the work. |
| Systems per Case | Applications opened and identifiers re-entered per review | A simple proxy for assembly failure. |
| Elapsed Time by Stage | Time in intake, awaiting documentation, queue and review | Separates software problems from capacity problems. |
| Documentation Burden | Mandatory fields without current use and fields removed | A permanent tax on every case. |
| UM and CM Connection | Care-managed members whose utilization events reached the care team and how quickly | Measures whether the member context is actually connected. |
| Record Integrity | Ability to produce the point-in-time record for appealed cases | What matters when the record is requested. |
Recovered clinical capacity does not have to mean reducing clinical staffing.
It can mean absorbing growth, shortening turnaround, handling complex cases properly and reducing the pressure that produces errors. The documentation audit may also identify mandatory fields that nobody can justify.
We will observe reviewers and care managers working real cases, decompose where the time goes, audit the documentation requirements against current use, and show you how much clinical capacity is recoverable from the application before any hiring is considered. That analysis usually changes the conversation from headcount to configuration.
Bring us a specialty or clinical setting where clinicians are spending too much time creating notes. We will assess where ambient documentation fits, what must remain clinician controlled, how it should integrate with your EHR, and how to measure whether it is actually reducing burden.
One conversation with people who have run these deployments, and a written readiness view you can use with or without us.
- AI Agents and Workflow Automation
- Voice and Conversational AI
- Document AI and Intelligent Processing
- Generative AI and Enterprise Copilots
- AI Strategy and Governance
- HCC and Risk Adjustment Analytics
Security & Compliance
