Who is this person?
Persistent across encounters.
EPIOVIA is designed around tenant resolution, hospital context and a persistent patient record. The public product site describes the architecture without pretending that a roadmap item is already production capability.
The blueprint calls for one application with tenant-aware database resolution for SaaS, while the same application package can run as a dedicated installation with one hospital and one database. Environment configuration decides the connection and storage model.
The blueprint explicitly protects these distinctions because collapsing them creates clinical and financial ambiguity.
Persistent across encounters.
Exact clinical event.
Hospital/day sequence.
Own record with verification identity.
Separate financial fact.
A Hospital Administrator is not automatically allowed to do every action. A doctor can hold a position and separately receive the capabilities needed for prescribing. The blueprint separates organizational position, system role and capability so hospital hierarchies remain configurable.