From the ACEP 2026 Scientific Assembly: ED Boarding Is a Flow Problem

In brief: ED boarding has two operational delays: no bed or destination is available, or a patient is still waiting for a specialist perspective after the next step has otherwise become possible. ConsultBridge cannot create inpatient or psychiatric capacity. It can help health systems keep the specialty-access lane moving with a documented question, response target, recommendation, and next action.

Part of the “From the ACEP 2026 Scientific Assembly” FabrixMed Insights series.

Boarding is the flow problem. Boarded patients are the people experiencing the hold. Improving flow starts by identifying what stopped it.

If no appropriate inpatient, psychiatric, or transfer bed is available, the constraint is capacity. If the patient has a bed or disposition path but is waiting for a clinical question to be answered, the constraint may be specialty access. Those delays can overlap, but they require different interventions.

That distinction is where FabrixMed can help. ConsultBridge routes a defined clinical question, relevant evidence, and care context to the appropriate specialist, then preserves the recommendation and next action in a documented handoff. It does not promise to solve every boarding hour. It gives the organization a way to reduce avoidable waiting when the delay is unanswered specialist input.

For a companion ACEP26 article on the continuity gap behind repeated ED use, see The ED Can’t Close the Continuity Gap Alone.

What kind of boarding delay is the ED trying to solve?

The American College of Emergency Physicians describes boarding as patients remaining in the ED while waiting for an inpatient bed or transfer destination, with delays that can last hours, days, or longer. The operational question is what is holding the patient at that moment:

• Capacity delay: No appropriate inpatient, psychiatric, or transfer bed is available. A consultation platform cannot create capacity that does not exist.
• Specialty-access delay: The next step is slowed because a specialist has not reviewed the case, answered a defined question, or documented a recommendation for the treating or admitting team.

The first delay calls for a hospital-flow, staffing, placement, or capacity response. The second can be measured as time from a complete clinical question to specialist review, recommendation, and next action. A credible program keeps those lanes separate instead of calling every delay a consult problem.

Where can specialty access change the flow?

Not every boarded patient needs ConsultBridge. The relevant patients are those for whom a defined clinical question is delaying disposition, transfer, treatment planning, or handoff.

1. Support safe treat-or-transfer decisions when clinically appropriate

Some patients are transferred because the local team cannot obtain timely specialty input, even when the patient may be safely managed locally. A documented specialist review can support a treat-locally plan when the specialist and treating team determine that local care is appropriate.

That does not mean every transfer is avoidable. It does not replace transfer agreements, bedside assessment, emergency stabilization, or the receiving facility’s acceptance process. It gives the organization a way to examine how often lack of specialty access—not clinical necessity—contributes to escalation.

2. Reduce waiting for a disposition-relevant opinion

An emergency physician may know that a patient needs a specialist’s judgment but still wait for a callback, an available consultant, or the next morning’s coverage. A structured ConsultBridge request gives the specialist the clinical question and supporting information in one workflow.

The goal is not to force a discharge or admission decision. It is to help the treating clinician make the appropriate decision with the specialist input the case requires.

3. Extend specialist coverage across ED locations

A health system may already employ or contract with specialists. The challenge is that those specialists may not be consistently reachable across every ED, microhospital, rural site, or overnight period.

ConsultBridge can serve as a shared workflow fabric across locations when the organization configures the participants, coverage rules, credentials, response expectations, escalation paths, and documentation requirements. The model may use internal specialists, contracted groups, FabrixMed-connected providers, or a hybrid arrangement.

4. Make the handoff easier to act on

When a patient moves from the ED to an inpatient team, the receiving clinicians need more than a verbal statement that “specialty was consulted.” They need the question asked, the relevant evidence, the specialist’s recommendation, the limits of that recommendation, and the next action owned by a named team.

A structured, timestamped consult record can make that handoff more complete and easier to audit. It does not eliminate the receiving team’s responsibility to evaluate the patient. It reduces the ambiguity that causes work to restart after the patient has already moved.

5. Reduce the overnight restart

Some decisions stall because the next available specialist review begins in the morning. A configured overnight coverage pathway can help an organization determine whether a complete clinical question can be reviewed outside local office hours, with the response target, escalation path, and clinical responsibility defined in advance.

The point is not to promise that every overnight case can be handled asynchronously. It is to avoid restarting the specialty-access process at 7 a.m. when the question could have been routed earlier and the appropriate coverage was available.

Can behavioral-health consultation reduce ED boarding?

Behavioral-health patients can experience prolonged ED stays while waiting for psychiatric evaluation, placement, or an appropriate level of care. Psychiatry access is therefore an important example of where a defined remote consultation workflow may help.

ConsultBridge could support a configured behavioral-health pathway by routing the clinical question and documented safety information to an appropriately credentialed psychiatric provider for the type of review the organization has designed. Depending on the patient’s condition, local law, hospital policy, and clinical coverage model, that may involve synchronous evaluation, asynchronous review, or escalation to in-person care.

The boundary is essential: a remote consultation does not by itself determine that a patient is safe for discharge, satisfy every legal or regulatory requirement, create a psychiatric bed, or replace emergency assessment and suicide-risk safeguards. The hospital remains responsible for its clinical governance, staffing, policies, and disposition decisions.

How should an ED measure specialty-access delay?

FabrixMed’s existing ophthalmology workflow is a useful design reference: service-level access works best when the question, required evidence, qualified coverage, response target, escalation rules, and documentation requirements are defined before the lane is launched. The same principle can be tested in other ED specialties without claiming that every lane works the same way.

For an ED program, useful measures may include:

• time from complete consult request to specialist review;
• time from specialist review to documented next action;
• consults completed overnight or outside local coverage hours;
• transfers where specialty input supported local treatment;
• disposition changes after specialist review;
• boarding hours associated with a pending specialty decision; and
• completeness of the consult and handoff record.

The results will vary by specialty, acuity, coverage, staffing, and bed availability. The first deployment should make the difference visible: which delays were caused by capacity, and which were caused by unanswered clinical questions?

For a health system evaluating this model, the next step is not to assume that every boarded patient needs ConsultBridge. It is to select one specialty lane, review its current wait pattern, define the coverage and response model, and measure what changes.

What can ConsultBridge not solve about boarding?

ConsultBridge is not an inpatient bed-management system and it does not solve hospital-wide capacity constraints. It cannot create a psychiatric bed, replace an admitting service, guarantee a transfer destination, or make a clinical decision autonomously.

Its role is narrower and practical: help a qualified treating clinician route a defined clinical question to the right specialist, receive appropriate input through a configured workflow, document the recommendation, and carry the next action forward.

That may not end boarding. But when the delay is waiting for specialty input, it can help the organization stop adding avoidable uncertainty to an already crowded system.

Sources and further reading

• AHRQ: Summit to Address Emergency Department Boarding
• ACEP: Emergency Department Boarding and Crowding
• ACEP: Emergency Department Boarding statement

FabrixMed and ConsultBridge support clinical workflows; they do not replace emergency evaluation, bedside care, hospital policy, specialist judgment, transfer agreements, or local legal and regulatory requirements.