2019-04-16 PossibleHealth -Phase I dependencies discussion II

Date

Apr 17, 2019

Participants

  • @laxman manandhar

  • @Uwe Wahser

  • @Dragos Dobre

  • @Kamil Madej (Deactivated)

  • @Xavier Gillmann (Unlicensed)

  • @Arkadiusz Lalo

  • @Sanjaya Poudel

  • @Dipak Thapa

Goals

  •  

Discussion topics

  1. Decide on bahmni-openIMIS Integration Phase I dependencies resolution

    1. Are we able to deliver FHIR apis for these resources ?

      1. FHIR Resources Analysis for OpenIMIS Integration

      2. Eligibility Coverage Resource (will be decided on the basis of Arkadiusz analysis ): @Arkadiusz Lalo

        1. We can make use of stored procedure, can be exposed as django service (Xavier) @Xavier Gillmann (Unlicensed)

        2. Arkadiuz will look after the Fhir fields mapping

      3. Claim Request/Response FHIR resource : No problem

      4. Claims status tracking :

        1. Status check : no

        2. Cancel claims :

        3. Re-process claims

      5. Financial-module Fhir resources : Analysis in progress

    2. Which version of FHIR we are going to use? FHIR 3.0.1 (http://hl7.org/fhir/STU3/)

  2. Discussion on current impediments for development

    1. Impediment 1 : For now No logics/Fields for eligibility fhir fields and balance check , will be added in new module/architecture only

    2. Mapping Reference: https://docs.google.com/spreadsheets/d/1ErGF_SaRuM4ISUYDTluL_6w7F3Zj67K3IP7VAPrRwXE/edit#gid=1306311133

  3. Decide on whether to use existing web service or wait for new architecture release

    1. If used existing web service , will have to reimplement same functionalities after the new architecture release : this may extend the timeline for release of fully fhir based integrated product

  4. Project management tool

    1. OpenIMIS JIRA

  5. Dev/QA platforms for openIMIS

    1. Testing platform :

      1. Unit tests: Travis (BlueSquare & SolDevelo, OS accounts), HipTest (openHIE), SpecFlow (Gherkin .net)

      2. User tests: Rent a new Linux server or use the Demo Windows Server

  6. WebService Or FHIR resource expose for list of Medical items and services with codes and details .

    1. These are required during claims resource construction

    2. Python object constructions done from Bluesquare @Xavier Gillmann (Unlicensed)

    3. Need to map to FHIR - Soldevelo- Needs analysis for exposing as fhir resource @Arkadiusz Lalo

  7. Login Authentication (Blue square )

    1. Is it for new architecture only

    2. How will be the new architecture rolled out to prod

      1. Parallel old and new systems : migration of only the newer modules




Action items

Eligibility Coverage Fhir Resource fields exposure analysis using stored procedures by @Xavier Gillmann (Unlicensed)
Eligibility Coverage Fhir Resource mapping analysis by @Arkadiusz Lalo
Claims status tracking using FHIR @Kamil Madej (Deactivated) @Arkadiusz Lalo
List of medical items and services with details : Python object constructions from Bluesquare @Xavier Gillmann (Unlicensed)
Expose List of medical items and services using FHIR @Arkadiusz Lalo

Decisions

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/