Test Data for Opus

This test data can be used to try out integration with Opus in Leyr Sandbox.
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 Opus 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 Opus. However, even in this case, we have fully replicated real Opus 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 Opus test environment.

Other Data for Testing

Even though the Sandbox is temporarily mocked, we have fully replicated real Opus data models, based on our the real-world testing. Feel free to explore any combinations of data returned by the endpoints in the API documentation - all the response structures, all the data formats there will match your production experience!

  • 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.
    Hint: When testing 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! 🙂

In case of any questions or if you feel stuck - please feel free to reach out at contact@leyr.io.
Table of Contents