Adapters Request Portal

Hello Lucas,

I proposed an alternative way for this connection via email.

Thanks,

Paola

Lucas,

More questions:

• purple: are the differents segments avaliated in blood groups. --> What do you mean with this?

• DGW11E.gru^3SCREEN.pln --> Is it all a test code? There are 2 components here. Are both components test codes?

Thanks

Hello Lucas,

Thanks for your replies.

1) O|1|QCS117011170715||^^^DGW11E.gru^3SCREEN.pln|20170706105041||||||||||||||||||REPORT^000^ERY|F| --> Is the bold text name of default template of erytra instrument or the test code? You defined the same piece of information in two different ways.

2) I understand the traces are generated with the ASTM simulator. My concern here is that they look pretty different from the manual, like M and C extra segments, or the O segment containing information in the O-2, while in the manual there's nothing. Can you double check the traces, please?

Paola

Hi Paola, about your questions:
1) Is it possible to get information about the definition of these segments. Should the green highligh be considered three different results?
Yes, can be considered three different results.
What information is the yellow, purple and red segments?
yellow: name of default template of erytra instrument.
purple: are the differents segments avaliated in blood groups.
red: is a run profile, was send REPORT^000^ERY because the instrument was forwarding an existing result.

2) The traces contain several segments that are totally absent from the manual description (see red-highlighted) and the instrument name does not match the erytra (yellow).
Are these traces right?
Yes, the traces attached was extracted directly from instrument using ASTM HOST SIMULATOR.
Can you ask the vendor what should be consider as the test code in the O segment?
Yes. Considering example below:
O|1|QCS117011170715||^^^DGW11E.gru^3SCREEN.pln|20170706105041||||||||||||||||||REPORT^000^ERY|F|
You can considered as test code: DGW11E.gru^3SCREEN.pln

Thanks,
Lucas Galdino

Dear all,

I connected in customer enviroment and used a ASMT simulator to received traces from instrument.

I attached the file.

Hi Marcus,

Thanks for the update.

Best regards,

Sara Julian

Hi Paola!

I requested the extraction of the traces to the local support team, because the instrument is located in the Porto Velho city, very far from the Roche office (3000 kilometers).

I'm monitoring this request to send it to you as soon as possible.

Hi Marcus,

Would it be possible to extract at least real traces from the instrument for all the workflows to support? In this way, internally the team can analyse if with that information it would be feasible to develop the driver.
Thanks!

Hello Paola! I hope you are well!

We tried to receive a new interface manual through our consumer. They contacted the instrument supplier, but obtained the same manual. We reported that it was incomplete, without success.

Is there anything we can help find in the document? Some information?

Thank you very much for your attention!

Hello Paola! I hope you are well!
We tried to receive a new interface manual through our consumer. They contacted the instrument supplier, but obtained the same manual. We reported that it was incomplete, without success.
Is there anything we can help find in the document? Some information?
Thank you very much for your attention!

Hello Lucas,

Do you have any update about this manual?

Thanks

Hello Lucas,

Thanks for reaching out.

Unfortunately, the manual attached does not have the field defined for each message segment. Is it possible for you to get a new document for this instrument where we can find this information?

Also, we have seen some screenshots in the manual that look like real traces. However, we'd like to have some examples.

Is it possible for you to get us both pieces of information before 25-JAN-2022?

Please share this information via email.

Regards,

Paola