EHRBase + Dental Templates: Structured Electronic Records for Dentistry
Context
EHRBase by itself is a solid openEHR engine. It handles structured medical records, stores them safely, and provides APIs. But on its own, it is a blank platform—powerful but without domain-specific content. The missing piece for dentistry comes from Dental Templates. These template sets carry clinical archetypes for dental exams, treatments, and imaging references. Alone, they are only models. When loaded into EHRBase, the system becomes a functional dental record solution. Administrators usually combine them: EHRBase provides the standards and security, while Dental Templates bring actual dental workflows.
Technical Snapshot (table)
| Area | EHRBase | Dental Templates | When combined |
| Role | Clinical data platform | Archetypes for dental care | Standards-based dental EHR |
| Platform | Java app + PostgreSQL | JSON/XML templates | Works together on same stack |
| Content | Generic openEHR archetypes | Dental-specific models | Unified schema for dental data |
| Interfaces | REST, FHIR bridges | Template validation | Structured exchange with dental focus |
| Security | TLS, RBAC, audit trails | N/A (content layer) | Secure records with domain logic |
| Scale | Enterprise-ready | Lightweight content | Adaptable from lab to hospital use |
| License | Open-source (AGPL) | Community open-source | Free to adopt and extend |
Scenarios
Teaching clinic. Faculty deploys EHRBase and loads dental templates, allowing students to log cases in a structured way.
Hospital record unification. A hospital adds dental templates to its existing EHRBase so dental and medical histories live together.
Research registry. A regional project collects oral health metrics using templates to keep datasets consistent across sites.
Workflow (admin view)
Provision a server with Java and PostgreSQL.
Deploy EHRBase and confirm APIs are functional.
Import dental templates (archetypes for exams, treatments, imaging).
Configure user groups and RBAC policies.
Enable TLS and set up regular backups for DB and templates.
Connect with external PACS through metadata references.
Monitor DB health, template use, and audit logs.
Strengths / Weak Points
Strengths
EHRBase enforces openEHR compliance and interoperability.
Dental Templates add immediate domain-specific workflows.
Supports FHIR and HL7 integration with PACS or analytics.
Scales from pilot lab setups to full hospital systems.
Weak Points
Setup requires experience with openEHR internals.
Template quality varies by source and maintenance.
More complex than standalone dental practice apps.
Why They’re Stronger Together
Running EHRBase without templates is like having a database with no schema: all mechanics, no context. Dental Templates alone are static models without a runtime. Combined, they deliver both the backbone and the content—structured, shareable records that fit dental practice. This pairing lets IT teams provide a standards-based system that is practical for clinics, universities, and research projects.
