Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This document summarizes the openIMIS features provided by the Policies module.

...

  • there are filters on the location… but a policy is not linked to a specific location. So we assume the location criteria are on policies' families (… which can be down to ‘village’).

  • when double clicking on a policy from the list, the legacy app opens the family overview (!), we’ll replace this by the default behavior (open the entity itself - in this case the policy, but add a ‘open family’ button in the rows to access the family overview from the policies (i.e. as we did for the insurees)

Note about the ‘historical’ checkbox:

The search in ‘historical’ values makes the assumption that archiving is performed “in live table”. This mechanism is under review (for performance reasons). This criteria may not be available anymore (depending on the new archiving mechanism chosen).

...

Policy Page

Policy form, screen mock:

...

Remarks/questions:

  • Are the policy ‘values’ (deductibility ‘in-patient,…) influenced by the product (i.e. distinct values to fill in depending on the product 'parameters’)

  • Policy amendments are not implemented. To change anything in a policy, one has to close/reopen (or renew) When adding/removing a policy. More specifically:

    • when adding a member to the family, the member is (by default) not covered by the policy (need to be added in the tblInsureePolicy)

    … BUT I see nowhere this can be done: does it mean it is performed by closing/reopening (or 'forced renewal) the policy? What about the contribution (transferred,…)?
    • when removing a member from a family, he remains covered by the policy until policy expiry (or anticipated renewal).

  • Policy status are Idle, Ready, Active, Suspended and Expired (??+ ONE NEW FROM TZ Patrick Delcroix ??). When creating a new policy, it remains in status “Idle” until contribution is recorded for it… in which case it either (based on module configuration) switches to:

    • “Ready” status (waiting for payment before switching to “Active”

    status,
    • )

    • … or straight to “Active” status (without waiting for payment)

once expiry date over, the policy switches to ‘Expired’ (via the policy renewal batch).

An Idle or Active policy can be switched to ‘Suspended’ via the ‘pause’ action button, for

...

“Expired” or “Suspended” policies, the ‘pause’ button is replaced by a ‘renew’ button:

...

Deleting a Policy

Simple delete (logical, by adding the validity_to date), with confirmation dialog.

...

Note: the service is already existing (bridging to the stored procedure) and used from the current enquiry screen, but also the FHIR API.

TODO: detailed reverse engineering of the stored proc: rules to be applied,…

Policy renewal batch (scheduled process)

Policy renewals … in “tools” menu + separate https://github.com/openimis/policy_renewal_service_vb

Batch launch screen mock:

...

Remarks/questionsRemark:

Actions on the top right (in the order): Update, Send SMS, Preview… and “update” is in fact “launch”… so should we use the ‘launch’ icon (as for claim batches?)

Current process

...

1. policy renewal inserts

...