Welcome to the Endeavour Health knowledge base: Difference between revisions

From Endeavour Knowledge Base
No edit summary
Line 2: Line 2:
__TOC__
__TOC__


These articles describe the various technologies underpinning the Endeavour and Discovery open source systems and related operational services which are currently live.  
These articles describe the various technologies underpinning the Endeavour open source technologies which have been adopted and used by a large scale NHS  London Data linkage and normalisation Service covering a population of 7 million registered citizens.  
==Discovery Data Service and information model==
==Data Service and Health Information model==
Discovery is based on the hypothesis that; If health related data is brought together at the level of the individual in close to real time, and stored together at the level of a medium size residential population, and made available via a common data model as part of a common ontology, and then subsequently used for individual and population based decision support, great benefits to health can accrue.
The data service is based on the hypothesis that; If health related data is brought together at the level of the individual in close to real time, and stored together at the level of a medium size residential population, and made available via a common data model as part of a common ontology, and then subsequently used for individual and population based decision support, great benefits to health can accrue.


Discovery consists of a set of technology components that link near real time data from millions of records from thousands of provider organisations, as well as an information model consisting of a set of ontologies and a common data model. All the technologies that have been developed are open source and available for anyone to use.  
The service uses technologies that consist of a set of components that link near real time data from millions of records from thousands of provider organisations, with scores of different formats and code systems and converts them to a single common information model, made up of a super ontology, a data model, ,maps between source data and the common model, sets of concepts sets and value sets for query, and query libraries.  


Discovery forms the basis of an NHS owned data service called the Discovery data service (we like nautical things) , operating across the city of London, covering 3 ICSs and a residential population of 7.5 million citizens. The service seeks to use data as close as possible to its original entry form as entered by health professionals or the citizen themselves, and to use that data as close to real time as the publishers of that data can make available.
All components are open source and are themselves built from open source and open standards such as the semantic web languages, JSON-LD and RESTful APIs. The ontology uses the NHS core ontologies of Snomed-CT and the NHS Data Dictionary, supplemented to accommodate the many local codes and text expressions.


== Information model Components ==
== Information model Components ==
These articles provide information about the software used by Endeavour- Discovery and the information modelling processes that these support.


*[[Discovery health information model|Health Information model]] - An overview of the approach to the Discovery information model,  the purpose, and type of content.
*[[Discovery health information model|Health Information model]] - An overview of the approach to the Health information model,  the purpose, and type of content.
*[[Health Information modelling language|Information model language]] - The Semantic Web languages and domain specific languages used to build the various components of the information models
*[[Health Information modelling language|Information model language]] - The Semantic Web languages and domain specific languages used to build the various components of the information models
*[[Querying data|Real data query]] - The relationship between the various information model artefacts and how actual health and care data in systems would be queried using the models
*[[Querying data|Real data query]] - The relationship between the various information model artefacts and how actual health and care data in systems would be queried using the models
Line 20: Line 19:
*[[GitHub repositories]] - descriptions and information relating to the application source code, .
*[[GitHub repositories]] - descriptions and information relating to the application source code, .


== Services ==
= Applications and APIs =
 
These articles provide information about the applications that have been by the technologies


