||Alert code (FiMVS)
The pack cannot be decommissioned.
The pack is already decommissioned at this location.
|The user attempted to decommission (not as Supplied) a pack that was already decommissioned.
||1320000, 51320200, 51320201, 51320300, 51320301, 51320400, 51320401, 51320500, 51320501, 51320600, 51320601, 51320700, 51320701, 51320800, 51320801, 51320900
A complete list of all return / alert codes beginning with 5132 with their descriptions can be found in this document on FiMVO website.
Possible root causes of the alert:
- The same user has already decommissioned the pack. The alert message will in this case state that the decommissioning was performed at the same location.
- Another end user has already decommissioned the pack. The alert message will in this case state that the decommissioning was performed at another location.
- In some rare cases it is possible that two packs with identical identifiers have been released on the market by the MAH/OBP and the other one of these two packs has already been decommissioned.
||Alert handling procedure
Pharmacy/ Hospital pharmacy/ Dispensary/ Wholesaler
- Check the pack status in FiMVS, if it is not evident based on the alert message.
- Undo the previous action on the pack, i.e. reactivate the pack.
- If the undo is successful, the original transaction was performed by the same user not more than 10 days ago, which suggests that the original transaction was cancelled but the user forgot to return the pack to the system. The pack state is now active, and the pack can be dispensed/decommissioned. The user must investigate the reason for the error and take preventive action not to repeat the error.
- If undo is not possible, and the system returns the exception “The pack cannot be reactivated. Time limit exceeded.”, the original transaction was performed more than 10 days ago by the same user and the pack cannot be reactivated anymore, see chapter 6.8. If the system returns the exception “The pack cannot be reactivated. It was decommissioned/supplied at another location.”, the original transaction was performed by a different user. This may be a falsified pack. In this case, the pack must not be dispensed until the reason behind the alert has been clarified. The pack should be set aside and clearly marked that it cannot be dispensed. See also chapter 6.9.
- If it is not possible to review the pack audit trail within the user’s own system, the user should contact FiMVO for the audit trail of the pack (firstname.lastname@example.org)
- If the audit trail implies a product defect or falsification, this must be notified to the MAH either through the wholesaler’s product defect system or directly via email or phone. Notifications must include the human readable data of the pack, 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. N.B. The pack should not be returned to the wholesaler before the cause of the alert has been resolved and / or before the return has been agreed with the MAH.
|MAH / OBP
If the pharmacy / wholesaler contacts the MAH/OBP, FiMVO can be asked to review the pack audit trail (email@example.com).