This profile leverages the base EHR project’s OperationOutcome resource to provide standardized error and warning messages without introducing additional constraints.
Simplifier project page:
Command 'link' could not render: Resource was not found for 'canonical=http://ontariohealth.ca/fhir/ehr/StructureDefinition/profile-operationOutcome'
Command 'tree' could not render: Resource was not found for 'canonical=http://ontariohealth.ca/fhir/ehr/StructureDefinition/profile-operationOutcome'
Hybrid View
Command 'tree' could not render: Resource was not found for 'canonical=http://ontariohealth.ca/fhir/ehr/StructureDefinition/profile-operationOutcome'
Snapshot View
Command 'tree' could not render: Resource was not found for 'canonical=http://ontariohealth.ca/fhir/ehr/StructureDefinition/profile-operationOutcome'
Table View
Command 'table' could not render: Resource was not found for 'canonical=http://ontariohealth.ca/fhir/ehr/StructureDefinition/profile-operationOutcome'
JSON View
Command 'json' could not render: Resource was not found for 'canonical=http://ontariohealth.ca/fhir/ehr/StructureDefinition/profile-operationOutcome'
Note:
Operation Outcomes are sets of error, warning and information messages that provide detailed information about the outcome of some attempted system operation. They are provided as a direct system response, or component of one, where they provide information about the outcome of the operation.
OperationOutcomes are used in the following circumstances:
When a RESTful operation fails
As the response on a validation operation, to provide information about the outcomes
As part of a message response, usually when the message has not been processed correctly
You cannot have two top level headers, when header numbering is enabled.
Using Operation Outcome Resources
On the RESTful interface, operation outcome resources are only relevant when a level of computable detail is required that is more granular than that provided by the HTTP response codes. This granularity could include:
more detail about the location of an issue
the ability to identify multiple distinct issues
provision of finer error codes that connect to known business failure states
You cannot have two top level headers, when header numbering is enabled.
Consent Indicator in OperationOutcome
The OperationOutcome resource may be included in the DHDR response bundle, in response to a MedicationDispense or MedicationAdministration search request. This may indicate that MedicationDispenseor MedicationAdministration records were not included due to a patient privacy consent directive. The OperationOutcome resource will have the following values:
severity = warning
code = suppressed
OperationOutcome.issue.code ValueSet for a consent directive
Code
Display
Definition
suppressed
Information Suppressed
Some information was not or may not have been returned due to business rules, consent or privacy rules, or access permission constraints. This information may be accessible through alternate processes.
You cannot have two top level headers, when header numbering is enabled.
Temporary Consent Unblock Indicator in OperationOutcome
The OperationOutcome resource may be included in the DHDR response bundle, in response to a MedicationDispense or MedicationAdministration search request. This may indicate that there is a patient privacy consent directive, but MedicationDispense or MedicationAdministration records were included due to a patient's temporary unblock directive. The OperationOutcome resource will have the following values:
severity = informational
code = information
OperationOutcome ValueSet.issue.code for a temporaily unblocked consent directive
Code
Display
Definition
information
Informational Note
Patient has temporarily unblocked access to view and use dispense and administration information.
You cannot have two top level headers, when header numbering is enabled.
Reporting Errors in the HTTP Headers
Server may also need to report errors in the HTTP headers - especially query parameters when processing searches. Errors are reported using a case sensitive location that has two parts, a fixed "http" and the header or query parameter name separated by a ".". Some examples:
HTTP Header Parameters.
Location
Description
http.name:exact
A reference to the search parameter "name" with the modifier ":exact"
http.Authorization
A reference to the Authorization header - perhaps to indicate that it is missing, and some form of authentication is required.