Study guide
24.2 Query Timeframes, Aging and Measurement
AHIMA Certified Documentation Integrity Practitioner CDIP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Authoritative Coding Resources & Conventions
1.1 Official Coding Resources: Scope, Authority & Research 1.2 General Coding Conventions, Punctuation & Instructional Notes 1.3 Chapter-Specific and Setting-Specific Coding Guidelines
2 Chapter 2: Principal & Secondary Diagnosis Determination
2.1 UHDDS Definitions & Principal Diagnosis Selection 2.2 Two or More Diagnoses Equally Meeting Criteria 2.3 Secondary Diagnosis Reporting Standards & POA Status
3 Chapter 3: Procedure Coding & Sequencing Standards
3.1 ICD-10-PCS Root Operations & Inpatient Procedure Coding 3.2 Principal Procedure Selection & Surgical Sequencing 3.3 Applying Official References to Ambiguous Records
4 Chapter 4: Inpatient Prospective Payment & DRG Grouping
4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels 4.2 Working vs. Final DRG Assignment & Optimization vs. Maximization 4.3 CDI-Coding Reconciliation & Annual Regulatory Updates
5 Chapter 5: Enterprise CDI Promotion & Program Value
5.1 Articulating CDI Value to C-Suite & Hospital Leadership 5.2 Organizational Models, Inpatient/Outpatient Scope & Staffing 5.3 Cross-Functional Collaboration: HIM, Quality & Case Management
6 Chapter 6: Cross-Functional Alignment & Improvement Projects
6.1 Partnering with Nursing, Pharmacy & Allied Health Professionals 6.2 Documentation Improvement Project Identification & Scoping 6.3 Executing, Piloting & Measuring CDI Project Outcomes
7 Chapter 7: Physician Champion Engagement & Clinical Advocacy
7.1 Selection, Role & Credibility of the CDI Physician Champion 7.2 Peer-to-Peer Engagement, Coaching & Overcoming Resistance 7.3 Developing Standard CDI Operational Policies & Procedures
8 Chapter 8: Compliant Policy Architecture & Query Governance
8.1 AHIMA/ACDIS Practice Brief Standards in Policy Construction 8.2 Medical Record Integration of Provider Query Responses 8.3 Policies for Electronic, Paper, and Verbal Query Communications
9 Chapter 9: Query Escalation & Professional Communication
9.1 Chain of Command & Protocols for Unanswered Queries 9.2 Conflict Resolution & Professional Feedback Mechanisms 9.3 Assessing Stakeholder Learning Needs & Specialty Curricula
10 Chapter 10: Educational Delivery & Broader Healthcare Impacts
10.1 Delivery Methods: Microlearning, Case Studies & Grand Rounds 10.2 Documentation Impacts on Clinical Research & Epidemiology 10.3 Documentation Impacts on Case Management, LOS & Reimbursement
11 Chapter 11: Clinical Record Synthesis & Encounter Trajectory
11.1 Synthesizing Provider Notes, Consults & Progress Trajectory 11.2 Interpreting Diagnostic Imaging, Pathology & Labs 11.3 Resolving Conflicting, Ambiguous & Copy-Forward Entries
12 Chapter 12: Advanced Clinical Concepts & Review Prioritization
12.1 Pharmacotherapy, Clinical Trajectories & Disease Correlations 12.2 Inpatient Review Prioritization: High-Risk & High-Volume 12.3 Payer Prioritization, Length of Stay & Re-Review Cadence
13 Chapter 13: Clinical Indicator Mapping & Gap Recognition
13.1 Systematic Identification of Documentation Gaps 13.2 Sepsis Definitions, SEP-1, and Coding 13.3 AKI Criteria, Tubular Injury, and CKD Staging
14 Chapter 14: Diagnostic Precision in High-Impact Conditions
14.1 Respiratory Failure: Acuity, Evidence, and Sequencing 14.2 Heart Failure Phenotype, Acuity, and Hypertensive Combinations 14.3 Encephalopathy, Delirium, and Acute Cognitive Change
15 Chapter 15: Clinical Validation & Complication Discrepancies
15.1 Malnutrition Assessment, Severity, and Provider Documentation 15.2 Principles of a Compliant, Nonleading Query 15.3 Open-Ended, Multiple-Choice, and Yes/No Queries
16 Chapter 16: Query Mechanics & Direct Provider Collaboration
16.1 Electronic Query Systems, Templates, and Technology Oversight 16.2 Collaborating With the Appropriate Query Recipient 16.3 Capturing and Clarifying Query Responses
17 Chapter 17: Quality Indicators & Post-Discharge Clarification
17.1 Present on Admission Clarification and Selected HAC Rules 17.2 Clarifying Acuity, Cause, Site and Severity 17.3 Post-Discharge Query Opportunities and Limits 17.4 Managing Post-Discharge Query Workflows
18 Chapter 18: CDI Operational Dashboards & Quality Auditing
18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use 18.2 Internal CDI Quality Audits and Reviewer Calibration 18.3 Query Trends: Understanding the Process and Provider Experience
19 Chapter 19: Benchmarking, Productivity & Data-Driven Workflow
19.1 Provider Documentation Benchmarking 19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay 19.3 Evaluating CDI Professional Performance 19.4 Using Data to Design CDI Workflow and Staffing
20 Chapter 20: Ethical CDI Standards & Regulatory Frameworks
20.1 Applying AHIMA Ethics to CDI Decisions 20.2 Responding to Financial Pressure and Upcoding Risks 20.3 Maintaining Competence and Professional Integrity
21 Chapter 21: Regulatory Compliance & Enforcement Landscapes
21.1 False Claims, Overpayments and Referral Laws 21.2 Regulatory Agencies, Review Contractors and Appeals 21.3 EHR Templates, Copied Text and Record Integrity
22 Chapter 22: Technology Risks & Second-Level Review Protocols
22.1 CAC, NLP and AI: Context, Oversight and Performance 22.2 Selecting Cases for Second-Level Review 22.3 Conducting and Closing a Second-Level Review
23 Chapter 23: Clinical Validation Queries & Risk Mitigation
23.1 Clinical Validation and Coding Clarification 23.2 Clinical Validation Queries and Denial Evidence 23.3 Detecting Leading, Biased and Unsupported Queries
24 Chapter 24: Noncompliant Query Remediation & Query Lifecycle Management
24.1 Query Remediation and Corrective Action 24.2 Query Timeframes, Aging and Measurement 24.3 Query Records, Retention and Evidence Preservation
24.2 Query Timeframes, Aging and Measurement
Key Takeaways Explain This Topic AI
Define the start event, response endpoint, time basis, exceptions, and observation cutoff before calculating or judging query turnaround.
A stated business-day policy and a calendar-hour policy can produce different deadlines; the 2026 brief leaves specific response windows to organizational policy.
Separate preliminary response, authenticated usable answer, CDI review, and administrative closure so each interval identifies the work it measures.
Retain unresolved work and distinguish overdue from not-yet-due requests; completed-only reporting can conceal delay.
Hospital record completion, local query targets, billing decisions, and retention have different scopes; preserve policy versions and actual event history.
Last updated: October 2026
Define what each query clock measures
Query timeframes are meaningful only when their start, end, calendar, and population are explicit. A request can be delivered, opened, answered, authenticated, reviewed, and administratively closed at different times. Calling all of these events “turnaround” makes it difficult to identify the actual delay or evaluate a local policy fairly.
Section IX of the 2026 AHIMA/ACDIS query brief leaves specific response timeframes to organizational policy. It recommends concurrent responses before or at discharge as best practice, a defined retrospective window, and escalation and closure for unanswered requests. It does not establish one national hourly response target or pre-bill holding period. This lesson applies that framework to clocks and aging; Section 9.1 addresses the escalation process itself.
Specify the events before calculating elapsed time
Build a local definition that someone outside the department can reproduce:
Element Definition needed Why it matters
Start event For example, dispatch through the approved channel A draft saved before delivery is not the same event
Response event Preliminary reply or authenticated usable clinical answer An opened message or an incomplete reply may not resolve the question
Review event When CDI evaluates the returned answer Staff review delay differs from provider response delay
Closure event Administrative disposition and responsible owner Closure can mean answered, withdrawn, or exhausted without response
Time basis Calendar hours, working hours, or defined business days A weekend changes these measures differently
Exceptions Treatment of absence, access failures, holidays, and revised requests An undocumented pause can make the result irreproducible
Document the approved interpretation before judging performance. Do not silently restart a clock when a reminder is sent or mark an unanswered question resolved because a notification was opened. If a request was defective or misrouted, preserve that fact and its correction; decide its treatment under the metric's stated rules rather than conceal the delay.
Work a calendar-versus-business-day example
Illustrative local policy: Business days are Monday through Friday, with no holidays in this example. All timestamps use one time zone with an unchanged UTC offset. The dispatch day does not count. A response is due at 17:00 on the second business day after dispatch. This is an invented local policy for calculation, not an AHIMA/ACDIS requirement.
A query is dispatched on Friday, October 23, 2026 at 15:00. Monday, October 26 is the first following business day; Tuesday, October 27 is the second. The local deadline is therefore Tuesday at 17:00. The elapsed calendar interval from dispatch to that deadline is 98 hours.
Under a different hypothetical rule requiring a response within 48 calendar hours, the deadline would be Sunday, October 25 at 15:00. These policies do not mean the same thing. Neither should be described simply as a national “two-day” standard. A hospital choosing either method would still need to consider its actual clinical setting, coverage, and applicable requirements.
The calculation also depends on the start rule. A policy counting the dispatch day would produce a different business-day result. Do not change that rule after observing whether a case met the target. Publish the definition and apply it consistently to the stated cohort.
Separate response, authentication, and staff processing
Use the same hypothetical Friday dispatch with the following recorded events:
- Event Timestamp Calendar time from dispatch
- Query dispatched Friday, October 23 at 15:00 Start
- Provider opens message Monday, October 26 at 09:00 66 hours
- Preliminary provider reply recorded Monday, October 26 at 10:00 67 hours
- Authenticated usable response available Tuesday, October 27 at 11:00 92 hours
- CDI completes response review Tuesday, October 27 at 14:00 95 hours
If the defined metric ends at an authenticated usable response, its result is 92 hours, not 66 or 67. The interval from that response to completed CDI review is three hours. These figures answer different operational questions. The preliminary reply's content and documentation must still be evaluated through the approved response process; the timestamp alone does not establish coding sufficiency.
Under the stated local business-day policy, the usable answer arrives before Tuesday's 17:00 deadline. That does not establish a national compliance conclusion, prove clinical accuracy, or determine the correct code. The example measures a defined process, while Section 16.3 addresses response content and authentication.
Include unresolved work in the aging picture
A report containing only answered queries can hide the longest delays. Define an observation cutoff, retain the pending population, and distinguish requests whose deadlines have passed from those not yet due. Also identify withdrawn or corrected requests under the published measure definition.
Worked cohort: At a stated cutoff, ten dispatched queries remain in the reporting cohort. Eight have reached their deadlines: six received usable responses on time and two remain unanswered and overdue. The other two queries remain pending and are not yet due. There are no withdrawals or other exclusions in this example.
Overall usable-response proportion at the cutoff is 6 ÷ 10 = 60% .
Eight requests have reached their deadlines: six answered on time and two overdue. The on-time response proportion among requests due by the cutoff is 6 ÷ 8 = 75% .
The two not-yet-due requests remain visible as pending; they are not overdue failures under this local definition.
Reporting only the six completed requests would produce an apparently perfect completed-case result while omitting the two overdue cases. Reporting every unanswered request as overdue would incorrectly classify the two whose deadlines have not arrived. State the numerator, denominator, cutoff, and definition with the result. These are illustrative operational measures, not required national thresholds.
Examine age bands and causes rather than use one percentage as proof of provider behavior. A long interval may involve routing, coverage, unclear content, incomplete documentation, or departmental processing. Investigate the actual record and workflow before assigning responsibility.
Keep query targets separate from record and billing requirements
For covered hospitals, 42 CFR 482.24(c)(4)(viii) includes final diagnosis and completion of medical records within 30 days after discharge. That is a hospital record-completion requirement, not a universal 30-day response window for every query. A local two-business-day query target does not replace that requirement; the record rule also does not supply a five-day billing hold or authorize delaying an urgent clinical concern.
Discharge, record completion, query closure, and claim readiness need separate owners and status information. Apply actual billing and amendment procedures to an unresolved or late answer. Do not infer a diagnosis from silence to release a claim. After exhausted escalation, the brief directs closure under policy and code assignment from the existing health record, using applicable coding guidance . Existing supported diagnoses are not automatically erased merely because requested additional specificity remains unanswered.
Preserve a reproducible time history
Keep the issued version, delivery and response events, responsible roles, due-date basis, and actual disposition linked through the approved systems. If a legitimate late response requires reopening, preserve the earlier closure and evaluate the new information through the applicable process. Do not overwrite an earlier event to make the case appear timely.
When policy changes, identify the effective version and which requests it governs. Explain whether an absence or system outage changes a deadline and who authorizes the decision. A retrospective dashboard should not apply whichever policy version gives the most favorable result. The record-management and preservation rules themselves are addressed in Section 24.3; maintaining a useful aging history does not create a new nationwide retention period.