Scan­ner test inte­gra­ted into mer­chan­di­se manage­ment

Many fal­se alarms in the secur­Ph­arm sys­tem are still cau­sed by incor­rect­ly set scan­ners. The­se do not read the pack data cor­rect­ly and trans­mit an incor­rect code to the secur­Ph­arm sys­tem, which leads to a fal­se alarm. To make it even easier to check the scan­ners, secur­Ph­arm and NGDA are now making the exis­ting scan­ner test in the ERP sys­tem available as a digi­tal test code. When scan­ning the Data Matrix code of the test pack, veri­fy­ing bodies recei­ve various feed­back mes­sa­ges that indi­ca­te whe­ther the tes­ted scan­ner is set cor­rect­ly or why the pack code was not read cor­rect­ly. The code should be scan­ned first:

PC:111234568408SN: 1234/-:_()edcb CH.-B.: Test.00.KEY.CHAR1M+Y usable up to: 250300

The fol­lo­wing mer­chan­di­se manage­ment con­fir­ma­ti­ons are pos­si­ble: SP-201: The respon­se “Pack is alre­a­dy boo­ked out (inac­ti­ve)” shows that the scan­ner is set cor­rect­ly. The feed­back is due to the fact that the test pack was boo­ked out in advan­ce to pre­vent misu­se. SP-102 or SP-212: If an alarm is trig­ge­red during scan­ning tog­e­ther with the feed­back that the seri­al num­ber or batch desi­gna­ti­on is not known, this means that the scan­ner is con­fi­gu­red incor­rect­ly. This is usual­ly due to an incor­rect lan­guage and/or case set­ting. If an alarm occurs during the test pro­ce­du­re, this alarm is auto­ma­ti­cal­ly de-escala­ted. The test can the­r­e­fo­re be car­ri­ed out as often as requi­red. It is important that the­se tests are car­ri­ed out with all scan­ners - e.g. in phar­maci­es at the HV as well as in the back office. The­se tests should be repea­ted at regu­lar inter­vals, as scan­ners can also beco­me mis­a­li­gned. You can find the scan­ner test in the secur­Ph­arm GUI or at https://ngda.de/loesungen/securpharm/securpharm-scanner.php