How to get slot-type and schedule.actor

100 views
Skip to first unread message

Neetoo Maurya

unread,
Aug 28, 2019, 3:29:18 PM8/28/19
to Cerner FHIR Developers
Hi Team,

I am calling below API and getting results.

But my question is how we will know the value of schedule.actor and slot-type which we are passing as query parameters.

I checked from this API https://fhir-ehr.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Schedule?_id=21265426-633867-3121665-0,21265426-633867-3121665-15, we are getting schedule.actor and slot-type, but again question, from where I can get Schedule ids passed as query parameters?


Valid ids for the schedule.actor and slot-type search parameters will be provided by the client, is it?

Joshua Fisk (Cerner)

unread,
Aug 30, 2019, 2:12:49 PM8/30/19
to Cerner FHIR Developers

The actor is going to come from either the Schedule or the Practitioner resource. As far as finding the Schedule ids, those will come from querying the Slot resource (the ids themselves are in the response). You can use the _include parameter on your Slot search so that you will only have to make a single call: https://fhir-open.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Slot?_id=21265426-633867-3121665-0&_include=Slot:schedule
 
With slot-type we recommend using proprietary codes, but LOINC codes can also be used. The way to get both of these would be through the client.

Thanks,
Joshua

Lee Arnett

unread,
Sep 9, 2019, 1:30:26 AM9/9/19
to Cerner FHIR Developers
Why don't (Cerner) just publish a list of location ids and provider ids that are your standard sandbox test data?
Lee

Joshua Fisk (Cerner)

unread,
Sep 9, 2019, 3:33:05 PM9/9/19
to Cerner FHIR Developers
Unfortunately, due to it being a sandbox environment, the data in it is volatile and maintaining a list is beyond our ability.
Reply all
Reply to author
Forward
0 new messages