Warning - Common cause of alerts in end user systems
Based on detailed analysis of the alerts that have occurred so far during medicines verification, it has been found that up to half of the alerts may occure due to failures in the end user system solutions.
Primarily, this is a mismatch of lower and upper letters or a substitution of Y and Z in the batch number and medicines verification with "00" at the expiration date. For all 3 types of alerts, we've provided information directly to representatives of IT companies for end-users systems. Nevertheless here are some basic information regarding the end-users system solutions connected to the national verification system and more details are also available in the Solidsoft Reply confluence database for legitimate users.
Therefore, we ask all end-users software vendors to pay extra attention to these issues.
I.1. Big x Lower letters
Both batch IDs and serial numbers are case sensitive. Always match the loaded characters with the values recorded in the CZMVS database.
The permissible GS1 features are: GS1 General Specification - page 456 set 82
I.2. Replace Y and Z - Problems of correct 2D code scanners settings
If the scanner is not set up properly, a large number of alerts are triggered unnecessarily. The Z / Y swap problem occurs in a number of national keyboards, not only on Czech ones. The end-user, when delivering solutions to FMD issues, is likely to expect this problem not to be addressed. NOOL has no generic solution above mentioned problem, we can only advice and expect that the end-user uses settings according to the GS1 specification.
More about this issue, for example, in Confluence database/Downloads and resources (for registered only)
Perhaps there is also a sensor configuration that mimics the numeric keypad instead of the keyboard (Alt + character number). Most scanners emulate this behaviour. For more information, see Confluence database / Using barcode scanners as keyboard emulators and subpages.
I.3. "00" on the date
Some SWs used by end users are trying to convert the expiration date, where there is "00" in DD on a particular day.
In terms of alerts, however, it is the determining outcome of comparing the data match to ID and storage. If "00" is on the packaging, it must be read and read, and only then compared to the record in the national repository.
User interpretations of such data (such as alerts on expired expiration date) must be consistent with GS1 standards.
For more details see: GS1 General Specifications: 3.4.7 Expiration date: AI (17)
According to GS1 specifications, there are only 2 options: either the exact date is used or only the month and year are used. The format for the date entry is a fixed length of 6 numeric positions. So, the variation when used as the EXP date only a month and a year can only be encoded in a single way, and it is zero with DD positions.
This situation is more acute in our country than elsewhere, because our NCA has traditionally accepted (and will probably continue to do so) the usability date in an eye-readable format mm / yyyy.
EMVO has now clarified that 00 in the DD is not 00: 00: 00: 01, but it must be understood as 23: 59: 59: 59 the last day of the month!
You can find the EMVO materials for the issues described above here: