Roche RIS Feedback Portal

Ok thank you

But then we see some difference, we use integrated IGW mode, there is no change possible as I understand to use some extra demographics with only integrated IGW?

So if we need to have extra demographics, as this request is about, we need to move to standalone IGW installation and ask IGW BPM for a change in the IGW so NMON can use this?

Just to clear out all things and we are all on the same page about this.

Yes. This is the documentation we have nowadays that the Documentation team is currently including in RDK

@Ruben Salvador Gareta

could you please confirm if the embedded IGW is configured from docker settings in RLX? If needed I would be happy to configure 1 installation with a standalone IGW and see if that works better.

Hi all,

Let me summarize a bit how navify Monitoring and cobas infinity central lab interaction works to avoid confusion:

Basically, navify Monitoring only can communicate with cobas infinity central lab via IGW. Nowadays, we offer two possibilities to configure IGW:

• Standalone (in a different server than navify Monitoring)

• Embedded (in the same server of navify Monitoring)

But IGW is a must.

Independently on this topology, the key point about this request is that, nowadays, IGW does not allow having more than one Sender demographic. In the case of standalone, to select one or other, it needs to be done thought the IGW installer. In the case of embedded it needs to be done thought Portainer settings of the IGW container, but in both cases only one demographic is allowed.

So, in summary, to have the possibility to add extra-non-coded demographics to widgets for filtering, a change in IGW is needed.

I hope this explanation provides you clarity.

Regards,

Hi Qilei,

Please see this RDK article:

https://rdkm.roche.com/search/products/335727/procedures/392822

and this one:

https://rdkm.roche.com/search/products/335727/procedures/392643?lang=en

This is the way we installed and use NMON for our 4 installation. I can imagine the performance should be better if we use the IGW standalone?

I will contact Roberto Tubio separately for addition of the requested functionality

Best regards,

Jordi

Hi, Jordi,

Oh, that's interesting. As I understood, nMon always goes through IGW to get events from infinity. @Ruben Salvador Gareta Any comments on this?

But the current standard approach is to go through IGW. So please contact Roberto Tubio and let him know this change request.

Please let us know any further questions.

Qilei

Hi Qilei,

Currently on all installation we use the direct connection from NMON to Infinity, so without the IGW.

Still the only option is to ask for a change in the IGW?

If so, I will directly contact Roberto Tubio and ask how to proceed on the change request

Kind regards,

Jordi

@jordi.van_der_steenhoven@roche.com,

We had a discussion with the PO and the team.

IGW installer currently only offers single-selection for demographic (Sender demographic). In order to allow nMon being able to have multiple selection of demographic as filters, you need to bring this request to IGW (infinity Gateway). The BPM is Roberto Tubio.

With the current state, only with IGW change, nMon is able to offer the filtering with multiple fields.

Please keep us posted about this request to IGW.

Qilei Ge

• Regarding customer Zuyderland & Maasstad, can you please let me know which 2 or 3 demographic filters they wish to use? For example: No.8-Physician, plus what other demographics?

Yes that should be demographic 114 (aanvrager) en 109 (nastollen), these are used for different widgets to create

• Use case example: (What I heard from you last week) They would like to track the samples from X GPs (with specific conditions). These samples will be run tests first in Lab site 1 and then move to lab site 2, so that the lab 2 will be able to know in advance how many samples are coming to lab 2 today. Does it sound correct

Yes that is 1 use case. Other use case is to see tubes which are still waiting for coagulation in a timed rack and specific widgets differentiated between different requestors (not physicians!)

@jordi.van_der_steenhoven@roche.com, Thank you for the input and hope you are feeling well! In order to address feasibility, we need more details for this case.

• Regarding customer Zuyderland & Maasstad, can you please let me know which 2 or 3 demographic filters they wish to use? For example: No.8-Physician, plus what other demographics?

• Use case example: (What I heard from you last week) They would like to track the samples from X GPs (with specific conditions). These samples will be run tests first in Lab site 1 and then move to lab site 2, so that the lab 2 will be able to know in advance how many samples are coming to lab 2 today. Does it sound correct

