Kipu 1104: What It Is and How UR Teams Use It

Published · 9 min read

Key takeaways

Table of contents

  1. What does 'Kipu 1104' mean?
  2. How does the 1104 document fit into a prior authorization workflow?
  3. How does 1104 documentation support concurrent review?
  4. How does the 1104 help you win a peer-to-peer or appeal a denial?
  5. Why do UR teams track 1104 tasks in spreadsheets instead of Kipu?
  6. How do UR tools compare for 1104 and authorization workflows?
  7. What should a UR coordinator do differently tomorrow?

Kipu 1104 refers to a document and report reference inside Kipu EMR that UR coordinators encounter when assembling clinical documentation for prior authorizations, concurrent reviews, and peer-to-peer calls. If you have seen "1104" on a task or report and wondered what it is and where it fits in your workflow, this explainer covers it.

What does 'Kipu 1104' mean?

"Kipu 1104" refers to a numbered document or report within Kipu EMR, the electronic medical record built by Kipu Health for addiction treatment and behavioral health facilities. Kipu's documentation uses numbered IDs for its clinical forms and reports, and 1104 is the label UR staff use shorthand for when pulling the clinical summary documents attached to a patient's chart for authorization work. Kipu's own help center indexes these documents by number, which is where the convention comes from.

Where the 1104 number appears in Kipu EMR

You'll see it referenced when staff share report IDs with each other: "run the 1104 on this client" is faster than naming the full report. The number identifies the output, not a module or a billing code.

Why UR staff search for it

UR coordinators juggle dozens of concurrent reviews across payors with different medical necessity criteria, and a missing note can trigger rework or an automatic denial (HIT Consultant on UR automation and denials). Tools like CriteriaIQ layer authorization workflows on top of Kipu (Kipu EMR Authorization Analysis | CriteriaIQ), so knowing which report number feeds your packets matters.

How does the 1104 document fit into a prior authorization workflow?

The 1104 is the clinical packet behind your initial authorization request. When a UR nurse pulls an assessment, ASAM dimensions, and length-of-stay justification together in Kipu, the 1104-style report is what gets attached to the service request form and submitted to the payor. It is the document the payor reviewer reads first.

From service request form to payer submission

In practice, the 1104 travels alongside the SRF, not instead of it. Your workflow is: verify demographics and level of care, confirm the ASAM 4th Edition criteria you are invoking, generate the clinical summary, attach both documents, and log the submission date and authorization window in your tracker. Miss any one of those steps and the request sits, or worse, denies for missing documentation. CriteriaIQ automates the criteria-mapping step inside the EMR you already run; Kipu's native tools and a spreadsheet-plus-inbox setup both leave the payor-specific formatting to you (CriteriaIQ vs Kipu: UR and Denial Management).

What payers expect alongside the 1104

Expect payors to ask for the most recent assessment, medication list, lab results, and any prior treatment history referenced in your medical necessity argument. Submit them with the 1104 rather than waiting for the pends call, because each pend cycle adds days to your authorization window and pushes your admission date later.

How does 1104 documentation support concurrent review?

Once a client is admitted, the 1104 stops being a prior auth artifact and becomes your working chart for concurrent reviews. Every continued-stay request is a fresh medical necessity argument, and reviewers pull from the same document: ASAM dimension ratings, treatment plan updates, and progress notes tied to length of stay. When UR nurses manage dozens of cases across payors with different criteria, a stale or incomplete 1104 is what turns a routine concurrent review into hours of rework or an automatic denial (HIT Consultant).

Continued stay and step-down documentation

Treat each continued-stay window as a deadline on the 1104 itself. Before the payor's review date, confirm the document reflects current level of care, recent assessments, and any step-down plan. A payor reviewer looking for justification for another week at residential will check whether the 1104 narrative shows active treatment toward stated goals, not just continued occupancy.

Matching ASAM 4th Edition criteria in the 1104 narrative

Map each ASAM 4th Edition dimension to specific notes in the 1104 before you submit. If dimension 4 (readiness to change) or dimension 6 (recovery environment) is your weakest argument, say so in your peer-to-peer prep rather than hoping the reviewer doesn't ask. CriteriaIQ RCM builds these criteria checks into the Kipu workflow, though no tool replaces your clinical judgment on whether the documentation actually supports the stay.

How does the 1104 help you win a peer-to-peer or appeal a denial?

Building the P2P packet

When a payor schedules a peer-to-peer, the reviewing clinician will judge medical necessity against the documentation, not your verbal summary. Pull the 1104 and every supporting note into a single packet before the call: admission assessment, ASAM level-of-care justification, treatment plan updates, and progress notes covering the authorization window. Flag gaps now, while you still have hours to ask a clinician for a supplemental note. A missing sleep study or an outdated assessment is fixable before the call; it is rarely fixable after a denial.

CARC/RARC codes and what they tell you about the missing documentation

If the denial lands anyway, the CARC and RARC codes on the remittance tell you what the payor says is missing. A medical-necessity CARC points back to the 1104: compare the criteria the payor cited against what your packet actually contained. If the note exists but was not in the packet, that is an appeal with a simple exhibit list. If the note never existed, route the gap back to the clinical team before you write the appeal letter. Either way, the 1104 is your index of what was and was not submitted.

