Present on Admission Indicator Assignment β FY 2025
Document Purpose
This reference provides comprehensive guidance for assigning Present on Admission (POA) indicators to diagnosis codes on inpatient claims. POA reporting is required by CMS for all principal and secondary diagnoses to distinguish conditions that develop during hospitalization from those present at admission. Accurate POA assignment directly impacts:
β’ MS-DRG payment (CC/MCC eligibility)
β’ Hospital-Acquired Condition (HAC) payment adjustments
β’ Quality measure reporting (e.g., PSI-90)
β’ Audit defense and compliance
π POA Indicator Definitions
The Five POA Values (CMS Official)
POA Value
Definition
When to Use
Payment Impact
Y
Yes β Present at the time of inpatient admission
Condition documented as existing when patient is formally admitted to the hospital (not ER/observation)
Eligible for CC/MCC payment adjustment if criteria met
N
No β Not present at the time of inpatient admission
Condition develops after formal inpatient admission; includes post-procedural complications
May trigger HAC payment denial if on HAC list; CC/MCC may still apply if not HAC-excluded
U
Unknown β Documentation insufficient to determine
Provider documentation does not clarify timing; clinical indicators ambiguous
Treated as βNβ for payment purposes; query recommended
W
Clinically undetermined β Provider unable to determine
Provider explicitly states timing cannot be clinically determined after review
Treated as βNβ for payment; rare; requires provider attestation
1
Exempt from POA reporting
Code is on CMS exempt list (e.g., external cause codes, Z codes for circumstances, certain V/Y codes)
Unaffected by POA logic; no CC/MCC or HAC impact
Critical Distinction
βAdmissionβ = formal inpatient admission order, NOT emergency department evaluation, observation status, or outpatient encounter. A condition developing in the ED but before inpatient admission = POA=Y. A condition developing after the inpatient order = POA=N.
π§ POA Assignment Decision Logic
Step-by-Step Assignment Workflow
1οΈβ£ IDENTIFY THE DIAGNOSIS
β’ Is it the principal diagnosis? β Almost always POA=Y (reason for admission)
β’ Is it a secondary diagnosis? β Proceed to step 2
2οΈβ£ REVIEW DOCUMENTATION FOR TIMING
β’ Does H&P, progress note, or discharge summary state "present on admission," "history of," or "developed day X"?
β’ Are clinical indicators (labs, imaging, assessments) consistent with pre-admission onset?
β’ Does the condition logically relate to the reason for admission?
3οΈβ£ APPLY POA RULES
ββ If documented as existing at inpatient admission β POA=Y
ββ If documented as developing after admission β POA=N
ββ If timing unclear but clinical evidence suggests pre-admission β POA=Y (default to Y when reasonable)
ββ If timing unclear AND no clinical evidence β POA=U (then query)
ββ If provider states "unable to determine" after review β POA=W (document rationale)
4οΈβ£ VERIFY EXEMPT STATUS
β’ Is code on CMS POA Exempt List? β POA=1
β’ Common exempt categories:
- External cause codes (V00-Y99)
- Z codes for circumstances (Z00-Z99) when not principal diagnosis
- Factors influencing health status (Z77-Z99)
- Certain screening codes (Z12-Z13)
5οΈβ£ DOCUMENT POA RATIONALE
β’ For POA=U/W: Include query response or provider attestation in record
β’ For high-risk diagnoses (HAC list): Explicitly document "present on admission" in H&P when applicable
Visual Decision Tree
graph TD
A[Diagnosis Code] --> B{On CMS POA Exempt List?}
B -->|Yes | C[Assign POA=1]
B -->|No | D{Principal Diagnosis?}
D -->|Yes | E[Assign POA=Y<br>Query only if clearly developed post-admission]
D -->|No | F{Documentation Specifies Timing?}
F -->|Yes, present at admission | G[Assign POA=Y]
F -->|Yes, developed after admission | H[Assign POA=N]
F -->|No, timing unclear | I{Clinical Evidence Supports Pre-Admission?}
I -->|Yes | G
I -->|No | J{Provider States Unable to Determine?}
J -->|Yes | K[Assign POA=W<br>Document rationale]
J -->|No | L[Assign POA=U<br>Trigger clinical validation query]
G & H & K & L --> M[Verify Against HAC List if POA=N]
M --> N[Finalize Claim Submission]
β οΈ HAC Interaction: POA=N + HAC List = Payment Denial
CMS Hospital-Acquired Conditions (HAC) List FY 2025
If a diagnosis is POA=N AND appears on the HAC list, Medicare will NOT pay the higher DRG weight for that CC/MCC. The hospital absorbs the cost.
Stage III/IV Intraventricular Hemorrhage in VLBW Infants
P52.01, P52.02
Neonatal-specific; timing critical for POA assignment
Foreign Object Retained After Surgery
T81.521A, T81.528A
By definition POA=N; triggers HAC review
HAC Mitigation Strategy
For conditions on the HAC list that are commonly present on admission (e.g., pressure ulcers in long-term care transfers):
β’ Explicitly document βpresent on admissionβ in the H&P
β’ Include wound staging/photos in admission assessment
β’ Use POA=Y with clear rationale to avoid automatic HAC denial
π Common Scenarios: POA Assignment Examples
Scenario 1: Chronic Condition with Acute Exacerbation
Patient admitted for acute exacerbation of COPD.Documentation: "History of COPD; presents with increased dyspnea, purulent sputum x3 days."Diagnoses:β’ [[J44.1]] COPD with acute exacerbation β POA=Y (exacerbation began pre-admission)β’ [[I10]] Essential hypertension β POA=Y (chronic, documented in H&P)β’ [[E11.9]] Type 2 diabetes mellitus β POA=Y (chronic, managed outpatient)Rationale: Chronic conditions and their acute exacerbations that prompted admission are POA=Y.
Scenario 2: Post-Procedural Complication
Patient undergoes laparoscopic cholecystectomy on hospital day 2.On day 4, develops fever, leukocytosis; CT shows intra-abdominal abscess.Diagnoses:β’ [[K80.20]] Calculus of gallbladder without cholecystitis β POA=Y (reason for surgery)β’ [[T81.4XXA]] Infection following procedure, initial encounter β POA=N (developed post-op)β’ [[A41.9]] Sepsis, unspecified organism β POA=N (secondary to post-op infection)Payment Impact: β’ [[T81.4XXA]] is a CC but POA=N; not on HAC list β still eligible for CC payment adjustmentβ’ [[A41.9]] is an MCC but POA=N; not on HAC list β still eligible for MCC payment adjustment
Scenario 3: Pressure Ulcer Developed During Stay
Patient admitted for stroke rehabilitation.Admission skin assessment: intact skin, Braden score 16 (moderate risk).Hospital day 7: Stage 3 sacral pressure ulcer noted.Diagnoses:β’ [[I69.351]] Hemiplegia following cerebral infarction β POA=Yβ’ [[L89.153]] Pressure ulcer of sacral region, stage 3 β POA=N (developed during stay)Payment Impact:β’ [[L89.153]] is an MCC AND on HAC listβ’ POA=N + HAC list = NO CC/MCC payment adjustment for this diagnosisβ’ Hospital absorbs cost of complicationDocumentation Best Practice: β’ Admission skin assessment with photos/staging prevents ambiguityβ’ Daily skin checks with documentation support POA=N assignment
Scenario 4: Uncertain Timing β Query Required
Patient admitted for pneumonia.Day 3: Acute kidney injury noted (creatinine rise from 1.0 to 2.4).Documentation: "AKI" in progress note; no timing specified.Initial Assignment: [[N17.9]] Acute kidney failure, unspecified β POA=UQuery to Provider:"Clinical indicators show creatinine elevation on hospital day 3. Per CMS guidelines, POA assignment requires determination of whether AKI was present at admission or developed during stay. Please clarify: Was acute kidney injury present on admission (POA=Y) or did it develop during hospitalization (POA=N)?"Provider Response: "AKI developed secondary to IV contrast administered day 2."Final Assignment: [[N17.9]] β POA=NPayment Impact: [[N17.9]] is an MCC; POA=N but not on HAC list β still eligible for MCC payment adjustment.
Scenario 5: Exempt Code Assignment
Patient admitted for hip fracture after mechanical fall at home.Diagnoses:β’ [[S72.001A]] Fracture of unspecified part of neck of right femur, initial encounter β POA=Yβ’ [[W01.0XXA]] Fall on same level from slipping, tripping, stumbling, initial encounter β POA=1 (exempt)β’ [[Y92.010]] Bedroom as place of occurrence β POA=1 (exempt)Rationale: External cause codes (V00-Y99) are exempt from POA reporting per CMS guidelines. Assign POA=1 regardless of timing.
π― Specialty-Specific POA Considerations
PMR / Inpatient Rehabilitation
β’ Comorbidities sequenced in IRF-PAI Item I must have accurate POA to support CMG assignmentβ’ Complications developing during rehab stay (e.g., pressure ulcers, UTI) = POA=Nβ’ Document "present on admission" explicitly for conditions impacting functional prognosisβ’ POA errors can affect both payment (CMG) and quality metrics (IRF QRP)
Urology
β’ Post-procedural urinary retention: If develops after catheter removal = POA=Nβ’ Hematuria: Specify if post-procedural ([[N02.9]]) vs. neoplasm-related ([[C64.9]]) for accurate POAβ’ CAUTI ([[T83.511A]]): POA=N by definition if catheter-associated; ensure documentation supports timing
Otolaryngology
β’ Post-tonsillectomy hemorrhage: Typically POA=N; document timing relative to procedureβ’ Airway edema post-op: POA=N if developing after extubation; link to procedure in documentationβ’ Aspiration pneumonia ([[J69.0]]): POA=N if occurring during hospitalization; POA=Y if reason for admission
Ophthalmology (Rare Inpatient Cases)
β’ Endophthalmitis post-cataract surgery: [[H44.001]] + [[T81.4XXA]] β POA=N for bothβ’ Orbital cellulitis with sepsis: [[H05.011]] may be POA=Y if reason for admission; [[A41.9]] sepsis POA depends on timingβ’ Focus POA documentation on systemic complications (sepsis, AKI) rather than ocular diagnosis itself
π Documentation Requirements for Defensible POA Assignment
What Clinicians Must Document
β FOR CONDITIONS PRESENT ON ADMISSION (POA=Y):β’ "History of [condition]" in past medical history sectionβ’ "[Condition] present on admission" or "known prior to admission"β’ Baseline values/labs consistent with chronic conditionβ’ For exacerbations: "Acute worsening of chronic [condition] beginning [date pre-admission]"β FOR CONDITIONS DEVELOPING DURING STAY (POA=N):β’ "[Condition] developed on hospital day X"β’ "New onset [condition] following [procedure/event]"β’ Timeline linking complication to in-hospital interventionβ’ Clinical indicators showing change from admission baselineβ FOR UNCERTAIN TIMING (TRIGGER QUERY):β’ Avoid ambiguous terms: "possible," "rule out," "vs." without clarificationβ’ If timing truly unclear after review: "Unable to determine if [condition] was present on admission after clinical review" β supports POA=W
Red Flag Phrases Requiring Query
Phrase in Documentation
Risk
Recommended Query
βRule out sepsisβ at discharge
Uncertain diagnosis + uncertain POA
βWas sepsis confirmed? If yes, was it present on admission or developed during stay?"
"Possible AKIβ without timing
POA=U default; may miss MCC
βIs acute kidney injury confirmed? If yes, what is the onset timing relative to admission?"
"Post-op infectionβ without procedure link
Ambiguous POA=N assignment
βWhich procedure is associated with this infection? Did it develop after that procedure?"
"Malnutritionβ without severity or timing
Missed CC/MCC + unclear POA
βDoes patient meet criteria for moderate or severe malnutrition? Was this present on admission?"
"Pressure ulcerβ without stage or admission assessment
HAC risk + POA ambiguity
βWhat is the stage of the pressure ulcer? Was it documented on admission skin assessment?β
βοΈ POA Logic in MS-DRG Grouper: Technical Details
How POA Affects CC/MCC Eligibility
CMS Grouper Logic for Secondary Diagnoses:IF diagnosis code is designated as CC or MCC in FY2025 CC/MCC listAND POA indicator = Yβ Diagnosis counts toward CC/MCC stratification β Higher DRG weightIF diagnosis code is designated as CC or MCCAND POA indicator = NAND code is NOT on HAC listβ Diagnosis STILL counts toward CC/MCC stratification β Higher DRG weightIF diagnosis code is designated as CC or MCCAND POA indicator = NAND code IS on HAC listβ Diagnosis DOES NOT count toward CC/MCC stratification β Base DRG weight onlyIF POA indicator = U or Wβ Treated as POA=N for payment purposes β Apply HAC logic above
MCE (Medicare Code Editor) POA Edits
Pre-grouper validation rules that reject claims with POA errors:β Edit 1: POA indicator missing for non-exempt diagnosis codeβ Edit 2: POA=1 assigned to non-exempt codeβ Edit 3: POA=Y assigned to diagnosis that logically cannot be present on admission (e.g., postprocedural complication without pre-existing condition)β Edit 4: POA=N assigned to principal diagnosis (rare; only if principal dx clearly developed post-admission)β Edit 5: Inconsistent POA across related codes (e.g., sepsis POA=Y but source infection POA=N without rationale)Resolution: Correct POA assignment or provide clinical justification in claim notes.
π POA Assignment Quick Reference Table
Diagnosis Category
Typical POA
Documentation Tip
HAC Risk?
Chronic conditions (HTN, DM, CKD)
Y
Document in H&P as βhistory ofβ or βmanaged outpatientβ
Distinguish from community-acquired; document timing
No
Pressure ulcer stage 3/4
Y or N
Stage and document on admission assessment
Yes (if POA=N)
CAUTI
N
Document catheter insertion date and symptom onset
Yes
Post-op PE/DVT
N
Document pre-op VTE risk assessment and prophylaxis
Yes
Delirium post-op
N
Link to anesthesia/surgery; document pre-op cognitive baseline
No
Acute kidney injury
Y or N
Compare admission creatinine to peak; document cause
No
Malnutrition
Y or N
Document severity and whether present pre-admission
No
External cause codes (falls, MVA)
1 (exempt)
Assign POA=1 regardless of timing
No
Z codes for circumstances
1 (exempt)
Assign POA=1 when not principal diagnosis
No
π Query Templates: POA-Specific Language
Template 1: Uncertain Timing
Subject: POA Clarification β [Condition] β [MRN]Clinical Context:β’ Admission date: [date]β’ Condition first documented: [date/note]β’ Relevant clinical indicators: [labs/imaging/assessments]Coding Requirement:Per CMS guidelines, POA indicator assignment requires determination of whether [condition] was present at the time of formal inpatient admission or developed subsequently.Request:Please clarify the timing of [condition]:β Present on admission (POA=Y)β Developed during hospitalization (POA=N)β Unable to determine after clinical review (POA=W) β if selected, please briefly document rationaleProvider Response: _________________________ Signature/Date: _________________________
Template 2: HAC-Prone Condition
Subject: POA Documentation β [HAC-Listed Condition] β [MRN]Clinical Context:β’ [Condition] documented on [date]β’ Admission assessment on [date]: [findings]β’ CMS HAC List Impact: If POA=N, this diagnosis will not receive CC/MCC payment adjustmentDocumentation Guidance:For conditions on the CMS HAC list, explicit documentation of "present on admission" in the history and physical supports accurate POA=Y assignment and payment integrity.Request:If [condition] was present at the time of inpatient admission, please add "present on admission" to the diagnostic statement in the discharge summary.Provider Response: _________________________ Signature/Date: _________________________
Template 3: Post-Procedural Complication
Subject: POA Assignment β Post-[Procedure] Complication β [MRN]Clinical Context:β’ Procedure performed: [procedure name] on [date]β’ Complication documented: [condition] on [date]β’ Clinical indicators: [findings supporting complication]Coding Guidance:Complications developing after a procedure are assigned POA=N. Accurate POA assignment ensures appropriate DRG grouping and compliance with HAC payment rules.Confirmation:Based on documentation, [condition] developed after [procedure] and is assigned POA=N. Please confirm this aligns with your clinical assessment or provide alternative timing.Provider Response: _________________________ Signature/Date: _________________________
β οΈ Compliance Risks & Audit Defense
Top POA-Related Audit Findings
Finding
Consequence
Prevention Strategy
POA=Y assigned to clearly post-admission condition
Overpayment recoupment + penalties
Train clinicians on POA definitions; implement pre-bill POA review
POA=U overuse without query follow-up
Systemic underpayment + compliance risk
Set query response SLA; track U/W rates by provider
HAC-listed condition POA=N without documentation
Payment denial + quality metric impact
Document βpresent on admissionβ explicitly for high-risk conditions
Inconsistent POA across related diagnoses
Grouper logic errors + DRG misassignment
Review code clusters (e.g., sepsis + source) for POA consistency
β Retain all clinical validation queries and provider responses in medical recordβ Document rationale for POA=W assignments (provider attestation)β Maintain admission assessment documentation for HAC-prone conditionsβ Conduct periodic internal audits focusing on: β’ High-dollar DRGs with CC/MCC β’ Conditions on HAC list β’ Providers with high POA=U/W ratesβ Update POA policies annually with CMS guidance changesβ Train new clinicians on POA requirements during onboarding
π Integration with Your Obsidian Vault
Recommended Wikilinks to Billable Codes Only
When referencing diagnoses in your notes, wikilink only reportable ICD-10-CM codes:
β [[A41.9]] for sepsis
β [[J96.00]] for acute respiratory failure
β [[N17.9]] for acute kidney failure
β [[L89.153]] for stage 3 sacral pressure ulcer
β [[T81.4XXA]] for postprocedural infection
β Do NOT wikilink non-billable concepts: MCC, CC, POA, HAC, DRG, MDC, etc.
ICD-10-CM Official Guidelines FY 2025 β Section III (additional diagnoses) and Appendix I (POA guidelines)
ADL Data CC/MCC Checklist β Quick lookup of CC/MCC designation and documentation requirements
Clinical Validation Query Templates β Standardized language for POA clarification queries
Callout Styles for Visual Scanning
> [!INFO] General guidance or definitions> > [!TIP] Practical workflow advice > > [!WARNING] Compliance risks or common errors> > [!QUERY] When to trigger a clinical validation query> > [!EXAMPLE] Concrete scenario with correct POA assignment> > [!ABSTRACT] Bottom-line summary for quick review>
β ALWAYS POA=Y:
β’ Principal diagnosis (unless clearly developed post-admission)
β’ Chronic conditions documented in H&P
β’ Acute exacerbations that prompted admission
β’ Conditions with clinical evidence of pre-admission onset
β ALWAYS POA=N:
β’ Post-procedural complications (infection, hemorrhage, dehiscence)
β’ Conditions developing after inpatient admission order
β’ Hospital-acquired infections (HAP, CAUTI, CLABSI)
β’ In-hospital falls with injury
β ALWAYS POA=1 (Exempt):
β’ External cause codes (V00-Y99)
β’ Z codes for circumstances when not principal diagnosis
β’ Factors influencing health status (Z77-Z99)
β’ Screening codes (Z12-Z13)
β QUERY FOR CLARIFICATION:
β’ Timing ambiguous in documentation
β’ Severity unspecified when CC/MCC depends on it
β’ Relationship between conditions unclear
β’ Provider uses "rule out," "possible," or "vs." at discharge
β DOCUMENT DEFENSIBLY:
β’ Explicitly state "present on admission" for HAC-listed conditions
β’ Link complications to procedures with timing
β’ Retain query responses in medical record
β’ Update POA assignments based on provider clarification
Bottom Line
POA reporting is a documentation-driven compliance requirement with direct payment impact. Accurate assignment requires:
1οΈβ£ Understanding the five POA values and their payment consequences
2οΈβ£ Reviewing clinical documentation for timing evidence
3οΈβ£ Applying HAC logic when POA=N
4οΈβ£ Querying proactively when timing is ambiguous
When clinicians document timing explicitly and coders apply CMS rules consistently, POA assignment supports both payment integrity and quality measurement.
Last synced: $(date) Next review: FY 2026 IPPS Final Rule (expected August 2025) Vault Status: β Integrated with CMS MS-DRG Definitions Manual v42.0]] and ADL Data CC/MCC Checklist*