Q1. Entity-Relationship Modeling The government of the province is implementing a program that manages vaccine distribution, monitors the pediatric and adult immunization levels and issues alerts when an emerging epidemic treat is detected. The program is managed by the Ministry of Health (MH). MH is building a dedicated an information system that can handle immunization records as well as vaccine distribution, vaccinee registration and booking for the immunizations that are covered under the provincial health insurance plan. MH hired your team to build their new information system. Your team must design and implement a new relational database that meets the MHs informational requirements and supports the functionality outlined below. Immunization providers that administer vaccines covered by the provincial health insurance plan receive the vaccines they will administer from the ministry. The MH must maintain accurate inventory records to keep track of the vaccines it procures from manufacturers and then distributes to providers. For each lot of vaccine, in addition to the type of vaccine in the lot, quantity of doses and expiration date, the MH also needs to record the supplier of the lot, along with information about them such as company name and address. For each manufacturer, the MH wants to also store the contact information of at least one manufacturer employee, their name, position, phone number and email, in case the lot has quality issues that need to be followed up on. The MH also needs to store information about each vaccine provider (hospitals, pharmacies, private clinics, university health centres, walk-in centres, etc.), and the supplies they received. The MH assigns one of its employees to serves as the point of contact for each provider. The fulfillment of a vaccine shipment to a provider is personally overseen by that providers MH point of contact. A point of contact can serve multiple providers. For each provider, the MH wants to record their name, address, along with contact information for a person from that organization (i.e., the persons name, position with the organization, phone number and email) who it can keep informed about the dispatch of new vaccine shipments and other relevant information. Each shipment that the MH sends to a provider may include several different types of vaccines. For each shipment, MH needs to store, and be able to make available, the date of the shipment as well as how many doses of which type of vaccine were delivered and what vaccine lots the doses of each vaccine type where from. In order to support an online vaccination booking system and serve as an immunization registry, the MHs system also needs to help collect information about each vaccination performed by a provider, including how many doses the person received, as some vaccines are multi-dose, and when the person received their first, and subsequent shots (for multi-dose vaccines). The MH must record, and be able to make available,.

1. Q1. Entity-Relationship Modeling
The government of the province is implementing a program that manages vaccine distribution,
monitors
the pediatric and adult immunization levels and issues alerts when an emerging epidemic treat is
detected.
The program is managed by the Ministry of Health (MH). MH is building a dedicated an
information system
that can handle immunization records as well as vaccine distribution, vaccinee registration and
booking for
the immunizations that are covered under the provincial health insurance plan.
MH hired your team to build their new information system. Your team must design and
implement a new
relational database that meets the MHs informational requirements and supports the functionality
outlined
below.
Immunization providers that administer vaccines covered by the provincial health insurance plan
receive
the vaccines they will administer from the ministry. The MH must maintain accurate inventory
records to
keep track of the vaccines it procures from manufacturers and then distributes to providers. For
each lot of
vaccine, in addition to the type of vaccine in the lot, quantity of doses and expiration date, the
MH also
needs to record the supplier of the lot, along with information about them such as company name
and
address. For each manufacturer, the MH wants to also store the contact information of at least
one
manufacturer employee, their name, position, phone number and email, in case the lot has quality
issues
that need to be followed up on.
The MH also needs to store information about each vaccine provider (hospitals, pharmacies,
private clinics,
university health centres, walk-in centres, etc.), and the supplies they received. The MH assigns
one of its
employees to serves as the point of contact for each provider. The fulfillment of a vaccine

2. shipment to a
provider is personally overseen by that providers MH point of contact. A point of contact can
serve multiple
providers.
For each provider, the MH wants to record their name, address, along with contact information
for a person
from that organization (i.e., the persons name, position with the organization, phone number and
email) who it can keep informed about the dispatch of new vaccine shipments and other relevant
information.
Each shipment that the MH sends to a provider may include several different types of vaccines.
For each
shipment, MH needs to store, and be able to make available, the date of the shipment as well as
how many
doses of which type of vaccine were delivered and what vaccine lots the doses of each vaccine
type where
from.
In order to support an online vaccination booking system and serve as an immunization registry,
the MHs
system also needs to help collect information about each vaccination performed by a provider,
including
how many doses the person received, as some vaccines are multi-dose, and when the person
received their
first, and subsequent shots (for multi-dose vaccines). The MH must record, and be able to make
available,
information about the vaccinated persons name, SIN, and address, the date of the immunization,
the type
of vaccine used as well as the lot the vaccine belonged to. For each reported immunization the
MH needs
to be able to help identify the provider who performed the vaccination and submitted the record.
Each
immunization record submitted by a provider must also contain the location the vaccination was
performed
at.
In addition to immunization records, every vaccination provider is required to report any serious
adverse
reactions, such as anaphylactic shocks, experienced by a person who was vaccinated by the

