...
❗ a lot of custom functionality: https://openimis.atlassian.net/jira/software/c/projects/ONI/boards/43
make a distinction between legacy features and new feature requests
(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: https://openimis.atlassian.net/jira/software/c/projects/ONI/boards/43
prio 2: 🧑🏭 new feature requests (must)
prio 3: 🧑🏭 new feature request (nice to have)
develop:
prio 1: 🧑🏭 existing modification in legacy / hybrid version: https://openimis.atlassian.net/jira/software/c/projects/ONI/boards/43
prio 2: new feature requests (must)
prio 3: new feature request (nice to have)
Custom Modifications in Tanzania
⚠️ budget discussion might not allow a migration within the current contract
payment layer through REST API - dedicated API for GePG (Government ePayment Gateway)
MUSE API exists (will not be changed) - fully based on modular version
⚠️ GoThomis - will TZ move to FHIR? (budget)
⚠️ AfyaCare - will TZ move to FHIR? (budget)
GePG API exits in legacy
needs to be migrated to modular architecture (as a custom API)
capitation payment,
commission
Covered by Project: 2022.T1c Modularisation III :
GePG not covered for the implementation in TZ, but support in global components might be possible
❗ 🧑🏭 mobile apps on REST API
🧑🏭 specific reports → migrate to ReportBro https://docs.google.com/spreadsheets/d/1ORCdW5qajBbDT4BaKmAKf6W7X4wbs2Rcd0EQNEVRRzQ/edit?usp=sharing
🧑🏭 Download master data (claim mobile app)
list of beneficiaries
🧑🏭 Funding - distribution per region (currently done via fake families)
…
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) - covered in Project: Customization Cameroon
...
🧑🏭 will need to be migrated to PostgreSQL?
testing - PostgesSQL uses low isolation level by default - might solve the problem
needs large data DB
in combination with report migration
might not be needed, documentation on how to approach potential problemswip
MS-SQL Driver in Django
Impact:
Custom Access to MS-SQL DB
affects JSON-B column access
hinders upgrade to Django 4
Discussion:
only a problem as long as s.o. is using MS SQL
maybe there are new drivers
solved - there is an official MS driver for Django now
...
List of reports: Wiki: Report module, migration status: https://docs.google.com/spreadsheets/d/1ORCdW5qajBbDT4BaKmAKf6W7X4wbs2Rcd0EQNEVRRzQ/edit?usp=sharing
🧑🏭 - which reports still need to be migrated? which ones are still used?
some reports don’t work
list of reports to all sites with feedback on what they are still using (no nice-to-haves!)
also have a look at https://www.metabase.com/start/oss/
🧑🏭 migration of reports
use of Kibana and OpenSearch in the context of CORE-MIS migration is out of scope
Documentation How-To / Best-Practices of Migration
...