9.1 Concurrent, Retrospective, Pre-Bill, and Prospective Timing

9.1 Concurrent, Retrospective, Pre-Bill, and Prospective Timing

Quick Answer: Inpatient clinical documentation integrity (CDI) prefers concurrent queries while the patient is still in-house. Retrospective queries occur after discharge. Pre-bill (often second-level) review targets high-risk accounts before the claim drops. Prospective review is mainly an outpatient contrast on this exam.

Timing describes when in the encounter and claim cycle you ask for clarification. It does not create a second set of compliance rules. The August 2026 Association of Clinical Documentation Integrity Specialists (ACDIS) and American Health Information Management Association (AHIMA) Guidelines for Achieving a Compliant Query Practice apply to concurrent, retrospective, and prospective queries alike: the question must be nonleading, the clinical indicators must be sourced from the record, the query must omit reimbursement and quality-outcome language, and the treating provider keeps independent clinical judgment. Technology-generated prompts, alerts, and nudges use that same standard no matter when they fire.

This independent OpenExamPrep chapter is written for the inpatient Certified Clinical Documentation Specialist (CCDS) exam. Most of your working day is concurrent review of patients under an inpatient order, with a retrospective safety net after discharge and a tighter pre-bill look at selected accounts. Prospective work exists, but it is the exception in acute-care Inpatient Prospective Payment System (IPPS) CDI and is taught here only so you can recognize it and not confuse it with in-house review.

Why timing still matters on an inpatient exam

Timing changes practical risk, even when the construction rules stay the same. A concurrent query can still be answered while the attending is writing daily notes and before the discharge summary is signed. A retrospective query may require an addendum days later, when recall is weaker and the bill is waiting. A pre-bill query sits on a high-dollar or quality-sensitive account; that operational pressure is exactly when staff are tempted to mention relative weights, complication or comorbidity (CC) capture, or Hospital-Acquired Condition (HAC) impact—language the 2026 brief still forbids.

Timing also interacts with who is still available. While the patient is in-house, consultants, the night intensivist, and the operating surgeon can still be reached. After discharge, you may have only the attending of record, a covering partner, or a delayed addendum workflow. None of that relaxes the requirement that a code-supporting answer live in the permanent health record (or in an approved query location that policy treats as part of that record).

Concurrent queries: the inpatient default

A concurrent query is issued while the patient remains in-house—after the inpatient order and before discharge. This is the preferred inpatient timing because:

• The treating team is still managing the case and can integrate clarification into today's progress note rather than reconstructing the stay later.
• The working diagnosis-related group (DRG) can be updated while utilization review, case management, and quality abstractors are still looking at the stay.
• Present on admission (POA) questions are easier to resolve while emergency department (ED) and admission facts are fresh, including conditions that began in the ED or observation before the inpatient order.
• The clinical picture can still evolve, which is a feature, not a bug: you may need a follow-up query if new imaging, cultures, or specialist notes appear.

Best practice described in the 2026 brief is that concurrent queries receive a response before or at discharge. Organizational policy sets the exact clock; the exam point is that in-house queries should not sit unanswered until the coder is closing the chart. Facilities may also cap how many concurrent queries go to one provider at once so the inbox does not become a pressure campaign.

Concurrent review is not a race to query every abnormal lab on hospital day 0. It is a disciplined look at whether the record is clear, complete, and consistent for conditions that meet Uniform Hospital Discharge Data Set (UHDDS) reporting logic. If the history and physical (H&P) already names acute hypoxic respiratory failure and the progress notes continue to support it, you do not query just because you happen to be concurrent. If two attendings contradict each other on the same day, concurrent timing is the best moment to ask a nonleading question.

Trap: Waiting until the discharge summary might invent missing specificity is not a documentation strategy. If the gap is already query-worthy on hospital day 2, issue the concurrent query. Hoping the summary will create a diagnosis that never appeared in the stay is how unspecified codes and denials are born.

Retrospective queries: after discharge

A retrospective query is issued after the patient has left the hospital. Typical sources include accounts the concurrent team never reached (weekend discharges, late transfers, high census), coding review that finds conflicting or incomplete documentation once the record is assembled, and quality, mortality, or clinical-validation lookbacks that start from the coded record rather than the live chart.

Retrospective work uses the same 2026 construction rules. You still cite indicators with locations. You still avoid leading emphasis. You still leave the diagnosis to the provider. What changes is logistics: the provider may need an addendum, and the organization should assign a defined response window. Unanswered queries should escalate, not linger forever. After escalation is exhausted, close the query per policy and code from the existing health record—do not invent a diagnosis from a hallway memory or a CDI worksheet that never entered the chart.

Trap: Treating retrospective queries as less official because the patient is gone. If the response will support a code, it must still land in the permanent health record. A query that is properly answered, authenticated, and part of that record can support code assignment without being copied into a second note—unless later documentation conflicts, in which case you query again.

Pre-bill and second-level review

Pre-bill review happens after discharge (or very late concurrent) but before the claim is submitted. Many programs call this second-level review: a smaller team re-reads high-risk accounts that first-level concurrent review may have missed.

High-risk screens commonly include mortality cases, possible HAC or Patient Safety Indicator (PSI) conditions, conflicting principal-diagnosis candidates, long length of stay, high-dollar outlier risk, and diagnoses with a history of payer challenge. The screen tells you which charts to open, not what the provider must say.

Pre-bill timing is where financial urgency is highest, so compliance failures cluster here: titles that name the hoped-for major complication or comorbidity (MCC), cover sheets that show the relative-weight delta, or yes/no questions that introduce a new diagnosis so the bill can go out tonight. None of that is allowed. A pre-bill query is still a query. If the record does not support a clarification, you bill from what is already documented.

Second-level review is also not a license to re-query the same provider until a preferred CC or MCC appears. The 2026 brief treats repeated, substantially similar queries as noncompliant when the intent is to pressure or override judgment. A new query is appropriate when new clinical information appears or when a prior answer needs further specificity (for example, type after presence is established). Volume alone is not the violation; intent to override is.

Post-bill queries exist in some recovery and audit workflows. They still must be nonleading. They are not a substitute for getting the record right before the claim drops, and they are not a scored-domain focus beyond recognizing that timing never waives the brief.

Prospective timing: outpatient contrast only

Prospective queries look forward to a planned encounter. In outpatient and ambulatory settings, visits are short, so concurrent review during the visit is often impractical. Staff may review the problem list, prior notes, and available diagnostics before the appointment and query only when the issue is relevant to that planned encounter. Prospective chart reviews that are not tied to a specific encounter, and that do not ask the provider to rewrite old notes, still follow the same nonleading, sourced-indicator rules.

That workflow is not the core of inpatient CCDS. Do not treat prospective problem-list scrubbing as a substitute for concurrent inpatient review, and do not import outpatient-only payment constructs into this exam's inpatient answers. If an inpatient item mentions prospective review, recognize it as the contrast case: same compliance standard, different setting and timing. POA, UHDDS principal-diagnosis logic, and MS-DRG grouping remain inpatient tools.

Putting the four timings together

Organizations should track query response rates and average turnaround. Slow concurrent response and unanswered retrospective queries are program problems to fix with education and workflow—not reasons to relax the 2026 rules. Close exhausted queries and code the record you have.