Three zones that should not be silently merged
- PVS/KIS/OEM: healthcare application, business purpose, user experience and organization-specific workflow.
- MEMM scope: agreed product, runtime, API and release boundaries.
- External operators/governance: infrastructure, providers, identity/trust services and externally assigned responsibilities.
Why the discussion belongs before the demo
A bounded scope exposes assumptions about deployment, updates, failure handling, external dependencies and later acceptance evidence before they become hidden project risk.
What this page explicitly does not claim: This is not a universal RACI. Actual responsibility depends on contract, deployment, regulatory role, target environment and release and must be agreed per project.