Roche RIS Feedback Portal

Good morning @Jinhong Park ,

Yes, events are the same, see the equivalence between nLO events and IGW events (the ones nMon consumes)

nLO Event: O2 (Order deleted from the system) = IGW Event: O0005 (Order deleted)

nLO Event: T2 (Test request deleted from the system) = IGW Event: T0012 (Test request deleted)

Even if the version is not 1.09, it should work as I commented so, probably there is an issue in the IGW connection or in the HCA message exchanges, for this I would recommend to contact Customer Support team and to start an investigation and troubleshooting session with GCS and Engineering team to try to find the root cause and solve the issue.

Regards,

Dear Ruben,

Thank you for reaching out and providing such a detailed explanation, along with the video demonstration. I have reviewed your comments and fully understand how the expected behavior works based on your description.

To provide some context on why this case was originally submitted, we observed a specific scenario where this expected behavior does not seem to apply. I have outlined the details and a couple of follow-up questions below:

Issue with O2 Events (Versions < 1.09): We raised this idea because we identified that in versions prior to 1.09, when an "Order cancel event" (O2) is triggered via HCA, the sample is not properly removed from the widget as it should be.

Question regarding T2 Events: In a scenario where the order remains active, but every individual test under that order is canceled (T2 event), will the sample also be successfully removed from the tracking list?

Event Clarification: Could you please clarify if the O2 and T2 events I mentioned are treated differently by the system than the O0005 event referenced in your table?

(O2 and T2 are nLO system event code, I cannot find O0005 in this list)

If the above events(O2 & T2) are the same as the event (O0005) you mentioned, I will try a technical follow-up by Smarteeva.

Thank you again for your collaboration and support. We look forward to your insights on these specific events.

Best regards,

Good afternoon @Jinhong Park ,

I hope this message finds you well. Allow me to introduce myself—my name is Rubén Salvador, and I am the Product Owner of navify Monitoring. It is a pleasure to connect with you.

I have carefully reviewed your comments and responses, and I would like to confirm my understanding of your request. Based on my analysis, it seems that what you are requesting is already supported in navify Monitoring. To demonstrate this, I have recorded a video (attached) in which you can see an LST widget with two samples being tracked.

In the first part, you will observe that after a sample is deleted from the navify Lab Operations "Order Entry" screen, it ceases to be tracked in the navify Monitoring widget after a few seconds. This demonstrates that regardless of the configured "Ending Event" in the widget, deleting a sample ensures that it disappears entirely from the widget.

In the second part, when tests are removed from a sample, those tests no longer appear in the tracking on the LST widget. Furthermore, if all tests for a sample are deleted, leaving no pending results, the sample itself disappears from the widget. This demonstrates that regardless of the configured "Ending Event" in the widget, deleting all the tests of a sample ensures that the disappears entirely from the widget.

In the following table we can see the Events received from navify Monitoring that made the widget staop tracking samples as commented before:

Based on my understanding, all the points raised in your Aha Idea are already accommodated by the product. If you observe this not being the case for a specific customer, it might indicate an issue of this particular installation. If that is the case, I recommend raising a ticket with customer support to initiate an investigation and resolution process.

Thank you very much for your input and cooperation. We look forward to receiving your feedback.

Kind regards,
Rubén Salvador

Hi @Jinhong Park ,

Thank you very much for your reply!
I'll review this info with my tech team and come back to you as soon as I have more updates.

Take care,

Mary

Hello @Maria Doretto,

Sorry for late reply

1. LIS to nLO: When a cancellation happens in LIS, what specific message or code is sent to nLO and how (HCA messages?) ?

-> Yes, we usually use "CA" signal in HCA order message

This signal should be process from LIS to nLO

2. nLO Reaction: When nLO receives that 'CA' signal, does it internally trigger the Order Deleted (O0005) event? This is the specific event our PO believes might already be in the system.

-> Yes, In nLO Order Deleted event executed

3. nMon Tracking: To cover the 'missing' flow, is it your expectation that as soon as that O0005 (Order Deleted) event occurs, the sample should disappear from the LST widget immediately even if it hasn't reached the 'Result Entry' end event?

-> Yes, If Order deleted message comes in nLO. customers want to delete this order also in LST widget immediately.

4. The 'Cancel Test' Scenario: Just to confirm: if a user only cancels (deletes) one test but the Sample Order remains, should the sample stay on the LST widget until the remaining tests are finished?

-> If only one test deletes and other tests are still remain then the sample ID should be stay on the LST widget.

Order cancle is quite comment process in laboratory. especially sample status is bad (Hemolysis, volume insufficient .. etc)

Thank you for contributing to the development of the product with you!

Thank you!

Jinhong Park

Hi @Jinhong Park ,

Thank you for the detailed breakdown of the 'Cancel vs. Delete' logic in nLO and the specific customer sites. This is very helpful.

