Pilot partnerships / Start with one interaction
Explore an OPASS pilot.
We’re seeking organizations to explore a focused pilot: one service, an accountable team, and a clearer path from a person’s first action to what happens next.
Tell us about your use caseChoose a workflow together.
Map an interaction your team already handles, such as an outreach request or a service queue. Define the participants, response owner, and evidence needed for completion.
Agree a practical pilot.
Scope the entry point, temporary pass, participant guidance, team response view, training, and support. Confirm readiness and required controls before real use.
Measure whether it helps.
Compare response times, unresolved requests, staff coordination effort, and participant feedback with your current process. Use the findings to decide whether to continue.
Before we begin
A few practical questions.
Is OPASS ready for immediate deployment?
OPASS is in development. Discovery can help define a suitable pilot, but delivery dates and activation depend on implementation, testing, and the controls needed for your workflow.
Would we need to replace our existing systems?
The proposed approach starts with a defined interaction. Your clinical, case-management, scheduling, or agency systems retain their authoritative records and decisions. Any integration would be scoped separately.
What does our organization contribute?
Your organization defines the service rules, assigns an operational owner and responding staff, agrees its information policy, and helps evaluate the participant experience. Configuration, training, support, and responsibilities are defined in the pilot scope.
How would we decide whether to continue?
Agree success criteria and a baseline before live use. Review participant feedback, response performance, staff effort, reliability, and total costs together before deciding whether to continue, revise, or close the pilot.
Contact OPASS / Pilot partnerships
Tell us about your use case.
Share your organization, the workflow you want to improve, and who handles it today. We’ll use your details to respond about a potential pilot.
All fields are required. Please describe the workflow without including personal information about individual patients, residents, or service users.
Prefer email? c2@tennesseesprovider.com
OPASS is being developed by Tennessee’s Provider.