Overview
The KIPU API has specific limitations that affect how documents can be transferred from Dazos CRM to the KIPU EMR system. Understanding these limitations helps set proper expectations for document handling workflows.
API Limitations
Face Sheet Direct Injection: The KIPU API does not allow images or documents to be injected directly into specific Face Sheet slots (such as the Insurance section). This means insurance card images cannot be automatically populated in the dedicated insurance fields on the patient's face sheet.
Folder Restrictions: The integration can only send files as attachments to available folders (tabs) in the EMR. There is no dedicated 'Insurance' folder for document transfers via the API.
Available Document Mapping Options
Documents can be mapped to existing folders in your KIPU instance, such as:
VOB tab (commonly used for insurance-related documents)
Other available folders/tabs configured in your KIPU system
The exact folder names and availability depend on your specific KIPU configuration.
Recommended Workflow
Descriptive File Naming: When uploading documents in the CRM, use clear, descriptive names to make identification easier once they transfer to KIPU. For insurance cards, recommended naming conventions include:
"Insurance Front"
"Insurance Back"
"Insurance Card - [Plan Name]"
Folder Organization: Work with your team to establish a consistent folder mapping that aligns with your clinical workflows, even if documents cannot reach their ideal destinations.
Staff Workflow Considerations
Since documents cannot be directly injected into Face Sheet slots, staff will need to:
Review transferred documents in the designated folder (e.g., VOB tab)
Manually add insurance images to the Face Sheet insurance section when needed
Use the descriptive file names to quickly identify document types
Tips & Notes
π‘ Tip: Coordinate with your KIPU administrator to identify the best available folders for different document types based on your facility's workflow needs.
β οΈ Important: These limitations are imposed by the KIPU API itself, not by the Dazos integration. Future API updates from KIPU may expand these capabilities.