Versions Compared

Key

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

Curent status

...

  • Benefit package: required to assess claim visit type limit, ceiling, deductible …

    • Benefit package Services: required for assess Child / Adult ceiling, Amount limits, limit exclusiosn and relative pricing

    • Benefit package Items: required for assess Child / Adult ceiling, Amount limits, limit exclusiosn and relative pricing

  • Medical Item: tblItems required to assess frequency and mask of service: Is it really needed ?

  • Medical Product: tblService required to assess frequency, service type and category and mask of service: Is it really needed ?

  • Medical Item Price List : needed to unsure the agreement update are taken in account for the right claims

    • Medical Item Price List Items details : tblPLItems

  • Medical Services Price List: needed to unsure the agreement update are taken in account for the right claims

    • Medical Service Price List Service details : tblPLService

  • Health facility (for price list, type of care and catchement)

  • Location:Villages (for population)

...

  • The solution should help the database persormance

    • either using different tables

    • either have field on which the valid row could be used to generate clustered index (Null value is not making it easy)

  • The solution should enable the search on valid and historical event (could)

  • not all table can be managed with a validity date for the underlying data (unlike catchement)

1 live table, 1 log table

...

Strengths

Weaknesses

easy to find the record valid at a given date

big table

difficult to manage clustered indexes

cannot have futuree value because the valitidy to as null is used to find line data

Opportunistes

Treats

Managed this on the front end to enable futur value too

1 table with active column

...