IT systems · Practical guide

Scilife validation: documents, training and quality processes in Smart QMS

An SOP has been approved in Scilife. Training is still open, yet the linked change action is already closed. Trace the links between Smart QMS modules to establish whether this sequence is acceptable for your process. QA, IT and the process owner can use the case to scope the system and review supplier evidence for human medicinal product GMP.

Table of contents

At a glance

How do you validate Scilife for GMP use?

Validate the Scilife modules in use with your roles, document types and quality processes. Test transitions between approval, publication, training and action closure. Map supplier documentation to requirements and fill evidence gaps. Include the software scope, your configuration and how the team handles different types of release in the same assessment.

  • Name specific Smart QMS and booked modules; separate medtech and printing functions clearly.
  • Approval, publication, and training completion are distinct forms of evidence.
  • Document actions and user-defined tasks may follow different completion rules.
  • Ensure timely retention of release documentation and evaluate changes based on their actual impact.

Which SciLife and which GMP process are referred to?

Scilife uses the term "Smart QMS software" on its current pricing page. In addition, it offers products for medical devices as well as Printing and Reconciliation. The QMS packages differ as follows: Essential includes documents and training; Core adds quality events, CAPA, and Change Control; further functionalities are listed under Core+. Therefore, customers should first define their booked and activated scope; the product family alone does not constitute the validation subject.

This article examines electronic quality processes in the GMP manufacturing of human medicinal products. For this application, the relevant requirements regarding computerized systems, documentation, and personnel are decisive. Medical device development, clinical trials, or GDP require a separate assignment. FDA Part 11 is aligned with the applicable FDA recordkeeping obligations and the actual electronic use; the presence of a product logo does not establish its applicability.

Capture module statuses, environments, configured workflows, interfaces, and binding procedure instructions. A later-added module expands the scope. It is not merely a new menu item, as future GMP decisions or required records may arise therein.

Sources: [1] [9] [10] [14]

Define requirements for transfer points

A function list does not confirm whether your process works. Define requirements from the perspective of the person making decisions: Which SOP can they use today? Which training is missing? Which action prevents the closure of a change? Also document which tasks remain outside of Scilife.

The following mapping is a standalone planning aid. It does not replace a product specification. Particularly valuable are requirements whose violation would initially go unnoticed: A task may be technically completed, even if the incorrect document version was edited.

Process decision and required evidence
Process decisionSpecific requirementRelevant evidence
Use SOPs The intended user group recognizes the current version and its validity. Comparison of versions with draft, approved, and published edition.
Assign training The right personnel receive the correct document version as the training basis. Alignment of roles, training materials, and individual assignments.
Finalize the change Document responsibility and affected document changes are inherently linked. Cycle with document ID, version, starting status, and completion event.
Assess CAPA Completion of the action and assessment of its effectiveness remain distinct. Implementation justification, decision, and, if applicable, open efficacy deadline.
Find evidence The process remains traceable together with relevant relationships. Targeted retrieval of a completed process with plants and history.

Sources: [1] [3] [6]

Document approval, release, and training are separated.

The Scilife Support distinguishes between an approved, non-published document status and published status. With appropriate authorization, a document may be assigned within an approval workflow to an existing or new training session. The publication function enables scheduling or immediate publication. However, this does not constitute general evidence that every publication automatically awaits all training sessions.

Define for your SOP versions the date at which a new edition may be used and specify which personnel must have received prior training. Explicitly verify that no training assignment remains outstanding on the planned expiry date. If your environment does not technically prevent this scenario, the operational process must include an appropriate, verifiable control. A mere statement in an SOP does not eliminate an uncontrolled risk.

Also monitor stand-by personnel, new employees, and departmental transfers. The training list may appear complete, even though a newly assigned individual is missing. A read confirmation does not automatically indicate practical competence for a task. Chapter 2 of the EU GMP Guideline addresses task-specific training and the assessment of its effectiveness. Select the appropriate learning control aligned to the task, for example, an observed execution for a critical process step.

Sources: [2] [3] [12]

Further reading:

Events, CAPA, and Change Control are professionally linked

