Matheus Krisciumas
ENPT
All work

Refmed · Full-time · Jan 2024 — Dec 2024

Patient referral product, built from scratch

Mobile, web, API, and database for a healthcare referral workflow.

Next.jstRPCPrismaReact NativeFirebase
Refmed web console listing clinic colleagues by specialty, with a Referenciar action and Salvador clinic context.
Operator console: colleagues in the clinic network, by specialty.

The idea

Nothing existed yet. The product had to be the referral workflow itself: two surfaces, one API, payments, and a chat that did not drift between clients.

The situation

Refmed needed a healthcare referral product from zero. Mobile for the people in the flow, a web console for operators, an API, and a database. Payments, messaging, uploads, and chat were not extras—they were how the referral actually moved.

How it works

Build the three surfaces against one contract. React Native for referrals in the field, Next.js for the people who operate the queue, tRPC and Prisma for the model. Chat had to stay in sync, so Firebase sat next to the SQL store instead of pretending SQL was realtime.

PIX, email, WhatsApp, uploads, and analytics plugged into that same path so a referral did not leave the product to complete.

What shipped

The stack went out as one product in 2024, used by two clients, with a SQL model and a realtime channel that did not fight each other.

  1. 01React Native clientreferrals
  2. 02Next.js consoleoperators
  3. 03tRPC + Prisma APISQL model
  4. 04Firebase chatrealtime sync
Clients
2
Payments
PIX
Chat
Firebase

The problem

Nothing existed yet. The product needed payments, messaging, uploads, and a chat that stayed in sync between clients.

What shipped

Shipped React Native, Next.js, and a tRPC/Prisma API, then added PIX, email, WhatsApp, uploads, analytics, and Firebase realtime chat.