PHP Referral for Emergency Department Discharge Teams

Approved by Clinical Staff

For emergency department discharge teams, a PHP referral begins with verifying that the requested program is within MVBH’s outpatient scope. The referral process should also confirm location, contact arrangements, privacy permissions, continuity needs, and a safe transition plan before information is exchanged or a next step is selected.

Start with the verified PHP service scope

Use professional referral resources to frame the handoff, then consult MVBH admissions for the receiving pathway. PHP appears within MVBH’s verified outpatient scope, but the scope statement alone does not establish access, acceptance, coverage, or individual fit.

MVBH’s verified scope includes PHP, IOP, OP, Virtual IOP, and Dual Diagnosis. For this route, PHP should therefore be treated as one named program option within a broader outpatient scope. The scope statement does not describe schedules, entry criteria, capacity, payment, or results.

A useful first step is to state the requested program clearly. The discharge team can then confirm service scope and location through the referral process. This avoids treating a general outpatient inquiry as a completed PHP referral. It also keeps the handoff centered on verified program categories rather than assumptions about access or individual suitability.

Apply the emergency department referral factors

Contact MVBH admissions for the receiving process, while using urgent and routine referral boundaries for emergency department discharge teams to distinguish pathway questions. For a PHP referral, verify every required handoff factor rather than relying only on the program name.

The verified emergency department referral guidance names the decision factors that require confirmation. They are service scope, location, contact arrangements, privacy permissions, continuity needs, and a safe transition plan. Each factor answers a separate operational question.

Service scope identifies what is being requested. Location identifies the relevant setting. Contact arrangements establish how the parties will communicate. Privacy permissions address information handling. Continuity needs connect the referral with existing plans. A safe transition plan places the referral within the broader discharge handoff. These factors structure the process without predicting a disposition or program response.

Keep the PHP decision within verified boundaries

Review urgent and routine referral boundaries for emergency department discharge teams before comparing outpatient treatment programs. The verified evidence supports a structured referral inquiry, not an individual care-level decision or a conclusion about availability.

The available evidence supports two limited conclusions. First, PHP is among MVBH’s listed programs. Second, emergency department referrers should confirm the six stated referral elements. Neither conclusion supplies a clinical threshold for choosing PHP over another program.

The urgent-versus-routine resource can help organize pathway boundaries, while the programs page provides broader service context. However, this page cannot establish urgency, care level, acceptance, capacity, insurance terms, or expected results. Keeping those limits visible prevents a general scope statement from being used as an individualized decision.

Coordinate contact and privacy permissions

Use outpatient treatment programs to identify the named service context, then review mental health conditions for general condition information. For this referral route, confirm location, contact arrangements, and privacy permissions before sending protected health information.

A usable handoff identifies the contact route and confirms who may exchange the needed information. The federal rule states that a covered entity may use or disclose protected health information for its own treatment, payment, or health care operations. This describes a permitted category, not every detail of a particular exchange.

The referral guidance separately calls for confirming privacy permissions. Discharge teams should keep that confirmation alongside location and contact arrangements. This creates a clearer operational record of the intended communication. It does not establish that every disclosure is permitted, required, or complete in a specific situation.

Complete the continuity and transition handoff

Consult mental health conditions for general context, then use therapy services to understand broader service language. The emergency department referral itself should end with confirmed continuity needs, clear contact arrangements, and a safe transition plan.

Continuity planning connects the referral request with the wider discharge process. The verified guidance does not define a particular transition model. It does require referrers to confirm continuity needs and a safe transition plan.

For route-specific documentation, record the requested program, confirmed location, agreed contact arrangements, privacy-permission status, continuity needs, and transition-plan status. Open questions should remain labeled as open questions. This approach gives the receiving conversation a clear agenda without implying that a referral has been accepted or that PHP has been selected for an individual.

PHP referral handoff check

Confirm PHP is the requested program
Verify service scope and location
Document contact arrangements and privacy permissions
Clarify continuity needs
Confirm a safe transition plan

FAQ

Frequently Asked Questions

Is PHP within MVBH’s stated program scope?

PHP is included in MVBH’s verified outpatient program scope. That scope also names IOP, OP, Virtual IOP, and Dual Diagnosis. This fact confirms the program category only. It does not establish current availability, acceptance, coverage, or whether PHP is appropriate for a particular person.

What should an emergency department discharge team confirm?

The verified referral guidance identifies six items: service scope, location, contact arrangements, privacy permissions, continuity needs, and a safe transition plan. These elements provide a structured handoff framework. They do not replace the emergency department’s own discharge procedures or establish acceptance into a program.

How does privacy affect a PHP referral?

The referral guidance says referrers should confirm privacy permissions. Federal regulation also states that a covered entity may use or disclose protected health information for its own treatment, payment, or health care operations. The permitted purpose and the specific referral workflow remain distinct questions that should be addressed during the handoff.

Does submitting referral information confirm PHP acceptance?

No. The verified facts establish that PHP is within MVBH’s program scope and identify referral topics to confirm. They do not verify current program availability, admission, coverage, results, or individual suitability. Emergency department discharge teams should treat the page as a referral-planning framework rather than an acceptance determination.

What supports continuity during the referral handoff?

Continuity needs and a safe transition plan should be confirmed as part of the referral process. Contact arrangements and location should also be clear. Together, these details help define who communicates, what still needs confirmation, and how the planned handoff connects with the discharge process.

Sources

Electronic Code of Federal Regulations

A clear next step starts with a conversation.

Call MVBH or review plan-specific benefits.

978-233-9597

Review Benefits Contact Us