TransportShockAndTemperatureLoggerQC
Transport Shock & Temperature Logger QC
Utility description: Transport Shock & Temperature Logger QC
Transport Shock & Temperature Logger QC — Xenon Transport Data Logger Analyzer
ℹ️ Utility checks transport condition recorder data:
• Maximum and minimum temperature
• Peak shock loads (G-force)
• Number of shock events
⚠️ CRITICAL: Overheating increases cylinder pressure!
Strong impacts can damage shut-off valves or internal coating.
Usage:
TransportShockAndTemperatureLoggerQC.exe → demo mode (console output)
TransportShockAndTemperatureLoggerQC.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,ProductName,Max_Temp,Min_Temp,Avg_Temp,Max_Shock_G,Shock_Count,Max_Allowed_Temp,Min_Allowed_Temp,Max_Shock,Max_Events
Example:
TRANS-2026-001,HP-Xe-129,28,15,22,2.5,1,40,5,5,3
— WHY IS THIS NEEDED?
Transport condition control is critical for HP-Xe safety and quality:
• Xenon is stored under pressure; overheating can lead to safety valve activation or rupture
• Sharp impacts can damage expensive shut-off valves or compromise seal integrity
• For HP-gas vials, impacts can destroy fragile anti-relaxation internal coating
• Low temperatures can cause moisture condensation or seal freezing
• Logger data serves as legal proof of delivery condition compliance
⚠️ CRITICAL:
• Temperature must not exceed 40°C (standard for most gas cylinders)
• Temperature must not drop below 5°C (seal risk)
• Shocks must not exceed 5G (for standard packaging)
• Number of significant shocks must be minimal (<3)
Key features:
• Peak temperature and shock value analysis
• Shock event frequency counting
• Temperature regime compliance check
• Rough handling detection
Critical parameters:
• Max Temp: ≤40°C
• Min Temp: ≥5°C
• Max Shock: ≤5G
• Shock Events: ≤3
💡 Usage tips:
1. Place loggers near cylinder valve (most vulnerable part)
2. Use shock-proof cases for HP-gas vial transport
3. If limits exceeded, necessarily perform leak test (sniffer test) before use
4. Save logger reports as part of batch documentation (DHR)
5. Calibrate loggers before each shipment
⚠️ Note: Unlike standard drugs where temperature affects chemical stability over months, here physical conditions affect mechanical integrity and pressure safety instantly. The utility helps prevent catastrophic equipment failures during gas commissioning.input.csv
BatchNumber,ProductName,Max_Temp,Min_Temp,Avg_Temp,Max_Shock_G,Shock_Count,Max_Allowed_Temp,Min_Allowed_Temp,Max_Shock,Max_Events TRANS-2026-001,HP-Xe-129 Cylinder (Air Freight),28,15,22,2.5,1,40,5,5,3 TRANS-2026-002,HP-Xe-129 Cylinder (Rough Handling),45,10,28,8.0,5,40,5,5,3 TRANS-2026-003,HP-Xe-129 Cylinder (Cold Chain Fail),25,-5,10,1.0,0,40,5,5,3
URS & FS — user requirements and functional specification
URS & FS — User Requirements and Functional Specification
This document defines the controlled interface and behaviour of TransportShockAndTemperatureLoggerQC for “Transport Shock & Temperature Logger QC”. Limits from the source description are an initial configuration and shall be reconciled with the approved specification, study protocol, equipment instructions and local SOPs before production use.
Domain constraints and critical parameters
- Max Temp: ≤40°C
- Min Temp: ≥5°C
- Max Shock: ≤5G
- Shock Events: ≤3
URS — User Requirements Specification
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The utility shall accept input.csv with the exact headers defined by the data contract. | High | The file is processed without manual header renaming. |
| URS-002 | The utility shall perform a deterministic assessment for “Transport Shock & Temperature Logger QC”. | High | PASS / WARNING / FAIL is produced for each row. |
| URS-003 | Required fields, types, ranges, units and data consistency shall be validated before domain rules. | High | Schema errors are separated from nonconformities. |
| URS-004 | Critical limits from the description and approved local configuration shall create a critical finding. | High | A critical rule violation results in FAIL. |
| URS-005 | The result shall be written to machine-readable output.json. | High | JSON contains source values, checks, warnings and failures. |
| URS-006 | The conformity decision shall not use machine learning. | Medium | The result is reproducible from explicit rules and inputs. |
| URS-007 | Traceability of batch, source file, rule version and final status shall be retained. | High | QA/QC can reproduce the decision. |
| URS-008 | The utility shall have exactly one primary portal tag: medical_devices. | Medium | The other api / instrumental / medical_devices tags are absent. |
| URS-009 | Documentation shall support IQ/OQ/PQ or equivalent CSA/CSV verification. | Medium | The contract, test scenarios and change-control rules are supplied with the utility. |
input.csv data contract
| # | Field | Type | Unit | Sample | Purpose |
|---|---|---|---|---|---|
| 1 | BatchNumber | string | as specified | TRANS-2026-001 | Batch/lot identifier for traceability. |
| 2 | ProductName | string | as specified | HP-Xe-129 Cylinder (Air Freight) | Name of the controlled product, gas, procedure or equipment. |
| 3 | Max_Temp | decimal | as specified | 28 | Storage, transport or process temperature parameter. |
| 4 | Min_Temp | decimal | as specified | 15 | Storage, transport or process temperature parameter. |
| 5 | Avg_Temp | decimal | as specified | 22 | Storage, transport or process temperature parameter. |
| 6 | Max_Shock_G | decimal | G | 2.5 | Controlled input.csv field: Max Shock G. |
| 7 | Shock_Count | decimal | °C | 1 | Controlled input.csv field: Shock Count. |
| 8 | Max_Allowed_Temp | decimal | as specified | 40 | Storage, transport or process temperature parameter. |
| 9 | Min_Allowed_Temp | decimal | as specified | 5 | Storage, transport or process temperature parameter. |
| 10 | Max_Shock | decimal | as specified | 5 | Controlled input.csv field: Max Shock. |
| 11 | Max_Events | decimal | as specified | 3 | Controlled input.csv field: Max Events. |
BatchNumber,ProductName,Max_Temp,Min_Temp,Avg_Temp,Max_Shock_G,Shock_Count,Max_Allowed_Temp,Min_Allowed_Temp,Max_Shock,Max_Events TRANS-2026-001,HP-Xe-129 Cylinder (Air Freight),28,15,22,2.5,1,40,5,5,3 TRANS-2026-002,HP-Xe-129 Cylinder (Rough Handling),45,10,28,8.0,5,40,5,5,3 TRANS-2026-003,HP-Xe-129 Cylinder (Cold Chain Fail),25,-5,10,1.0,0,40,5,5,3
FS — Functional Specification
| ID | Function | Implementation |
|---|---|---|
| FS-001 | CLI execution | TransportShockAndTemperatureLoggerQC.exe supports demo mode and input.csv output.json mode. |
| FS-002 | CSV import | Read UTF-8 CSV and validate header, column count and order. |
| FS-003 | Schema validation | Validate required values, empties, types and basic plausibility. |
| FS-004 | Domain rule engine | Apply explicit rules for “Transport Shock & Temperature Logger QC” and locally approved limits. |
| FS-005 | Status aggregation | FAIL for a critical finding; WARNING for a non-critical deviation; PASS for conformity. |
| FS-006 | JSON export | Write source values, applied rules, statuses, warnings, failures and configuration version. |
| FS-007 | Audit support | Retain a result structure suitable for review, investigation, IQ/OQ and change control. |
| FS-008 | Integration contract | LIMS/ELN/MES or an instrument wrapper creates CSV; the utility returns JSON. |
output.json example
{
"utilityId": "transport-shock-and-temperature-logger-qc",
"primaryTag": "medical_devices",
"overallStatus": "PASS|WARNING|FAIL",
"sourceFile": "input.csv",
"checks": [
{
"parameter": "BatchNumber",
"value": "TRANS-2026-001",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "ProductName",
"value": "HP-Xe-129 Cylinder (Air Freight)",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Max_Temp",
"value": "28",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Min_Temp",
"value": "15",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Avg_Temp",
"value": "22",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Max_Shock_G",
"value": "2.5",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Shock_Count",
"value": "1",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Max_Allowed_Temp",
"value": "40",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
}
],
"warnings": [],
"criticalFindings": []
}
OQ/PQ test scenarios
| ID | Scenario | Expected result |
|---|---|---|
| OQ-001 | Valid example row | PASS or an allowed WARNING under local rules. |
| OQ-002 | Required column missing | Schema error; domain checks do not mask it. |
| OQ-003 | Non-numeric value in numeric field | Type-conversion error. |
| OQ-004 | Critical parameter outside its limit | FAIL and a critical finding. |
| OQ-005 | Boundary value | The result follows the configured ≤ / ≥ / < / > operator. |
| PQ-001 | Real site data | Agreed QA/QC review retaining CSV, JSON, version and checksum. |
QA/QC and change control
- Do not change column names without updating the validator, documentation and test set.
- Retain input.csv, output.json, executable version, rule version and checksums.
- Before production use, verify local limits and execute IQ/OQ/PQ or equivalent CSA.
- Changes affecting patient safety, dosimetry, gas composition, polarization or equipment require documented impact assessment.
Included in packages
Rph Hyperpolarized Xenon Lifecycle QC Suite
29 utilities for the hyperpolarized xenon lifecycle: isotope composition and gas purity, SEOP and polarization, T1/storage/transport, safe blending and delivery, MRI/SPECT QC, dosimetry, scavenging, recovery and recycling.
OpenRPH isotope family: xenon and gas tracers
Xe-127, Xe-129 and Xe-133 for ventilation, hyperpolarized imaging, gas QC and safety.
OpenRPH organ/system: hepatobiliary and GI
HIDA, mebrofenin, gallbladder, gastric emptying, GI transit, bleeding and liver/spleen imaging.
OpenRPH organ/system: pulmonary and ventilation
Lung perfusion, MAA, V/Q, aerosol, xenon ventilation, shunt and pulmonary dosimetry.
OpenRPH use case: xenon, ventilation and medical gases
Xe-129, Xe-133, Xe-127, hyperpolarization, SEOP, T1, mixing, scavenging, transport, recovery and ventilation imaging.
OpenRPH workflow: stability, storage, decay and waste
Kinetic stability, shelf life, decay correction, expiry, storage, trend and radioactive waste.
Open