Public CV // evidence-linked

B. Fabio
Mejías Fernández

Physician, Clinical Pharmacology Resident and eHealth Developer in Madrid, working at the boundary between clinical reasoning, product scope and software delivery.

ContactGitHub ↗

Professional profile

I translate clinical and operational questions into inspectable software prototypes. The public work emphasizes explicit intended use, synthetic demonstrations, human review, security boundaries and honest separation between repository capability and deployed state.

This concise CV intentionally avoids institutions, employment dates, degrees and claims that are not independently documented on the public portfolio. A formal chronology can be requested directly.

Selected project evidence

  • PsychApp v0.2: research-only longitudinal mental-health POC with participant and professional views, agent contracts, model-service architecture, synthetic data and clinician-supervised safety boundaries.
  • Domain Mail v1.2: Flask webmail evolution from IMAP/SMTP implementation to a synthetic public showcase separated from live credential handling.
  • Pharmacovigilance Workbench: public openFDA exploration, local CSV analysis and ROR/PRR screening separated from restricted authorized data access.
  • bfab.io v2: employer-facing information architecture, versioned technical writing, security hardening and production-to-repository discrepancy auditing.

Demonstrated technologies

Technologies listed here are visible in the linked repositories; no proficiency rating is implied.

  • React, Vite, TypeScript and browser JavaScript.
  • Node.js, Python, Flask, FastAPI and REST-style APIs.
  • Supabase Postgres, RLS concepts and Edge Functions.
  • Render, GitHub Pages, GitHub Actions and Docker-oriented deployment.
  • IMAP, SMTP, TLS, CORS, CSRF, CSP and fixed-origin proxy controls.
  • Clinical safety framing, pharmacovigilance screening and synthetic-data demonstrations.

Working principles

  • Define the clinical and product boundary before adding automation.
  • Build a narrow vertical slice across interface, API, data and deployment.
  • Use live discrepancies as evidence and document unresolved state.
  • Keep uncertain outputs reviewable and separate signals from causality.
  • Prefer safe public showcases over demonstrations that require real credentials.

Availability and contact

For hiring conversations, collaborations or technical discussion about digital health and responsible clinical software: requests@bfab.io.