SDD Configuration
Back end configurations
Environment Variables
Environment variables and secrets are managed through Laravel Vapor. Configuration is categorized into standard variables and secrets (sensitive credentials).
Important: Variables should be changed via Deployment Console, not Vapor interface directly. Deployments are immutable - changes require redeployment.
Variable Categories Summary:
| Category | Count | Security Level |
|---|---|---|
| Application Core | 7 | Standard |
| Database (Audit) | 3 | Restricted |
| Session | 2 | Standard |
| Pusher (Real-time) | 7 | Restricted |
| Cognito (Auth) | 13 | Restricted |
| Monitoring | 5 | Standard |
| Security | 3 | Restricted |
| 2 | Standard | |
| Secrets | 10 | Highly Restricted |
Full Reference: Complete environment variable listings are documented in SDS Configuration Reference.
Client Configuration
Usage of Client configuration
Client configuration in a PCR.AI system involves setting up and customizing the system. It includes adjusting interface settings, importing configurations, and personalizing preferences to meet specific laboratory needs. The configuration covers categories such as login and user management, data import, data export, display preferences, result editing and management, Westgard settings, and showing or hiding certain features.
High Level Use Case Diagram
Import Configuration
Site-Based S3 Folder Structure
When the multi_site_feature is enabled, each site receives a dedicated S3 folder structure for run file import and export operations.
S3 Folder Hierarchy (per site):
{client-bucket}/
└── {site-name}/
├── toPcrai/ # Import folder - monitored for new run files
├── Processing/ # Temporary folder during import processing
├── Problem_Files/ # Failed imports moved here for review
├── LIMS_Reports/ # Export destination for LIMS results
└── archive/ # Successfully processed files archived here
Configuration Settings:
| Setting | Type | Description |
|---|---|---|
multi_site_feature | Boolean | Enables site-level S3 folder isolation |
s3_preserve_structure | Boolean | Preserves source folder hierarchy in archive |
s3_folder_name | String | Custom folder name override (default: site name) |
Import Flow:
- Files placed in
{site}/toPcrai/trigger S3 event notification - Lambda moves file to
{site}/Processing/during import - On success: file archived to
{site}/archive/ - On failure: file moved to
{site}/Problem_Files/with error log
Related Requirements:
- REQ-SITE-001 - Provision Storage on Site Creation
- REQ-SITE-002 - Configure S3 Structure Preservation
- REQ-FILEIMPORT-010 - Manage Import Folder Structure
Control Labels Configurations
Usage of Control Labels
Ability to specify how the run file sample label should interact with the system.
How this works
This configuration is used to establish a link between the run file label and the system Role. By employing this configuration, the system can effectively identify relevant observations
How does the user see the Control Labels Configurations?
Excel Configurations
Excel format and required data are as follows:
Sheet Name : Control Labels
| Column Names : | ROLE | ROLE TYPE | MIX | IS EXTRACTED | BACKUP MIXES | LABELS IN IMPORTED RUNFILE |
|---|---|---|---|---|---|---|
| Examples : | CC | PC | HDV | HEV | HEVF | N | CC1 | CC2 | |
| Examples : | PEC | PC | All mixes | Y | LO POS | HI POS | POS | |
| Examples : | NEC | NC | All mixes | Y | NEC | |
| Examples : | NTC | NC | All mixes | N | NTC | |
| Description : | Role name | Type of the Role | Related mixes | Is role extracted or not (Y/N) | Backup mixes | Labels in run file |
Excel Configurations
Excel format and required data are as follows:
Sheet Name : Combined Outcomes
| Column Names : | ROLE | OUTCOME TYPE | WELL ERROR CODE / LIMS CODE | TARGET ERROR CODE | TARGET TO HAVE ERROR | MIX | IC_FAILED | TARGET | RESULT | MINIMUM CT | MAXIMUM CT | MINIMUM QUANTITY | MAXIMUM QUANTITY | GROUP |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Examples : | Patient | Error | DO_NOT_EXPORT | VZV | FALSE | QVZV | Pos | 38 | 50 | 1 | ||||
| Examples : | Patient | Error | DO_NOT_EXPORT | CONTROL_CLSDISC_TARGET | SARS E gene | VZV | FALSE | QIPC | Any | 1 | ||||
| Description : | Role name Patient / Control | Outcome Type Error / LIMS | Suitable Error Code/ Lims Code | Target error code should be able to fill target level error when error typed outcome is selected and non sample type role is selected (This is optional ) | This should be able to define the target which should get the error when control typed role is selected (This is optional ) | MIX name | When applying the Combined Outcome Rule to a well, if the IC Failed option is true, an error is expected. If the IC Failed option is false, no error is expected. | Target Names | Result of the outcome (Pos, Neg, or Any) | The Minimum CT Value to trigger this | The Maximum CT Value to trigger this | for configure outcomes for targets based on observation minimum quantity | for configure outcomes for targets based on observation maximum quantity | Use for the sort by combine outcomes Group |
Alerts Configurations
The usage of the alert feature
To enhance the functionality of the Trends Report by providing the user with the ability to set and view alerts based on defined outcomes and their respective thresholds
The Alert feature serves the following purpose:
Alerts:
Alerts enable users to monitor trends data and receive notifications when configured thresholds are exceeded.
How alerts stored?
Alerts are stored in the database with the following structure:
Alert Configuration Table:
| Field | Type | Description |
|---|---|---|
| id | UUID | Unique alert identifier |
| name | String | User-defined alert name |
| condition | Enum | Comparison operator (greater than, less than, equals) |
| threshold | Decimal | Threshold value to trigger alert |
| mix_id | FK | Target mix (nullable for all mixes) |
| target_id | FK | Target target (nullable for all targets) |
| outcome | String | Outcome type to monitor |
| schedule_frequency | Enum | daily, weekly, monthly |
| rolling_period | Boolean | Use rolling time period vs fixed |
| rolling_days | Integer | Number of days for rolling period |
| enabled | Boolean | Alert active status |
| site_id | FK | Site scope (nullable for global) |
| created_by | FK | User who created alert |
| created_at | Timestamp | Creation timestamp |
| updated_at | Timestamp | Last modification timestamp |
Related Requirement: REQ-REPORTS-013
How/When Alerts are triggered?
Alerts are evaluated in two contexts:
1. After Run Analysis (Real-time)
- When a run completes analysis, relevant alerts are evaluated
- Compares current trends data against configured thresholds
- Triggers immediately if threshold exceeded
2. Scheduled Evaluation (Batch)
- Scheduled job runs at configured frequency (daily, weekly, monthly)
- Evaluates all enabled alerts against aggregated trends data
- Triggers notifications for any threshold breaches
Trigger Workflow:
- Alert condition evaluated against trends data
- If threshold exceeded:
- Create notification record in database
- Send email to configured recipients (if email enabled)
- Display in system notification area
- Notification includes: alert name, triggered value, threshold, timestamp
Related Requirement: REQ-REPORTS-014
How aggregation works?
Alerts support two aggregation modes for trends data evaluation:
1. Fixed Period Aggregation
- Evaluates data within a specific date range
- Used for point-in-time threshold checks
- Example: "Alert if positive rate > 5% this month"
2. Rolling Period Aggregation
- Evaluates data over a rolling window (e.g., last 30 days)
- Window moves forward with each evaluation
- Smooths out daily variations for trend detection
- Example: "Alert if 7-day rolling average CT > 35"
Aggregation by Scope:
- Per-Mix: Aggregate trends data filtered by specific mix
- Per-Target: Aggregate trends data filtered by specific target
- Per-Outcome: Aggregate by outcome type (Positive, Negative, etc.)
- Per-Site: Multi-site deployments can scope alerts to specific sites or global
Schedule Frequency Impact:
| Frequency | Aggregation Window | Use Case |
|---|---|---|
| Daily | Previous 24 hours or rolling N days | Rapid detection |
| Weekly | Previous 7 days or rolling N days | Trend smoothing |
| Monthly | Previous month or rolling N days | Long-term monitoring |
Related Requirement: REQ-REPORTS-013
Cross Contamination Limits Configurations
CT value thresholds used by the ADJ (Adjacent) rule to detect potential cross-contamination between adjacent wells.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Mix | The assay mix for this limit | Required, must exist in Mix configuration |
| Target | The specific target within the mix | Required, must exist for selected mix |
| Potential Contaminated | CT threshold for potentially contaminated well | Non-decimal numeric, minimum 1 |
| Potential Contaminating | CT threshold for contaminating source | Non-decimal numeric, minimum 1 |
| Quant/Ct | Mode selector (CT or Quantity) | CT: non-decimal, Quant: decimal min 0.0000000001 |
Design Notes:
- Enforces Potential Contaminated > Potential Contaminating
- Only allows adding limits for targets without existing limits
- Used by ADJ rule during analysis to flag potential contamination
- All changes logged to audit trail
Related Requirement: REQ-KITCFG-013
Curve Control Limits Configurations
Upper and lower CT bounds used by the BCC (Baseline Curve Control) rule for curve control validation.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Mix | The assay mix for this limit | Required |
| Target | The specific target within the mix | Required |
| Sample Role | The control role (e.g., CC, PEC) | Required |
| Lower Bound Ct | Minimum acceptable CT value | Positive non-zero |
| Upper Bound Ct | Maximum acceptable CT value | Positive non-zero, must be > Lower Bound |
Design Notes:
- BCC rule triggers "curve control out of expected range" error when control CT falls outside bounds
- Supports bulk addition for multiple mix/target/role combinations
- Each bound change logged separately to audit trail
Related Requirement: REQ-KITCFG-014
Delta CT Configurations
Target pairs and CT difference thresholds used by the Delta CT rule to detect unexpected variation between related targets.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Target Pair | Formatted as "Target A vs Target B" | Both targets must exist |
| Value | Maximum allowable CT difference | Positive non-zero numeric |
Design Notes:
- Delta CT rule triggers BAD_CT_DELTA error when difference exceeds threshold
- Import ignores rows with non-existent targets or empty values
- Prevents duplicate target pair configurations
- Supports Excel import/export
Related Requirement: REQ-KITCFG-019
Error Codes Configurations
Definitions and classifications of error codes used throughout the analysis workflow.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Code | Unique error identifier | String, immutable after creation |
| Message | User-facing error description | Free text |
| Type | Error classification | Classification category |
| Affects | Scope of error | Well, Target |
| LIMS Export | Include in LIMS export | Boolean |
| Control Error | Flag as control-specific | Boolean |
| Westgard Error | Flag as Westgard-related | Boolean |
| Prevents Analysis | Blocks further analysis | Boolean |
| Ignored | Hide from run file reports | Boolean |
| Causes Missing Mixes | Triggers missing mix status | Boolean |
| Inhibited | Marks as inhibition-related | Boolean |
Design Notes:
- Error codes can be ignored but not deleted (preserves historical data)
- Ignored codes hidden from run file reports
- Supports filtering by code, type, and prevents-analysis flag
- New codes require: code, message, type, affects, prevents analysis
Related Requirement: REQ-KITCFG-005
Error Resolutions Configurations
Resolution options for quality control errors, including affected wells and outcome assignments.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Error Message | The error this resolution applies to | Must exist in Error Codes |
| Resolution Message | User-facing resolution description | Free text |
| Affected Wells | Wells impacted by resolution | LIMS status, Error code, or "All Wells" |
| Rules Skipped | Rules to skip on re-analyze | Multi-select rule list |
| Outcome | Result after resolution | Configurable outcome |
| Default | Set as default resolution | Boolean |
| Affected Well Type | Type of affected wells | Configurable |
| Resolution Level | Scope of resolution | Well, All Observations, Discrepant Observations |
Design Notes:
- Resolutions grouped by error message in UI
- Supports enabling/disabling and deleting resolutions
- Supports Excel import/export with affected well type column
Related Requirement: REQ-KITCFG-006
Extractions Configurations
Extraction instrument configurations grouped by extraction model.
Data Elements:
| Column | Description |
|---|---|
| Extraction Model | Grouping category for instruments |
| Instrument Name | Individual extraction instrument identifier |
Design Notes:
- Instruments grouped by extraction model in UI
- Supports adding new models and instruments
- Model names are editable
- Instruments cannot be deleted (preserves data integrity)
- Supports Excel import/export
- All changes logged to audit trail
Related Requirement: REQ-KITCFG-003
Features Configurations
Feature visibility toggles controlling which application capabilities are available to users.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Feature Name | Identifier for the feature | System-defined |
| Enabled | Feature availability status | Boolean |
| Description | Purpose of the feature | Free text |
Design Notes:
- Part of Client Configuration category
- Used to enable/disable optional functionality per client
- Feature flags evaluated at runtime to show/hide UI elements and functionality
Related Requirement: REQ-CLIENTCFG-001
Help Items Configurations
Configuration for contextual help items and their associated tags.
Data Elements:
| Column | Description |
|---|---|
| Help Item | Help content identifier |
| Tags | Comma-separated list of associated tags |
| Content | Help text content |
Design Notes:
- Tags displayed in help items table as comma-separated list
- "No tags available for this help item" shown when no tags assigned
- Supports Excel import/export of tags via kit configuration
Related Requirement: REQ-KITCFG-028
Known Quantities Configurations
Expected quantity values for control roles used in quantification by standard curve calculations.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Role | Control role identifier | Must exist in Control Labels |
| Mix | The assay mix | Required |
| Target | The specific target | Required |
| Known Quantity | Expected quantity value | Positive numeric (rejects negative, zero, alpha, special chars, whitespace, empty) |
Design Notes:
- Used by quantification calculations for standard curve generation
- Validates quantity values strictly to prevent data entry errors
Related Requirement: REQ-KITCFG-015
Lims Exports Configurations
Mappings between LIMS export codes and outcome messages for downstream integration.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Code | Unique LIMS code identifier | String |
| Message | Associated outcome message | Supports dynamic terms: {LOQ}, {Quant}, {HIQ} |
| Type | Message classification | Exclude, Information, Warning |
| Causes Missing Mixes | Triggers missing mix status | Boolean |
| Is Inhibited | Marks as inhibition-related | Boolean |
| Does Prevent Analyse | Blocks further analysis | Boolean |
Design Notes:
- Supports dynamic LIMS terms in messages for quantity reporting
- Prompts for confirmation when closing with unsaved changes
- Code values must be unique
Related Requirement: REQ-KITCFG-009
Mix and Targets Configurations
Core assay configuration defining mixes, their constituent targets, and analysis parameters.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Mix Name | Unique identifier for the mix | Required for enabled mixes |
| Target | DNA/RNA sequence detected | Part of mix definition |
| Dye | Fluorescent dye used | Part of target definition |
| Internal Control (IC) | Target used for extraction/amplification verification | Boolean, mutually exclusive with Passive |
| Passive Target | Reference dye for normalization | Boolean, mutually exclusive with IC |
| Extraction Instrument | Associated extraction model | Optional |
| CT Inhibition Delta | IC-specific CT threshold | Positive non-zero integer, default 3 |
| Target Display Order | Sorting order within mix | Numeric, alphabetical if empty |
| Minimum Fluorescence | Min RFU threshold | Max 16 integer + 16 decimal places |
| Expected Threshold | Expected CT value | Max 3 integer + 15 decimal places |
| Max Fluorescence | Max RFU threshold | Max 16 integer + 16 decimal places, >= Min Fluorescence |
| Enabled | Mix availability status | Boolean |
Design Notes:
- Mix uniqueness determined by unique set of target/dye combinations
- Unknown mixes auto-created when imported targets don't match any configured mix
- Disabled mixes retain configuration settings but excluded from dropdowns
- Sorting: enabled mixes first (alphabetical), then disabled (alphabetical)
- Targets sorted alphabetically with IC penultimate, passive last
Related Requirement: REQ-KITCFG-001
QIR - Quantification Settings Configurations
Slope and intercept parameters used for quantification calculations.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Targets | Target(s) using these settings | Multi-select |
| Slope | Standard curve slope | Non-nullable decimal (both or neither with Intercept) |
| Intercept | Standard curve intercept | Non-nullable decimal (both or neither with Slope) |
| MinSlope | Minimum acceptable slope | Validation bound |
| MaxSlope | Maximum acceptable slope | Validation bound |
| MinEfficiency | Minimum acceptable efficiency | Validation bound |
| MaxEfficiency | Maximum acceptable efficiency | Validation bound |
| MinR2 | Minimum R² value | Validation bound |
| MinControls | Minimum controls required | Integer |
Design Notes:
- Slope and Intercept must be both filled or both empty
- Import validates non-nullable decimal values
- Supports moving targets between QIR setting rows
Related Requirement: REQ-KITCFG-018
Qualitative Reportings Configurations
Upper bound limits for quantitative groupings used by RQUANT, RQUAL, and RQUANTASQUAL reporting rules.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Mix | The assay mix | Required |
| Targets | Target(s) for this reporting | Multi-select |
| Specimen Types | Applicable specimen types | Multi-select |
| Group | Reporting group number | 1-9 for RQUANT, 1 for RQUAL/RQUANTASQUAL |
| Group Description | Description of the group | Free text |
| Upper Bound | Maximum value for this group | Numeric |
Design Notes:
- Prevents duplicate reportings for same mix/target/specimen/group combination
- Configured cut-offs used by reporting rules during evaluation
- All changes logged to audit trail
Related Requirement: REQ-KITCFG-016
Rules Mapping Configurations
Assignment of analysis rules to specific observation types based on role, mix, target, and specimen type.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Run Order | Execution sequence | Integer |
| Rule | The analysis rule | System-defined rule list |
| Type | Rule category | Classification type |
| Role | Applicable roles | Multi-select, includes "All" |
| Mix | Applicable mixes | Multi-select, includes "All" |
| Target | Applicable targets | Multi-select, includes "All", "All non-IC" |
| Specimen Type | Applicable specimen types (if enabled) | Multi-select |
Design Notes:
- Supports multi-select for role, mix, target, specimen type
- "All" and "All non-IC" options available for target selection
- Passive (reference) targets excluded from target selection
- Unused rules (no assignments) can be hidden via toggle
- Specimen type column only shown when use_sample_type config enabled
Related Requirement: REQ-KITCFG-024
Test Codes Configurations
Mappings between test codes on sample labels and specimen types.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Test Code | Code appearing on sample labels | Unique, required |
| Mix | Associated assay mix | Required |
| Specimen Type | Resulting specimen classification | Existing or new value |
Design Notes:
- Prevents duplicate test codes
- Allows selecting existing specimen types or entering new ones
- Used during run file import to classify samples
Related Requirement: REQ-KITCFG-017
Thermocyclers Configurations
Thermocycler instrument configurations grouped by thermocycler model.
Data Elements:
| Column | Description |
|---|---|
| Thermocycler Model | Grouping category for instruments |
| Instrument Name | Individual thermocycler identifier |
Design Notes:
- Instruments grouped by thermocycler model in UI
- Maintains default "Unknown" model and instrument entry
- Instruments cannot be deleted (preserves data integrity)
- Supports Excel import/export
- Can optionally auto-populate entries from imported run file data (configurable via thermocycler_auto_populate setting)
- JSON field mapping configurable via thermocycler_instrument_field setting
Related Requirement: REQ-KITCFG-004
Westgard Limits Configurations
Statistical control parameters (mean, standard deviation) for Westgard quality control rule evaluation.
Data Elements:
| Column | Description | Validation |
|---|---|---|
| Mix | The assay mix | Required |
| Target | The specific target | Required |
| Role | The control role | Must have valid control label mapping for mix |
| Range | Westgard range identifier | System-generated |
| Start Date | Range effective date | Date |
| Extraction Models | Applicable extraction models | Multi-select |
| Instrument | Extraction instrument | Optional |
| Mean | Statistical mean for the range | Editable only when no control data exists |
| SD | Standard deviation for the range | Editable only when no control data exists |
| Quant/Ct | Mode selector | CT or Quantity |
| Enabled | Range active status | Boolean slider |
Design Notes:
- Ranges with existing control data become display-only (except enabled slider)
- Mean/SD changes reset Westgard failures on re-analysis if the failure was affected by the change
- Import/export uses role name (not alias) - rows with aliases are ignored
- Role selector shows only roles with valid control label mappings for selected mix
- Disabled settings can be hidden via toggle (hide_disabled_westgard config)
Related Requirement: REQ-KITCFG-012
Dyes Configurations
Fluorescent dye definitions used in target detection.
Data Elements:
| Column | Description |
|---|---|
| Dye Name | Unique dye identifier |
| Color | Display color for the dye |
| Wavelength | Emission wavelength |
Design Notes:
- Dyes are defined as part of the mix/target configuration
- Each target within a mix is associated with a specific dye
- Dye assignments determine which fluorescence channel is read during analysis
Related Requirement: REQ-KITCFG-001 (part of mix/target configuration)
Roles Configurations
Sample role definitions used for classifying wells during run file import.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Role | Role identifier | Unique name |
| Type | Role classification | PC (Positive Control), NC (Negative Control), Sample, Ignore, Quantitative |
| Is Extracted | Extraction control flag | Boolean |
| Labels | Matching labels in run files | Pipe-separated list, supports wildcards |
| Mix | Associated mix | Required |
| Backup Mixes | Failover mixes | Optional, pipe-separated |
| Resolution Priority | Priority for resolution matching (when enabled) | Integer |
Design Notes:
- Roles are managed through Control Labels configuration
- Wildcard patterns supported in label matching (case-insensitive)
- Role aliasing and remapping supported
- Can be excluded from IC delta check
- Resolution priority column shown when use_role_priority_resolution config enabled
Related Requirement: REQ-KITCFG-007
Rules Configurations
Rule execution settings including error well handling and precedence order.
Data Elements:
| Column | Description | Values |
|---|---|---|
| Rule | Rule identifier | System-defined |
| Type | Rule category | Classification type |
| Is Allow Error Wells | Execute against wells with errors | Boolean |
| Precedence Order | Execution priority within type | Integer |
Design Notes:
- "Is Allow Error Wells" controls whether rule runs against error-flagged wells
- Precedence changes automatically reorder affected rules within type category
- Precedence changes take effect immediately for subsequent rule executions
Related Requirement: REQ-KITCFG-025
Westgard Events Configurations
Event codes and messages generated by Westgard rule violations.
Data Elements:
| Column | Description |
|---|---|
| Event Code | Unique identifier for the Westgard event |
| Message | User-facing description of the violation |
| Rule | Associated Westgard rule (1:2S, 1:3S, 2:2S, 7T, etc.) |
| Severity | Event severity level |
Design Notes:
- Westgard events are generated when control measurements violate statistical boundaries
- Events tied to specific Westgard rules (see sdd-algorithms.md for rule definitions)
- Part of the overall Westgard quality control configuration
Related Requirement: REQ-KITCFG-012 (part of Westgard settings)
Specimens Configurations
Specimen type definitions used for sample classification and reporting.
Data Elements:
| Column | Description |
|---|---|
| Specimen Type | Unique specimen identifier |
| Description | Specimen type description |
Design Notes:
- Specimen types are used by:
- Rule mappings (when use_sample_type enabled)
- Reporting cut-offs (RQUANT, RQUAL, RQUANTASQUAL rules)
- Test code mappings
- Can be created via Test Codes configuration or directly
- Specimen type filtering available in multiple configuration screens
Related Requirements:
- REQ-KITCFG-016 (Reporting Cut-offs)
- REQ-KITCFG-017 (Test Codes)
- REQ-KITCFG-024 (Rule Mappings)
Related SRS Requirements
The following SRS requirements are implemented by the design described in this document:
| Requirement | Domain | Description | Relevance |
|---|---|---|---|
| REQ-CLIENTCFG-001 | Client Configuration | View and Edit Client Configuration Settings | This SDD documents the client configuration usage and categories that REQ-CLIENTCFG-001 manages |
| REQ-CLIENTCFG-002 | Client Configuration | Export Client Configuration | Environment variables and configuration data documented here support export functionality |
| REQ-CLIENTCFG-003 | Client Configuration | Import Client Configuration | Configuration schema documented here defines importable settings |
| REQ-KITCFG-007 | Kit Configuration | Manage Control Labels | Control Labels Configurations section documents Excel schema and role mapping design |
| REQ-KITCFG-011 | Kit Configuration | Manage Combined Outcome Rules | Combined Outcomes Excel schema section documents the configuration data format |
| REQ-KITCFG-012 | Kit Configuration | Manage Westgard Settings | Westgard Limits Configurations section documents Westgard parameter management |
| REQ-KITCFG-013 | Kit Configuration | Manage Cross Contamination Limits | Cross Contamination Limits Configurations section documents this requirement |
| REQ-KITCFG-014 | Kit Configuration | Manage Curve Control Limits | Curve Control Limits Configurations section documents this requirement |
| REQ-KITCFG-019 | Kit Configuration | Manage Delta CT Configurations | Delta CT Configurations section documents this requirement |
| REQ-KITCFG-005 | Kit Configuration | Manage Error Codes | Error Codes Configurations section documents error code management |
| REQ-KITCFG-006 | Kit Configuration | Manage Error Resolutions | Error Resolutions Configurations section documents resolution configuration |
| REQ-KITCFG-028 | Kit Configuration | Manage Help Item Tags | Help Items Configurations section documents help item management |
| REQ-CONFIGIO-004 | Config Import/Export | Import and Export Combined Outcomes Configuration | Combined Outcomes Excel schema directly supports import/export validation |
| REQ-CONFIGIO-005 | Config Import/Export | Import and Export Control Labels Configuration | Control Labels Excel schema directly supports import/export validation |
| REQ-CONFIGIO-011 | Config Import/Export | Validate Westgard Limits on Import | Westgard Limits Configurations section relates to import validation |
Notes on Completed Sections
All configuration sections in this SDD have been populated from SRS requirements or SME input. The Alerts subsections were populated from REQ-REPORTS-013 and REQ-REPORTS-014 in the Reports SRS.