Competency information
Details
Produce appropriate documentation to define the system.
Considerations
- The key elements and importance of database design:
- creating the database – considerations on size, logical structure for data storage
- structure – tables, views, joins, primary/foreign keys
- field types
- nulls and empty strings – how do we deal with missing data?
- normalisation (to ensure data consistency and save space, primary/foreign keys)
- indexes
- importance of documentation
- importance of using standardised coding.
- The relational model of data.
- Implementation of relational databases.
- Schema and tables and be able to explain different data types and models.
- Database relationships, keys and indexes and normalisation.
- Common identifiers and fields to link data sets.
- Distributed relational systems and data replication.
- Security considerations (e.g. backups, access and management of risk).
- The role of ‘big data’ in epidemiology.
- Large data set methodologies.
- Database standards and standards for interoperability and integration.
- The need to manage records and all other information in accordance with applicable legislation, protocols and guidelines.
- Legal requirements that may form part of the agreements, including those that underpin our work.
- How the agreements tie in with information governance policy and procedures.
- The role of the Caldicott Guardian, patient confidentiality/disclosure and the Data Protection Act (including the impact on privacy).
- How system security measures facilitate the appropriate use of sensitive data (e.g. encryption).
Relevant learning outcomes
# | Outcome |
---|---|
# 1 | Outcome Document and design a specification for a relational database for collecting or storing health data, ensuring compliance with security, governance and ethical issues. |