Benefits on a statutory clock
Anything a state deadline drives: first indemnity payments, rate changes, waiting-period math. Shown: the first check in New York, due by day 18.
Charcoal runs your claims-handling procedures as approved playbooks inside the claims system, EDI, the state boards, CMS, and bill review. It does the rules-based work and stops when an adjuster needs to decide.
Above: one rejected SROI. A missing field is filled from the account record. A date conflict goes to the adjuster. The run corrects the claim and resubmits.
The run above is one playbook. Most of the work on a claims desk takes one of a few shapes. A playbook fits any of them.
Anything a state deadline drives: first indemnity payments, rate changes, waiting-period math. Shown: the first check in New York, due by day 18.
Anything an adjuster approves item by item against the file: medical bills, pharmacy authorizations, RFAs and PARs. Shown: a bill approval queue on a 45-day clock.
Anything you submit and get acknowledgments back on: EDI FROI and SROI, Section 111, state reports. Shown: a quarterly Section 111 response file.
Charcoal reads the documents, works the portals, and updates the claims system your team already uses.
If your team can sign in to it,
Charcoal can work in
it.
You bring what your desks already follow: an account’s special handling instructions, your best-practices audit checklist, the state’s edit matrix, a written walkthrough. Charcoal turns it into a playbook your team reviews and approves before anything runs.
No. Charcoal is not a system of record and there is nothing to migrate. Your claims system stays the system of record, your EDI vendor and bill review stay as they are. Charcoal signs in to those systems the way your desks do and works inside them.
Days, not quarters. A first playbook is typically in production within 24 to 48 hours of the procedure being handed over. There is no integration to build and no data to move, so the work is writing the procedure down and approving it.
No. Compensability, reserves, and settlement stay with the adjuster. Playbooks do the rules-based work around those decisions: reading documents, working portals, keying the claims system, filing evidence. When a step needs judgment, the run routes it to the person you name and waits.
It works your EDI vendor’s portal the way your coordinator does: reads the TE and TR acknowledgments, decodes the data element and error numbers against the state’s edit matrix, fixes what the file supports, and resubmits. Charcoal is not a trading partner itself; your vendor and jurisdiction relationships stay as they are.
Yes. A playbook can carry an account’s special handling instructions, so the same claim type runs one way for one client and another way for the next, with the difference written down and approved.
Playbooks work the same screens your team does. Origami Risk, DXC Assure Claims, ClaimCenter, or a proprietary system: if your desks sign in to it in a browser, a playbook can work in it, alongside the state boards, the Section 111 COBSW, bill review, and the PBM.
Every run keeps a step-by-step record of what was read, what was checked, what was changed, and who signed off, and it writes the file note in your claims system. Client audits, carrier audits, and a DWC audit get answered from the record.
It doesn’t decide compensability, set reserves, or negotiate. It doesn’t improvise: if a run hits something the approved playbook doesn’t cover, it stops and hands the claim to a person.
Independently audited controls.
Controls for regulated data.
Covered deployments with access and audit controls.
Bring the account instructions or the checklist your desks work from today. We’ll show you the same procedure running as a playbook in your systems, evidence and all.