Standards & models
OpenHI’s product story is shared foundations: standards, APIs, and infrastructure that many applications can reuse.
OpenHI ontology lives here
Section titled “OpenHI ontology lives here”We will publish OpenHI-specific ontology and terminology on this documentation site: models, vocabularies, code systems, and related artifacts as they are ready for builders.
That content is still being drafted. When packages ship, they will show up under Standards & models and related API docs.
OURS is the authoring framework
Section titled “OURS is the authoring framework”OURS is a framework for writing ontology. It is not OpenHI’s published terminology by itself. We use OURS (and point builders there) when the topic is how to author and maintain ontology in general.
Resource-oriented APIs
Section titled “Resource-oriented APIs”OpenHI APIs are resource-oriented and built for interop. Healthcare standards practice informs a lot of the shapes we use, including patterns familiar from FHIR-style REST. This site is not a FHIR Implementation Guide, and we do not lead with resource laundry lists.
For OpenHI vocabulary and terminology, watch this site. For the general framework used to write ontology, see OURS.
Domain extensions
Section titled “Domain extensions”Not every product surface is a classic clinical record. OpenHI also models CRM, CMS, ERP-style, and control-plane concerns with consistent resource habits (identity, metadata, JSON over HTTPS, scoped tenancy). Shared OpenHI models keep those extensions coherent instead of inventing one-off dictionaries per app.
Next: API conventions.