MediFlowresources
- Roadmap

Roadmap for a calmer clinical operations platform.

Follow MediFlow's current pilot-readiness path across patient records, documents, vitals, scheduling, dashboard facts, AI assistance, admin tools, verification, and launch decisions.

MediFlow has an alpha clinical workspace foundation and is now being tightened toward a small-clinic pilot: organization setup, team management, operational dashboard facts, governed AI assistance, feedback, release notes, and verification.

Join pilotRead pilot terms

Product guidance only. Roadmap and pilot details depend on shipped evidence, commercial scope, and legal review.

Now

Alpha foundation clinicians can evaluate

alpha foundation

The product has enough clinical workspace spine to evaluate real flows while the team closes pilot gaps.

Evidence posture

Current MediFlow main branch contains the core workspace foundations, but pilot acceptance and deployment evidence still matter.

  • Authentication, session restore, active organization context, route protection, and pilot role gates.
  • Patient records, appointments, documents, quick notes, medical history, vitals, dashboard foundations, and profile completeness indicators.
  • Audit event path, server-side workflow controls, feature flags, and a manual operations copilot boundary.
Next

Pilot gaps being closed

pilot readiness

The next layer is not a feature grab. It is the work needed for a small clinic to complete one daily workflow without developer help.

Evidence posture

Tracked in the pilot scope, current-state audit, and open MF issues for integration, AI behavior, release notes, and verification.

  • Organization creation or join, real team management, and pilot-safe onboarding.
  • Dashboard source facts for tomorrow workload, missing documents, incomplete profiles, pending work, and drilldowns.
  • AI quota, cache, PHI-safe audit events, copy/export, disabled/quota/provider-error states, in-app feedback, release notes, and known limitations.
  • Focused unit, integration, E2E, and manual verification for happy paths plus empty/error/unauthorized states.
Later

Beyond pilot readiness

under review

Broader platform and production claims stay future-facing until the controls, contracts, and evidence exist.

Evidence posture

These items require product, legal, security, commercial, and jurisdiction review before public availability claims.

  • Commercial launch terms, payment operations, and subscription infrastructure.
  • Compliance evidence portal, DPA/BAA/DPIA and vendor evidence, data-subject workflows, enterprise identity, network controls, and external audit integrations.
  • Patient portal, native mobile apps, EHR integrations, telemedicine, e-prescribing where allowed, full i18n/PWA scope, and clinical AI after separate review.
Principles

Rules for what gets built

operating principle

MediFlow should earn trust by showing how decisions are made, not by promising a crowded feature list.

Evidence posture

Product rules that guide sequencing, public claims, and pilot tradeoffs.

  • Clinical workflow first.
  • Governance before automation.
  • AI as controlled assistance.
  • Evidence over promises.
  • Pilot feedback matters.
Resources

Keep reading.

How to use MediFlowHow to use MediFlow.ChangelogChangelog coming soon.RoadmapRoadmap for a calmer clinical operations platform.Pilot termsPilot terms for early MediFlow teams.About KesharonAbout Kesharon.PrivacyPrivacy posture for MediFlow.