This will help us to understand the use case and evaluate the feasbiilty and effort estimation.

Thank you!

Hi Qilei,

please find below some explanation:

Customer 1 = Maastricht UMC+ too busy with other things right now because they are having LIS migration and will start using NMON more after that. So happy for the moment

Customer 2 = Deventer Ziekenhuis is very happy with the solution, would like to have more features regarding filters etc.

Customer 3+4 = Zuyderland & Maasstad, both say if no improvement, they will see it as a product which does not give any really additional value when they can not use the proposed filters / widgets

@jordi.van_der_steenhoven@roche.com, can you please add the details about the these customers, as you mentioned in the call? Which customers are they? Also a bit of the context around their current attitude towards nMon.

Customer 1: too busy with other things right now.

Customer 2: very happy with the solution, would like to have more features.

Customer 3+4: if no improvement, they will not use nMon.

Discovery 10.Oct:

• Pre-requisite: demographics in a list format, not dynamic.

• Need development on the combined filter: inclusive or exception

• Technical implementation effort: need to check. Maybe need to open more tables.

@jordi.van_der_steenhoven@roche.com For understanding the need, can you please kindly give an example of such combined (custom) demographics? such as using "physician"+"?". Why is it needed? So that we could push the priority within the backlog. Thank you!

Hi Qilei,

Thank you, I know this procedure but the case is indeed to have 1 or 2 or even more (custom) demographics. If needed we can schedule a meeting.

Hi, @jordi.van_der_steenhoven@roche.com, discussed with the team. Here is

1. It is possible for the customer to use a customised demographics other than the default (origin). Please see the attachment of how to make the change.

• • However, the custom demo should be in the format of a list.

  • If it does not work, please create a service ticket, so GCS will look into it.

2. If your request is to have a combined filter with more than 1 custom demo, this would be a new feature and we need to understand the use case.

• What are the newly configured custom demographics? How would it be used together with other demographics? If needed, we can schedule a quick call to clarify the ask.

Hi Qilei,

Sorry for the delay in my answer, but please find them here:

• Configure specific widgets for Specific GP-codes: The lab wants to track the sample processing for specific GP or a group of GP, because they require short TAT. Is it the scenario?
  Yes correct, this is one of the scenario's. But there are more possible scenario's which some customers would like to implement when the possibility is there for custom demographics.

• For the custom ones, you refer to 101-112 at the bottom of the list, right?
  In this case yes, but with this specific customer I tried to use a predefined demographic (no. 8 - doctor) and that is also not working as NMON completely stops working and does not seem to filter on this demographic. They are shown and refreshed in the widget configuration however.

• If tomorrow you can have 3 custom demographics in nMon for configuring TAT and LST, which ones might the customer choose to have? Why are they helpful?
  As mentioned before, probably no. 8 which is predefined but we also configure custom demographics newly in Infinity which are very useful. Basically any reliable option to add or use some extra demographics other than 25 and 26 which are standard would be a big step in usability of the product. For now 2 customers are really waiting for this, otherwise their feedback is " we really doubt usability for us without this option"

@jordi.van_der_steenhoven@roche.com I have some follow up questions:

• Configure specific widgets for Specific GP-codes: The lab wants to track the sample processing for specific GP or a group of GP, because they require short TAT. Is it the scenario?

• For the custom ones, you refer to 101-112 at the bottom of the list, right?

• If tomorrow you can have 3 custom demographics in nMon for configuring TAT and LST, which ones might the customer choose to have? Why are they helpful?

Hi Qilei,

We have currently 2 customers (Zuyderland and Maasstad) who want to have this implemented. This is mainly for LST and TAT widgets. Please see sceenshots I have attached for examples of nod-coded / custom demographics.

This is used for creating specific widgets regarding specific GP-codes. Now only the demographics 25 and 26 are standard configured and we tried to change these to custom ones but that did not work.

@jordi.van_der_steenhoven@roche.com, in order to evaluate the feasibility and efforts, we need a real example:

• Which customer

• Which widget, let's say LST.

• What non-coded / custom demographics

• What is it used for, if they are able to configure with non-coded / custom demographics?