Hilbi only works if clinical reality fits a clean data model — and that model fits real hospital systems. You own data correctness end to end, from the internal model to the FHIR boundary to the integrations that touch existing AIS/EMR systems and registries.
Research & DevelopmentOpen
Clinical Informatics Engineer
"The structure beneath every care plan. FHIR in, hospitals out."
Why this role matters
What you'll work on
- Turning clinical flows from the Clinical Product Lead into structure: FHIR R4 resources at the API boundary and a clean canonical model behind a FHIR Facade
- Choosing and maintaining terminology bindings — LOINC, SNOMED CT, ICD-10 / MKCH-10, ATC
- Designing reusable archetypes for recurring clinical patterns
- Owning interoperability: HL7 v2, GDT, registry submissions, AIS/EMR integrations across markets
- Defining the boundary between the internal canonical model and the FHIR Facade
- Owning data correctness, idempotency and safe failure handling for every integration
Skills needed
- Software / informatics engineer with hands-on FHIR R4 experience
- Comfortable with healthcare terminologies (LOINC, SNOMED CT, ICD-10 / MKCH-10, ATC)
- Real integration experience (HL7 v2, GDT, registries, AIS/EMR)
- Deep understanding of healthcare data — not required to be a clinician
- Pragmatic, safety-minded engineer who cares about data integrity
- Fluent English
Valuable extras
experience with one or more EU / India / Middle East / US healthcare systemsregistry or public-health reporting experiencebackground in standards work (HL7, IHE)
What we evaluate
- FHIR modeling correctness
- terminology appropriateness
- grasp of the facade pattern
- pragmatic and safe integration design
- data-integrity thinking
The assignment
Practical exercise (~3–4 hours): from a short care plan spec (one graded measure, one diagnosis, one medication, one PRO) — map each item to FHIR R4 resources, choose terminology bindings with rationale, describe the canonical model ↔ FHIR Facade boundary, and sketch ONE integration path (GDT to AIS, HL7 v2, or registry submission) including sequence and failure handling. Submit in your candidate area.
Full brief is shared after a short intro call.