HTTP Request Headers

the fhir® panel and prescription notifications delivered to the surescripts service must include the http request headers content type codes and encodings please be aware that the only valid accept content type is application/json+fhir , where application/json+fhir is used as the default value although other content types listed here are supported, the application will only return content that maps to application/json+fhir supported content types application/json+fhir (default value) application/fhir+json application/json text/json http request header elements code field comment accept optional the accept request header field can be used to specify certain media types which are acceptable for the response values application/fhir+json content type optional the content type header is to specify the media type of the content being sent for more information see the content types and encodings section below values application/fhir+json x sender uid mandatory participant id example t00000000012345 x sender uid qualifier mandatory participant id qualifier fixed 10 x requester id conditional this will be included in the http header request of the fhir response and identifies the bundle id http header request example accept application/fhir+json content type application/fhir+json; charset=utf 8 x sender uid t00000000012345 x sender uid qualifier 10 fhir request parameters this section outlines common fhir parameters that customers may use in their requests to view the full capabilities of surescripts medication history for populations, retrieve the capabilitystatement resource from the fhir api note see the messages overview docid\ qirl1as9dw4k3lea9ojgr section for details on how search requests are processed on the back end of your organization’s system parameter requirement description example lastupdated optional indicates the date time of search request use gt to indicate greater than and lt for less than to define the loopback window of the request format must be yyyy mm ddthh🇲🇲ssz (in utc) note you may use a smaller lookback window (e g , last 4 hours or 1 day) when generating panels or notifications the maximum allowable lookback period is one month from the requested date lastupdated=gt2026 09 15t11 00 00z lastupdated=lt2026 09 15t15 00 00z include optional identifies resource to be returned in your response include\ iterate must be used for resources beyond the 1st resource requested include=communication\ based on include=medicationdispense prescription include\ iterate=medicationrequest\ requester revinclude optional identifies resource to be returned in your response by performing a reverse reference lookup include\ iterate must be used for resources beyond the 1st resource requested revinclude=condition\ subject note this looks up condition resources based on the subject (patient resource) page token conditional indicates which page of results to retrieve defaults to 1 if not provided required when additional pages are available the next page’s token is supplied in bundle link page token= ad86narb wb3lsoymhxmqinwoxes5lc5mlhnki48yruce58ic2kyqmet count optional size of page that will contain the matches of medicationdispenses defaulted to 50 if not populated max is 1000 count=50 \[parameter]\ missing optional the missing modifier used with a parameter will filter fhir search results include/exclude results don’t have an associated value true = values exist false = values don’t exist note this can be used to exclude patient results where the patient was not found based on\ missing=false