Test Data for WebDoc
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 WebDoc 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 WebDoc. However, even in this case, we have fully replicated real WebDoc 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 WebDoc test environment.
Other Data for Testing
Even though the Sandbox is temporarily mocked, we have fully replicated real WebDoc 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 theGET
/resources endpoint, or healthcare serviceid
returned from theGET
/healthcare-services endpoint, when testingGET
/timeslots.Hint: When testingGET /timeslots
try your first call withoutresource_id
orhealthcare_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 testPOST
/appointments.
Happy coding! ๐