Study guide

5.3 Cross-Functional Collaboration: HIM, Quality & Case Management

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

5.3 Cross-Functional Collaboration: HIM, Quality & Case Management

Key Takeaways Explain This Topic AI

Share accurate record facts while preserving distinct responsibilities for provider diagnosis, coding, quality algorithms, and admission review.

Resolve actual documentation or input differences through a source-based process; a preferred DRG or quality result does not establish the right answer.

AHRQ v2025 PSI 11 has separate diagnosis and procedure routes with specific dates and exclusions; a generic over 48-hour or POA-only test is insufficient.

Apply POA within each measure’s actual logic; a suspected safety event is not itself an automatic hospital-level HACRP reduction.

The Two-Midnight regulation includes supported shorter-stay circumstances; GMLOS and transfer payment require their own rules rather than a diagnosis-driven utilization target.

Last updated: October 2026

5.3 Cross-Functional Collaboration: HIM, Quality & Case Management

The same record can support coding, quality measurement, utilization review, and care transitions. Each use has different rules. Effective collaboration begins by identifying which decision is being made and who owns it. A diagnosis code, a safety-measure event, and a payment adjustment are related possibilities, not interchangeable conclusions.

Share the facts while preserving distinct responsibilities

The AHIMA CDI ethical standards support interdisciplinary education and collaboration with coding and quality professionals. A practical division of work is:

Partner Question to resolve Information CDI can help clarify

HIM and coding What is reportable, and how do the applicable classification rules represent it? Provider wording, conflicting diagnoses, procedure details, timing, and query responses

Quality and patient safety Does the correctly abstracted case meet the specified measure logic? Relevant record facts and documentation discrepancies, with the analyst verifying code lists, dates, population, exclusions, and calculation

Case management and utilization review What admission, coverage, care-transition, and utilization questions need resolution? The documented clinical course, admission-order timing, ongoing needs, and discharge plan

Treating providers What condition, relationship, or clinical significance is supported? A neutral clarification request presenting the relevant record information

Define handoff and release responsibilities locally. A shared discussion should not turn a desired payment or quality outcome into a diagnostic answer. The coding team still applies the classification rules; the quality team applies the measure; admission decisions remain with appropriately authorized practitioners and the relevant review processes.

Resolve the specific discrepancy

When a working and final coding result differ, use the reconciliation approach from chapter 4 to compare the same encounter, release, and input set. Determine whether documentation changed, a procedure was omitted, a rule was applied differently, or a clarification remains unresolved. A matching DRG does not prove every input is correct, and a lower-weighted final result is not automatically wrong.

For a clinical-validation concern, reviewers can bring the relevant evidence to the responsible provider through a compliant clarification process. Locally agreed clinical guidance may help teams recognize concerns, but a threshold on a worksheet does not itself authorize the coder or CDI practitioner to assign or delete a diagnosis. CM guideline I.A.19 and the 2026 query brief distinguish provider diagnostic responsibility from the need to clarify conflicting or questionable documentation.

Record the resolved input and reason. Huddles, shared case reviews, and escalation can support this work, but they do not guarantee that all mismatches, delays, or denials disappear.

Separate quality-event logic from hospital payment

AHRQ PSIs identify potentially preventable safety events through specified administrative-data algorithms. For the examples below, use the published AHRQ v2025 specification. An actual CMS reporting or payment program requires the version, population, software, and measurement period selected by that program; do not assume an AHRQ example is the complete CMS payment algorithm.

The AHRQ v2025 composite guide lists ten PSI 90 components: PSI 03, 06, 08, 09, 10, 11, 12, 13, 14, and 15. PSI 04 is not a component of that composite. A measure's number and title do not establish that it belongs in every safety composite.

CMS's HAC Reduction Program overview describes a hospital-level scoring and payment program. A single suspected PSI event is not itself an automatic 1% reduction. The separate selected-HAC/POA payment rules discussed earlier also do not supply a universal POA scoring table for all quality measures.

Apply the actual PSI 11 routes

The AHRQ v2025 PSI 11 specification concerns eligible elective surgical discharges for patients aged 18 or older, using its specified surgical-discharge and OR-procedure definitions. Evaluate the denominator and all exclusions before the numerator.

Its numerator can be satisfied through separate routes:

Route Published v2025 criterion

Diagnosis A secondary code in the acute postprocedural respiratory-failure collection, which includes J95.821 and J95.822

