πŸ“– FLAVORx LogBook
✨ The Future-State Workflow

Two quick taps turn every fill into a permanent, audit-ready record.

Before a single drop of water is dispensed, the Fillmaster device captures who performed the operation and which transaction it belongs to. Everything that follows β€” drug, lot, expiry, flavor, water volume, timestamp β€” is stitched to that identity automatically and pushed to the LogBook cloud. No paper. No transcription. No gaps.

2
new steps added up front
~6 sec
added to each fill
100%
of fills traceable to a user
0
PHI identifiers stored
What changes

The same fill β€” now with traceability built in

The technician's hands barely change what they do. The record does all the heavy lifting.

πŸ—‚οΈ Today

  • β€” Scan drug, pick flavor, dispense water.
  • β€” No durable record of who ran the operation.
  • β€” No link between the fill and the pharmacy's transaction.
  • β€” Audit prep means digging through paper logs or memory.
  • β€” Recalls require manual lot reconciliation.

πŸ“– With LogBook

  • βœ“ Badge scan stamps every fill with the operator.
  • βœ“ Transaction scan ties the fill to the pharmacy's own tracking code.
  • βœ“ Drug, lot, expiry, flavor & volume captured automatically.
  • βœ“ Searchable cloud record, ready the moment an auditor asks.
  • βœ“ Recall? Filter by lot number in seconds.
Interactive demo

Step through the operator experience

Tap the buttons on the screen β€” or use a step on the left β€” to walk the full flow. The two New steps at the start are what make LogBook possible.

Scan badge to begin

Tap your badge on the reader β€” or sign in with your PIN.

Scan transaction #

Scan the barcode on the work order, or key it in.
πŸ”³ SCAN OR ENTER
TX-4471-0098|

Scan medication

Scan the 2D barcode on the stock bottle.

Which flavor would the customer like?

Ready to dispense water?

Reconstitute Amoxicillin 400 mg/5 mL
Water to add: 62 mL Β· Flavor: Grape

Dispensing water & flavor

First half with flavor, then the rest with water β€” exactly as logged.

Operation complete

βœ“
Record sealed and uploaded to LogBook.

1 Β· Scan badge New step

The operator taps their staff badge (or enters a PIN). This is the foundation of accountability β€” every downstream action is now attributable to a named, trained user.

Logged: operator initials E.E. Β· role CPhT Β· sign-in timestamp. No full name, no employee SSN β€” initials only.

2 Β· Scan transaction # New step

The operator scans the barcode the pharmacy system already prints on the work order. This is a tracking code generated by the pharmacy β€” not the Rx number and not the patient. It is the hook that lets the pharmacy (and only the pharmacy) connect this machine record back to a fill.

Logged: transaction code TX-4471-0098. The code-to-patient mapping never leaves the pharmacy β€” see the Β§164.514(c) detail.

3 Β· Start the fill

From here the workflow is exactly what your team does today. Tap SCAN to read the drug barcode, or NDC to key it in manually.

4 Β· Scan the medication

The device reads the stock bottle and pulls the drug identity straight from the barcode β€” no typing, no transcription errors.

Logged: medication name Β· NDC Β· lot number Β· expiry Β· BUD Β· storage conditions.

5 Β· Select the flavor

The technician picks the flavor the customer requested. On the Fillmaster Auto the flavor bottles are onboard, so flavoring happens automatically during the pour.

Logged: flavor name Β· ingredient UPC Β· quantity Β· lot Β· expiry (one row per ingredient, up to four).

6 Β· Confirm & dispense

The operator reviews the calculated water volume and confirms. This is the deliberate "go" β€” captured as an explicit, attributable approval.

Logged: target water volume Β· operator confirmation timestamp.

7 Β· Dispensing

The Auto delivers the first half of the water with flavor, then the remainder as plain water. The device measures what actually came out β€” not just what was requested.

Logged: actual dispensed volume vs. target Β· start/end timestamps Β· device serial & firmware.

8 Β· Complete β€” and sealed

The moment the fill finishes, the device assembles the full machine-telemetry record and pushes it over an encrypted outbound connection to the LogBook cloud, where it becomes searchable and immutable.

Result: a complete, tamper-evident record β€” browse a finished example β†’
The two devices

One workflow, both Fillmaster models

LogBook runs the same record-keeping flow whether you reconstitute, flavor, or both.

πŸ’§

Fillmaster 4000

Primarily reconstitution. Fully automated water dispensing, integrated barcode scanning for 6,500+ NDCs, and flavoring instructions on the 5β€³ touchscreen.

πŸ§ͺ

Fillmaster Auto

Reconstitutes and flavors simultaneously from onboard bottles. 20,000+ NDCs, 2D barcode scanner, and State Board–compliant record-keeping.

πŸ”’

Same secure pipeline

Both push logs to LogBook over encrypted, outbound-only HTTPS/TLS. The device never accepts inbound connections β€” closing off edge-level intrusion.

For leadership

Why the two extra taps are worth it

🧾

Audit on demand

When a surveyor or board inspector asks "who, what, when," the answer is a saved search β€” not a fire drill.

πŸ“¦

Recall in seconds

A flagged ingredient lot becomes a filter. Identify every affected fill across every store instantly.

πŸ›‘οΈ

Zero-PHI by design

Accountability without liability. The record proves diligence while staying outside HIPAA jurisdiction β€” here's how.

Read the compliance FAQ β†’