Label Migration Process

Any customers upgrading from a version of ClinSpark prior to 1.5 will need to go through a label migration process. The follow guide serves as a way to become familiar with the settings unique to this functionality.

Barcode Settings

Many system-level barcode settings exist in Administration > General Settings > Barcodes. These exist to establish requirements for generating barcodes in ClinSpark.

These settings are always visible to customers, but only Foundry Health superadmins are able to modify them. This is due to the implications these padding, delimiter, and prefix settings have across a variety of ClinSpark features that leverage barcodes, as well as site lab interface workflows.

Barcode Padding Characters

Barcodes can be padded from zero to twenty characters for barcode generation. This padding will apply to all label templates.

Include Delimiter for Multi-Part Barcodes

If container(s) are associated with a sample path or lab panel, the barcode can optionally include the ‘-’ delimiter prior to the container suffix.

Delimiter Included

Delimiter Not Included

Optionally Include Specimen Container Prefix

If container(s) are associated with a sample path or lab panel, the specimen container can optionally include a prefix.

Specimen Container Included

Update Barcode Prefix

The prefix to barcodes can be updated as needed. The prefix in ClinSpark also needs to match the prefix of the label template.

After Upgrading

Default label templates will be available in your ClinSpark environment to edit upon upgrading.

Review Label Templates

Once a UAT environment has been made available, the default label designs should be reviewed. These labels should be reviewed by printing the templates to a Zebra printer.

Printing Labels for Review

Using a Zebra printer, label templates can be printed from the following ClinSpark modules:

Label Template Name	Where to Print

Label Template Name	Where to Print
Device	`Devices > Manage > Actions > Print Barcodes`
Item	`Barcode Printing > Labels` > Complete Required Fields on the Screen > Transfer Label Actions = Include Transfer Labels `> Print`
LIMS	`Lab > LIMS Labels` > Scan Sample for Collection with a created Lab Order
Sample Batch Data	`Samples > Processing` > Printed During Configured Step
Sample Container	`Samples > Packaging > Action > Print Barcodes`
Subject	`Barcode Printing > Subjects` > Complete Required Fields on the Screen `> Print`
User	`Administration > Users` > Select Users Hyperlinked Name `> Actions > Print Barcode`
Void Container	`Samples > Intervals > Action > Print` (Next to the Interval Barcode)

Update Label Templates

Any necessary changes should be made within the ZebraDesigner3 design utility software. As a starting point, we provide editable label template .nlbl files for all default labels that come stock in your environment.

Once these labels have been updated the .nlbl file should be saved and made available for future reference. It is also helpful to create label specifications (example) to keep track of requirements.

Import New Label Design

Once a label has been redesigned and stored to the printer it can be imported to the current label design. Alternatively, a new label template can be added. Once barcode verification has been complete the label template can be saved.

Please visit our Merge Tag Reference page for next steps if new merge tags are needed for a label design.

Can I use Labels printed in previous versions?

No, any labels previously printed will need to be reprinted for use.

Barcode Verification Troubleshooting

In order for a template to become active, it is required to scan the three example labels. If the barcode is not verified ensure the barcode example output prefixes also match the configured prefixes in Administration > General Settings > Barcodes.

For example; Item Prefix = 9, the merge tag for ITEM_BARCODE Example Outputs need to start with ‘9’ not ‘F’. Please reach out to Foundry Health via a service desk ticket to update any of these Example Outputs.