Behavioral health integration fit check
30 minutes · Please do not submit PHI
Choose the smallest integration that removes the handoff.
Bring your EHR, Salesforce edition, and the step your staff repeats today. Leave with the recommended shape, known API or access blockers, and a practical next step.
Admission pushThis build
Create the patient, episode, and packet when the admission milestone is reached.
Real-time sync
Keep patient and appointment changes aligned while both teams stay in their system.
Operating layer
Add census, VOB, documents, and attribution around the clinical system.
A national addiction-treatment network ran its entire admissions funnel in Salesforce (inquiry, verification of benefits, clinical screening, contract) and then, at the moment of admission, the process fell off a cliff: a coordinator re-keyed the patient into theOpus Behavioral Health EHR from a paper packet. Demographics, insurance, emergency contacts, screening documents. Every admission, by hand.
Now that step is gone. Accepting an admission creates the patient in Opus, opens their episode of care, and files the screening documents, on its own, safely repeatable, so a retry after a dropped connection never produces a second chart. The coordinator who used to spend that time re-typing spends it on the patient instead.
The funnel that feeds it
Patients are Person Accounts; each admission is an Opportunity carrying 62 custom fields: demographics, insurance and VOB detail, program, therapists, admission and discharge dates, and the vendor linkage fields. The stages walk the real admissions process: VOB sent to billing, VOB received, screening complete, and finally the admitted stage that fires the push.
Two automations upstream make the final push complete. When a lead converts, a flow auto-creates the 48-field clinical screening with 31 fields pre-filled from the lead. The clinician reviews instead of re-typing, then files it as a branded PDF with one click. And when billing returns a verification-of-benefits document by email, an inbound email handler matches the Salesforce record ID embedded in the subject line and attaches the PDF to the right Opportunity automatically: original messages only, replies and forwards excluded.
The push: five endpoints, one Queueable
The admitted-stage flow makes one decision before enqueueing the job: does this patient already exist in Opus Behavioral Health EHR? It counts admissions on the account: first admission means create the patient; any later one means reuse the stored vendor patient ID and create only a new episode of care. Then the Queueable runs the sequence:
| Step | EHR endpoint | What it does |
|---|---|---|
| 1 | Auth | Obtains a bearer token, retrieved once, reused for every call in the transaction |
| 2 | Patients | Creates the patient from Person Account demographics (new patients only); vendor patient ID and MRN write back to Salesforce |
| 3 | Episodes of care | Creates the episode with program, admission dates, care team, consents, and referral context; episode ID writes back |
| 4 | Patient contacts | Creates the emergency contact when one is on file |
| 5 | Documents | Uploads each eligible, allow-listed file (screening, VOB, agreements) as multipart form data against the episode |
A typical new-patient admission with a full intake packet lands at roughly a dozen HTTP callouts across those five endpoint types. Every create validates its inputs and short-circuits its dependents; every failure logs status and body; and a standalone re-push action lets operations re-send documents to an existing episode without re-running the orchestration.
Opus Behavioral Health EHR integration fit check
Move admitted patients into the EHR without rebuilding the packet by hand.
Configuration over code
Environment routing lives outside the codebase: connection settings in protected custom metadata, the endpoint behind a Named Credential, and the document host switching automatically between sandbox and production based on org context: the same deployment works in both without touching a line of Apex. An allow-list in custom metadata controls which document titles are eligible for upload, so the EHR receives clinical files, not every attachment that ever landed on the record.
Why this shape
This is the milestone push pattern: Salesforce owns the funnel, and the EHR record comes into existence at exactly the moment it should (admission), linked to the right patient and carrying its documents. When clinical staff instead live in the EMR all day and the CRM must mirror it continuously, you want the opposite topology: real-time event-driven sync, which we cover in Salesforce EMR integration for behavioral health alongside the decision framework for choosing between them. For the broader set of what we've shipped in this vertical, see the behavioral-health build library.
Frequently asked questions
Can Salesforce integrate with Opus Behavioral Health EHR?
Yes. In the production implementation audited here, Opus Behavioral Health EHR provides endpoints for authentication, patients, episodes of care, patient contacts, and document upload. An admitted Opportunity creates the required patient and episode records, the emergency contact when present, and eligible attached clinical PDFs without an admissions coordinator re-keying the packet.
How do you prevent duplicate patients on repeat admissions?
Three layers reduce the risk. The trigger flow counts admissions on the patient's account: the first creates a patient in Opus Behavioral Health EHR, while later admissions create only a new episode of care. The vendor patient ID and MRN write back onto the Salesforce record after the first push. A before-save flow copies those IDs onto any new admission for the same patient, so linkage exists before the push fires.
How are clinical documents transferred to Opus Behavioral Health EHR?
At admission, the job queries eligible files attached to the Opportunity (the pre-admission screening PDF, verification-of-benefits documents, and signed agreements) and uploads each as multipart form data against the episode of care. Because inbound VOB emails already file themselves onto the right Opportunity, the packet reaches the EHR without an admissions coordinator gathering attachments.
What happens if a callout fails mid-sequence?
Each step validates its inputs and short-circuits its dependents: no episode, no document upload. Failures are logged with status and response body, and a standalone re-push action lets operations re-send documents to an existing episode without re-running the whole orchestration. Recovery uses stored identifiers and purpose-built re-push paths rather than assuming every call can be repeated blindly.
Admissions team re-keying patients into Opus Behavioral Health EHR, or another behavioral-health EHR? Bring us the workflow. See what we build for healthcare operators.