Facility Access with Employee, Patient or Visitor Tracking

The codeREADr app and Web service empowers you to capture, track, monitor and report in ways that were either impossible or impractical before. Why? Because of the ready-availability of low-cost, feature-rich smartphones and tablets along with enterprise apps – like codeREADr. This is especially true for special access control and monitoring requirements, e.g., for temporary, remote or multiple monitoring points.

The cost is very attractive, too. For a single access point you could buy one iPod touch and then license codeREADr for as little as $9.99 monthly. If you don’t have IDs, there are many choices for printing them (see below) in advance or as needed.Facilities that already have tracking & control systems in place can work with their current service providers to integrate with codeREADr using our extensive APIs. In that way they get the best of both worlds – their purpose-built application plus codeREADr for mobility and special applications.

Facilities without such systems use codeREADr as a simple employee, patient or visitor tracking tool – basically a check-in and check-out function at one or more points within the facility, in both fixed and mobile locations. The application is very similar to how codeREADr is used for attendance tracking. That basic functionality can be used for one location or for multiple locations simultaneously or consecutively. For example, you could track a patient on arrival and through every step of their visit, collecting timestamps, location and other data all along the way.

  • Starter – Record-Only: For this type of service you won’t need a validation database. When the app user scans the barcode ID, you will prompt the app user to enter information regarding the person or process. A potential tradeoff with record-only services is that you cannot give directed information about that specific person to the app user as they scan their barcode. For example, with a validation service you could give them the name and related details about the person scanned. You can’t do that with a record-only service. Another tradeoff is that, instead of scanning, you can’t use the text/voice-search feature to search the validation database. Step by Step Instructions.
  • Intermediate – Validation: For this type of service you will need a validation database.  When the app user scans the barcode ID, you will prompt the app user to enter information regarding the person or process. You can also give the app user directed information about that person or specific instructions as they scan their ID. For example, you can tell them if there are any special accommodations required. And, with validation services, you can use text- or voice-search if the ID doesn’t have a barcode or NFC tag. Step by Step Instructions.
  • Advanced – IT/Developer Integration: IT/Developers can seamlessly integrate codeREADr into their existing applications and back-end using our extensive set of APIs. The can also use advanced features such as regular expression, contextual variables and Webify.

Capturing Asset IDs:  Scan barcodes, tap NFC tags, text/voice entry and search database

IDs should ideally be printed with a barcode (low cost) or an NFC tag (somewhat expensive, plus not all smartphones are NFC enabled yet). Alternatively, you could simply print each ID with a human-readable number for text/voice-entry. If you are using a validation database, you could use the apps Look-Up feature to text- or voice-search for the name or ID in the database.  It’s remarkably fast and accurate even when searching for the name or first few characters of the ID.

For record-only services, you could distribute IDs with QR codes printed on the media. You can embed an ID, a name or both in the QR code. You can easily print QR labels using low-cost programs, such as iBarcoder for PC and MAC.

Alternatively you could use the barcode already on the ID, if it has one. With a validation service this is no problem because you would have already associated the barcode ID to the person’s name – see importing a CSV file. However, with a record-only service you have to associate this ID with the person’s name when you do your reporting.  If you are familiar with Excel or other database programs, it’s relatively simple to do.

in Best Practices with Instructions