If Cerner FHIR support Holds and Blocks

[Neetoo Maurya]

Hi Team,

Please let me know if Cerner FHIR have such API through which we can pull Holds/Block created in provider schedules.

Holds are the slots in calendar, those are available for booking  only for mapped appt types.

Blocks, not available for booking at all.

Also let me know if there is any API to create holds.

Regards,

[Neetoo Maurya]

Hi Team,

Can I get the answer of my question?

Regards,

[Max Philips (Cerner)]

Hi Neetoo,

Which FHIR APIs are you wondering if we have support for? The APIs that Cerner has implemented are documented on fhir.cerner.com and in the metadata of our server.

For Scheduling resources we have exposed the following APIs:

DSTU2 - Appointment, Schedule, Slot

R4 - Appointment

Thanks,

Max (Cerner)

[Neetoo Maurya]

Thanks for your reply. I want to know If I can use any FHIR API through which I can pull Holds/Block created in provider schedules.

Regards,

[Max Philips (Cerner)]

Hi Neetoo Maurya,

I believe that the Slot API is likely where that kind of information would be stored, but let me know if you were thinking of a different API.

As documented on fhir.cerner.com Cerner currently exposes Slot read and search for DSTU2, and does not expose any Slot operations for R4.

Thanks,

Max (Cerner)

[Brent Lanphear]

Any update on this Neetoo or Max? It doesn't seem like there was any answer to this except to check the docs which does not answer the question of if you can "hold" a time slot. A book appointment API call requires all information for the booking (like a patient to tie the appointment to). A "hold" operation for example, should not necessarily need patient information before it can be held. 

Thanks, 

Brent

[Benjamin Eichhorn (Cerner)]

Hi Brent,

As Max mentioned, all of the functionality of our APIs is listed on fhir.cerner.com. We work to ensure it is accurate and describes the full capabilities of our APIs. If you do not see a resource or action listed on there then it is not something that we currently support. We do not currently support the workflow you are describing.

Thank you,

Ben (Cerner)