Problem: Multiple customers in US having hematology instruments (Sysmex) but not connected to infinity. Therefore, when automation sends the samples to Sysmex, the samples can not be monitored with TAT or LST.
Idea: The reformaters are a part of 8100 connection. Infinity receives messages from 8100 connection. Based on this, the idea is to track the samples with the end point as “sample seen by reformater”.
Updated information (22.04.2024):
The Sysmex is a virtual target. In the USA third party instruments are not connected to infinity so data is not sent from Sysmex to infinity but the information could potentially be sent over the 8100. That way infinity would have information on what is on the Sysmex.
Updated information (comment Pedro, 22.04.):
It needs to be investigated, but when the tube is "reformatted" from a single tube container to an R5 rack, the 8100 sends a message to infinity and it probably generates D18 events setting the distribution.
Idea detail description
There is currently no way to monitor samples that go to the reformater only (RFX for Sysmex instruments). |
|
Product review evaluation
nMon only shows event from instruments that are connected to infinity. This is the current design. In the mid term future with consider to connect other data sources via navfiy integrator. Sysmex instruments can be connected to infinity like the Roche ones. There are drivers available. |
|
Product evaluation start date | 2024-03-07 |
Dear Seda, yes this is what we discussed last week.
Hi Ruben, it needs to be investigated, but when the tube is "reformatted"
from a single tube container to an R5 rack, the 8100 sends a message to
infinity and it probably generates D18 events setting the distribution.
Regards,
Pedro
Hi @Pedro Cardoso
What do you mean with "the information could potentially be sent over the 8100"? Sent how? From nMon point of view doesn't matter which information is in infinity side, the only point of data for nMon is what IGW exposes. If there is not an event exposed by Infinity Gateway that can inform nMon that something happened, for nMon this data is not consumible. Can you provide us a bit of context about how this communication between instruments and modules occur and which kind of data and how is arriving to infinity from Sysmex via c8100?
Thanks.
@Pedro Cardoso Added the following information in the description from our meeting last week:
"Updated information:
The Sysmex is a virtual target. In the USA third party instruments are not connected to infinity so data is not sent from Sysmex to infinity but the information could potentially be sent over the 8100. That way infinity would have information on what is on the Sysmex."
Could you confirm if it's correct or correct it where needed? Thank you!
Nowadays, Infinity Gateway provides information about the modules of instruments in fields 'instrumentModuleRef' and 'performingInstrumentModuleRef' (we would need to check if data about this particular module is populated in the events), but in nMon we don't have this granularity on the tracking filters.
@Ruben Salvador Gareta Please see the re-written problem statement and idea for this ticket. Is such event of reformater could be received from infinity?
Yes @Qilei Ge , you summarized exactly the feedback
that we received from the customer. They would like to have an end point
for the reformaters.
@Pedro Cardoso The problem and idea proposed are not clear to me. I re-write based on what I understood as below, can you please help to make it correct?
Problem: Multiple customers in US having hematology instruments (Sysmex) but not connected to infinity. Therefore, when automation sends the samples to Sysmex, the samples can not be monitored with TAT or LST.
Idea: The reformaters are a part of 8100 connection. Infinity receives messages from 8100 connection. Based on this, the idea is to track the samples with the end point as “sample seen by reformater”.
Only when system is connected with infinity, nMon can track.