Homeo AI vs Dr. Homo: Offline Prescriptions or Case Review?

Quick answer

Choose Dr. Homo when the tested job is running a Bangladesh homoeopathy clinic's patient register, medicine catalogue, prescriptions, invoices, dues, and Android workflow in English or Bangla, including periods without internet. Choose Homeo AI when the tested job begins with a completed case narrative and requires a practitioner to inspect proposed symptoms, rubric mappings, source passages, remedy differences, and follow-up changes before accepting any clinical interpretation.

These products are not substitutes for every part of each other. Dr. Homo is primarily an operational practice system. Homeo AI is primarily a reviewable case-analysis copilot. A clinic may reasonably use an operations system around Homeo AI, but it should decide which product holds the authoritative patient record and how approved information moves between them.

This comparison uses Dr. Homo's live product and pricing page and its Bengali user guide, published in July 2026. Those are vendor-controlled primary sources. They document the available workflow and offer, but they do not independently validate speed, security, clinical quality, adoption, or outcomes.

What is current in Dr. Homo

Dr. Homo's current product page describes a browser application plus Android v1.0.1 for Android 8 and later. The vendor says the Android app can add patients, write prescriptions, record payments, and sync after connectivity returns. The browser version still needs internet. The interface supports English and Bangla, while the July 2026 guide itself is written in Bangla.

The operational sequence is concrete. A clinic configures its own potencies, doses, pack sizes, disease catalogue, medicine catalogue, and default prices. A practitioner selects a patient, records the complaint and history, chooses a diagnosis field, adds medicines, sets advice and follow-up, finalises the prescription, and receives a PDF plus an invoice. The guide says a finalised prescription cannot be edited. That can help preserve an audit trail, but the clinic should test how corrections, cancellations, and replacement prescriptions are represented.

The vendor also describes a separate MySQL database for each clinic, patient lookup by phone number, family contacts, partial payments, dues tracking, printable invoices, clinic logos, and uploaded signatures. These are vendor descriptions, not an external security assessment. A database-per-clinic architecture can reduce accidental cross-clinic mixing, but isolation also depends on credentials, authorization, backups, support access, logging, patching, and incident response.

Price and contract questions

On 13 August 2026, the public page displayed a pay-as-you-go option at BDT 0 per month with BDT 1 per prescription, Pro at BDT 1,000 per month, and Premium at BDT 2,000 per month. It also advertised 16 percent savings for yearly payment. The visible Pro allowance was up to 15,000 patients per year and 1,200 prescriptions per month; Premium displayed unlimited patients and prescriptions. Payment routes included bKash, bank transfer, and cash.

The pay-as-you-go wording deserves a written checkout definition. Ask which action creates the BDT 1 charge, whether drafts count, whether a correction creates another charge, whether taxes apply, and whether the offline app can queue work after a payment or plan limit is reached. For the paid plans, confirm whether patient and prescription limits are hard stops, whether archived records count, and what support or updates the price includes.

The July guide says that when a subscription expires, clinic data remains stored but login is unavailable until renewal. That is useful behavior to know before purchase, but it is not a complete exit policy. Request written terms for retention duration, export format, deletion timing, backup removal, account recovery, and access to records needed for continuity of care.

The current footer labels Privacy and Terms, but both links resolved to the product root during this review rather than to separate, reviewable documents. Before putting any real patient information into the service, obtain dated privacy, service, breach-notification, processor, retention, deletion, and data-export terms. Also confirm where data and backups are hosted and which support staff can access them. A homepage statement about database isolation cannot replace an executed agreement.

Where Homeo AI fits

Homeo AI should be evaluated on a different primary job. It starts with the practitioner's original narrative and helps structure symptoms, propose rubric mappings, inspect source material, compare remedies, and carry the reasoning into follow-up review. The useful distinction is not whether a tool can store a complaint or print a prescription. It is whether the practitioner can see and correct the path from the original wording to every accepted interpretation.

Homeo AI does not replace Dr. Homo's advertised offline Android prescribing, Bangla interface, bKash-centered purchasing, invoice ledger, dues workflow, medicine-price catalogue, or Bluetooth printing. Dr. Homo should not be assumed to reproduce Homeo AI's exact narrative-to-rubric correction trail merely because its guide includes complaint, history, diagnosis, and medicine fields.

If a clinic uses both, keep the raw narrative and practitioner-approved interpretation distinct. Do not copy a generated remedy suggestion into a prescription as if it were verified. Decide whether Dr. Homo stores only the final authorised prescription and operational record, while Homeo AI stores the analysis trail, or whether an approved export is attached to one system. Avoid two editable master records.

A reproducible clinic test

Use three completed, de-identified cases: one routine first consultation, one follow-up with several changed modalities, and one bilingual note containing English and Bangla phrases. Remove names, phone numbers, dates, addresses, document images, and other identifiers before testing.

In Dr. Homo, create a test patient and configure a small medicine catalogue with test-only prices. Record the history, draft a prescription, save it, reconnect after working offline, finalise it, create a partial payment, download the prescription and invoice PDFs, and attempt a documented correction. Measure time to find the record, sync reliability, duplicate creation, correction clarity, PDF accuracy, Bangla fidelity, and whether dues reconcile after reconnecting. Do not use a real prescription, real payment, or patient data.

In Homeo AI, enter the same de-identified narratives. Record which symptoms and rubrics are proposed, accepted, edited, or rejected; which source passages are opened; whether a second practitioner can reconstruct the reasoning; and whether the follow-up remains visibly separate from the original case. Repeat the bilingual case and compare meaning preservation rather than only the final remedy list.

Score both products on correction time, source traceability, offline behavior, export completeness, language fidelity, access after cancellation, data exposure, actual annual cost, and the ability to reconstruct a decision. A fast PDF is not proof that a prescription is appropriate. A plausible differential is not proof that its inputs or reasoning are correct.

Known limits and clinical responsibility

Dr. Homo's public materials are vendor statements. This review did not independently validate its database isolation, sync conflict handling, backup restoration, encryption, prescription speed, or clinical results. Its current public legal-document path is incomplete, so data governance must remain a procurement gate.

Homeo AI can also misread a narrative, omit context, propose an unsuitable rubric, surface an irrelevant passage, or produce a plausible differential that requires correction. Inspectability makes review possible; it does not make the output correct.

Neither product replaces diagnosis, referral, an emergency-care decision, practitioner judgment, prescription, potency, dosage, or follow-up responsibility. Urgent, severe, or rapidly worsening symptoms require appropriate medical assessment. The practitioner remains responsible for every accepted interpretation, source, record, prescription, and action.

Conditional verdict

Choose Dr. Homo if a hands-on test confirms that the clinic needs an English and Bangla operational system with offline Android patient and prescription work, invoices, dues, local payment methods, and simple public pricing. Proceed only after the vendor supplies complete legal, retention, export, deletion, backup, security, and correction terms.

Choose Homeo AI if the priority is a reconstructable case-review path from original narrative through practitioner-approved symptoms, rubrics, source inspection, remedy differentiation, and follow-up. If both are used, establish one authoritative record, a one-way approved handoff, and a documented correction process before real clinical data enters either system.

Official sources checked

• Dr. Homo official product and pricing page
• Dr. Homo official July 2026 Bengali user guide
• Dr. Homo official Android v1.0.1 download

Product facts reviewed 2026-08-13. Confirm current features, prices, source libraries, and terms with the vendor.