Platform overview

OpenHI is built so many products can share the same foundations: identity and tenancy, a unified API, and durable resource contracts.

One API, many product lenses

Domains like content, relationships, clinical operations, and back-office operations are ways of thinking about use cases. They are not separate backends you wire differently for each product.

Front ends and partner apps compose the surfaces they need. The platform stays one HTTP API with shared authentication and tenancy rules.

Control plane vs data plane

OpenHI separates two kinds of resources:

• Control plane: who can use the system (users, tenants, workspaces, memberships, platform roles).
• Data plane: the operational and domain records applications create and query day to day.

Authorization spans both. Your session tells the API which tenant and workspace you are acting in. Data you touch is interpreted in that scope.

Why this matters for builders

• You integrate against one set of conventions instead of stitching siloed services.
• Apps can specialize in UX while sharing infrastructure.
• OpenHI ontology and terminology publish here as they stabilize. OURS is the framework we use to author those models.

Next: Tenancy & workspaces and Standards & models.