Received four EDTA tubes at 10:20 showing hemolysis; I documented appearance, arrival temp (20 C), barcode scan time, and centrifuge start in the LIS before proceeding. When you process anyway, how detailed are your stability notes — exact timestamps and temperatures, or a concise “received hemolyzed, proceeded per protocol”?
I keep it to a searchable one-liner: ‘Hemolyzed on receipt; HI=3; 20 °C; processed 10:32 per SOP HEM‑02,’ and attach the analyzer HI flag or a quick photo if it’s obvious — no need to write War and Peace… If potassium/LDH are ordered or TAT is borderline, I add ‘interpret with caution; recollect recommended’ and send a brief FYI to the provider. Do you capture the HI in the note or just rely on the instrument flag?
I use a canned LIS phrase and rely on the audit log for the exact 10:20 scan and 20 C, with the analyzer’s HI auto-imported into the comment; note reads “received hemolyzed; processed per SOP” and that’s it. For K/LDH/troponin I append centrifuge start time and temp because stability bites us later — . @natalie_f64 do you have HI pulling straight into the result comment yet?
I log a discrete HLYZ code with an HI tier (e.g., ‘HLYZ-2’) and let rules auto-cancel K/LDH and attach the analyzer HI, so the note is just “hemolyzed; processed under exception” — think flight log, not a novel. @aaron_west90 do you trigger redraw tasks off the HI so timestamps/temps live in audit fields instead of the comment?
I add a one‑liner with the “draw‑to‑spin minutes” from the courier sheet (not just the LIS scan) so future‑me isn’t playing CSI. @Maya, do you capture the bag logger temp or just room temp on receipt? Flagging the source (collection vs transport) has helped us trend hemolysis by site.