SauBit API

Medication safety as critical infrastructure

SauBit is the medication-safety engine that hospitals, clinics and pharmacies integrate directly into their prescribing and dispensing workflow. Every call returns a structured, traceable risk analysis of a prescription — drug-drug interactions, clinical contraindications, dose adjustments, allergies, pharmacogenomics and more — with the evidence behind every alert made explicit in the response, never hidden behind a black box.

This is the public technical documentation of the API, written for the engineering teams integrating the system — not a commercial or marketing document.

Clinical decisions cannot rest on a black box

SauBit's decision engine is deterministic: every interaction, contraindication and critical alert is produced by versioned, auditable clinical rules — not by a language model's inference. The AI layer exists to explain and contextualize the result, never to decide on its own whether a combination is safe.

What sets SauBit apart

Principle	What it means in practice
Deterministic engine, not probabilistic	Every known severe interaction is caught by an offline clinical safety net — a false negative on a dangerous combination is treated as worse than any AI hallucination, and handled as a production incident.
Evidence always visible	Every alert exposes the source backing it (curated base, DDInter, openFDA, DailyMed, PubMed, the organization's internal knowledge base) in source_coverage — nothing is asserted without traceable provenance.
Transparency about uncertainty	When relevant clinical data was not provided, the response explicitly states what could not be evaluated, instead of appearing safe when it isn't.
Alert governance, not risk governance	An organization can tune how alerts are presented by unit and clinical role, but prescription_risk_level is always computed over the complete set — presentation suppression never lowers the actual risk.
End-to-end traceability	Every analysis carries an analysis_id, engine version, rules version and source coverage — auditable long after the call, not just at request time.
Fluent in hospital standards	Speaks FHIR R4, HL7 v2 and CDS Hooks natively — SauBit fits the integration the hospital already has, instead of demanding a new one.

What you'll find in this documentation

• Quickstart guide — from your first API key to your first analysis, in minutes.
• Authentication — X-API-Key, scopes and security best practices.
• Interactive API reference — the full specification, with Try it right in the browser.
• Operational guides — drug interactions, drug comparator, alert governance, clinical context, clinical chat and more.
• Hospital integration — FHIR R4, CDS Hooks, HL7 v2, MCP and webhooks.
• Pharmacies — a dedicated flow for pharmacy dispensing.
• Compliance — LGPD and regulatory posture.

Environment

Production	https://api.saubit.com.br
Authentication	X-API-Key header (see Authentication)
Format	JSON over HTTPS; stable, versioned contract
Billing	Per transaction — see Commercial model

Technical support

• Email: suporte@saubit.com.br
• Enterprise SLA: as per contract.

Scope of this documentation

This site documents exclusively the client-facing routes (hospital, clinic and pharmacy), authenticated via X-API-Key. Administrative routes (organization management, keys, billing and internal governance) use their own authentication and live in separate documentation, restricted to the SauBit operations team — they are not part of this material.