Distinguish within the process the reporting of a quality incident, its investigation, the resulting CAPA, and a planned change. Not every incident requires the same follow-up actions. Your procedures must clarify who evaluates each case and how related activities are logically linked and traceable.

Scilife defines different action types for CAPA. For document actions, the document workflow is evaluated for completion; for internal actions, responsible users close their tasks, potentially with additional QA confirmation. Review these approaches separately. Confirmation of completed tasks does not automatically validate the appropriateness of the associated equipment or the effectiveness of a CAPA.

For Change Control document task responsibilities, two publicly available support pages define different final states: publication or a approved but not yet published status. Do not unverifiedly transfer either of these end states to your environment. Confirm the rule governing your module status and perform a test with documented initial status.

The CAPA support also includes a closure pathway without a separate effectiveness verification. However, the availability of a software option does not determine GMP suitability. Chapter 1 requires monitoring and evaluation of the effectiveness of corresponding actions in accordance with Quality Risk Management principles. The procedure must provide and document an appropriate evaluation.

Sources: [4] [5] [6] [7] [13]

Which manufacturer documentation supports your validation?

For Scilife, the manufacturer's guide describes a module-based access to validation documentation. The scope and types of documents depend on the release. These documents can verify standard functions. What is essential is which of your requirements are actually covered and under what conditions the manufacturer's review was conducted.

Prepare the following mapping: Requirement, Risk, existing supplier evidence, covered configuration, and remaining checks. A passed standard test for a document signature does not necessarily confirm that the correct individuals sign on behalf of your organization or that the relevant site is properly captured. Conversely, a complete replication of supplier tests is not beneficial merely due to a different company logo.

Assess the supplier and define responsibilities. Document who performs configuration changes, who evaluates disruptions, and how data remains accessible upon contract termination. If evidence is missing, specifically identify the gap. A comprehensive package including IQ and OQ documentation is not a substitute for a traceable release of the intended operational mode.

Sources: [8] [9]

Example: A sampling SOP is amended

The following example was not executed at Scilife. An amendment to SOP-LAB-017 replaces version 3 with version 4. Two laboratory roles require the updated procedure; one office group does not. The amendment includes a documentation task and an additional task for providing new sample containers.

Before testing starts, module level, environment, user roles and output data are recorded. The desired release rule in the example is: The new process only starts when the relevant employees are trained and the vessels are available. Whether this rule is implemented technically or through additional controls is part of the specification. The table describes target checks and does not claim any existing standard lock.

Example: Test matrix for a linked change process
Test caseTesting with error or edge case scenariosExpected evidence
T1 – Document version Version 4 is approved; Version 3 remains the working basis until the specified transition date. History and user view display the intended version transition.
T2 – Training Allow an untrained laboratory user to operate; have the office group perform supervision. Missing training is evident; no unjustify ed assignment to the office group.
T3 – Document responsibility With documented starting status, the release procedure has been completed. The actual final state is consistent with the verified specification.
T4 – Own responsibility Reject the request to provide the vessel or leave it pending. The open condition remains evident and prevents professional operational release.
T5 – Unauthorized Action A user without an appropriate role attempts a authorization. The action is prevented; the authorized alternative route remains available.
T6 – Traceability Call the completed process again later. Document version, training, responsibilities, and decisions can be reconstructed together.

Sources: [3] [6] [7] [9]

Inherit existing documents and training data

Plan the takeover by data type. A valid SOP, a superseded version, a signed training certification, and an open CAPA issue carry different implications. A common file import must not obscure these distinctions. Define in advance which information is to be carried forward into the target system and which remains under control in the legacy archive.

For a SOP, the assignment typically includes, for example, old document ID, new ID, subject matter version, status, validity, owner, and training reference. Check for duplicate numbers, missing validity dates, and a previously retired signer. For historical training records, the import date must not appear as the actual training date.

Conduct a pilot run with representative edge cases. Compare content and significance, not merely file counts. A balance of 120 source documents and 120 target documents may still conceal a duplicate and a missing SOP. Use clear mappings and retain the acceptance protocol. This approach serves as a practical audit aid, not a formally authorized import function of Scilife.

