Request data while authenticated as an authorized patient or patient proxy. a patient asking for data about a stranger's allergies).Īdditional data may be present for patient Request data that the authenticated user is not allowed access to view (i.e. Request for an Immunization resource without a documented CVX code. This error only applies to DSTU2 version paging functionality.Ĭalled in paging context if the user has gone to the next page of the same session but changed the original query:ĪllergyIntolerance?patient= <- original queryĪllergyIntolerance?patient=&page=2&session=123 <- validĪllergyIntolerance?patient=&page=2&session=123 <- error is logged. Required search parameter has an invalid valueĪn invalid parameter required for searching: Condition?Patient=&category=foo Making a request for previously accessed paginated search results after the search has expired. Session ID for cached search results has expired. The resource request contained an invalid combination of parametersĪ search containing multiple different patient ID: AllergyIntolerance?patient=&patient= Required search parameter missing from requestĪ request missing a required parameter (such as the patient): Condition?category=diagnosis No parameters are provided in the search requestĪn invalid search request such as : AllergyIntolerance? To browsers and many HTTP clients, the redirect will be transparent. Requesting a Patient which has been merged - in this event, in addition to the error response, we will respond with an HTTP Redirect status. The read resource request has been merged
#Epic beaker code
Invalid Resource ID: AllergyIntolerance/fooĪ read request for a resource that was deleted in the systemĪ required FHIR element was not available to send in the responseįailed to determine a SNOMED code for the smoking status. The read resource request contained an invalid ID a patient with no pertinent implanted devices, or a demographic search where no patients met the search criteria). Invalid parameter such as a nonexistent patient ID: AllergyIntolerance?patient=fooĪ request for data that was otherwise valid but no information was documented or found (i.e. The resource request contained an invalid parameter Warning Errors accompany a successful response and are used to indicate that part of a request could not be fulfilled - for example, if a status is unknown, but the request can be fulfilled, the API will return the data and indicate that part of the request couldn't be understood.
Instead, your application should interpret the codes and provide user-friendly resolution steps when data cannot be filed. These codes are meant for developer use only - they should not be presented to end users. Currently, the error code is not included in the REST version of the specification, but it is provided here for your reference. When things go wrong, the API will respond with an error code and a human-readable description to describe the incorrect submission.
0 kommentar(er)
