openIMIS Modules
In openIMIS, (nearly) everything is a module: even "low level" (and mandatory) features follow this principle.
Modular Architecture
The following features are implemented as (interchangeable) modules
Overview of Modules
Additional Information
Tests cases for the various modules are documented in a separate wiki page.
Plugins (can) provide several types of archetypes, dedicated to the various openIMIS layers: openIMIS Mobile FE, openIMIS Web FE, openIMIS Online BE, openIMIS Batch BE,...
openIMIS can be deployed with an extra layer dedicated to implement a FHIR API, based on openIMIS core (base) modules.
Today the FHIR API is a unique module, but there is an open point on splitting it into separate modules (per FHIR resource?):
Code (static) analysis, as well as unit tests coverage metrics of each module, is automated via travis-ci and codeclimate. You can log into these tools via your GitHub login. If you are registered in openIMIS GitHub, you'll have access to openIMIS build job and code quality metrics.
Here my point of view on the module list details in 4 groups (core, business...)
The module with * leading are not found in JLN
IT core
*Core & security
Database access,
Logins, user, roles including enrolment office & claim admin,
Email
Business
Claims Management
Claim,
Feedback,
Review
Appeal (not available)
Scheme Policy
Insurance companies (not available),
provider policies settings,
Product
Eligibility Requirements,
Product
Benefit Package Formulary
Product
provider rates
Price lists (Item and services),
Funding
Premium Collection ,
Payer
Policy payment
Beneficiary Management
Insures,
Group,
Policy,
Renewal
Register
*Locations (regions … )
Provider Management
*Client registry
*Medical item
*Medical Service
*Diagnosis
Reporting
Performance Management
Statistics and reports