Enter the access code to open the HIS Implementation Action Plan.
Comprehensive implementation roadmap for a fully integrated Health Information System — Al-Faraby Medical Complex
Phase 3 (26 Oct → 31 Dec) owns core-system UAT, defect closure and launch readiness. Phase 4 (from 9 Nov) builds patient-facing tracks in parallel and does not block core UAT. Critical path to live ops: Phase 1 → Phase 2 → Phase 3 readiness → 1 Jan 2027. Phase 4 tracks must be trial-ready by mid-December training, but clinic live operations do not wait on every Phase 4 polish item.
1) Staff training (1–19 Dec) — first three weeks, non-negotiable for go-live readiness. 2) Final trials & P0/P1 defect closure (7–26 Dec) — runs alongside training without cancelling sessions. 3) Pre-launch checklist (20–31 Dec) — cut-over plan, go/no-go. Live clinic operations start 1 Jan 2027 — December is training + trials, not full production go-live.
A 2-week contingency buffer is reserved after Phase 2 / inside early Phase 3 (use preferentially 26 Oct → 8 Nov) for NPHIES credential delays, migration rework or critical UAT findings. Consuming the buffer may compress Phase 3 UAT windows but does not move the 1 Jan 2027 live-ops target unless jointly approved in writing by Al-Faraby and Thirty Eight Technology. Hard dependencies (NPHIES provider credentials, Nafath SP access) must still be delivered by the client on time.
The full delivery scope below covers every module in the contract plus all required external integrations. Each item is built and signed off across Phases 1–4.
All 17 contracted scope items above are scheduled across Phases 1–4: operational modules & e-invoicing in Phase 1, NPHIES + RASAD in Phase 2, UAT/training in Phase 3–December, and Patient Portal / Homecare / Telemedicine / Mobile App in Phase 4 — with live operations from 1 Jan 2027.
Deliver a fully functional first version of the HIS platform covering all contracted modules — with complete UI screens, workflows, and data structure. No NPHIES or external platform integration in this phase. Client signs off on all screens and workflows before Phase 2 begins.
All contracted operational modules (incl. native pharmacy & warehouse) operational in staging
Staging URLPostgreSQL HA Cluster, Redis, Queue workers, Backup strategy active
Saudi CloudFormal sign-off on all workflows and screen specifications
Approved DocAll roles configured with correct permissions for Al-Faraby team
Roles ReadyInvoice types (Insurance, Cash Saudi, Direct Company) matching Al-Faraby format
ZATCA CompliantDatabase schema, integration list, operational reports, process documents
v1 DocsFormal agreement on which datasets are migrated and which start fresh
DM.1 · JunLegacy field → HIS field mapping with cleansing rules for each dataset
DM.2 · JunExtraction, transformation and load scripts stored in the project repository
DM.3 · JulFormal written approval from Al-Faraby that staging data is accurate and complete
DM.5 · SepRecord count verification report confirming production data matches approved staging load
DM.6 · NovRegister at portal.nphies.sa as a healthcare provider. Obtain: (1) Provider ID, (2) OAuth 2.0 Client ID, (3) Client Secret, (4) Token Endpoint URL, (5) NPHIES Payer Code for each insurance company. This is free of charge but requires CCHI approval. Process takes 1–3 weeks. Start this in Week 1 of Phase 1.
All transaction types tested and validated in NPHIES sandbox
FHIR R4Invoice types with QR codes matching Al-Faraby reference format
ZATCASFDA controlled substance tracking and reporting enabled
SFDAAll active integrations documented with endpoints and credentials reference
Docs v2Validate the core HIS through Integration Testing and User Acceptance Testing (UAT) with Al-Faraby clinical and administrative staff. Close P0/P1 defects. Complete staff training in December (see Training Plan). Finalize production cut-over readiness. Live clinic operations target: Friday 1 January 2027 — not a December go-live. Phase 4 patient-facing tracks run in parallel from November and do not replace core UAT.
Phase 3 closes with testing, UAT and launch readiness. Actual production operations start at the beginning of 2027 (target: Friday 1 January 2027), after December training and final trials.
Deliver the patient-facing digital experience: a native iOS & Android mobile application, a full Telemedicine capability built directly on Al-Faraby's Telemedicine Technical Framework, a complete Homecare workflow that digitizes the official Home Care Service Flow Chart and forms (Initial Assessment, Follow-Up Appointments, Home Visit Log), and integration with the Saudi National Login (Nafath) platform for unified patient and provider authentication. Phase 4 runs in parallel with Phase 3 from 9 Nov (Nafath Track D: 2–24 Nov). It does not gate core UAT. December priority: (1) staff training 1–19 Dec, (2) final trials & defect closure, (3) pre-launch checklist. Live / production operations: Friday 1 January 2027.
Telemedicine is implemented as a "Virtual Visit" encounter type within the EMR — not a separate system — so scheduling, documentation, prescribing, billing and reporting all reuse the existing HIS workflows. The tasks below directly mirror sections 3, 4 and 5 of the framework document (Telemedicine Services, Clinical Workflow, and Security/Privacy).
The tasks below digitize Al-Faraby's existing home-care workflow exactly as documented: Referral → Initial Screening & Eligibility → Consent + Policy Agreement + Assessment Fee → Initial Home Visit Assessment → Care Plan → Follow-Up Visits + Home Visit Log → Discharge Summary & Final Bill. Each paper form (Initial Client Assessment, Follow-Up Appointments, Home Visit Log) becomes a structured digital screen tied to the patient EMR.
Apply for Nafath (National Single Sign-On) Service Provider access via the National Information Center / Absher Business portal. Obtain: (1) Service Provider ID, (2) OAuth 2.0 Client ID & Secret, (3) Authorized callback / redirect URIs, (4) Approved scopes (identity, basic profile). Provide credentials to Thirty Eight Technology before 2 Nov 2026 (Day 1 of Track D, aligned with Phase 4 parallel start).
Published on App Store & Google Play. Full appointment, results, prescription, payment & insurance card features.
ProductionVideo consultation integrated with EMR, e-prescription & NPHIES billing. MOH-compliant consent flow.
LiveScheduling dashboard, field-nurse mobile app, visit documentation, billing & insurance claims active.
OperationalOIDC connector live in production for both patients and staff. Strong-identity verification across web & mobile.
National SSOPatient-app onboarding video, TeleVisit doctor guide, Homecare nurse SOP, Nafath login FAQ.
Docs v3App downloads, active users, TeleVisits/day, Homecare visits/day, Nafath login success rate.
KPIsSingle entry/exit point for every external interaction. Built on a pluggable adapter pattern — one adapter per external system or protocol. Every message is normalized, validated, queued, retried and logged before it reaches the HIS or leaves it.
All four mandatory Saudi-Arabia regulatory connections are implemented as dedicated adapters inside the Integration Hub — never as direct calls from clinical or billing modules.
Bidirectional integration with on-site hardware: lab analyzers send results back automatically; imaging modalities push studies to PACS; the HIS receives results & image links and posts them to the encounter and the patient app.
For every HIS module, the table below lists the exact external systems it integrates with. All connections go through the Integration Hub adapters described above — no module talks directly to an external party.
Arabic + RTL is not a separate phase — it is implemented inside every task in Phases 1–4. UAT in Phase 3 explicitly validates Arabic rendering on every screen, every PDF and every notification. The patient mobile app is published to the App Store and Google Play with Arabic as the default language for users with an Arabic device locale.
Training runs in the first three weeks of December 2026 (1–19 Dec), immediately before live operations at the start of 2027. Staff train on the same environment they will use in production. Sessions combine on-site instructor-led training at Al-Faraby Medical Complex with online live sessions for finance, reporting and management. Pharmacy, warehouse and ZATCA workflows are taught as native HIS modules (Odoo is covered only for accounting handoff). Every session is recorded; guides and a video library remain available after go-live.
Hands-on, instructor-led sessions held at Al-Faraby Medical Complex. Clinical and operational staff use the live system on their actual workstations with role-based logins. Ideal for reception, doctors, nurses, lab/radiology technicians, pharmacists, warehouse and cashiers.
Remote live sessions over Microsoft Teams / Zoom for management, finance, insurance, reporting, dashboards and refresher Q&A. Sessions are recorded and uploaded to an internal training library for replay and onboarding new staff after go-live.
Each track ships with a printed quick-reference guide (Arabic + English), short how-to videos, and a final knowledge-check. Trainees who complete their track receive a Certificate of Completion issued by Thirty Eight Technology. Two on-site super-users per department are appointed to support peers post-launch.
After the December program, a floor-walking support team from Thirty Eight Technology stays on-site through late December and the first weeks of January 2027 hyper-care as live operations begin. A dedicated support hotline + Teams channel remains open for instant questions before and after the 1 January 2027 production launch.