Scenarios · Workforce health
Patient intake and workforce screening, with one policy stack across every kiosk.
Multi-site employers running onsite clinics keep one source of truth for screening forms, kiosk UI, and the policy text behind them. Employees fill the form, nurses answer follow-up questions in the same workflow, and every site reflects today's rules — not a PDF from last season.
Where the work happens
- Studio — the live screening form and the kiosk UI rendered from it.
- Assistant — nurse-led chat for "Should I see a doctor?" questions, grounded in the same policy text.
- Public API — optional ingestion from badge systems or temperature kiosks.
How it works
-
A coordinator updates the form once.
Every plant kiosk renders from the same live definition — no emailed PDFs, no out-of-sync copies across sites. EHS pushes a change; the next employee sees it.
-
Employees and patients answer at the kiosk.
You decide how PHI flows: send it under your BAA when the clinical step needs identifiers, or have HASP detect and mask the 18 HIPAA Safe Harbor identifiers before anything leaves your environment. The choice and scan result land on the audit chain tied to that session.
-
A nurse handles the "Should I…?" questions live.
"Should I see a doctor today?" or "Is this symptom urgent?" opens a chat grounded in the same OSHA recordkeeping rules and internal clinical protocols as the kiosk form. Each exchange is signed and appended to the same audit chain as the intake event.
-
Finance sees kiosk traffic separate from model calls.
Burst submissions during a flu-season check are metered on their own axis, so they don't get blended with AI query spend. Occupational health budget reports stay legible.
Try this as a Studio template.
Why this survives governance
-
Workforce health lives at the intersection of HIPAA, ADA, and OSHA.
A kiosk system that sends raw responses to a general-purpose AI — even with good intent — collides with HIPAA's minimum-necessary rule, the ADA's medical-inquiry restrictions, and OSHA recordkeeping under 29 CFR 1904. Scoping the data to the clinical decision at hand, on a per-step basis, is what keeps the program defensible.
-
Recordkeeping rules increasingly demand the process, not just the answer.
State occupational health reporting mandates and OSHA's electronic recordkeeping requirements expect documentation of how the data was collected. Which version of the form was live for which employee; which policy was current when a nurse answered. Paper logs and spreadsheets cannot reproduce that.
-
Process integrity beats a clean log when an employee complains.
Programs that can replay the screening session — form version, policy version, who answered the follow-up — respond to regulatory review and employee complaints from documented fact instead of recollection.
Deploy this workflow in your environment.