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.