McKesson PPS ePrescribing Notification

Posts related to Medisoft Clinical go here. You should consult with your Medisoft Clinical VAR if you are unsure about any configuration changes suggested here.
Post Reply
User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

McKesson PPS ePrescribing Notification

Post by Gavin Walker » Tue Feb 15, 2011 3:44 pm

McKesson PPS ePrescribing Prescribers:

This morning, February 15th from 4:50am to 10:35am, the Practice Partner clearinghouse experienced an issue where received transactions were forwarded twice. Transactions affected include New Prescriptions and Refill Responses. This could result in error messages being returned from pharmacies indicating a duplicate transaction. These errors vary and can include the following:

• ERROR 900 - Partner rejected duplicate message Duplicate Transaction
• ERROR 900 – UIB TRACE # IS INVALID
• ERROR 602 – Internal Processing Error
• ERROR 601 – Internal Processing Error
• ERROR 601 – MessageID ####### from [mailto:######.[email protected]] has already been received

It is not necessary to re-transmit any transactions due to these errors. The first transaction sent was received by the pharmacies. No action needs to be taken on the customer’s end to resolve this issue.
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Wed Feb 16, 2011 5:44 pm

The Practice Partner clearinghouse is continuing to experience an issue where received transactions were forwarded twice. This is happening in brief, intermittent periods today.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Thu Feb 17, 2011 4:59 pm

The issue has been resolved and prescriptions are being transmitted normally now.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Mon Feb 21, 2011 3:13 pm

McKesson PPS ePrescribing Prescribers:

As you are aware, McKesson has been experiencing delays of prescription transactions due to high amount of volume they process on Mondays. They identified the root cause was they were receiving transactions faster than they could forward them to Surescripts, due to processing almost 50% more volume on Monday than any other day of the week.

Over, the past few weeks, McKesson PPS engineers have been analyzing the problem and a fix was put into place in their Clearinghouse systems on Friday, February 18th. We are pleased to report that this fix appears to have resolved the issue. Currently, today they are processing similar volume to the past few Mondays and transactions are being forwarded in a timely manner. The longest delay has been 2 minutes 15 seconds, with majority of transactions being forwarded within 15-20 seconds.

If you have any questions or concerns, please contact me.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Thu Mar 03, 2011 4:04 pm

The Practice Partner Clearinghouse is currently experiencing a technical issue with the main CH database. NewRX, Refill Response, RxHub eligibility and Fill History transactions will be rejected and prescribers will receive 601 error message. PPS Engineers are working to fix the problem as quickly as possible. Another notification will be sent when the issue is resolved.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Fri Mar 04, 2011 9:38 am

McKesson PPS ePrescribing Prescribers:

From ~11:15am PST till ~8:30pm PST, the PPS ePrescribing clearinghouse database encountered a critical problem. NewRX, Refill Responses, eligibility, and fill history transactions were all affected and 601 error messages were returned indicating timeout problems.
Currently, as of ~10:06pm PST, all transmissions have been successfully restored.
  • • Refill requests during this time were forwarded to prescribers via Surescripts fax backup services, with full electronic transmissions restored at 8:36pm PST.
    • RxHub functions (RX eligibility & Fill History) were fully restored at ~8:30pm PST.
    • New prescriptions and refill responses started being accepted from prescribers at ~8:36pm PST, and transmission to pharmacies was restored at 10:06pm PST. Transactions received during this ~90min. period were forwarded shortly after 10:06pm PST. Any transaction sent to today that received a 601 error from the Practice Partner Clearinghouse will need to be retransmitted if it hasn’t already been called or faxed to the pharmacies.
If you have any further questions, please contact us.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Mon May 23, 2011 9:58 am

Saturday May 21 from 8:21pm till 9:52pm (PDT), the Practice Partner Clearinghouse experienced a network connectivity issue with the Surescripts network. A “(503) Server Unavailable” error was being returned when trying to forward transactions to the Surescripts network.

New Rx and Refill Response transactions sent during this time were received successfully by the Practice Partner clearinghouse, queued for transmission, and transmitted when the issue was resolved. It is not necessary to resend any transactions as they were just delayed in reaching pharmacies. Refill request transactions from pharmacies via Surescripts were delayed during this time as well, however all transactions are currently being received and sent in a timely manner. Rx Eligibility and fill history (i.e. RxHub) transactions were not affected by this issue.

If you have any questions, please contact me.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Fri Jun 24, 2011 7:21 am

The Practice Partner Clearinghouse was experiencing a technical issue with the main CH database last night. NewRX, Refill Response, RxHub eligibility and Fill History transactions were being rejected and prescribers were receiving the 601 error message.

The issue has been resolved and prescriptions are being transmitted normally now. Any prescription transactions that received a 601 error need to be retransmitted.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Tue Jul 12, 2011 5:26 pm

McKesson PPS Prescribers:

The Practice Partner Clearinghouse encountered an unexpected problem related to an update change made last night. This only affected sites on versions 9.5.x. The error message below was related to this issue:

Error Code: 601
Description Code:
Description: Exception thrown calling internal function, Error:System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileLoadException: Could not load file or assembly 'PMSI.Networking.CH.Messenger.Interface, Version=9.5.2.0, Culture=neutral, PublicKeyToken=8e29483452ed690c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)…

As of 9:44 AM PDT, all systems are functioning normally and prescriptions are being transmitted to pharmacies successfully. Any prescription that received an error will need to be retransmitted. Sites on versions older than 9.5.x were not affected by this issue.

If you have any questions, please contact us.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Wed Aug 03, 2011 4:38 pm

From 10:44am PDT to 12:06pm RelayHealth encountered a connectivity problem with Surescripts. The Practice Partner ePrescribing clearinghouse forwards transactions through RelayHealth en route to Surescripts. Some prescribers may have received the following error:

An error message has been received from the SureScripts network.

Error Code: 600
Description Code:
Description: Message failed pre-processing: unable to determine/set endpoint data.
Error Code: 600

Any transactions that were sent during this period that received this error need to be re-transmitted. However, any transactions that were sent during the period that did not receive this error were transmitted to Surescripts successfully at 12:06 PDT and do not need to be resent.

If you have any questions, please private message me.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: McKesson PPS ePrescribing Notification

Post by Gavin Walker » Wed Oct 05, 2011 10:10 am

From 8:15pm to 6:13am PDT, there was a technical problem with the ePrescribing clearinghouse. The rxtx.practicepartner.com website that receives prescription transactions was down. Anyone affected by this issue would’ve received the following error message:

601 Clearing House Server Could Not Be Reached. Unable to connect to the remote server System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 208.46.235.239:443 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) Make sure you are connected to the internet and the networkingConfig.ini file is setup correctly.

The issue has been resolved and all messages are transmitting normally now. Any transactions that received this error message will need to be resent. If you have any questions please contact Technical Support.

Post Reply