Kickoff 19 July 2026 · Status as of 21 July 2026 · ONA → Staging → Production
OCN / NPHIES IntegrationObeid Group of Specialized Hospitals
NPHIES integration with Lean / CHI across three branches — Riyadh, Al Hamra (Jeddah) and Al Ahsa.
Programme day
3of 36 planned
Since the 19 Jul kickoff
Hospitals active
2of 3 branches
Riyadh & Al Hamra in parallel · Al Ahsa awaiting scope
ONA use cases started
1of 8
Riyadh — ADT in progress
Open ADT items — Riyadh
4 / 1OSH / Cloudtech
OSH is testing the remaining events · Cloudtech items are extra help
7 open items below
The 36-day plan, per branch
ONA → Staging → Production · 12 days eachHow many days each stage should take. The striped block is work the hospital does. Its width is only an example, not real days.
ONA use cases — Riyadh
12 days plannedSolid bars are the planned days. Striped bars are the real days the hospital spent building it.
Who does what next
ADT session · 21 Jul 2026The integration guide already covers every case and field. The Cloudtech items are extra help we are checking on, and we will share them as they are ready. Nothing here stops the hospital from moving ahead.
- Test the remaining ADT eventsUsing the existing guide and samples, development in parallel.
- Build ward-to-ward transfer (A02)Transfer development sits on the HIS side.
- Finalise the .NET pipelineTidy and complete the working submission pipeline.
- Show the NPHIES clinical summary to doctorsRender the link from the SSO response. Meeting 22 Jul.
- Unified JSON per ADT event — shared ✓One merged structure per event, cases A, B and C together.
- HL7 formats for all ADT events — shared ✓Delivered, including ward transfer. A02 build sits on the HIS side.
- Log the dashboard AA / AR enhancementDownloadable logs remain available meanwhile.
The full plan
Every task and its planned duration, from the Development Plan v2 · Riyadh status shown
| Phase | Task | Standard | Planned | Hospital days | Riyadh status |
|---|---|---|---|---|---|
| ONA · 12d | SSO (SAML)The hospital's issuer name is registered with Lean and a signed sign-on request is accepted by NPHIES. Everything else runs under it, including the patient and provider registries, and doctors reach the NPHIES clinical summary through it. | SAML 2.0 | prereq | — | Reported complete |
| Registries — patient & provider (Health ID)Health ID and practitioner data retrieved through OCN, with token and keys confirmed working. Runs under SSO. | REST / OAuth | 1 d | — | Reported complete | |
| ADT (encounter)All ADT cases pass in HL7 format, in the required sequence (for example A04 → A01 → A11). | HL7 v2.x | 3 d | 1 d | In progress | |
| Medication — Prescribe (Raqeeb & Non-Raqeeb)All prescribe cases pass in FHIR format, including Raqeeb-controlled medications. | FHIR | 1 d | — | Not started | |
| Medication — Dispense (Raqeeb & Non-Raqeeb)All dispense cases pass in FHIR format, including narcotics and split-dose scenarios. | FHIR | 1 d | — | Not started | |
| Lab — Order & ResultAll lab order and result cases pass in FHIR format. | FHIR | 2 d | — | Not started | |
| Radiology — Order & ResultAll radiology order and result cases pass in FHIR format. | FHIR | 2 d | — | Not started | |
| Clinical Notes / SummariesAll summary cases pass in XML format, with codes mapped by the hospital's doctors. | XML | 2 d | — | Not started | |
| Total | ONA stage | 12 d | TBD | ||
These days do not include the work the hospital does in its own system.
Timeline since kickoff
Milestones completed, by dateOne area per branch. The shaded band is the hospital build, from 20 Jul 2026. Click any point to open that branch below.
Detail by branchObeid Group · 3 branches
Where each branch is, what is open, and who does the next step.
Obeid Specialized Hospital, Riyadh
CHI 1088- HIS stack
- Oracle-based HIS with a .NET integration layer
- Integration approach
- HIS → OCN via custom JSON development
- NPHIES issuer
- TBD — not yet issued
Pipeline — click a stage to see its use-case statuses
Under way since the 19 Jul kickoff. OSH's automated .NET pipeline passed a live A04 end to end on 21 Jul with an AA acknowledgment from NPHIES. OSH is now testing the remaining events and building ward-to-ward transfer (A02) using the existing guide and samples. Cloudtech is checking on some extra help to make that faster.
Test the remaining ADT events
OSH is working through the remaining events using the existing guide and samples, with development running in parallel.
Build ward-to-ward transfer (A02)
Cloudtech has shared the HL7 formats for all ADT events, including ward transfer. The A02 build itself sits on the HIS side.
Finalise and clean up the .NET pipeline
The pipeline already submits ADT successfully end to end. Remaining work is tidying and finalising on the OSH side.
SSO — show the NPHIES clinical summary to doctors
The SSO success response carries a link to the NPHIES clinical summary, which the HIS saves and renders so doctors can view patient data. OSH does not have this in their UI yet. Meeting set for 22 Jul.
NPHIES ack status (AA / AR) on the OCN dashboard
Logged as an enhancement request so outcomes are visible at a glance. Downloadable logs remain available in the meantime.
▸ Read full status▾ Hide full status
Kicked off 19 July and submitting ADT within two days. On 21 July OSH demonstrated a live A04 end to end through their own automated .NET pipeline — HTTP 200 from OCN and an AA acknowledgment from NPHIES. A01, A03 and A04 are prepared; OSH is now testing the remaining events and building ward-to-ward transfer (A02) on the HIS side, using the existing integration guide and samples. Cloudtech is checking on some extra help alongside this. The registered organisation ID must be confirmed with Lean before staging.
Al Hamra Hospital, Jeddah
CHI 1114- HIS stack
- Oracle-based HIS with a .NET integration layer
- Integration approach
- HIS → OCN via custom JSON development
- NPHIES issuer
- TBD — not yet issued
Pipeline — click a stage to see its use-case statuses
Running in parallel with Riyadh, as set out in the development plan. Same OSH technical team, same Oracle HIS and .NET integration layer, so the ADT pipeline and integration guide carry across directly.
Test the ADT events for Al Hamra
Running in parallel with Riyadh on the shared ADT pipeline and integration guide.
▸ Read full status▾ Hide full status
Al Hamra Hospital (CHI 1114) is running in parallel with Riyadh, as set out in the development plan. The same OSH technical team, Oracle HIS and .NET integration layer serve both branches, so the ADT pipeline, JSON template and integration guide carry across directly rather than being rebuilt. It follows the same twelve-day ONA path.
Obeid Specialized Hospital, Al Ahsa
CHI 1144- HIS stack
- Oracle-based HIS with a .NET integration layer
- Integration approach
- HIS → OCN via custom JSON development
- NPHIES issuer
- TBD — not yet issued
Pipeline — click a stage to see its use-case statuses
Pending scope with Lean/CHI. The scope and issuer-name requests went to CHI on 20 Jul and a reply is awaited. ONA starts once Lean completes the issuer name and IP whitelisting.
Add Al Ahsa to scope & issue its SSO issuer name
The issuer name is the branch's SSO identity, so everything else follows it. Requested from CHI on 20 Jul; a reply is awaited.
▸ Read full status▾ Hide full status
Al Ahsa (CHI 1144) is pending scope with Lean/CHI. On 20 July, following Atif Ahsan's coordination with Ms. Najla Almuhaideb, Dr. Pathan emailed CHI to add the third branch to scope and to request its issuer name; a reply is awaited. The issuer name is the branch's SSO identity, so everything else follows it. Al Ahsa joins the same track once that setup is done.