RheumAI
RheumAI is a specialized clinical decision-support system for rheumatology. It combines clinical conversation, literature retrieval, medical tools, and post-generation review. Its purpose is to help clinicians organize information, find gaps, and examine hypotheses. This description explains its function; it does not claim prospective validation, regulatory approval, or medical-device status. It does not replace clinical judgment or autonomously approve registry data.
In one sentence
Section titled “In one sentence”RheumAI turns a clinical question or note into a structured response reviewed by several software layers:
flowchart LR A["Question or note"] --> B["Planner"] B --> C["Sources and tools"] C --> D["Clinical response"] D --> E["ORVS and citation controls"] E --> F["Ethical review"] F --> G["Response for the clinician"]
Current surfaces
Section titled “Current surfaces”| Surface | Use | Observed state |
|---|---|---|
| Web application | Conversation, files, and sessions | Active in the main codebase |
POST /api/chat |
Persistent conversational flow | Active; database-backed and file-aware |
POST /v1/study/rheumaai-reply |
Controlled evaluation of a de-identified note | Active; stateless, authenticated, and designed not to write RheumAI rows |
vanilla, rag, dag, quick-orvs, full-orvs |
Compare pipeline variants | Experimental; explicitly selected |
| Deep research | Longer evidence search and synthesis | Active as a separate flow |
| x402 | Optional payment for API clients | Optional, configuration-controlled integration |
What happens during a clinical request
Section titled “What happens during a clinical request”- Access controls apply authentication, limits, and optional x402 enforcement.
- RheumAI creates or retrieves the conversation and prepares request state.
- Uploaded files are parsed before planning.
- The planner selects tools and sources, such as PubMed, Semantic Scholar, local knowledge, the knowledge graph, or lab interpretation.
- Retrieved sources are reranked for the question.
- The response generator uses RheumAI’s clinical persona.
- ORVS reviews the response when applicable. A failed score can trigger regeneration.
- A separate gate checks retrieved PubMed IDs and removes unverified identifiers.
- Ethical review can block a rejected output. If that review fails technically, current code passes the response through and records the failure.
- The result returns to the clinician with the evidence available in that turn.
What it does not do yet
Section titled “What it does not do yet”- It does not independently produce a complete BIOBADAMEX record ready for submission.
- It does not score the input note against every required registry field.
- It does not return a structured distinction among missing, not applicable, and unknown data.
- It does not replace clinician review and approval.
The proposed BiobadamexAI integration uses RheumAI for reasoning and explanation. Registry schema, field-level provenance, completeness rules, and clinician approval remain in the controlled institutional workflow. See Clinical notes and completeness and the current BiobadamexAI workflow.
Interpretation limits
Section titled “Interpretation limits”These pages describe code at commit 149508b3ab79da0b88c56deb63f6fb66e35d0e68. A registered tool is not proof that every environment configures it or that it has clinical validation. Experimental paths and fallbacks are labeled throughout this section.