Care doesn't fail for lack of a system. It fails in the spaces between them.

1. Knowing what belongs to whom

Before organizing any flow, there's a basic question: who does each piece of data belong to? Every exam, every report, every result must be assigned to the right patient — and a person's results gathered into one coherent whole. But each system identifies the patient its own way (name, CNS, CPF, address), and a single differently-typed name or a missing CNS is enough to scatter one person's results. Without reliable attribution, the complete picture of each patient never forms — and everything else depends on that picture.

2. Living with many systems

A network professional moves through several systems in a single appointment, each with its own login, interface and logic. The same data is retyped at every step; work is duplicated; context is lost between screens. Much of the information still travels manually and incompletely, and no tool brings these processes into one place.

3. Making sense of the information

Gathering and attributing data isn't enough — it has to become a decision. Scattered across systems that don't talk, information doesn't become knowledge: protocols exist but stay on paper; requests arrive without structured clinical justification; the queue is ordered by arrival date, not risk; and the results themselves don't sort into what needs immediate attention versus what's merely normal. What's missing is the single clinical logic that qualifies what comes in, distinguishes what needs action, prioritizes by severity, connects the decision-makers and ensures the answer returns to whoever started the care.

All three are problems of clinical coordination — serious, but operational: they're born in the space between systems, and that's where MediRec acts. There is, however, a fourth problem of another order.

MediRec's greatest strength isn't the technology itself, but what it enables: turning a human process — made of steps, decisions and back-and-forth — into a bespoke digital process, shaped to the reality of those who use it.

That's how the clinical protocols defined by the Ministry of Health come to life. Instead of sitting in a document few consult, they operate inside the work: guiding the request as it's created and supporting the professional during the consultation. What the norm defines, MediRec applies in the flow — with the decision always validated by a human.

This design is never generic. MediRec's request flow was born from a concrete clinical need of our Medical Director, Dr. Luana Moussallem, and was refined and adapted to the reality of the network as we reached each unit. Every adjustment came from real use, not from a drawing board.

The DNA-HPV flow shows the leap this represents. Where before you had to open two separate requisitions — one in GAL and another in SISCAN, across two distinct, unfriendly systems — MediRec does both at once, in a single action. A process that took time and created rework became one click.

MediRec is developed by 2BLP Futuro Ltda., which brings together Dr. Luana Moussallem (Medical Director), Matthias Hasler (CTO and Data Protection Officer) and Tarek Nabaa. The first module was born from Dr. Luana's own routine, then a doctor leading a Family Clinic team. It was conceived from inside the system — not commissioned from outside.

The method hasn't changed since. A concrete care problem becomes a flow, takes shape and is tested in the field: nothing reaches the network without first proving results in a real unit. Short cycles, always close to the front line.

There are now more than 130 modules, built one by one by the same method, from primary to specialized care — all on a single layer that connects to existing systems and organizes them into one flow.

Four principles run through MediRec: complementarity, human decision over AI, protected data on national territory, and the network's autonomy over its own technology. In the end, it all serves one goal: organize the network to give time back to those who care — and to those who are cared for.