A governed path from population signal to accountable action.
MbeleMed connects the steps that are often fragmented across risk selection, outreach, monitoring, physician interpretation, follow-up, and program evidence.
Each stage has a clear purpose, owner, and evidence requirement.
Prioritize
Apply approved risk criteria and available population information to define who may benefit from monitoring.
Reach
Coordinate outreach and deployment through home, clinic, community, or mobile settings defined with the partner.
Monitor
Support device-agnostic monitoring workflows without presenting MbeleMed as the diagnostic device manufacturer.
Physician review
Route potential findings through qualified interpretation before any clinical action proceeds.
Act
Support documented outreach, escalation, and follow-up under partner-defined clinical governance.
Measure
Capture workflow completion, confirmed findings, follow-up, and agreed program outcomes for review.
Coordination is not the same as clinical authority.
A credible deployment separates operational coordination, device and interpretation services, clinical decisions, and joint program measurement.
| Function | Primary role | Boundary |
|---|---|---|
| Population criteria and cohort definition | Partner, supported by MbeleMed workflow design | Criteria must be approved for the applicable program and population. |
| Outreach and deployment coordination | MbeleMed and partner operations | Operational contact does not constitute diagnosis or treatment. |
| Monitoring device and diagnostic service | Applicable monitoring partner | MbeleMed does not manufacture the diagnostic device. |
| Professional interpretation | Qualified physician | Clinical interpretation remains attributable to the qualified reviewer. |
| Escalation and treatment decisions | Partner care team and applicable clinicians | MbeleMed does not prescribe or autonomously direct treatment. |
| Program evidence and review | Joint partner and MbeleMed review | Modeled economics and pilot results remain separately labeled. |
The same operating layer can support different access pathways.
- HomeMonitoring coordinated around the person rather than a specialist visit.
- ClinicScreening integrated into an existing clinical or population-health pathway.
- CommunityDeployment through trusted access points closer to underserved populations.
- MobileOperational workflows that move across geographies or partner sites.
A first pilot should answer a defined set of questions.
- 1
Who is eligible?
Define the population, geography, clinical criteria, exclusions, and source of the initial population signal.
- 2
How will people be reached?
Specify outreach, consent, deployment setting, monitoring logistics, and responsibility for unresolved contact attempts.
- 3
Who holds clinical authority?
Name the qualified interpreting physician, escalation pathway, follow-up owner, and emergency boundary.
- 4
What will count as evidence?
Agree on operational completion, confirmed findings, follow-up measures, limitations, and economic assumptions before launch.
Start with the pathway, not the device.
A credible first pilot begins by defining the population, governance, and evidence the program must produce.