Test Data for Cerner Millenium

Time Slots

When calling the GET /timeslots endpoint, you can use the following combination of care_unit_id, resource_id and healthcare_service_id to find available time slots.

Patients

When calling the GET /patients/{patient_id}, you can use the following patient_id to get patient details. Those ids work with any valid care_unit_id from the GET /care-units endpoint.

When calling the POST /patients, you will see a mocked response, where emr_id and id are set to MOCKED.
This is because Millenium does not allow creating patients via API in their Sandbox environment.

Please reach out at contact@leyr.io if you have a clinic using Cerner Millenium, so we could test patient creation there together.

Appointments

When calling the POST /appointments, you will see a mocked response, where emr_id and id are set to MOCKED.
This is because Millenium does not allow booking appointments via API in their Sandbox environment.

Please reach out at contact@leyr.io if you have a clinic using Cerner Millenium, so we could test appointments booking there together.

Other Data for Testing

Apart from two mocked endpoints above, 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.
• You can then use resource id returned from the GET /resources endpoint, or healthcare service id returned from the GET /healthcare-services endpoint, when testing GET /timeslots.
• You can also call GET /appointments without any optional parameters to get all appointments for the clinic. There you can find even more patient ids to test with the GET /patients/{patient_id} endpoint.

Happy coding! 🙂