Page Comparison

version = 1
status = active
UUID = 0a1b6d54-5681-4fa6-ac47-2a99c235eaa8
calculation_rule_name = “payment: capitation “

type = account_payable

sub_type = third_party_payment

dateValidTo = None

dateValidFrom = 2000-01-01

Registration on signals from other module(existing or not):

• billCreationFromCalculation

Batch run might be required upfront to have the relative indexes calculated / all claim valuated where there is relative prices.

billCreationFromCalculation will have a variable that will tell the signal listener to be activated or not: this will be activated for “capitation“Only the “valuated“ claims are eligible for bill generation meaning that the batch run might be triggered before in case .

Batchrun will trigger billCreationFromCalculation and will send: when the payment plan would be deliver the batch run page could be replaced by payment plan (this page could call billCreationFromCalculation service on selected payment plans) page and bill page.

• date_from

• date_to

• type

• sub_type

Converter

[to be updated]

1. two way of creating the accountPayableare possible for the capitation, in both case there will be one “accountPayable” per HF

   1. one asset (line) per weighted indicator I for product P : Allocated contribution/ Sum(indicator for P) as unit price , indicator I as quantity, (1-weight) as discount;

      1. Population living in catchments area of the health facility

      2. Number of families living in catchments area of the health facility

      3. Insured population living in catchments area of the health facility

      4. Insured number of families living in catchments area of the health facility

      5. Number of claims (contacts) with the health facility by insured in the catchment area

      6. Adjusted amount

   2. asset (line) per product with the detail of the calculation as asset description