Full Functional dependency
Learning outcomes for this page: Be able to describe and recognise Full Functional Dependency
The term ‘Full Functional dependency’ indicates that the dependency is related to the full key, i.e. if it is a composite key all the fields that make it up.
Taking the above example only average hours taken is fully functionally dependent. i.e. dependent upon the full key. Surgeons name is only dependent on the surgeons PIN and similarly the procedure name is only dependent upon the procedure ID. When a field is not dependent upon the entire key it is said to be partially dependent as stated on the previous page.
Portfolio exercise: Full functional dependency sect7|07|07
Time: 5 minutes
For: Clinicians | NHS managers | Non healthcare workers
Look back and re-read the key point regarding normalisation.Is the above surgeons procedure directory table fully normalised?
Written by Robin Beaumont & Chris Noden e-mail:robin@ieg-net.co.uk or chrisnoden@hotmail.com
