6.4 The batch identifier mismatches the recorded batch identifier

The batch identifier mismatches the recorded batch identifier.

OR

The batch identifier mismatches the recorded batch identifier. The length or format does not match what has been uploaded. Possible scanner or software malfunction. 

Pharmacy/ Hospital pharmacy/ Dispensary/ Wholesaler

1. Check the data of the transaction in the pharmacy system (if possible).
2. Compare the data of the transaction (especially the batch data) to the human readable data on the pack. If the data matches, the most probable cause is that the batch data differs from what has been uploaded to the EMVS. In this case, move directly to point 6.
3. If the transaction data (batch data) does not match the data on the pack, scan the 2D code again. If this is successful and does not generate an alert, the pack can be dispensed.
4. If this still fails, try using another scanner or enter the information manually. If the 2D code scanning or manual entry is successful and no alert is generated, the pack can be dispensed. NOTE. If the 2D code cannot be scanned and the human readable data is also illegible, the pack must not be dispensed. The pack must be reported to the MAH as a product defect.
5. If scanning is successful with one scanner but not another, the problem could stem from the scanner’s configuration. Check that the scanner has been correctly configured. Contact your IT supplier to solve this. The scanner should read and transact data without changing it in any way.
6. If the pack cannot be dispensed, it should be put aside, and investigations should continue with the MAH. Alerts should be notified to the MAH through the wholesaler’s product defect system or directly via email or phone. Notifications must include the pack’s human readable data, i.e. product code, serial number, batch ID and expiry date. It is helpful to send a photograph of the pack as an attachment. The photo should include the 2D code and the human readable data on the pack.

1. Check the batch ID and serial number in the alert message, is the serial number linked to the batch and does the data match the data uploaded to EMVS?
2. If the data differs, the batch data printed on the pack may differ from the batch data uploaded to the system, or there is an error with the scanner or an error in manual data entry. 
3. If the end user does not contact the MAH/OBP, FiMVO (nmvs@fimvo.fi) may be asked to check the pack’s audit trail. Often the alerting pack has been successfully verified and/or decommissioned after the alert. In this case the end user does not usually contact the MAH/OBP. FiMVO can also contact the end user in question, if necessary.
4. If the end user requests clarification with an attached photograph of the pack, check that the 2D code on the pack has the correct information. In addition, check also that the 2D code data is the same as data uploaded to EMVS.
5. If the data on the pack differs from the data uploaded to FiMVS, the MAH should, if necessary, request the distributor to place a sales ban on the batch for the duration of the investigation and work with the OBP to solve the situation. The MAH should pay particular attention to informing pharmacies, wholesalers and Fimea in order to keep them up to date of the situation and to ensure uninterrupted treatment and patient safety.
6. If the investigations confirm that this is a genuine falsified medicine, the product defect process should be followed (Class 1 product defect). The MAH is responsible for the planning and implementation of the required actions. Fimea oversees that the measures are adequate and appropriate. (https://www.fimea.fi/web/en/supervision/pharmacovigilance/product_defec…).