We’re revamping our sample tracking so consent status follows each library and run; we process about 96 samples a week on a NextSeq 2000. What LIMS or add-ons have you used that enforce consent checks and audit trails without exposing identifiers, and can they handle de-identified barcodes plus re-contact flags per IRB requirements?
We solved this in Clarity LIMS by adding a ‘consent_ok’ UDF and an EPP that hard‑stops the pre‑run step if false, with labels carrying only a UUID; the ‘recontact_flag’ sits in a separate UDF restricted to PI role, and we sync consent via the REDCap API to keep PHI out of LIMS. If you’re on NextSeq 2000, this plays nicely with the stock steps — ref: https://support.illumina.com/sequencing/sequencing_software/clarity-lims.html — do you already have REDCap or another consent source?