...

General topics (compitation accross modules)

Authorities

To manage the group insurance several authorities will be added, the existing authorities have a "*" :

• PolicyHolder

  • C/R/U/D (4 authorities)

  • Portal R

• PolicyHolderInsuree

  • C/R/U/D (4 authorities)

• Approve (TBC)

  • Portal C/R/U/D (4 authorities)

• PolicyHolderContract

  • C/R/U/D (4 authorities)

  • Submit

  • Approve/ask for change

  • Amend

  • Portal Submit

  • Portal Amend

• PolicyHolderContractDetails

  • C/R/U/D (4 authorities)

  • Approve

  • Portal C/R/U/D (4 authorities)

• PolicyHolderUser

  • C/R/U/D (4 authorities)

  • Portal C/R/U/D (4 authorities)

• Payment

  • C*/R*/U*/D*(4 authorities)

  • Submit (TBC)

  • Validate

  • CreditNote

• ContributionPlanBundle

  • C/R/U/D(4 authorities)

  • Portal R

• ContributionPlan

  • C/R/U/D(4 authorities)

  • Portal R

Roles

To manage the group insurance several roles will be added, the existing roles have a "*" :

• SchemeClerk(*TBC)

  • PolicyHolder

    • C/R/U

  • PolicyHolderInsuree

    • C/R/U/D

    • Approve (TBC)

  • PolicyHolderContract

    • C/R/U

    • Submit

    • Approve

  • ContributionPlanBundle

    • R

  • ContributionPlan

    • R

  • PolicyHolderContributionPlan

    • R

• SchemeAdmin*PolicyHolderC/R/U/DPolicyHolderInsureeC/R/U/DApprove (TBC)PolicyHolderContractC/R/U/DSubmitApproveContributionPlanBundleC/R/U/DContributionPlanC/R/U/DPolicyHolderContributionPlanC/R/U/D

• PolicyHolderClerk

  • PolicyHolderInsuree

    • C/R/U

  • PolicyHolderContract

    • R/U

    • Submit

  • ContributionPlanBundle

    • R

  • ContributionPlan

    • R

  • payment

    • submits

• accountant*

  • Payment

    • Validate

Database Versioning

The entities will have different versioning in place:
Entity related to a specific date (contract …) no versioning will be in place only logging/audition, the code or reference will be used to differentiate them on a business level.
Configuration item (Product, plans, bundle, calculation, policy holder, policyholders insuree): those could be replaced by another version at a given time therefore no CI could have the same code and overlapping validity dates; they will have

• DateValidFrom (date)

• DateValidTo (date)

• Active

• Code (this stays the same across version)

Sub tables won't have any versioning because a new version of the parent table will create a new row in the sub tables.

Drop down list

The configuration of the the droip down list won’t be on the database but on the module configuration, in case a configuration is required across al module, the code will be updated to accept this configuration