Brazilian Physician · CRM-ES 21188 · Emergency & Acute Care · Court-Appointed Medical Expert
Building clinical, operational and medico-legal systems from real-world workflows.
I am a Brazilian physician (CRM-ES 21188) working in emergency care and as a court-appointed medical expert.
I build software around problems I have actually met in clinical and medico-legal work.
That usually means starting with the workflow itself: what happened, what is known, what is still uncertain, what needs a source, and what the software must never invent.
Real workflow → clear rules → usable software.
| Project | Why I built it | What is in the repo |
|---|---|---|
| Quem Votar? | Build a public civic-data product for factual candidate research, with traceable sources and explicit review gates. | Python · JavaScript · data pipeline · GitHub Actions · auditability · governance |
| ZeraPS | Emergency documentation for a high-volume PS without losing chronology or inventing findings. | JavaScript · PWA · temporal states · automated tests · CI |
| Kit do Perito | Bring calculations and references I already used in medical expertise into one practical web tool. | JavaScript · Balthazard · AIPE/Brasil · automated tests · GitHub Actions |
| VoeTupper | Replace part of a distributed sales operation built around spreadsheets with a usable system. | Next.js · React · TypeScript · Supabase · Zod · Vitest |
| AuditorES | Organize healthcare audit data and surface what deserves human review. | JavaScript · Chart.js · structured data · decision-support UI |
| EcoMaster Pro | Turn echocardiography references into a faster study and consultation interface. | JavaScript · structured clinical references · clinical UX |
| Joyce · Estudos | Track residency-exam errors and review what actually needs to be studied again. | JavaScript · JSON · analytics · rule engine · Node.js tests |
The projects are different, but they all started with a workflow I wanted to make clearer or faster.
Quem Votar? · ZeraPS · Kit do Perito · VoeTupper V3 · AuditorES · EcoMaster Pro
These are small rules, but they matter in clinical software:
missing data ≠ negative finding
template ≠ performed examination
suggestion ≠ clinical fact
evidence ≠ conclusion
new information ≠ old state rewritten
automation ≠ authority
I care about speed, but not at the cost of turning uncertainty into a false fact.
Technologies used in the projects above.
LANGUAGES Python · JavaScript · TypeScript · HTML · CSS
FRONTEND React · Next.js · responsive web · PWA
DATA / BACKEND data pipelines · Supabase · JSON domain models · schema validation with Zod
QUALITY Vitest · Node.js test runner · type checking · GitHub Actions CI · CodeQL
VISUALIZATION Chart.js
ENGINEERING domain modeling · state/workflow design · authorization · safety-by-design
I am currently interested in:
- clinical workflow and documentation;
- healthtech product development;
- professional workflow automation;
- medico-legal technology;
- healthcare operations and decision support;
- tools that return professional attention to the work that actually requires judgment.
I like software that removes repetitive work without pretending to replace professional judgment.
I am interested in conversations around digital health, clinical software, healthcare operations, medico-legal technology and physician-led product development.
LinkedIn: linkedin.com/in/drajoyceradis
Website: drajoyceradis.com
Email: contato@drajoyceradis.com
Public repositories are portfolio, evaluation and demonstration projects. Project-specific licensing, privacy and security terms apply.