This bThis 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).
...
The (medical) Service and Item eligibilty check, contributed in Insuree Enquiry screen are part of (calculated from) the policy module and, in legacy openIMIS, implemented via the uspServiceItemEnquiry stored procedure. This stored procedure will be was migrated to a python service in openimis-be-policy_py module.
See details in Service or Item Eligibility
Note: the service is already existing (bridging to the stored procedure) and used from the current enquiry screen, but also the FHIR API.
...