Adapters Request Portal

Driver request for SKYLAB DASIT

Useful driver in order to connect SKYLAB and Infinity -Affidea contract

  • Guest
  • Jul 21 2023
  • Released
  • Attach files
  • Paola Maita Gonzalez commented
    January 02, 2024 14:21

    Hello Stefania,

    Happy New Year. We have added query mode to the development.

    Thanks,

    Paola

  • Guest commented
    December 20, 2023 16:57

    please add " sample query"

  • Paola Maita Gonzalez commented
    November 21, 2023 11:15

    Hi Stefania

    As already discussed in today meeting with Andrea from Skylab we have requested:

    • Patient results, QC results and Calibration results traces

    • Vial kinds table match for each value

    Once we have this info we will plan the driver development.

    Best,

    Núria

  • Guest commented
    November 20, 2023 08:50

    · The HIM states that the specimen ID field, the third component can either be 0,1,2 and incremental. Compared to the trace we have observed that, for the same patient and even test code there are some cases in which the information sent is repeated in blocks but having this specimen ID third component field different.
    The repeated information represents (in the case of replicates) the average value and the result calculated on the average value. This behavior is configurable from the SkyLAB software.

    o Is this a regular behaviour? What does this third component mean? We were technically evaluating the feasibility of sending all the info, but it would require treating each combination of testcode and specimen ID as unique, which would require more test mapping configuration and result display of those repeated values (see first image marked in orange and purple the repeated values)
    It's a regular behavior, and you can choose whether to turn it off.

    · On the other hand, in the trace provided there were some segments with a field of Negative and CAL_N, both of them sent as SAMPLE (see attached image marked as bright yellow). As the HIM states, whenever it is QC or Calibration it is sent as such (QC and CALIBRATOR respectively) instead of SAMPLE. Could you please provide us with additional traces with QC and Calibration results?
    This behavior is fully configurable when programming the methods to be performed on the SkyLAB instrument. In order to send coherent traces, it would be necessary for us to receive the methods that will be used in order to produce the real layout and send it to you.

  • Paola Maita Gonzalez commented
    October 23, 2023 09:34

    Dear Stefania,

    As aligned via xat we will pass the yellow elements as flags and the QC identifier will be the blue one on the table.

    Best regards,

    Sara Julian

  • Paola Maita Gonzalez commented
    October 20, 2023 07:00

    Dear Stefania,

    In order to develop the driver we would need this information. Could you please send it to us?

    Best regards,

    Sara Julián

  • Paola Maita Gonzalez commented
    September 25, 2023 10:34

    Hello Stefania,

    Thanks for sharing the traces. Do you have any response about the QC flags and identifiers?

    Regards,

    Paola

  • Guest commented
    September 25, 2023 10:29

    Thanks

  • Guest commented
    September 25, 2023 10:28

    Hi Paola, here attached the real trace report, thanks a lot in advance

  • Paola Maita Gonzalez commented
    August 08, 2023 08:18

    Hello Stefania,

    Thanks for reaching out. Is it possible you to provide instrument's real traces? It'd be nice to check the instrument's real behavior and the message description in the manual. Also, if every field marked as null in the manual is sent by the instrument empty or it's not sent at all.

    On the other hand, we'd like to know if the vial kinds should be interpreted like this:

    The yellow-highlighted are flags and the green-highlighted is QC result identifier?

    Thanks,

    Paola