SQL

I find SQL to be the code that I interact with the most outside the classroom, besides Excel. I realised soon after learning about SQL in class that it is the basis of the computer programs that I use daily at work. I work in the medical field currently but as a front end user of these systems, I cannot see how it functions, however I noticed that whenever the system fails, an SQL error message appears. SQL is truly the perfect system for hospital settings, as each patient is given a unique identifier, but is often searched for using name or date or birth. A simple front end search function means that non-technical employees cannot accidentally delete any information, and it is very easy to limit who can access different aspects of the stored information, ensuring patient data protection. While the current system is efficient within individual hospitals, there is no inter-hospital system in place. There are also issues with the code which can cause redundancies, for example, every time a patient is referred to the hospital a new unique number/primary key is created for that patient, even if they already have a unique number.

SQL Project

Below you will find an example of an SQL database that I created. The CSV files are example data from Bike Store that I downloaded from Kaggle. I used these individual CSV files to create an interconnected database within SQL and demonstrated the usability by running a few basic queries. I chose not to include the Staff ID database to show the functionality of only giving some people access to limited information. In a real world scenario, it is much more likely that customer information would be the redacted information.