PHP Referral for Employee Assistance Programs

Approved by Clinical Staff

Employee Assistance Program professionals may use this route when considering a PHP referral to MVBH. The verified scope confirms that PHP is among MVBH’s programs. It also confirms that EAP professionals can refer adults for screening for outpatient behavioral health and dual-diagnosis services. Screening, rather than an assumed placement, is the supported next step.

What the EAP PHP referral route supports

Start with professional referral resources, then review MVBH admissions. Together, these routes place an EAP referral within the professional and admissions context while preserving screening as the verified purpose.

The route begins with a narrow, verified fact: EAP professionals can refer adults to MVBH for screening for outpatient behavioral health and dual-diagnosis services. The supported function is referral for screening. The evidence does not support promising admission, availability, coverage, program fit, or a specific result.

PHP is one of the programs within MVBH’s locked scope. The same scope also names IOP, OP, Virtual IOP, and Dual Diagnosis. Listing these programs does not establish that every program applies to every person or referral. For an EAP professional, the practical distinction is between identifying PHP for consideration and deciding that PHP is the required destination. Only the first is supported here.

Decision factors before sending the referral

Review MVBH admissions before applying the urgent and routine referral boundaries for employee assistance programs. These resources separate the general admissions route from the distinct question of referral urgency.

The central decision is how to frame the request. An EAP professional can identify PHP as the program being considered while requesting screening for an adult. This wording reflects both verified facts without turning the referral into an unsupported care-level conclusion.

Urgency is a separate referral question. The supplied evidence does not define urgent indicators, routine timing, or response procedures. Those issues should remain within the linked urgent-versus-routine boundary rather than being inferred from the PHP label. Likewise, the term PHP does not establish acceptance or immediate access. A concise referral purpose can state the adult screening request, the outpatient context, and that PHP is under consideration. It should avoid predictions about the resulting program decision.

Evidence boundaries for a PHP referral

Use the urgent and routine referral boundaries for employee assistance programs alongside the verified outpatient treatment programs. The first addresses referral framing, while the second supplies program context without determining individual placement.

The evidence boundary establishes program names and the EAP referral role. It does not provide diagnostic criteria, clinical thresholds, comparative intensity, scheduling details, or individual recommendations. Those conclusions should not be added to a PHP referral merely because PHP appears in the verified scope.

The strongest supported statement is limited: an EAP professional may refer an adult for screening for outpatient behavioral health and dual-diagnosis services. PHP can be named because it is in MVBH’s documented program scope. The referral should not state that screening will lead to PHP or any other listed program. It also should not suggest that the existence of a program confirms availability. This boundary keeps the route useful without converting general program information into an individual determination.

Access, privacy, and continuity boundaries

Consult outpatient treatment programs for scope, then use mental health conditions only as broader context. Neither route should be treated as confirmation of access, coverage, diagnosis, individual placement, or continuity.

Access and continuity should be handled as process questions, not assumptions. The supplied facts confirm the adult screening referral pathway and the program scope. They do not confirm appointment timing, service availability, payment, coverage, admission, or continued participation. An EAP professional should avoid presenting any of those matters as settled.

Privacy also remains bounded. A covered entity may use or disclose protected health information for its own treatment, payment, or health care operations. That statement supports those named purposes only. It does not resolve every consent, authorization, or organizational-policy question. For this referral route, share and handle information according to the relevant permitted purpose and applicable process. Do not use the privacy fact as evidence that PHP, another program, or payment has been approved.

Next-step context for EAP professionals

Review mental health conditions for general context and therapy services for service context. An EAP professional can then keep the actual request centered on adult screening and PHP consideration.

A useful EAP next step is a clearly bounded adult screening referral. The request can identify the professional referral source, note that outpatient behavioral health or dual-diagnosis screening is sought, and state that PHP is under consideration. This approach uses the verified referral authority and program scope without deciding the final program.

Conditions and therapy information can provide general vocabulary, but neither establishes an individual diagnosis or service selection. Keep the referral focused on the screening purpose rather than adding unsupported conclusions. If the main uncertainty concerns urgency, use the dedicated urgent-versus-routine route. If the uncertainty concerns admissions process, use the admissions route. These distinctions help direct each question to its relevant MVBH resource while maintaining the limits of the evidence supplied for EAP PHP referrals.

EAP PHP referral decision checkpoints

Confirm the referral concerns an adult
Request screening rather than assuming PHP placement
Keep PHP within the verified outpatient program scope
Separate urgent and routine referral questions
Handle protected information under applicable permissions

FAQ

Frequently Asked Questions

Is PHP included in MVBH’s verified program scope?

Yes. The verified MVBH program scope includes PHP, IOP, OP, Virtual IOP, and Dual Diagnosis. This establishes PHP as part of the documented scope. It does not establish availability, acceptance, coverage, individual fit, or a particular result. An EAP referral should request screening rather than presume a program decision.

What can an EAP professional request from MVBH?

EAP professionals can refer adults to MVBH for screening for outpatient behavioral health and dual-diagnosis services. That statement supports an adult screening referral pathway. It does not authorize a conclusion about diagnosis, care level, admission, or program fit before screening and review through the appropriate MVBH process.

Does a PHP referral establish placement in PHP?

No. A referral can identify PHP as the program under consideration, but the supplied evidence supports referral for screening. It does not support assuming placement, acceptance, availability, coverage, or an outcome. Keeping the request framed around screening preserves the distinction between the EAP’s referral purpose and MVBH’s subsequent process.

What privacy boundary is relevant to referral information?

A covered entity may use or disclose protected health information for its own treatment, payment, or health care operations. This fact describes a permitted-use category, not every referral situation. EAP professionals should keep information handling connected to the relevant purpose and avoid treating the rule as proof of coverage, placement, or authorization beyond its stated scope.

What other programs appear in the verified MVBH scope?

The confirmed programs are PHP, IOP, OP, Virtual IOP, and Dual Diagnosis. The evidence does not compare those programs or assign an individual to one of them. For this EAP route, the supported action is an adult referral for screening, with PHP identified as the specific program being considered.

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