Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixed typos & added Table of Contents

...

Page Properties

Organizer

Swiss TPH SolDevelo

Type

Competition

Weblink

https://summerofcode.withgoogle.com/

Deadline

2022-04-19

Status

Status
colourGreen
titleIn progress

Projects

openIMIS: Improve openIMIS software

Content

Table of Contents
minLevel1
maxLevel1
excludeContent

PROJECT: MODULE MANAGER

TIME: 350h

...

MENTORS: Patrick Delcroix / Seweryn Niedzielski

Description 

Calculation rules are a solution to accommodate complex calculations that vary between IMIS implementations. Calculation rules  are defined in the backend and based on their configuration the frontend adding the required parameters in different business items screens (kind of templating using json) via the Calculation module (front end and back end).

...

OpenIMIS mobile app was created in 2013 and it can be seens seen in its look and feels but also in its internal architecture. Also Health IT is going toward the FHIR standard, openIMIS as a health IT system should follow.

The goal of this project would be to create a FHIR application to manage insurance that will be compatible with openIMIS but could be a basis for other insurance company system.  In that regards Google started a project called  Android-FHIR SDK that provide a FHIR application framework, meaning that the database structure is already FHIR compliant and the work required to communicate with openIMIS would be minimal as openIMIS is already fhir FHIR compliant.

Most of the work would be on the UI/UX to fit FHIR insurance models and insurance/opeIMIS openIMIS business processes (the project can do one or multiple processes)  : Registration, EnrolmentEnrollment, Renewal, Client Portal, Claiming, Claiming Audits/feedback

...

POC that will implement of the business processes of openimis openIMIS following the agile methodology with this product backlog ordered by priority (up to point 4 will be already a success)

  1. Set-up the project

  2. Authenticate a user with openIMIS as backend (FHIR login)

    1. at least once online, then local auth possible if not network

  3. Retrieve the user preferences (language, locations, organisation organization etc )

    1. for offline usage

      1. Location (Location)

      2. HealthFacility (OrganitationOrganization)

      3. Users (Praticionner Practitioner ? OE and CA)

      4. List

        1. Product (InsurancePlan)

          1. Pricing/limits ? TBC

        2. items (Medications)

        3. services (ActiviyDefintionActivityDefintion)

        4. diagnosis (CodeSystem)

        5. hardcoded hard coded : claim type etc… CodesytemCodeSytem

    2. Saving data : Can the app use StructureDefintion StructureDefinition ?

      1. hold the extension (new properties etc)

      2. hold constrainstconstraints

  4. Check insurance coverage based on insurance number

    1. CoverageEligibility

    2. Coverage

  5. Enable the registration of a new insuree

    1. Insuree : registration of a person in the system

  6. Enable the update of an existing insuree 

    1. Insuree

  7. Enable the enrolment enrollment of an insuree on a product (payment not included)

    1. Enrolment Enrollment into a product/policy (including payment): Contract

    2. challenge: define the price offline (TBD)

  8. Add beneficiary on a policy

    1. create/update Insuree

    2. add add the beneficiary on the contract

  9. Register and submit new claims using items and services defined in openimisopenIMIS

    1. claim and claimResponse (kind of async)

    2. Challenge: high input density

  10. manage pricelist (TBD)

    1. items

    2. services

...