The Emergency Department sits at the intersection of three regulatory regimes that most other hospital departments touch only lightly: the FGI Guidelines that govern how the space is designed and built, EMTALA — the federal statute that uniquely obligates the ED to screen and stabilize everyone who arrives — and the trauma-center designation standards that, when pursued, layer a verification overlay on top of both. Understanding how these three regimes interlock, where they conflict, and which authority enforces each is the single most important compliance task in any ED project, because a design that satisfies the building code can still fail EMTALA, and a trauma application can be denied for facilities that are otherwise fully licensed and accredited.

The three regulatory regimes and how they differ

These three frameworks operate on different objects, are enforced by different bodies, and bite at different points in the project. Conflating them is the most common source of late-stage rework.

The practical consequence: a project can be code-compliant and accreditation-ready and still carry EMTALA exposure (e.g., a poorly located triage point, no signage) or fail a trauma site review (e.g., resuscitation room undersized, imaging not immediately adjacent). The design team must treat all three as parallel acceptance criteria, not as a single "code" box to check.

FGI Guidelines — the design-and-construction baseline

The FGI Guidelines for Design and Construction of Hospitals (published by the Facility Guidelines Institute, updated on a roughly four-year cycle) is the foundational design code for the ED in most U.S. jurisdictions. Critically, FGI is not self-enforcing — it has legal force only where a state adopts it by reference into its licensing regulations or building code. The edition that applies is the one your state has adopted, which often lags the most current FGI edition by one or two cycles. Confirming the adopted edition with the Authority Having Jurisdiction (AHJ) at project start is non-negotiable; designing to a newer edition than the state adopted can introduce requirements the AHJ will not credit, while designing to an older one risks a deficiency at survey.

FGI sets the ED-specific minimums and references the engineering standards that govern systems:

• ASHRAE 170 (Ventilation of Health Care Facilities) — incorporated by FGI; governs air-change rates, pressurization relationships, filtration, and temperature/humidity for ED spaces including treatment rooms, triage, waiting, decontamination, and airborne-infection isolation. (Detailed application is covered in the sibling HVAC and pressurization article.)
• NFPA 99 (Health Care Facilities Code) — risk-based requirements for medical gas/vacuum systems, electrical systems, and the gas/electrical risk categories that the ED's high-acuity spaces fall into.
• NFPA 101 (Life Safety Code) and NFPA 110 (emergency/standby power) — egress, occupancy separation, and the essential electrical system / generator requirements that keep the ED powered through an outage.
• NEC / NFPA 70 Article 517 — health-care electrical wiring, including patient-care space classification and the wet-procedure-location and redundant-grounding rules.

FGI also sets functional-program and room-level requirements specific to the ED: minimum clear floor areas and clearances for treatment bays and resuscitation rooms, the requirement for an accessible and observable triage/intake position, provisions for behavioral-health-safe and secure holding spaces, decontamination capability, and a public entrance that is open and accessible 24/7 with a clearly identified path from the public way. Many of these requirements exist precisely to make EMTALA compliance physically possible — the codes are coordinated by design.

EMTALA — the obligation that shapes the front door

The Emergency Medical Treatment and Labor Act (EMTALA), enforced through the CMS Conditions of Participation, is unique among healthcare regulations in that it imposes an affirmative operational duty rather than a building requirement — but that duty has direct, non-negotiable design implications for the ED. Any Medicare-participating hospital with a dedicated emergency department must provide a Medical Screening Examination (MSE) to anyone who "comes to the emergency department" requesting examination or treatment, and must stabilize any emergency medical condition (or appropriately transfer) regardless of ability to pay, insurance status, or citizenship.

The phrase "comes to the emergency department" is interpreted broadly by CMS, and this is where design and EMTALA collide:

• The 250-yard rule (hospital campus). EMTALA obligations extend to the entire hospital campus, generally interpreted to include areas within 250 yards of the main buildings. A patient who collapses in the parking structure, on the ambulance apron, in a connected medical office building lobby, or at a campus bus stop may trigger EMTALA. Site planning, wayfinding, and the location of the ED entrance relative to parking and drop-off all interact with this radius.
• No financial discussion before the MSE. Registration and any insurance or payment inquiry must not delay or appear to condition the screening exam. This shapes the sequencing of triage, registration, and treatment in the front-end design — triage and the MSE must be reachable without passing through a billing gate, and many EDs deliberately separate quick-look triage from full registration for exactly this reason.
• Signage. CMS requires conspicuously posted signage informing patients of their EMTALA rights (the right to a screening exam and stabilizing treatment regardless of ability to pay) in the dedicated ED, including waiting and treatment areas, in language(s) appropriate to the community served. This is a literal design deliverable — sign locations and content belong in the documents.
• Central log. The ED must maintain a central log of every individual who comes to the department, what was done, and the disposition. This is operational but drives IT/registration workstation placement and the intake workflow.