Homeo AI vs ResoField: Protocol Platform or Case Review?

Quick answer

Choose ResoField only when a qualified practitioner deliberately wants to evaluate its free client-record and AI protocol workspace across homeopathy, RIFE, bioresonance, and radionics, and is prepared to validate every suggestion independently under an adequate clinical-data agreement. Choose Homeo AI when the job is narrower: review a completed homeopathic narrative, inspect proposed symptom and rubric mappings, open supporting passages, correct the differential, and preserve an accepted reasoning trail for follow-up.

These are materially different products. ResoField combines several modalities and presents AI-generated protocol suggestions, including remedy and potency guidance. Homeo AI is positioned as a practitioner-led review aid that keeps the case-to-source chain inspectable. A buyer should not treat a longer list of modalities as stronger evidence, and should not assume a free plan removes the cost of verification, governance, or error.

ResoField's official product, feature, about, terms, and privacy pages were reviewed on 27 September 2026. They establish what the vendor currently publishes. They do not independently validate clinical effectiveness, recommendation accuracy, source completeness, security implementation, legal compliance, or outcomes for any modality.

What ResoField currently presents

ResoField describes a progressive web application for practitioners who use homeopathy alongside RIFE, bioresonance, and radionics. The product page lists client management, protocol construction, an AI protocol builder, import and export, language support, and access across devices. It presents the current offer as free.

The feature page says the AI builder uses OpenAI to suggest lists based on entered symptoms or conditions. For homeopathy, the page describes remedy and potency recommendations. It also describes frequency and item libraries for the other modalities. Those outputs are vendor-described suggestions, not independently verified prescriptions or evidence that the named modalities are effective. The page's references to encryption, row-level security, and controlled access are useful questions for diligence, but public technical labels do not demonstrate the deployed configuration.

The about page is unusually direct about provenance. It says the product began in 2025 and was created by a software developer and self-taught homeopathy practitioner rather than medical professionals. It also says the included modalities lack conclusive scientific evidence and that the application is not medical advice. Buyers should preserve these disclosures when assessing the product instead of allowing a polished interface or AI output to imply a stronger authority.

Free software still has a procurement cost

A zero-dollar subscription can reduce a trial barrier, but the total cost includes practitioner review, data preparation, staff training, migration, correction, export testing, contract review, and incident response. The terms say the service may offer free and paid plans and can change or discontinue features. A clinic should confirm what the current free commitment covers, whether usage limits apply, what happens if a paid tier launches, how notice is given, and whether records remain exportable before any change takes effect.

The terms also state that AI suggestions may be incomplete, inaccurate, or misleading and that the practitioner remains solely responsible for decisions. That is a meaningful warning. Testers should record the time required to verify each output, not just the time required to generate it. If a protocol appears instantly but demands extensive independent checking, the apparent productivity gain can disappear.

The same applies to import and export. A JSON or spreadsheet download is only useful if it includes the clinic's necessary fields, preserves relationships between clients and sessions, identifies the source and time of generated content, and can be restored elsewhere. Run an export, inspect it, re-import it into a disposable account if supported, and confirm that deletion and account closure do not strand an inaccessible copy.

The public privacy policy excludes the account application

ResoField's privacy page was updated on 9 September 2026, but its scope statement says it covers the public website only. It explicitly excludes the separate account application and its client, session, and treatment data. The public notice therefore cannot answer the most important clinical-data questions created by the product pages.

Before entering identifiable or linkable case material, request the binding policy or data-processing agreement for the account application itself. It should identify the controller and processor roles, legal entity, purposes, lawful basis, hosting regions, subprocessors, model provider data flow, encryption and key management, staff access, logging, retention, backups, breach notice, export, deletion, account closure, and whether prompts or outputs are used for training, evaluation, or product improvement.

This scope gap is not cured by a security claim elsewhere on the site. Encryption does not define who can access a record, how long a backup survives, what reaches an external model provider, or whether deletion covers generated protocols and logs. A clinic needs one document set that governs the actual service receiving clinical information.

The terms say the user keeps ownership of submitted content but grants a license required to operate and improve the service. Ask whether improvement includes model training, human review, analytics, or retained derived data, and how an opt-out works. Also reconcile the terms' processor language and Netherlands-law provision with the clinic's own professional, privacy, and record-retention duties.

Separate modality breadth from evidence quality

