Bidirectional Data Flow
The Opus integration supports full bidirectional synchronization:
Dazos → Opus: Patient demographics, contact information, insurance details, and episodes of care are sent to Opus when created or updated in Dazos
Opus → Dazos: Updates made in Opus, including discharge dates and status changes, are automatically pulled back into Dazos
💡 Tip: Discharge dates push back from Opus into Dazos automatically. When a patient is discharged in Opus, the corresponding Dazos record is automatically updated.
API Modules Used by the Opus Integration
Authentication
POST /api/integration/Auth— Exchanges API key for bearer token authentication
Patient Management
/api/integration/Patients— Creates new patient records/api/integration/Patients/{patientId}— Updates existing patient information/api/integration/PatientContacts— Syncs patient contact information/api/integration/PatientInsurances— Manages patient insurance policies
Episodes of Care
/api/integration/EpisodesOfCare— Creates new episodes of care/api/integration/EpisodesOfCare/{case_file_id}— Updates existing episodesGET /api/integration/EpisodesOfCare?pageSize=100&status=Active— Retrieves active episodes for bed board functionality
Insurance Companies
/api/integration/InsuranceCompanies— Looks up and creates insurance company records
Bed Board Management
POST /api/integration/BedBoard— Creates bed recordsDELETE /api/integration/BedBoard/{ehr_bed_id}— Removes bed recordsGET /api/integration/BedBoard?location={name}— Fetches beds for specific locations.
When to Use This Information
This article is helpful when:
Opus EMR requests specific API module details for integration setup
Troubleshooting data sync issues between systems
Confirming which patient data elements are supported in the integration
Verifying bidirectional capabilities for discharge tracking
For additional information about EMR integrations, see:
What are the different EMR system integration capabilities? (CRM)
EMR Integration Configuration and Setup guides