Understand
The cohort, setting and continuity gap.
Start with one real workflow
Where does approved care break in everyday life?
Bring one defined cohort and continuity problem—after OPD, after discharge or across a managed-care programme. We’ll map the approved clinical authority, present workflow, evidence, human ownership and safety boundaries before discussing technology.
Begin without PHI
No patient-identifiable information is needed here.
Define the pathway
Cohort, condition, care setting, current process and failure point.
Make ownership explicit
Patient, caregiver, coordinator, doctor and service responsibilities.
What happens next
A focused first conversation.
The first conversation maps one care pathway and separates what is implemented, what requires configuration and what remains part of the designed roadmap.
Bound
Clinical authority, coverage and exclusions.
Assign
Patient, coordinator, doctor and service roles.
Measure
Learning questions and operating evidence.
Decide
Configure, revise, defer or stop.
Frequently asked
Before you contact us.
Should I include patient information?
No. Please describe the workflow and cohort without protected or patient-identifiable information.
Can I ask about services outside my city?
Yes. Availability, credentialing and coverage will be assessed for the intended geography before any commitment.
Is this an emergency or patient-support channel?
No. This form is for institutional and partnership conversations, not urgent clinical support.
Should we assume every capability in the ACIS vision is available?
No. Pilot design will identify the exact frozen, implemented, in-development and designed capabilities relevant to the proposed workflow.
What should we bring to the first discussion?
A target cohort, current workflow, approximate volume, clinical owner, operational owner, known failure points and the questions the pilot should answer.