I’ve been thinking a lot about medical AI agents lately, and I’m increasingly convinced that the most useful ones will not start as general “AI doctors.” That framing feels both risky and too broad. The more practical opportunity may be narrow, workflow-specific agents that help with the fragmented parts of healthcare: symptom collection, pre-visit preparation, report explanation, structured summaries, follow-up tracking, and continuity of care. I’m currently building an open-source project called Allergos: https://github.com/kimogrant/allergos The idea is to explore what an allergy-focused medical AI agent could look like. The scope is intentionally narrow. Not:
- replacing doctors
- making formal diagnoses
- acting as an autonomous medical decision-maker Instead, I’m interested in whether an agent can help with things like:
- collecting allergy-related symptoms through adaptive questioning
- structuring messy patient input into usable context
- helping users prepare for a doctor visit
- explaining allergy test reports in plain language
- tracking triggers, reactions, medications, and follow-ups
- creating a longitudinal allergy profile that can be reused over time My current belief is that medical AI agents need to be designed around workflow continuity, not one-off answers. Healthcare is rarely a single Q&A session. It is usually a chain of messy events: symptoms, uncertainty, reports, appointments, lifestyle changes, medications, follow-ups, and repeated decisions. A generic chatbot is not enough for that. A useful medical agent probably needs: Clear scope boundaries The system should be explicit about what it can and cannot do. Structured memory User-approved health context should be saved, edited, deleted, and reused transparently. Human handoff The agent should know when to stop and recommend professional care. Source-grounded explanations Especially for reports, medical concepts, and risk-related guidance. Workflow integration The output should become something useful: a summary, a checklist, a record, a follow-up plan, or structured context for a clinician. I’m especially interested in allergy because it is a good example of a condition area where daily triggers, symptoms, test reports, and long-term management are all connected. The product challenge is not just answering questions. It is helping users organize and reuse health context over time. I’d love feedback from people working in AI, healthcare, health IT, or open-source:
- Is allergy a good domain for a vertical medical agent?
- What safety boundaries would you consider mandatory?
- What parts of the workflow should stay human-led?
- How would you structure allergy-related memory and user context?
- Are there existing open standards or data models I should look at? Again, this is not meant to be a diagnostic tool or a replacement for clinicians. I’m treating it as an exploration of domain-specific medical AI agents and how they might support real healthcare workflows safely. submitted by /u/clzncu
Originally posted by u/clzncu on r/ArtificialInteligence
You must log in or # to comment.