Please submit any feature requests and vote on ideas that have already been submitted to indicate your interest in seeing them developed
Samples should be removed from LST widgets once validated/sent to host, regardless of whether or not the end event is reached. E.g. many labs will enter 'clotted', 'short' etc for samples which visibly cannot be run. These samples may have reached their LST start event (e.g. order entry), however, they may not reach their end event (e.g. sample seen on analytic) as the lab staff can see that these samples are clotted or short etc. Since there is no option to remove samples from the widgets manually, it would make sense for completed samples (i.e. samples that have been resulted and validated) to be removed from LST widgets, regardless if they have reached their end event. Otherwise, these samples remain on the widgets until the widget timeout.
Many of our large UK labs complain about nMon due to scenarios described above. Having completed samples on widgets undermines the effectiveness of nMon and makes customers feel like they cannot trust the data that nMon is displaying. If nMon was able to remove samples from all LST widgets when they were 'complete', this would make the data displayed in LST widgets more reliable. I have already raised two separate ideas to negate the above scenario: 1) to be able to manually remove a sample from a widget; 2) to be able to configure more than one end event (like LiveView did), but simply removing completed samples from widgets regardless if it reaches its end event would solve the issue and makes sense.
Guest
|
Idea detail description
Samples should be removed from LST widgets once validated/sent to host, regardless of whether or not the end event is reached. E.g. many labs will enter 'clotted', 'short' etc for samples which visibly cannot be run. These samples may have reached their LST start event (e.g. order entry), however, they may not reach their end event (e.g. sample seen on analytic) as the lab staff can see that these samples are clotted or short etc. Since there is no option to remove samples from the widgets manually, it would make sense for completed samples (i.e. samples that have been resulted and validated) to be removed from LST widgets, regardless if they have reached their end event. Otherwise, these samples remain on the widgets until the widget timeout. |
Hi @Jinhong Park, @Alberto Biancardi and @Patrice Fayolle,
I can see you voted this idea and, since I was not able to receive a reply from the creator of the idea, I would like to gather your feedback instead.
In the current version, the only factors that close a sample are:
The ending event
Tube deleted
Sample deleted.
All tests of samples with test results when the ending event is defined as "Sample seen on the analyzer"
Pending tests validated and sent to host are not closing the sample if ending event is not test validated or result sent to host.
Could you please confirm in which situations would you like the sample to close automatically independently of the ending event?
Thank you!
Mary - UX Lead
Hi @Kathryn Carrick ,
I wanted to follow up on this as we’ve identified that the v1.08 release (launched in July 2025) addressed the core of this issue.
In this version, once a sample is seen on the analytic, it is considered closed and automatically removed from the widget. This should prevent "clotted" or "short" samples (or any sample that has been resulted/validated) from lingering until the timeout.
Have you noticed this improvement in your workflow since the update, or do you think this is not been resolved yet?
Regards,
María
Hi @Kathryn Carrick ,
Following up on your request to have samples removed from LST widgets once completed: our Product Team is reviewing the logic and needs one specific clarification.
Currently, if a sample’s 'End Event' is not set to 'Validated, or "Result sent to host", the sample stays on the widget.
Could you confirm that you want the system to automatically close and remove the sample as soon as all pending tests are validated or sent to the host, regardless of whether it has reached its configured 'End Event' (e.g., 'Sample seen on analyzer')?
We want to ensure this 'Completion Override' covers all the scenarios you mentioned, like clotted or short samples that never reach the analyzer but are technically 'done' in the system.
Thank you
Mary