01 / The participant action
What was submitted?
A recorded request captures the participant’s action. Opening a QR code or submitting a form does not independently prove physical presence, eligibility, or delivery of a service.
How it works / Digital Orientation
Different environments.
One connected experience.
Explore outreach, public services, workplaces, education, healthcare, and community living. Follow the participant’s action, the team’s response, and the next step to see how each environment configures the same OPASS core.
01 / Explore the interaction
See OPASS in
different environments.
Choose a setting and follow both sides of the interaction, from a participant’s first action to the team’s response and next step.
Illustrative concept
Participant view
◈ OPASSTemporary pass
Request received
Your request is with the team.
Your food package request has been recorded. The outreach team still needs to respond.
ContextCommunity outreach
Example passOP-1042
Organization view
Food package request
Illustrative organization inboxCurrent interaction
A food package has been requested. A team response is still needed.
Recorded activity
Request submittedParticipant-submitted request
What this establishes: The request is recorded. Availability and assistance are still unconfirmed.
Concept screens show proposed behavior using fictional examples. OPASS is in development; capabilities depend on implementation, the configured workflow, and deployment validation. This demonstration sends no requests.
What the record actually means
Each stage answers
a different question.
02 / The organization response
What did the team acknowledge?
An acknowledgment, pickup instruction, or counter call is its own event. It tells the participant what has changed and what to do next, while preserving what remains unresolved.
03 / The confirmation
What supports completion?
The organization defines the claim and required evidence. A staff attestation or external confirmation supports only the claim it actually establishes. Missing confirmation stays visible.
The temporary pass connects the interaction’s context, actions, and next instructions. Its validity and the service request’s status are separate: expiry of the credential does not erase an outstanding request.
One core / Configured for your environment
Your service.
Your response rules.
A configured orientation profile defines what people need to know, what they can do, and how your team responds. The five orientation dimensions guide that configuration.
- Who and where: the role, organization, access point, and only the participant information the interaction needs.
- When and what: the relevant service window, pass validity, purpose, and available action.
- What comes next: a response, instruction, pending condition, handoff, or closure.
Contact OPASS / Pilot partnerships
Let’s explore your first use case.
Tell us your organization, the service you want to improve, and who handles the response today.
OPASS is being developed by Tennessee’s Provider.
Email about a pilot Opens your email app · you review and sendc2@tennesseesprovider.com