Moving to a hybrid model is a change in how we deploy and secure software. To keep the infrastructure “Lean,” we must move toward Containerized Gateways and Managed Identity.
1. Scaling the Gateway with Containers#
Instead of installing your application directly onto a VPS, we use Containers (Docker/Podman).
- The “Cloud Gateway” (the frontend doctors and patients see) should be a lightweight container.
Why?
If traffic increases e.g., during a sudden telemedicine surge, you can spin up three more containers in seconds. Because the container is “stateless” (the data is safely in local facility), scaling the frontend doesn’t risk database integrity.
- Using a simple orchestrator (like a lightweight Kubernetes or Docker Compose) allows you to update the frontend with zero downtime.
2. Outsourcing the “Front Door” Security (IAM)#
Building a secure login system from scratch is expensive and risky. Instead, we use “Ready-Made” Identity Providers (IdP) like Google Workspace or Microsoft Entra.
Pro
Cloud Gateway doesn’t store passwords. It simply asks Google or Microsoft: “Is this person who they say they are?”
If Organizations already pay for these services. By leveraging them, you get Multi-Factor Authentication (MFA) and Great security without adding cost.
3. Fine-Tuning the “Local” Permissions#
While Google/Microsoft handles the Authentication, local facility server handles the Authorization.
Role-Based Access Control (RBAC)
Inside your facility, you define roles (e.g., Physician, Nurse, Admin).
Hierarchy-Based Control
The administrator can fine-tune permissions based on your specific organization. For example, a “Nurse” role might have “Read” access to all records, but “Edit” access only for patients currently checked into their ward.
When the Cloud Gateway verifies a user via Google, it passes a secure “token” to your local server. Your local server then checks its own internal database to see what that specific person is allowed to do.
4. Stays Lean#
No “Pet” Servers
If a container breaks, you delete it and start a new one. No manual troubleshooting is required, or even automated this via kubernetes.
Reduced Management Tax
By no need to manage a password database. The focus is now on the local permission logic and the FHIR data structure, while “Identity” has been outsource on the more reliable providers.
A lean infrastructure is only as good as the people who operate it. Because we have shifted to a “Human-in-the-Loop” model for data reconciliation, staff training is targeted at two specific areas:
The Reconciliation Workflow
Clinical leads must be trained on how to use the Conflict Archive. They need to understand that their role is the “Final Validator” when the system detects multi-site sync errors.
Staff should know that after Internet down, they run on the Local Failsafe DNS, their workflow remains the same during an internet drop, but they should be aware of the “Offline” status indicator in the EMR.
| Feature | Traditional On-Premise | Lean Hybrid (Container + IdP) |
|---|---|---|
| Frontend Scaling | Buying/Configuring new VMs | Spinning up new Containers |
| Password Security | Hosted on your server (Risky) | Managed by Google/Microsoft (Secure) |
| Permission Logic | Hard-coded in the App | Flexible RBAC/Hierarchy on-site |
| Maintenance | Manual Updates | Automated Container Rebuilds |