Christopher R. Smith, Senior Counsel in the Health Care & Life Sciences and Litigation & Business Disputes practices, in the firm’s Washington, DC, office, was quoted in Pharmaceutical Commerce, in “HDA 2024 Traceability Seminar: A Legal Perspective Regarding DSCSA,” by Nicholas Saraceno.

Following is an excerpt:

The final day of HDA’s Traceability Seminar built off the established momentum of day one, with a panel that was centered around “Legal Perspectives for DSCSA Compliance Legal Teams,” with Ilisa B.G. Bernstein, president of Bernstein Rx Solutions, LLC as moderator.

She was joined by Jennell Bilek, equity partner, Carlson Caspers; Chris Smith, senior counsel, Epstein Becker & Green, P.C.; and Theodore Sullivan, partner, Quarles & Brady LLP, to discuss their insight on surrounding some of the more common questions that they encounter in their practice, pertaining to the management of standard operating procedures (SOPs), stabilization efforts, and plenty more.

Please note that the conversation below has been edited for length and clarity.

Bernstein: In regard to SOPs, how have you been working with your clients to implement or draft procedures, specifically when it comes to suspect and illegitimate products?

Bilek: I’m probably speaking to the choir in stating that SOPs are very valuable—not only valuable not only in terms of your employees knowing what to do, but also understanding that there's always going to be mistakes, whether it's a machine or it's a person, and it's a lot easier to negotiate and work with an agency or another private party to acknowledge that there may have been a mistake, here’s our SOP. Everyone should know this because if you're licensed—whether it be a state board of pharmacy, Department of Health, the FDA, or you have to comply with cGMP, you have SOPs in place already.

I think what DSCSA has done is just make sure to look at your SOPs and make sure that you've added the extra detail and the little nuances that have come from the Act, and when I say little nuances, just from maybe more of a legal perspective, not talking about interoperability at all, and the conflict of complexity with the data exchange that is needing to happen. If you already have SOPs in place, it involves—in my experience—tweaking them that to be a little bit more precise and detailed on things like product identifiers and non-saleable returns.

Smith: I am still amazed at the number of clients that come to me who are just getting around to wanting SOPs. I still see that. I always remain shocked by the level that exists of lack of awareness of the DSCSA even 11 years out.

Just to give it some other context for the SOP issue, if you're going through a sale of acquisition, it's to come up in diligence, increasingly these days, and if you don't even have them, there's going to be questions about whether you're really complying with the DSCSA. Is that some potential lagging liability for buying or even it isn’t, have you had any issues? Are you really practicing what you have in place? Additionally, I've seen it come up in adverse actions against entities—recruitment actions—where the lack of SOPs came up as part of the basis for payer recruitment. There are a number of contexts in which this could become important as we move forward.

Sullivan: One of the top questions in my acquisition checklist is show me your compliance SOPs. But beyond SOPs, one thing has come up with inspections is that companies will have SOPs, but they're not following them, and there's no documentation of training. It’s important to have the SOPs, train your people, and document the training.

When you develop SOPs, it does not just put you in attempt to compliance—it really does increase your understanding of the requirements. We work through SOPs, where the client. in drafting them, will come to me with questions such as, “we thought we understood this, but what does this mean once you start really digging into it?” So it'll raise attention to areas where you may not have full understanding of requirements, and actually increase your compliance beyond just the SOPs.

Bernstein: The last year has been a time where the supply chain and trade partners are supposed to be working with each other and stabilizing those connections. What have you been talking with your clients about, in terms of pilots?

Smith: I think it's beyond frustration here. The issue was highlighted by Kevin [Nicholson] and NACDS [National Association of Chain Drug Stores] in their outreach to the FDA.

Jump to Page

Privacy Preference Center

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.

Strictly Necessary Cookies

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.