QR codes and rapid execution
FlaskTrack can generate QR codes that help users open the correct record or execution action at the bench.
QR code types
Entity QR codes
Entity codes open a record such as a sample, batch, species, ingredient, tool, plasmid, or other supported object. They are useful for labels, storage containers, workstations, and printed packets.
Scanning an entity code does not bypass authentication or permission checks. The user must still sign in and be authorized to view the record.
Execution QR codes
Execution codes open a specific batch or sample workflow context so an operator can review scheduled steps and complete the intended action.
The server still enforces:
- organization membership;
- role permissions;
- current entity state;
- required structured form fields;
- inventory availability and configured effects;
- compliance authorization and checklists;
- electronic-signature requirements.
Print and placement
Use a label size that remains scannable after printing. Include a short human-readable identifier so the record can still be located when the code is damaged.
Avoid placing codes where they can be confused between adjacent containers or equipment. Replace labels after reassigning or retiring the physical object.
Security
A QR code may reveal a record identifier or URL. Do not treat it as a secret or as proof of identity. Do not publish operational execution codes in public locations.
Troubleshooting
- Code opens the wrong record: retire the incorrect label and print a new code from the authoritative record.
- Permission denied: verify organization membership and the user’s role.
- Step cannot be completed: review required fields, timing, inventory, compliance policy, and signature requirements.
- Camera cannot scan: improve lighting, clean the label, or enter the displayed identifier manually.