Retrieve or search appointment or breaks in Drchrono
A documented Drchrono operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Retrieve or search appointment or breaks.
- GETReads data · Clinical
app.drchrono.com/api/appointments
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Drchrono operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Drchrono operations
- Create a taskPOST · changes data
- Create messages in doctor's message centerPOST · changes data
- Create a new appointment or break on doctor's calendarPOST · changes data
- Create sub-vendors - When you get ordersPOST · changes data
- Create lab tests. An example lab workflow is as following: - WhenPOST · changes data
- Create patient amendments to a patient's clinical recordsPOST · changes data
- Create lab orders. An example lab workflow is as following: - WhenPOST · changes data
- Create a task notePOST · changes data
Questions
- Can HumDay retrieve or search appointment or breaks in Drchrono?
- Yes. This operation is published in Drchrono's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Drchrono account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Drchrono.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Drchrono account.
Where this came from
Read from a published API description for Drchrono at drchrono.com/openapi-schema. The description above is the provider’s own wording, not ours. Last published 2021-07-12.