While developing the driver we have found this inconsistency between the manual and the traces. In the manual, OBX-7 is defined as reference range of results that might contain up to 90 characters:
In the traces, we see a wide type of information sent in this field:
As you may see, we have the ranges written in several ways, and we cannot be sure that all the possible combinations are in this trace. Therefore, I wanted to ask you: Do you need us to support the reference range of results? In case you do, we can send those that are "number-number" as asymmetric values only. The rest of them, like number~number or text, we can send them as as comment to the result.
Can you please confirm which approach suits your needs better before next Wednesday, January 10th?
Hi Nuria, My name is Jakkree. Implementation and Support Lead.
Could you please confirm the delivery date for this driver because this driver process is too long and our customer asks us several times when will they get the driver. Hope you to understand about our situations.
I am Núria Pena, currently covering as a PO for Lab drivers while Paola is in her EDO. Having analysed it with the team we would need additionally information so as to be able to proper develop the driver. Could you please send us the following information for the different workflows (QC, Patient results, Query messages)?
- Real traces for the graphical results - Real traces from UT5500 - Real traces from US2000
The team has reviewed the information and no more questions were raised. Regarding the development, the driver is accepted for the PI-21 planning (October-January). Once the planning is complete we can come back with a more specific date or you can check the driver in the Roadmap.
Thanks for the clarification about the traces. Can you provide the complete manual in UT5500 in that case? As mentioned above, the manual provided is incomplete and it does not match with the traces you provided. With the traces only, we cannot develop a driver.
Thanks for sending real traces. Unfortunately, as mentioned via email, the request created in April was not correctly processed by AHA!, which means that we didn't get it.
While checking the traces provided vs the manual, I see that there are several differences in the message structure. Also, the US2000 bi-directional description looks like an incomplete doc, because not all the segments and the messages are described. The traces say UT5500 where the device name should be:
Do they belong to the same instrument? There are segments in the doc to the right missing from the doc to the left and viceversa. Can we have terh complete manual of the instrument messsages?
Currently, this driver would be added to the next PI backlog (from late October to late January) if we receive the information necessary to start the development (new manual and traces corresponding to said doc).
Please, don't hesitate to reach out if you have further doubts.
Please reply and take action. Because we requested since April, but the information is not shown in the system, causing the installation process to be delayed beyond schedule.
Guest
Hello Nithipun,
While developing the driver we have found this inconsistency between the manual and the traces. In the manual, OBX-7 is defined as reference range of results that might contain up to 90 characters:
In the traces, we see a wide type of information sent in this field:
As you may see, we have the ranges written in several ways, and we cannot be sure that all the possible combinations are in this trace. Therefore, I wanted to ask you: Do you need us to support the reference range of results? In case you do, we can send those that are "number-number" as asymmetric values only. The rest of them, like number~number or text, we can send them as as comment to the result.
Can you please confirm which approach suits your needs better before next Wednesday, January 10th?
Thanks,
Paola
Dear Jakkree,
As already sent by mail, as we included the driver in our backlog, it is planned to be delivered by the end of December.
Best,
Núria
Hi Nuria, My name is Jakkree. Implementation and Support Lead.
Could you please confirm the delivery date for this driver because this driver process is too long and our customer asks us several times when will they get the driver. Hope you to understand about our situations.
Please check detail in attach file.
Hi Paola,
This information for the different workflows (QC, Patient results)
"Query messages = No option on instrument"
Please check detail in attach file.
Dear Nithipun,
I am Núria Pena, currently covering as a PO for Lab drivers while Paola is in her EDO. Having analysed it with the team we would need additionally information so as to be able to proper develop the driver. Could you please send us the following information for the different workflows (QC, Patient results, Query messages)?
- Real traces for the graphical results
- Real traces from UT5500
- Real traces from US2000
Thanks a lot!!
Best,
Núria
Dear Nithipun,
The team has reviewed the information and no more questions were raised. Regarding the development, the driver is accepted for the PI-21 planning (October-January). Once the planning is complete we can come back with a more specific date or you can check the driver in the Roadmap.
Best regards,
Sara Julián
Hi Team,
Any update for driver?
Regards,
Nithipun
Thanks for sharing this information.
I'll share all of it with the team and if further questions come, I'll follow up in this comment thread.
Regards,
Paola
Hi Paola,
This real traces US2000
<VT>
MSH|^~\&|URIT|US2000||LIS|20200304150503||ORU^R01|2|P|2.3.1||||||ASCII|||<CR>
PID|2||||||||||||||||||||||||||||||<CR>
OBR|2||000002||||20200304120322|20200304120322||9^7||||||||||||||||||||||||||||||||||||||<CR>
OBX|1|NM|UC_VC||+2|PLUS|-|N|||F|||||||<CR>
OBX|2|NM|UC_NIT||-|PLUS|-|N|||F|||||||<CR>
OBX|3|NM|UC_MA||30mg/L|SI|<=10|N|||F|||||||<CR>
OBX|4|NM|UC_LEU||-|PLUS|-|N|||F|||||||<CR>
OBX|5|NM|UC_CR||>=300mg/dL|CONV|50~>=300|N|||F|||||||<CR>
OBX|6|NM|UC_KET||-|PLUS|-|N|||F|||||||<CR>
OBX|7|NM|UC_URO||Normal|PLUS|Normal|N|||F|||||||<CR>
OBX|8|NM|UC_BIL||-|PLUS|-|N|||F|||||||<CR>
OBX|9|NM|UC_GLU||-|PLUS|-|N|||F|||||||<CR>
OBX|10|NM|UC_PRO||-|PLUS|-|N|||F|||||||<CR>
OBX|11|NM|UC_SG||1.027|PLUS|1.010~1.030|N|||F|||||||<CR>
OBX|12|NM|UC_PH||6.0|PLUS|5.0~7.5|N|||F|||||||<CR>
OBX|13|NM|UC_BLD||-|PLUS|-|N|||F|||||||<CR>
OBX|14|NM|UC_CA||100mg/dL|CONV|50~200|N|||F|||||||<CR>
OBX|15|NM|UC_MACR||2.14mg/mmol|CONV|<30|N|||F|||||||<CR>
OBX|16|NM|UC_COL||Yellow|PLUS|Yellow|N|||F|||||||<CR>
OBX|17|NM|UC_CLA||Clear|PLUS|Clear|N|||F|||||||<CR>
OBX|18|NM|UD_RBC||0|HPF|0-3|N|||F|||||||<CR>
OBX|19|NM|UD_UNDF1||0|HPF|0-3|N|||F|||||||<CR>
OBX|20|NM|UD_G1||0|HPF|0-3|N|||F|||||||<CR>
OBX|21|NM|UD_COIN||0|HPF|0-3|N|||F|||||||<CR>
OBX|22|NM|UD_GHOST||0|HPF|0-3|N|||F|||||||<CR>
OBX|23|NM|UD_WBC||1|HPF|0-3|N|||F|||||||<CR>
OBX|24|NM|UD_UNDF2||0|HPF|0-1|N|||F|||||||<CR>
OBX|25|NM|UD_HYA||0|LPF|0-1|N|||F|||||||<CR>
OBX|26|NM|UD_PAT||0|LPF|0-0|N|||F|||||||<CR>
OBX|27|NM|UD_SQEP||0|HPF|0-3|N|||F|||||||<CR>
OBX|28|NM|UD_NSE||0|HPF|0-3|N|||F|||||||<CR>
OBX|29|NM|UD_CAOX||0|HPF|0-3|N|||F|||||||<CR>
OBX|30|NM|UD_URIC||0|HPF|0-3|N|||F|||||||<CR>
OBX|31|NM|UD_STRUVITE||0|HPF|0-3|N|||F|||||||<CR>
OBX|32|NM|UD_AMORF||0|HPF|0-3|N|||F|||||||<CR>
OBX|33|NM|UD_UNCX||0|HPF|0-3|N|||F|||||||<CR>
OBX|34|NM|UD_YST||0|HPF|0-3|N|||F|||||||<CR>
OBX|35|NM|UD_BACT||-||-|N|||F|||||||<CR>
OBX|36|NM|UD_COCCI||0.0|/uL|0-15|N|||F|||||||<CR>
OBX|37|NM|UD_BACILLI||-||-|N|||F|||||||<CR>
OBX|38|NM|UD_MUCS||4|HPF|0-3|N|||F|||||||<CR>
OBX|39|NM|UD_SPRM||0|HPF|0-3|N|||F|||||||<CR>
<FS><CR>
Please check detail in attach file.
If you need more information please contact me.
Thank for support.
Hi Paola,
I Already Attach file manual protocol instrument UT5500 for create driver US2000
,Instrument specialist US2000 confirmed same protocol with instrument UT5500.
Please check detail in attach file.
If you need more information please contact me.
Thank for support.
Hello Nithipun,
Thanks for the clarification about the traces. Can you provide the complete manual in UT5500 in that case? As mentioned above, the manual provided is incomplete and it does not match with the traces you provided. With the traces only, we cannot develop a driver.
Sorry for the inconveniences,
Paola
Hi Paola,
We confirmed with instrument specialist US2000 same protocol with instrument UT5500.
If you need more information please contact me.
Thank for support.
Hello Nithipun,
Thanks for sending real traces. Unfortunately, as mentioned via email, the request created in April was not correctly processed by AHA!, which means that we didn't get it.
While checking the traces provided vs the manual, I see that there are several differences in the message structure. Also, the US2000 bi-directional description looks like an incomplete doc, because not all the segments and the messages are described. The traces say UT5500 where the device name should be:
Do they belong to the same instrument? There are segments in the doc to the right missing from the doc to the left and viceversa. Can we have terh complete manual of the instrument messsages?
Currently, this driver would be added to the next PI backlog (from late October to late January) if we receive the information necessary to start the development (new manual and traces corresponding to said doc).
Please, don't hesitate to reach out if you have further doubts.
Thanks,
Paola
Hi team,
Please reply and take action. Because we requested since April, but the information is not shown in the system, causing the installation process to be delayed beyond schedule.
If you need more information please contact me.
Thank for support.