If an ICE officer walked into your facility tomorrow, would your staff know what to do?


That is not a political question. It is an operational and compliance question. And the time to figure out the answer is not when an ICE officer is standing in your lobby.
What Changed?
For many years, hospitals and other healthcare facilities benefited from federal policies that generally discouraged immigration enforcement activities in or near locations where people receive healthcare.
That changed in January 2025, when the Department of Homeland Security rescinded its previous protected-areas guidance and moved toward a more discretionary approach to enforcement activity in healthcare settings.
What is important from a compliance perspective is what didn't change.
The policy change did not eliminate constitutional protections governing access to private property. It did not eliminate HIPAA or other privacy protections. And it did not change hospitals' obligations under EMTALA. What changed was the environment in which healthcare organizations may need to apply those requirements.
That creates a preparedness issue for compliance departments.
The Front Desk Is Probably Where Your Policy Will Be Tested
Imagine the following scenario.
An ICE officer walks into the reception area of a healthcare facility and asks whether a particular individual is receiving treatment there. What happens next?
Does the receptionist answer the question?
Call security?
Call the Privacy Officer?
Ask to see a warrant?
Allow the officer to walk further into the facility?
Tell the officer to leave?
The problem is that several different compliance issues have suddenly converged at the front desk, and the person being asked to manage them may have little or no training on any of them.
Healthcare organizations should not expect front-line employees to become experts in immigration law, HIPAA or warrant requirements. They should expect employees to know when to stop and escalate.
Public and Nonpublic Areas Matter
ICE officers generally may enter areas that are open to the public, such as lobbies, reception areas and public waiting rooms. Access to nonpublic areas such as treatment rooms, nursing stations, staff-only areas and medical records departments is a different matter and generally requires appropriate legal authority, consent or another recognized exception.
That distinction sounds straightforward until you try applying it to an actual facility.
Is the hallway beyond reception public?
What about registration?
A patient intake area?
An administrative office?
The entrance to a clinical suite?
Organizations should consider identifying those boundaries before they matter and making sure the employees responsible for managing facility access understand them.
A Document Labeled "Warrant" Doesn't End the Analysis
Another potential problem is what happens when an officer presents documentation.
Most healthcare employees are not going to know the difference between an administrative immigration warrant, judicial arrest warrant, judicial search warrant, subpoena or court order. Nor should they be expected to make that legal determination themselves.
But the distinction matters.
An administrative immigration warrant issued by DHS may authorize the arrest of an individual but generally does not, by itself, authorize officers to enter nonpublic areas of private property without consent.
The compliance solution isn't to teach receptionists how to interpret warrants. It's to teach them not to interpret warrants.
Organizations should establish a clear process identifying who reviews warrants and other legal requests and how that person is contacted. Depending upon the organization, that may involve legal counsel, compliance, privacy, security or some combination of those functions. Front-line employees need to know enough to recognize the issue and activate that process.
Don't Forget HIPAA
The same principle applies when law enforcement asks for patient information.
There can be a tendency to think about HIPAA in absolutes:
"We can't give information to law enforcement because of HIPAA."
Or, conversely:
"It's law enforcement, so we have to give them the information."
Neither is a particularly good compliance policy.
HIPAA permits certain disclosures to law enforcement under specified circumstances.
Whether information can or must be disclosed depends upon the nature of the request and the applicable legal authority.
Before information is released, the organization may need to determine whether disclosure is required or permitted, verify the requesting official's authority, determine whether the minimum necessary standard applies and consider whether another law imposes additional restrictions.
And HIPAA may only be the beginning of the analysis. Depending upon the patient and the information involved, additional protections may apply to substance use disorder records, mental health information, HIV-related information, reproductive healthcare information and other categories of sensitive health information.
Again, this isn't a decision that should be made by whichever employee happens to receive the request.
Patient Care Still Comes First
Hospitals also need to remember that immigration enforcement does not suspend EMTALA. A patient's immigration status does not change a hospital's obligation to provide an appropriate medical screening examination or, where required, stabilizing treatment or an appropriate transfer.
That means an immigration enforcement response plan cannot focus exclusively on security, access and privacy. It also needs to address continuity of patient care.
If enforcement activity occurs while a patient is undergoing evaluation or treatment, clinical leadership needs to be part of the response process.
Seven Things Compliance Can Do Now
You don't necessarily need a 30-page immigration enforcement policy.
You do need a workable process. Here are seven practical steps healthcare organizations can consider:
1. Decide who owns the response.
Identify who should be contacted when immigration enforcement personnel arrive or request information. Depending on the organization, that may include compliance, privacy, legal counsel, security, clinical leadership and executive leadership.
2. Create a simple escalation protocol.
Give front-line employees straightforward instructions. Who do they call? What information should they collect? What should they avoid doing until the request has been reviewed?
3. Identify public and nonpublic areas.
Review the physical layout of the facility and determine where public access ends. Make sure reception and security personnel understand those boundaries.
4. Establish a process for reviewing warrants and other legal documents.
Determine who is authorized to evaluate administrative warrants, judicial warrants, subpoenas, court orders and other requests. Employees receiving those documents should know where to send them rather than attempting to determine their validity themselves.
5. Build privacy review into the process.
Requests for patient information should be routed through the organization's existing privacy and legal processes. The analysis should consider HIPAA as well as other federal and state confidentiality requirements that may apply.
6. Train the people most likely to encounter the situation.
A short, role-specific training for reception, registration, security, health information management, nursing leadership, privacy and compliance may be considerably more useful than another organization-wide policy employees are unlikely to remember.
7. Test the process.
Run a tabletop exercise.
For example:
An ICE officer enters your reception area at 10:15 Tuesday morning and asks whether John Smith is currently a patient. The officer then produces a document and asks to enter the clinical area.
Now walk through what happens.
Who speaks to the officer?
Who reviews the document?
Who contacts legal counsel?
Who determines whether information can be disclosed?
Who communicates with the clinical team?
Who documents the encounter?
And what happens if the designated Privacy Officer happens to be out of the office that day?
A tabletop exercise has a way of identifying gaps that look perfectly fine on paper.
This Is What Compliance Preparedness Looks Like
Healthcare organizations cannot anticipate every situation their employees will encounter. They can build systems that help employees respond appropriately when something unexpected happens. Immigration enforcement is a good example.
Your receptionist does not need to understand immigration law. Your security officer does not need to become a HIPAA expert. Your nurse does not need to determine whether an administrative warrant authorizes entry into a treatment area.
They need to know their role, understand the boundaries of their authority and know when and to whom to escalate.
This blog was informed by the American Health Law Association article, “ICE Enforcement in Health Care Settings: Legal and Operational Considerations.” The original article provides a more detailed discussion of the underlying legal authorities, litigation and state-law developments.


Comments