When to Use This Article
This article is helpful when:
The Opus EMR team requests a list of API modules required for the integration
A patient push to Opus returns a 400 Bad Request error
You are setting up the Opus integration for the first time and need to know what data to prepare
API Modules Used by the Dazos-Opus Integration
The Dazos-Opus integration requires access to the following API modules:
Authentication
POST /api/integration/Auth— Exchanges the API key for a bearer token
Patient Management
POST /api/integration/Patients— Creates a new patient record in OpusPATCH/PUT /api/integration/Patients/{patientId}— Updates an existing patient record/api/integration/PatientContacts— Pushes patient contact information/api/integration/PatientInsurances— Pushes patient insurance policies
Episodes of Care
POST /api/integration/EpisodesOfCare— Creates a new episode of carePATCH/PUT /api/integration/EpisodesOfCare/{case_file_id}— Updates an existing episode of careGET /api/integration/EpisodesOfCare?pageSize=100&status=Active— Retrieves active episodes for bed board functionality
Insurance Companies
/api/integration/InsuranceCompanies— Looks up or creates insurance company records
Bed Board Management
POST /api/integration/BedBoard— Creates a bed recordDELETE /api/integration/BedBoard/{ehr_bed_id}— Removes a bed recordGET /api/integration/BedBoard?location={name}— Fetches beds for a specific location
Required Fields for Creating a Patient in Opus
When pushing a patient from Dazos to Opus, the following fields are required by Opus. If any of these fields are missing, Opus will return a 400 Bad Request error and the patient will not be created.
Mobile Phone Number
Address Line 1
City
State
Zipcode
Legal Sex
Make sure all six fields are populated on the patient's record in Dazos before attempting to push to Opus.
⚠️ Warning: A push attempted without these fields will fail immediately. The Opus API will return validation errors for each missing field. No partial record will be created.
Additional Setup Requirements
To complete the Opus integration configuration in Dazos, you must also provide the following information so it can be mapped in the integration settings:
Discharge Types — The list of discharge reasons used in your Opus instance
Levels of Care (LOC) — The levels of care configured in your Opus instance
Admitted Statuses — The admission statuses used in your Opus instance
💡 Tip: Collect this information from your Opus administrator and share it with the Dazos support team during integration setup. These values must be mapped before the integration can function end-to-end.
Tips & Notes
✅ Best Practice: Before initiating your first patient push, verify that all six required fields are consistently populated on your patient records in Dazos.
💡 Tip: The Opus API key provided during setup must have permissions enabled for all modules listed above — not just the Patients module. Contact your Opus administrator to confirm the correct permissions are assigned.
⚠️ Note: The API key is tied to a live production environment. Ensure all configuration and testing is done carefully before processing live patient data.
Related Resources
Opus EMR Integration API Modules and Bidirectional Capabilities (CRM)
Required Fields for Pushing Clients to Alleva EMR (CRM)
Sunwave Integration: Required Field — Admitting to LOC for Successful Patient Push