Why do UR teams track 1104 tasks in spreadsheets instead of Kipu?

Because the 1104 tells you what was authorized, but not what happens next. Deadlines for the next concurrent review, the peer-to-peer call, and the step-down request live outside the document, and Kipu's native tools don't chase them for you.

The authorization window problem across multiple payors

Each payor sets its own authorization window and concurrent review cadence, so a residential case might need a re-auth on day 5 while an IOP case runs on day 14. UR nurses juggling dozens of cases across different criteria end up building their own countdown in Excel and a shared inbox, because that is faster than configuring anything else. Behavioral health facilities lose 10-20% of potential revenue to preventable billing mistakes and denials, and a missed concurrent review date is one of the most preventable causes.

What Kipu tracks natively vs what it doesn't

Kipu stores the clinical record, the 1104, and the authorization details in one chart, which is genuinely useful. What it doesn't do natively is push a payor-specific deadline to your queue three days before it lapses, or log that a peer-to-peer was requested and by whom. That gap is why tracking drifts to spreadsheets, and why a missed date usually surfaces only after the denial posts.

How do UR tools compare for 1104 and authorization workflows?

Comparison criteria

Judge any UR tool on four things: does it pull the 1104 document (or its equivalent) automatically, does it track concurrent review deadlines per payor, does it prep peer-to-peer packets, and does it run inside your existing EMR rather than beside it. Prior authorization remains the most operationally disruptive part of behavioral health RCM, so deadline tracking matters more than dashboard polish.

Tool1104 handlingConcurrent review trackingRuns in Kipu
Spreadsheets + shared inboxManual copy-pasteManual, error-proneBeside
RittenUR workflow built inYes, nativeStandalone
Behave HealthBuilt for BH treatment opsYes, nativeStandalone
CriteriaIQ RCMPulls from Kipu/BestNotesYes, per payorInside

Where CriteriaIQ fits and where it falls short

CriteriaIQ runs on the Kipu or BestNotes EMR you already use, so the 1104 and supporting notes feed authorization timelines without a second login. It handles concurrent review tracking and peer-to-peer prep across payors.

Where it falls short: it is a UR and RCM layer, not a full EHR. Scheduling, e-prescribing, and clinical documentation stay in Kipu. If you want one vendor for everything, Ritten or Behave Health cover more of the stack; if you want UR depth without switching EMRs, CriteriaIQ is the narrower, focused bet.

What should a UR coordinator do differently tomorrow?

A same-day checklist

Pull the 1104 for every active case and verify each one shows the current level of care, admission date, and the most recent ASAM dimensions. Flag any chart where the last assessment is older than your payor's concurrent review interval. Set calendar reminders for every authorization window expiring in the next 14 days, not the next 72 hours. Before each peer-to-peer, print the 1104 and highlight the two data points the payor reviewer will challenge: length of stay and step-down readiness.

When to escalate to an RCM platform

If you are tracking more than a handful of concurrent reviews in spreadsheets and a single missing note has already cost you a denial, manual tracking is the constraint. Dedicated tools exist: Ritten and Behave Health serve this space directly, while Kipu Health and Sunwave Health offer adjacent capabilities. CriteriaIQ RCM runs authorization timelines, concurrent review prompts, and P2P prep on top of the Kipu or BestNotes EMR you already use, so the 1104 data you have drives the deadlines instead of your inbox. Where it falls short: it is built for behavioral health UR only, so facilities running mixed service lines will still need separate billing workflows.

FAQ

Is Kipu 1104 a form, a report, or an error code?

It is a numbered clinical document or report inside Kipu EMR, not an error code and not a module. Kipu indexes its clinical forms and reports by number, and UR staff use "1104" as shorthand when asking a colleague to run the clinical summary needed for prior authorization and concurrent review work.

Can I customize the 1104 in Kipu EMR for different payors?

Payor-specific formatting is not something the 1104 handles on its own. The document gives you the clinical summary; mapping it to each payor's medical necessity language and required attachments stays with your UR team. Tools like CriteriaIQ automate that criteria-mapping step, while a spreadsheet setup leaves the formatting manual.

Does CriteriaIQ replace Kipu EMR?

No. CriteriaIQ is a UR and RCM layer that runs on top of the Kipu or BestNotes EMR you already use, pulling the 1104 and supporting notes into authorization timelines. Scheduling, e-prescribing, and clinical documentation stay in Kipu. If you want one vendor covering the full stack, Ritten or Behave Health fit better.

How do I fix a denial caused by missing 1104 documentation?

Read the CARC and RARC codes on the remittance to see what the payor says is missing, then compare that against your 1104 packet. If the note exists but was never attached, appeal with a simple exhibit list. If the note never existed, route the gap to the clinical team before drafting the appeal letter.

Is the 1104 the same for detox, residential, PHP, and IOP levels of care?

The document type is the same, but the content should differ by level of care. Each one needs the ASAM dimensions that justify that specific setting, current level-of-care language, and a step-down plan where relevant. A residential packet leaning on occupancy instead of active treatment will not survive a concurrent review.