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.
How it works
Three layers, one transaction.
DHealth is not one program installed at one hospital. It is a network layer, plus two ways for a facility to reach it.
-
DHealth Native
In developmentThe software a facility uses directly
Workflow applications for clinics and laboratories that need one: patients, orders, assigned work, result entry, release, review and follow-up. Everything a facility does here becomes a transaction on the Exchange.
-
DHealth Exchange
In developmentThe network layer
The part that makes a network a network. It holds the organizations and who may send work to whom, where every order stands, which result answers which order, how a result is released and later corrected, and a record of every step behind all of it.
-
DHealth Connect
In designThe integration path for existing systems
How a facility that already runs its own software reaches the same Exchange, through the connections that software already has rather than through typing everything twice.
DHealth Native
In developmentFacilities that use DHealth directly
DHealth Connect
In designFacilities that keep their own system
DHealth Exchange
Organizations · who may send work to whom · where each order stands · which result answers which order · release and correction · a record of every step
Two ways in, one network underneath.
-
The order is a record
Not a form somebody types up later. It exists from the moment it is made.
-
Routing is configured
Which laboratories may receive which work is administered, not arranged by telephone.
-
Release is an act
A named person releases a result. It is not a save, and it is recorded as a decision.
-
The history is written as it happens
Not reconstructed from paper once everyone has gone home.
This is the whole argument. A system where the paperwork is scanned in at the end is a filing cabinet with a screen. A digital process is one where the work and the record are the same thing, and the history is written as it happens.
What the Exchange is responsible for
-
Organizations
Who exists on the network, and who is authorized to act for them.
-
Who may send work to whom
Which clinics may send work to which laboratories. Configured, not open by default.
-
Where each order stands
The same answer for the clinic and the laboratory, at the same moment.
-
Which result answers which order
And which version of that result, when one has been corrected.
-
Release and correction
A result is released deliberately. A correction is a new version, and the earlier one is kept rather than overwritten.
-
A record of every step
What happened, in what order, and on whose authority.
How an order travels.
The same transaction, seen as a relay. Each organization takes it on, does its part, and hands it forward with the state recorded — so nobody has to telephone to find out where it got to.
-
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
One order, carried across organizational boundaries, with every handover recorded.
Deliberate boundaries
- DHealth does not interpret clinical results or provide decision support.
- DHealth is not a national or cross-facility patient search: joining does not let one organization look up another's patients.
- DHealth is not a marketplace. Routing relationships are established between organizations, not bid for per order.
- Patient data is never sent to a third-party AI or machine-learning service.
DHealth is in active development. No facility is live on the network, and nothing here has been used in real patient care.