Intake Technology Research
Studying Check-In Kiosk Recovery Time at Dispensary Intake
A study protocol for measuring how long a dispensary takes to recover patient intake after a self-service check-in kiosk freezes, with separate intervals for detection, fallback, device recovery, and record reconciliation.
Key takeaways
- Define recovery from the first frozen screen to a completed paper-to-system reconciliation, not from the device restart.
- Measure the fallback start, the queue impact, the device recovery, and the record reconciliation separately.
- Report the share of patients handled on paper beside the recovery time so a fast restart is not mistaken for a clean outcome.
- Keep the vendor ticket and the device log with the local observation so the cause can be reviewed later.
Question and scope
This study asks how long a dispensary takes to restore patient intake after a self-service check-in kiosk freezes. The unit is one kiosk failure tied to one store, one device, and one intake period. The review separates the detection, the paper fallback, the device recovery, and the reconciliation of paper entries. It does not judge whether the kiosk vendor's software is reliable.
Set the scope to one store and a fixed observation window. Record the kiosk model, the software version, the network type, and the staffing level at the time of the failure. If the store changes devices or vendors during the window, separate the periods. A hardware change can create a failure pattern that looks like a staff problem.
Include failures that were resolved by a restart, failures that required a vendor ticket, and failures that ended with the kiosk offline for the rest of the day. A study that looks only at quick restarts will understate the recovery time. Record the disposition for every failure, including the ones that never returned to service. The disposition mix is part of the result.
What the sources establish
The Virginia Cannabis Control Authority sets the licensed retail and patient-intake context in which the kiosk operates. The HHS Office for Civil Rights publishes health-information privacy guidance that is relevant to paper forms and device handling. The NIST Cybersecurity Framework offers a general model for logging and reviewing device events. These sources frame the operating conditions, not a required recovery time.
The sources do not establish a maximum kiosk outage or a required paper fallback. They also do not say whether a store must keep a second device. The study therefore measures the store's own continuity plan and the vendor's service record against what actually happened. The report should keep that local scope visible.
The sources support separating a technology delay from a record delay. A kiosk that restarts in four minutes has created a short technology outage, while a paper log that is not reconciled until the next day has created a longer record problem. The study should report both. The fix for one is a device process, and the fix for the other is a reconciliation owner.
Definitions and measures
Define detection as the time a staff member or patient notices the frozen screen. Define fallback as the time the first patient is moved to the paper process. Define recovery as the time the kiosk accepts a test check-in again. Define reconciliation as the time every paper entry is matched to the patient record.
Measure detection, fallback, recovery, and reconciliation separately. Report the total intake-recovery time as the interval from detection to reconciliation, but keep the components visible. A fast fallback followed by a slow reconciliation is a different problem from a slow fallback followed by a fast restart. The components point to different fixes.
Record the number of patients in the lobby at detection and the number handled on paper. Note whether any patient left without checking in. Report the queue wait beside the recovery time. A kiosk that recovers quickly but leaves a long line has not fully recovered the intake period.
Sampling and collection
Sample kiosk failures from the device log, the vendor ticket system, and the front-desk incident notes. Match each failure to an intake period and note any that cannot be matched. Record the device identifier, the software version, and the error message. The match is the foundation of a defensible recovery-time measure.
Collect the paper intake forms and the arrival log for the same period. If the store cannot produce the paper record, record that gap as a finding. A kiosk failure that cannot be reconstructed is a record problem in addition to a technology problem. The study should not infer the queue from the appointment schedule alone.
Observe at least one failure at the counter. Record the time the screen froze, the first fallback action, and the first patient served on paper. The observation shows whether the written continuity plan matches the actual practice. A plan that looks clear on paper may be improvised under pressure.
Verification pathway
Confirm the kiosk recovery with a test check-in, not only with a green status light. Record the test time and the staff member who ran it. The study should distinguish a device that powers on from a device that completes the intake flow. A test with a staff account is safer than a test with a patient record.
Check the paper entries against the patient records and the appointment schedule. Record any duplicate profile, missing arrival time, or unmatched appointment. The reconciliation is complete only when every paper entry has a system destination. A count that matches the number of forms is not enough if the entries are attached to the wrong records.
Review the vendor ticket and the device log for the same failure. Confirm that the ticket time and the observed time agree. Do not record patient details in the study file beyond what the store already keeps. The kiosk recovery routine describes the counter-level sequence that should feed this record.
Operational side effects
Check whether the failure pulled a staff member away from the counter during a busy block. Record the minutes spent on the device and who covered the intake work. A kiosk failure is not free even when the queue is short. The study should show the labor cost beside the recovery time.
Review the patients who were handled on paper and the time their entries took to reconcile. A paper entry that sits unattended for a day is a record risk even when the patient was served promptly. Record the reconciliation time separately from the service time. The study should not treat the patient's departure as the end of the event.
Check whether the failure affected the privacy of the intake area. A paper form left on the counter or a screen visible to the lobby is a privacy problem, not only a technology problem. Record the observation and the correction. The study should connect the device to the surrounding intake controls.
Analysis and reporting
Report the number of failures, the median time to fallback, the median time to recovery, and the slowest reconciliation. Break the results down by device, software version, and time of day. Report the paper volume beside the recovery time. A single average hides the difference between a quick restart and a slow record cleanup.
Inspect the failures for patterns. A cluster of morning failures may point to an overnight update, while a cluster of afternoon failures may point to heat or network load. Choose one change, such as a pre-shift test or a printed fallback kit. Do not rank staff by recovery time when their device access differs.
Report the failures that were still open at the review date separately. An open failure is not a zero-minute recovery, and treating it as one understates the backlog. Show the age of each open ticket and the owner. The report should make the unresolved devices visible.
Keep the results in one page that the front-desk lead reviews monthly. Show the failure count, the fallback time, the recovery time, the reconciliation time, and the open backlog. The page should be short enough to discuss in a ten-minute meeting. A long report with no decision is not a useful study.
Limits and next action
The study cannot prove that a second kiosk would eliminate the queue or that every failure was recorded. It also cannot capture a patient who gave up before reaching the counter. A missing patient is a limitation, not a zero. The report should state how many patients were excluded and why.
Set a repeat review date and keep the definitions stable. Assign the correction to the front-desk lead and give the counter a clear paper fallback. The next review should test whether the same device or the same shift fails again. A useful result is a check-in process that the store can explain and complete without a second visit.
Record the date the store last tested the full check-in flow with the people who actually work the counter. A test that works for the manager may fail for the weekend crew. Add the test to the monthly device review. The next study should use the current kiosk and the current continuity plan.
Sources
The sources below support the retail, privacy, and device-review context for this review. They do not measure this store, and no source is presented as a local benchmark. Check each link for its date and scope before reuse. The operational finding comes only from the kiosk records described in the method.
This article describes a measurement method rather than legal or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation.
Reviewed by the DispensaryVA editorial team on 2026-11-17.