# Using the openEHR Base IG as a Structural Reference for Modelling gitEHR

**Category:** [gitehr](https://openhealthhub.org/c/gitehr/57)
**Created:** 2025-12-03 11:27 UTC
**Views:** 15
**Replies:** 0
**URL:** https://openhealthhub.org/t/using-the-openehr-base-ig-as-a-structural-reference-for-modelling-gitehr/2900

---

## Post #1 by @FibrinLab

While reading through the **openEHR Base Implementation Guide artifacts page**([https://build.fhir.org/ig/FHIR/openehr-base-ig/artifacts.html](https://build.fhir.org/ig/FHIR/openehr-base-ig/artifacts.html?utm_source=chatgpt.com)) shared by Marcus, I wondered whether this could serve as a useful foundation for discussion.

The artifacts summary provides logical representations of core openEHR concepts (`EHR`, `Composition`, `Entry`, `Observation`, `Action`, etc.) expressed in a FHIR-compatible form. For a project like gitEHR, which treats the medical record as a semantically rich, auditable history of clinical events, this seems like a useful reference point.

However, these logical models are low-level reference constructs and not full clinical artefacts. Implementations still require archetypes of FHIR profiles.

1. Is this a reasonable start point? 
2. How do you think we can navigate the boundary btw reference model structure and clinical context definition?

---


**Canonical:** https://openhealthhub.org/t/using-the-openehr-base-ig-as-a-structural-reference-for-modelling-gitehr/2900
**Original content:** https://openhealthhub.org/t/using-the-openehr-base-ig-as-a-structural-reference-for-modelling-gitehr/2900