SOFTWARE SUPPLIERS
Connecting users to the verification system
Users (wholesalers, pharmacies and hospitals) who have received approval from BeMVO to access the verification system NMVS, have to implement the technical connection to the NMVS.
Their selected software provider or own IT department need to develop and implement a connection module to the NMVS. The first step is to connect to the development portal (sandbox): www.sws-nmvs.eu
The different steps are:
Functionalities for end users
In summary:
| Functionalities for end users | |
| Decommissioning transactions and Undo’s | in this case the status of the pack is changed and set to ‘Inactive’ or reset to ‘Active in case of an ‘Undo’. Be aware that for the transaction types ‘Destroy’ and ‘Stolen’ the undo is not possible. It might be wise to include a confirmation step for the user to execute such a transaction. Further, wholesalers can run a ‘Homogeneous Bulk’ and pharmacies a ‘Mixed Bulk’ transaction. |
| Information | the possibility to download at any moment the Product Master Data file for a selection of pack codes or for all. This extract contains by product code the ‘Designated Wholesalers’ (distributing in name of the MAH) and the MAH. If the MAH has filled in the national code (CNK), this information will also be present (be aware it is the information entered by the MAH). |
| Management | a set of processes to manage the end user connection: password renewal (needed every 90 days), Certificate renewal (every 2 years) and acceptance of the T&C (mandatory). |
| GUI | the possibility for the end user, in case of emergency due to technical problems, to connect to the NMVS using his internet browser. To do so his certificate must be installed in the browser. |
Consult here the table with more details on these processes: table1
End user interactions with NMVS
When a transaction is submitted to the NMVS, the NMVS will respond with a return code and description, indicating if the transaction was processed successfully or if an issue occurred.
Consult here the complete list of return codes, what can be the root cause and what should be done: return codes nl; return codes fr
Some of these return codes indicate that the verified or decommissioned pack is a potential falsification. The processes to follow in case of a potential falsification can be found in the section ALERTS.
From a software perspective, it is critical that the user is made clearly aware about the alerts he is generating and that a trace (log file) keeps track of all the transactions and generated alerts, and most important the alert-ID, so the concerned pack information can be traced back in case the user is contacted by BeMVO or by the authorities when the alert would have been escalated to them.
Most common ‘technical’ causes for False Alerts
Scanner configuration
Where the scanner of the end user is provided by his software supplier, the software supplier must make certain that this scanner is correctly configured and also remains in that state.
A typical issue is that the scanner is configured for QWERTY or German keyboard, where the user uses a AZERTY keyboard. Another cause can be that the scanner does not correctly read the GS-1 separator and that different data elements are concatenated together.
Transformation of scanned data
The (correctly) scanned information should be used as such to construct the transaction to be sent to the verification system. It should be avoided that the data elements received from the scanner are transformed based on any internal software logic.
Transaction repetition
It still happens that some transactions are running into a loop whereby the same transaction is re-sent to the verification system every x minutes.
Besides these causes, there are also the process errors made by the end users, e.g., multiple decommissioning of the same packs.
Problem shooting
User cannot perform the verification/transaction
Different reasons can be led to the user being unable to perform verifications. In general the reason can be identified based on the return code the user receives when trying to perform a transaction.
In these cases where the user cannot set up a valid connection to the NMVS, or he cannot immediately solve the technical issue preventing him from performing the verification, he can nevertheless continue to distribute and dispense the medicinal product.
However, in such case, the transactions performed must be stored in the user’s system and submitted to the NMVS when the connection is re-established (D.R. art.29).
|
User has no connection or certain transactions are rejected |
||
|
|
Invalid password |
The user receives a notification 10 days before expiry of the password. If not changed, the user will be locked after 3 connections with the wrong password. |
|
|
Solution |
Option a) BeMVO unlocks the user. Option b) Request BeMVO to be unlocked and receive a new password. ! Attention: the new password provided is to be processed as a new ‘initial’ password. The first transaction to run is the G445 Password change where the provided password is to be used as the ‘old’ password. |
|
|
Invalid password for one of multiple systems not interconnected |
When the password has been changed in one of multiple not interconnected systems from the end user, the other system(s) will receive a notification that they have to update with the changed password within 5 days. If not changed in time, the user will be locked after 3 attempts. |
|
|
Solution |
Option a) BeMVO unlocks the user. Option b) Request BeMVO to be unlocked and receive a new password. ! Attention: the new password provided is to be processed as a new ‘initial’ password. The first transaction to run is the G445 Password change on all systems where the provided password is to be used as the ‘old’ password. |
|
|
No Certificate or expired |
There is no certificate installed in the system of the user or the certificate used is expired. When the certificate is going to expire, the user receives an email with the link to the PKI server and the TAN code for downloading the certificate. As from day 30, he receives an email every day. If not installed, the user will be locked. |
|
|
Solution |
Download and install the new certificate if still available (before expiry of the current one). Otherwise, contact BeMVO for a new certificate and download + install asap. |
|
|
T&C not accepted |
The end user receives a notification by when a new ‘mandatory’ version of the T&C has to be accepted. If not accepted in time, the transactions will not be processed. |
|
|
Solution |
Accept the T&C immediately. The version to accept is mentioned in the system response when service G482 (current version 6001) |
|
|
Error in the XML structure |
These error codes indicate that the xml of the submitted web service is incorrect. Most frequent errors are: – A mandatory field is empty – The data in the field is invalid (e.g. invalid expiry date format) – Field too long (e.g. SN has more than 20 characters) – The input contains non-GS1 compliant characters |
|
|
Solution |
The end user software should validate these elements before the web service is submitted. |
|
|
No system response with an intermarket transaction |
When the end user receives the return code NMVS_TE_REQ_01, this indicates that the user tries an Intermarket Transaction (IMT), i.e., the verification of a non-BE/LU pack in the system of another country. The return code indicates that the EU Hub or the other system did not respond in time. |
|
|
Solution |
The user has to run the transaction again at a later moment. |
Consult here the table with all return codes from the system and possible actions for the end user and his FMD module
Table 1
Verification and Decommissioning web service transactions
|
Process ID |
Process |
Pharmacy/ |
Wholesaler |
Undo Y/N |
Comment |
|
G110 |
Verify Single Pack |
Y |
Y |
na |
Verification can be done at any moment. |
|
G112 |
Manual Verification Single Pack |
Y |
Y |
na |
Only to be used if pack cannot be scanned. Requires only PC and SN as input. |
|
G120 |
Dispense Single Pack |
Y |
Y |
Y |
Reminder : Undo only possible within 10 days and by same user. |
|
G122 |
Manual Dispense Single Pack |
Y |
Y |
Y |
Only to be used if pack cannot be scanned. Requires only PC and SN as input. |
|
G130 |
Destroy Single Pack |
Y |
Y |
N |
No UNDO possible. Add safety by requesting (double) confirmation. |
|
G140 |
Export Single Pack |
N |
Y |
Y |
|
|
G150 |
Sample Single Pack |
Y |
Y |
Y |
|
|
G160 |
Free Sample Single Pack |
N |
Y |
Y |
|
|
G170 |
Lock Single Pack |
N |
Y |
Y |
|
|
G180 |
Stolen Single Pack |
N |
Y |
N |
No UNDO possible. Add safety by requesting (double) confirmation. |
|
G115-G185 |
Submit Homogeneous Bulk |
N |
Y |
Undo possible for transactions where it is also possible for the Single Pack transaction. |
|
G188 |
Request Bulk transaction result |
N |
Y |
Be aware that a ‘Bulk’ transaction is not possible for non-BE/LU packs |
|
G195 |
Submit Mixed Bulk |
Y |
N |
Undo possible for transactions where it is also possible for the Single Pack transaction. |
|
G196 |
Request Mixed Bulk result |
Y |
N |
Be aware that a ‘Bulk’ transaction is not possible for non-BE/LU packs |
|
G101 |
Download Master Data |
Y |
Y |
This web service allows to download the product master file from NMVS, containing all GTINS in the system, the Marketing Authorisation Holder having uploaded the Product Code and the national code uploaded by the MAH. |
User management
|
Process ID |
Process |
Comment |
|
G445 |
Change password |
This web service allows to change the password of the user. The password needs to be renewed every 90 days. |
|
G482 |
Load Terms & Conditions |
Download the T&C document from the NMVS. The NMVS response XML contains also the Version ID to be used for the Confirmation step (currently version 6001). |
|
G483 |
Confirm Terms & Conditions |
This webservice allows the mandatory acceptance of the T&C. |
|
G615 |
Download client certificate PKI |
This webservice allows to download the certificate. Consult the documentation explaining the 2 ways to access and download/renew the certificate. |
|
GUI |
Graphical User Interface |
The verification, single pack transactions, password change and T&C confirmation is also possible for the user by accessing the NMVS with the GUI in the internet browser. To be able to access the NMVS with the GUI, the certificate needs to be installed in the browser. |
List of Software versions that have passed the Baseline Testing and are ready for implementing the connection to the LIVE environment of the National Medicines Verification System for End Users in Belgium and Luxembourg.
Update: January 2023
|
Company |
Software |
Version |
Pharm.Single Transactions |
Pharm.Bulk Transactions |
WHS Single Transactions |
WHS Bulk Transactions |
|
ADC NV |
ADC-FMD |
1.0 |
X |
X |
X |
X |
|
ADENTS |
ADENTS DISPAX |
0.5.0 |
X |
X |
X |
X |
|
ADHERTEC S.R.O. |
NMVS.ONLINE |
1.00 |
|
|
X |
|
|
ALN TECHNOLOGY LTD |
FMDPLUS |
1.2 |
X |
X |
X |
X |
|
ARVATO SYSTEMS GMBH |
ARVATO SMART LOGISTICS PLATFORMS – HEALTH CARE SUITE |
1.2 |
X |
|
X |
X |
|
BECTON DICKINSON AND COMPANY |
BD PYXISTM FMD VERIFY |
1.0.0.0 |
X |
|
|
|
|
C. CONSULT ADVICE |
ADMED/PHARMA |
201501 |
X |
|
|
|
|
CEGEDIM |
HOSPITALIS |
3 |
X |
X |
|
|
|
CENTRE HOSPITALIER BOIS DE L’ABBAYE (CHBA) |
CHBAPHA |
1.0 |
X |
X |
|
|
|
CENTRE SPECIALITES PHARMACEUTIQUE |
CSPPRODUCT |
1.0 |
X |
|
X |
X |
|
CERP |
NPI1 |
1.0 |
X |
X |
X |
X |
|
CHIPSOFT |
CHIPSOFT HIX |
6 |
X |
|
|
|
|
CHRH |
GINET |
1.0 |
X |
|
|
|
|
CORILUS |
CARECONNECT PHARMACIST |
1.00.66 |
X |
|
|
|
|
CPL |
CPLWEB |
4.0.0 |
|
|
X |
X |
|
CVBA VOORUIT |
VOORUIT PRODUCT |
1 |
X |
X |
X |
X |
|
DAXANT SA |
CHECKFMD |
1.0.0 |
|
|
X |
X |
|
DEBISCOM BVBA |
MERCATOR |
V3 |
|
|
|
X |
|
EASI SA |
SOFT ADFINITY |
1.6 |
X |
X |
X |
X |
|
EPC FAMILIA |
EPC |
02 |
X |
X |
X |
|
|
FARMAD |
TWIN |
BETA 2 |
X |
|
|
|
|
FEBELCO |
PDC FMD |
0.1 |
|
|
X |
X |
|
FRESENIUS NETCARE GMBH |
SAP OER |
7 |
|
|
X |
|
|
GOED ICT |
VIANOVA (PHARMACY) -ESCAPO (WHOLESALER) |
20.9.2 |
X |
X |
X |
X |
|
H. ESSERS |
H. ESSERS WMS |
5.8 |
|
|
X |
|
|
HANFF GLOBAL HEALTH SOLUTIONS |
HANFF |
1.0.0 |
|
|
X |
X |
|
INEO |
MERCATOR |
1.0.0.0 |
X |
X |
X |
X |
|
INFOHOS |
NMVS-CONNECTOR |
1.0 |
X |
X |
|
|
|
IPHARMA LOGISTIC |
IPHARMA |
1.18 |
X |
|
|
|
|
LOGIPHARM |
LOGIPHARM |
1.105.0.1 |
X |
X |
|
|
|
MAUVE MAILORDER SOFTWARE GMBH |
MAUVE SYSTEM 3 |
2020.2 FF |
X |
X |
X |
X |
|
MEDASPIS B.V. |
MEDASPIS CONNECTOR PLUS (FOR PHARMACIES AND HOSPITALS) |
2018.08.27 |
X |
X |
|
|
|
MEDASPIS B.V. |
MEDASPIS CONNECTOR PLUS (FOR WHOLESALERS) |
2018.08.27 |
|
|
X |
X |
|
MEDITECH |
MTULTRAFICTUS |
1.0 |
X |
X |
|
|
|
MEDSOC |
APOMEDSOC |
1 |
X |
X |
X |
X |
|
MMS-SOLUTIONS |
YGLOBAL |
8.0 |
X |
X |
X |
X |
|
MOVILITAS |
MOVILITAS.CLOUD-ARVATO CONNECTOR |
1.2.0 |
X |
X |
X |
X |
|
MULTIPHARMA SCRL |
MULTIPHARMA-FMD |
2.0 |
X |
|
X |
|
|
NEWPHARMA |
SOAP UI |
5.4.0 |
X |
X |
|
|
|
NEXTPHARM |
NEXT |
V22 |
X |
|
|
|
|
OBASI |
OBASI SOFTWARE |
1.0 |
X |
X |
|
|
|
OCP |
PORTAIL |
1.0 |
|
|
X |
|
|
OFFICINALL |
OFFICINALL |
19 |
X |
|
|
|
|
OPTEL GROUP |
OPTEL CERTA |
1.0 |
X |
X |
|
|
|
OPTIMA SYSTEMS |
MEDTRACS |
1.0 |
X |
X |
X |
X |
|
PHARMABELGIUM-BELMEDIS |
PHBFMD |
1.0 |
|
|
X |
X |
|
PHARMAGEST |
FMD-ENGINE |
1.0.0 |
X |
X |
|
|
|
PHARMONY SA |
PHARMONY ONE |
1.1.564 |
X |
X |
X |
X |
|
PROPHAC |
PRONAV |
1 |
X |
X |
X |
X |
|
QUICK PHARM SOLUTIONS LIMITED |
EASYFMD |
1.0.5.6 |
X |
X |
X |
X |
|
RFXCEL CORPORATION |
RFXCEL TRACEABILITY SYSTEM (RTS) |
5.8.2 |
X |
X |
X |
X |
|
S.A. LOGAL |
EVOLUTIVE COMPTA |
79 |
X |
X |
|
|
|
SAP |
SAPICH |
2268 |
X |
X |
X |
X |
|
SBIM |
GCLWIN |
1B40 |
X |
|
|
|
|
TCK GMBH |
NMVS CONNECT |
1.1 |
X |
X |
X |
X |
|
TRACELINK |
TRACELINK LIFE SCIENCES CLOUD |
2018.5 |
X |
|
X |
|
|
TRACINGINMOTION BVBA |
TRACFMD |
1.0 |
X |
X |
|
|
|
UZ ANTWERPEN |
UZA ZIS-APOTHEEK |
9.7 |
X |
X |
|
|
|
UZ LEUVEN |
UZL-DUMMY2 |
1.0 |
X |
|
|
|
|
VPHARMA |
VPHARMA |
1.0 |
X |
X |
X |
X |
|
VZW NETWERK HIERONYMUS |
DIBROSI INFORMATIE SYSTEEM |
1.0 |
X |
X |
|
|
|
Wininfo |
WininfoNMVS |
1.0.0.0. |
|
|
X |
|
|
XPERTHIS |
XPERTHISFMD |
0.1 |
X |
X |
|
|
|
ZETES UK LTD. |
ZETESOLYMPUSFMD |
1.0.0 |
X |
X |
X |
X |
Important information concerning the urgent implementation of the user interface Version 5.
It is mandatory to switch to interface V5 before October 2023
You can find info in this document
