Temporary and Emergency Privileges: The Four Joint Commission Pathways

Hospitals use “temporary privileges” and “emergency privileges” loosely, but Joint Commission-accredited hospitals actually operate under four distinct pathways, each triggered by a different situation, each governed by a different standard (or, for one of the four, no numbered standard at all), and each carrying different verification and documentation requirements. Confusing one for another is a common source of survey findings — and, per the National Practitioner Data Bank, an adverse action taken against any of the four is reportable exactly as if it had been taken against a standard privilege. This guide covers all four side by side. For the routine, non-urgent credentialing and privileging process each pathway is a shortcut around, see CASRAI’s credentialing and privileging process guide.

The three pathways, at a glance

Joint Commission-accredited hospitals recognize temporary privileges under two separate Medical Staff (MS) chapter standards, plus a bylaws-based emergency provision, plus a fourth, separately-chaptered disaster pathway:

• New-applicant temporary privileges (commonly cited to MS.06.01.09) — bridges a clean, complete application while the credentials committee, medical executive committee, and governing body finish the full review, capped at a maximum duration commonly cited as 120 consecutive days.
• Important-patient-care-need temporary privileges (commonly cited to MS.06.01.13) — covers a documented care gap: locum tenens coverage, a volume surge the current privileged roster can’t meet, or a single-patient need — granted after verifying current licensure and competence, without waiting for full primary source verification (PSV) on every element.
• Emergency privileges — a bylaws-based provision, not tied to a specific numbered standard, that lets any medical staff member with clinical privileges provide whatever care is necessary as a life-saving measure or to prevent serious harm, regardless of their specific privilege scope, as long as it stays within their license.
• Disaster privileges (Emergency Management chapter, commonly cited to EM.02.02.13 and EM.02.02.15) — a different population entirely: volunteer licensed independent practitioners (and, under a separate provision, other volunteer practitioners) brought in once the hospital’s Emergency Operations Plan (EOP) has been formally activated.

A sourcing note, in the interest of accuracy: jointcommission.org blocks automated access, so the specific standard numbers above are corroborated across multiple independent secondary sources (credentialing consultancies, NAMSS-affiliated guidance, health-law counsel) rather than fetched directly from a Joint Commission primary source this session. Verify the current Element of Performance text directly against your hospital’s own Joint Commission e-dition subscription before citing a number in a survey response or bylaws revision.

Pathway 1: temporary privileges while a new applicant’s file is still pending

This is the pathway for a practitioner who has submitted a complete, apparently-clean application — no gaps, no red flags on the pieces verified so far — but whose full credentials-committee review, medical executive committee recommendation, and governing body approval haven’t finished yet. It exists so a hospital doesn’t have to choose between rushing the full review or leaving a needed practitioner unable to work while paperwork catches up.

What distinguishes it from a shortcut: the hospital still verifies the load-bearing elements before granting — current licensure, no active exclusion or sanction, no unexplained adverse action — it just doesn’t wait for every remaining PSV element to close out first. The duration is commonly cited as capped at 120 consecutive days; if the full file still hasn’t closed by then, the hospital has to either finish the review or let the temporary privileges lapse, not extend them indefinitely as a substitute for finishing the process.

Pathway 2: temporary privileges for an important patient care need

This pathway doesn’t require a pending application at all — it addresses an active care gap. Typical triggers: a locum tenens practitioner covering a scheduled absence, a volume surge that outpaces the current privileged roster, or a specific patient whose care requires a practitioner not otherwise privileged at the hospital. The Joint Commission’s Element of Performance for this pathway is commonly described as requiring two things: verification of the practitioner’s current licensure and current competence, and documentation of the specific patient care need that justifies granting the privilege — not just a general statement that coverage was short.

That second requirement is where surveys most often find gaps. A file that shows “temporary privileges granted, locum tenens” without a documented, dated statement of the actual care need being addressed doesn’t satisfy the standard even if the verification itself was done correctly.

