The problem — or rather, the problems
When care coordination fails, it's tempting to blame a single cause. In practice, distinct problems overlap. As in most of the country's public networks, they're structural — they don't reflect a lack of effort from those on the front line. MediRec was designed to face them one by one.
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 in 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 is not enough — you need to transform it into a decision. Spread across systems that do not talk, information does not become knowledge: protocols exist, but they remain on paper; requests arrive without structured clinical justification; the queue is ordered by arrival date, not by risk; and the results themselves do not separate themselves into what requires immediate attention and what is just normal. The unique clinical logic that qualifies what comes in, distinguishes what needs action, prioritizes by severity, connects those who decide and ensures that the response returns to those who started the care is missing.
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.
A problem of another order Sovereignty
When a secretariat adopts a system that organizes the health of its entire network, it does not just hire a service — it entrusts the infrastructure of a public policy to a private company. If you never own this technology, dependence only deepens over time: the flows, institutional memory and data that support the care of millions of people start to live in a system that is not yours.
Leaving means starting over and risking continuity of care; staying means paying forever. This isn't a line item — it's a question of who controls the infrastructure of an essential public service. That's why we treat this point as different in nature, not just in degree.
How MediRec responds to this → 
MediRec