Published

A contract research organisation investigates incomplete study-document handoffs. Its quality team opens a corrective and preventive action, or CAPA, because the procedure leaves an index check unclear. The document owner revises the SOP. Quality still needs to establish which revision governed the earlier work, whether the new release met its prerequisites and whether the correction worked.
Clinical document management does not automatically replace an electronic quality management system (eQMS). Controlled content, quality events and learning records answer different questions. The model below gives the document application responsibility for the controlled release and the eQMS responsibility for the investigation, actions and closure decision.
A selected suite may provide several of those functions. For example, Veeva's Quality overview describes QMS, QualityDocs and Training applications that can work together. Compare the workflows, integrations and controls in the actual products before deciding whether separate applications are needed.
| Record or decision | Primary responsibility | Connected evidence |
|---|---|---|
| Deviation, investigation and CAPA | The eQMS and authorised quality owners. | Event, investigation findings, actions, acceptance criteria and outstanding effectiveness work. |
| Controlled procedure and revision | The controlled-document application and designated document owner. | Exact content, revision identity, review decisions, effective period and superseded history. |
| Learning and readiness | The learning system or responsible assessor under the agreed quality process. | Affected role/person, procedure revision, assigned activity, result and any required assessment. |
| Release and effective use | The document controller applying the authorised release conditions. | Accepted prerequisites, release decision, effective date and current/superseded relationship. |
| Quality-event closure | The eQMS process owner and authorised quality reviewer. | Accepted action evidence, effectiveness result, exceptions and reason for the closure decision. |
Document approval, release and CAPA closure establish different things. A draft cannot satisfy an action that requires an effective procedure. An approved revision cannot, by itself, establish completion of separate learning and effectiveness actions.
Resolve the procedure and effective revision for the event, then retain the findings and proposed action.
Connect the authorised change to the exact draft, impact assessment, decisions and release prerequisites.
Return the effective release and required learning evidence. Quality evaluates remaining actions and effectiveness before closure.
Agree the integration contract: quality-event and action IDs, controlled-document identity and revision, approved change reference, effective dates, learning assignment/result references, returned status and exception owner. These are requirements for the configured process, not a prescribed FormKiQ API schema or a claim of a supplied connector for a particular eQMS.
Match each returned result to the action it can satisfy. A generic completed-course flag without its person, activity and revision context may not answer the required readiness question. Preserve unmatched or unavailable-system cases as owned exceptions. Define how duplicate and older updates are reconciled before they change an accepted state.
In this fictional example, deviation DEV-308 concerns an incomplete study-document package transferred on April 4. Quality opens CAPA-114. The agreed actions require a clarified procedure, revision-specific learning for affected document controllers and a later check of package handoffs. These are illustrative organisational acceptance rules.
The investigation identifies SOP-DOC-12 revision 5 as effective for the April 4 transfer. The event keeps that exact reference and the relevant package evidence. A current-document shortcut must not later substitute revision 6 for the procedure being investigated.
Change CHG-27 links CAPA-114 to proposed revision 6. Reviewers assess the clarified index check, its record and the affected roles. Quality records the learning decision and release conditions; document review and approval identify the exact content proposed for issue.
Revision 6 is approved, but the example's required learning evidence is not yet complete. Keep the release awaiting its prerequisites. The eQMS can record document approval while the action requiring an effective procedure remains pending.
One returned completion refers to revision 5. Preserve it as historical evidence and resolve the unmatched revision-6 assignment. Once the agreed learning and other prerequisites are accepted, the controller makes revision 6 effective. The returned release evidence identifies the exact revision, effective date and linked action; revision 5 remains superseded history.
The document action now has its accepted evidence. The planned check of later package handoffs is still open. Quality records the observed result, evaluates it against the agreed criteria and decides whether to close CAPA-114 or require further work. Document release alone does not make that decision.
The document-change and retraining guide explains how to choose the learning response and retain readiness evidence. This example adds the eQMS action, acceptance and closure relationships around that release.
Select the accepted event evidence, historical revision 5, approved and released revision 6, matched learning results and quality decisions. Retain the source identifiers, exact versions, selection scope, export time and responsible owner. A version-specific evidence package preserves that selection when the live systems continue changing.
A reader permitted to see a current SOP may not be permitted to see the associated investigation or personal learning records. Test the configured permissions on each retrieval and export path. A document-to-event reference provides context; access still depends on the relevant controls. Share the approved inspection scope and retain the original selection when a later package revision is issued.
Agree the configured application, integrations, access controls, release rules, testing and required signature evidence with quality, security and validation owners for the intended use. This guide defines a workflow responsibility model; it does not prescribe a universal CAPA deadline, retention period or clinical procedure.
Choose document, quality-event and learning capabilities around their actual workflows. Keep the historical procedure, controlled correction, accepted learning and quality closure decision connected through specific identities and versions. Staff should be able to explain both what changed and why the quality owner considered the action complete.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.