Overview
This guide explains how to set up a new Ritten EMR integration with Dazos CRM. The integration enables pushing patient demographics, discharge data, and LOC mapping between the systems.
Before You Begin
You'll need the following information from your Ritten account:
Location Alias
Client ID
Client Secret
Integration credentials (similar to Sunwave integration setup)
⚠️ Note: If you already have one Ritten account connected and want to add a second location, you can follow the same setup process for the additional account.
Integration Capabilities Matrix
Our integration with Ritten is highly robust and covers several key areas of data synchronization:
1. Sending Data TO Ritten (CRM ➡️ EMR)
Supported:
Send patient to EMR (including via automated workflows/workflows).
Send full demographic and contact data (including custom demographic field mapping, such as SSN).
Send patient insurances and related contacts.
Send PDFs/documents (already in use via workflow automations).
Under Review/Limited:
Referral Source: Not currently open, but Ritten can enable this upon request.
2. Pulling Data FROM Ritten (EMR ➡️ CRM)
Supported:
Manual and scheduled pulls (hourly/daily).
Real-time updates via Webhooks: Programs (level of care, admit, transfer, discharge) update Dazos automatically. This includes LOC history, admitted/in-treatment status, patient info updates, insurance updates, and related-contact updates.
Limitations:
Fields not included in the standard program webhook payload (e.g., a changed phone number) do not push instantly; they require a scheduled hourly/daily CRM refresh to sync.
Outbound Referrals: Not currently supported/confirmed.
3. Linking & Matching
Supported:
Manual linking of CRM opportunities to existing EMR patients.
Auto-linking based on admission date, name, and date of birth (DOB).
Automatic creation of new CRM opportunities when a patient exists in the Ritten census but has no matching CRM record (all linking logic resides on the Dazos side).
4. Field & Form Mapping
Supported:
Discharge type and discharge reason mapping (fully supported and updated via webhooks).
NOT Supported:
Pre-Admission Assessment (PAA) field-for-field form rendering inside Ritten (Workaround: Send completed pre-assessments to Ritten as flat PDFs).
One pre-assessment mapped to multiple forms.
Direct treatment program field mapping.
5. Specialty Features
NOT Supported:
Bed Board: Not currently connected to Ritten's API (can be custom-built upon request, but not active out-of-the-box).
Steps to Integrate
Gather Required Information: Contact your Ritten administrator or Barry O'Brien (
[email protected]) to obtain your Location Alias, Client ID, and Client Secret.Provide Integration Credentials: Create integration credentials for Dazos (using your dedicated integrations email).
Submit Integration Request: Open a ticket with Dazos Support, providing the credentials and Ritten API details.
Configuration & Mapping: Dazos support will set up the handshake, establish webhook endpoints for instant LOC updates, map custom demographic fields, and test the initial data flow.
Expected Timeline and Considerations
⚠️ Important: Working with Ritten support can be complex and may involve delays, especially for custom requirements that need cross-department coordination. Standard mapping is processed first, with specific customizations handled as additional requests.
Verification / Expected Result
After setup is complete, you should be able to:
Push patient demographics from Dazos CRM to Ritten
Receive discharge updates in your CRM
View accurate LOC mapping between systems