MediRec
Living custody
The code is not kept in a sealed vault no one can inspect. It lives in a shared, continuously updated repository that the municipality can verify at any time. Custody you can see is custody that counts.
Ownership · Public health
In the end, the technology can stay with the municipality.
In public health software, the norm is to rent forever. MediRec offers a simple, predictable path for the network to own its own technology — without giving up the ready-to-use product it already relies on.
Why this almost never happens
Almost every health system runs on perpetual monthly fees. The customer rents, operates, depends on it — and never receives the code.
The market rule
For the market, dependence is revenue.
Opening a path to ownership would run against the very revenue stream of those who sell it. That is why autonomy rarely makes it into the contract — and the corner of the map where it would exist remains almost empty.
The answer
Autonomy is written into the contract.
The Technology Ownership Program reverses the logic without giving up what works. The network keeps using a ready, managed and evolving product — while progressing toward a perpetual license of use, with the code held in continuous, verifiable custody.
It is not a promise for the end of the contract: it is a right built from day one.
From day one to the finish
Ownership is not an isolated event at the end of the contract — it is a path that starts on day one and ends with the code in the hands of the network.
- 01
From day one
Code in custody
The municipality follows the repository in read-only mode, always updated and verifiable. - 02
An intermediate milestone
The right is established
From a defined point in the contract, ownership becomes a guaranteed right — including in case of early exit. - 03
At the end
Ownership of use
The source code and binaries pass into the network's hands, with a perpetual license of use. - 04
Afterwards
Real autonomy
The network operates independently or continues with 2BLP — the municipality gets to choose.
How it works, without fine print
The mechanism is designed so that autonomy is real and actionable — not decorative contract language.
Two paths, one direction
There is more than one way to get there: one predictable and gradual, another with a guaranteed exit from a defined point. The pace changes; the destination is the same — ownership.
Real safeguards
Autonomy cannot depend on goodwill. If the supplier disappears or maintenance stops, the municipality's access automatically rises to full ownership. The right is actionable, not symbolic.
Knowledge transfer
Receiving the code is not enough; the network must know how to operate it. Near the end, a network developer joins MediRec engineering and learns the platform from within. On transfer day, autonomy is real.
Each side keeps what makes sense
The network gains autonomy; 2BLP continues evolving the product. None of this locks in the municipality — and that is the difference.
The municipality keeps
Perpetual use of the platform · source code in hand · operational autonomy for the network — to run its own network, not to resell or transfer it. It is an open condition: the parties may review it together at any point in the contract.
2BLP retains
The technology's intellectual property, which remains available to other networks — keeping the product in continuous evolution for all of them.
The part nobody believes
Public ownership of software may sound impossible. It isn't.
The path exists, is in the contract and is simple to follow: use it today, verify it always and — at the right time — become the owner. Instead of dependence, the network builds public assets.
Autonomy is not a promise. It is a clause.
Autonomy that becomes public assets.
It already works, connects everything, is intelligent, was built with the front line — and, in the end, stays with the municipality.
Talk to the team →