Skip to content
← BLUEHEALTHCARE
blueChart

blueChart

Utilization-management evidence mapper

For clinics and hospitals: checks a treatment that has been ordered or done against the patient's insurance coverage requirements and maps each requirement to the exact chart evidence that supports, contradicts, or never addresses it — then hands your own staff a signed evidence packet for the insurance submission, not a verdict.

Flagship — demo-ready
Request a demo Request a pilot conversation Read the manual
Start here →
Runs locally · CLI or web UI · Ed25519-signed receipts · no cloud account required
Who it's for

Clinics and hospitals. Nurses, physicians, and billing or utilization-management staff who check a treatment that has been ordered or done against the patient's insurance coverage requirements and need a signed evidence packet for the insurance submission.

What it is not

blueChart never approves, denies, recommends, or alters coverage. It is not a prior-authorization decision engine.

How it works
1
Load the insurer's coverage requirement (a policy or criteria set) and the patient's chart evidence.
2
blueChart's deterministic matcher runs the evidence map: every requirement is typed into one of the engine's lanes — SUPPORTED, CONTRADICTED-NUMERIC (contradiction is currently detected against a numeric threshold, not free text), SEARCHED-ABSENT or NEVER-SEARCHED, UNVERIFIABLE, NEEDS-JUDGMENT, or CANNOT-CERTIFY.
3
A member of the clinic's staff opens the packet, inspects each lane's linked evidence, and reaches their own determination.
4
The packet is signed and exported for the insurance submission and the case file.
5
Anyone can verify the signature offline, without installing blueChart, with the standalone verifier.
Decision file example: requirements matched to evidence, each requirement marked as supported, contradicts, or missing evidence, with the reviewer decision recorded separately and checkable offline
Screens

blueChart is worked the way clinic staff work a case: find it in the library, open the packet, inspect the evidence behind any verdict you doubt, then export and sign. The four screens below follow one synthetic case from the library to the signed receipt. No screen is a coverage decision, and every screen carries the same footer saying so.

blueChart Case library screen: the suite shell's sidebar (Case intake with Library and New analysis, Evidence map, Reviewer, Case file) beside a table of synthetic cases including SYN-0154 marked Incomplete evidence and SYN-0152 marked Cannot certify, with a New case button.
Synthetic demo data
Case library — 57 synthetic cases, with tabs for All work, Draft, Ready for review, Needs attention and Archived. Two statuses to notice: Incomplete evidence and Cannot certify are review states the engine reports, not outcomes it has decided.

Open any row and blueChart lands on the packet.

blueChart Case evidence packet screen: three coverage requirements mapped to chart evidence, one Supported, one Contradicted (numeric), one Searched-Absent, with a claim-boundary note that a signed receipt does not prove an underlying claim is true, and a packet status of Incomplete evidence, human review required.
Synthetic demo data
Case evidence packet — three coverage requirements, three verdicts: R1 Supported by an exact chart citation, R2 Contradicted (numeric) — the chart's figure conflicts with the policy threshold — and R3 Searched, absent. The packet status reads Incomplete evidence, human review required. The screen says so itself: evidence preparation, not a coverage decision.

Inspect evidence opens the matrix behind these three rows.

blueChart Requirement-by-evidence matrix screen, filtered to Exceptions, showing a Contradicted (numeric) verdict with the exact chart citation and source hash in an evidence inspector panel.
Synthetic demo data
Requirement-by-evidence matrix, filtered to Exceptions. The inspector shows why R2 is Contradicted (numeric): policy requires at least 72 hours, the chart documents 48, cited to page 2, with the source document's SHA-256 and the parser recorded as local and deterministic. Copy citation puts the exact reference in the reviewer's own notes.

From here the reviewer reaches their own determination; Export writes the signed packet for the case file.

blueChart Signed process receipt screen for case SYN-0100: a Download JSON button, instructions for the standalone verify_receipt.py script including how to pin a trusted signer's public key, a receipt body showing coverage-ledger entries each marked CONSULTED with a matched requirement and source id, a Verify offline button, a Run tamper demonstration button, and a Reviewer attestation panel reading 0 recorded.
Synthetic demo data
Signed process receipt — the packet closes here. verify_receipt.py runs the identical check this page runs, offline, and a --trusted-signer-pub flag lets the clinic's own auditor or counsel confirm who signed it, not just that the shape is intact. The reviewer attestation panel below shows 0 recorded, because in this synthetic run no reviewer has signed off yet.
Status, measured

measured Demo-ready: all 12 build-contract milestones complete. Full backend suite, strict type checks, and an end-to-end UI test all pass. make demo and make verify-demo both verified on a fresh clone.

not true yet No signed pilot. No live PHI has ever been processed. No non-US deployment.

A signed receipt proves what blueChart ran and recorded; it does not prove an underlying real-world claim is true. blueChart does not approve, deny, recommend, pay, retract, or alter anything a named human is responsible for deciding.