> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/dragen-protein-quantification/references/documentation-revision-history.md).

# Documentation Revision History

<table><thead><tr><th width="146.22216796875">Date</th><th>Changes Made</th></tr></thead><tbody><tr><td>March 2025</td><td>Initial Release</td></tr><tr><td>May 2025</td><td><ul><li>Multiomic Walkthrough Updated</li><li>ADAT Compatibility with Excel Added</li></ul></td></tr><tr><td>June 2025</td><td><p>Release with DRAGEN Protein Quantification v2.1.0</p><ul><li><p>Changes to ADAT Content</p><ul><li>Header: Addition of Median, Q75, Q90 Intra-Plate and Inter-Plate CVs</li><li>Header: Removal of PlateRefCorr_PassFlag</li><li>SOMAmer metadata clean up</li><li>SOMAmer metadata: Removal of PassFlags for Calibration and QC: not used for analysis</li><li>Sample metadata: EmpHybTemp_PassFlag added</li><li>Sample metadata: RefCorr_PassFlag removed</li><li>Sample metadata: MedNormInt_PassFlags for serum, plasma and QC samples, and MedNormExt_PassFlags from blank and calibrator samples removed</li></ul></li><li>Updated hybridization normalization to only use calibrator and QC samples</li><li>DRAGEN Application Manager support</li></ul></td></tr><tr><td>September 2025</td><td><ul><li>Updated 6k and 9.5k SeqID lists in multiomics walkthrough</li><li>Updated SW version to v2.2.2</li></ul></td></tr><tr><td>November 2025</td><td><ul><li>Added Known Limitations page</li></ul></td></tr><tr><td>February 2026</td><td><p>Release with DRAGEN Protein Quantification v2.3.0</p><ul><li>Changes to ADAT output directory structure and filenames</li><li>Introduction of PLATE_FAIL for sample-level RowCheck_Flag</li></ul></td></tr><tr><td>August 2026</td><td><p>Release with DRAGEN Protein Quantification v3.0.0</p><ul><li>Added CSF and MultiMatrix kit support (FCR2)</li><li>Renamed Illumina Protein Prep to SomaSeq Discovery</li><li>Renamed IPPAS to SomaSeq Automation System</li><li>Updated metrics appendix with kit-type-specific thresholds and new metrics (HybQC, CrossPlateMedNormInt, PlatformSpecificQCCheck)</li><li>Added Flex Normalization documentation</li><li>Updated ADAT compatibility versions (SomaData v1.2.4 Python, SomaDataIO v6.4.0 R)</li><li>Updated sample capacity table by flowcell type</li><li>Added v1/v2 IPPAS format support (TMS and exTMS)</li><li>Fixed FAQ on multi-project splitting (multiple projects per plate allowed)</li><li>Standardized LibraryPrepKits field to SomaSeqDiscovery</li><li>Updated Override Cycles documentation</li><li>Updated pipeline URN to v3.0.0</li></ul></td></tr><tr><td>September 2026</td><td><ul><li>Documented that autolaunch always uses the latest available (at time of publishing) reference for the second calibration step (Cross Platform Calibration), including v1-to-v2 bridging when a v1 assay is analyzed with DRAGEN Protein Quantification v3.0</li><li>Added cloud demo-data sample sheets: Plasma and MultiMatrix on NovaSeq 6000, Serum on NovaSeq X</li><li>Added Bridging FAQs</li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/dragen-protein-quantification/references/documentation-revision-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.