Adapters Request Portal

I have 2 questions :

1) to fix the issue described below (also a CASE has been made for this)

2) take as the controlname the whole string (and not only the first 6 characters) received from Immulite (because this contains the control level)

1 )The driver is not working correctly when a QC name is less then 3 characters :

Control code from Immullite can contain after the ~C 3 until 6 characters.

See examples below

~CACT 1302025011

~CEBVNEG1302025011

Info after controlename :

130 = Lotnumber

2025 = Experation year

01 = Experation mothn

1 = control level

The driver is not working properly when the control name is less then 6 characters.

It seems that for the capturing of the control name is taking a part of the controle lot and after that all the cutting is incorrect

Raw data : 3 spaces after controlname because it exists of 3 characters instead of 6

H|\^&||||111 Canfield Ave^Randolph^NJ^07869||(201)927-2828|N81|||P|1|20230112101705

P|1|130|||ACT||20250131||||||1

O|1|~CACT 1302025011||^^^ACT|R|||||||||||1||||||||I2629

R|1|^^^ACT|31.5|pg/mL|25.4\5.00^34.6\1250|N|N|F|||20230112090642|20230112101704|I2629

L|1

Info captured by Infinity :

The driver is taking away 2 spaces and is adding the first to numbers of the lot to the control name. The controle LOT is the last number of the LOT with the first the numbers of the expiry year

<SampleResult Batch="false" Version="1.0" DriverName="IMMULITEV3" DriverVersion="3.1.0.25" InstrumentType="IMMULITEV3" xmlns="http://roche.com/CIT/InstrumentInterface">

<Sample SampleID="~CACT 1302025011" Control="true" ControlName="ACT 13" ControlLotID="020">

<Result TestCode="ACT" DateTime="20230112090642" DateTimeFormat="YYYYMMDDHHMMSS">

<ResultPart Part="1" Unit="pg/mL">31.5</ResultPart>

<Flag Value="N">

</Flag>

</Result>

</Sample>

</SampleResult>

2) Capture the control level identification :

The last number of field O-2 is the control level

~CACT 1302025011 (= here 1).

For level 2 the controle name look like this :

~CACT 1302025012

With how the driver works now the customer cannot identify from which control level the value is coming from (we receive now as control name ACT 13, which is also wrong, see point 1).

A solution could be to take as the control name the whole O-2 field and not cutting it.