Sources: [9] [11]

Verify authorizations and historical decisions

Verify authorizations using realistic test roles. This includes regular staff, document approvers, training responsible parties, and privileged users. The release assistance document outlines additional options for administrators and managers. Therefore, also consider actions outside of standard document roles.

Select a specific change for the validation test: a responsible person is replaced or a deadline is extended. Can QA later determine which version was in place, who performed the action, and on what basis the decision was made? Verify the available history and its reliability. A PDF report may suffice for a specific inspection; whether it replaces the complete retained dataset must be evaluated separately.

Additionally, agree on retrieval, backup, and restoration including vendor responsibilities and authorities. For your team, it is essential that any required procedure and its associated relationships are readable and traceable. The existence of a backup process alone does not address this requirement.

Sources: [2] [9] [11]

Scilife - Updates to be handled according to release type

The Scilife Support distinguishes clearly: for Medium and Major Releases, it specifies a provisioning in the validation environment with a minimum of 60 days between testing and production. For Minor Releases and Hotfixes, notification is provided by the same source only after the update has been completed in all three environments. Therefore, do not plan a universal pre-release testing period.

For minor changes, the manufacturer provides IQ/OQ tests and release notes; for major changes, an expanded package is supplied. As a reviewing user, you will only see the most recently published document versions in the help section. Therefore, promptly archive the supporting evidence relevant to your release in your controlled archive.

Establish a representative for the validation contact. Review new alerts for affected modules and operating procedures. In the case of a short-term fix, a subsequent impact assessment may be required; such an assessment does not constitute a retroactive update of a release. Document actual time points, findings, and required actions.

Sources: [8]

Further reading:

Checklist for Introduction and Ongoing Operation

For a SME, the main driver of effort is the number of open process decisions: different SOP types, role assignments per location, existing inventories, and linkages to actions. Identify a process owner, a system owner, and QA responsibility. Plan specific personnel engagement milestones instead of a generic project duration.

The following checklist serves as a basis for discussion regarding batch release. Open items are documented with impact, responsible party, and decision; a simple tick list alone does not constitute an appropriate operation.

  • The modules, environments, and releaseable processes employed are clearly defined.
  • Document validity and required training are aligned.
  • Closure rules for document tasks, own tasks, and CAPA are confirmed.
  • Supplier documentation is assigned; remaining risk-related testing activities have been evaluated.
  • Data transfer and representative historical records were reviewed.
  • Rights, representations, and privileged interventions are governed.
  • Hotfixes handling, update contacts, and record retention procedures are functioning.
  • Restoration, failure procedures, and subsequent data release have been clarified.

Sources: [9] [13]

Project experience and collaboration

Link the document change, training and action closure

Your team selects an SOP change. With Quality and training owners, we trace which version is approved, published and assigned to affected roles. We follow associated tasks to see whether the required work was completed or only its status changed. We map relevant manufacturer evidence and test any different approval or closure paths. The controls depend on the quality process you configured and the significance of the change.

Frequently asked questions about Scilife

Has Scilife been validated by the manufacturer?

Scilife provides module- and release-specific validation documentation. Assess the standard functions and prerequisites supported by this documentation. For your specific application, the process requirements, roles, configurations, and outstanding evidence gaps remain to be evaluated. Based on this mapping, determine which documentation is to be accepted and which additional assessments are required. A general assessment of the entire customer environment cannot be derived from the product designation alone.

Sources: [8] [9]

Which SciLife package must be included in the validation plan?

Please state the agreed-upon package and, in particular, the actually utilized modules. The current pricing overview distinguishes Essential, Core, and Core+; additional offerings include medical devices and controlled printing. A module that is not currently in use does not require a fictitious customer process. If it is later activated for GMP documentation purposes, evaluate the expansion including its integration with the existing system.

Sources: [1]

Does an approved SOP automatically mean it may be applied?

No. Scilife distinguishes between approval and release. Your operating procedures must additionally specify when the instruction is effective and which training is required. Check for an open training assignment at the release date. Do not rely on a technical training lockout, provided its existence and effectiveness have not been verified in your configuration.

