Page Status: Outdated

Operation Outcome - Reply

Page index

Introduction

This section describes the process of TODO

Sequence diagram

The diagram below shows the typical sequence needed to TODO

Examples

Create prescription with AFF-issues

This example shows how an OperationOutcome looks like if there are blocking AFF-issues when creating a prescription. The HTTP status would in this case be 422 and no MedicationRequest would be created.

Note that if there had been only warnings the MedicationRequest would be created and the HTTP status would be 201. An OperationOutcome would be returned only if it was requested by setting Prefer to "return = OpertationOutcome".

Create MedicationRequest with AFF-issues

Create dispense with AFF-errors

This example shows how an OperationOutcome looks like if there are blocking AFF-issues when dispatching a set of prescriptions, i.e. a Bundle of MedicationDispenses. The HTTP status would in this case be 422 and no MedicationDispenses would be created.

Each AFF-error points at the related entry in the Bundle in two ways, by an extension NLLDispatchRowNo and by a FHIRPath in issue.expression. Expression points at the index in the Bundle and NLLDispatchRowNo at the expeditionradnummer the requestor has defined. This makes it possible for an implementer to use a standard FHIR parser and map the issue by the expression or using snippet of NLL specific code to use the extension.

Create multiple MedicationDispenses with AFF-errors

Application error

This example shows how an OperationOutcome looks like when the request is rejected by a business rule (not an AFF-issue). The HTTP status would in this case be 400.

OperationOutcome.issue.details containes an error code and the display element an error text.

OperationOutcome with an application error

System error without error code

This example shows how an OperationOutcome looks like when the request is rejected by the FHIR parser. The HTTP status would in this case be 500.

Note that OperationOutcome.issue.details is missing in this case because it was a parser error.

OperationOutcome with a system error

Low level system error

This example shows a low level error. The Content-Type would be "text/html" in this case and the HTTP status 503.

systemerror-example-1