The assurance products — the model layer they were designed to have
No patient data in either. Adoption is by numbered edition, never by individual run, so a stranger can rerun the exact result later.
ITEM 17PlannedNo patient data
Helps author coverage criteria and back-tests them
Helps a payer reviewer draft coverage criteria in plain language, then back-tests the draft against past synthetic cases — adopted only by numbered edition, never by individual run, so a stranger can rerun the exact edition later and get the exact same result.
Synthetic example walkthrough
Who
Dr. Samuel Otieno (synthetic example), a medical policy reviewer at a payer using blueChart.
Situation
He needs to update coverage criteria for a diagnostic test and wants to see how a draft change would have affected last year’s cases before publishing it.
Blue shows
A candidate criteria draft in plain language, plus a back-test summary: “Applied to 340 archived synthetic cases: 12 decisions would change.”
They do
Dr. Otieno reads all 12 changed cases individually, edits the draft if the change is not what he intends, and publishes a new numbered edition only once satisfied.
Design mockup · not built Shown inside blueHealthcare's real shell (top bar, left rail, product tokens) with synthetic data, composed from the platform's own components — not a live feature, and not a real screenshot of a shipped screen.
What it never does
Never publishes an edition on its own.
Never changes a decision already made — the back-test is a preview, not a re-decision.
ITEM 18PlannedNo patient data
Generates a policy sidecar and checks it is grounded
Drafts a plain-language explanation (a “sidecar”) of a coverage policy alongside the deterministic rule, and checks that every sentence in it is actually supported by the rule text it describes — no personal data involved anywhere in this feature.
Synthetic example walkthrough
Who
Dr. Samuel Otieno (synthetic example), publishing the criteria edition from the tool above.
Situation
Reviewers using the policy need a plain-language explanation next to the formal rule, and a mismatched explanation is worse than none at all.
Blue shows
A candidate sidecar sentence — “This test is covered when ordered after a documented trial of first-line therapy” — with a grounding check result: “Supported by rule clause 3(a).”
They do
Dr. Otieno reads every sentence the grounding check flags as unsupported, rewrites or removes it, and publishes the sidecar only once every remaining sentence passes.
Design mockup · not built Shown inside blueHealthcare's real shell (top bar, left rail, product tokens) with synthetic data, composed from the platform's own components — not a live feature, and not a real screenshot of a shipped screen.
What it never does
Never publishes a sentence the grounding check marks unsupported.
Never lets the sidecar’s wording override what the deterministic rule actually decides.