Pathway 3: true clinical emergencies

This is the pathway most people mean when they say “emergency privileges” in conversation, and it’s the one least tied to a specific numbered standard — it’s typically written into a hospital’s own medical staff bylaws rather than imposed as a standalone Joint Commission requirement with its own EP number. The substance is consistent across hospitals that have it: any member of the medical staff who already holds clinical privileges may provide whatever care, treatment, or service is necessary as a life-saving measure, or to prevent serious harm to a patient, regardless of whether that specific service falls within their currently-granted privileges — provided it stays within the scope of their license.

This is deliberately narrow. It is not a general license to practice outside one’s specialty; it’s a bounded exception for the moment a patient will suffer serious harm before any privileging process — even an expedited one — could run. Once the immediate emergency passes, ongoing care of that patient reverts to a properly privileged practitioner.

Pathway 4: disaster privileges under an activated Emergency Operations Plan

Disaster privileges live in a different chapter of the Joint Commission standards — Emergency Management, not Medical Staff — because they solve a different problem: bringing in practitioners who are not already members of the medical staff at all. This pathway only exists once a hospital has formally activated its Emergency Operations Plan in response to a genuine disaster (a mass casualty event, a natural disaster, a facility-disabling incident). It applies to volunteer licensed independent practitioners, and — under a related provision — potentially to other volunteer practitioners as well, subject to the hospital’s own EOP and oversight protocol for that population.

Because these are practitioners entirely new to the hospital, verification here is necessarily lighter at the point of granting than any of the other three pathways — a hospital can’t run full PSV on a volunteer walking in during an active disaster — but that’s exactly why oversight during the disaster period (direct supervision, a defined scope, and post-event review) matters more, not less, for this population. See CASRAI’s CMS Conditions of Participation guide for how the Emergency Preparedness Condition of Participation interacts with medical staff standards during an activated disaster response.

What verification is actually required, across all four pathways

The floor doesn’t disappear just because a pathway is faster than the routine process. At minimum, every pathway above requires confirming:

• Current, unrestricted licensure in the relevant jurisdiction
• No active exclusion from federal healthcare programs and no unexplained adverse licensure or privileging action
• A National Practitioner Data Bank (NPDB) query
• For pathways 1 and 2 specifically: documented current competence for the privileges being granted

What’s genuinely skipped or deferred, and what isn’t, differs by pathway — pathway 1 defers the remaining PSV elements to the full review still in progress; pathway 2 requires documenting the specific care need in addition to the verification above; pathway 3 requires no separate verification step at the moment of the emergency because it relies on privileges the practitioner already holds; pathway 4 is the only one where even licensure verification may be abbreviated at the point of entry, contingent on the hospital’s own EOP.

NPDB reporting treats all four the same way

One point hospitals sometimes get wrong: assuming a lighter verification process means a lighter reporting obligation if something goes wrong. It doesn’t. Per the NPDB Guidebook, “no distinction is made between temporary clinical privileges (including but not limited to emergency and disaster clinical privileges) and clinical privileges” for reporting purposes — an adverse action taken against a practitioner holding any of these four privilege types is reportable exactly as it would be against a standard, fully-processed privilege. The one narrow exception: if temporary privileges simply expire on schedule with no renewal decision made (because, for example, the underlying application was still pending), that expiration by itself is not a reportable nonrenewal or surrender — there was no renewal decision to report. See CASRAI’s NPDB reporting requirements for hospitals guide for the full reporting mechanics.

Who can grant these privileges, and how the file gets closed out

Bylaws typically designate a specific authority for the faster pathways rather than routing them through the full credentials-committee cycle — commonly the chief executive officer, the chief of staff or medical staff president, or a designee, acting on a recommendation captured in the file. That authorization, along with the documented justification (the care need for pathway 2, the activated EOP for pathway 4), belongs in the practitioner’s credentialing file regardless of how quickly it was granted — a survey reviewing a temporary-privileges file expects to see the same paper trail logic as a standard file, compressed in time but not skipped in substance.

