You mentioned a problem with a problem message at the top of a queue that is holding up processing on the remainder of the queue. I'm told that you should delete the front queue entry.
A little more that I gathered from my conversation with the VistA HL7 team...
The VistA HL7 package (the CLASSIC that's been used for years) is being frozen; no new development, and patching only for critical problems. They are documenting known problems with the package, and work arounds. (This problem will most likely be included.) As mentioned before, they've rewritten the VistA HL7 package and are encouraging everyone to transition as soon as possible and practical.
Here's a blurb from one of the VistA HL7 developers about the new software...
Any message that won't successfully transmit after several attempts over a defined period of time is automatically taken off the queue and an error generated to the local site. This unblocks the queue, but is done in such a way to guarantee that the site isn't flooded with huge numbers of errorred messages.
Hope this helps!
LJA
There are now two different flavors of the VistA HL7 package on VistA...(1) VistA HL7 (I'll call it) CLASSIC(2) VistA HL7 NEWThe VistA HL7 package has been totally rewritten recently. I have little awareness of the features in the NEW VistA HL7 package, but will make inquiries of the VistA HL7 team.Also, will ask for their advice on your question.
On 12/22/05, Robert Leonardo <[EMAIL PROTECTED] > wrote:Larry A.,
Thanks for helping me configure the encoding characters for my interface. I have made the appropriate changes and tried sending a new message. The trouble I'm running into now is that the logical link does not give up sending the bad message (protocol requires ack) at the front of the line to let the ones behind it try to go. I have tried the purge messages function in the HL7 Main Menu but it seems to only allow me to delete messages that have been around more than a day. T-1.
Is there another way to clear out the outgoing queue?
Thanks,
Robert
