More and more trading partners are getting their systems transitioned to accept DSCSA data. This is great news, particularly as the November 27, 2023 enforcement deadline draws ever closer. However, the flip side of implementing EPCIS is being able to navigate more complex data errors that must be cleared for business to continue.
The transaction errors that prevent an order from being received into inventory are known as exceptions, and they can be caused by common data issues, mismatches between the EPCIS data and the physical product as received, damage to packaging, or even everyday hassles like parts of a shipment arriving on different days.
Exceptions management is a critical capability under DSCSA. But don't just throw time and money at the problem; it's worthwhile to find out what resources are available to make them easier and more efficient to handle.
The difficulty of resolving exceptions can vary wildly, though across the board, they're more difficult if you don't have a robust solution for exceptions management. It's not possible for any company in the pharmaceutical supply chain to say they're invulnerable to a given error, or even a category of them. Don't get caught off-guard by writing off exceptions as minor or one-off concerns; rather, they should be a core part of your supply chain planning.
An undiscovered exception becomes increasingly difficult to resolve the further down the supply chain it is (that is, the closer a medication is to reaching the patient), due in part to the need for the receiver and sender to re-establish the chain of events in its history before they have enough information to determine how best to fix the error. As such, having thorough DSCSA protocols and procedures are important at every step in the supply chain.
Exceptions can have serious consequences, as missing transaction data, or any mismatches with the product they describe, must be resolved before a shipment can be received. This can result in temporary quarantine, return to the sender, or even destruction of the product. At the dispenser level, these can directly prevent medications from reaching patients, or cause staff to go to great lengths to source a needed medication on short notice.
Implementing DSCSA without planning for exceptions is like building a boat without planning for leaks. It's important to note that the errors that can cause an exception can go undiscovered for quite some time. For example, a case may contain 11 aggregated items when the file says it has 12, an issue where the case can change hands multiple times before someone opens it.
With an advanced solution like LSPedia's OneScan Investigator, exceptions management can be automated, helping companies proactively defend against exceptions; this, in turn, protects their partners, patients, and stress levels.
Investigator cuts the resolution time for an exception from days to minutes by alerting users to errors and guiding them through the resolution process. This enables a company to locate a problem before it can stop business, sending notifications with live hyperlinks that allow the point of contact to quickly view the issue and take the next step.
We've already established that affordable, accessible exceptions management is available; the benefit isn't just in fixing problems quickly, but in avoiding the heavy costs they can incur.
Exceptions affects all parts of the classic resource trio of labor (personnel needed), space (storage of quarantined product), and time (hours/days needed to pursue difficult issues). As such, these can be expensive slowdowns, and major headaches for receivers and senders alike. Quarantine storage requires valuable space, particularly for product that legally cannot be sold or moved through the supply chain (outside of a return) while its status is in question.
And if exception situations lead to lost product, then it needs to be re-ordered. On the patient-facing end, dispensers may need to figure out alternatives for their patients, forcing last-minute changes that can be met with suspicion. All of this takes additional staff hours to work through, with the clock ticking for the patient.
With the industry-wide adoption of tracing at the package level, data exchanges are rising at an incredible rate. This is good news for the supply chain overall -- as it's the mechanism for complete traceability -- but it brings along an according increase in exceptions, including many complex new situations for trading partners to work through under pressure.
It's possible to predict the types of exception that will occur, but not every individual variation can be predicted perfectly. That's one reason we launched the Exceptions Pilot, a cross-industry effort to document the exceptions that are arising at this pivotal moment and create a playbook of standards and procedures around them.
In short: While exceptions will become more familiar over time, they'll never be something you can ignore. To get started, contact LSPedia today.
.svg){kind=icon}
