Managing Incompatible FHIR Implementation Guides in a Single Backend: Namespace-Based Storage in Neo4j and Multi-Profile Delivery...20th Health Informatics Meets Digital Health Conference, May 12–13, 2026, Vienna, Austria.
Achieving interoperability with HL7 FHIR in practice requires creating a FHIR Implementation Guide (IG). Between the many IGs at international, national, and local levels, incompatibilities are inevitable. For example, one IG requiring a field to be filled in while another explicitly forbids it. The...
| Publicado en: | Studies in Health Technology & Informatics Vol. 335; pp. 203 - 210 |
|---|---|
| Autores principales: | , , |
| Formato: | proceedings research tables/charts Journal Article |
| Publicado: |
Sage Publications Inc.
2026
|
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=ccm&AN=193648547&site=ehost-live header: @attributes: shortDbName: ccm uiTerm: 193648547 longDbName: CINAHL Complete uiTag: AN controlInfo: bkinfo: dissinfo: jinfo: jid: 09269630 U1V jtl: Studies in Health Technology & Informatics issn: 09269630 maglogo: N pubinfo: dt: 2026 vid: 335 pid: 344 pub: Sage Publications Inc. place: Thousand Oaks, California artinfo: ui: 193648547 193648547 193648547 10.3233/SHTI260085 193648547 ppf: 203 ppct: 7 formats: tig: atl: Managing Incompatible FHIR Implementation Guides in a Single Backend: Namespace-Based Storage in Neo4j and Multi-Profile Delivery...20th Health Informatics Meets Digital Health Conference, May 12–13, 2026, Vienna, Austria. aug: au: KRAUSS, Oliver POINTNER, Andreas PRASCHL, Christoph affil: University of Applied Sciences Upper Austria, Campus Hagenberg, Softwarepark 11, 4232 Hagenberg, Austria sug: subj: Health Information Management Database Management Software Electronic Data Interchange Information Storage Congresses and Conferences Austria Austria Comparative Studies Conflict (Psychology) Electronic Health Records Implementation Science Data Management ab: Achieving interoperability with HL7 FHIR in practice requires creating a FHIR Implementation Guide (IG). Between the many IGs at international, national, and local levels, incompatibilities are inevitable. For example, one IG requiring a field to be filled in while another explicitly forbids it. The same application, such as a FHIR server or FHIR facade, must then handle inherently incompatible resource structures. We use Germany as a real-world failure case: three competing IGs (basisprofile-de, KBV-Basis-Profile, and ISiK), which were not aligned during development, have become mandatory; many organizations must implement all three for the same patient. We systematically compare KBV Base 1.x and ISiK Basismodul v2, identifying hard structural conflicts including closed versus open slicing on Condition.onset[x] and disjoint address and name type constraints on Patient, Practitioner, and RelatedPerson. We show one possible technical response: we cannot resolve the fact that FHIR disallows one resource from conforming to all three IGs at once, but our namespace-based data management in Neo4j is designed to allow storing data without redundancy and delivering the same patient in three different formats depending on which profile the client requests. Future work includes integrating this model with FHIR profile comparison tooling, evaluating performance at scale, and aligning with HL7 Europe EHDS implementation guides as they mature. pubtype: Academic Journal doctype: proceedings research tables/charts Journal Article ougenre: Article language: English refInfo: holdings: @attributes: islocal: N |
|---|