GNUmed + Dental Forms: Electronic Health Records for Dentistry
Context
GNUmed has been around for years as an open-source EHR, mainly serving general medicine. It’s steady, reliable, but it was never built with dentists in mind. That’s where the Dental Forms project comes in. On their own, the forms look like a set of templates — odontograms, treatment notes, billing sheets. Not much more. But when plugged into GNUmed, something changes: dental workflows suddenly sit next to lab results, prescriptions, and patient histories.
This pairing matters because many dental tools run in isolation, while GNUmed gives them a clinical backbone. Instead of maintaining two record systems, schools and clinics can run both domains inside one. It’s not as shiny as commercial software, but the mix of completeness and low cost makes it attractive for teaching hospitals and outreach programs.
Technical Snapshot
| Area | GNUmed Core | Dental Forms Add-on |
| Platform | Cross-platform (Linux, Windows, macOS); PostgreSQL backend | Integrated into GNUmed client |
| Focus | General practice EHR: labs, meds, history | Dental charting, odontograms, notes |
| Content | Full medical records, documents, imaging links | Tooth-level charts, procedures, billing |
| Features | HL7/FHIR support, role-based security, plugins | Odontogram graphics, customizable forms |
| Licensing | GPL, open-source | GPL, open-source |
| Scale | Small to mid-size clinics, academic use | Teaching labs, community clinics |
Scenarios
– Student training. Dental students record cases in Dental Forms, while medical students work on the same patient’s general history inside GNUmed — one record, two angles.
– Community clinic. A small clinic logs both oral exams and systemic conditions in the same database, avoiding double entry.
– Research project. Investigators link periodontal disease data from Dental Forms with systemic conditions stored in GNUmed.
Workflow (admin view)
1. Spin up a PostgreSQL server and install GNUmed.
2. Configure the core system: users, roles, modules.
3. Add the Dental Forms package into the client.
4. Adjust odontogram templates to match local coding rules.
5. Train staff to navigate between medical and dental sections.
6. Back up the database regularly — now it holds both domains.
7. Keep an eye on updates from GNUmed and from the dental fork, as they move separately.
Strengths / Weak Points
Strengths
– GNUmed is proven and standards-based, with HL7/FHIR support.
– Dental Forms bring the missing odontograms and procedure charts.
– Together they unify medical and dental data under one roof.
– Fully open-source, adaptable to teaching and research.
Weak Points
– Dental Forms alone are fairly simple, not a full dental EHR.
– Interface shows its age compared to modern cloud tools.
– PostgreSQL setup requires admin skill.
– Smaller user base than big-name systems.
Why They’re Stronger Together
On their own, GNUmed is blind to dentistry, and Dental Forms are too barebones to stand alone. But combined, they complement each other. GNUmed provides the serious infrastructure — standards, security, full EHR backbone. Dental Forms add the day-to-day tools a dentist needs. The result: a single record that covers both oral and systemic health. For dental schools, that means realistic training. For clinics, fewer silos and less duplication. For researchers, a more complete dataset. And that’s why the pairing matters more than the parts alone.
