Skip to content
Apex Flow

KAIS Reviewer Sheet · Prior and retro authorization · On its own or inside COMMAND PLUS

The moment he signs.

One sheet carries the whole life of an authorization. Before the visit, KAIS answers from the payer's published list and names who decides. When the provider signs, it reads the note against the payer's published criteria, line by line, and lays the evidence beside each one. The clinician answers the clinical questions, the payer's form is filled with what KAIS already holds, and a person sends it. After the visit, the same sheet carries the retroactive window. When a denial still comes back, it is the evidence on the appeal.

  1. 01Before the visit
  2. 02The Reviewer Sheet
  3. 03The packet a person sends
  4. 04Retro authorization
  5. 05The appeal
  6. WISeROriginal Medicare
  7. 062027 · FHIR

Why it exists

Prior authorization is decided by a reviewer reading your note against criteria you rarely see.

Every payer publishes what its reviewer looks for. The policy runs to dozens of pages, the reviewer is often a vendor the payer delegated, and the note was written for the patient, not for the policy. So the request goes out, the reviewer looks for a line the note never states, and the denial lands weeks later on care already given. The AMA's 2025 prior authorization survey puts the work at about 13 hours of physician and staff time a week, for about 40 requests per physician.

01 · Before the visit · Does it need authorization, and who decides

The payer's own list answers. The reviewer is named before anyone opens a portal.

From the day's schedule, KAIS opens a sheet for each visit whose code needs authorization: the patient, the plan, the provider, the reason for the visit. It answers from the payer's published prior authorization list and shows the payer document behind the answer. Then it names who decides the request: the payer itself, or the review vendor the payer delegated it to, written out by name with where the request is submitted. In a WISeR state, the card names the state's Medicare contractor and the WISeR participant beside it.

41WISeR codes, every one on Appendix A of the CMS operational guide
6WISeR states, each with its Medicare contractor and WISeR participant named on the card

Codes and states read from the KAIS WISeR table on October 5, 2026, and matched code for code to Appendix A of the CMS operational guide (version 7.0, July 24, 2026). Payers and review vendors appear by name as plain text. Apex Flow is not affiliated with, endorsed by, or sponsored by any payer or review vendor named.

02 · The Reviewer Sheet

Each criterion from the payer's own published policy, answered in the chart's own words.

Every line on the sheet is a documentation criterion from the payer's published policy, cited to its policy number and source. When the signed note reaches KAIS, it answers each line with the exact sentence from the note, computes it from the note's own dates and numbers with the arithmetic shown, maps it to the chart's own line through a cited rule your practice adopted by name, or leaves it blank and names every file it searched. The clinician reads the evidence and decides each answer.

Quoted

The note's exact sentence

The provider's own words sit beside the payer's criterion and its policy citation. No paraphrase and no generated sentence in the answer, so the reviewer reads the record, not a summary of it.

Computed

The arithmetic on the page

A duration or a count is worked from the note's own dates. When a stated duration and the dated record disagree, the line shows both, side by side, rather than filling.

Mapped

A cited rule, adopted by name

Where the words do not answer a line, a cited finding rule can put the chart's own line on it, once your practice adopts that rule by name. Until then the line stays blank and says which rule would read which words.

Absent

The search, named

Where the chart is silent, the line stays blank and lists every file searched, so the gap surfaces at the desk instead of in a denial letter.

Weight shown

Every answer shows how much it carries

Each line is graded so the clinician sees at a glance what stands on the chart and what does not. A denial in the note answers only its own line, and a negative finding is quoted as the note denying it.

On fileQuotedComputedMappedContradictedNot applicableAbsentYours

The clinician

Decides every answer

Accept, change or clear each line. A change or a clear takes a name and a reason, and the peer-to-peer brief carries every line as it was signed.

An example sheet · Synthetic data
Payer criterion (from the published policy)Answer from the chartLevel
At least six weeks of physician-directed conservative care, including physical therapy"Completed 8 weeks of supervised physical therapy with home exercise program; persistent radicular pain."Quoted
Radicular symptoms present for at least six weeksOnset 2026-07-06 to visit 2026-08-31: 56 days, 8 weeksComputed
Results of imaging performed in the past twelve monthsBlank. Files searched: visit note 2026-08-31, referral 2026-08-24, therapy discharge summary 2026-08-28Absent