*[https://wiki.discoverydataservice.org/index.php?title=Welcome_to_the_Discovery_Data_Service_knowledge_base London Discovery data service.] Provides information about the London NHS service that are based on these technologies.
*
* [[ASSIGN- UPRN address match application|ASSIGN - UPRN]]. An address matching application and service that matches addresses held in source systems in various forms, to the addresses made available under license by the Ordnance Survey and Post office, including the assigning of a URPN. The application and service has been jointly developed by the Endeavour Health Charitable trust and Queen Mary's University of London and the Clinical effectiveness Group (CEG)
*[[Information_model_service|Information model services]] - the technical services , such as APIs and apps that enable an model instance to be used or to implement an EHR based on the model or particular data model
*[[Information_model_service|Information model services]] - the technical services , such as APIs and apps that enable an model instance to be used or to implement an EHR based on the model or particular data model
*[[FHIR Get Structured Record API|Get Structured Record API]] - returns a complete patient record in a structured format following GP and Care Connect standards.
*[[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[Case studies|Data Distribution services]] that distribute daily weekly or adhoc small data sets from the Discovery core data stores with examples from 2020
= Applications =
These articles provide information about the applications that have been by the technologies


* [[Information model manager]] - an application designed to provide a view of the common information model, concept sets, value sets and query definitions and support the authoring of the content of the model.
*[[Information model manager]] - an application designed to provide a view of the common information model, concept sets, value sets and query definitions and support the authoring of the content of the model.
*[[FHIR Get Structured Record API|get Structured Record APIs]] - returns a project specific patient record in a structured format using FHIR standards.
*[[Monitoring and alerting]] - provides an overview of the monitoring and alert systems in place.
*[[Monitoring and alerting]] - provides an overview of the monitoring and alert systems in place.


*[[Data Sharing Manager|Data Sharing manager]]- DSM provides a visual representation of data that is being shared and processed and by which organisations, regions, and/or services.
*[[Data Sharing Manager|Data Sharing manager]]- DSM provides a visual representation of data that is being shared and processed and by which organisations, regions, and/or services.
*[[UPRN address match application|ASSIGN- UPRN address matching application -]] a web based application that matches single or batches of hand entered address to authoritative addresses and assigns a unique property reference number.
*[[UPRN address match application|ASSIGN- UPRN address matching application -]] a web based application that matches single or batches of hand entered address to authoritative addresses and assigns a unique property reference number.
*[[Alert Generator]] - a system that generates a patient alert based on a query, sends a notification to recipients and provides recipients with access to a  web application to view the content of the record according to the data set
*[[Alert Generator]] - APIs that generates a patient alert based on a query, sends a notification to recipients and provides recipients with access to a  web application to view the content of the record according to the data set
*[[Case studies|Data Distribution services]] that distribute daily weekly or adhoc small data sets from the linked core data stores with examples from 2020
*
*

Revision as of 10:27, 21 August 2022

These articles describe the various technologies underpinning the Endeavour open source technologies which have been adopted and used by a large scale NHS London Data linkage and normalisation Service covering a population of 7 million registered citizens.

Data Service and Health Information model

The data service is based on the hypothesis that; If health related data is brought together at the level of the individual in close to real time, and stored together at the level of a medium size residential population, and made available via a common data model as part of a common ontology, and then subsequently used for individual and population based decision support, great benefits to health can accrue.

The service uses technologies that consist of a set of components that link near real time data from millions of records from thousands of provider organisations, with scores of different formats and code systems and converts them to a single common information model, made up of a super ontology, a data model, ,maps between source data and the common model, sets of concepts sets and value sets for query, and query libraries.

All components are open source and are themselves built from open source and open standards such as the semantic web languages, JSON-LD and RESTful APIs. The ontology uses the NHS core ontologies of Snomed-CT and the NHS Data Dictionary, supplemented to accommodate the many local codes and text expressions.

Information model Components

  • Health Information model - An overview of the approach to the Health information model, the purpose, and type of content.
  • Information model language - The Semantic Web languages and domain specific languages used to build the various components of the information models
  • Real data query - The relationship between the various information model artefacts and how actual health and care data in systems would be queried using the models
  • Mapping concepts and transforming published data - Introduces the approaches to matching and mapping concepts and the structural maps used in transforming published data,
  • Architectures - A high level overview of the architectures that the technologies contribute to
  • GitHub repositories - descriptions and information relating to the application source code, .

Applications and APIs

These articles provide information about the applications that have been by the technologies

  • Information model services - the technical services , such as APIs and apps that enable an model instance to be used or to implement an EHR based on the model or particular data model
  • Information model manager - an application designed to provide a view of the common information model, concept sets, value sets and query definitions and support the authoring of the content of the model.
  • get Structured Record APIs - returns a project specific patient record in a structured format using FHIR standards.
  • Monitoring and alerting - provides an overview of the monitoring and alert systems in place.
  • Data Sharing manager- DSM provides a visual representation of data that is being shared and processed and by which organisations, regions, and/or services.
  • ASSIGN- UPRN address matching application - a web based application that matches single or batches of hand entered address to authoritative addresses and assigns a unique property reference number.
  • Alert Generator - APIs that generates a patient alert based on a query, sends a notification to recipients and provides recipients with access to a web application to view the content of the record according to the data set
  • Data Distribution services that distribute daily weekly or adhoc small data sets from the linked core data stores with examples from 2020