Test Data for DIPS
It is applicable when using Leyr credentials, as described in the EHR configuration guide.
If you'd like to use your own credentials or are going live, please refer to our DIPS EHR setup guide.
Environment Overview
We have a partially integrated Sandbox for testing with DIPS. Patient management and document workflows are fully functional, while appointment-related features are not yet available due to DIPS API limitations. We monitor DIPS API developments and will enable additional endpoints as they become available.
Common Workflows
Care Units Discovery
This is the typical entry point to the Leyr API. The care unit ID returned here is required for all subsequent API calls.
Call GET /care-units to discover available care units in your DIPS system. Use any id from the response in the path parameter for other endpoints.
Patient Management
Retrieve and create patient information with real DIPS data.
Get Patient: Use GET /patients/{patient_id} with the following test patient ID, which works with any valid care unit ID:
| patient_id |
|---|
| cdp1000807 |
Create Patient: Use POST /patients to create new patients. All standard patient fields are supported and will be reflected in your DIPS system.
Availability
Discover available resources and services, though time slots and appointment booking are not supported.
Get Services: Call GET /healthcare-services to retrieve available healthcare services configured in your DIPS system.
Get Resources: Call GET /resources to get available practitioners and resources.
Appointment Booking
Medical Notes
Documents
Access and manage patient documents with real DIPS data.
Get Documents: Use GET /documents with the test patient ID (cdp1000807) or any patient ID from your DIPS system.
Create Document: Use POST /documents to upload or create new documents for patients.
Happy coding! 🙂