Payer criterion, from the published policy, cited

Documentation of at least six weeks of physician-directed conservative care, including physical therapy, before advanced imaging of the lumbar spine.

Signed note, quoted

"Completed 8 weeks of supervised physical therapy with home exercise program; persistent radicular pain."

If the note does not say it, the line stays blank and says which files were searched. KAIS never fills a gap with a sentence the provider did not write.

The guardrail

The clinician decides. The record remembers.

The provider answers every clinical question and is the one who declares an exception when the patient does not fit the policy. KAIS records that decision with the clinician's name, shows it first the next time the same patient meets the same policy line, puts the argument on the peer-to-peer page and in the appeal, and sends a policy it finds wrong or outdated to the library for correction. The next sheet on that payer line shows how it was signed before.

Medicare WISeR · Arizona, New Jersey, Ohio, Oklahoma, Texas, Washington

CMS pairs technology with clinician review. KAIS brings that pairing to the payer policies in its library.

CMS's WISeR model reviews selected Original Medicare services in six states, using enhanced technology such as artificial intelligence along with human clinical review, and every recommendation for non-payment is determined by a licensed clinician. KAIS brings the same discipline to the practice, before the request: where the payer's published policy for the service is in the KAIS library, it reads the signed note against that policy's documentation criteria, and your clinician decides each answer. On a WISeR service, the card names the state's Medicare contractor and WISeR participant, asks for the UTN, and keeps the request and its answer on one record.

What CMS built

  • Technology paired with clinical review for selected Original Medicare services, January 2026 through December 2031
  • Six states, one participating company assigned to each
  • A licensed clinician determines every recommendation for non-payment
  • A prior authorization request before the service, or pre-payment medical review after it
  • An exemption, the gold card, since July 2026: earned per clinician NPI with at least 10 requests and the participant's minimum affirmation rate in an assessment period, and held for at least a year

What KAIS holds for WISeR

  • All 41 codes on the CMS Appendix A list, across seven service families, read from operational guide version 7.0 (July 24, 2026)
  • The state's Medicare contractor named on the card in all 50 states, DC and the territories, and in a WISeR state the WISeR participant beside it
  • The UTN asked for wherever Medicare prior authorization applies, so the claim carries it
  • Each request and the answer that comes back, kept on one record

What WISeR means for a practice

  • The request is voluntary. CMS's operational guide (Section 7.2) says submitting a prior authorization request for a WISeR service is voluntary. Requesting before the visit settles the question early and puts a UTN on the claim.
  • No request, then pre-payment review. A claim sent without a decision on file is suspended by the Medicare contractor and routed to the WISeR participant, who asks for the medical records. The practice has 45 days to answer; the participant decides within 3 days of the complete records, and the contractor pays or denies the claim on that decision. No records within 45 days, and the claim is denied.
  • A non-affirmed request is resubmitted, not appealed. Resubmit as many times as needed with the original UTN, and ask for a peer-to-peer review. A denied claim follows the standard Medicare appeal path, starting with redetermination.
  • Skin substitutes, by jurisdiction. Reviewed in New Jersey, Ohio, Oklahoma and Texas. In jurisdiction JF (Arizona and Washington), the participants do not proceed with prior authorization or pre-payment review of skin substitutes (operational guide, footnote 22).
  • Hypoglossal nerve stimulation codes C8007 and C8011 are in WISeR for dates of service on or after April 6, 2026.

What KAIS does on a WISeR visit

  • Flags the line from the schedule when the code is on Appendix A, the state is a WISeR state, the plan is Original Medicare and the date of service is in range, with the JF skin substitute carve-out and per-code start dates applied
  • Reads it as CMS wrote it: WISeR prior authorization request recommended (voluntary), with pre-payment medical review for a claim sent without a decision on file
  • Names where the request goes: the state's WISeR participant, or the Medicare contractor, which forwards it
  • Asks for the UTN so the claim carries it, and keeps the request and the decision on one record
  • After the visit, a WISeR claim with no decision on file moves to the retro lane: the 45-day records due date is counted from the date of the records request, and a denied claim is set up for redetermination with the sheet's evidence
  • A person on your team sends every request; the clinician decides every clinical answer
