What the examiner receives

An examiner does not receive the reviewer's memory, the hallway conversation, or the chart that still sits only in the hospital. The examiner receives the file the plan can produce. This page is what that file has to contain when the question is a utilization management denial. It is not a description of every audit a health plan can face.

What the examiner is handed

The packet is the reviewer's recollection, written the week the letter arrived. A hallway conversation is cited and was never entered. The hospital chart is named and is not in the envelope. The file is thick and the determination is still a checkbox.

Those are the signs.

Who is asking

Several different readers get called an examiner, and they do not all want the same exhibit. A state insurance department market-conduct examiner samples utilization management files and reads them against the notice rules and the criteria the plan says it uses. A Medicaid external quality review looks at whether a managed care plan's utilization management decisions are supported by the records the plan kept. A program audit can sample Medicare Advantage or Medicaid files for the same kind of question. An independent review organization, or a hearing officer, reads the file because someone appealed. Counsel in a coverage dispute asks for the same stack.

Those readers differ in authority. They do not differ in the practical limit: they can grade only what arrives. If the clinical note never left the hospital electronic record, it is not in the envelope. If the criteria edition was never written down, the examiner has a brand name and a conclusion. If the reviewer is identified only as a queue, the examiner cannot see a credential. The rest of this page is the stack those readers can actually hold. The plan-side statement of the same stack is denial evidence for health plans.

The stack, not the story told later

For a single denial, the file an examiner can use is a short list, and every item on it is a document rather than a recollection. The request, including what service, how many units, and what dates. The clinical documents that were in front of the reviewer when the decision was made, not a later print of a chart that has been amended. The criteria or policy, named and versioned. The reviewer's name and credential, and, where the line of business requires a physician or a particular specialty for an adverse medical-necessity determination, that person's identity. The determination itself: approved, modified, pended, or denied, and for which span. The notice that went to the member or the provider, and when. Anything that happened next: more documents, a peer-to-peer, an appeal, a hearing request, and the decision on that appeal.

A narrative written the week of the audit, explaining what the reviewer would have considered, is not a substitute for that stack. Readers are used to narratives. They are also used to asking which sentence in the narrative was true on the decision date. The utilization management record exists so the answer is a document, not a reconstruction. How a hash chain makes a later edit visible is explained in hash chains and chain of custody. The point of that machinery, on this site, is the file. It is not a claim that a court will admit the file, and it is not a claim that the examiner will agree with the denial.

What a thin file looks like

Thin files are recognizable, and they fail before anyone reaches a close clinical question. The workqueue line says criteria were not met and names no element. The denial letter cites medical necessity and the case note cites a missing form. The criteria attached are this year's edition, and the decision was last year. The progress notes are summarized in two sentences by someone who is not the reviewer, and the source notes are absent. The appeal letter repeats the first letter and does not mention the new records the provider uploaded. None of these is a subtle disagreement about a guideline. Each one is a file that cannot show its work.

InsuredAudit is built to make that thinness visible at decision time, when it can still be fixed, rather than during the exam, when the only honest answer is that the document was never kept. Binding the determination to the criteria and to the inputs does not make the denial correct. It makes a supported denial and an unsupported denial distinguishable. A complete file can still document a denial that a later reviewer overturns. An empty file cannot document anything. The overturn, if it happens, belongs in the file as its own layer, which is the difference described in an appeal file versus a note.

A manifest instead of a scavenger hunt

Plans often can find the pieces if someone hunts across the utilization management system, the imaging archive, the letter vendor, and a reviewer's messages. An examiner on a schedule does not do that hunt. A Court Ready Evidence Bundle, CREB™, on this host is the utilization management export: the timeline, the criteria version, the source documents that were attached, a manifest of what is included, and a chain of custody. What goes in the bundle is described in what a CREB bundle is. The manifest is how a reader sees whether the export is the stored record or a selection assembled for the visit. Counsel can offer that export. The examiner, the hearing officer, or the court decides what to do with it. The software does not.

If the search that brought you here is what a risk adjustment examiner receives on a RADV sample, or what a special investigations unit assembles on a fraud referral, that product is on jilsovereign.com. The company is the same JIL Sovereign Technologies, Inc. The file is not the same file. Do not send a utilization management examiner a risk-adjustment chart and call it the denial file. Do not send a RADV reviewer a prior authorization workqueue and call it the medical record for diagnosis coding. This page stays with the coverage decision.

What is deliberately not in the envelope

The examiner does not receive a promise. InsuredAudit does not decide medical necessity, does not decide the appeal, and does not decide admissibility. AVA can summarize a file and draft language a person reviews before anyone sends it. AVA's draft is not the determination, and it should not be relabeled as the reviewer's reasoning if the reviewer did not adopt it. A model summary that was never shown to the reviewer is not the basis of the denial. If it is produced at all, it is produced as what it is: a later summary, with the person who reviewed it identified. The boundary is what AVA can and cannot do.

The examiner also does not need the member's entire lifetime chart by default. Minimum necessary still applies. The documents that travel are the ones the decision used. A production that dumps unrelated years of notes is not more rigorous. It is harder to read, and it exposes information the decision did not use. The test is whether every fact the denial relied on is in the stack, and whether every document in the stack was actually available when the reviewer decided. Bulk is not the same virtue as a record.

Questions people ask

Who counts as the examiner on this page?

Any outside reader of a utilization management file: a market-conduct examiner, a Medicaid external quality reviewer, a program auditor, an independent review organization, a hearing officer, or counsel asking for the file in a coverage dispute. They do not all have the same authority. They all have the same practical limit. They can read only what the plan produces.

Does the examiner receive the hospital's full chart?

Only if that chart, or the part the reviewer used, was kept with the decision. The hospital's live record is not automatically in the plan's file. A later download can also differ from the copy the reviewer saw, because charts are amended. The production is the copy tied to the decision date.

What if the plan can find the pieces if it looks hard enough?

An examiner on a schedule does not hunt across a workqueue, an imaging archive, a letter vendor, and a reviewer's inbox. A file that can be assembled only by heroics is not the file that was kept. A manifest that lists what the export contains is the opposite of that hunt.

Will a court admit whatever the examiner received?

Not as a rule the software can declare. The record is built so counsel can offer it and so a reader can see what was stored. Whether a court, a hearing officer, or another tribunal admits the file depends on that proceeding. InsuredAudit does not decide admission.

Is a RADV chart the same envelope?

No. A risk adjustment exam and a special investigations file answer different questions and live at jilsovereign.com, operated by the same company. A utilization management examiner receives the coverage-decision file. Do not send one reader the other reader's stack and call them the same production.