Page Comparison

In openIMIS, (nearly) everything is a pluginmodule: even "low level" (and mandatory) features follow this principle.

In other words, even the following features are implemented as (interchangeable) pluginsmodules:

• Login (authentication)

Beyond these low-level pluginsmodules, several plugins modules will be dedicated to configuration/administration:

• openIMIS (as a whole) configuration

• User & Roles management

The real business needs will be implemented in dedicated pluginsmodules:

• Payers

• Locations & Health Facilities

• Medical Services and Items

• Medical Services and Items Price Lists

• Insurance Products

• Claim

...

• Persons & Families

  module scope

  (under Beneficiary Enrollment)

• Policies

  module scopeContributions module scope

  (under Beneficiary Enrollment)

• Contributions (under Beneficiary Enrollment)

In addition, the following modules are used for integrating openIMIS with external systems:

• openIMIS FHIR module

Tests cases for the various modules are documented in a separate wiki page.

...

Today the FHIR API is a unique module, but there is a an open point on splitting it into separate modules (per FHIR resource?):

height250 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 GitHub login. If you are registered in openIMIS githubGitHub, you'll have access to openIMIS build job and code quality metrics.

...