BioChirp Help & Documentation
BioChirp is a biological intelligence hub that combines LLM reasoning with curated drug–target–disease databases and real-time web search. This page explains how to use it safely, interpret answers, and troubleshoot issues.
What BioChirp focuses on
Drug–target–disease relationships, mechanisms of action, biomarkers, pathways, gene associations and approval status, with structured, auditable outputs.
Who it is for
BioChirp enables researchers, students, and clinicians to access the complete landscape of biomedical associations (drug–target, gene–disease, pathways, and more) across entire datasets. Unlike standard LLMs, which often provide only partial, summarized information due to context limits, BioChirp delivers structured, verifiable results with deeper insights and transparent evidence beyond simple text summaries.
Important safety notice
BioChirp is a research assistant, not a medical device. It must not be used for emergency care or as a sole basis for clinical decisions.
1. Quick start
If you are opening BioChirp for the first time, follow these steps to get a reliable, auditable answer in under a minute.
-
Open the chat:
Go to
Start Chattingfrom the top navigation. - include at least one of: drug, target/gene, disease, pathway, biomarker, mechanism of action or approval status.
- Add context if you care about filters: for example: “for multiple myeloma”, “approved in ADHD”, “associated with fever”.
- Send the query and wait for the orchestrated answer: BioChirp sequentially uses its interpreter, biomedical databases, and web/literature search—selecting the most relevant tool based on your question’s scope.
- Review detailed, structured results: Each tool’s output is clearly labeled so you can trace and audit every step. If your question matches BioChirp’s biomedical scope, you’ll get a comprehensive association table directly from curated databases. For broader topics, web and literature sources are included. All results are transparent, verifiable, and available for download (CSV/JSON), making it easy to review or identify any discrepancies.
Good starting queries
List PARP inhibitors used to treat ovarian cancerTargets involved in the NF-kappa-B pathwayBiomarkers relevant to ADHDApproved drugs targeting EGFR in non-small cell lung cancer
Queries that may fail or be routed to web
Is this patient curable?→ out of scope, clinical judgement only.Should I stop this drug?→ BioChirp will not give treatment decisions.-
Negative / “not” questions(e.g. “drugs that do not cause X”) are usually routed to web search because databases rarely encode negative evidence.
2. Asking good questions
BioChirp performs best when you tell it what kind of entity you care about and how you want the result organized.
Specify intent explicitly
Use phrases like “list targets”, “find biomarkers”, “show pathways”.
List drug–target pairs for HER2-positive breast cancerShow pathways associated with TNF in inflammatory diseasesProvide biomarkers with evidence for early detection of pancreatic cancer
Note: BioChirp only returns association relations that exist in its curated databases. Some advanced filters (e.g. “early detection”) may not be supported if corresponding associations are not available in the source data/ biochirp scope.
Add filters when needed
You can include simple constraints, which the planner will translate into database filters where possible.
only approved drugs/experimentalfor multiple myeloma/for fevertargeting JAK family
How the Interpreter uses your query
The Interpreter normalizes acronyms, expands obvious synonyms (e.g. “tb” → “tuberculosis”),
and fills a structured dictionary with fields such as drug_name,
target_name, disease_name, pathway_name,
biomarker_name and approval_status.
If your query is too vague or purely clinical, without clear biomedical entities or relations, BioChirp automatically routes it to the web and literature search tools, since database lookup requires explicit, mappable entities.
3. Data & sources
BioChirp is designed as a “Database-GPT” for drug–target–disease questions. For biomedical queries, the orchestrator follows a strict order of tools and databases.
Curated database sources
- TTD (Therapeutic Target Database): drug–target–disease associations and target classes.
- CTD (Comparative Toxicogenomics Database): chemical–gene–disease interactions and environmental exposures.
- HCDT (Highly Confident Drug–Target Database): validated drug–target pairs with strong supporting evidence.
Note: BioChirp answers biomedical association queries using these databases whenever possible for maximum reliability and traceability.
Web & literature integration
If a query falls outside the scope of these databases or needs the latest evidence, BioChirp will automatically supplement with:
- A general web search micro-service (for guidelines, official sources, or recent updates)
- A Tavily-like biomedical literature search for the most up-to-date scientific findings
All web- or literature-derived answers are clearly labeled and include references or links when available.
How BioChirp is different from traditional LLMs
Most chatbots answer directly from the LLM’s internal training data, sometimes using simple web search or RAG. BioChirp inverts this approach: the source of truth is the database layer. The LLM acts as a precise interface to interpret queries, expand terms, and organize results from these databases.
- No “LLM knowledge base” answers: BioChirp does not rely on model memory for biomedical facts. Instead, it first queries trusted databases: Therapeutic Target Database (TTD), Comparative Toxicogenomics Database (CTD), and Highly Confident Drug–Target Database (HCDT).
-
LLM for understanding, not guessing: The LLM interprets your question, normalizes synonyms and acronyms, and maps terms to database fields like
drug_name,target_name, anddisease_name. - Hybrid synonym and family search: BioChirp combines fuzzy matching, deep-learning embeddings, and official APIs for robust synonym and family member expansion.
- Graph-based planning: A graph traversal algorithm builds a join/filter plan so that only relevant associations from the database are retrieved.
- LLM only for summarization: When structured results are available, the LLM is used only to summarize the database output—not to generate new facts.
Note: If your query cannot be answered using BioChirp’s in-scope database fields, the system will fall back to web and literature search, similar to general LLM tools. However, BioChirp is designed to prioritize authoritative biomedical sites and primary literature, not generic web results, ensuring higher trust and transparency in every answer.
Execution order (for valid biomedical queries)
- Interpreter & synonym/family tools (normalize entities).
- Planner (graph-based join and filter plan across tables).
- TTD → CTD → HCDT (always in this order for structured data).
- Optional web / Tavily calls if more context is needed.
- Summarizer (produce a friendly, traceable answer from the final tables).
4. Understanding BioChirp answers
Answers are designed to be short, inspectable and reproducible. Most responses have two layers: a human-readable explanation and a machine-readable table.
Narrative section
- 1–3 short paragraphs describing how the query was interpreted, which databases were used, and how many rows were found.
- Key entities such as drug names, targets, and diseases are often highlighted.
- Limitations or missing data are explicitly mentioned instead of being silently guessed.
Tabular / structured section
- Stable column names (e.g.
drug_name,target_name,disease_name,evidence_source,approval_status). - Preview of the first N rows in the chat interface.
- Download options (CSV / JSON) when enabled in your deployment.
Provenance & reproducibility
- Each micro-service call (interpreter, planner, TTD, CTD, HCDT, web, Tavily) can be logged with its exact inputs and outputs for audit trails.
- If something looks wrong, you can re-run the same query and compare tool-level JSON to debug.
5. Scope & limitations
What BioChirp is designed to do
- Map drug–target–disease relationships, including approval status, pathways, and biomarkers using curated databases.
- Provide mechanistic or pathway-level overviews with citations from trusted sources.
- Summarize recent literature related to specific biomedical entities.
- Export structured data in formats suitable for further analysis in Python, R, or Excel.
What BioChirp will not do
- Provide personal medical advice, diagnosis, or treatment recommendations.
- Replace clinical guidelines, specialist judgment, or regulatory documents.
- Guarantee completeness for newly approved drugs, rare diseases, or off-label uses.
- Occasionally fail to fully understand the query, leading to incorrect results. However, each tool’s output is clearly explained in layman's terms, and users can audit each step to identify discrepancies.
- Reliably handle negation-based queries (e.g., "drugs that do not cause X"); such queries are better suited for web or literature search.
Bias, Uncertainty & Conflicting Sources
- BioChirp prioritizes curated database entries, but conflicting information across databases will be highlighted for transparency.
- If evidence is weak or limited, the summary will explicitly state it, ensuring you are aware of any uncertainty in the data.
- For critical findings, always cross-check against the original databases or primary literature to verify accuracy.
6. Troubleshooting & common issues
If BioChirp behaves unexpectedly, use the hints below to understand which micro-service may be involved.
“Your query is invalid or too vague”
- The Interpreter could not confidently extract any drug, target, disease, pathway or biomarker.
- Try adding at least one explicit entity and desired relation, e.g.
drugs targeting JAK2 in myelofibrosis. - Avoid purely clinical descriptions without drug terms etc.
“No rows found in TTD / CTD / HCDT”
- The databases may genuinely not contain your query combination (e.g. very new indication).
- Check spelling and try a more generic formulation (e.g. disease family instead of subtype).
- BioChirp may still return web/literature summaries, but these will be clearly marked as such.
Service unreachable / timeout
- One of the micro-services (e.g. TTD, CTD, HCDT, web, Tavily) may be temporarily down.
- Try again in a few minutes; if the issue persists, send the error message and timestamp to support.
- Check the service health status to verify if all services are online and functioning properly.
Answer looks inconsistent or suspicious
- Cross-check the cited rows against the original database or paper.
- Re-run the query with slightly different wording to see if the same pattern appears.
- If you can, inspect the underlying JSON for the Interpreter, Planner and database responses.
- Report clearly with examples so the team can adjust filters or prompts.
7. Frequently asked questions
How is BioChirp different from ChatGPT or other general LLMs?
General LLMs answer directly from their internal training data and, in some cases, from simple web or RAG search. BioChirp, in contrast, treats curated databases (TTD, CTD, HCDT) as the primary source of truth. The LLM is used mainly to understand your query, normalize terms, map them onto database schemas, set dynamic similarity cut-offs, and summarize the resulting tables. This “database-first, LLM-last” design reduces hallucinations and makes answers easier to audit.
If BioChirp reduces hallucination, why can its responses still vary like an LLM?
BioChirp minimizes hallucinations by grounding all core answers in structured database rows. Final summaries are generated from the “head view” (top 50 rows) of the complete results table, so context-length limitations rarely apply.
However, minor variations can still occur, mainly in the synonym and family member expansion step. BioChirp uses three complementary processes:
- Fuzzy search: Always returns reproducible results for a given input.
- Official APIs (e.g., PubChem, HGNC): Provide consistent results across runs, as long as the external API services are available and unchanged.
- Semantic transformer embeddings: This method uses dynamic similarity thresholds and an LLM-based false-positive filter, which can occasionally introduce minor differences in the set of returned synonyms or family members between runs.
These factors can sometimes lead to small, non-deterministic changes in the complete association list, but overall, BioChirp remains much more consistent and auditable than standard LLM-based tools.
What databases does BioChirp have access to?
BioChirp is directly integrated with several authoritative, curated biomedical databases, including:
- TTD (Therapeutic Target Database): Comprehensive resource for drug–target–disease relationships and target classes.
- CTD (Comparative Toxicogenomics Database): Chemical–gene–disease interactions and information on environmental exposures.
- HCDT (Highly Confident Drug–Target Database): High-confidence drug–target associations with strong supporting evidence.
When relevant associations are not found in these databases, BioChirp can supplement answers using trusted web and biomedical literature sources, which are always clearly labeled and kept separate from database results.
How does BioChirp reduce hallucinations and response variance?
BioChirp restricts where the LLM can introduce uncertainty by enforcing a strict structure. The Interpreter and Planner must generate dictionaries and join-plans that match the underlying database schema; if they fail to map cleanly, the system does not guess and instead requests clarification or routes the query elsewhere.
For entity expansion, BioChirp combines fuzzy search and deep-learning embeddings similarity, along with LLM based selection, with results from official biomedical APIs (e.g., PubChem, HGNC/HUGO, OpenTargets) to retrieve standardized synonyms and family members. These expansions are then filtered with dynamic similarity thresholds so only well-supported candidates are included.
Even with synonym/family expansion, the final associations always come directly from curated databases. If no rows are found or if the query falls outside BioChirp’s database scope, the system will not fabricate relations—it clearly returns “no result.”
When database results are unavailable, BioChirp falls back to web and literature search using trusted biomedical sources through its Tavily-like search layer. This ensures the answer remains grounded in reputable, verifiable resources rather than random web pages.
Does BioChirp update its backend data when the source databases release new versions?
BioChirp currently operates on offline, locally downloaded snapshots of curated biomedical databases. We plan to update these datasets periodically—typically once a year or as needed based on major upstream releases or user requirements.
Any significant updates to the underlying data or system will be announced so users remain aware of version changes and improvements.
Can I export results for downstream analysis?
BioChirp allows you to export results in CSV or JSON formats when the query falls within the scope of the available biomedical data. The columns and entity names are designed to be stable, making it easy to integrate the data into your own analysis pipelines.
If you use BioChirp's services, please be sure to cite us as part of your work to acknowledge the platform and its data.
Is user-identifiable data stored?
BioChirp is designed to operate without requiring user logins, ensuring that no user-identifiable data is stored. User privacy is prioritized, and we do not collect any personal information during interactions.
8. Contact & support
When to contact the BioChirp team
- Persistent errors or timeouts from a specific micro-service.
- Clear mismatches between database entries and what BioChirp returns.
- Feature requests, UI issues, or questions about the roadmap.
- Concerns about safety, bias, or misinterpretation of evidence.
How to get help
When you report a problem, include: the full query you used, approximate time, a screenshot if possible, and whether the issue is reproducible.
Reminder: BioChirp is for research support only and is not a substitute for professional medical judgement. For medical emergencies, contact local emergency services immediately.