Print a Specimen Barcode (Label)

A specimen label can be printed at any stage of the specimen life-cycle, and as many times as needed.  Specimen labels are typically affixed to specimen containers and/or specimen reports, depending on the workflow.  The content and layout of a specimen label is fully configurable (see Edit a Label) and there are two distinct specimen labels, type 1 and type 2,  that can be independently configured and printed, e.g. for different containers, or, one for a container and one for a report.

Step 1

Select the Specimens option from the main menu.

Note: The visibility of main menu options is determined by menu permissions. For more information about configuring menu permissions, see: Understanding menu permissions.

Step 2

Assuming the current role has the corresponding event permission(s) (see Understanding Event Permissions), the Print Barcode actions (type 1 and type 2) are available both from the specimen row within the specimen list-view, and from within the specimen record-view, if displayed.

Select the Overflow icon (“…”) for the specimen row corresponding to the specimen for which the label is required.

Step 3

Select Print Barcode (type 1) or Print Barcode (type 2), as desired. The browser’s print‑preview window will then open, displaying the selected label in its current configuration.  The example below (with the form panel truncated) shows a label configured to display both a linear barcode and a QR code side‑by‑side, along with the encoded number and three specimen attributes, all of which are optional. It also illustrates three identical rows, representing three duplicates of the same label type.

Step 4

Select Print (or the equivalent option) in the browser’s print panel to send the label to your configured label printer (or any other selected printer).

Note: The option Print Barcode would more accurately be named Print Label, as labels do not necessarily contain a barcode. This terminology may be updated in a future version.

 

Was this article helpful?
0 out of 0 found this helpful