Architecture overview
Shared records, interface patterns, execution and evaluation services behind HEPO's three offerings.
Architecture
Understand the shared systems, data boundaries and security responsibilities behind HEPO.
Browse by audience
Choose the documentation written for your role.
Find documentation
Search guides, references, and tutorials for the work you need to do.
Search by category
Documents in this category
The data model and its boundaries
Six database concerns, business identifiers, definition history and deployment-specific isolation.
The security model
Identity, roles, permissions, validation and audit as responsibilities to verify in a HEPO deployment.
Data, kept apart by purpose
Working records, definitions, audit, readings and platform data have distinct responsibilities.