Dazos supports a bidirectional integration with KIPU EMR, enabling patient data to flow seamlessly between both systems. This connection helps eliminate manual data entry and ensures your teams always have access to the most up-to-date patient information.
Patient Creation: What Dazos Sends to KIPU
When a new patient is created in Dazos, the following information is sent to KIPU to generate the patient record in their EMR system:
{
"first_name": "Test1",
"last_name": "Test2",
"preferred_name": "TJ",
"dob": "2000-01-01",
"marital_status": "Single",
"location_id": "2",
"mr": "",
"phone": "+15133206417",
"alternate_phone": "+15131234567",
"address_street": "123 Oak St",
"address_street2": "Unit B",
"address_city": "Middletown",
"address_zip": "45044",
"address_state": "OH",
"address_country": "US",
"gender": "Male",
"email": "[email protected]",
"first_contact_name": "Dazos Main Line",
"first_contact_information": "Phone Inquiry",
"first_contact_relationship": "Self",
"referrer_id": "11",
"referrer_name": "Recovery in the Ocean",
"admission_date": "2025-04-16 00:00:00",
"discharge_date": "",
"payment_method": "Insurance"
}Custom Field Mapping
Dazos allows custom fields to be mapped to KIPU. If there’s a field you need that doesn’t exist in Dazos:
Link to KIPU API Documentation: https://api.kipuapi.com/api-docs/index.html#/Patient/post_patients
Create the field in Dazos.
Submit a support ticket requesting it to be mapped.
Our team will:
Review KIPU’s API documentation to check if the field is supported.
Map it accordingly if available.
⚠️ Field mapping depends on the availability of the field in KIPU’s API.
Requirements to Enable Sync from KIPU
To begin pulling updates from KIPU, the following fields must be populated in the KIPU patient chart:
First Name
Last Name
Date of Birth
Admission Date
MR Number (automatically generated by KIPU)
Once these fields are present, Dazos begins syncing patient updates from KIPU, based on configured field mappings.
What Dazos Pulls Back from KIPU
After admission is completed in KIPU, Dazos will receive the following data if present and mapped:
{
"first_name": "Test1",
"last_name": "Test2",
"gender": "Male",
"dob": "2000-01-01",
"address_street": "123 Oak St",
"address_street2": "Unit B",
"address_city": "Middletown",
"state": "OH",
"address_zip": "45044",
"address_country": "United States",
"email": "[email protected]",
"admission_date": "2025-04-28T07:00:00.000Z",
"discharge_date": "",
"discharge_or_transition_id": "4",
"discharge_or_transition_name": "Outpatient Program",
"discharge_type": "Planned",
"discharge_type_code": "P01",
"first_contact_name": "Dazos Main Line",
"referrer_name": "Recovery in the Ocean",
"mr_number": "DHR2025-63",
"payment_method": "Insurance",
"payment_method_category": "2",
"created_at": "2025-04-23T18:56:17.866Z",
"last_updated_at": "2025-04-23T18:57:13.721Z",
"insurances": [
{
"member_id": "A123456789",
"group_number": "GR987654321"
}
],
"patient_contacts": [
{
"name": "Jane Doe",
"relationship": "Mother",
"phone": "555-123-4567"
}
],
"phone": "+15133206417",
"level_of_care": "Residential",
"program": "Substance Use",
"bed_name": "A-101",
"room_name": "102",
"building_name": "Main Building"
}Referral Source and Insurance Details are mapped by default on the backend and will sync automatically.
Need Help?
Our support team is available to help with:
Creating custom fields
Reviewing field compatibility with KIPU’s API
Assisting with field mapping
Submit a ticket anytime, and we’ll ensure your Dazos <> KIPU connection is set up for success.