Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The process of getting a label template into ClinSpark must be completed with physical access to the Zebra printer. It’s recommended that the computer being used for this process be connected to the Zebra printer via direct USB. Foundry Health has not developed or tested this process to work over any ‘networked’ printer configurations, therefore it’s strongly recommended to complete these steps via direct connection.

...

After saving your template file for later editing, you’re ready to upload the new template into ClinSpark.

The ClinSpark Agent will look in one specific location for the label files: your printer’s internal flash memory. This point has been made before, but it is worth repeating:

...

Info

The ClinSpark Agent will ONLY look for template files that are stored within your printer’s internal flash memory. It

...

will not find templates stored

...

on the local PC file system.

Within the ZebraDesigner software, click File > Store. Choose “Internal Flash” from the “Printer memory location:” dropdown menu, and make sure the other printing settings are appropriate for your printer model.

...

Everywhere you plan to fill information with merge tags should be listed below the dropdown, and you should see each merge tag in the “Prompt” column. The “Value” column can remain blank, as the values will be pulled dynamically from ClinSpark.

...

Once the template has been stored to the printer, the rest of the workflow is completed through ClinSpark.

...

Above is an example of how this light will look on a ZD410 when saving to internal flash.

Upload Template in Barcode Printing > Manage

...

To confirm a design 3 example barcodes need to be scanned. For that to work it’s crucial to have the prefix set in Administration > general settings General Settings > Barcodes to match the Example Output under Label Merge Tags in the same section.

...

If the barcode fails to scan, a good test is to enter the expected barcode as a barcodeListenCallback() event in Google Chrome Developer Tools. This doesn’t require an actual scan, and bypasses any additional errors that can be causing the barcode not to scan (e.g., misprinted barcode, misconfigured scanner, Chrome window not having focus while scanning etc).

...

INSERT VIDEO HEREhttps://vimeo.com/605754459

Clearing out the Zebra Printer Memory

...