Health has a memory. Too often, healthcare does not.

When people move between clinics, hospitals, laboratories, or even cities, important parts of their medical history can be left behind. A test result may live on paper, in a PDF, in a WhatsApp chat, or inside a system that the next provider cannot access. At the next appointment, the conversation begins again: What happened before? Which medicines have you taken? Do you have the result?

The problem is not that clinicians do not care about context. It is that the systems around them rarely allow reliable health information to travel with the person it belongs to.

That is the problem Merdra exists to solve.

Merdra is health-data infrastructure

Merdra is building the trust and interoperability layer that lets medical information follow a patient.

We are not trying to become every hospital's electronic medical-record system, nor are we building another place to upload documents and forget them. We are building the underlying infrastructure that can help laboratories, healthcare providers, patient applications, and future clinical tools work from health information that is structured, permissioned, and trustworthy.

We are also building Merdra so other healthcare startups and developers can build their own applications on it.

In simple terms, Merdra should make it possible for the right health information to be available to the right person or system, at the right time, with the patient's permission.

Why records today are not enough

Most healthcare information is created for a moment: a consultation, a prescription, a test, or a discharge. But a person's health is not a series of isolated moments. It is a continuing story.

When that story is fragmented, every new provider has to reconstruct it. Patients must remember details under pressure, carry documents around, or repeat tests that may already have been done. Providers make decisions with less context than they should have. And valuable information that could support better care stays trapped in formats and systems that cannot easily work together.

The consequences of fragmented history are not abstract. In Medical History, we shared conversations with two doctors on our team about the difficulty of retrieving older records and using information from elsewhere during care.

Digitising a document alone does not solve this. A scanned result is easier to store, but it is still difficult for software and often for another provider to understand, compare, or safely use.

Merdra is being built so health data can be more than a collection of files.

What Merdra makes possible

At its core, Merdra brings together a few things healthcare data needs in order to be useful across systems:

  • Structured information. Important clinical details such as a lab test's name, value, unit, reference range, and date should be represented as data, not just as pixels on a page.
  • Provenance. A record should show where it came from, who created it, and when. That gives the next person or system a basis for understanding whether it can be trusted.
  • Consent and access control. Health information is deeply personal. Patients should be able to understand and control how it is shared, while providers get the information they are authorised to use.
  • Interoperability. Different organisations and applications should not need to start from zero every time they need to work together. With permission, they should be able to exchange relevant information in a reliable way.
  • An audit trail. Access and changes should be accountable. Trust cannot be an afterthought when the data concerns someone's health.

These capabilities may sound technical, but their purpose is human: to give patients continuity, give clinicians context, and make safer, more useful health software possible.

We are starting with lab results

Merdra's first focus is structured diagnostic laboratory results.

Lab results are a practical place to begin because they are important, common, and often difficult to carry from one point of care to another. They also contain the kind of precise information that becomes far more useful when it is structured: a result can be compared over time, interpreted alongside other records, or shared with a new provider without someone having to manually re-enter it.

The first milestone is not to capture every piece of medical information at once. It is to create a trustworthy path for a laboratory result to become a portable, usable record—one a patient can access and share, and one an authorised provider or tool can understand.

From there, Merdra can expand carefully toward a more complete longitudinal health history: medication records, diagnoses, care events, and other information that helps tell the full story.

Trust is the product

Health data is not ordinary data. It can affect a diagnosis, a treatment decision, a person's privacy, and their confidence in the healthcare system.

That means Merdra has to be built around trust from the beginning. Information needs clear provenance. Sharing needs meaningful consent. Access needs accountability. And interoperability cannot come at the cost of patient dignity or security.

The goal is not simply to move more data around. It is to make the data that moves understandable, traceable, and appropriately controlled.

Beyond continuity: building clinical context

Continuity is the first promise, not the final value. A record that can move with a patient is useful; a trustworthy longitudinal history can also help people and software understand what has changed, what may be connected, and what information is still missing.

As Merdra's records become more structured and longitudinal, we can support clinician-facing tools that surface trends over time, relevant medication and diagnostic history, family-health context, and gaps or contradictions in the record. Each signal should make its basis visible: the source records, the dates, the units, and the limits of what is known.

This is not about asking software to make a diagnosis on its own. It is about giving clinicians clearer, source-grounded context so they can apply their judgement. Over time, validated clinical decision-support and preventive tools may be built on this foundation. But trustworthy data, meaningful consent, transparency, and human review have to come first.

Family context deserves particular care. Knowing relevant family history is not the same as having access to another person's private medical record.

Building from Nigeria, with a global ambition

We are starting in Nigeria, where fragmented records, paper workflows, PDFs, and disconnected providers make the need for continuity especially clear. But this is not only a Nigerian problem. Around the world, healthcare is still organised around institutions while people's lives and health needs move across them.

Nigeria is Merdra's beachhead, not its boundary.

We want to prove the model where the problem is real and urgent, learn directly from patients, laboratories, and providers, and build infrastructure strong enough to support healthcare wherever people need their information to move with them.

A foundation for the next generation of care

Better health software and eventually responsible clinical intelligence depends on better underlying information. AI cannot responsibly fill the gaps created by missing, unverified, or disconnected records. It needs data that is structured, longitudinal, permissioned, and traceable.

Merdra is building toward that future, but it begins with a much simpler promise: your health information should not be trapped where it was created.

It should be able to follow you, with context and with your permission.