The Architecture Brief — Life Sciences Edition | Miraki23 LLP
| Life Sciences Edition |
|
The Architecture Brief
|
|
September 4, 2026 |
|
| |
Two weeks ago we wrote about the pharma company still running its QMS on email chains and PDF sign-offs — 47 manual handoffs per CAPA, an audit trail assembled from memory whenever an investigator asked for it. That story got a version of the same response from several readers: "We already digitised our QMS. We're fine."
This week's story is for those readers. Because digitising a QMS and building an inspection-ready audit trail are not the same accomplishment — and the gap between them is where a growing number of companies are discovering, mid-inspection, that the electronic system they bought three years ago was never configured to answer the one question an FDA investigator actually asks: not "do you have a record of this," but "prove, without doubt, who touched this record, when, and why it changed."
38% of all FDA Warning Letters in 2024 cited data integrity as the primary issue. Not manufacturing. Not formulation. The paperwork behind the paperwork — and, increasingly, the electronic paperwork behind the paperwork. This week we return to Layer 3 and Layer 8 of the Pharmaceutical Digital Capability Framework with a sharper question: your QMS is digital. Is it actually defensible?
— Editorial Team · Miraki23 LLP
|
|
|
Life Sciences · Data Integrity · Audit Trail Governance
You Digitised Your QMS. You Still Failed the Mock Audit.
The system was electronic. The signatures were digital. The investigator still walked out with three data integrity observations. Going paperless was never the requirement. Being defensible was.
A mid-market pharma company ran a mock FDA audit ahead of a real one, confident in the investment they had made two years earlier: a fully electronic QMS, cloud-hosted, with digital signatures on every batch record. The mock auditor — a former FDA investigator now doing consulting work — asked for the audit trail on a single deviation record from four months prior. The system produced it in seconds. Then the auditor asked a second question: "Show me who had the administrative privilege to modify this audit trail after the fact." Nobody in the room could answer. Not because the answer was concerning — because nobody had ever been asked to define it. The audit trail existed. Its own integrity had never been governed.
This is the failure mode that a growing share of "digitised" pharma companies are walking into. The electronic QMS was purchased to satisfy 21 CFR Part 11 and EU Annex 11 on paper — the vendor's compliance datasheet says so. But Part 11 compliance is not a feature you switch on. It is a set of governed practices: audit trail review cadence, administrator privilege segregation, meaning-of-signature attestation at the point of signing, and — the piece almost every mid-market deployment skips — a documented, testable answer to "what happens if someone with system access tries to alter a record after approval." A platform can support all of this architecturally and still fail an inspection, because the organisation never configured, documented, or rehearsed the governance layer sitting on top of the software.
Four Places a "Compliant" Electronic QMS Still Fails Inspection
|
Audit Trail Never Reviewed
The system captures every event. Nobody has a defined cadence for reviewing that captured data for anomalies. A complete but unreviewed audit trail satisfies the letter of the requirement and fails the intent.
|
|
Administrator Privileges Ungoverned
The IT team retains system-level access to production QA records "for support purposes," with no segregation from QA operations and no logging of when that access is used. This is precisely the control gap investigators are trained to probe.
|
|
|
|
Signature Meaning Not Captured
An electronic signature that does not explicitly attest what the signer is confirming — reviewed, approved, witnessed — is a click, not a signature under Part 11. Many systems allow this to be misconfigured or skipped at implementation.
|
|
No Tested Tamper-Response Protocol
Nobody has ever simulated "someone attempted to alter an approved record" and traced whether the system flagged it, who was notified, and how the incident would be documented for an investigator. Untested controls are, functionally, undocumented controls.
|
|
The Regulatory Evidence
38% of all FDA Warning Letters in 2024 cited data integrity as the primary issue — not manufacturing, not formulation. Inadequate electronic records and broken audit trails remain the single most cited category, even at organisations with electronic systems already in place.
— FDA Warning Letter Data Analysis, 2024 Annual Report
The companies that pass FDA inspections calmly are not the ones who build a war room sixty days before the investigator arrives. They are the ones whose QMS was designed, from day one, to be inspection-ready every single day — where audit trail review is a scheduled operational task rather than a scramble, where administrator access is segregated and logged as a matter of routine, and where someone has already asked, and answered, "what would we show an investigator who doubted this record's integrity, right now, without preparation."
Audit-readiness is a system design decision, not a scramble — and increasingly, it is a governance decision layered on top of software that was already purchased correctly. The platform is rarely the gap anymore. The configuration and the discipline around it usually are.
|
Audit Trail Defensibility Review — Complimentary
A digitised QMS is not the same as an inspection-ready one. Let us pressure-test yours before an investigator does.
|
Start the Review →
|
|
|
|
Two Weeks Ago · Quality Management
Quality Compliance Is Your Highest-Risk Manual Process
This is the companion story. That issue covered the company still on paper and email — 47 handoffs per CAPA. This week's story is what happens after that company "solves" the problem by digitising, and discovers the harder work — governance, not software — was still ahead of them.
Read That Issue →
|
|
Last Week · Demand Sensing
Your SAP IBP Licence Cost ₹4 Crore. Your Planners Still Trust Excel.
Same underlying lesson in a different domain: a ₹4 crore forecasting platform, overridden 60% of the time, because the organisation bought the software and skipped the governance. This week's audit trail gap and last week's override rate are the same failure mode wearing different clothes.
Read Last Week's Issue →
|
|
|
| Pharma Digital Capability Framework |
|
|
Pharmaceutical Digital Capability Framework · Layer 3 + Layer 8
Manufacturing & Supply Operations + Cybersecurity & Digital Trust
9 Layers · 36 Domains · ~200 Capabilities · Sandeep Bansal, 2026
|
This week's story sits at the exact seam between Layer 3's Quality Management domain and Layer 8's Identity & Access Management domain. A digital QMS satisfies Layer 3. An inspection-ready one requires Layer 8's access governance discipline layered directly on top — because a record's integrity is only as strong as the controls governing who could have altered it.
Layer 3 · Manufacturing & Supply Operations — The Relevant Domain
|
Quality Management
Quality event management, CAPA management, deviation handling, audit management, supplier quality oversight — this is the domain where the electronic record lives, and where its integrity is either governed or assumed.
|
Layer 8 · Cybersecurity & Digital Trust — Five Domains
Layer 8 addresses the full spectrum of capabilities required to protect pharmaceutical data and preserve organisational trust. This week's mock-audit failure lived almost entirely inside its first domain — Identity & Access Management — because the question the investigator asked was, at its core, a question about who could have touched a record and whether that access was governed.
|
Identity & Access Management ★ This Week's Focus
Single sign-on, multi-factor authentication, privileged access management, identity governance and administration. This is the domain that makes every electronic signature attributable to a real, verified individual — and that governs whether IT support access to production QA records is segregated and logged.
|
|
|
Security Operations
Security information and event management, threat detection and response, vulnerability management, penetration testing — the layer that would flag an attempted tamper event in real time, if the tamper-response protocol had ever been configured and tested.
|
|
|
Data Protection
Data loss prevention, encryption management, privacy impact assessments, GDPR and CCPA compliance.
|
|
|
IP & Research Data Security
Trade secret protection, research data security, clinical data encryption, secure collaboration platforms.
|
|
|
Third-Party Risk Management
Vendor security assessments, supply chain security, partner access governance, third-party monitoring — relevant when the QMS itself is a vendor-hosted platform, and the vendor's own access controls become part of your inspection posture.
|
Map Your Layer 3 + Layer 8 Maturity →
|
|
Miraki23 Perspective
“Going paperless was never the requirement. Being defensible was. The most expensive assumption in pharma digital transformation is believing the two are the same thing.”
Aparna Bansal · Founder, Miraki23 LLP
|
|
HIS. EMR. LIS. RIS. PACS. Five systems, five acronyms.
|
|
Subscribe to the Newsletter
The Architecture Brief — Every Week
Pharma digital architecture, GxP compliance, AI governance, higher education transformation, GCC strategy, and enterprise advisory — weekly, for leaders who build, not just manage.
Subscribe Free →
|
Share on LinkedIn
Know a QA Head or Pharma CIO Who Needs This?
Share this issue with a Quality leader who assumes "we digitised the QMS" means "we're inspection-ready." Those are two different accomplishments — this issue explains the gap.
Share on LinkedIn →
|
|
|
Topics This Week
#DataIntegrity
#FDACompliance
#AuditTrail
#21CFRPart11
#PharmaCIO
#GxPCompliance
#QualityManagement
#IdentityAccessManagement
#DigitalTrust
#PharmaDigitalTransformation
#LifeSciences
#Miraki23
|
|
|