GAPS: Scan 2D DataMatrix

[mark-prins]

Is your feature request related to a problem? Please describe 👀

Note: we've been asked to implement a standard format for the DataMatrix - but the standard doesn't exist yet. To meet the requirement, we'll define the standard and implement against that. Code changes later as a result of standard (re)definition will be costed additionally.

Description: to look up an individual asset scanning a QR code

1. Navigation: Asset Register: List View > Scan QR Code button Navigation: CCE Inventory: List View > Scan QR Code button
2. User clicks on the Scan QR code button
3. For mobile device: system opens the camera
4. If a matching record is found in the registry, user is redirected to the Asset Register: Detailed View of the asset / CCE Inventory: Detailed View of the CCE
5. If no matching record is found, a popup window: “Asset not found” / “CCE not found”

User Story A.7.2

As a…	Health Care Worker (HCW) or warehouse worker
I want…	To be able to scan our custom QR barcode that has been attached to the CCE
So that…	I can quickly navigate to the CCE’s details in the CCEI register

Solution A.7.2 The system will allow users to scan the unique QR code printed in User Story A.7.1 by using the device’s camera or a dedicated barcode scanning device. Once scanned, the system will navigate the user to the detailed view for that particular CCE.

Describe the solution you'd like 🎁

• Define a standard for the datamatrix ( delimeters / field identifiers )
• API to lookup items by code
• UI for scanning and redirection

Specification

4.1.2 Required barcode 2D Datamatrix information

Information included in the barcode 2D Datamatrix must include the following in the listed order, as defined in the GS1 General Specifications (GS1 code in parentheses):

• Global Trade Item Number (GTIN) containing the allocated company prefix and item reference (i.e. manufacturer and model) using Application Identifier (01)
• Production date using Application Identifier (11) followed by six numerals signifying year and month and day the appliance was produced. As specified in the GS1 General Specifications, if it is not necessary to specify the day, the field must be filled with two zeros (e.g. 11170300 for March 2017)
• The unique serial number for the individual appliance using Application Identifier (21)
• PQS number using Application Identifier (241) followed by seven alphanumeric characters (e.g. 241E003001 for the PQS product number 001 in PQS category E003). The AI (241) identifies a customer part number per the GS1 General Specifications.

The following should be added as far as possible bearing in mind the 2335 alphanumeric characters limitation of 2D Datamatrix codes and should follow the PQS product sheet descriptions and abbreviations.

• Title (Type)
• Energy source
• Vaccine storage capacity (litre) plus 5
• Vaccine storage capacity (litre) minus 15
• External dimensions cm (WxDxH)
• Waterpack storage capacity (Kg)
• Waterpack freezing capacity per 24h (Kg)
• Energy consumption (stable running, continuous power) KWh/24 h
• Energy consumption during freezing (KWh/24 h)
• Hold over time (hours)
• Climate zone
• Freeze protection (Y/N)
• Refrigerant type
• Temp monitoring device included (Y/N)
• Voltage stabilizer included (Y/N)
• Warranty period (start-end date)

Further links to:

• PQS Specification sheet
• Manufacturer’s Operating Manual
• Manufacturer’s Warranty
• Manufacturer’s Maintenance Instructions

Additional context 💌

Moneyworks Jobcode 🧰

[adamdewey]

So UNICEF actually gave us a document that they wanted us to use to base the standard on (or it was like a quasi standard anyway)

See here: https://drive.google.com/drive/folders/1qTEG8hofvf0gLO8pdXbadVT0RN1HtNdO

[mark-prins]

thanks! I'm unsure how to parse the additional fields (in red) which have been added. the others have delimiters specified but not those ones. It gives us something to work with though

[adamdewey]

Hmm yes, it's a bit vague eh!

But I guess we can sort of try to define it ourselves inside those constraints hopefully.

They do say this: "The following should be added as far as possible bearing in mind the 2335 alphanumeric characters limitation of 2D Datamatrix codes and should follow the PQS product sheet descriptions and abbreviations."

And these are the PQS product sheets they're referring to: https://apps.who.int/immunization_standards/vaccine_quality/pqs_catalogue/categorypage.aspx?id_cat=17