1. **Hospital** Table:

Attributes:
	`HospitalID` (Primary Key)
	`Name`
	`Address`
	`City`
	`Postcode` (Unique)

The Hospital table is in 1NF as values would be atomic with no repeating groups. It is in 2NF as all attributes are dependent on the primary key with no partial dependencies, and it is in 3NF as there are no transitive dependencies; all attributes exclusively depend on the primary key.

1. **TransplantUnit** Table:

Attributes:
	`UnitID` (Primary Key)
	`HospitalID` (Foreign Key referencing Hospital)
	`Specialisation`

The TransplantUnit table is in 1NF as values would be atomic with no repeating groups. It is in 2NF as all attributes are dependent on the primary key with no partial dependencies, and it is in 3NF as there are no transitive dependencies; all attributes exclusively depend on the primary key.

1. **Organ** Table:

Attributes:
	`OrganID` (Primary Key)
	`OrganType`

The OrganType table is in 1NF as values would be atomic with no repeating groups. It is in 2NF as all attributes are dependent on the primary key with no partial dependencies, and it is in 3NF as there are no transitive dependencies; all attributes exclusively depend on the primary key.

1. **Donor** Table:

Attributes:
	`DonorID` (Primary Key)
	`Name`
	`Age`
The Donor table is in 1NF as values would be atomic with no repeating groups. It is in 2NF as all attributes are dependent on the primary key with no partial dependencies, and it is in 3NF as there are no transitive dependencies; all attributes exclusively depend on the primary key.

1. **Patient** Table:

Attributes:
	`PatientID` (Primary Key)
	`Name`
	`Age`

The Patient table is in 1NF as values would be atomic with no repeating groups. It is in 2NF as all attributes are dependent on the primary key with no partial dependencies, and it is in 3NF as there are no transitive dependencies; all attributes exclusively depend on the primary key.

1. **Operation** Table:

We need an Operations table to record / capture information related to the operations themselves. This should include an ID for the operation as a primary key, the ID of the unit it was conducted in, the ID of the organ type used, the ID of the donor and the ID of the patient. This allows us to establish proper relationships to the other tables, and allows for a comprehensive record of the transplant process.
This table also allows us to query easier, since all queries can be done on the one table to find essentially any information.
Attributes:
	`OperationID` (Primary Key)
	`UnitID` (Foreign Key referencing TransplantUnit)
	`OrganTypeID` (Foreign Key referencing OrganType)
	`DonorID` (Foreign Key referencing Donor)
	`PatientID` (Foreign Key referencing Patient)

The Operation table is in 1NF as values would be atomic with no repeating groups. It is in 2NF as all attributes are dependent on the primary key with no partial dependencies, and it is in 3NF as there are no transitive dependencies; all attributes exclusively depend on the primary key.

In summary, the provided relational database model is in 3NF as each table has a primary key, and there are no transitive dependencies or non-prime attributes dependent on other non-prime attributes. This ensures the data is organized efficiently and minimizes redundancy.