This page is part of the FHIR Specification (v0.06: DSTU 1 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
The kind of response to a message
These codes are used in the follow places:
The following codes are defined:
| ok | The message was accepted and processed without error | |
| error | Some internal unexpected error occurred - wait and try again. Note - this is usually used for things like database unavailable, which may be expected to resolve, though human intervention may be required | |
| rejection | The message was rejected because of some content in it. There is no point in re-sending without change. The response narrative must describe what the issue is. | |
| rules | The message was rejected because of some event-specific business rules, and it may be possible to modify the request and re-submit (as a different request). The response must include an Issue report that describes what problem is | |
| undeliverable | A middleware agent was unable to deliver the message to its intended destination | |
See the full registry of codes defined as part of FHIR.
This is an old version of FHIR retained for archive purposes. Do not use for anything else
Implementers are welcome to experiment with the content defined here, but should note that the contents are subject to change without prior notice.
© HL7.org 2011 - 2012. FHIR v0.06 generated on Tue, Dec 4, 2012 00:03+1100. License