Latest revision as of 11:36, 28 November 2024

The Voror Health Platform wiki provides a technical overview of the architecture that underpins the data service, the components that make up the service, the testing and assurance processes, and the resources, open source technologies, and software that are used to host, develop, and support the service.

Overview

What is the Voror Health Platform?
Data is kept up to date in close to real time - at least within 24 hours; see Latency of extract data feeds for more details.

Data publishers and subscribers

These articles provide information for organisations that send data, and those that use that data.

Publishers - includes technical interface information, FHIR mapping, system requirements.
Subscribers - includes set up, data mapping, and schema information.
National data opt-out - includes information on the NHS national data opt-out and how this is applied.

Services and applications

These articles provide information about some of the services and applications included in the Voror Health Platform.

NHS 111 Discovery frailty flagging / Frailty algorithm
FHIR Get Structured Record API - returns a complete patient record in a structured format following GP and Care Connect standards.
****Remote subscriber database**** - contains published data from health records for specific purposes, often immediately on receipt, and where the subscriber is hosting a copy of the data permanently.
Sextant - distributes sets of data for populations of patients where the definition is complex or where the subscriber is hosting a copy of the data permanently.
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.
HL7v2 API - Send HL7v2 ADT and ORU (clinical events) data.
DDS-UI dashboards - used to monitor data flows in to and out of the health platform and provide back-end management utilities.
Data Sharing manager- the IG controller used to manage data processing and data sharing agreements.

Architectures

The health information model services are maintained as open source by the Endeavour health charitable trust. They use standard W3C semantic web languages to model health data, concepts, sets, and queries, thus maintaining compatibility with the main stream technologies.
The Data Storage Architecture illustrates how data is stored within the health platform.
Identity, authentication and authorisation**** specifies the approach taken to access utilities, applications, and data resources.
Application zone architecture**** illustrates how the data is accessed in different places and in different ways according to different use cases.
Pseudonymisation describes how pseudonymised data is generated.
Data linking describes how multiple patient records are linked to a single person/citizen record.

The Voror Health Platform in London - The Discovery Data Service

The data service has been live and in use in North East, North West, and South East London since 2016.
It currently stores and processes the data from over 35 million linked organisational patient records in the UK.
It contains long term records on over 15 million unique UK citizens who have been resident in London at some point in the last 30 years (including people who have left or died).
Current published data - provides the latest data publisher information.
Current data sets - the types of data received from publisher systems.
Case studies - An overview of projects that access and utilise data from Discovery.

Resources

GitHub repositories - descriptions and information relating to the application source code.
Data Sharing Manager publisher/project set up - instructions to set up data sharing and data processing agreements.
Record Viewer - Record Viewer shows a combined view of an individual's patient records, using data from different source organisations.

Wiki tips

