The PCC 8.0 release included the all-new PCC eRx. Since the official PCC 8.0 release, PCC has rolled out dozens of updates, medication adjustments, and quick fixes to bugs that you helped us find.
Below are some of the PCC eRx updates and fixes that arrived on your system between PCC 8.0 and PCC 8.1.
May and June
Highlights from PCC eRx patches delivered in May and June include:
Faster: After the PCC 8.0 release, we tracked down many performance issues, including a “slow typing” effect and slow Rx Queue performance. We were able to improve PCC eRx performance without a full update.
Renewal Requests for Controlled Substances: Authorized prescribers can now approve or deny EPCS renewal requests. They will appear on your Rx Queue.
DNTF: The “Deny, New Request to Follow” feature for renewal requests now works as expected for electronic renewal requests on your Rx Queue. Note that DNTF does not yet work for EPCS renewals, so for now please deny and then create a new Rx instead for controlled substances.
Rx Queue History Update: When you review the Rx Queue history, you can now see more information. You’ll see details for denials or DNTF, including the patient, provider, action, and denial reason. You can also review the date a renewal request was made and responded to, and any notes to the pharmacy.
Patient Mismatch for Renewals: PCC eRx prompts you to find a patient whose name doesn’t quite match a renewal request. This process now works better and allows you to approve a pending refill prescription.
Better EPCS Token Validation: The EPCS ID-Proofing process was improved with better token ID validation.
Editing Finalized Prescriptions: It is now impossible to accidentally edit a prescription that has already been finalized and sent.
New Configuration Option for Discontinuing Medications: Your practice can decide whether you want to be prompted for the “reason for deleting” a medication, a message that appears when you delete a medication from a patient’s record. Contact your PCC Client Advocate for help with this option or other PCC eRx configuration options.
Support of Ohio Drug Reporting Requirements: Ohio pediatric practices can now generate a Daily Prescription Report from the RxQueue. They can use this report to meet Ohio’s 2-factor identification requirement.
Fix for eRx Allergies Migrated from DrFirst: If a patient had an allergy listed in the previous prescription system, and that allergy was updated or changed, under certain circumstances those changes would not appear on the patient’s Medical Summary screen. This no longer occurs.
Improved Support for Pharmacy-Initiated Renewal Requests: Under certain circumstances, it was not possible to approve a renewal request. PCC has improved how this function works.
Printing: PCC made numerous improvements to printed prescriptions between the 8.0 and 8.1 releases, including alignment and placement of practice name and margins.
Highlights from the 7/10 and 8/1 PCC eRx patches include:
Improved Support For Imported Allergy Records: Under certain circumstances, allergy data from the prior eRx system (DrFirst) was not appearing correctly. In addition, due to DrFirst’s data format, manual updates to those allergies might not sync to PCC EHR. PCC fixed these problems and updated affected clients.
Printing EPCS Prescriptions in Ohio: For a brief period after a previous patch, EPCS prescriptions could not be printed in Ohio. This issue was resolved with a quick patch.
Renewal Requests and the SurescriptsRejectionValidationFailed Error: Some renewal requests from pharmacies could not be approved, accompanied by a “SurescriptsRejectionValidationFailed”. This issue has been fixed.
Pharmacy Name Missing from Review & Sign Component: Under certain circumstances, the pharmacy name was not available when hovering over a prescription in the Review and Sign component. Now it is.
Improved Rx Queue Refresh: PCC has improved how the Rx Queue counter and list refreshes.
Retail Rx Hx Results: Due to a mismatch in identifying a pediatric practice’s location NPI, Retail Rx histories sometimes showed very few results, particularly for Provider Agents and Clinical Staff. This has been corrected.
PCC eRx 'asynchronous error': When a laptop’s internet connection failed, users would sometimes see a “An asynchronous error has occurred while processing your request” message. This has been corrected.
Formulary Info Absent: PCC eRx has improved eligibility and formulary matching and will now display formulary information when available.
Dispense Quantity: Under certain circumstances, incorrect dispense quantity could appear on a prescription. This no longer occurs.
Prescription Component Update Improved: Under certain circumstances, a patient’s prescription component would not update immediately due to a logjam of interface requests. This no longer occurs.
Prescription Interface Restoring After Down Time: If a practice’s connection to the eRx service was interrupted for more than an hour, it could encounter problems dealing with the message backlog afterwards. This process now works better.
Improved Prescription Audit report: Under certain circumstances, the Rx Audit and Audit Log reports would fail to run. This no longer occurs.
Improved Pharmacy Searching: The pharmacy search field is now more responsive. The search field also now accepts unusual characters.
August and September
Highlights from patches delivered in August and September include:
Prescription Errors Could Cause a Backlog of Updates: If a prescription was unsuccessful for some reason, prescription information could stop synching back to the patient’s chart in PCC EHR. This will no longer happen.
Inaccurate 'Patient Record Modified By Another User' Message: Prescribers would occasionally see an error message in PCC eRx stating that, “Patient record has prescriptions that have been modified by another user. Click Ok to reload the page.” This message was appearing when it should not. This issue has been fixed.
Renewal Requests with Unspecified Quantity: Renewal requests for prescriptions marked PRN, or with a dispense quantity of “Unspecified”, could result in incomplete prescriptions in the Review and Sign component that can not be completed. This issue has been fixed.
The Sleepy Search: Repeating a Search for a Medication Appeared to Freeze: If a prescriber searched for a medication and then repeated the search, under certain circumstances the search would appear to hang or freeze, unless they typed a different search. This no longer occurs.
Improved Pharmacy Search Results: Some practices had problems searching for pharmacies, due to a set of missing zip codes. We have added the new zip code information to PCC eRx’s zip code library, which will improve pharmacy searching.
Norvelt Pharmacy Rejections: Under certain circumstances, a code error caused Norvelt (and possibly other pharmacies) to reject electronic prescriptions. This no longer occurs.
Duplicate Strengths When Renewing From History: When a user renewed a prescription from the patient’s Prescription Hx or Medication Hx, it was possible to click on options in such a way that the strength appeared twice in the prescription. This will no long occur.
Incorrect Dispense Quantity: For certain medication forms (such as inhalers, patches, and pumps), conversions between dosing forms could occasionally cause the wrong dispense quantity to be sent to pharmacies. This no longer occurs.
What Updates and Fixes Are We Working On Now?
PCC’s eRx team continues to monitor and troubleshoot errors, large and small, and we will update this article to reflect the latest news of patches in the PCC 8.0 to PCC 8.1 release cycle. If you are experiencing any issues with PCC eRx, chat with your client advocate and let us know!
Here’s a list of upcoming patches that are currently in testing:
An Asynchronous Error Has Occurred: Users sometimes see a pop-up error message with the text “An asynchronous error has occurred while processing your request.” This error does not impact the prescription you are working on. It relates to PCC eRx’s update of the Rx Queue count. PCC eRx and FDB have developed a fix to this error and are testing it internally.
PCC eRx is Unavailable: Under certain circumstances, users could see a “PCC eRx is unavailable” message, and need to close and reopen a patient chart or PCC EHR to continue. This bug may also relate to problems with the Rx Queue.
Improved Rx Queue and Rx Queue Hx Query: For some practices, filtering the Rx Queue by provider was very slow, and performance and responsiveness for the Rx Queue Hx tool made it difficult to use. PCC and FDB have redesigned the software queries to optimize performance. This may also help resolve the above two error messages.
For more information about PCC eRx, visit PCC’s library of PCC eRx training videos and documentation. We add new eRx videos and materials every month.