These are by no means a complete list of conventions but they have been used during the design and implementation phases to help standardize conventions. There are also exceptions to these rules where it makes common sense and is easily understandable.
Some conventions for naming
Columns used for joining between columns should be named the same; some exceptions apply
Keeping column names reasonably unique between tables
"code" or "description" should include the full table name
"LIMS" prefix indicates a value directly related to value provided by the LIMS. Often this is a dictionary related column where the lookup values are not provided by a standard.
If code comes from a specific standard should include abbreviate for standard in the column name (E.g. LOINC, HL7) (Column name example: HL7SexCode)
Where possible try to utilize HL7 identifiers when naming column
If it is a code then identify with Code so it's obvious that it's a dictionary lookup list: HL7SexCode
Camel Case / Mixed case
No underscores
No "of" (e.g. BirthDate not DOB)
Recognized abbreviations