FSED EMTALA Transfers:
A Practical Guide to Best Practice

Back to Insights

Freestanding emergency departments have become an increasingly common part of hospital system architecture, and with them come important EMTALA questions that are frequently misunderstood in practice. When does a patient movement from an FSED constitute an EMTALA transfer, and when does it not? What obligations attach before any movement occurs? And can you transfer a patient to another hospital if your system has the capability to treat the patient at the main campus? Not knowing the answers to these questions creates real compliance exposure.

First, the MSE: Before Anything Else

Regardless of where a patient is going, the main campus, a different hospital, or home, an appropriate Medical Screening Examination must be performed at the FSED before any movement occurs. This obligation is triggered the moment a patient presents requesting examination or treatment of a medical condition. It cannot be deferred, and it cannot be satisfied by routing the patient elsewhere. The MSE must be completed (within the facility's capabilities) and documented at the point of presentation.

The primary sources of EMTALA violations at FSEDs are failure to perform an appropriate MSE and failure to provide stabilizing treatment within the hospital's capabilities. Often, in a rush to get the patient elsewhere, critical aspects of MSE or stabilization are overlooked or deferred. While the FSED and main campus may technically be one hospital under a shared CCN, meaning the MSE and stabilization obligations could in principle be fulfilled at the main campus, any delay in performing them while arranging transport would itself constitute an EMTALA violation. The practical and safe approach is therefore to perform the MSE and provide stabilizing treatment within the FSED's capabilities before any movement occurs. For a true EMTALA transfer to a different hospital, this is not merely best practice, it is required: the MSE must be completed and stabilizing treatment within the hospital's capability provided before the transfer takes place.

Movement to the Main Campus: Transport, Not Transfer

When a provider-based FSED (a freestanding emergency department formally designated as a department of its parent hospital under Medicare rules) shares a Medicare provider number (CCN) with its associated main hospital, moving a patient from the FSED to the main campus is not an EMTALA transfer. It is an intra-hospital transport, movement between departments of the same hospital, and the formal EMTALA transfer requirements do not apply.¹ No physician certification. No risk/benefit documentation. No receiving-hospital acceptance. No EMTALA transfer form.

The regulatory basis is the statutory definition of "transfer" under EMTALA:² "the movement of an individual outside a hospital's facilities." When the FSED and main campus share a CCN, both are facilities of the same hospital. CMS has made this explicit in its interpretive guidance:³ "Movement of the individual to the main campus of the hospital is not considered a transfer since the individual is simply being moved from one department of a hospital to another department or facility of the same hospital."

The analysis turns on two requirements that must both be satisfied: the FSED must share the same Medicare provider agreement and CMS Certification Number (CCN) as the main hospital, and it must have valid provider-based status under federal provider-based rules.⁴ CCN alone is not sufficient, and shared state licensure or corporate ownership is not dispositive. Provider-based status is a formal Medicare designation that recognizes an off-campus facility as a department of its parent hospital rather than a separate, independently operating entity. A facility with provider-based status bills under the main hospital's Medicare provider number, is subject to the hospital's conditions of participation, and is surveyed as part of the hospital. Obtaining and maintaining that status requires, among other things, clinical integration with the main hospital, unified governance and control, shared medical records, financial integration, and consistent public identification as part of the main provider, not as a freestanding independent facility. If either requirement is absent, the sites are separate hospitals for EMTALA purposes, and any patient movement between them is a full EMTALA transfer. Verify both the CCN relationship and current provider-based status explicitly, and revisit whenever the facility undergoes acquisition, restructuring, or changes in billing arrangement.

The Default Path and When External Transfer Is Permitted

In practice, when a patient at an FSED requires resources beyond what the FSED can provide, the expected and appropriate course is transport to the main campus. Because the FSED and main campus are one hospital, the main campus's capability counts as the FSED's capability. If the main campus can stabilize the patient, the FSED can stabilize the patient, and the obligation is to do so. Transporting the patient to the main campus in that scenario is not an EMTALA transfer, and it is the right call.

CMS does note, however,³ that there is no requirement that the patient always be routed back through the main campus, and a direct EMTALA-compliant transfer from the FSED to an unaffiliated hospital is permissible in appropriate circumstances. The circumstances are specific: the unaffiliated hospital must be the more medically appropriate destination, for example because it has specialty capabilities the main campus lacks for the specific condition or because the patient requests to go elsewhere. In those situations, a proper EMTALA transfer meeting all applicable transfer criteria is permitted.¹

The critical point is what this carve-out does not permit. If the main campus has the capability and capacity to stabilize the patient and there is no genuine clinical reason favoring the unaffiliated hospital, transferring the patient there would likely be an EMTALA violation. The benefits-exceed-risks test that governs EMTALA transfers must reflect clinical judgment, not payer status, bed management, or administrative preference. The existence of main-campus capability and capacity does not make all outside transfers unlawful, but it does mean any outside transfer must be justified on clinical grounds, and documented as such.

This has direct enforcement consequences. CMS has instructed surveyors⁵ investigating EMTALA complaints involving an off-campus ED to consider the capability and capacity of the main campus, not just the off-campus site in isolation. A hospital cannot defend an outside transfer by presenting only what the FSED could do. If the main campus could have stabilized the patient, CMS will evaluate the transfer decision against that full capability. Any claim that the hospital could not stabilize must account for what the hospital as a whole, including the main campus, was able to provide at the time.

When a patient with an unstabilized emergency medical condition is moved from the FSED to a different hospital with a different CCN, that movement is a full EMTALA transfer regardless of the clinical justification, and all transfer requirements apply.¹ A patient whose EMC has been stabilized is no longer subject to EMTALA's transfer framework; once stabilized, further movement is governed by ordinary standards of care and discharge planning rather than EMTALA.

Best Practice Recommendations

The regulatory framework is clear, but operational compliance at FSEDs requires deliberate policy and training attention across all three scenarios:

Always perform and document the MSE first. No patient movement, to the main campus, to another hospital, or otherwise, should occur without a completed and documented MSE.

Begin stabilization within the FSED's capabilities concurrently with any transport arrangements. Arranging transport to the main campus does not suspend the obligation to stabilize. If a patient is hemorrhaging, initiating whatever blood products and resuscitative measures the FSED has available is required even as transport is being arranged. The FSED's stabilization obligation runs in parallel with logistics, not after them. Waiting until the patient reaches the main campus to begin stabilization when the FSED has the means to act is not acceptable under EMTALA.

Confirm both your CCN relationship and provider-based status, and review them periodically. The intra-hospital transport rule requires both a shared Medicare provider agreement and CCN, and valid provider-based status under federal provider-based rules.⁴ Neither alone is sufficient. Acquisitions, restructurings, and billing changes can alter either without triggering an obvious operational flag.

Document intra-hospital transport correctly and ensure continued care throughout. Movement to the main campus should be documented as intra-hospital transport, not as a discharge. An unstabilized patient being moved to the main campus remains under the hospital's care throughout that movement and must be monitored accordingly. While EMTALA's formal transfer form is not legally required, consider standardizing this process as it enforces good habits and protects the hospital if the CCN or provider-based status is ever called into question.

Account for state-specific requirements. Several states, notably Texas, Colorado, and Ohio, have FSED-specific statutes that may impose documentation or notification obligations beyond federal EMTALA requirements. Ensure your FSED policies address both layers.

The EMTALA framework governing FSED transfers is coherent once the key distinctions are internalized. Transport to the main campus within a shared CCN and valid provider-based status is not a transfer. The default and expected path when the patient needs more than the FSED can provide is the main campus. External transfer to an unaffiliated hospital requires a genuine clinical justification and full §489.24(e) compliance. And the MSE and stabilization within the hospital's capabilities are the prerequisites to all of it.

Getting these distinctions right is what allows your FSED to serve patients well while operating with regulatory confidence. Getting them wrong, in any direction, creates the conditions for an EMTALA violation.