Ventilation greater than 96 consecutive hours The last date of the listed ventilation procedure is zero or more days after the first major OR procedure, when both dates are available

Ventilation 24–96 consecutive hours The last date of the listed ventilation procedure is two or more days after the first major OR procedure, when both dates are available

Intubation The last date of a listed intubation procedure is one or more days after the first major OR procedure, when both dates are available

The procedure collections include 5A1955Z for ventilation greater than 96 hours and 5A1945Z for 24–96-hour ventilation. Use the exact code collections and date logic rather than replacing them with a generic over 48-hour test.

The specification has numerous denominator exclusions. They include the specified principal or POA respiratory-failure and end-stage-heart-failure conditions; specified tracheostomy circumstances; malignant hyperthermia; POA neuromuscular or degenerative neurological disorders; listed airway-compromise, esophageal, lung-cancer, and transplant procedures; specified respiratory, obstetric, and newborn MDC circumstances; and defined missing-data or ungroupable cases. The analyst must apply the complete specification and linked lists, not only one familiar exclusion.

Example: A quality analyst has verified that an adult elective surgical discharge meets the v2025 denominator and has no exclusion. The first major OR procedure date is June 10. The recorded last date of 5A1945Z is June 12. That is two days after the first major OR procedure, satisfying this procedure route's date criterion. A secondary respiratory-failure diagnosis is not required for this route. The example does not authorize diagnosing respiratory failure from ventilation or predict a hospital-level penalty.

Conversely, if a diagnosis route does not apply, assess the procedure routes before concluding that no event exists. Changing wording to respiratory insufficiency cannot be used as a substitute for checking the actual algorithm.

Use POA and complication documentation for their proper purposes

Assign POA from its coding guidance and the relevant record facts. Then let the analyst apply the specific measure's handling of that information. Do not teach that every Y or W excludes a case from every PSI, that every N creates an event, or that all measures handle U identically. The particular diagnosis, denominator, exclusions, procedure routes, and other inputs can matter.

Likewise, a condition described after an operation is not automatically a coded complication. CM guideline I.B.16 addresses documentation of complications of care, including the required relationship when applicable. A reviewer should not translate delayed extubation or postoperative respiratory insufficiency directly into acute postprocedural respiratory failure. Clarify a genuine diagnostic or relationship question neutrally; do not seek a particular phrase to remove a quality flag.

This division of responsibility permits two valid findings at once: a diagnosis may need clarification, while a procedure-based measure route may already be satisfied. Correct each issue through its own rules.

Coordinate admission review without a clock-only rule

42 CFR 412.3 includes a formal inpatient order by a qualified, licensed practitioner with the required admitting privileges. Under paragraph (d)(1), admission is generally appropriate for Medicare Part A payment when the admitting physician expects hospital care to cross two midnights and the documented medical factors support that expectation.

The regulation also addresses other circumstances:

An unforeseen event such as death or transfer can shorten an expected two-midnight stay without automatically making inpatient treatment inappropriate.

A specified inpatient-only procedure is generally appropriate for Part A payment regardless of expected duration, under paragraph (d)(2).

Under paragraph (d)(3), a shorter expected stay may be appropriate based on the physician's clinical judgment and supporting record.

Two midnights is not a requirement to spend 48 hours in observation before admission. An inpatient-only listing is also not a blanket guarantee that every coverage or claim requirement is satisfied. CDI can help clarify the clinical course and missing documentation; it does not manufacture an admission rationale or replace the authorized admission decision.

Keep utilization and discharge information accurate

GMLOS is a group benchmark, not an individual treatment plan or a target to increase by obtaining another diagnosis. Adding a reportable condition does not universally move a case to a higher group or produce a higher GMLOS. Review ongoing clinical needs and discharge barriers with case management using the actual record.

For a potential postacute transfer, verify disposition and services with the relevant partners. 42 CFR 412.4 requires qualifying circumstances and provides a graduated calculation, cap, and special rules. As the earlier worked example shows, a below-GMLOS stay need not yield a reduced payment. Documentation should accurately describe where the patient went and what services were planned and delivered, rather than select a disposition to obtain a preferred payment.

Close the communication loop by recording the corrected fact, responsible owner, resulting coding or measurement review, and any education needed. The shared objective is an accurate account of care and appropriate use of that account in each process.