...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Custom Modifications
Impact: depends, will have to be collected per country by implementation partners
push for customizations based on module configuration
Custom Modifications in Nepal
❗ a lot of custom functionality: https://openimis.atlassian.net/jira/software/c/projects/ONI/boards/43
(tender in preparation as part of a general openIMIS maintenance contract) : Swiss TPH establish list of functions that need to be migrated
prio 1: existing modification in legacy / hybrid version
prio 2: new feature requests (must)
prio 3: new feature request (nice to have)
Custom Modifications in Tanzania
payment layer through REST API - dedicated API for GePG (Government ePayment Gateway)
MUSE API exists (will not be changed) - fully based on modular version
GePG API exits in legacy
needs to be migrated to modular architecture
Covered by Project: 2022.T1c Modularisation III :
mobile apps on REST API
specific reports: capitation payment, commission → migrate to ReportBro
- capitation payment configuration in Product
- batch run
- capitation payment SP
- batch run SP
Custom Modifications in Cameroon
HIV
report on migration needs done by STPH (-> Implementers)
EDUCASH
Cash-Transfer scheme => to be migrated to modular?
Custom Modifications in Gambia
Cash-Transfer scheme is in progress of migration
REST API
Impact:
Mobile Apps will not work any more
GOTHOMIS & Payment Layer in TZ
stuck to MS SQL because of stored procedures that are called from REST API (ca. 45)
Discussion:
C#-part can be re-used, but depend on stored procedures
done - needs to be compiled for .net core per Windows and Linux (done in Docker)
Mobile App on REST
Need new mobile app on FHIR → budget needed
ePayment on REST
migrate APIs to python = new adapter to payment switch → budget needed
Interoperability on REST
e.g. GOTHOMISs & afyacare
will remain on rest - will need to be done by GOTHOMIS & Afyacare
done - Added to Docker packaging
done - issue with env variables (ex. DB connection string)
done - sharing of files (ex. Insuree pictures)
rejected - Test REST API against PostgreSQL - not practical as REST-API will not be migrated on PostgreSQL
list of interactions with DB: https://docs.google.com/spreadsheets/d/1XdamXxLejmPRzM5xN8dCSPSIbfNv1PgJ/edit#gid=1496686413 - will not be needed after
create/modify payment layer adapter on the openIMIS side for TZ
Custom Modifications
Impact: depends, will have to be collected per country by implementation partners
push for customizations based on module configuration
Custom Modifications in Nepal
❗ a lot of custom functionality
wip (tender in preparation as part of a general openIMIS maintenance contract)
Custom Modifications in Tanzania
budgeted - payment layer through REST API - dedicated API for GePG (Government ePayment Gateway)
budgeted - mobile apps on REST API
budgeted - specific reports: capitation payment, commission → migrate to ReportBro
done - capitation payment configuration in Product
done - batch run
done - capitation payment SP
done - batch run SP
Custom Modifications in Cameroon
HIV
report on migration needs done by STPH (-> Implementers)
EDUCASH
Cash-Transfer scheme => to be migrated to modular?
Custom Modifications in Gambia
- Cash-Transfer scheme is in progress of migration
Stored Procedures
Impact: depends
Discussion: need to list remaining stored procedures that will not be migrated
https://docs.google.com/spreadsheets/d/18XxbBsPXvHrq7Enu7Bj02WpE1GiIaslNP1aMK6ECQcU/edit#gid=0
done:
in modular version: everything needed was migrated either to Python (business logic) or PostgreSQL (a few small queries)
SPs for REST API will not be migrated - need to run on MS SQL (-> see there)
...