@@ Line 1: / Line 1: @@
+{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
+__TOC__
-The articles describe and define Discovery Data Service functionality and technology; the architecture that underpins the data service software, the components that make up the service, the testing and assurance processes, and the resources, technologies, and software that are used to host, develop, and support the service.
+The Voror Health Platform wiki provides a technical overview of the architecture that underpins the data service, the components that make up the service, the testing and assurance processes, and the resources, open source technologies, and software that are used to host, develop, and support the service.
-Types of articles&nbsp;are described below
+=Overview=
-&nbsp;
+* [[What is the Voror Health Platform?]]
+* Data is kept up to date in close to real time - at least within 24 hours; see [[Latency of extract data feeds]] for more details.
-== Information model related topics ==
+= Data publishers and subscribers =
+These articles provide information for organisations that send data, and those that use that data.
-These articles provide information about the services, structure, and functionality&nbsp;that operate using the Discovery Common Information Model;&nbsp;one of the fundamental tenets of the Discovery Data Service. This is the starting point for those interested in health data and the information derived from it, and why Discovery may be different from other approaches:
+*[[Publishers]] - includes technical interface information, FHIR mapping, system requirements.
+*[[Subscribers]] - includes set up, data mapping, and schema information.
+*[[National data opt-out]] - includes information on the NHS national data opt-out and how this is applied.
-*[[Basic_health_data_categories|Basic types of health data]]&nbsp;- a very high level overview of the types of data held within the Discovery data stores
+= Services and applications =
-*[[Information_model_service|Information model services]] - the technical services that enable the common information model to be used
-*[[Current_data_sets|Current data sets]]&nbsp;- the broad types of data received from various systems
+These articles provide information about some of the services and applications included in the Voror Health Platform.
-== Operational and interoperability topics ==
+* [[NHS 111 Discovery frailty flagging]] / [[Frailty algorithm]]
+* [[FHIR Get Structured Record API]] - returns a complete patient record in a structured format following GP and Care Connect standards.
+* ****Remote subscriber database**** - contains published data from health records for specific purposes, often immediately on receipt, and where the subscriber is hosting a copy of the data permanently.
+* [[Discovery Query|Sextant]] - distributes sets of data for populations of patients where the definition is complex or where the subscriber is hosting a copy of the data permanently.
+* [[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.
+* [[HL7v2 API]] - Send HL7v2 ADT and ORU (clinical events) data.
+* [[DDS-UI dashboards|DDS-UI dashboards]] - used to monitor data flows in to and out of the health platform and provide back-end management utilities.
+*[[Data Sharing Manager|Data Sharing manager]]- the IG controller used to manage data processing and data sharing agreements.
-These articles provide information about how systems can interoperate with Discovery and provide further links into test APIs, schemas, and other documentation associated with data formats for sending and receiving data.
+= Architectures =
+* The [https://wiki.endeavourhealth.org/index.php?title=Welcome_to_the_Endeavour_Health_knowledge_base health information model services] are maintained as open source by the Endeavour health charitable trust. They use standard W3C semantic web languages to model health data, concepts, sets, and queries, thus maintaining compatibility with the main stream technologies.
+* The [[Data Storage Architecture]] illustrates how data is stored within the health platform.
+* [[Identity Authentication Authorisation|Identity, authentication and authorisation]]**** specifies the approach taken to access utilities, applications, and data resources.
+* [[Application zone architecture]]**** illustrates how the data is accessed in different places and in different ways according to different use cases.
+*[[Pseudonymisation]] describes how pseudonymised data is generated.
+*[[Data linking]] describes how multiple patient records are linked to a single person/citizen record.
-*[[Secure_publication_to_the_DDS|Secure publication to the DDS]]&nbsp;- lists the technical interfaces in place for receiving data from publishers.
+= The Voror Health Platform in London - The Discovery Data Service =
-*[[Remote_Subscriber_Database_(RSD)_SQL_guide|Remote Subscriber Database (RSD) SQL guide]]&nbsp;- provides information for subscribers that wish to host their own copy of data supplied by Discovery.
+*The data service has been live and in use in North East, North West, and South East London since 2016.
-*[[Generic_publisher_system_data_requirements|Generic publisher system data requirements]]&nbsp;- provides a set of guides for systems that are publishing data through the Discovery Data Service.
+* It currently stores and processes the data from over 35 million linked organisational patient records in the UK.
+* It contains long term records on over 15 million unique UK citizens who have been resident in London at some point in the last 30 years (including people who have left or died).
+*[[Current published data]] - provides the latest data publisher information.
+*[[Current data sets]] - the types of data received from publisher systems.
+*[[Case studies]] - An overview of projects that access and utilise data from Discovery.
+= Resources =
-== Services ==
+*[[GitHub repositories]] - descriptions and information relating to the application source code.
+*[[Data Sharing Manager#Data Sharing Manager publisher/project set up – high level overview|Data Sharing Manager publisher/project set up]] - instructions to set up data sharing and data processing agreements.
+*[[Record Viewer]] - Record Viewer shows a combined view of an individual's patient records, using data from different source organisations.
-These articles provide information about the services provided by the Discovery Data Service and the underlying functionality.
+= Wiki tips =
-*[[Simple_generic_query_service|Simple Generic query Service]]&nbsp;- describes a service that provides data on request for data&nbsp;that might be conceptually very complex, but falls into simple common patterns.
+*[[Adding a new page to the wiki]]
-*Get health record -&nbsp;describes the service that obtains a fully structured health record about a person, in real time via a standards based API.
+*[[Adding tables from word documents]]
-*Record publication service -describes the service that publishes data from health records for specific purposes, often immediately on receipt.
+*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
-*Data set distribution service -&nbsp;describes the service that distributes sets of data for populations of patients.
+*[[Creating a wiki watchlist]]
+*[[Creating a new user]]
-&nbsp;
+*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
+*[[Test page]]
-== Technologies ==
-These articles provide information about the technologies used in the Discovery Data services including summaries of considerations and tests that have been undertaken when selecting technologies
-*[[Graph_or_relational_databases|Graph versus relational database&nbsp;]] Considers two of the approaches for storing the main health care record stores
-&nbsp;
-&nbsp;
-&nbsp;