Designing

The first option to finding a solution to this problem is by assuming the issue on doctors being added up to three with an assumption that the same requirement will not occur again. Even though the circumstance presented may make this approach feasible. Similarly, another approach can be creating a different table that tracks the existing relationship between doctors and patient which would match up the numerous perspective tables.

Since the system only supports two doctors but with the government initiative, now there are three doctors. The system can be created in such a way one column is adjusted to handle three doctors (Department for Work and Pensions 2015). With this system the hospital is enabled to retain only the amount of required doctors. However, this solution does not seem to provide an original response to the dilemma since in the future if the number of doctors should increase, the number of columns will keep increasing which may be tedious to find retrieve doctor-patient information.

The hospital might need to create a different table in the system that aims at keeping track of relationships that are unique between doctor and patients and these kind of relationship should not be duplicable. Once the relationship is established and the table created, a different group can be created to enable physicians find out who exactly will provide care to the patients, who will conduct the diagnosis process and which doctor will conduct research. A last approach can be an actual fix to the problem by implementing systems of proof for future use. Since we cannot have information stored on relational databases, there is a higher call to creativity in how to add columns and tables to support the system