Accept Level Acknowledgement
Warning: the use of the term accept-level acknowledgement is ambigious in HL7 v2. In HL7 v2 the functionality of the accept level acknowledgement is quite often combined with that of the Commit Acknowledgement. In HL7 v3 the Accept Level Acknowledgement has been explicitely defined NOT to overlap with the functionality of the Commit Acknowledgement.
An Accept Level Acknowledgement is an HL7 interaction-based indication by the protocol software on the receiving application as to whether an interaction that was received can, or can not, be accepted for further processing.
The protocol software on the receiving system makes an initial determination as to whether or not the interaction can be accepted. This process may include the following optional steps, depending on the design of the receiving system:
- Verifying the syntactical correctness of the interaction, e.g. a schema validation if the XML ITS is used.
- Verifying that the interaction identifier, structure type identifier, version, processing code, processing mode code as specified in the interaction are supported by the receiving system.
- Verifying any syntactical constraints as defined by Conformance Profiles or Realms as specified in the interaction.
The Sending system specifies within the HL7 Transmission Wrapper whether or not an accept-level acknowledgement has to be sent by the Receiver. All receiving applications SHALL be able to send an Accept Level error interaction should they discover an issue which prevents them from processing an interaction.
- An accept-level error interaction may be generated by any routing application (e.g. interface engines) or by its destination. The Sending system should process these accept-level errors as if they were sent by the Receiver. See the Abstract Transport Specification for a description of the expected behaviour of Intermediaries, Bridges and Gateways.
- Accept-level acknowledgement interactions are always sent to the sending device as contained in the Transmission Wrapper. The RespondTo class of the initial interaction is not used.