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 2: / Line 2: @@
 __TOC__
-These articles describe the Voror Health Platform; 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.
+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=
@@ Line 15: / Line 15: @@
 *[[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.
+* [[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.
+= 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.
 = 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.
@@ Line 25: / Line 45: @@
 *[[Case studies]] - An overview of projects that access and utilise data from Discovery.
-= Services and applications =
+= Resources =
-These articles provide information about some of the services and applications included in the Voror Health Platform.
-* [[DDS-UI dashboards|DDS]] - internal DDS-UI dashboards that are used to monitor data flows in to and out of the DDS and provide many back-end DDS management utilities, such as those for setting up new publisher feeds.
-* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
-*[[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.
-*[[FHIR Get Structured Record API]] - returns a complete patient record in a structured format following GP and Care Connect standards.
-*[[HL7v2 API]] - Send HL7v2 ADT and ORU (clinical events) data to Discovery.
-*Get health record - the service that obtains a fully structured health record about a person, in real time via a standards based API.
-*Record publication service - the service that publishes data from health records for specific purposes, often immediately on receipt.
-*Data set distribution service - the service that 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.
-*[[NHS 111 Discovery frailty flagging]] / [[Frailty algorithm]]
 *[[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.
-= Architectures =
-These articles provide information about the overall high level software architecture models providing a descriptions and visualisations of the Discovery Data Service and information service components and how they interact.
-* 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 service and the various implementation options available for organisations that wish to use some or parts of the services.
-*[[Identity Authentication Authorisation|Identity, authentication and authorisation]] specifies the approach taken by Discovery for accessing utilities and controlling some aspects of access to application functionality and some data resources, after all of the other locks have been opened.
-*[[Application zone architecture]] illustrates how the data is accessed in different places and in different ways according to different use cases
-*[[Pseudonymisation]] describes how Discovery generates pseudonymised data.
-*[[Data linking]] describes how Discovery links several patient records into a single person/citizen record.
-= Application help =
-*[[Data_Sharing_Manager|Data Sharing Manager]]&nbsp;-&nbsp;Data Sharing Manager provides a visual representation of data that is being shared and processed and by which organisations, regions, and/or services.
-*:You can also amend or cancel data sharing and processing agreements in real time.
 *[[Record Viewer]] - Record Viewer shows a combined view of an individual's patient records, using data from different source organisations.
@@ Line 63: / Line 56: @@
 *[[Adding tables from word documents]]
 *[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
-*[[Creating a DDS wiki watchlist]]
+*[[Creating a wiki watchlist]]
 *[[Creating a new user]]
 *[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
 *[[Test page]]