Test Data for J4
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 J4 EHR setup guide.
Mocked Environment
We currently don't have a test environment that we could share with you, so when using Leyr credentials only, you will be interacting with a mocked version of J4. However, even in this case, we have fully replicated real J4 data models, so the response data that you will receive while trying our Sandbox out will fully match your production experience!
When using your own credentials, you will be interacting with the real J4 test environment.
Other Data for Testing
Either with Leyr Credentials or your own - feel free to explore any combinations of data returned by the endpoints in the API documentation!
Start by calling GET /care-units to get care units available for testing.
Then you can use resource id returned from the GET /resources endpoint, or healthcare service id returned from the GET /healthcare-services endpoint, when testing GET /timeslots.
GET /timeslots try your first call without resource_id or healthcare_service_id to get more test data back. You can then use those parameters to filter the results.You can use found timeslots, together with patient created with the POST /patients endpoint, to test POST /appointments.
Happy coding! 🙂