- This topic has 1 reply, 2 voices, and was last updated 15 years, 3 months ago by .
We have run into an issue with rescheduled orders between Imagecast and Eclipsys. The issue is that when Imagecast reschedules an order the same accession/order number is being used for the “new” order. Eclipsys can’t handle using the same accession/order number. Here is the order of things:
1) New order is placed – a “NW” order transaction is sent
2) Order is rescheduled in Imagecast – 2 transactions are sent: a “CA”
order transaction (cancelling the original order) and a “NW” order transaction (containing the new date/time).
The second “NW” has the same accession number as the first. So what happens on Eclipsys is the first order is cancelled and the second “NW” transaction errors out because of the duplicate accession number.
We have been told that it is possible for Imagecast to send a single “rescheduled” transaction, but unfortunately Eclipsys can’t handle that either.
We were just curious if anyone has encountered this same issue either with these two systems or any other systems.
- The forum ‘Cloverleaf’ is closed to new topics and replies.