Welcome to the Endeavour Health knowledge base: Difference between revisions

Revision as of 09:58, 22 March 2024

These articles describe the Endeavour open source technologies and services.

The technologies and services cover the following areas

Decision support services, for example calculating risks of heart disease or stroke
Information models describing the Endeavour information model approach encompassing ontologies, data models, value sets, and queries
Ontology services for using and managing ontologies , data models, value sets
Query and data set services for maintaining feature and query libraries
Address matching and UPRN allocation for single individuals, households or large populations.
Health record APIs. Describes a set of APIs for accessing health records using FHIR.

All of these services have live and development deployments and are free to access.

They all operate in three ways:

Use of web or online user interfaces to enable users to use the services directly. Provides viewing or downloading facilities
User of Web APIs for systems to interoperate so that the resources can be used as part of an integrated offering
Local implementations whereby local code APIs are used instead of Web APIs.

These technologies form part of a broader set technologies, many of which have been used by a large scale NHS London Data linkage and normalisation Service Known as Discovery, covering a population of 7 million registered citizens.

@@ Line 1: / Line 1: @@
-__TOC__
+These articles describe the Endeavour open source technologies and services.
-These articles describe the Endeavour open source information model and various services,  used as part of a broader set of Endeavour open source technologies, which have been adapted and used by a large scale [https://wiki.discoverydataservice.org/index.php?title=Welcome_to_the_Discovery_Data_Service_knowledge_base NHS  London Data linkage and normalisation Service] covering a population of 7 million registered citizens.
+The technologies and services cover the following areas
-==Health Record Data Service and Health Information model==
-The health record 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.
-To make sense of such a large repository of thousands of data types and millions of codes from thousands of providers using dozens of different systems,  it is useful to create a common information model which presents a simpler view but covers most of the data items published by providers.
+* [[Decision support services|Decision support services,]] for example calculating risks of heart disease or stroke
+* [[Information modelling|Information models]] describing the Endeavour information model approach encompassing ontologies, data models, value sets, and queries
+* [[Information model service|Ontology services]] for using and managing ontologies , data models, value sets
+* [[Information model service|Query and data  set services]] for maintaining feature and query libraries
+* [[ASSIGN- UPRN address match application|Address matching and UPRN allocation]] for single individuals, households or large populations.
+* [[FHIR Get Structured Record API|Health record APIs.]] Describes a set of APIs for accessing health records using FHIR.
-Such a model is not an alternative to the health standards based models, instead it is a common model of the models as well as the proprietary data models and codes
+All of these services have live and development deployments and are free to access.
-Having established such a model, it is then possible to construct logical definitions of query and concept sets that can then be used on the data published from the sources.
+They all operate in three ways:
-The services that link and normalise the data  (such as Discovery), can use this model, creating maps between source data and the common model and thus enabling easier and more efficient use of the data,
+# Use of web or online user interfaces to enable users to use the services directly. Provides viewing or downloading facilities
+# User of Web APIs for systems to interoperate so that the resources can be used as part of an integrated offering
+# Local implementations whereby local code APIs are used instead of Web APIs.
-All components of the information model are open source and are themselves built from open source and open standards such as W3C standards.
+These technologies form part of a broader set technologies, many of which have been used by a large scale [https://wiki.discoverydataservice.org/index.php?title=Welcome_to_the_Discovery_Data_Service_knowledge_base NHS  London Data linkage and normalisation Service]  Known as Discovery, covering a population of 7 million registered citizens.
-The content of the model incorporates concepts from a number of recognised sources including:
-a) The main stream health ontology Snomed-CT with extensions to accommodate the unmapped NHS data dictionary attributes, local codes, and code taxonomies such as OPCS, ICD10 as well as the legacy mappings to Read 2.
-b) The main stream data model resources such as FHIR making the IM FHIR compatible via simple transforms.
-c) The main stream query definitions such as QOF enabling the IM to hold definitions of most complex business rules used in query.
-== Information model Components ==
-*[[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 used to build the various components of the information models
-*[[Information model meta model]]. The class model (shapes model) of the classes used to hold the model content.
-*[[Mapping and matching concepts|Mapping concepts and transforming published data]] - Introduces the approaches to matching and mapping concepts and the structural maps used in transforming published data,
-*[[Architectures|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_service|Information model applications and services]] - the applications and 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 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|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.
-*[[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
-*