Finding a slot for creating an appointment in R4

[David Gileadi]

The R4 documentation for creating an appointment requires a slot ID in the creation request. However I haven't been able to find any R4 resource that provides me with slot IDs to use. There is one for DSTU2 but my app* is configured to use R4 and so if I try a DSTU2 request it fails with a 403. Can you help me figure out how to get slot IDs so I can create an R4 appointment?

* App Id: 83f4a9f8-b018-4186-9f09-4a349094cee3

[Benjamin Eichhorn (Cerner)]

Hi David,

Unfortunately we do not currently support the Slot resource for R4. To use the Appointment Create API in R4 you'll currently need to consume both DSTU2 and R4 versions of the server. This will present some challenges as you will need to flex which version of the server you are hitting depending upon the resource rather than relying on the iss parameter for your app. You will effectively need to parse the "dstu2" or "r4" version in the URL which will likely couple your app to Cerner's implementation of the FHIR server. From an Authorization perspective you won't be able to authorize for the Slot resource if you select the R4 version while creating or modifying your app. I would suggest that you select the "DSTU2" version for your app which will allow you to select the "Appointment" resource for both creates and updates. Scopes are version agnostic so you can call the DSTU2 and R4 versions of the server regardless of which version your app launched against.

Let me know if you have further questions.

Thanks,

Ben (Cerner)