Table of contents
At a glance
What does Chromeleon validation involve in a GMP laboratory?
Demonstrate that the installed Chromeleon configuration is suitable for the intended laboratory workflows. Assess acquisition, methods, processing, data history, access, review and retention together. The evidence applies to the particular version, instruments and interfaces in use. A supplier certificate or successful software IQ can support this assessment, but does not demonstrate the suitability of the entire laboratory process.
- Data Vault, sequence, and method versions serve as the basis for the review.
- Audit Trail Events highlight configured facts; they do not assess these professionally.
- Review queries require known test cases so that their hits can be traceable.
- CMBX-Export, long-term archiving, and reactivation of the environment are distinct tasks.
1. Clearly distinguish between version status and laboratory process
Capture the complete Chromeleon version including Maintenance Update, the Data-Vault environment, Instrument Controller, drivers, and connected devices. Add operating mode, user management, and interfaces. "Chromeleon 7" is insufficient for a reproducible demonstration of accuracy.
The manufacturers referenced in this guide cover different versions: a functional specification for section 7.3, installation documentation and release notes for section 7.4, and the document list for section 7.2.10 MUk. This does not indicate which version currently supports or is appropriate for your laboratory. Use the documentation associated with your target version and evaluate any existing deviations.
The scope begins with the intended use: Which tests are performed here, what results contribute to a batch release decision, and which data are transferred to a LIMS? Annex 11 covers GMP activities. Other GxP applications require appropriate classification; the product name alone does not establish the regulatory application area.
2. Understand the Data Vault and Sequence as a Proof-of-Structure Framework
Chromeleon organizes analytical data within Data Vaults. The manufacturer's documentation describes the sequence as a relationship comprising injections, recorded data, and associated objects such as methods and report templates. Data history and version information are also dependent on the configured environment. Therefore, documentation should not only include storage locations but also the actually activated controls.
Proceed with a representative dataset through the following mapping. It shows which question a record is intended to answer. Completeness can then be systematically verified, for example after an export, a migration into another data vault, or a restore.
| Data or Object | Question in the validation proof | Own inspection point |
|---|---|---|
| Raw signal and data capture information | What was recorded on which sample? | Verify assignment to injection and instrument. |
| Instrument Methodology | With which equipment settings was the data recorded? | Locate the actually used version. |
| Processing Method | How were peak assignment and results obtained? | Compare parameters, modifications, and calculation method. |
| Report Template and Results Presentation | What information did the auditor receive? | Filter, select and display against the dataset to verify. |
| Data and instrument histories | What changes or events explain the process? | Define appropriate sources and review period. |
Sources: [2]
3. Evaluate method changes and reprocessing separately
A change to the instrument method may affect the next data acquisition. A modified processing method impacts the analysis of captured data. A different report template may alter what a reviewer sees, without changing the raw signal. These scenarios should appear separately in your change assessment.
When reprocessing, consider both the original and the current state including justification. The Chromeleon 7.3 documentation includes version comparison and read-only access to historical objects, supporting targeted review but does not replace the professional assessment of whether a change is acceptable.
Displays also develop further depending on the version: The release notes for 7.4 describe additional information on manual integration and manual assignment in the change comparison. Therefore, do not take any screen statement from another version unchecked. It is crucial whether your team can reliably recognize and explain the relevant intervention in its environment.
4. Audit Trail Events: Separation of Configuration and Events
The manufacturer's description of Chromeleon 7.3 defines Audit Trail Events (ATE) as configurable highlighting of specific events. When creating a new sequence, the ATE configuration is inherited as a read-only template. This sequence-specific setting is critical for the subsequent capture of ATE events.
This has a practical implication: A globally updated rule applied later cannot be considered equivalent to the monitoring of all existing sequences without proper evaluation. Consider the configured event selection and the actually recorded events separately. Missing ATE matches do not constitute a blanket indication that no relevant change occurred.
As a standalone test, you may create one sequence prior to and one sequence after a batch release policy adjustment. Initiate a known, test-selected process and compare configuration, underlying history, and event representation. Explicitly document which functional level was evaluated.
Sources: [1]
5. Test known states in review queries
A query may technically be correct yet generate the wrong worklist for your team. Therefore, define the clinical selection first: Are you retrieving all submitted sequences, or only those processes whose review still remains pending?
The release notes on Chromeleon 7.4 explain a specific example: An injection query on "Sequence Signature Status = Submitted" also finds already tested or approved sequences. Additional exclusion criteria are required for a selection of only unaudited or approved operations.
Prepare intentional datasets with varying states. Compare the expected hit list with the actual selection and additionally verify access rights as well as the selected data scope. An automated list supports review when its purpose and limitations are known. It provides neither a professional assessment of notable changes nor automatic release.
Sources: [3]
6. Example: Verify altered peak assignment
The following example considers a test sequence with two adjacent peaks. An authorized person modifies the assignment window in the Processing Method following the initial evaluation. The laboratory must first define the expected assignment based on scientific rationale and establish the appropriate procedure for handling a justified change.
Review the procedure with a second party who relies solely on stored information. Can they explain what was changed and which version underlies the reported result? Also document how a rejected edit state remains traceable.
| Test scenario | Define expectations prior to test start | Suitable evidence |
|---|---|---|
| Analysis using Method Standard A | Probe, raw signal, and assignment are unambiguously linked. | Starting point and expected peak assignment |
| Change the matching window in version B | The change and its rationale are traceable compared to A. | Version comparison and data history |
| Reprocess with B | The result can be attributed to the applicable standard at the time. | Comparison of A and B including results |
| Reject a change that is not permitted | Rejection and current valid status remain identifiable. | Documented business decision |
| Perform a review query | Known open and closed cases will be appropriately selected. | Requested List, Actual List, and Filter |
| Restore sequence later | The key relationships remain verifiable. | Comparison with the original assay package |
7. Align rights and electronic signatures within the process
For Chromeleon 7.3, Thermo Fisher specifies the signature levels Submit, Review, and Approve for the electronic report in relation to the sequence. The individual whose statement must be confirmed—specifically, which person and which assertion—shall be determined by your laboratory based on technical expertise. Identify both the permitted actions and the conditions under which a confirmation is required.
Start a negative test with a routine account. Can it change an administrator-only setting or confirm something outside its authority? Also verify that the designated reviewer can see the required data. An apparently strict role matrix fails in practice if the reviewer has to use someone else's account.
Plan the correction case following confirmation. What data modification is still possible, how is it visible, and which step must be repeated? A signed copy alone does not answer these questions. Incorporate the applicable requirements for electronic signatures into your definition.
8. CMBX, archiving and full reinitialization differ
An exported sequence and a restored operational environment serve distinct objectives. For archiving, the primary concern is the future auditability of a process. For a restart, in addition to the required environment and its configuration, the restored operational setup is evaluated. The installation guidance in section 7.4, for example, addresses a local standard Data-Vault database and files as separate components.
In Section 6.2 of the 7.4 release notes, Thermo Fisher expressly advises against importing CMBX files from a newer version of Chromeleon into older releases: Unrecognized schema extensions can cause significant problems until the older Data Vault is damaged. Restriction 231359 also describes a specific case with the schema used since 7.3.2: Import may still be possible, but subsequent processing of the object is blocked. Therefore, technically possible import is not proof of appropriate backward compatibility.
Use a modified and optionally signed sequence for a restore test. Review raw data, method versions, relevant histories, and evaluation context. A PDF provides a representation; whether it fully replaces the required electronic record must be evaluated based on the dynamic information needed.
9. Distinguish manufacturer certificate from internal validation
For Chromeleon 7.2.10 MUk, Thermo Fisher provides a Certification of Validation alongside Release Notes and compatibility documentation. The listing confirms that such documentation exists for this version. It does not constitute approval of your laboratory configuration.
The software IQ also has a defined scope: According to section 7.4 Installation Guide, it compares installed files against manufacturer references and generates a report. Evaluate warnings and deviations. This documentation addresses different questions than a test of your individual review query or a calculation within the report.
Additionally, distinguish between instrument qualification and validation of the computerised laboratory workflow. The suitability of the pump and detector, correct software installation, and controlled execution of your analysis each require appropriate validation evidence. Existing supplier offerings can be strategically leveraged when their scope aligns with your specific requirements.
10. Plan the upgrade based on the affected usage
Begin with a comparison of the current and planned states. Include version and database schema, instrument drivers, used analysis functions, reports, queries, and interfaces. Evaluate relevant resolved defects as well as new features and remaining limitations.
From this, a targeted regression can be derived: for example, a method comparison, the selection of open reviews, export of results to the LIMS, and access to historical sequences. Include cases from known previous deviations. Define in advance how different results are evaluated and when laboratory operations are reauthorized.
For SMEs, it is particularly important to know who prepares these decisions. The laboratory and method responsibility holders provide representative cases; IT describes migration and the possibility of rollback; QA evaluates evidence and open items. A designated system owner consolidates scope and responsibilities. Unclear initial conditions often generate significantly more planning effort than the mere installation.
11. Checklist: Documentation for a Reliable Startup
Before scheduling meetings, compile the following information. The list serves as a practical preparation tool and must be tailored to your specific needs. Missing documents shall be recorded as open action items; they should not be replaced by general assumptions about the product.
- Capture exact software, update, driver, and instrument versions with operational overview.
- Identify GxP-related analyses, result recipients, and interfaces.
- Provide representative sequences including edited and rejected cases.
- Document data vault settings, user roles, and relevant global policies.
- Assign methods, report templates, and review questions to responsible personnel.
- Clarify the ATE-configuration and its coverage for existing as well as new sequences.
- Define archive scope, export options, target version, and recovery procedure.
- Combine supplier certifications, internal requirements, and pending tests.
Sources: [7]
Project experience and collaboration
Test the laboratory requirement against the installed Chromeleon version
With your laboratory, we select a critical workflow such as a change to processing followed by review. QA and IT identify the combination of Chromeleon version, drivers, roles and data storage in use. Suitable manufacturer documentation can support your tests. We investigate unresolved queries or version boundaries with controlled cases. For archive or version changes, we consider the permitted export and target version. The evidence should explain the intended laboratory process beyond successful software IQ.
Frequently asked questions about Thermo Scientific Chromeleon
Does the Thermo Fisher Validation Certification suffice?
It should be evaluated according to its actual content and version reference. The manufacturer's certificate can support supplier's evidence; your methods, roles, queries and data transfers need a separate assignment to requirements. Request the concrete evidence and keep in mind which questions it answers and which ones remain open.
Does automated software installation qualification (IQ) cover the whole of Chromeleon validation?
No. The IQ described in the 7.4 help checks the installation against manufacturer references. Your process questions go beyond this: Voices Transfers of results, provided rights and can the laboratory check an edited record? Use the IQ report as delimited proof and supplement the open application questions.
Sources: [5]
Are Audit Trail Events and Audit Trail the same?
ATEs are configurable event highlights within the described 7.3 function. They must be evaluated in conjunction with the underlying history. The absence of an event highlight may therefore carry a different implication than the absence of a history entry. Review both at a known process instance before relying on a review rule based on this.
Sources: [1]
Does a new global ATE setting automatically apply to each old sequence?
This should not be assumed. The manufacturer's description in section 7.3 refers to the adoption of the configuration during sequence development. Therefore, existing and newly generated sequences should be reviewed separately. Any change to the global rule requires an evaluation of the actual coverage provided by the intended monitoring.
Sources: [1]
How do we audit a worklist for open reviews?
Create known test cases with different processing and signature states. Compare the expected selection with the actual query result. Pay attention to combined criteria, access scope, and excluded states. The 7.4 documentation illustrates at the criterion "Submitted" why the colloquial meaning of a status does not always align with the full technical logic of the system.
Sources: [3]
Can peaks be retrospectively re-integrated or reassigned?
The scientifically justified framework must arise from the analytical method and the controlled processing procedure. Document the rationale, change, and decision regarding the result used. A later suitable result does not justify arbitrary adjustments. The original data and rejected processing steps must remain fully traceable to the required extent.
Sources: [8]
Does a CMBX file serve as a complete backup?
A CMBX file is not a general proof of restoration for any restoration purpose. Clarify whether you need to restore a specific sequence or the entire work environment. Thermo Fisher advises against importing files from newer releases into older versions in the 7.4 Release Notes. Select an appropriate target version that is identical or newer, and verify the actual export scope as well as version and schema compatibility. A successful file transfer does not confirm complete context or successful reactivation.
Can we retain PDF reports exclusively for an audit?
PDF reports can provide a valuable readable format. When evaluation requires dynamic data, method status, or processing histories, a reduced representation is insufficient without further consideration. Define the required documentation scope and have a reviewer reconstruct a known process from the intended archive.
Sources: [8]
What should a small and medium-sized enterprise (SME) prepare prior to its first validation?
Name the system owner, laboratory point of contact, QA, and IT. Provide a version history, representative analyses, roles, methods, reports, and existing supplier documentation. Key drivers for effort include variations, interfaces, custom evaluations, legacy inventories, and unclear workflows. Early joint inventory review enables more reliable planning than relying solely on a standard offer based on equipment count.
Sources: [7]
Must all tests be reperformed during a maintenance update?
Not automatically. Assess the actual changes and their impact on used functions, drivers, and data. From this, determine which previous justifications remain valid and which regression tests are required. Document in particular the evaluation of relevant error indications and the decision regarding re-use. The update designation alone does not justify the scope of testing.
Sources and review date
Sources opened on October 6, 2026. Function representations of Chromeleon 7.3 and older technical whitepapers are expressly distinguished from documents relating to 7.4 and 7.2.10 MUk. They are not a commitment for any version or configuration. The content of the listed MUk manufacturer certificate is not displayed here as fully checked. Test procedures are own recommendations.
- Thermo Fisher Scientific: Using Chromeleon 7.3 CDS to Comply with Regulations, PP73567
- Thermo Fisher Scientific: Chromeleon CDS Audit Trails and Ease of Review, WP72664
- Thermo Fisher Scientific: Chromeleon 7.4 Release Notes, Version 3
- Thermo Fisher Scientific: Chromeleon 7.4 Installation Guide – Rename a computer with Chromeleon 7 installed
- Thermo Fisher Scientific: Chromeleon 7.4 Installation Guide – Installation Qualification
- Thermo Fisher Scientific: Chromeleon 7.2.10 MUk Software and Documents, Document Version March 2026
- European Commission: EU GMP Annex 11, January 2011 revision
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, Final Guidance, December 2018
- eCFR: 21 CFR Part 11, Electronic Records; Electronic Signatures
Sources checked: .
Align your Chromeleon validation records to the specific intended use.
Daniel Herrmann Consulting supports you in defining the testing requirements and in integrating laboratory procedures, system configuration, and existing evidence. The starting point is your analyses and your system environment.
- 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.

