Skip to content
Dijla Health
An Iraqi laboratory technician working with a modern analyzer beside imaging equipment

For labs & radiology

Verified orders in, validated results out

Every order is anchored to a verified doctor's encounter; every result carries a validated unit and a human release. A separation-of-duty guarantee protects each result from entry to release. Arabic-first, inspection-ready.

3,782 tests · 229 audit event types · FHIR R4 · inspection-ready

Results by chat app, no chain of custody

  • Results are shared as photos of printouts — no units, no reference ranges.

  • Critical values can be received and missed, with no systematic flagging.

  • Radiology reports live in Word docs with no versioning.

  • One person can enter and release a result — nothing separates the two.

  • There's no FHIR interoperability with hospitals or a national registry.

Integrity built into every result

  • Every order is anchored to a verified doctor's clinical encounter — no orphan requests.

  • Every value is UCUM-validated, so results are finally comparable across providers.

  • A rules engine flags abnormal and critical values — it flags, it never diagnoses or releases.

  • The person who enters a result can never release it — enforced at three independent layers.

  • Released results are immutable; corrections are versioned, never silent overwrites.

What you get

From a verified order to a released, exportable result

Upload Result
FHIR R4 · HL7
PDF reports today — DICOM imaging available on request
CBC••••••••Delivered
Chest X-Ray••••Delivered

Encounter-anchored orders, results in-system

Orders are created only from an open clinical encounter — with priority and a bilingual clinical indication. Results return in-system with UCUM reference ranges beside every value, and export cleanly as FHIR R4 for hospital and national-registry integration.

  • No orphan orders — each ties to a verified encounter
  • UCUM units validated at entry — no unitless values
  • FHIR R4 ServiceRequest / DiagnosticReport export
Result · CBC
Potassium
6.4 mmol/L
CRITICAL
Hemoglobin
10.1 g/dL
LOW
WBC
7.2 10⁹/L
NORMAL

Validated results, critical values first

A pure rules engine flags every value against population-matched reference ranges — NORMAL, LOW, HIGH, CRITICAL. Critical results hard-block release until a clinical user acknowledges them, with automated reminders until they do. The engine flags; it never diagnoses.

  • Traffic-light flags on every value
  • Critical values hard-block release until acknowledged
  • Rules engine flags — humans decide
Release · separation of duty
Entered byyou
Acknowledgedcritical
Releasermust differ
Release blocked — a different reviewer must release

Three-layer separation of duty

The person who enters a result can never be the one who releases it — and no AI or system account can release under any circumstances. It's enforced at three independent layers: the permission matrix, the service transaction, and a hard block on automated actors.

  • Enterer ≠ releaser — a hard system rule
  • AI and system accounts can never release
  • Chain of custody survives staff turnover & inspection

A provenance chain for every result

Immutable Audit Log
Patient Consent Enforced
FHIR R4 Compliant
AI assists only — humans approve
Ministry of Health Inspection Ready
3,782
automated tests
34
backend modules
229
audit event types
5
milestones shipped

Questions labs ask

Frequently asked questions

Who can order a lab test or radiology study?

Only verified doctors with an active clinical encounter. Front desk, pharmacists, and administrative users cannot create diagnostic orders — it's enforced at the permission level.

Can we release results without a second reviewer?

No. The person who enters a result cannot be the one who releases it — a hard rule, not a setting. You need at least two credentialed staff in the workflow.

What happens when a result has a critical value?

Release is hard-blocked until a clinical user acknowledges the critical value, and an automated reminder fires until they do. A critical value can't be dismissed silently.

What units does the system accept?

All values use validated UCUM units, checked at entry — an invalid unit is rejected before the result is saved. Every result is comparable and machine-readable.

Can an AI release results automatically?

No. AI never releases results — any release request from an AI or system actor is rejected unconditionally, at three independent layers. AI assists — summarize, score, flag, translate; humans approve. AI never diagnoses, prescribes, approves results, or overrides consent.

How do we integrate with a hospital or national FHIR registry?

Every order exports as a FHIR R4 ServiceRequest, and every released result as a DiagnosticReport with Observation components — standard endpoints ready for any FHIR-compliant system.

Bring your lab or radiology center onto the network

Register your facility and produce results with a full chain of custody from day one.

Register your facility

Questions about integration? Contact us