Overview
When integrating your CRM with KIPU, it's important to understand how the "Admitting to LOC" and "Current LOC" fields work differently. These two fields serve distinct purposes in tracking patient care levels and behave differently during data synchronization.
When to Use / Why It Matters
Understanding this distinction is crucial for:
Accurate patient tracking and reporting
Proper EMR integration setup
Avoiding confusion when LOC values appear to revert or not update as expected
Maintaining data integrity between your CRM and KIPU
Key Differences Between the Fields
Admitting to LOC (Static Field)
Purpose: Captures the initial Level of Care at the time of admission (e.g., "Detox", "Residential").
Behavior:
Once pushed from the CRM to KIPU, this value will not change
Serves as a permanent record of where the patient started treatment
Acts as a historical reference point for the patient's admission
Current LOC (Dynamic Field)
Purpose: Shows the patient's current placement in treatment.
Behavior:
Updates automatically as the patient progresses through different levels of care
Changes every time the patient's Level of Care is updated within KIPU
Reflects real-time treatment status
How This Works in Your Integration Workflow
When Pushing Data (CRM → KIPU)
The Admitting to LOC field from your CRM gets mapped to the Program field in KIPU. This establishes the patient's starting level of care in the EMR system.
When Pulling Data (KIPU → CRM)
If you pull updates from KIPU back to your CRM:
The Admitting to LOC field will retain its original value
The Current LOC field will update to reflect any changes made within KIPU
💡 Best Practices
For Initial Setup
Consider leaving the Admitting to LOC field empty initially in the CRM if you want KIPU to determine and record the starting level of care. This approach allows the EMR to serve as the source of truth for admission data.
For Reporting
Use Admitting to LOC to track where patients entered treatment
Use Current LOC to monitor program progression over time
Both fields together provide a complete picture of the patient's treatment journey
⚠️ Common Issues
If you notice that LOC values are not updating as expected after pulling from KIPU:
Verify that you're looking at the correct field (Current LOC vs Admitting to LOC)
Remember that Admitting to LOC should not change after the initial push
Check that the Current LOC field is properly mapped for dynamic updates