A pharmaceutical quality system may be mature for drug development, manufacturing, change control, deviations, suppliers, and regulatory operations while still lacking several capabilities required to govern a device constituent and the combination product as a whole. Treating that situation as a complete quality-system rebuild creates unnecessary duplication. Treating it as a narrow document exercise creates a different risk: the product work proceeds before responsibilities, interfaces, and evidence expectations are clear.
Begin with the complete product
The assessment should begin with the intended combination product, not with a generic checklist. The product configuration, delivery technology, user interaction, critical performance, development stage, supplier model, manufacturing network, regulatory pathway, and internal responsibilities determine which gaps matter first.
For example, a pharmaceutical organization sourcing an established delivery device may still need internal capability to define combination-product requirements, evaluate device changes, integrate use-related risk, approve supplier evidence, govern design-transfer interfaces, maintain product-level risk management, and assemble a coherent product-specific development record.
Separate three layers of readiness
1. Organizational quality-system capability
This layer includes procedures, roles, training, governance, escalation, review, change control, document and record controls, supplier oversight, and management responsibility. The question is whether the organization can govern the work.
2. Cross-company and cross-function interfaces
This layer defines how the pharmaceutical sponsor, device supplier, CDMO, testing laboratories, human-factors teams, and internal functions exchange information and make decisions. Quality agreements alone rarely define the entire development interface.
3. Product-specific execution
This layer includes the design and development plan, intended use, user needs, requirements, risk analyses, design outputs, verification and validation, human factors, manufacturing controls, supplier evidence, traceability, and submission content for the priority product.
Readiness is not achieved when a procedure exists. It is achieved when the organization can use the procedure, interfaces, responsibilities, and evidence model to execute the product work.
Prioritize by decision consequence
Not every gap should be closed at the same time. Prioritization should consider which missing capability could prevent a necessary decision, allow uncontrolled work to continue, obscure product risk, delay evidence generation, or create rework near a regulatory milestone.
A practical first wave often addresses development planning, design-control governance, product risk management, human-factors integration, supplier and partner responsibilities, requirements and traceability, design changes, and the structure of the product-specific development records.
Connect the quality system to the product record
A recurring failure mode is to create procedures in one workstream and product deliverables in another. The procedures should define the operating model; the product record should demonstrate that the operating model is being applied. Roles, states, reviews, approvals, inputs, outputs, interfaces, and evidence should align across both layers.
Use a phased resolution plan
A phased plan can distinguish immediate controls required for the priority product, near-term procedure and training work, product-specific deliverables, supplier-interface actions, and longer-term digital or enterprise improvements. Each action should have an owner, rationale, dependency, target evidence, and completion criterion.
Where QMSpace fits
QMSpace can provide a controlled environment for the product-specific records and relationships while GessNet consulting supports the quality-system, responsibility, and execution model. The software should not determine the process by itself; the configured structure should reflect the organization’s approved operating model and intended use.