Sources: [2] [3] [12]

Why does a document task remain open in change control?

Possible root causes lie in the initial document status and the processing of the approval cycle. Publicly available Scilife support materials describe varying final document states. Capture module status, task ID, document version, and status history; verify the expected rule. Do not alter the professional document workflow solely for visual clarity. A targeted repeat test generates a more robust validation evidence.

Sources: [6] [7]

Can a CAPA be closed without a effectiveness check?

A technical completion does not replace effectiveness evaluation. According to EU GMP Chapter 1, Section 1.4 (xiv), the efficacy of CAPA shall be monitored and assessed in accordance with the principles of quality risk management. Define how and when this evaluation is performed and who is responsible for assessing it. If the evaluation is conducted as part of a concurrent process or at a later date, clear assignment of responsibility and accountability must remain evident. A closed status or completion of training alone does not indicate that the root cause has been resolved.

Sources: [5] [13]

How do we verify the correct training assignment?

Select at least one affected role, one unaffected role, and one employee with altered responsibilities. Verify document version, assignment, and release documentation. Purposefully add missing training records. The number of completed trainings is not indicative of training effectiveness when the incorrect target group is assumed. For practical tasks, the selected training method must also align with the required competency.

Sources: [3] [12]

Must every update be tested beforehand within its own system?

The approach is risk-based and considers changes. At Scilife, the lead time is not uniform across all release types: for minor releases and hotfixes, the manufacturer support document specifies information following the update. Therefore, establish a practical process for impact assessment, targeted retesting, and failure escalation. One-size-fits-all pre-release testing obligations that are technically unfeasible do not serve your operations.

Sources: [8] [9]

Is it sufficient to link to the supplier's current documentation?

For a historical release justification, the risk is significant. Scilife indicates that read-only users only view the most recently published document versions. Secure the actually evaluated version with module and release reference. This enables clear explanation of the basis upon which a decision was made. Verify accessibility and readability, even in the event of a change in validation contact.

Sources: [8]

How much internal work remains upon implementation?

Your team must primarily make the technical decisions: document types, validity rules, training groups, authorization roles, and closure actions. Additionally, you must address the selection and cleansing of legacy data, as well as the evaluation of supporting evidence. Consolidate these decisions in pre-arranged workshops with QA, IT, and process owners. A fixed timeline without a clear understanding of your processes would not constitute a credible plan.

Sources: [9] [13]

What evidence should we prepare for a future supplier change?

Define the required documents, versions, signature requirements, training records, and relationships to quality processes. Clarify which exports actually enable the agreed-upon scope of functionality. Review early on a representative completed process outside the production view for readability and coherence. File export, complete archiving, and restoration are distinct tasks and require respective criteria.

Sources: [9] [11]

Sources and review date

Source status of manufacturer support documents and regulatory submissions: October 6, 2026. Publicly described functionalities and release conditions must align with the version of module in use. Specific distinctions regarding the completion of change control document tasks are explicitly defined. Test matrix and checklist are standalone work aids and do not constitute completed product testing.

  1. Scilife: Pricing & Plans
  2. Scilife: Setting a Document to Published
  3. Scilife: Assigning a Document to Trainings
  4. Scilife: Closing CAPA Actions
  5. Scilife: CAPA — Under Signing by QA
  6. Scilife: Closing Change Request Tasks
  7. Scilife: Why is the Update Document Task not closed?
  8. Scilife: Validation Documentation
  9. European Commission: EU GMP Annex 11 — Computerised Systems
  10. FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application
  11. European Commission: EU GMP Chapter 4 — Documentation
  12. European Commission: EU GMP Chapter 2 — Personnel
  13. European Commission: EU GMP Chapter 1 — Pharmaceutical Quality System
  14. European Commission: EudraLex Volume 4 — current document overview

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Your Scilife processes clearly traceable and verifiable

Daniel Herrmann Consulting supports QA and IT in defining the scope of implemented systems, evaluating existing evidence, and conducting targeted reviews of critical module interfaces.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →