What should a homeopathic patient record contain that a generic medical EHR doesn't?

The totality. A generic EHR is organised around diagnoses, prescriptions and billing codes; a homeopathic record is organised around the symptom picture — mental and general symptoms, modalities, peculiar symptoms, the repertorisation that followed from them, the remedy and potency chosen, and how the picture changed at each follow-up. If your software can't show you last year's totality next to today's, it's storing your data but not your reasoning.

Do I need separate software for patient records and repertorisation?

Historically that was the norm: a repertory program on one side, paper files or a generic EHR on the other, and endless retyping between them. Integrated platforms remove that seam — the case narrative, the extracted symptoms, the repertorisation and the prescription live in one record. The practical test: when a patient returns after eight weeks, can you reopen the original analysis in one click, or do you reconstruct it from notes?

Is cloud storage of patient data legal for homeopaths under GDPR?

Yes, provided the processor handles health data appropriately: encryption in transit and at rest, EU-appropriate data processing agreements, access controls, and the ability to export or delete a patient's record on request. What GDPR actually punishes is informality — patient files in a personal spreadsheet or unencrypted folder. A purpose-built platform with GDPR compliance is generally a step up from the improvised systems it replaces.

Does Similia handle appointment scheduling and billing?

No — deliberately. Similia manages the clinical side: the case record, repertorisation, materia medica, prescriptions and follow-ups. Scheduling and invoicing are generic problems with excellent dedicated tools, and duplicating them badly would tax the thing homeopaths actually need from us. Most practices pair Similia with their existing calendar and invoicing setup.

Can I move my existing paper or spreadsheet cases into a digital system?

Yes, and you don't need to migrate everything at once. The workable pattern is forward-first: every new consultation goes into the platform from today, and historical cases are added when the patient next returns — a few minutes to summarise the story so far, often helped by dictating it with live transcription. Within a year, the active caseload has migrated itself.

Homeopathy Practice Management Software: Patient Records, Follow-Ups & Data Protection

Ask a homeopath what software they use for repertorisation and you'll get a quick answer. Ask what they use for the practice — patient files, follow-up histories, consents, prescriptions across the years — and the answer is usually a pause, followed by some combination of paper folders, a spreadsheet, a generic EHR built for allopathic clinics, and memory.

That gap has a name in every other branch of healthcare: practice management. This article is about what practice management actually means for a homeopathy clinic — which parts you genuinely need, which parts you don't, and how to choose software that treats the homeopathic case record as the first-class object it is.

The patient record is not a formality — it's the instrument

In homeopathy, the record isn't administrative exhaust; it's clinically load-bearing in a way few other disciplines match. The follow-up decision — repeat, wait, change remedy, change potency — depends on comparing today's picture against the original totality, sometimes years later. Hering's direction of cure is literally unobservable without a record of where the symptoms started.

A practice management system for homeopathy therefore has one non-negotiable job: preserve the reasoning, not just the data. The narrative as the patient told it. The symptoms you selected as characteristic. The repertorisation that ranked the field. The differential you weighed in the materia medica. The prescription, the potency, and what happened next. A system that stores PDFs of scanned notes technically "has" all of this — and can answer none of it.

What a homeopathy practice actually needs

Strip away the enterprise-EHR feature lists and a homeopathic practice needs five things:

1. A case record built around the totality. Structured symptoms with modalities and grades, linked to the narrative they came from, with the repertorisation attached — not stored in a different program.

2. Follow-up continuity. Each return visit as a new entry against the same case, with the original analysis one click away. This is where spreadsheet systems die: version seven of a file called MariaK_final_v7.xlsx is not continuity.

3. Prescriptions with history. What was given, when, at what potency, with what response — queryable across the whole patient history, so "have we tried Lycopodium before, and what happened?" takes seconds, not archaeology.

4. Data protection you can defend. Health data is special-category data under GDPR. Encryption, access control, export and deletion on request, and a data processing agreement you could actually show a supervisory authority. Our HIPAA & GDPR guide for homeopaths covers the specifics; the short version is that an improvised system is a liability wearing a familiar interface.

5. Portability. House calls, clinic rooms, the desk at home: the record has to follow you, and it has to work on a phone without pretending your thumb is a mouse.

Notice what's not on the list: billing codes, insurance claims, lab integrations, bed management. Homeopathy practices are lean; the software should be too.

Where the admin layer ends and the clinical layer begins

Here's the honest structural point most vendors won't make: scheduling and invoicing are generic problems; the case record is not. Calendar tools and invoicing apps are polished, cheap, and interchangeable. The homeopathic case record is none of those things — it's the specialised core that generic tools can't fake.

So the sane architecture for a small practice is a split: a dedicated clinical platform for cases, repertorisation and follow-ups, plus whatever calendar and invoicing tools you already like. Distrust any homeopathy product whose billing module gets more screenshots than its case screen — it tells you where the development effort went.

How Similia covers the clinical layer

Similia is the clinical side of that split, built as one environment for the whole loop described in our practitioner workflow guide:

Cases as living records. Narrative, structured symptoms, analyses, prescriptions and follow-ups in one place, synced across devices, with the original totality always in view at follow-up.
Case taking that keeps your eyes on the patient. Live audio transcription turns the consultation into text as it happens; Notes-to-Rubric extracts candidate symptoms and maps them to rubrics you approve or reject — the record builds itself while you listen.
Repertorisation and materia medica in the record, not next to it. The analysis is attached to the case; remedy differentials link straight into the integrated materia medica library.
Data protection as a feature, not a promise. GDPR-compliant handling of patient data, encrypted in transit and at rest, with export when you need it.
A free start. The free plan includes case management with the classical repertories — enough to run the workflow on real consultations without spending a euro — and Pro removes the monthly case limits and adds the AI toolkit when the practice needs them.

And the deliberate omissions: no scheduling, no invoicing, no insurance claims. Your calendar app is better at calendars than we would be.

Choosing: the five-question test

Whatever you evaluate — including us — sit down with a trial account and one real (anonymised) case, and ask:

Can I see the original totality and today's picture side by side at a follow-up?
How many retypes does one consultation take, from the patient's words to a saved analysis?
If a patient invokes GDPR tomorrow, can I export or erase their record — and would the vendor's data agreement survive scrutiny?
Does it work, honestly, on my phone?
If I leave the platform in three years, what do I take with me?

Any system that passes those five will run a homeopathy practice. Most of what's marketed as "clinic software" fails at least three.

The bottom line

Practice management for homeopathy isn't about becoming a hospital in miniature — it's about protecting the thing your prescriptions depend on: the record of reasoning across time. Keep the generic admin in generic tools, put the clinical record in software that understands a totality, and the practice runs lighter, safer, and faster.

If you want to feel the difference, open a free Similia account, enter one real case, and take it through analysis to a saved record. The comparison with the folder-and-spreadsheet system makes its own argument.