Locations and requirements for barcoding can be set up under the settings page. Navigate to settings and select the "Bar Code Setup" tab to review the setup options.
Locations
Barcode settings can be configured on a branch by branch basis. Use the branches drop down list to select the branch you want to setup.
Under the locations section, locations can be created in the system to indicate where a body is and what is happening throughout various processes. This can be as simple or complex as you want it to be. Some default locations exist in the system but an unlimited amount of custom locations can be added to suit your needs. To create a location, simply type in a name for the location and select if anything is needed to complete the step at that location.
A list of all locations that are setup for bar code scans will display in the location list.
Options are also available to make a location scan repeatable, make it a global resource that can be shared across different SRS branches, or if the resource should show in Portal. The option to make repeatable is particularly useful to ensure certain steps are not entered more then once. For example, an embalming only happens once, so turning off the repeatable scans option for that step will ensure that it can only ever be entered once on a case.
Once you have your locations set up, labels can be printed via the print icon below the location list. Each resource will have a name on the right side of the label along with a unique resource code. Stickers of the barcodes can be placed in their corresponding locations for easy usage.
Location Requirements
Under the Bar Code/Branch Requirements section, requirements can be set up for locations so that a location scan cannot be entered out of sequence. For example, a body cannot be taken out of the cooler if it was never put into the cooler, or a cremation cannot end if it has not started.
To set up a requirement, simply select your location from the resource 1 list, and add the location that is required under the resource 2 section.
For example, if you want Cooler Out to require Cooler In before it can be scanned, you would set Cooler Out to Resource 1 and Cooler In to Resource 2. Now if someone tries to scan Cooler Out before Cooler In, they will receive an error message letting them know about the requirement.
