Pharmaceutical software development for GxP work
DT Nova provides pharmaceutical software development for manufacturers, contract manufacturers, laboratories, distributors and life science companies that need software their quality unit can validate. We build GxP systems with the controls inspectors look for: audit trails, unique electronic signatures, access by role and documented change control. Projects run in fixed-price phases, hosting is in the EU and the code belongs to you. Buyers looking for a pharma software development company usually come to us for the gaps between their ERP, LIMS and quality systems.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Where pharmaceutical companies need their own software
Large GxP platforms cover the core of many operations: ERP, laboratory information management, manufacturing execution, document and quality management. The work that remains is often done on paper or in spreadsheets: a logbook for equipment, a calculation sheet for a process step, a tracker for deviations, an export from one system typed into another. Every one of those is a data integrity risk, and every one is a candidate for focused software built to the same standard as the large systems.
| System | Who uses it | What it replaces |
|---|---|---|
| Electronic logbooks | Production, engineering | Paper logbooks for equipment use, cleaning and maintenance |
| Batch record support | Production, QA | Spreadsheet calculations and manual checks in batch documentation |
| Quality workflows | QA | Trackers for deviations, CAPA, change control and complaints |
| Laboratory tools | QC laboratories | Manual result transcription, sample tracking, stability schedules |
| Serialisation and distribution | Packaging, supply chain | Manual handling of unique identifiers, returns and decommissioning |
| Integrations | IT, QA | Exports and re-typing between ERP, LIMS, MES and quality systems |
21 CFR Part 11: electronic records and signatures
For records the US Food and Drug Administration relies on, 21 CFR Part 11 sets the rules for electronic records and signatures. Section 11.10 requires controls for closed systems, including validation, the ability to produce accurate and complete copies for inspection, protection of records throughout the retention period, limiting access to authorised individuals, and secure, computer-generated, time-stamped audit trails that record operator entries and actions without obscuring previous information. Section 11.50 requires signed records to show the printed name of the signer, the date and time, and the meaning of the signature, such as review or approval. Section 11.70 requires signatures to be linked to their records so they cannot be excised or copied to falsify another record. Section 11.100 requires each electronic signature to be unique to one individual and never reused or reassigned; 11.200 requires at least two distinct components, such as an identification code and a password, for signatures not based on biometrics; and 11.300 sets controls for identification codes and passwords, including loss management and detection of unauthorised use (eCFR, 21 CFR Part 11, read 12 November 2026).
For drug manufacturing, 21 CFR 211.68 adds that computer systems must be controlled so that changes to master production and control records are made only by authorised personnel, and that input to and output from the system are checked for accuracy (read 12 November 2026).
EU GMP Annex 11: computerised systems
In the EU, EudraLex Volume 4, Annex 11 on computerised systems (revision January 2011, read 12 November 2026 from the European Commission's health website) asks for risk management throughout the system lifecycle, with the extent of validation and data integrity controls based on a documented risk assessment. Where third parties provide, configure, validate, maintain or host a system, formal agreements must state their responsibilities. Annex 11 also asks for audit trails of GMP-relevant changes and deletions, with the reason documented, controlled change and configuration management, and periodic evaluation to confirm that a system remains in a valid state.
We work to both texts at once: one audit trail design, one signature model, one change control process, documented so that your quality unit can map them to either rule set.
Serialisation under the Falsified Medicines rules
For prescription medicines in the EU, Delegated Regulation (EU) 2016/161, Article 4, requires a unique identifier on each pack: a product code, a serial number of at most 20 characters, a national reimbursement number where required, the batch number and the expiry date. The probability that a serial number can be guessed must be lower than one in ten thousand, and the combination of product code and serial number must stay unique for at least one year after the pack's expiry date or five years after release, whichever is longer (read 12 November 2026 via the EU Publications Office). Software around serialisation, such as generating and managing serial numbers, linking packs to batches, handling returns and reporting to the repositories system, has to respect those rules exactly.
How we build software that can be validated
- Requirements you can trace. Each user requirement has an identifier and a risk rating, and each one is traced to design, code and test.
- Risk-based testing. Testing effort follows the risk to patient safety, product quality and data integrity, in a lifecycle approach of the kind GAMP 5 describes.
- Audit trails by design. Every create, change and delete of a GxP record is logged with user, time, old value, new value and reason, and the log cannot be edited.
- Signatures that meet both rules. Two-component signing, name, date, time and meaning shown on the record, and signatures linked to the exact record version.
- Change control. No change reaches production without a recorded request, impact assessment, approval and test evidence.
- Environments kept apart. Development, test and production are separate, and production data never flows backwards without control.
Ready-made GxP software or custom?
For core functions, established products such as Veeva Vault, MasterControl, LabWare or SAP are often the right choice, because their vendors supply validation packages and your peers already use them. Custom software pays off for processes those products do not cover, for the integrations between them, and for focused tools where a large platform would cost more to configure and validate than a small system built for the job.
| Need | Ready-made platform | Custom software |
|---|---|---|
| Core quality or laboratory system | Usually the better choice | Rarely worth it |
| A paper or spreadsheet process next to the platform | Often outside the licensed modules | Small system with full audit trail |
| Data moving between systems | Exports and re-typing | Validated interfaces |
| Ownership of code and documents | The vendor's | Yours |
How the project runs
- Process and risk walk-through. With QA and the process owner, we map the process, its records and the risks to patient safety and data integrity.
- Scope and fixed price. User requirements, validation deliverables and acceptance criteria on a written scope, priced firmly for the first phase.
- Build with documentation alongside. Design, code and test documents written as the system is built, not at the end.
- Test version and qualification. Your team tests on a separate environment, test evidence is recorded, and deviations are fixed within the fixed price.
- Release and maintenance. Release under your change control, followed by a written maintenance plan and support for periodic evaluation.
You own it
Code, documentation and test evidence are stored in your own repositories and document systems from the first day. Hosting runs in an EU data region in your company's account, under a written agreement that states our responsibilities, as Annex 11 expects.
Pharmaceutical work sits next to other regulated industries we build for: see healthcare software development, medical device software development and manufacturing software development. For pharmacies rather than manufacturers, see pharmacy automation and pharmacy inventory management software; for laboratories, laboratory inventory management software. For how we work in every industry, see our custom software development company page and our bespoke software process. See prices. Send us a short brief.
Questions we get
What is GxP software?
Software that creates, changes or stores records required by good practice rules such as good manufacturing practice (GMP), good laboratory practice (GLP), good clinical practice (GCP) or good distribution practice (GDP). Because those records support decisions about medicines, the software must be validated and must protect the integrity of the data it holds.
Do you validate the software?
We build and document the software so it can be validated: requirements, risk assessment, design, traceability from requirement to test, test scripts and evidence, and change control. Validation itself is your quality unit's decision, made under your procedures; we support it with the documentation and with test execution where you want that.
Is your software compliant with 21 CFR Part 11?
Compliance is a property of the system as you use it, including your procedures, not of code alone. We build the technical controls Part 11 requires, such as audit trails, unique electronic signatures with name, date, time and meaning, signature-record linking and access controls, and document them so your quality unit can assess the whole system.
Can you integrate with our ERP, LIMS or MES?
Yes. Most pharmaceutical software is valuable because it connects to systems that already exist: ERP for batches and stock, LIMS for test results, MES for execution, quality management for deviations and CAPA, and serialisation systems for unique identifiers. Each interface is specified, tested and included in the validation scope.
Do you use GAMP 5?
We structure the documentation along a risk-based lifecycle approach of the kind GAMP 5 describes, so it fits the validation approach most quality units already use. The exact deliverables follow your own procedures.
Who owns the code and the validation documents?
Your company. Code, documentation and test evidence sit in your own repositories and document systems from the first day, so inspectors and auditors see your records, not a supplier's.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.