Closing out: pathway 1 resolves when the full credentialing file completes (converting to standard privileges) or the 120-day window lapses. Pathway 2 resolves when the documented care need ends. Pathway 3 resolves the moment the immediate emergency passes. Pathway 4 resolves when the EOP is deactivated, at which point volunteer practitioners’ privileges under that provision end unless they separately pursue standard credentialing. Any privilege granted under any of these four pathways still triggers Focused Professional Practice Evaluation (FPPE) the moment it converts to an ongoing privilege — see CASRAI’s OPPE vs. FPPE comparison for how that evaluation period works.

Where hospitals get this wrong

Recurring survey and risk-management findings across these four pathways: granting pathway-2 temporary privileges without a documented, specific care need in the file (a blanket “coverage need” statement instead of a dated, particular justification); treating pathway-3 emergency privileges as though they require no documentation at all, when the hospital’s own bylaws still typically require a post-hoc note describing what care was provided and why; letting pathway-1 temporary privileges run past the 120-day cap without either finishing the file or formally lapsing them; and failing to distinguish pathway 4’s volunteer population from the hospital’s existing medical staff in the disaster-response org chart, which creates confusion about who is actually accountable for a volunteer’s care during the event. Each of these shows up in accreditation survey findings as a medical-staff-standards gap even when the underlying care itself was appropriate — the standard is being surveyed on documentation and process discipline, not just clinical judgment. See CASRAI’s medical staff bylaws requirements guide for how these provisions should actually be written into bylaws in the first place, and the delineation of privileges forms guide for how the specific privileges being granted, temporarily or otherwise, get documented on the form itself.

Frequently asked questions

Is “emergency privileges” the same thing as “temporary privileges”?

No. Temporary privileges (pathways 1 and 2 above) are a faster version of the ordinary privileging process, granted in advance of a specific, anticipated need. Emergency privileges (pathway 3) require no advance grant at all — they activate automatically, under a bylaws provision, the moment a life-threatening or serious-harm situation exists and no otherwise-privileged practitioner is available.

Do temporary privileges skip primary source verification entirely?

No. They defer some elements, not all of them. Current licensure, competence, exclusion status, and an NPDB query still get verified before granting; it’s the remaining, slower-to-complete PSV elements (education/training verification through primary sources, board certification confirmation, malpractice history) that get deferred to the full review still in progress.

How long can temporary privileges last?

For the new-applicant pathway, the duration is commonly cited as capped at 120 consecutive days. For the important-patient-care-need pathway, duration is tied to the documented need itself rather than a fixed calendar cap — it should end when the need that justified it ends. Confirm both figures against your own hospital’s current bylaws and Joint Commission e-dition subscription, since exact cited durations can be revised.

Who can be granted disaster privileges?

Volunteer licensed independent practitioners, once the hospital’s Emergency Operations Plan is formally activated — and, under a related provision, other categories of volunteer practitioner, subject to the hospital’s own EOP and oversight protocol. This is a distinct population from the hospital’s existing, already-privileged medical staff.

Does an adverse action against a temporary or emergency privilege have to be reported to the NPDB?

Yes, on the same basis as a standard privilege — the NPDB Guidebook makes no distinction between temporary, emergency, disaster, and standard clinical privileges for reporting purposes. The narrow exception is a temporary privilege simply expiring with no renewal decision made, which is not itself reportable.

Does granting emergency privileges require board approval first?

No — that’s the point of the pathway. It’s designed to activate without a prior committee or board decision, because the situation it addresses (imminent serious harm) can’t wait for one. What typically is required, per most bylaws, is contemporaneous or after-the-fact documentation of what care was provided and why, so the file reflects what happened even though no advance approval occurred.