Hospital type
Multi-site Corporate Chain
One brand, many sites, one governed platform.
The problem
Two to fifty sites on different HIS versions, no group-level view, and a patient who cannot be recognised across sites.
The platform
How Pensieve serves this
- org→site modelA native multi-tenant model: an organisation contains many sites; data and permissions are scoped to a site.
- FalconCross-site metrics roll up; leadership sees group-wide, site heads keep day-to-day control.
- CorneaRehearses a new site's configuration before it goes live.
- orophinEach site's existing machines are bridged.
What changes
- Site-scoped data on one platform, one tenant across every site.
- A live group view.
- A new site rehearsed before go-live.
Questions we get
- How does this affect our security posture?
- Authorization is checked on every read and every write, with a patient lens at the database read path. Every action is audited in the same transaction as the change. The orophin bridge opens one outbound mTLS connection, with no inbound firewall holes.
- Are we locked in?
- Export speaks HL7 v2, FHIR R4, and DICOM, so the data stays portable. An automated check fails the build when a tool tries to bypass a core system, which keeps the platform governed rather than proprietary.