Difference between revisions of "Accept Level Acknowledgement"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | {{Lore}} | ||
| + | {{INM Workitem}} | ||
| + | |||
'''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 Acknowledgement]] has been explicitely defined NOT to overlap with the functionality of the [[Commit 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 Acknowledgement]] has been explicitely defined NOT to overlap with the functionality of the [[Commit Acknowledgement]]. | ||
Revision as of 09:13, 4 July 2006
This page documents Lore, i.e. all the facts and traditions about a particular subject that have been accumulated over time, but that have not been documented in a ballot yet.
This page documents an INM Workitem, i.e. an issue within scope of the INM Committee that either is still being discussed, or the resolution of which has not yet been included in an INM ballot.
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 Acknowledgement has been explicitely defined NOT to overlap with the functionality of the Commit Acknowledgement.
Definition
An Accept Level Acknowledgement is a message-based indication by the protocol software on the receiving application as to whether the message can, or can not, be accepted.
The protocol software on the receiving system makes an initial determination as to whether or not the interaction can be accepted, based on factors such as:
- The syntactical correctness of the interaction, if the design of the receiving system includes this type of validation at this phase
- The interaction identifier, structure type identifier, version, processing code, processing mode code, if the design of the receiving system includes this type of validation at this phase.
The Sending system will determine (as conveyed in the HL7 Transmission Wrapper) whether or not an accept-level acknowledgement has to be sent by the Receiver. All receiving applications have to be able to send an accept-level error interaction should they discover an issue which prevents them from processing an interaction. All sending applications are required to be able to receive and process these accept-level interactions. (they may do this by e-mailing the system manager, or flag something in an audit file, the exact process is left up to the application).
Notes
- 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.