Could you help us clarify the specific workflow for these 4-5 clients?

1. LIS to nLO: When a cancellation happens in LIS, what specific message or code is sent to nLO and how (HCA messages?) ?

2. nLO Reaction: When nLO receives that 'CA' signal, does it internally trigger the Order Deleted (O0005) event? This is the specific event our PO believes might already be in the system.

3. nMon Tracking: To cover the 'missing' flow, is it your expectation that as soon as that O0005 (Order Deleted) event occurs, the sample should disappear from the LST widget immediately even if it hasn't reached the 'Result Entry' end event?

4. The 'Cancel Test' Scenario: Just to confirm: if a user only cancels (deletes) one test but the Sample Order remains, should the sample stay on the LST widget until the remaining tests are finished?

Mapping this 'LIS → nLO → nMon' sequence will help us identify exactly where the communication is breaking down.

Thank you!
Mary, new UX Designer for navify Monitoring

@Qilei Ge,

First of All, cancle order = delete order

Additionally, there are two options. cancle TEST and cancle ORDER

• cancle TEST means only cancle one (or several) test. but Sample Order is still remain.

• cancle ORDER means delete sample order.

These two events are also different event in navify Lab Operation.

• Is there any difference between order cancelled and order deleted?

-> same

• If an order is cancelled, is the sample cancelled or deleted?

-> if ORDER cancelled, all sample information will be deleted.

• If an order is deleted, is the sample also deleted?

-> if cancle TEST, sample order still remain.

-> if cancle ORDER, sample order will be deleted.

There are two events, and we usaully discuss these event with lab users.

if you have any questions please let me know!!

Thank you

Best regards

Jinhong Park

@Jinhong Park Currently, we track on samples and tests but not orders. So if samples are deleted, nMon will stop tracking.

Can you please let us know:

• Is there any difference between order cancelled and order deleted?

• If an order is cancelled, is the sample cancelled or deleted?

• If an order is deleted, is the sample also deleted?

That will be very helpful! We are also checking with nLO experts internally.

Thanks,

Qilei

@Jinhong Park Thank you for the quick reply! Do you know if samples are also deleted in nLO? This is important data for nMon.

@Qilei Ge,

It's slightly different for each laboratory, but I'll guide you based on the laboratory I worked on recently.

• 학교법인 성균관대학삼성창원병원 Samsung Changwon Hospital

nM : 1.08

IGW : 1.12.0.2

nLO : 3.03.15

• 아주대학교병원 Ajou University Hospital

nM : 1.08

IGW : 1.12.0.2

nLO : 3.03.14

I confirmed that the order of the sample was deleted from nLO at the site.

Thank you!

Jinhong Park

@Jinhong Park Discussed with the team, we have two questions below:

- Can you let us know the versions of nMon, IGW and nLO the customers are currently using?
- Please confirm in this case, the samples and orders are deleted in nLO.

Hello, @Qilei Ge

• Can you please share with us the starting and ending event of the LST widget?

starting event : order entry (or first sample seen in the lab)

ending event : result entry from instrument

• To help us to understand, can you please describe the purpose of configuring LST with such starting and ending events?

Check the TAT from receiving the order (hospital blood collection or reception event) message in the laboratory to the results from our instruments.

Sometimes, canceled samples still remain on the list.

This interferes with accurate TAT verification for lab users.

• What does the sample workflow look like? e.g. Order entered > Sample received and registered > Load to pre-analytics > Sample quality issues > cancel order?

Sample cancel orders can occur at the hospital LIS for a number of reasons and can occur at any stage. (Whenever receive the original order) When they occur, nLO receives the order with an action event called "CA" and deletes the order or test.

• Who are the 4 Korean customers? Can you please specify?

• 학교법인 성균관대학삼성창원병원 Samsung Changwon Hospital

• 인제대학교 해운대백병원 INJE UNIVERSITY HAEUNDAE PAIK HOSPItal

• 아주대학교병원 Ajou University Hospital

• 목포한국병원 Mokpo Hankook Hospital

• 가톨릭관동대학교 국제성모병원 International St. Mary's Hospital

• 학교법인건양교육재단 건양대학교병원 Daejeon Konyang Medical Foundation

If you have any question regarding this topic please let me know!

Thank you!

Jinhong Park

@Jinhong Park Thank you for entering the idea! I have couple of questions below:

• Can you please share with us the starting and ending event of the LST widget?

• To help us to understand, can you please describe the purpose of configuring LST with such starting and ending events?

• What does the sample workflow look like? e.g. Order entered > Sample received and registered > Load to pre-analytics > Sample quality issues > cancel order?

• Who are the 4 Korean customers? Can you please specify?

Please provide above information, so that we can discuss tomorrow internally. Thank you!