ResoField's central distinction is multimodal breadth. A practitioner can organize homeopathic items beside frequency-based and energy-oriented libraries. That may match an existing practice model, but a combined dashboard does not provide a common evidence standard. Every modality, source list, recommendation type, and patient-facing claim must be evaluated on its own evidence and professional boundary.

Homeo AI takes a narrower route. It starts with a completed narrative and focuses on whether the practitioner can see and correct the transformation into symptoms and rubrics, inspect supporting passages, compare remedies, and preserve accepted reasoning. It should not be credited with ResoField's frequency libraries, radionics items, multimodal protocols, or free client-management workspace. ResoField should not be assumed to reproduce Homeo AI's exact narrative-to-rubric correction trail because it offers homeopathy lists.

For either product, the useful question is not whether AI can output something plausible. It is whether another qualified practitioner can reconstruct the input, source, transformation, uncertainty, correction, and final human decision. A fluent list without that trail can increase review burden and encourage automation bias.

A reproducible safety-first evaluation

Prepare eight completed, de-identified cases whose reasoning is already documented. Use invented identifiers and remove names, contacts, exact dates, addresses, record numbers, photographs, rare occupations, and unusual combinations that could identify a person. Keep the original records and the re-identification key outside both products under the clinic's own controls.

Build an answer packet for each case containing the original wording, accepted symptoms, selected rubrics, source passages and editions, rejected interpretations, final differential, and follow-up changes. Include two straightforward narratives, two close differentials, one follow-up, one negation, one material modality, and one incomplete case that should produce uncertainty rather than confident completion.

In ResoField, test only the homeopathy workflow unless the evaluator is independently qualified and authorized for another modality. Record the entered text, generated items, any remedy or potency suggestion, visible source provenance, uncertainty, corrections, regeneration behavior, export, deletion, and time. Do not act on generated treatment guidance during the software evaluation. Change one negation and one modality, then verify whether the output changes for a reviewable reason. Repeat the same case to observe stability.

In Homeo AI, use the same completed narratives. Record every proposed symptom and rubric accepted, edited, or rejected, each passage opened, correction time, differential changes, export, and whether a second practitioner can reconstruct the accepted review. Reopen the follow-up and confirm that the earlier reasoning remains distinguishable from the new information.

Score the tools on narrative fidelity, source identity, edition visibility, correction burden, uncertainty, repeatability, export completeness, deletion, access control, and total verification time. Do not award points because a leading item matches a historical prescription. Agreement can occur for an unsupported reason, while a disagreement may expose an ambiguity worth reviewing.

Result-set and identity caution

ResoField's exact-name search results have limited independent diversity. The official application and dashboard dominate relevant results, while other prominent domains use the same name for unrelated cooling or research projects. This does not mean the product is invalid. It means search visibility should not be mistaken for independent validation and buyers must confirm they are reading documents for the correct service.

Keep procurement evidence tied to the resofield.app identity, current legal documents, and the actual account contract. Do not import claims from an unrelated ResoField project, a general AI discussion, or a different practitioner product merely because a result page appears beside the vendor.

Known limits and clinical responsibility

An AI-generated list can be wrong, incomplete, or misleading. A free plan does not prove sustainability. Encryption labels do not prove access control or deletion. A founder's transparent disclaimer improves provenance but does not validate a clinical recommendation. Combining homeopathy with experimental modalities does not create shared evidence for them.

Homeo AI can also misread a narrative, suggest an unsuitable rubric, omit relevant evidence, or produce a plausible differential that requires correction. Source visibility improves reviewability; it does not make a conclusion 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 accountable for the original record, every accepted interpretation and source, and every clinical action.

Conditional verdict

Choose ResoField only if its multimodal protocol workspace is deliberately in scope, the practitioner accepts the evidence limits, a controlled trial shows an adequate review trail, and the vendor supplies binding account-application privacy and data-processing terms before clinical data is entered.

Choose Homeo AI if the priority is a focused, reconstructable homeopathy review from completed narrative through corrected symptom and rubric structure to inspected passages, remedy differentiation, and follow-up. If both are tested, keep the trial de-identified, avoid acting on generated treatment guidance, and compare verification burden rather than output speed or modality count.

Official sources checked

• ResoField official product page
• ResoField official feature page
• ResoField official about page
• ResoField terms of service
• ResoField public-website privacy policy

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