Engineering reliability into a critical pharmaceutical workflow

Global pharmaceutical company

Industry

Life Sciences

Service

Engineering & DevOps

Summary

  • Takeaway

    Printer configurations reviewed

    Nearly 2,000 records evaluated to identify inconsistencies before deployment.

  • Takeaway

    63% of configurations flagged for review

    Unverified records held back to prevent inaccurate configurations from entering production.

  • Takeaway

    5-minute automated status checks

    Print jobs checked automatically to identify failures and prevent missed errors.

Hero pharma 1440x810 background 2

Overview

A global pharmaceutical company partnered with 8th Light to modernize a critical document-printing workflow across its regulated operations. What appeared to be a simple integration carried significant complexity: every printed document needed to be traceable, but disconnected systems and inconsistent printer configurations made it difficult to verify outcomes and maintain reliable records.

Drawing on its experience engineering software for highly regulated industries, 8th Light built verification into the workflow itself. Automated status checks, failure alerts, and a repeatable data validation process helped prevent errors from going unnoticed, with 63% of printer configurations flagged for further review before entering production. The result is a more dependable, auditable process designed to support compliance and future scale.

The Engagement, In Brief

For a global pharmaceutical company, even something as routine as printing a document came with strict compliance requirements. Every controlled copy needed to be traceable, from the approved document version to the printer, recipient, and time of issuance.

The challenge was that the process relied on several connected systems, each with its own potential points of failure. A print job could be accepted without ever being completed, while inconsistent printer configurations across sites introduced additional uncertainty.

8th Light brought an approach shaped by its experience building software in highly regulated environments. Rather than simply connecting the systems, the team focused on making each critical step visible, verifiable, and accountable. The goal was to create a dependable workflow that could meet compliance requirements without introducing unnecessary operational complexity.

The result was a controlled-print service now in production at a client site, supported by automated verification, more reliable configuration data, and an architecture designed to accommodate future growth.

Here's how:

  • Verify the outcome, not just the request. Track print jobs through completion instead of assuming that an accepted job means a successful print.
     
  • Catch problems before they reach production. Validate printer configurations against the systems of record and hold back information that can't be verified.
     
  • Make failures visible and actionable. Build automated status checks, persistent records, and alerts into the workflow so teams can investigate issues quickly.
     
  • Design for the next stage of growth. Prepare a separate, cache-first architecture to handle increased document-rendering demand without overwhelming existing systems.

The Challenge

When routine workflows carry outsized risk.

In a surgical operating room, teams rely on systematic checks to make sure critical steps aren't missed. The principle is straightforward: when the consequences of an error are high, you don't leave success to assumption.

The same principle applies to software systems, particularly when critical workflows depend on multiple technologies working together.

For this pharmaceutical company, that challenge surfaced in an unexpected place: printing documents.

It looked like a simple integration. Retrieve an approved document from a quality management system and send it to a printer.

But in a regulated pharmaceutical environment, every controlled copy must be accounted for. The organization needed to know which version was printed, where it was printed, when it was issued, and who received it to support Good Practice (GxP) compliance requirements, a set of quality standards governing regulated pharmaceutical operations.

The problem was that a print job could appear successful without the document ever reaching the printer. And with different printer setups across sites, figuring out what went wrong wasn't always straightforward.

What should have been a routine process introduced opportunities for errors, incomplete records, and time-consuming investigation.

The challenge wasn't simply getting documents to print. It was creating a process the organization could depend on without having to continually question whether it worked.

The Approach

Building reliability into every step.

When critical workflows cross multiple systems, reliability depends on more than whether each individual component works. You need to know that the entire process worked as intended.

Through our experience building software in highly regulated industries, including finance and insurance, we've learned that the best way to achieve this is to make each step visible, verifiable, and accountable. That means designing systems that can confirm outcomes, catch failures, and provide a clear record of what happened.

We brought that same thinking to the pharmaceutical client's printing workflow. Rather than simply connecting its document management and printing systems, we looked at where the process could break down and built safeguards into the workflow itself.

Our approach focused on two things: confirming that print jobs actually completed and making sure the printer configurations supporting those jobs were accurate before they entered production.

1. Verify outcomes instead of assuming success

A print server accepting a job doesn't mean the document actually printed.

8th Light built a controlled-print service that independently checks the status of submitted jobs every five minutes, records their outcomes, and alerts the team when something fails.

By connecting those results back to the company's quality management system, the service creates a more dependable record of each controlled document. Rather than allowing failures to go unnoticed, the workflow makes them visible so the team can investigate and respond.

2. Catch problems before they reach production

Reliable software also depends on reliable inputs.

When 8th Light examined printer configuration data collected from sites across the organization, the team discovered that much of it couldn't be trusted without further validation.

Across 62 submitted spreadsheets, the team reviewed 1,937 printer configuration records. Only 37% could be verified as accurate and ready for use.

Instead of importing questionable data and addressing problems after deployment, 8th Light developed a repeatable validation process. Unverified configurations were held back, discrepancies were identified, and sites received targeted questions to resolve outstanding issues.

The result was a more controlled onboarding process designed to prevent avoidable configuration errors from entering production.

The Impact

A dependable process, without the guesswork.

The controlled-print service is now in production at a client site, providing a more reliable foundation for regulated document printing. The engagement demonstrates how a verification-first engineering approach can turn a routine but high-stakes process into a more manageable, accountable system.

Greater confidence in critical operations

Print jobs can now be tracked beyond submission, with status information recorded in the quality management system and failures surfaced for investigation.

Less risk from inconsistent data

A repeatable validation process helps ensure only verified printer configurations enter the system, reducing the risk of errors caused by inaccurate or incomplete information.

A foundation for future scale

8th Light also designed a separate document-rendering architecture to prepare for a planned increase in demand. The proposed solution uses caching to reduce repeated requests to the underlying document platform while protecting shared infrastructure.

Performance testing and deployment remain future steps.

 

The Takeaway

Build verification into the system, not around it.

The controlled-print workflow shows how much engineering rigor can matter in even the most routine business processes. By making critical steps visible and verifiable, 8th Light helped the company establish a more dependable process without relying on assumptions about whether individual systems had completed their work.

For organizations managing complex, regulated technology environments, that same approach can help reduce uncertainty, improve accountability, and make critical workflows easier to operate and maintain.

 

Build software that holds up in production.

8th Light helps organizations modernize complex systems, improve reliability, and build software they can depend on.

Spark a Conversation →