In development · Built around people
Digital Orientation Infrastructure
OPASS is being developed as a configurable way to help people understand where they are, what they can do, and what comes next.
The right context. The relevant action. A clear next step.
01 / The orientation layer
A clear next step for every interaction.
OPASS connects everyday interactions with the organization, information, and response needed to move them forward. A person may arrive to request help, join a queue, attend a class, volunteer, complete a shared responsibility, or connect with a service.
OPASS brings the relevant context and action into that moment. A temporary digital pass helps maintain continuity as the interaction progresses.
01 / WHO
Who am I?
The role or participant reference relevant to this interaction.
02 / WHERE
Where am I?
The organization, access point, or location for this moment.
03 / WHEN
When is it?
The service window, event time, deadline, and pass validity.
04 / WHAT
What is this?
The purpose, relevant instructions, and available action.
05 / NEXT
What’s next?
The next action, organizational response, destination, or closure.
These are system responsibilities, not five mandatory form questions. Your organization configures the experience so people receive relevant guidance and provide only the information needed for that purpose.
02 / From entry to next step
How OPASS works.
Many ways in. One context model.
QR code
NFC
Digital link
Kiosk
Staff assistance
In action / Both sides of the experience
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.
Your request is with the team.
Your food package request has been recorded. The outreach team still needs to respond.
Food package request
Illustrative organization inboxA food package has been requested. A team response is still needed.
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.
Explore the workflow and evidence behind each step03 / OPASS 360°
Configured for your environment.
A business, church, household, community, nonprofit, or public agency can configure the same core around its own people, services, and responsibilities. Choose your environment to go straight to a relevant example.
Businesses & workplaces
Guide visitor arrivals, staff participation, training activities, customer requests, and service follow-up.
View exampleChurches & ministries
Connect outreach requests with team responses, pickup arrangements, and a confirmed next step.
View exampleNonprofits & communities
Organize volunteer assignments, service projects, assistance requests, and program participation with visible follow-up.
View exampleGovernment agencies
Replace a paper queue ticket with a temporary digital pass, queue instructions, a counter call, and a clear next step.
View exampleHomes & community living
Coordinate shared tasks, activities, support requests, and agreed responsibilities with guidance appropriate to the home or program.
View exampleEducation & training
Connect session check-ins with facilitator responses, activity instructions, and confirmation of defined participation.
View exampleHealthcare & services
Guide encounter check-ins, clinic responses, next instructions, and staff-confirmed attendance, with protection appropriate to the interaction.
View example04 / An organizational foundation
Build your organizational infrastructure.
OPASS gives an organization a common structure for its programs, services, locations, access points, and response routes. Teams can start with one interaction and expand across departments, sites, or community partners as their needs develop.
That structure can also support an organization’s own operational measures and indices. Authorized records can help teams understand response times, unresolved requests, participation patterns, and confirmed handoffs. Each measure needs a clear definition and appropriate evidence so the organization understands what its results describe.
YOUR ORGANIZATION
01 / CONFIGURE
Programs, services & locations
02 / CONNECT
Access points & response routes
03 / UNDERSTAND
Events, evidence & authorized measures
Private by default. Defined by purpose.
05 / Purpose-led trust
Verification and protection, matched to purpose.
Verification that matches the purpose.
Different interactions need different kinds of confirmation. Opening a pass, submitting a request, receiving an acknowledgment, and completing a service are separate moments. OPASS is designed to preserve those distinctions and apply the evidence checks chosen for the interaction.
A food request can remain open until the organization records the next action. A queue entry can progress to a counter call. A completed service can carry its own confirmation. People and teams can see what has been recorded and what still needs attention.
A submitted request is not a completed service.
Protection when sensitive information is needed.
Some interactions require additional protection, such as a clinic check-in that needs a name and date of birth. OPASS is designed to collect only necessary information, direct it to authorized recipients, and apply stronger security controls when sensitive details are involved. A pass can reference the interaction without displaying the underlying personal information.
Cryptographic exchange records can help establish what was sent and what the receiving system acknowledged. Optional independent timestamp proofs can support later checks that a selected record version existed by an anchoring point. The organization’s evidence requirements determine what confirms the underlying activity.
06 / Technical overview
A common core. Clear system boundaries.
A versioned orientation profile connects the access point, temporary pass, interaction, and organizational response. These are logical architecture layers: an initial deployment can use one application, background workers, and managed storage.
Access & orientation
Temporary pass
Interaction & communication
Evidence & verification
Protected exchange
Audit & timestamp proofs
Organization measurement
Integration & operations
Independent proofs, not payments or participant wallets.
PROPOSED ARCHITECTURE
Capabilities described here require implementation and deployment validation. Organization isolation, recovery, retention, key management, and evidence checks must be tested before activation.
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.