...

Those are just a few of the areas we’ve considered. Our goal in ClinSpark is for users to leverage the scanner as much as possible for the best possible user experience in context of various workflows as a way to make a foot pedal not necessary.

Troubleshooting

When If your scanner doesn’t seem to work in Clinspark with ClinSpark, a good first step would be to try & to scan the barcode in a text editor, like notepad. A more advanced editor like Notepad++ comes in handy to detect the correct characters.

The procedure would be as follows:

• Open Notepad++

• In Notepad++ go to View > Show Symbol > Show All Characters:

• 

  Scan a barcode

• The result should look like this:

...

• The cursor is on the next line, and that the CR LF (Carriage Return, Line Feed) special characters are placed after the barcode. If that is not the case, re-check the steps at the section Configuring the LS4208 and LS2208 for ClinSpark

• Characters match the case (F instead of f), and that dashes and numbers are displayed correctly. If that is not the case, re-check the steps at the section QWERTY and AZERTY

• Clinspark ClinSpark expects the barcode to come in about 400msec from start to end. If the barcode is appearing appears very slowly in Notepad++ notoriously slow, check the connection or try another scanner.

A One last thing to try, is entering the barcode manually in Clinspark ClinSpark using Chrome Developer tools & and the barcodeListenCallback() function. Clinspark ClinSpark should then behave similarly as if the barcode was processed.

• Open ClinsparkClinSpark, and navigate to the dashboard.

• Open up Chrome Developer tools

• Go to the Console

• Ignore possible warnings in the console, and type on the last line, after the > the following: barcodeListenCallback("S1"). Replace S1 with the barcode you actually want to try/enter.

• 

  Press enter. Clinkspark ClinSpark will now execute that barcode, as when it would scan with a barcode scanner.

...