I agree, possibly "conversation" is inappropriate in
this context. I would think that from the MSH's perspective,
that the referenced message is terminated, no further
retries are attempted (by the MSH, in the context of RM)
Cheers,
Chris
Dick Brooks wrote:
> David,
>
>
>
> I'm not sure I understand this statement from the spec: "...there is an
> unrecoverable error in the message and no further messages will be
> generated as part of the conversation."
>
>
>
> If a ConversationID is synonymous with a "Session" there will likely be
> multiple message exchanges, including some with ErrorList, throughout
> the course of the session. IMO, the spec should not dictate the behavior
> of a Conversation, this is application specific.
>
>
>
> It may be the intent of this statement is to indicate the "responder"
> will send no further "responses" after issuing an ErrorList. That is
> understandable. However, a client MUST be able to send additional
> request messages over the same ConversationId, after receiving
> an ErrorList response, and the server should be able to respond to these
> additional requests.
>
>
>
> Dick Brooks
> Systrends, Inc
> 7855 South River Parkway, Suite 111
> Tempe, Arizona 85284
> Web: www.systrends.com <http://www.systrends.com
> <http://www.systrends.com/>>
> Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714
>
>
>