Design of the Data Model

Key Field: 

A specific field to identify the entity as a whole.  e.g. Provider ID in the Provider entity.

Non Atomic Data: 

Data that has not been broken up into its smallest possible parts to create new fields. This type of data is not specific and can lead to confusion. This makes searching for queries inside the data base that mach harder to achieve. E.g. when the field is labelled “Name” when it can be broken down into “title”, “Surname” and “First name”. And if possible middle name.

Repetition of Data:

Data in which can force the individual using the system to create another field and can even make unlimited fields e.g. Option A, Option B etc…. This can cause loss of time and problems such as define a specific search criteria. This can be resolved by giving these fields such as the option fields its own entity.