Cr51RBCSampleTimingChecker

Cr-51 RBC Sample Timing Checker

Cr-51 RBC Sample Timing Checker

ℹ️  Utility performs:
    • Check of actual serial-sample timing against the approved red-cell survival protocol.
    • input.csv structure and numeric-value validation
    • LabWare-compatible output.json generation
    • Deterministic PASS / FAIL / ERROR status

⚠️  CRITICAL: Any nonconformity shall be reviewed by qualified personnel before the result is used in an operational workflow.

Usage:
  Cr51RBCSampleTimingChecker.exe                            → demonstration mode (console output)
  Cr51RBCSampleTimingChecker.exe input.csv output.json      → evaluate user data

Input format:
BatchNumber,InitialSampleHours,Day7SampleDay,Day14SampleDay,Day21SampleDay,AllowedInitialDeviationHours,AllowedDayDeviation

Example:
  CR51-TIME-001,1,7,14,21,1,1

— WHY IS THIS NEEDED?
Check of actual serial-sample timing against the approved red-cell survival protocol.
The utility belongs to “RPH Cr-51 Labelled Red Blood Cells QC Suite” and can be used as a standalone check or as part of a wider nuclear-medicine workflow.

⚠️  CRITICAL:
• InitialSampleTiming: <= allowed deviation from 1 h
• Day7Timing: <= allowed deviation
• Day14Timing: <= allowed deviation
• Day21Timing: <= allowed deviation

Key features:
• One .NET 6 executable and one Program.cs
• Complete input.csv example with passing, boundary and failing records
• LabWare-compatible JSON: Header, Samples, Results, Status, StatusCode, ErrorMessage, Description and DescriptionEN
• CultureInfo.InvariantCulture for numeric values
• Explicit result for every parameter and empty ErrorMessage for PASS

Critical parameters:
• InitialSampleTiming: <= allowed deviation from 1 h
• Day7Timing: <= allowed deviation
• Day14Timing: <= allowed deviation
• Day21Timing: <= allowed deviation

💡 Usage tips:
1. Before operational use, reconcile limits with the approved specification, product information, local SOP and equipment configuration.
2. Retain the source input.csv together with output.json and the executable version.
3. For clinical calculations, use only verified source data and an approved protocol profile.
4. FAIL requires review and is not an automatic medical decision.
5. Limit changes require change control and renewed verification.

⚠️ Note: The utility implements a deterministic CSV-to-LabWare-compatible-JSON workflow and does not replace an approved method, specification, SOP or medical judgement.

The reference limits in this version are a conservative FUZKK project starting profile. They shall be confirmed by the process owner before OQ/PQ and production use.