When to Use / Why It Matters Because the Ritten API requires a multi-step approach to data transfer, users may initially see "minimal" patient profiles. Understanding this flow helps administrators identify where data is being held and ensures that insurance information is correctly mapped for billing and clinical review.
Details / Main Content
1. The Two-Step Integration Flow
Step 1: Patient Creation (Create API): Initially, the patient is created in Ritten with a limited set of mandatory fields. At this stage, the profile will contain only basic information.
Step 2: Patient Update (Patch API): Once Ritten generates a unique Patient ID, Dazos sends a "PATCH" call. This second step carries the bulk of the data, including demographics, contact details, and related clinical data.
2. Insurance Data Requirements Insurance information is bundled into the Step 2 (Patch API) call. For insurance data to successfully transfer to Ritten, two conditions must be met:
Data Availability: The parent account in the CRM must have insurance information associated with the patient.
Payer Code Mapping: The Payer Code must be correctly mapped within the Dazos EMR Settings. If the EMR does not recognize the CRM’s payer code, the insurance segment will be excluded from the transfer.
Troubleshooting / Common Errors
Symptom: Patient exists in Ritten but insurance data is missing.
Cause A: The parent account in the CRM has blank insurance fields.
Cause B: The Payer Code is not mapped in the EMR settings, causing the system to drop the insurance payload to prevent EMR errors.
Solution: Navigate to Settings > EMR Settings and verify that your Payer Codes match the requirements of the Ritten EMR.
Symptom: Missing Demographic Info.
Cause: The Step 2 "Patch API" call may have failed or timed out.
Solution: Refresh the integration link or contact support to review the Patch API logs.