DNAI · BiobadamexAI · Secure registry intake

WhatsApp-first intake
for rheumatology registries.

BiobadamexAI captures clinical requests and PDFs, validates the payload, encrypts storage at rest, separates metadata from blobs, and routes the case to downstream analysis — built around Dr. Erick Zamora's operational workflow.

Request demo Read the brief
Proof of concept · Active evaluation · Dr. Erick Zamora
BiobadamexAI · Intake / registry / handoff En uso

Intake capture

WhatsApp / PDF · New registry intake Operator sends a clinical request, a secure PDF, or both. The system validates the payload before it reaches storage or analysis.

Channel logic

WhatsApp first · secure PDF fallback · operator allowlist · audit-friendly routing

What gets captured

Input

Text / PDF

Validation

Checked

Storage

Encrypted

Handoff

RheumaAI / DNAI

Registry workflow output

Validated Payload accepted and structured The intake is checked for format and context before it enters the registry workflow.
Encrypted Blob and metadata stay separate The document is protected at rest, while audit metadata remains queryable and distinct.
Handoff Ready for RheumaAI and DNAI Clinical interpretation and deeper analysis are delegated instead of being mixed into intake.

Demo narrative

Step 1: capture the request from WhatsApp or the web upload path

Step 2: validate, encrypt, and store with separated metadata

Step 3: hand the case off to the right analysis layer

Step 4: keep the workflow auditable for the registry owner

"The real problem is not just collecting the file. It is making intake secure, auditable, and usable by the people who need to act on it next. BiobadamexAI does that."

Dr. Erick Zamora - Rheumatologist · Primary operator

7 layers in the
intake and
analysis stack

Registry intake breaks when the message, the PDF, and the analysis all live in different places.

Fragmented intake

Clinical requests arrive through chat, attachments, and ad hoc forwarding.

The team needs one secure place to receive the request, validate it, and preserve the evidence without losing context or creating extra manual work.

Security gap

Forwarding PDFs manually makes auditability and privacy fragile.

BiobadamexAI encrypts intake files at rest and keeps metadata separate so the workflow stays reviewable.

Analytics handoff

Intake should not be the same thing as interpretation.

BiobadamexAI hands the structured case to RheumaAI and DNAI so the clinical and analytical layers stay cleanly separated.

How BiobadamexAI works.

01

Receive intake through WhatsApp or secure PDF upload.

The system starts where the operator already is. Text or document input enters the workflow through a secure channel instead of getting lost in forwarding chains.

02

Validate the payload and encrypt what needs to be stored.

BiobadamexAI checks the intake structure, keeps the blob and metadata separate, and persists the document with at-rest encryption.

03

Route the structured case to the right analysis layer.

RheumaAI handles the clinical interpretation, DNAI handles deeper analysis, and the registry workflow remains auditable end to end.

Core capabilities

What BiobadamexAI manages.

Current capabilities

  • WhatsApp-first intake routing for the primary operator path
  • Secure PDF fallback when the document should not move as chat
  • Encrypted at-rest storage for intake blobs
  • Separated metadata for traceability and audit
  • Document extraction and validation for registry-ready payloads
  • Analytics handoff to RheumaAI and DNAI
  • Allowlist-based access controls for operator and admin flows
  • Split frontend and API surfaces for a clean demo or deployment

Access status

Proof of concept in active evaluation.

BiobadamexAI is built for registry operators, clinical teams, and collaborators who need a secure demo path and a clearer intake story.

Request demo Read the DNAI brief first

Part of the DNAI proof stack

BiobadamexAI LES AI RheumaAI RheumaScore ORVS Beach Science / clawRxiv STORM

Common questions.

Is BiobadamexAI a chatbot?

No. It is a secure registry intake and workflow layer. Chat can be the entry point, but the product is really about validation, encryption, metadata separation, and clean handoff into analysis.

What happens to uploaded PDFs?

They are encrypted at rest and stored separately from metadata so the workflow stays auditable without exposing the document handling logic.

Who is it for?

Registry owners, clinical teams, operators, and collaborators who need a secure intake path and a demo story that actually matches the workflow.

What is the commercial angle?

A pilot or implementation that proves the secure intake path first. If the workflow sticks, the recurring model comes later through support, hosting, analytics, or operations.