Scenarios
Step-by-step examples of payer workflows, message triage, intake programs, and compliance exports—each one shows Assistant, Studio, Public API, and Agent SDK sharing the same PHI handling, metering, and audit chain. Plan limits stay aligned with what's published at checkout; your contracts and policies still decide what ships in production.
Scenario 01 · Clinical ops
A specialty practice merges Studio checklists, Assistant Q&A against policy text, and the Data API so each payer packet inherits the same PHI handling and hash-chained evidence as everything else inside HASP.
Read narrative →Scenario 02 · Access center
Care coordination teams orchestrate outbound Agent SDK drafts for portal messages while supervisors approve them in Studio queues—every Agent Action traces to both the automation and the human who released it.
Read narrative →Scenario 03 · Population health
Occupational-health programs iterate intake questionnaires in Studio, keep Assistant-aligned PHI controls for kiosk and lobby Q&A, and meter kiosk bursts separately from inference through App Operations when volume spikes.
Read narrative →Scenario 04 · Compliance
Governance leads schedule nightly pulls through the authenticated Public API, land signed exports in their own archival storage, and give examiners JSON plus the published /trust/verify recipe—not dashboard screenshots.
Read narrative →