Pipeline and QC Configuration
Use Pipeline & QC Configuration to register custom pipelines, upload pipeline and QC configuration YAML files, and edit QC metric thresholds for built-in and custom pipelines.
Edit QC Metrics for a Pipeline
Configure the pipeline metrics that appear on the report and edit the default values for each metric as follows.
On the top toolbar, select Configuration, and then select the General tab.
In the left-side pane, select Pipeline & QC Configuration.
Select the applicable pipeline. QC metric configurations display to the right of the selection.
Select Edit.
To add or remove metrics from the report, select the Add to Overview & Report toggle for each metric.
To edit specification limits for applicable metrics, select the Lower Spec Limit or Upper Spec Limit fields and enter the new value. If you cannot edit a value, NA replaces the field.
[Optional] To undo all of your changes, select Reset to Default Values.
Select Save. The updated metrics appear in the Lab QC tab of the case along with the Pass/Fail designations.
Upload a Custom Pipeline Configuration
A custom pipeline is not recognized out of the box. A custom pipeline configuration YAML describes such a pipeline to Connected Insights in three respects:
What the pipeline is — its display name, version, and (optionally) its Platform Core pipeline id for cloud import.
Where each output file is — the path of every VCF, biomarker, QC-metrics, and visualization file, so Connected Insights can locate and ingest them.
How QC is assessed — the QC metrics, their pass/fail thresholds, and which of them are up-leveled to the case Results and report.
Once the file is authored and uploaded, the custom pipeline behaves like a built-in one: Results, Visualize, and Lab QC are populated, and cases can be ingested by auto upload or manual upload.
In Connected Insights, go to Configuration > General and open Pipeline & QC Configuration in the left navigation.
Select + New to open the Upload Pipeline & QC Configuration panel.
Select attached template to download a starter YAML (the same structure as the Sample Custom Pipeline YAML).
Edit the template to describe the pipeline. For the complete YAML schema, refer to Pipeline and QC Configuration YAML. For file-layout sections (
sampleSheet,jointFiles,sampleFiles), refer to Custom Pipeline Configuration.In the panel, Drag and drop the file or select Select a file, then select Upload. The file must be a single
.yamlfile no larger than 10 MB.
An existing user-uploaded configuration can be modified with Edit, retrieved with Download, or replaced with Re-upload.
Platform Core Linking and Ingestion Paths
Every uploaded custom pipeline supports local ingestion — manual upload and the Data Uploader (folder monitoring). Optionally supplying the Platform Core pipeline ids (icaPipelineId + icaUrn) also links the pipeline to Platform Core so analyses can be auto-imported or manually imported from there. These paths are not mutually exclusive: a pipeline with Platform Core ids can still be used via the Data Uploader. For details on the pipeline: block and the ICA-id pairing rule, refer to Pipeline and QC Configuration YAML.
Validation and Limitations
Connected Insights validates the file at upload. Uploads are rejected when:
The file is not a
.yamlfile, is empty, or is not valid YAML.The
pipeline:block is missing, or is missingdisplayName,name, orversion.Exactly one of
icaPipelineId/icaUrnis set (they must be supplied together or not at all).The
threshold:section has no metrics.A metric is missing its
name, is missing itstype, or uses atypeother thanRANGE/BOOLEAN.
Additional considerations:
Declare a variant file. Upload validation does not check the file layout, but a configuration with no
jointFilesimports no variants and can cause the analysis import to fail. Always declare at leastsnvFiles. For file-layout details, refer to Custom Pipeline Configuration.Unknown keys are ignored, so a typo in a key name does not raise an error — it silently drops that setting. Field spelling should be verified.
Effect on cases: a new or re-uploaded configuration applies to cases ingested after it takes effect; already-ingested cases retain their existing QC/pipeline association until re-ingested.
Test before production: there is no live schema editor — a new file should be validated in a non-production workgroup before rollout.
Last updated
Was this helpful?

