Current published data and Collaborative Glossary: Difference between pages

From Discovery Data Service
(Difference between pages)
Jump to navigation Jump to search
 
No edit summary
 
Line 1: Line 1:
__NOTOC__
This is an area of the Wiki for members of the Discovery Collaborative to share definitions of common terms. It is public and can be referenced from other documents and websites as necessary. Please let us know if you would like to challenge or add definitions.  simon.meredith@nhs.net or jack.barker@nhs.net
This article provides the latest data publisher information by sector, geographical area, service, and system provider.
{| class="wikitable sortable"
|+
!Term
!Definition
!External Links
|-
|Categories
|Broad sections of an Ontology or Classification such as the Categories in ICD 10 which contain all ICD 10 codes related to one body part.  It might be also be large groupings of test results e.g. Haematology, Biochemistry, Immunology, Microbiology etc.
|[https://icd.who.int/browse10/2010/en#/II ICD 10]
|-
|Cloud
|The Cloud refers to IT infrastructure, platforms, and services that are hosted in a remote data centre, managed by a third party. Typically these data centres are run and managed by large companies such as Microsoft (Azure), Amazon (AWS), and Google (GWP), but there are many other providers too. Using the cloud removes the need for customers to buy and maintain their own physical IT equipment. Instead, the cloud provider typically charges customers daily rates based on storage used, computational power used, memory, number of servers etc
|[[wikipedia:Cloud_computing|Cloud Computing]]
|-
|Cloud Native
|Cloud Native refers to building software and systems in the cloud that make use of services made available by cloud providers, to run scalable, resilient applications. For example, instead of creating a SQL database on a server in the cloud, which the customer would need to monitor, maintain, patch, back-up etc, they could make use of a “SQL database as a service” from the cloud provider, who would automatically take care of all the maintenance without any further intervention from the customer
|[[wikipedia:Cloud_native_computing|Cloud Native Computing]]
|-
|Cluster
|A group of concept codes making another idea. The Cluster may be made up of concepts from different ontologies or classifications e.g., Snomed CT and ICD10. Synonyms for Cluster are refset, value set, codelist, code set, grouper.  The name "cluster" was strongly advocated for by John Robson ([https://www.qmul.ac.uk/blizard/ceg/ Clinical Effectiveness Group] (CEG) NEL) because of his work in primary care.
|[http://app.powerbi.com/view?r=eyJrIjoiZTY0ODY0YzEtMjhhYy00ZTViLWJjZDQtMWZjOWVkMTZlOGExIiwidCI6IjUwZjYwNzFmLWJiZmUtNDAxYS04ODAzLTY3Mzc0OGU2MjllMiIsImMiOjh9 Primary Care Domain Reference Set Portal]
|-
|Common Data Model
|This is the shared Data Model which has been adopted as a standard for an organisation or group. It defines how the elements of data relate to one another and enables data to be transferred between different systems which share the Common Data Model with ease.
It defines the transformation of data from multiple different databases with potentially multiple coding systems into a common storage format (data model) as well as a common representation (terminologies, vocabularies, coding schemes)
|[https://www.jamesserra.com/archive/2019/06/common-data-model/ Microsoft Example]
|-
|Concept
|A coded idea. For example, Name = Baker's Asthma, SNOMED CT code = 34015007
|
|-
|Conceptual Data Model
|This is a high level model, describing business processes and how they relate to one another. In simple terms, it is a map of concepts and rules relating to the business which can then be used to define relationships between data entities in order to describe the business concepts – this leads to the creation of a logical data model
|
|-
|Data Dictionary
|A centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format e.g. NHS Data Dictionary.
|[[wikipedia:Data_dictionary|Data Dictionary]]
|-
|Data Model
|Data models exist at different levels of abstraction, from conceptual data models which are high-level and consider business activity and relationships, to a physical data model which represents the implementation of a database. A data model shows how elements of data relate to one another and how they are structured, how they relate to business needs, and how they can be manipulated.
|[[wikipedia:Data_model|Data Model]]
[https://digital.nhs.uk/services/nhs-data-model-and-dictionary-service NHS Data Model and Dictionary Service]
|-
|Data Platform
|A Data Platform is any digital solution which enables an organisation to store, transform, aggregate, and analyse data. It integrates many different technologies for different purposes to meet the data needs of the organisation. It includes security and access controls to ensure IG compliance
|
|-
|Database Index
|Indexes are used to quickly sort and retrieve data in a database. They may take the form of a physical, clustered index, which is the physical ordering of the data in the table (e.g. by ID or surname), or a non-clustered index which describes the logical ordering of the data separately – like the index at the back of a book: the index key is ordered (e.g. surname) and next to it is information showing where to find the record.
|
|-
|Database Schema
|This is the definition of the structure of a relational database and defines how data is organised, including the table names, fields (also known as columns), data types, constraints, indexes, and relationships between these entities. The schema is a blueprint of how the database is constructed.
|
|-
|[https://ico.org.uk/for-organisations/guide-to-data-protection/ico-codes-of-practice/data-sharing-a-code-of-practice/data-sharing-agreements/ Data Sharing Agreement] (DSA) Framework
|The arrangements for storing and managing data sharing agreements to ensure transparency across controllers and processors.  It is likely that the Data Usage Committees/Data Access Groups ([https://ico.org.uk/for-organisations/guide-to-data-protection/key-dp-themes/guidance-for-the-use-of-personal-data-in-political-campaigning-1/controllers-joint-controllers-and-processors/ Joint Controllers]) will generate and store a copy of the DSA, whilst processors and sub-processors will also need a copy.
|
|-
|Data Warehouse
|A data warehouse stores data for the main purpose of reporting and data analysis. They are central repositories which bring together disparate data sets into one place, to enable reporting at scale and pace.
|[[wikipedia:Data_warehouse|Data Warehouse]]
|-
|DDS Information Model Manager
|The Information Model Manager is an application developed by the Endeavour Charitable Trust which provides a view of the Common Information Model and supports authoring of the content of the model. It can be used to view the model structure and content, download artefacts (e.g. value sets), and manage the ontology. It can be used to view entities and their relationships (e.g. an A&E admission, which is an Encounter and has a subject of a Patient and has a sub-encounter of a Triage Encounter etc)
|[https://wiki.endeavourhealth.org/index.php?title=Discovery_health_information_model Discovery Health Information Model]
|-
|Endeavour Information Model
|
|
|-
|Expression (Snomed CT)
|A combination of concepts that represent something that is not already represented as a Concept or Cluster. It typically links things across concepts (disease of infection (finding), with bacteria name (organism), with sepsis (observable entity) with kidney (body structure).
|[https://confluence.ihtsdotools.org/display/DOCGLOSS/SNOMED+CT+expression Snomed CT Expression]
|-
|FHIR
|FHIR stands for Fast Healthcare Interoperability Resources. It is an international standard for health care data exchange and is published by HL7. It is designed to enable the exchange of healthcare related information, including clinical, administrative, publich-health, and research data. DDS stores data in the core in FHIR format before it is restructured and sent to subscriber databases
|
|-
|Functional Requirements
|These are product features or functionality that must be developed in order for the system to satisfy requirements. They must be implemented in the system in order for it to achieve what it is supposed to accomplish. Examples include "users should be able to download data based on their filtered search criteria" or "only admin-level users should be able to reset passwords for other users"
|[[wikipedia:Functional_requirement|Functional requirement]]
|-
|GitHub
|GitHub is a provider of version control and source-code management using [[wikipedia:Git|Git]] (which is software used for tracking changes in files). It enables software developers to safely store source code and work on it collaboratively, merging changes from different developers into the main "production" branch safely. It provides additional features such as bug/issue tracking, continuous integration, feature requests etc. GitHub was acquired by Microsoft in 2018.
|[[wikipedia:GitHub|GitHub]]
|-
|Graph Database
|Graph Databases are used to represent data as elements and their relationships (known as nodes and
edges). They are particularly beneficial when representing large datasets with complex and numerous relationships, such as social media contacts and relations. Unlike a relational database, where to return data it is often necessary to join many tables, in a graph database this isn’t necessary. Relationships are stored natively alongside the data elements enabling much faster querying
|
|-
|HDRUK Phenotype Library
|This is a comprehensive, open access resource which exists to provide the research community with information, tools, and phenotyping algorithms for UK electronic health records (EHRs)
|[https://phenotypes.healthdatagateway.org/ HDR UK Phenotype Library]
|-
|Information Model
|A model describing ontologically standardised data items following a specific database schema within a specific relational database architecture.
It is an abstract model, showing the constraints, relationships, concepts, and data items for a domain.  


'''Total number of distinct person records in the Discovery Data Service = 12,840,983'''
The Discovery Information Model is a representation of the meaning and structure of data held in the electronic records of the health and social care sector. It includes libraries of queries, value sets, concept sets, data set definitions and mappings. The main purpose is to bridge the chasm that exists between highly technical digital representations and plain language so that when questions are asked of data, a lay person could use plain language without prior knowledge of the underlying models.
|[[wikipedia:Information_model|Information Model]]


=== GP practices ===
[[Discovery health information model|DDS IM]]
Total number of distinct GP patient records = 15,758,706


* [[#NEL|North East London]] = 5,444,631
[https://im.endeavourhealth.net/#/ IM Viewer]
*[[#NWL|North West London]] = 5,868,109
* [[#SEL|South East London]] = 4,512,437
* Other = 28,790
{{Note|10 years' of 'left and deads' data is included for inner North East London - City & Hackney, Newham, Tower Hamlets, and Waltham Forest.}}


Total number of GP practices = 850
[https://blog.softwaresuperglue.com/2018/11/09/information-model-vs-data-model/ Information Model vs Data Model]
|-
|Joint Controller Agreement (JCA)
|The arrangements by which a group of data controllers agree to work together to agree the uses of data and how they jointly take responsibility for that.  This is frequently manifested as the development of a representative committee that reviews the five safes, the legal basis for use of personal data, the worthiness of the proposed use of data
|[https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/controllers-and-processors/what-does-it-mean-if-you-are-joint-controllers/ Joint Controllers]
|-
|Knowledge Graph
|An information architecture where concepts are represented as nodes and edges in a network of relationships. This is usually represented in a NoSQL architecture designed to around relationships between concepts.
|
|-
|[[Logical Data Model]]
|The logical data model (or logical schema) describes how data objects relate to each other, but is independent of the technology or database management system used. Logical data models typically show entities (e.g. a patient, an appointment, a result), relationships (e.g. an appointment is linked to a patient via a unique identifier), and attributes (information that is useful to further describe the entities)
|[[wikipedia:Logical_schema|Logical Schema]]
|-
|London Care Record
|A shared care record used for individual care.  It is based on Cerner Health Information Exchange architecture.
|
|-
|Mauro Data Mapper
|Mauro Data Mapper is a third-party toolkit for the design and documentation of databases, data flows, and data standards, as well as related software artefacts such as data schemas and data forms. It was originally developed for the description of data in clinical research.
|[https://maurodatamapper.github.io/about/introduction/ Mauro Data Mapper]
|-
|Medical Classification
|Medical Classifications transform descriptions of procedures or diagnoses into standardised codes through the process of clinical coding. E.g., ICD10, OPCS4, LOINC. These
can also be called code sets. Hence, we call them a medical classification to avoid confusion with Clusters
|[[wikipedia:Medical_classification|Medical Classification]]
|-
|Metadata Library
|A tool that allows management of clusters
|
|-
|NHS Terminology Server
|The NHS Terminology Server “is a FHIR compliant solution that holds and disseminates assured international terminologies and classifications (such as SNOMED-CT and ICD-10) and national terminologies (such as NHS Data Model and Dictionary codes).”
See <nowiki>https://digital.nhs.uk/services/terminology-servers</nowiki>. Content is delivered in machine readable format and can be accessed as a real-time resource through APIs to support other applications.
|[https://digital.nhs.uk/services/terminology-servers NHSD Terminology Server]
|-
|Non-functional Requirements
|These are requirements concerning the operation of a system rather than functionality, and typically relate to security, scalability, performance, reliability etc. Examples include "the page must load within 500ms" or "the website must conform to WCAG AA accessibility standards"
|[[wikipedia:Non-functional_requirement|Non-functional Requirements]]
|-
|Normalisation (health data)
|In healthcare, this is the process of taking data from different sources, in different formats and with different code sets, and converting the data into a singular, unified clinical language or terminology – for example mapping proprietary codes from EPR systems to SNOMED codes
|[https://www.imohealth.com/ideas/article/data-normalization-working-toward-a-common-clinical-terminology/ Healthcare Normalisation]
[https://blog.clinicalarchitecture.com/what-is-data-normalization What is data normalisation?]
|-
|Normalisation (database)
|This is the process of structuring a relational database in accordance with a series of derived rules, called ''normal forms'', in order to reduce redundancy, duplication, and improve data integrity.
|[[wikipedia:Database_normalization|Normalisation]]
|-
|NoSQL Database
|NoSQL stands for Not Only SQL, and is a generic name given to databases which store data in a non-tabular format. They are not relational databases – they may use storage techniques such as key-value pairs, document stores, graph databases. In some cases, SQL can still be used to query them
|
|-
|OMOP Data Model
|OMOP stands for Observational Medical Outcomes Partnership, which was formed to inform the appropriate use of observational healthcare databases. OHDSI (Observational Health Data Sciences and Informatics) is a collaborative that now includes all of the original OMOP research investigators and will continue to develop tools using the OMOP common data model and vocabulary (OMOP is no longer and active programme). 
|[https://www.ohdsi.org/data-standardization/the-common-data-model/ OMOP]
[https://github.com/OHDSI/CommonDataModel/blob/v5.4.0/inst/ddl/5.4/sql_server/OMOPCDM_sql_server_5.4_ddl.sql OMOP Common Data Model (GitHub)]
|-
|On-Premise (On-Prem)
|IT infrastructure build and maintained in-house – for example, database servers sitting in the basement of a hospital building which the IT department maintain and upgrade themselves
|
|-
|Ontology
|An Ontology is a set of concepts and categories showing the relationships and properties between them in a particular domain. In healthcare, and ontology is used for modelling the semantics of medical concepts and to enable the exchange of medical data between systems. The most currently used ontology is SNOMED CT - the DDS ontology is made up of several ontologies (such as READ, CTV3 etc) mapped to SNOMED where appropriate SNOMED terms already exist, and extended where they don't.
A representation, formal naming, and definition of the categories, properties, and relations between the concepts, data, and entities that substantiate one, many, or all domains of discourse (e.g., medicine). Example: Snomed CT.
|[[wikipedia:Ontology_(information_science)|Ontology]]
[https://termbrowser.nhs.uk/ NHSD SNOMED browser]


*[[#NEL|North East London]] = 293
[https://www.snomed.org/ SNOMED.org]
*[[#NWL|North West London]] = 351
*[[#SEL|South East London]] = 204
* Other = 2
{{Note| This also includes closed GP practices.}}


=== Acute services ===
[https://www.england.nhs.uk/digitaltechnology/digital-primary-care/snomed-ct/ SNOMED - NHS England]
 
|-
* Total number of acute patient records = 4,060,479
|OpenCodelists
*[[Category:Data Sets]] Total number of acute services = 3
|OpenCodelists was created by OpenSAFELY for creating and sharing codelists. See "Cluster" definition above.
 
|[https://www.opencodelists.org/ OpenCodelists]
=== Community and Mental Health services ===
[https://www.opensafely.org/ OpenSAFELY]
 
|-
*Total number of Community and Mental Health patient records = 4,185,615
|PESTLE Analysis
*Total number of Community and Mental Health services = 59
|A PESTLE analysis studies the key external factors (Political, Economic, Sociological, Technological, Legal and Environmental) that influence an organisation. It can be used in a range of different scenarios, and can guide people professionals and senior managers in strategic decision-making
 
|[https://www.cipd.co.uk/knowledge/strategy/organisational-development/pestle-analysis-factsheet Pestle Analysis]
=== Other services ===
|-
 
|Physical Data Model
*Total number of other patient records = 2,887,021
|The physical data model describes how a database should be structured and is a representation of table structures, columns, column names, column constraints, primary keys, foreign keys, and any other physical features of the database. A database is an implementation of a physical data model.
*Total number of other services = 20
|[[wikipedia:Physical_schema|Physical Schema]]
 
|-
===<span id="NEL"><span>North East London ===
|Primary Care Reference Set
<table class="borders">
|This is a cluster of codes used within business rules authored and maintained by NHSD's primary care domain.
<tr>
|[https://digital.nhs.uk/data-and-information/data-collections-and-data-sets/data-collections/quality-and-outcomes-framework-qof/quality-and-outcome-framework-qof-business-rules/primary-care-domain-reference-set-portal NHSD Primary Care Domain Reference Set Portal]
<th colspan="3" class="borders" style="border-bottom: solid 1px black">Primary Care GP</th>
|-
<th colspan="2" class="borders" style="border-bottom: solid 1px black">Secondary Care</th>
|Relational Database
<th class="borders" style="border-bottom: solid 1px black">Unscheduled Care</th>
|A Relational database is one where the data is stored in tables, featuring rows and columns and has predefined relationships between the data items. Typically, a table will have a primary key, which is a unique identifier for items in that table. Other tables will reference that primary key for items that are related to it by means of a foreign key. For example, in a table of patients, the primary key might be the NHS number
<th colspan="2" class="borders" style="border-bottom: solid 1px black">Community &amp; Mental Health</th>
|
</tr>
|-
<tr>
|SNOMED CT Concept
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">EMIS Web</td>
|A clinical idea to which a unique concept identifier has been assigned.
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">SystmOne</td>
|[https://confluence.ihtsdotools.org/display/DOCGLOSS/concept SNOMED CT Concept]
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">Vision</td>
|-
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold;">Cerner Millenium</td>
|SQL
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold;">Medway</td>
|A Relational database is one where the data is stored in tables, featuring rows and columns and has predefined relationships between the data items. Typically, a table will have a primary key, which is a unique identifier for items in that table. Other tables will reference that primary key for items that are related to it by means of a foreign key. For example, in a table of patients, the primary key might be the NHS number
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">Adastra</td>
|[[wikipedia:SQL|Structured Query Language]]
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold" ; "border-bottom: solid 1px black";>EMIS Web<br/> Community</td>
|-
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold;" "border-bottom: solid 1px black";>Rio</td>
|SQL Database
</tr>
|A SQL Database is a relational database, which is a collection of tables storing a specific set of structured data, with a fixed schema, which can be queried using SQL
<tr>
|
<td class="borders">Barking & Dagenham<br/>32</td>
|}
<td class="borders">Barking & Dagenham<br/>1</td>
<td class="borders">Havering<br />2</td>
<td class="borders"><ref>ADT feed only.</ref>Homerton Hospital Trust</td>
<td class="borders">BHRUT</td>
<td class="borders">CHUHSE</td>
<td class="borders">Barts Community<br /> Services
9
</td>
<td class="borders"><span style="color: #ff0000;">East London Foundation Trust*</span></td>
</tr>
<tr>
<td class="borders">City &amp; Hackney<br/>40</td>
<td class="borders" style="border-bottom: solid 1px black">Redbridge<br/>6</td>
<td class="noborders"></td>
<td class="borders"><ref>ADT feed plus daily file feed that includes CDE and CDS files.</ref>St Barts Hospital Trust</td>
<td class="noborders"></td>
<td class="borders">Hurley Group</td>
<td class="borders">City &amp; Hackney GP Confederation</td>
<td class="borders"><span style="color: #ff0000;">North East London Foundation Trust*</span></td>
</tr>
<tr>
<td class="borders">Havering<br/>40</td>
<td class="borders">Waltham Forest<br/>5</td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="borders">London Ambulance Service</td>
<td class="borders">Patient First</td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders">Newham<br/>49</td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="borders"><span style="color: #ff0000;">Newham OOH*</span></td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders">Redbridge<br/>36</td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="borders">PELC</td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders">Tower Hamlets<br/>35</td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>           
<tr>   
<td class="borders" style="border-bottom: solid 1px black">Waltham Forest<br/>34</td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
</tr>
</table>
 
===<span id="NWL">North West London<span> ===
<table class="borders">
<tr>
<th colspan="2" class="borders" style="border-bottom: solid 1px black">Primary Care GP</th>
<th class="borders" style="border-bottom: solid 1px black">Secondary Care</th>
<th colspan="2">Community &amp; Mental Health</th>
<th colspan="3"></th>
</tr>
<tr>
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">EMIS Web</td>
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">SystmOne</td>
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold;">Cerner Millenium</td>
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold;" "border-bottom: solid 1px black";>SystmOne<br/> Community</td>
<td class="borders" style="background-color: #37474f;color: #ffffff;font-weight: bold;" "border-bottom: solid 1px black";>EMIS Web<br /> Community</td>
</tr>
 
<tr>
<td class="borders">Brent<br/> 51</td>
<td class="borders">Central London<br/>33 <span style="color: #ff0000;">1*</span></td>
<td class="borders" style="border-bottom: solid 1px black"><span style="color: #ff0000;">Imperial College</span> <span style="color: #ff0000;">Healthcare NHS Trust*</span></td>
<td class="borders">Imperial College Healthcare NHS Trust
 
10
</td>
<td class="borders"><span style="color: #ff0000;">The Confederation -  
Hillingdon CIC
 
1*</span>
</td>
</tr>
 
<tr>
<td class="borders" style="border-bottom: solid 1px black">Ealing<br />1</td>
<td class="borders">Central & North West London NHS Trust
27
</td>
<td class="noborders"></td>
<td class="borders">Chiswick PCN Extended Hours Hub</td>
<td class="borders"><span style="color: #ff0000;">Harrow Covid / GP Access Hub</span></td>
</tr>
 
<tr>
<td class="borders">Harrow<br />33</td>
<td class="borders">Ealing<br />73 <span style="color: #ff0000;">2*</span></td>
<td class="noborders"></td>
<td class="borders">Hammersmitth & Fulham Weekend Plus</td>
<td class="borders">K&W Healthcare</td>
</tr>
<tr>
<td class="borders">Hillingdon<br />43 <span style="color: #ff0000;">2*</span></td>
<td class="borders">Hammersmith &amp; Fulham<br />29</td>
<td class="noborders"></td>
<td class="borders">West London Extended Hours</td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders" style="border-bottom: solid 1px black">Hounslow<br />1</td>
<td class="borders" style="border-bottom: solid 1px black">Hounslow<br />44 <span style="color: #ff0000;">1*</span></td>
<td class="noborders"></td>
<td class="borders" style="border-bottom: solid 1px black">Ealing GP Access Centres</td>
<td class="noborders"></td>
</tr>
<tr>
<td class="noborders"></td>
<td class="borders" style="border-bottom: solid 1px black">West London<br />41</td>
<td class="noborders"></td>
<td class="borders" style="border-bottom: solid 1px black">Hounslow Extended Hours<br />4</td>
<td class="noborders"></td>
</tr>
 
<tr>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="borders" style="border-bottom: solid 1px black">Central London Community Healthcare
40
</td>
<td class="noborders"></td>
</tr>
 
<tr>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
</table>
 
===<span id="SEL"><span>South East London ===
 
<table class="borders">
<tr>
<th colspan="2" class="borders" style="border-bottom: solid 1px black">Primary Care GP</th>
<th class="borders" style="border-bottom: solid 1px black">Unscheduled Care</th>
<th colspan="5"></th>
</tr>
<tr>
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">EMIS Web</td>
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">Vision</td>
<td class="borders" style="background-color: #ff9800;color: #ffffff;font-weight: bold;">Adastra</td></tr>
<tr>
<td class="borders">Bexley<br />18
</td>
<td class="borders">Bexley<br/>4</td>
<td class="borders" style="border-bottom: solid 1px black">London Ambulance Service</td>
</tr>
<tr>
 
<td class="borders">Bromley<br /> 43
</td>
<td class="borders" style="border-bottom: solid 1px black">Greenwich<br/>19</td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders" style="border-bottom: solid 1px black">Greenwich
12
</td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders" style="border-bottom: solid 1px black">Lambeth <br />40</td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders" style="border-bottom: solid 1px black">Lewisham<br /> 34</td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
<tr>
<td class="borders" style="border-bottom: solid 1px black">Southwark<br /> 32</td>
<td class="noborders"></td>
<td class="noborders"></td>
</tr>
</table>
 
Numbers indicate the number of GP practices that are sending live data.
Numbers and text in <span style="color: #ff0000;">red <sup>*</sup></span> indicate data that is not yet live.</p>
{{Note| This does not include closed GP practices.}}
     
'''Last update:''' 4 May 2021
 
'''See also:'''
 
* [[Current data sets]]
*[[Latency of extract data feeds]]
<references />

Revision as of 08:48, 9 May 2022

This is an area of the Wiki for members of the Discovery Collaborative to share definitions of common terms. It is public and can be referenced from other documents and websites as necessary. Please let us know if you would like to challenge or add definitions. simon.meredith@nhs.net or jack.barker@nhs.net

Term Definition External Links
Categories Broad sections of an Ontology or Classification such as the Categories in ICD 10 which contain all ICD 10 codes related to one body part. It might be also be large groupings of test results e.g. Haematology, Biochemistry, Immunology, Microbiology etc. ICD 10
Cloud The Cloud refers to IT infrastructure, platforms, and services that are hosted in a remote data centre, managed by a third party. Typically these data centres are run and managed by large companies such as Microsoft (Azure), Amazon (AWS), and Google (GWP), but there are many other providers too. Using the cloud removes the need for customers to buy and maintain their own physical IT equipment. Instead, the cloud provider typically charges customers daily rates based on storage used, computational power used, memory, number of servers etc Cloud Computing
Cloud Native Cloud Native refers to building software and systems in the cloud that make use of services made available by cloud providers, to run scalable, resilient applications. For example, instead of creating a SQL database on a server in the cloud, which the customer would need to monitor, maintain, patch, back-up etc, they could make use of a “SQL database as a service” from the cloud provider, who would automatically take care of all the maintenance without any further intervention from the customer Cloud Native Computing
Cluster A group of concept codes making another idea. The Cluster may be made up of concepts from different ontologies or classifications e.g., Snomed CT and ICD10. Synonyms for Cluster are refset, value set, codelist, code set, grouper. The name "cluster" was strongly advocated for by John Robson (Clinical Effectiveness Group (CEG) NEL) because of his work in primary care. Primary Care Domain Reference Set Portal
Common Data Model This is the shared Data Model which has been adopted as a standard for an organisation or group. It defines how the elements of data relate to one another and enables data to be transferred between different systems which share the Common Data Model with ease.

It defines the transformation of data from multiple different databases with potentially multiple coding systems into a common storage format (data model) as well as a common representation (terminologies, vocabularies, coding schemes)

Microsoft Example
Concept A coded idea. For example, Name = Baker's Asthma, SNOMED CT code = 34015007
Conceptual Data Model This is a high level model, describing business processes and how they relate to one another. In simple terms, it is a map of concepts and rules relating to the business which can then be used to define relationships between data entities in order to describe the business concepts – this leads to the creation of a logical data model
Data Dictionary A centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format e.g. NHS Data Dictionary. Data Dictionary
Data Model Data models exist at different levels of abstraction, from conceptual data models which are high-level and consider business activity and relationships, to a physical data model which represents the implementation of a database. A data model shows how elements of data relate to one another and how they are structured, how they relate to business needs, and how they can be manipulated. Data Model

NHS Data Model and Dictionary Service

Data Platform A Data Platform is any digital solution which enables an organisation to store, transform, aggregate, and analyse data. It integrates many different technologies for different purposes to meet the data needs of the organisation. It includes security and access controls to ensure IG compliance
Database Index Indexes are used to quickly sort and retrieve data in a database. They may take the form of a physical, clustered index, which is the physical ordering of the data in the table (e.g. by ID or surname), or a non-clustered index which describes the logical ordering of the data separately – like the index at the back of a book: the index key is ordered (e.g. surname) and next to it is information showing where to find the record.
Database Schema This is the definition of the structure of a relational database and defines how data is organised, including the table names, fields (also known as columns), data types, constraints, indexes, and relationships between these entities. The schema is a blueprint of how the database is constructed.
Data Sharing Agreement (DSA) Framework The arrangements for storing and managing data sharing agreements to ensure transparency across controllers and processors. It is likely that the Data Usage Committees/Data Access Groups (Joint Controllers) will generate and store a copy of the DSA, whilst processors and sub-processors will also need a copy.
Data Warehouse A data warehouse stores data for the main purpose of reporting and data analysis. They are central repositories which bring together disparate data sets into one place, to enable reporting at scale and pace. Data Warehouse
DDS Information Model Manager The Information Model Manager is an application developed by the Endeavour Charitable Trust which provides a view of the Common Information Model and supports authoring of the content of the model. It can be used to view the model structure and content, download artefacts (e.g. value sets), and manage the ontology. It can be used to view entities and their relationships (e.g. an A&E admission, which is an Encounter and has a subject of a Patient and has a sub-encounter of a Triage Encounter etc) Discovery Health Information Model
Endeavour Information Model
Expression (Snomed CT) A combination of concepts that represent something that is not already represented as a Concept or Cluster. It typically links things across concepts (disease of infection (finding), with bacteria name (organism), with sepsis (observable entity) with kidney (body structure). Snomed CT Expression
FHIR FHIR stands for Fast Healthcare Interoperability Resources. It is an international standard for health care data exchange and is published by HL7. It is designed to enable the exchange of healthcare related information, including clinical, administrative, publich-health, and research data. DDS stores data in the core in FHIR format before it is restructured and sent to subscriber databases
Functional Requirements These are product features or functionality that must be developed in order for the system to satisfy requirements. They must be implemented in the system in order for it to achieve what it is supposed to accomplish. Examples include "users should be able to download data based on their filtered search criteria" or "only admin-level users should be able to reset passwords for other users" Functional requirement
GitHub GitHub is a provider of version control and source-code management using Git (which is software used for tracking changes in files). It enables software developers to safely store source code and work on it collaboratively, merging changes from different developers into the main "production" branch safely. It provides additional features such as bug/issue tracking, continuous integration, feature requests etc. GitHub was acquired by Microsoft in 2018. GitHub
Graph Database Graph Databases are used to represent data as elements and their relationships (known as nodes and

edges). They are particularly beneficial when representing large datasets with complex and numerous relationships, such as social media contacts and relations. Unlike a relational database, where to return data it is often necessary to join many tables, in a graph database this isn’t necessary. Relationships are stored natively alongside the data elements enabling much faster querying

HDRUK Phenotype Library This is a comprehensive, open access resource which exists to provide the research community with information, tools, and phenotyping algorithms for UK electronic health records (EHRs) HDR UK Phenotype Library
Information Model A model describing ontologically standardised data items following a specific database schema within a specific relational database architecture.

It is an abstract model, showing the constraints, relationships, concepts, and data items for a domain.

The Discovery Information Model is a representation of the meaning and structure of data held in the electronic records of the health and social care sector. It includes libraries of queries, value sets, concept sets, data set definitions and mappings. The main purpose is to bridge the chasm that exists between highly technical digital representations and plain language so that when questions are asked of data, a lay person could use plain language without prior knowledge of the underlying models.

Information Model

DDS IM

IM Viewer

Information Model vs Data Model

Joint Controller Agreement (JCA) The arrangements by which a group of data controllers agree to work together to agree the uses of data and how they jointly take responsibility for that.  This is frequently manifested as the development of a representative committee that reviews the five safes, the legal basis for use of personal data, the worthiness of the proposed use of data Joint Controllers
Knowledge Graph An information architecture where concepts are represented as nodes and edges in a network of relationships. This is usually represented in a NoSQL architecture designed to around relationships between concepts.
Logical Data Model The logical data model (or logical schema) describes how data objects relate to each other, but is independent of the technology or database management system used. Logical data models typically show entities (e.g. a patient, an appointment, a result), relationships (e.g. an appointment is linked to a patient via a unique identifier), and attributes (information that is useful to further describe the entities) Logical Schema
London Care Record A shared care record used for individual care. It is based on Cerner Health Information Exchange architecture.
Mauro Data Mapper Mauro Data Mapper is a third-party toolkit for the design and documentation of databases, data flows, and data standards, as well as related software artefacts such as data schemas and data forms. It was originally developed for the description of data in clinical research. Mauro Data Mapper
Medical Classification Medical Classifications transform descriptions of procedures or diagnoses into standardised codes through the process of clinical coding. E.g., ICD10, OPCS4, LOINC. These

can also be called code sets. Hence, we call them a medical classification to avoid confusion with Clusters

Medical Classification
Metadata Library A tool that allows management of clusters
NHS Terminology Server The NHS Terminology Server “is a FHIR compliant solution that holds and disseminates assured international terminologies and classifications (such as SNOMED-CT and ICD-10) and national terminologies (such as NHS Data Model and Dictionary codes).”

See https://digital.nhs.uk/services/terminology-servers. Content is delivered in machine readable format and can be accessed as a real-time resource through APIs to support other applications.

NHSD Terminology Server
Non-functional Requirements These are requirements concerning the operation of a system rather than functionality, and typically relate to security, scalability, performance, reliability etc. Examples include "the page must load within 500ms" or "the website must conform to WCAG AA accessibility standards" Non-functional Requirements
Normalisation (health data) In healthcare, this is the process of taking data from different sources, in different formats and with different code sets, and converting the data into a singular, unified clinical language or terminology – for example mapping proprietary codes from EPR systems to SNOMED codes Healthcare Normalisation

What is data normalisation?

Normalisation (database) This is the process of structuring a relational database in accordance with a series of derived rules, called normal forms, in order to reduce redundancy, duplication, and improve data integrity. Normalisation
NoSQL Database NoSQL stands for Not Only SQL, and is a generic name given to databases which store data in a non-tabular format. They are not relational databases – they may use storage techniques such as key-value pairs, document stores, graph databases. In some cases, SQL can still be used to query them
OMOP Data Model OMOP stands for Observational Medical Outcomes Partnership, which was formed to inform the appropriate use of observational healthcare databases. OHDSI (Observational Health Data Sciences and Informatics) is a collaborative that now includes all of the original OMOP research investigators and will continue to develop tools using the OMOP common data model and vocabulary (OMOP is no longer and active programme). OMOP

OMOP Common Data Model (GitHub)

On-Premise (On-Prem) IT infrastructure build and maintained in-house – for example, database servers sitting in the basement of a hospital building which the IT department maintain and upgrade themselves
Ontology An Ontology is a set of concepts and categories showing the relationships and properties between them in a particular domain. In healthcare, and ontology is used for modelling the semantics of medical concepts and to enable the exchange of medical data between systems. The most currently used ontology is SNOMED CT - the DDS ontology is made up of several ontologies (such as READ, CTV3 etc) mapped to SNOMED where appropriate SNOMED terms already exist, and extended where they don't.

A representation, formal naming, and definition of the categories, properties, and relations between the concepts, data, and entities that substantiate one, many, or all domains of discourse (e.g., medicine). Example: Snomed CT.

Ontology

NHSD SNOMED browser

SNOMED.org

SNOMED - NHS England

OpenCodelists OpenCodelists was created by OpenSAFELY for creating and sharing codelists. See "Cluster" definition above. OpenCodelists

OpenSAFELY

PESTLE Analysis A PESTLE analysis studies the key external factors (Political, Economic, Sociological, Technological, Legal and Environmental) that influence an organisation. It can be used in a range of different scenarios, and can guide people professionals and senior managers in strategic decision-making Pestle Analysis
Physical Data Model The physical data model describes how a database should be structured and is a representation of table structures, columns, column names, column constraints, primary keys, foreign keys, and any other physical features of the database. A database is an implementation of a physical data model. Physical Schema
Primary Care Reference Set This is a cluster of codes used within business rules authored and maintained by NHSD's primary care domain. NHSD Primary Care Domain Reference Set Portal
Relational Database A Relational database is one where the data is stored in tables, featuring rows and columns and has predefined relationships between the data items. Typically, a table will have a primary key, which is a unique identifier for items in that table. Other tables will reference that primary key for items that are related to it by means of a foreign key. For example, in a table of patients, the primary key might be the NHS number
SNOMED CT Concept A clinical idea to which a unique concept identifier has been assigned. SNOMED CT Concept
SQL A Relational database is one where the data is stored in tables, featuring rows and columns and has predefined relationships between the data items. Typically, a table will have a primary key, which is a unique identifier for items in that table. Other tables will reference that primary key for items that are related to it by means of a foreign key. For example, in a table of patients, the primary key might be the NHS number Structured Query Language
SQL Database A SQL Database is a relational database, which is a collection of tables storing a specific set of structured data, with a fixed schema, which can be queried using SQL