3. provider. Besides
information identifying the person who experienced the adverse effect, the report must also
contain
information about the type of vaccine used and the vaccine lot the vaccine dose belonged to.
Your database
design should also support assigning the MH employee who serves as a point of contact for the
provider
who submitted the report to be the person in charge of handling that report.
Providers must also report any quality issues they encountered while using vaccines it received
from the
MH. This information will be used to determine whether to renew or discontinue supplier
contracts. (Some
suppliers are producing vaccines under license from the original manufacturers.)
In addition to the employees that serve as points of contact for vaccination providers, MH has
various other
employees, from administrative assistants to doctors and scientists. MH stores for each employee
their
name, address, position, status and email address and assigns to each of them a unique ID.
Doctors are
charged with handling adverse effects reports. Scientists are tasked with testing samples from
each vaccine
lot and MH needs to be able to enforce that only doctors are assigned to follow up on the adverse
effects
reports, only scientists are assigned to perform vaccine tests and only people with administrative
roles can
be assigned as points-of-contact for providers.
For each vaccine sample test, the system should keep information about the vaccine lot tested,
the date the
test was performed, the type of test performed and the result of the test and the MH scientist who
performed
the test. For auditing purposes, MH also needs to be able to identify the doctors who were
assigned to
follow up on severe adverse reaction reports. Only one doctor should be assigned to follow up on
a report,
and only one scientist should be assigned to test a vaccine lot.
The residents of the province can request to be booked for immunizations covered by OHIP at

4. any time. In
order to verify eligibility, MH needs to store for each person requesting immunization their
name, SIN, and
date of birth. A request for vaccination should include the SIN of the person requesting the
vaccination as
well as the date the request was made. Once a request for vaccination is received, the booking
system will
schedule the immunization at one of the providers nearest to the persons address and
communicate that to
the provider and the prospective vaccinee.
MH needs to be able to verify at any point in time for every person registered to be vaccinated
whether
their immunization was accomplished, i.e., whether they have received all required doses. Not all
vaccines
can be given together, or even be administered within a certain exclusion period. Your database
design
should also support storing information about which other vaccines a certain vaccine should not
be administered
together with, as well as the exclusion period. For example, it is recommended that the
antiorthopoxvirus
vaccine currently approved in Canada, IMVAMUNE, not be given within 4 weeks of an
mRNA vaccine for COVID-19. This information should be available in the system so that it can
be used to
determine if a person can be booked for an immunization with a particular vaccine, given their
most recent
immunization history.
Lastly, some residents, e.g., international students enrolled in the provinces colleges and
universities, may
have been vaccinated abroad either on travel trips or in their home countries and MHs
information system
must support functionality that allows these residents to upload information about the
vaccinations they
received (what, when, where and from whom).
Q1.1 [25 points] Design conceptual model that would support the operations of the MH and
represent it as Entity-Relationship model using the diagramming technique presented in class.
Specify all applicable entity sets (their attributes, and primary keys), as well as all relationships

5. between entity sets (and their descriptive attributes, if applicable). Clearly state, in natural
language, the assumptions that you made (if any) and the constraints not captured in your
diagram (if any). Make sure to note on the diagram all relationship cardinalities, mandatory or
optional participation constraints, primary keys, etc. Q1.2 [10 points] Transform your E-R
diagram into a relational model using the technique presented in class. List all resulting relations
and clearly identify all primary and foreign keys. Q1.3 [3 points] Identify and list 5 functional
dependencies in your model using the format discussed in class. Question 2 [22 marks] Consider
the following database schema: R(A, B, C, D, E, F, G, H) with the set of functional dependencies
FD={FA,ACE,EB,BGF,BED,BDHE,DH,CDA,AE,ADBE} Q2.1 [12 points] 1. List all the
candidate keys for R with respect to the set FD. 2. Explain why R is not in BCNF with respect to
FD. 3. Produce a BCNF decomposition of this schema using the algorithm presented in class. For
full points, clearly list ALL the relations in the final decomposition and, for each relation, state
what is the corresponding set of functional dependencies. Show the full details of your work.
Q2.2 [10 points] 1. Explain why R is not in 3NF with respect to FD. 2. Produce a 3NF
decomposition of this schema using the technique discussed in class (list both the relations and
the corresponding set of functional dependencies). Make sure to identify the minimal basis on
which you based your 3NF decomposition. Discuss whether you need to apply the last step of the
algorithm discussed in class and add an additional relation. Show the full details of your work.
Sample assignment cover page