Physician certification is a distinct condition of Medicare Part A payment, separate from the routine admission order a physician signs on arrival. Missing or late certification does not just cost you a few days of reimbursement. It puts the entire covered stay at risk.
If you’ve seen a “Day 12” deadline mentioned for the initial certification, that number belongs to a different rule entirely. CMS’s own manual keeps the hospital inpatient certification timeline and the skilled nursing facility (SNF) extended care certification timeline in two separate rows of the same summary table.
QUICK SUMMARY
Initial physician certification is due at admission or as soon as reasonably practicable, with no fixed day number attached. The first recertification is due no later than day 14 of the stay. Every recertification after that is due within 30 days of the prior signature date, not the admission date. Certification can be signed by the attending physician, a SNF staff physician with knowledge of the case, or a physician extender who is not employed, directly or indirectly, by the facility. Late certifications are allowed only with a signed, dated, written explanation for the delay. Verifying an extender’s employment status before they sign, and knowing a separate rule blocks any APP from billing the initial comprehensive visit, closes the two gaps facilities miss most.
Table of Contents
What Physician Certification Actually Requires
Physician certification is a signed statement from a physician confirming that a resident’s condition requires daily skilled nursing or skilled rehabilitation services that can only be provided on an inpatient SNF basis. Recertification is the same confirmation repeated at fixed intervals for as long as the covered stay continues.
The Centres for Medicare & Medicaid Services (CMS) is explicit that the admission order itself does not satisfy this requirement. A separate, distinct, signed statement is required, tied either to the condition treated during the qualifying hospital stay or to a new condition that arose after the resident transferred to your facility.
This matters because certification is a condition of payment, not a paperwork formality. If it is missing, late without a valid explanation, or signed by someone not authorized to sign it, Medicare can deny the entire covered stay under review, not just the days closest to the gap.
The Correct Timeline: Why the "Day 12" You May Have Seen Online Is Wrong
The actual SNF timeline has three parts. Initial certification is due at admission or as soon thereafter as is reasonably practicable, with no independent day-number deadline attached to it. The first recertification is due no later than day 14 of inpatient extended care services.
Every recertification after that is due within 30 days of the date of the previous signature. That last point is the one facilities get wrong most often: the 30-day clock resets from the last signature date, not from a fixed calendar built off the admission date.
Here is what the timeline actually looks like when built correctly, compared to the miscalculated version that treats Day 12 as a real SNF deadline.
|
Stay Day
|
Correct SNF Requirement
|
Miscalculated Version (Day 12 Rule)
|
|---|---|---|
|
Day 1
|
Resident admitted to SNF Part A
|
Resident admitted to SNF Part A
|
|
Day 1-14
|
Initial certification obtained (no fixed day)
|
Initial certification "due" by Day 12
|
|
Day 14
|
First recertification due
|
First recertification due
|
|
Day 44
|
Second recertification due (30 days from Day 14 signature)
|
Same, if math holds
|
|
Ongoing
|
Every 30 days from the prior signature date
|
Drifts once any signature is early or late
|
CMS’s Medicare General Information manual, Chapter 4, keeps hospital inpatient certification and SNF extended care certification in separate sections with separate rules. The 12th-day deadline applies to general hospital inpatient stays under Section 10.8.1.
It does not appear anywhere in the SNF extended care section, Section 40, and it is not part of the SNF row in CMS’s own summary table.
The Day 12 confusion traces back to source material that reuses hospital-certification language inside SNF-specific guidance, a copy-paste artifact from a document covering both provider types. Even official-looking Medicare Administrative Contractor pages carry this kind of drift. A facility that builds its compliance calendar off a scraped summary inherits the error without knowing it.
Who Is Legally Allowed to Sign (And the Rule Most Facilities Miss)
A physician extender, in this context, means a nurse practitioner (NP), clinical nurse specialist (CNS), or physician assistant (PA) authorized to sign certifications and recertifications in collaboration with a physician.
Three parties can legally sign: the attending physician, a physician on staff at the SNF with knowledge of the case, or a physician extender. The physician extender condition carries a restriction most facilities never check: that person cannot have a direct or indirect employment relationship with the facility.
If your covering NP is paid through a facility-funded staffing arrangement, directly or indirectly, that relationship disqualifies their signature, regardless of how clinically appropriate their judgment is.
This restriction almost never gets checked at credentialing intake, where it would be simple to verify. It typically surfaces for the first time during an Additional Documentation Request (ADR), a formal request from a Medicare reviewer for the records supporting a claim.
By then the signature is already on file, with no way to fix it retroactively. Facilities using a covering NP under any facility-funded staffing arrangement should confirm this before that NP signs a single certification.
Verifying Employment Status Before an Extender Signs
Knowing the signature restriction does not verify compliance with it. The rule only protects a facility if someone actually checks it, and that check is rarely built into standard credentialing intake.
Ask one direct question before any covering NP, CNS, or PA signs a certification: does any portion of their compensation come from the facility, whether through a direct paycheck or through a staffing or management company the facility pays for that person’s time. Either arrangement disqualifies the signature.
What belongs in the credentialing file:
- A written attestation of the extender’s employment relationship, signed and dated at intake
- The name of the staff member who verified the relationship, and the date it was verified
- A copy of the relevant staffing agreement terms when the extender is placed through a third-party agency, showing who pays whom
- A renewal date for re-confirming employment status, since staffing arrangements change over time
If a disqualified extender has already signed:
If a facility discovers a covering extender was facility-employed all along, the fix starts with an audit, not a shrug. Pull every certification and recertification that extender signed and cross-reference each one against the periods already billed to Medicare.
Determine whether an eligible signer, the attending physician or a properly independent extender, can review the record and issue a corrected certification for any period still open. Loop in your compliance officer or billing lead before deciding how to handle periods that are already closed and paid, since that decision carries its own reporting obligations.
Facilities that use a preferred or on-call NP group for after-hours coverage often assume group placement equals independence. If that group holds a staffing contract paid by the facility for coverage hours, the individual NP signing under that contract is still facility-connected, even though the paycheck comes from the staffing company’s letterhead instead of the SNF’s.
A Related Rule Facilities Often Confuse With This One
The certification signature rule and the initial comprehensive visit rule cover two different moments in a resident’s stay, but facilities frequently treat them as one question. They are not, and mixing them up creates a separate compliance exposure.
Advanced practice practitioner (APP) is the term CMS guidance uses for the same group referred to as physician extenders elsewhere in this guide: nurse practitioners, clinical nurse specialists, and physician assistants.
CMS requires the initial comprehensive visit, the visit that establishes the physician’s plan of care and admitting orders, to be performed and billed by the physician. This holds regardless of who employs the APP or whether that APP would otherwise be qualified to sign the certification.
An APP can perform and bill other medically necessary visits before and after that initial visit. CMS guidance is explicit that a physician may not delegate the initial visit itself to a non-physician practitioner in the SNF setting, a restriction confirmed in CMS Survey and Certification guidance.
An APP can be fully independent of the facility, eligible under every condition covering certification signatures, and still not be the person who performs or bills that first comprehensive visit. The two rules answer different questions: who may attest to continued need for skilled care, and who may perform the visit that opens the physician’s plan of care.
CMS guidance includes one exception to physician-only performance of the initial visit, but it applies to the nursing facility (NF) setting, not to a Medicare Part A SNF stay. Content that says an NPP can perform the initial visit if not facility-employed, without naming which setting it means, is describing the NF exception, not the SNF rule covered here.
An APP performing and documenting the initial comprehensive visit does not become billable later just because a physician co-signs the note afterward. If the visit itself was required to be physician-performed, a retroactive co-signature does not convert it into a compliant claim.
What Each Certification and Recertification Must Actually Say
An initial certification must state that the resident requires daily skilled nursing or rehabilitation services, that those services can only be provided on an inpatient SNF basis, and that the need is tied to the condition treated during the qualifying hospital stay or to a new condition that arose at your facility. It requires a signature and a date.
A recertification must state the reason continued care is required, the estimated additional time the resident will need to remain in the facility, and any plans for care after discharge. Like the initial certification, it requires a signature and a date.
Neither statement can be satisfied by a routine physician order. CMS requires a separate, distinct statement even when the supporting clinical detail already exists elsewhere in the chart, as long as that statement points clearly to where the required information lives.
The Mistake That Breaks Every Recertification After It
Most facilities build their recertification tracking off the admission date: a form or spreadsheet pre-populated with reminder dates counting forward from Day 1. That works exactly until the first time a physician signs early.
Say a resident is admitted on day 1, and the physician signs the first recertification on day 10 instead of waiting until the deadline on day 14. The 30-day clock for the next recertification now runs from day 10, landing the true due date on day 40, not day 44.
If the tracking sheet was pre-filled with day 44 as the next reminder, the facility is now four days past a valid recertification window before anyone notices.
This isn’t a training gap. It’s a template design problem.
Any tracking system built on fixed calendar math from the admission date will eventually drift the first time a physician signs off-schedule. Physicians signing off-schedule is normal behavior, not an edge case a facility can train away.
A recertification tracker built on the admission date is measuring the wrong clock. It is accurate right up until the first time a physician signs early, and then it is wrong for the rest of the stay.
When a Certification Is Late
Delayed certifications and recertifications are allowed when there has been an isolated oversight or lapse. The delayed document must include everything a timely one would, plus a written explanation for the delay, signed and dated by the physician.
A certification or recertification without a signature and date does not meet CMS’s basic documentation standard. Reviewers treat it as though it does not exist, regardless of how strong the clinical narrative around it is.
Facilities have documented delayed certifications that met every content requirement, only to have a reviewing contractor challenge the claim anyway. In at least one documented case, the denial was upheld through the first level of appeal before eventual resolution.
“Allowed” is not the same as “automatically accepted.” The regulation gives you a documentation standard to meet, it does not guarantee a reviewer won’t push back on it anyway.
This is exactly the kind of gap the Triple Check process is supposed to catch before a claim goes out, not after a reviewer flags it.
Who Owns This in Your Facility
Certification compliance breaks down when no one owns it end to end. The Director of Nursing (DON) typically owns the clinical documentation that supports continued need. The Minimum Data Set (MDS) coordinator must watch for overlap between the assessment cycle and the recertification cycle, since the two run on different clocks.
The business office or billing team should confirm a valid certification is on file before any claim tied to that period is released, the same checkpoint covered in our Medicare Part A eligibility requirements guide.
This same documentation discipline connects directly to the 30-day transfer window and 3-day qualifying hospital stay requirements covered elsewhere in our compliance guide. All three sit on the same admissions-to-billing chain, and a gap in one usually signals a gap in how the others are tracked too.
Our compliance documentation guide covers this exact chain, from qualifying stay through certification through claims submission.
Whoever manages credentialing intake, often the DON or the administrator, owns verifying and documenting an extender’s employment status before that person signs anything. The business office should also confirm which visit type was billed for a new admission, since the initial comprehensive visit and the certification signature follow different rules with different owners.
Who This Is For
LTC Apps is built for you if:
- You operate a skilled nursing facility or small regional SNF group
- You want tighter control over admissions documentation without replacing your clinical system
- You are evaluating modular operations software built for SNFs, not adapted from hospital platforms
This is not the right fit if:
- You are looking for a full clinical EHR with physician-facing charting
- You need software for assisted living only, with no skilled nursing component
- You require an enterprise contract with a dedicated implementation team from day one
What Happens After You Request a Demo
- A member of our team reaches out within one business day to schedule a call
- We run a 30-minute live walkthrough of the modules most relevant to your facility
- You get pricing specific to your facility size and module selection
Most facilities have a clear picture of fit and pricing within one week of reaching out.
Common Questions Before Booking a Demo
No long implementation timelines. Most facilities are live on their first module within 2-4 weeks. No minimum facility size. We work with single-facility operators and regional groups. If you’re mid-contract with another vendor, we can run a parallel evaluation so you’re ready to switch at contract end.
Our Admissions & Patient Intake module tracks document completion per resident and flags when a required document, including a certification, is missing from the file. It won’t calculate your recertification due dates for you, but it will stop a missing certification from disappearing into an incomplete chart unnoticed.
Frequently Asked Questions
At the time of admission, or as soon thereafter as is reasonably practicable. There is no fixed day-number deadline for SNF initial certification.
Every recertification after the first one is due within 30 days of the date the prior recertification was signed, not 30 days from the admission date.
A physician on staff at the SNF with knowledge of the case, or a physician extender (NP, CNS, or PA) who does not have a direct or indirect employment relationship with the facility.
No. If the NP has a direct or indirect employment relationship with the facility, they cannot sign the certification or recertification, regardless of their clinical involvement in the case.
Ask directly whether any portion of their pay, direct or through a staffing or management company, comes from the facility for their time at your SNF. Document that answer, the date it was confirmed, and who confirmed it in the credentialing file before they sign anything.
No. CMS requires that visit, which establishes the physician’s plan of care and admitting orders, to be performed and billed by the physician regardless of the APP’s employment status. This is a separate rule from the certification signature requirement.
The delayed certification must include everything a timely one requires, plus a written, signed, and dated explanation for the delay.
No. The 12th-day deadline applies to general hospital inpatient certification. SNF initial certification has no fixed day-number deadline; it is due at admission or as soon as reasonably practicable.
If you operate a skilled nursing facility and want tighter control over the documentation that keeps your admissions revenue intact, LTC Apps was built for exactly this.