StateMedicare contractorWISeR participant
ArizonaNoridian (JF)Zyter
New JerseyNovitas (JL)Genzeon
OhioCGS (J15)Innovaccer
OklahomaNovitas (JH)Humata Health
TexasNovitas (JH)Cohere Health
WashingtonNoridian (JF)Virtix Health
Service familyWhat it coversAppendix A codes
Spinal proceduresEpidural steroid injections, vertebral augmentation, cervical fusion13
Skin and tissue substitutesApplication for diabetic and venous leg ulcers (not reviewed in jurisdiction JF)8
Incontinence control devicesSlings, artificial sphincters, sacral nerve stimulation7
Nerve stimulators and induced nerve lesionsNeurostimulator implants; 64605 and 646106
Sleep apneaHypoglossal nerve stimulation (C8007 and C8011 from April 6, 2026)3
Sexual functionPenile prostheses3
Arthroscopic proceduresKnee arthroscopy for osteoarthritis1
TotalSeven families41

Requests began January 5, 2026, for services from January 15, 2026. Requests go to the state's participant directly, or to the Medicare contractor, which routes them. Skin substitutes are reviewed in New Jersey, Ohio, Oklahoma and Texas, and not in jurisdiction JF (Arizona and Washington), where the LCD was withdrawn (operational guide, footnote 22). WISeR applies to Original Medicare only. Family counts read from the KAIS WISeR table on October 5, 2026. Sources: the CMS WISeR model page, the WISeR frequently asked questions and the WISeR Provider and Supplier Operational Guide (version 7.0, July 24, 2026). The participants are named as plain text; Apex Flow is not affiliated with, endorsed by, or sponsored by CMS or any company named.

More on WISeR

03 · The packet a person sends

The request comes out assembled, correctly addressed, and sent by a person.

The form

The vendor's own form, filled

KAIS fills the payer's or vendor's own worksheet with what it already holds: patient, plan, provider, practice. Every determination is listed, and every clinical box stays empty for the clinician, on purpose.

The evidence

The sheet travels with it

The quotes from the signed note, each beside the payer criterion it answers, with the policy cited by number and source, so the reviewer finds the line they look for.

A person sends

Nothing submits itself

A person on your team reviews the packet and sends it. Their name and the time stay on the record with what KAIS advised before anyone decided. Every request carries its own audit trail.

04 · After the visit · Retro authorization

The visit happened without a number. The sheet tells the biller whether a retro request stands a chance.

Once the date of service has passed and no authorization number is on file, the sheet prints its retro line: whether that payer class allows a retroactive request, and why, from the payer class's published rule. It is the same sentence the claim scrub prints, so the biller reads one clock, not two. Once a number is on file, the line steps aside.

The rule, by payer class

Named on the line, with its reason

Original Medicare, Medicaid, the delegated review vendors, and an elective office or ambulatory surgery service each carry their payer class's published rule and the reason behind it. Each one is labeled as that class's published default until the plan's own handbook confirms it.

Elective is the strictest

Argued out of, never into

An elective service reads as not allowed for retroactive review unless the payer's own policy says otherwise. The biller spends the early days on the corrected claim or the write-off decision, while both are still easy.

A claim already sent

It opens its own sheet

A billed line from the claims export for a code a reviewer scores, with no authorization number, and not already paid by the payer unless the payment carries an authorization or necessity takeback, opens its own sheet, titled as a retroactive request. The criteria, the quotes from the record and the request all follow, and the clock runs even on a service billed the day it was performed.

A person decides

Request, correct, or write off

KAIS lays out the window and the evidence. A person on your team makes the call and sends what goes out.

05 · When it is denied

The appeal comes from the record, with a named approver.

When a medical-necessity, authorization or documentation denial comes back (CARC 50 or CARC 197) on that visit, the sheet's quotes from the signed note join the appeal as its evidence, quoted rather than rewritten, with the payer's policy cited by number and source. A quote still in conflict waits for a named reviewer to resolve it before it is cited. The letter asks for a written determination with the specific reasons and the policy provisions relied on. It stays a draft until a named approver at the practice releases it, and that name stays on the record.

CARC 197, prior authorization absent, explained

More from the Reviewer Sheet

Three short films on how the sheet thinks.

The Exception

When the payer's line does not fit the patient, KAIS shows exactly where the case stands against the payer's published policy, and the clinician decides. Synthetic data. Apex Flow is not affiliated with, endorsed by, or sponsored by any company named.

