Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Objective

Integration of FHIR R4 into the openIMIS FHIR module

Who

Faris Ahmetasevic from University of Basel

Duration

4 months

Starting date: 23.03.2020

Ending date: 22.07.2020

Activities

  1. Become familiar with the existing openIMIS implementation and HL7 FHIR (versions 3 and 4)

  2. Provide a mapping from relevant fields of the most popular and relevant hospital management systems and openIMIS, with focus on the fields and attributes that are so far not yet supported

  3. Integrate support for HL7 FHIR version 4 into openIMIS (back‐end implementation in python)

  4. Develop a tool for the transfer of data from the openIMIS database to a FHIR database through the new developed FHIR version 4.

Discussions

  • Proposal to split the FHIR module per resource and version: FHIR_Claim_V4 module

Api Root

  • Firstly, a new directory ‘api_fhir_R4’ was created, which contained the copied files of the api_fhir module of version 3.

  • These files have been processed in order to create a new api root for the version 4 of the module.

  • After launching the backend server it is now possible to reach the api root for both versions using:

    http://localhost:8000/api_fhir

    / for version 3http

    _r4/

openIMIS FHIR R4 Implementation Guide

https://

...

openimis.github.io/openimis_fhir_r4_

...

Mapping

Overview Table

...

FHIR R4 Resource

...

OpenIMIS database tables

...

notes

...

mapping status

ig/index.html

openIMIS FHIR R4 Profiles

FHIR R4 Resource

openIMIS FHIR R4 Profile

openIMIS database tables

Claim

openIMIS Claim

Request properties are mapped to Claim

mostly mapped

ClaimResponse

ClaimResponse

openIMIS Claim Response

Response properties are mapped to Claim

mostly mapped

Coverage

openIMIS Coverage

tblPolicy

mostly mapped

Patient

openIMIS Patient

tblInsuree

mostly mapped

tblInsurees

Group

openIMIS Group

tblFamilies

Practitioner

openIMIS Claim Administrator Practitioner

tblClaimAdmin

used to represent base fields of Claim

Administrator (without relation with health facility- FHIR R4 Location)

mapped

PractitionerRole

tblClaimAdmin

used to represent a relation between base ClaimAdmin (FHIR R4 Partitioner) and Health facility (FHIR R4 Location)

mapped

Location

  • tblHF

FHIR R4 location.mode field is used to switch between mapping from tblHF and tblLocations

mostly mapped

CoverageEligibilityRequest

CoverageEligibilityRequest

mostly mapped

CoverageEligibilityResponse

CoverageEligibilityResponse

mostly mapped

CommunicationRequest

tblFeedback

mapped

Links to the sub-pages of the FHIR R4 mapping:

...

FHIR R4 - Claim

...

FHIR R4 - ClaimResponse

...

FHIR R4 - Coverage

...

FHIR R4 - Patient

...

FHIR R4 - Practitioner

...

FHIR R4 - PractitionerRole

...

FHIR R4 - Location

...

FHIR R4 - CoverageEligibilityRequest

...

FHIR R4 - CoverageEligibilityResponse

...

Contributors

Swiss TPH (Dragos Dobre) / Faris Ahmetasevic - FHIR R4 Integration - bachelor thesis - Swiss TPH

Swiss TPH (Dragos Dobre) / SolDevelo (Damian Borowiecki) - openIMIS AI-based Claim Adjudication - Digital Square - GIZ

Swiss TPH (Dragos Dobre, Patrick Delcroix) / SolDevelo (Damian Borowiecki, Seweryn Niedzielski, Kamil Malinowski) - Project: E0 Shelf Readiness - Digital Square - BMGF

Swiss TPH (Dragos Dobre) / SolDevelo (Damian Borowiecki) - openIMIS AI-based Claim Adjudication - Swiss TPH Investment Fund