Paramus — Excipient Compatibility Screen

Overview

Rank candidate excipients by compatibility risk against an active ingredient, flagging known problematic pairings. The value is the active×excipient triage, not a single reactivity lookup.

Guidance vs execution: reactivity, property, and known-interaction data come from tested Paramus tools. Treat outputs as screening signals to prioritize lab confirmation.

When to Use

• Selecting excipients that won't react with or destabilize an active
• Narrowing an excipient longlist before compatibility studies Do not use for: full formulation optimization (use property optimization) or regulatory filings.

Workflow

Active ingredient + candidate excipients + dosage form
  ↓ 1. Characterize active reactivity   → functional groups, sensitivities
  ↓ 2. Screen each excipient pairing     → chemical + physical incompatibility
  ↓ 3. Check known-interaction data      → literature/knowledge-graph flags
  ↓ 4. Rank by compatibility risk        → low / medium / high
  ↓ 5. Emit ranked shortlist             → recommended excipients + provenance

Procedure

1. Discover tools via search/get_schema ("compatibility", "reactivity", "excipient", "interaction").
2. Characterize the active's reactive groups and physical sensitivities.
3. Screen each active–excipient pairing for chemical and physical risk.
4. Cross-check known problematic pairings from datasets/knowledge graph.
5. Rank excipients by compatibility risk with rationale.
6. Emit a ranked shortlist with provenance and confidence.

Domain Judgment

• Consider both chemical (reaction) and physical (moisture, polymorph) incompatibility.
• Known-pairing evidence outweighs prediction — cite the source when flagging.
• Present a shortlist with reasons, not a single "safe" pick — lab confirmation still required.

Fallbacks

• Reactivity/knowledge tool unavailable → deliver a manual functional-group compatibility checklist, clearly scoped.
• Endpoint unreachable → stop and report; do not fabricate compatibility rankings.