The Blank

Where the chart is silent, KAIS leaves the answer blank, names every file it searched, and records the clinician's answer under their name. Synthetic data. Apex Flow is not affiliated with, endorsed by, or sponsored by any company named.

Signed, Not Sent

KAIS reads the chart and builds the packet. A person reviews it, downloads it with their name and a timestamp, and submits it. Synthetic data. Apex Flow is not affiliated with, endorsed by, or sponsored by any company named.

See every KAIS video

06 · 2027 · FHIR prior authorization

Built toward the payers' FHIR prior authorization APIs.

CMS's Interoperability and Prior Authorization final rule (CMS-0057-F) requires Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and qualified health plan issuers on the federally facilitated exchanges to offer a FHIR Prior Authorization API, with compliance dates beginning January 1, 2027. CMS recommends the HL7 Da Vinci implementation guides for it, Prior Authorization Support (PAS) among them.

Apex Flow's engine carries a mapping layer shaped to the Da Vinci PAS format: the authorization record's service lines and diagnoses as a FHIR claim for preauthorization, with the questionnaire answers and references to the supporting documents beside it. Each payer connection is built as that payer's API goes live, and a person sends every request.

The same rule already holds Medicare Advantage, Medicaid and CHIP payers to decisions within 72 hours for expedited requests and seven calendar days for standard ones, and every impacted payer to a specific reason for each denial of a non-drug item or service. A KAIS appeal asks for that reason in writing.

Source: the CMS CMS-0057-F fact sheet. HL7® and FHIR® are the registered trademarks of Health Level Seven International, and their use here does not constitute an endorsement by HL7.

07 · Every decision recorded

What KAIS advised, what the clinician decided, what the payer answered. One record.

KAIS writes down its advice before anyone acts on it, and every later step joins the same record, so agreement can be measured: the engine against the clinician, and the request against the payer, by payer and by specialty.

What KAIS advised

Each determination, with its source

The note it was read from, the payer criterion it answers, and the rule and version behind it, kept as they stood the moment the sheet was filled.

What the clinician decided

Each decision, under a name

Accept, change or clear, recorded under the clinician's name. A change or a clear carries its reason, and a changed answer is a new entry beside the old one.

What the payer answered

Each answer, as it arrives

The decision, the authorization number, and the units and dates it is good for, with who recorded the answer and how it came in.

The Reviewer Sheet does

  • Quote the signed note beside each criterion the payer's reviewer looks for
  • Name who decides the request and where it goes
  • Fill the vendor's own form with the facts KAIS holds
  • Show the retroactive window and what the request needs after the visit
  • Keep the clinician's decisions and exceptions on the record
  • Become the evidence on the appeal

It never

  • Calls a service approved or covered: the payer decides that
  • Ticks a clinical box or writes a sentence the provider did not write
  • Submits anything on its own
  • Takes a clinical decision away from the clinician

KAIS Reviewer Sheet · Who it is for

The sheet, on its own.

The KAIS Reviewer Sheet is sold as its own product, for a team that wants prior and retro authorization read against the payer's published criteria and keeps the rest of its system as it is. It starts from a schedule file and the signed notes.

PRACTICES

The authorization desk

For a practice whose denials start at authorization: buy-and-bill drugs, surgical and interventional procedures, imaging. The sheet opens from the day's schedule, and the clinician decides each answer.

BILLING COMPANIES

Every client, the payer's own line

For a billing company that works authorizations for its client practices. The request your team sends carries the note's own sentences beside the payer's criteria. KAIS for billing companies.

HOSPITALS

Outpatient services first

For rural and critical access hospitals: outpatient surgery, imaging, infusions and drugs, before the service and after it. KAIS for rural and critical access hospitals.

On its own, or inside COMMAND PLUS

Prior and retro authorization, worked from the payer's own published policy.

Built for practices where a denied claim is worth thousands: buy-and-bill drugs and biologics, surgical and interventional procedures, more than one site of service. The KAIS Reviewer Sheet is sold on its own at $1,950 per provider per month for practices and billing companies. Hospitals are quoted per facility, in writing. It also comes inside COMMAND PLUS, with chart review and everything in COMMAND. Run the 7-day demo under your own practice identity, with synthetic patients and authorization checks inside its caps, or see every price on the pricing page.