Find Appointment Slot

a key step in the appointment scheduling flow is finding an available appointment slot based on the parameters in the find appointment slot request, possible appointment times are returned where all required "assets" are available interaction finding the available appointment slots can be done by sending a post request with the fhir $find operation to the appointment endpoint https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/appointment/$find where \<region> should be defined according to the different founda docid\ ncff15xnu1wglst2wnm p and \<org x> should be replaced with the healthcare provider's organization id that you are integrated with the post request should contain the required assets in the body according the parameters table the response contains a bundle with a search set of proposed appointment times, matching the amount that was queried for in the body profile founda adheres to recognized standards (ihe, hl7 fhir) to ensure compatibility and harmonization among diverse systems if there is a profile available for an interaction, it is recommended and preferred to follow the prescribed transactions the find appointment slot interaction with the founda platform is based on the ihe fhir scheduling profile's https //build fhir org/ig/ihe/iti scheduling/iti 114 html parameters these input parameters determine which assets are needed to be able to schedule the visit the $find operation returns a set of possible appointment times where all required assets are available true 124,59,89,117 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type example api call curl location 'https //api eu founda com/1/health/organizations/org 4c5739ba994d4ce9b5255d3f84a2d367/fhir/4/appointment/$find' \\ \ header 'content type application/json' \\ \ header 'authorization bearer ory at j3f3k53svp4b8fuoqij99xsxg0ytisqdo6n89ie 8zu 1jzkaqauuq tj79ljqfczrubxq4gtqlo4xbvkwvemqm' \\ \ data ' { "resourcetype" "parameters", "parameter" \[ { "name" "start", "valuedatetime" "2017 07 15t20 00 00z" }, { "name" "end", "valuedatetime" "2017 07 17t20 00 00z" }, { "name" "provider", "valueuri" \["practitioner/2079"] } }, { "name" "location", "valuestring" \["south wing, second floor"] } ] }'