Pilot purpose
The MediFlow pilot gives selected clinical teams early access so they can validate patient workflows, scheduling, document management, vitals, AI-assisted operations, and organization administration in a controlled environment.
- Pilot terms
Pilot terms for early MediFlow teams.
MediFlow pilots are intended for selected clinicians and organizations to evaluate the product, validate workflows, and provide feedback before broader availability.
Pilot participation is controlled by scope, usage limits, data rules, privacy expectations, feedback loops, and written agreement. These terms are product guidance, not a final legal contract.
Product guidance only. Roadmap and pilot details depend on shipped evidence, commercial scope, and legal review.
What is included
- Organization setup, authentication, email verification, and active organization context.
- Role-based user management, patient directory, patient registration, and patient detail.
- Documents upload/view/download where enabled, vitals entry and charting, scheduling foundation, dashboard, and daily workflow.
- AI operations copilot where enabled, read-only behavior testing where applicable, and compliance feedback.
Data and PHI rules
Pilot work should use synthetic or non-production data unless production PHI is expressly permitted in writing. Production PHI use requires appropriate legal agreements, provider configuration, access controls, retention policy, and compliance review.
Excluded unless agreed
- Production PHI use, emergency or mission-critical workflows, sole system of record usage, diagnosis automation, or autonomous treatment recommendations.
- Live web search with PHI, EHR/FHIR/HL7 integration, patient portal, telemedicine, e-prescribing, or enterprise-only controls unless specifically included in the pilot.
Pilot end
At the end of the pilot, the organization may continue under a written launch agreement, extend by written agreement, export permitted data, or request deletion according to the agreed retention policy.