Our Digitized Mess
All Situation Room examples are constructed and not descriptions of actual events.

Published on: September 7, 2024
Walter Routh
Share This Article with the Stability Community!
What is the stability situation?
As part of our push to become a paperless stability program, we went through the past five years of paper files and scanned everything to PDF. These files were stored on a secure shared drive and can be easily retrieved by anyone granted controlled access. Scanning was a lot of work, but we’ve archived 10 lateral file cabinets of paper and made it so much easier to find information on any study. Information for all new studies is digitized similarly—all the information from manufacturing, release testing, packaging and stability logistics is “PDF’d” and filed in the same shared drive.
My concern is that, after reading the Digitized vs Digitalization article written by Susan Cleary from Novatek in this month’s newsletter (September 2024), I realize that we have digitized, but not digitalized our program. The data generated from our stability studies are housed in a Stability LIMS, but it’s not connected to the scanned information that is critical to the studies. We have to transcribe manufacturing data and release results for example, into our Stability LIMS in order to be able to include it in a report generated by the LIMS. When running statistical analyses of last year’s annual lot with the four previous years we have to collect and compile all of the relevant data into an excel report. While this is way easier and faster than it was, it’s still a delicate and error-prone process that requires verification.
How should this be resolved?
Here's one response: Unfortunately, much of the PDF information is still not going to be linkable to a LIMS, report writer or statistical system without being transcribed. If the last five years of studies are still in a Stability LIMS, I would recommend entering much of the critical parameters from the previous paper files into LIMS fields, and then working with IT to map those fields and the data to a centralized data repository. That’s a lot of additional work, but probably not more than the amount of manual verification you’re already having to do (or at least should be doing).
We Want to Hear Your Thoughts!
February 7, 2025
Upper management has a dangerously low awareness and vigilance of stability. They haven’t had a significant event or audit observation to raise alarms and put us at top of mind. As a result, we get the dregs of personnel and budget—this needs to change.
January 4, 2025
Samples swapped identities when human error caused incorrect storage conditions to be tested, but the only evidence is historical data trends. How can they prevent the error and shore up sample integrity?
December 7, 2024
When an unidentified impurity pops up on stability testing of a topical drug-containing cosmetic, internal political conflict erupts regarding filing strategies. Should they delay filing and ID the impurity or push ahead favoring the cosmetic side of the product?
Share your questions and experiences
A stabilitarian encounters new situations every day. StabilityHub’s discussion forums give Stabilitarians an opportunity to ask questions and offer solutions to specific scenarios. Join in the conversations with other Stabilitiarians and share your knowledge!
A stabilitarian encounters new situations every day. StabilityHub’s discussion forums give Stabilitarians an opportunity to ask questions and offer solutions to specific scenarios. Join in the conversations with other Stabilitiarians and share your knowledge!