Get started

> Plug in the network cable

> Connect your APP to our API

> Show the package

> Done.

The Healthcare challenge

Why is product identification still painful and error-prone in healthcare?

We found out 3 reasons:

1. Medical supply barcodes are complex
2. Scanning requires skills
3. Code parsing and processing is hard

Fast, Always on, hands-free and real-time traceability of supplies

Real-time traceability is challenging because a ward nurse on a busy shift has a patience of a toddler waiting for a snack. If a scan takes long or is not instantly available - it's not happening.

Our scanner is built for the 'grab-and-go' reality - meeting MDR traceability requirements without the wait. Withdraw and consumption scanning is completely hands-free.

Scanner's event data - freshly served

Event data is delivered to your app through two different APIs: REST and Websocket. Providing easy connectivity and real-time access when needed.

Event data includes information, such as: date/time, scanner name, unique device identifier (e.g. GTIN / HIBC UPN), currently active function button, context, production date, expiry date, LOT and SN.

What's with the buttons?

Set of function buttons is organized by screens. E.g. in the Ward supply room default screen you see Withdraw and Restock buttons (localized versions available).

There are several screens available for OR. The default OR screen has three buttons: Use, Discard and Return.

You select the screen for the scanner that best meets your tracking and stock-keeping needs.

Showing supply names on the screen

This is optional but it's a nice touch. If you want to show your users the product name on the screen, send the updates to our Products API. This way supply's global unique identifier is tied to your product name and we can show it on the screen when the scan happens.

No more guessing

Our scanner reads all the codes on a package and chooses what data is relevant. No guesswork needed.

Supports MDR traceability

The scanner supports reliable UDI data capture on multiple standards.

Solving the complexity

UDI codes don't solve all the problems. Reality is complex.

UDI codes come in different standards, there are packages without UDI codes, packages where data is spread between multiple barcodes and a ton of barcodes that are not meant to be read. You don't want to store manufacturer's internal codes or company's website addresses on patient records.

We have designed our scanner to survive such cases.

Context is King

We provide implicit and explicit context mapping. Implicit context mapping happens when your App assumes context based on a scanner ID. E.g. if your OR supply app registers Scanner A to OR 1, then data from Scanner A is implicitly mapped to that OR context.

Explicit context can also be given directly to the scanner by reading a special context code that stays on the screen while batch of codes have been scanned. E.g. you can read a cost center's context code or show a case number from your mobile app in a supply room.

This way, events data is linked to that context. E.g. your app knows what product, with what tracking details, left the supply room A, taken by which cost center.

Explicit context can be set as required for a scanner.

No PC needed

Our Scanner is a pure IoT device, so it cannot be directly attached to a PC. All communication happens over APIs.

Same scanning data can be read by multiple applications.

High security by default

From a hardened embedded OS to strict back-end policies, we control everything. We secure every connection with TLS 1.3, while all interfaces are governed by the OAuth 2.0 protocol. To ensure total isolation, your organization receives separate credentials for test and production environments. For every session, your App fetches a temporary JWT token from Pointerio's authentication service. Also each scanner is locked to talk only to your specific environment.

No patient-identifiable information (PII) is handled or stored. OTA updates for OS and App are available. In the event of loss or theft, scanner's access can be revoked.