A diagnostic network
Clinics order.Laboratories receive and release.Clinicians review.Patients stay informed.
Today the order is a piece of paper and the record is typed in afterwards. DHealth makes the process itself digital, across organizations that do not share the same software.
In development, starting in Djibouti.
Clinic
Registers the patient and creates the order.
OrderLaboratory
Accepts the work, performs it, releases the result.
Released resultClinician
Reviews the released version and records follow-up.
Follow-upPatient
Sees where the order stands and what happens next.
DHealth Exchange where the work goes · where it stands · which result answers which order · release · a record of every step
One order, carried across organizational boundaries, with every handover recorded.
The problem
A patient sees her doctor, who decides she needs lab work. She is handed a printed order and sent to a laboratory somewhere else in the city. She gives her sample. She is told to come back the next day to collect the result, and she does. Then she books another appointment, because her doctor does not have that result — she is carrying it.
He reads it in front of her, from the paper in her hand. Afterwards, someone at the desk types it into a computer. The record of what happened is created last, by hand, once everybody is already finished with it.
When the patient carries the paper
4 journeys for the patient two of them only to move paper
Her doctor orders the tests
She goes to the laboratory
She returns for the printed result
She books a visit to hand it over
Her doctor reads the result
Someone types it in afterwards
She gives the sample once. She travels four times, and twice only to move a result from one building to another.
With the DHealth Exchange
2 journeys for the patient both of them for care
Her doctor orders the tests
She goes to the laboratory
She returns for the printed result
no longer needed
She books a visit to hand it over
no longer needed
Her doctor reads the result
Someone types it in afterwards
no longer needed
The order reaches the laboratory before she does, and the result reaches her doctor when the laboratory releases it.
The same tests, ordered on the same morning. DHealth does not make a laboratory faster. It removes the journeys whose only purpose was carrying the result.
Two of those four journeys were care. The other two existed only to move a result from one building to another. The process was never digital — a record of it was typed up at the end, once everybody had already finished.
The network
The DHealth Exchange is the layer that holds a diagnostic transaction together while it moves between organizations: who may route work to whom, what state the order is in, which result belongs to which order, and what was released when.
A clinic sends work to laboratories it has an established relationship with. Routing relationships are explicit and administered, not an open marketplace a clinician has to shop in mid-consultation.
Accepted, collected, under way, entered, released, reviewed. Each organization sees the same transaction, described the same way, without telephoning to ask.
Every release is bound to the exact set of results it contained. A later correction becomes a new, clearly-labelled version rather than quietly overwriting what a clinician already acted on.
One network, two ways to join
A facility should never have to run the same diagnostic transaction twice by hand. Which path fits depends on what you already have.
Need software?
For clinics and laboratories that need a workflow system. Staff work directly in DHealth: registering patients, creating orders, receiving assigned work, entering results, and releasing them under explicit authority.
The clinic, laboratory and patient surfaces are built and under test. They have not yet been deployed to a facility.
Explore DHealth NativeAlready have software?
The integration path for organizations that already run their own software. Connect is being designed so an existing system joins the network through the connections it already has, instead of asking staff to keep the same work up to date in two places.
Connect is in design. Connector availability depends on the specific software and interfaces a facility runs, and requires technical discovery before any production integration.
Learn about DHealth ConnectThe diagnostic journey
This is the workflow the Exchange models. Each step is a recorded fact, held against one order, visible to the organizations entitled to see it.
The clinic registers a new patient or finds an existing one in its own directory.
A clinician selects the diagnostic services required, once.
The order goes to a laboratory the clinic is authorized to send work to.
The laboratory takes the work on, or declines it — and the clinic learns which, without a phone call.
The sample is collected. That is a step of its own, not an assumption folded into another one.
The laboratory records that the analysis is under way.
A technician enters structured results. Entered is not the same thing as released.
Someone with release authority releases the results explicitly. That act creates the version a clinician will see.
The ordering clinician reviews the released version and records the follow-up. The patient is told where things stand.
DHealth records and routes. It does not interpret results, flag them, or offer clinical decision support.
Two sides of the same order
Clinics and hospitals
Laboratories
Built for organizations, not silos
One laboratory can serve many clinics. Joining the same network does not merge them into one pool of patients: each organization remains a separate organization, and access follows the transactions it is actually party to.
A clinic sees the orders it placed. A laboratory sees the work assigned to it, with the patient detail that work requires and no more. Two clinics sending work to the same laboratory do not thereby gain any view of each other.
DHealth is a diagnostic network. It is deliberately not designed to become an unrestricted lifelong medical record simply because diagnostics pass through it.
DHealth Exchange
No view between clinics
A laboratory can serve many clinics. The clinics remain separate organizations.
For patients
In development
A patient does not need a staff login, a smartphone habit, or a digital-literacy course to know where their test stands. A clinic can hand out a secure link or a printed code scoped to one order, which shows the status of that order and what to do next.
How the patient view worksHow facilities join
DHealth is onboarding-driven. There is no sign-up form that turns a stranger into a live facility on a clinical network, and there should not be.
Tell us what your organization does and what you run today.
We confirm the facility and the people authorized to act for it.
The organization is established on the network with its roles and relationships.
Either your staff work in DHealth, or we begin technical discovery on your existing system.
Synthetic transactions end to end, before anything real is routed.
Only once the facility, and DHealth, are satisfied it is ready.
If you run a clinic, a hospital, a laboratory, or the software one of them depends on, we would like to talk. Early participants shape what this network becomes.
We will tell you plainly what is built, what is still in development, and what your facility would be taking on. Nothing on this site describes a product in clinical use.