Join the DHealth Network.
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.
For clinics and hospitals
Create the order once. Follow it across the boundary.
The order a clinician writes is the same object the laboratory accepts, the same object the result attaches to, and the same object the clinician reviews. Nothing is re-typed at a handover.
What a clinic actually does on the network
-
Patient identity that stays yours
Register a patient or find one already in your clinic's directory. Your patient record belongs to your organization; what travels with an order is what the laboratory needs to do the work.
-
Ordering without a second system
Select the diagnostic services from a shared catalogue, on one screen, in French. The order is created once and carries its own identity for the rest of its life.
-
Routing to a laboratory you actually work with
Work goes to laboratories your organization has an established routing relationship with. This is administered deliberately — DHealth is not a price-shopping marketplace a clinician has to navigate during a consultation.
-
Progress you can see without telephoning
Accepted or declined, collected, under way, results entered, released. The clinic sees the state of its own orders rather than calling to ask.
-
Released results, and the version that was released
A clinician sees results when the laboratory has explicitly released them — never a half-entered draft. If the laboratory later issues a correction, it arrives as a new version, labelled as such, alongside the version already reviewed.
-
Review, and a follow-up that is recorded
The reviewing clinician records the follow-up decision against the exact version reviewed. It becomes part of the record, and it is what the patient's status view reflects.
-
Clinic
Registers the patient and creates the order.
Order -
Laboratory
Accepts the work, performs it, releases the result.
Released result -
Clinician
Reviews the released version and records follow-up.
Follow-up -
Patient
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
-
You create the order
Once, as a record — not as a form to be copied later.
-
You write it out for the patient to carry
So it can reach a laboratory in another building.
no longer needed
-
It routes to an authorized laboratory
One your organization has an established relationship with.
-
You telephone to ask whether it is ready
Because nothing tells you, and the patient is waiting.
no longer needed
-
The released result arrives on the order
Attached to the request you made, not to a sheet of paper.
The order is created once, as a record. It carries its own history: who created it, where it was routed, what state it is in, and which released result belongs to it.
What DHealth does not do
DHealth does not interpret results. It does not mark a value normal or abnormal, raise clinical alerts, suggest a diagnosis, or offer decision support of any kind. It records what a laboratory reported and routes it to the clinician entitled to read it. The clinical judgement stays with the clinician.
Already using software?
Then the goal is not to make your staff keep two systems in step by hand. DHealth Connect is the path being designed for that, and it starts with discovering what your system can already talk to.
DHealth is in active development. No facility is live on the network, and nothing here has been used in real patient care.