[ REVENUE CYCLE ]LIVE
Hub for Hospital Claims Denials Management
Utilisation review, written from the chart. Hub highlights the clinical evidence that bears on level of care, applies the organisation's criteria and the payer's specific requirements, and drafts the review note — which the case manager verifies before it goes to the insurer.
Chart · Encounter A-20481 · 46 pages
Extracted · source-linked
| Diagnosis | Sepsis, suspected UTI source | p.3 |
| Lactate | 3.4 mmol/L (↑) | p.12 |
| Heart rate | 118 bpm on arrival | p.6 |
| IV antibiotics | Started 02:10 | p.14 |
| Comorbidity | CKD stage 3 | p.2 |
| Missing | Repeat lactate not documented | — |
Checks
- InterQual: inpatient met
- Payer: Aetna criteria
- Repeat lactate missing
- Physician attestation
// Problem
The Problem
Denials are usually documentation failures rather than clinical ones. The patient genuinely required the level of care delivered, but the utilisation review sent to the payer did not assemble the evidence in the form that payer requires — so the claim is denied, an appeal is written, and the hospital carries the cost of the delay whether or not it eventually wins. The underlying work is brutal: a case manager reads a chart that runs to hundreds of pages, finds the abnormal results, comorbidities and risk factors that justify the admission, and writes it up, repeatedly, throughout the stay.
- The evidence that justifies level of care is scattered through a chart nobody has time to read exhaustively.
- Payer-specific requirements differ, so a review written to one insurer's expectations fails another's.
- Reviews are drafted during the stay under time pressure, which is when detail gets dropped.
- Denials are contested after the fact, which costs more than getting the first submission right.
// Overview
Hub supports case managers at the two points that decide the outcome. On admission it assists in validating and reviewing the patient's chart to establish whether documentation adequately supports the current level of care, highlighting information likely to be relevant — abnormal lab results, comorbidities, risk factors evident in the clinical history — for the case manager to assess. It then produces a preliminary utilisation review draft, which the case manager refines and sends to the payer with wording aligned to what that payer accepts. Through the remainder of the stay the same assistance continues for ongoing review notes, which both reduces the administrative load and reduces denials grounded in level-of-care documentation. Case managers apply their own evaluative criteria throughout — diagnosis-specific care guidelines and payer-specific requirements — and every note is verified by them before it is forwarded.
// AI System
Why AI
The chart is the argument for a model. It is long, unstructured, written by many clinicians in clinical shorthand, and the relevant facts are relevant only in combination — a lab value matters because of a comorbidity that appears eighty pages earlier. Surfacing that combination is comprehension work. Drafting is the second task, and it is genuinely constrained: the note must argue from evidence actually present in the chart, which is why the system highlights before it writes and why the case manager verifies before anything reaches the insurer. Nothing here is autonomous; the clinical and compliance judgment stays with the person accountable for it.
// Specs
Specifications
- CHART REVIEW
- Relevant findings highlighted — labs, comorbidities, risk factors
- CRITERIA
- Organisation's care guidelines plus payer-specific requirements
- DRAFTING
- Preliminary and ongoing utilisation review notes
- SCOPE
- Admission through discharge, not a one-off review
- AUTONOMY
- Every note verified by the case manager before submission
// Features
Features
- 01Chart review simplified by highlighting information bearing on appropriate level of care.
- 02Abnormal lab results, comorbidities and clinical-history risk factors surfaced for assessment.
- 03The organisation's own evaluative criteria applied, not a generic clinical standard.
- 04Payer-specific requirements factored into the wording of each review.
- 05Preliminary utilisation review drafted at admission, refined by the case manager.
- 06Ongoing review notes assisted throughout the stay, reducing administrative load.
// Architecture
Architecture
REVIEW FLOW
Runtime · one item, left to right
- 01Patient Admission
- 02Chart Ingestion
- 03Evidence Highlighting + Criteria MatchLab ResultsComorbiditiesCare GuidelinesPayer Requirements
- 04Utilisation Review Draft
- 05Case Manager Verification
- 06Payer Submission
dashed = the inference step, where the system exercises judgment
System stack
Data in · decisions out
01
Sources
The chart and the rulebook
02
Ingestion
Clinical data, structured and free text
03
Ontology
Encounter, evidence, criterion
04AI
Intelligence
Find the evidence, argue from it only
05Human
Human control
Case manager verifies every note
06
Actions
Written back
Observability
Every model call traced; evals run on real cases, not anecdotes.
Governance
Entitlements enforced at retrieval; rules versioned by the organisation.
Write-back
Systems of record are written only through the approval gate.
Drafts argue only from evidence present in the chart; the case manager verifies every note before it is sent.
// Impact
Impact
- At admission
- First review drafted, against end-of-stay assemblydesign intent
- Verified
- Every note, by the accountable case managerdesign intent
Interested in Denials Management?
Let's look at what your denials are actually being denied for.
Get in touch