Role Summary
Expertise in the Saudi national healthcare data layer. This engineering role understands the NPHIES exchange and the HL7 FHIR R4 structure deeply—what each bundle contains, how the resources relate, and how to transform that data into clean, correct, model-ready tables in a data warehouse.
This is a hands-on build role with a domain core expertise. Experience with cloud providers such as GCP or AWS is required. This role is embedded with the wider data engineering team; you bring genuine, production NPHIES/FHIR expertise and the judgement to map Saudi national health data correctly.
This is a forward-deployed (FDE) role based on-site in Saudi Arabia.
What You'll Do
- Design and build the ingestion pipelines that pull NPHIES claims data (FHIR R4, JSON/XML bundles) and flatten it into structured data warehouse tables: claim lines, diagnoses, procedures, providers—preserving clinical and billing meaning through every transformation.
- Define the FHIR-to-table mapping and run validation to ensure data correctness.
- Reconcile provider and physician identity across Saudi national systems, matching NPHIES provider IDs against SCFHS license data to produce a trusted, deduplicated provider layer for downstream detection.
- Handle the realities of real-world health data: malformed bundles, validation failures, dead-lettering, reconciliation checks, and partition/freshness assertions before data is promoted for use.
- Ensure outputs and codes stay aligned with the NPHIES standard, including mapping detection results to NPHIES denial codes for claim resubmission (English and Arabic).
- Integrate supporting claims and TPA data sources alongside NPHIES, applying consistent PHI tokenization and data-residency controls.
- Contribute to building and documenting data-quality monitoring (freshness, completeness, reconciliation variance) for the health data pipelines.
- Ensure proper documentation and knowledge transfer of all work, including architecture diagrams, code, operational procedures, and troubleshooting guides.
Required Expertise & Skills
The following are non-negotiable. All must be demonstrated through verifiable production experience.
- Hands-on, production experience with NPHIES, the Saudi National Platform for Health Information Exchange. This is the hard requirement; generic FHIR experience alone is not sufficient.
- Deep understanding of HL7 FHIR R4 resource models, profiles, bundle structures, claim/encounter/practitioner resources, and the practicalities of parsing and flattening them at scale.
- Strong data engineering experience designing and operating ingestion and transformation pipelines: SQL, Python/PySpark, partitioning, incremental processing, orchestration, and pipeline monitoring.
- Healthcare claims data fluency, with an understanding of how claims, diagnoses, procedures, and provider identity are represented, and what "correct" looks like in a Saudi payer context.
- Provider/entity resolution and record linkage across systems with no shared key, combining deterministic matching (e.g. SCFHS licence) with fuzzy matching. Understanding and experience is a plus.
- Handling PHI under strict data-residency and privacy constraints: tokenization, encryption, access controls, and working within PDPL/NDMO obligations. Saudi data compliance knowledge is a must.
- Comfort working with Arabic-language healthcare data, RTL text, and bilingual code/denial mappings.
Preferred Qualifications
- Cloud data engineering on Google Cloud Platform (BigQuery, Dataform, Dataproc, Cloud Composer, Healthcare API); GCP Professional Data Engineer certification.
- Familiarity with the Saudi health regulatory data ecosystem beyond NPHIES: SCFHS licensing and CCHI coding, bundling, and fee rules.
- Prior delivery inside a Saudi payer, TPA, HIS vendor, or NPHIES integrator.
- Experience with TPA/claims adjudication systems and the end-to-end claims lifecycle.
Location & Eligibility
KSA-based candidates are strongly preferred. The role is on-site and embedded; all data access is in-Kingdom only. Candidates must be eligible to work on-site in Saudi Arabia. Remote access to production health data from outside Saudi Arabia is not permitted.
