Voror_Wiki - User contributions [en-gb]

MediaWiki:Mainpage

2024-03-21T15:24:20Z

Admin:

Voror Discovery Knowledge Base

Voror Health Platform

2024-03-21T14:32:44Z

Admin:

{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
__TOC__

These articles describe the Voror Discovery Data Service; 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.

=Discovery Data Service status=

* The data service is live and in use in North East, North West, and South East London.
* 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* 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.

= Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Information model topics =

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:

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.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

Voror Health Platform

2024-03-21T14:13:50Z

Admin: /* Discovery Data Service status */

{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
__TOC__

These articles describe the Voror Discovery Data Service; 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.

=Discovery Data Service status=

* The data service is live and in use in North East, North West, and South East London.
* 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* 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.

= Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

File:Voror tree only width135.png

2024-03-20T15:19:22Z

Admin:

File:Voror tree only width350.png

2024-03-20T11:49:58Z

Admin:

Voror Discovery Wiki

2023-10-17T13:05:00Z

Admin: Admin moved page Voror Discovery Wiki to Voror Discovery Knowledge Base

#REDIRECT [[Voror Discovery Knowledge Base]]

Voror Health Platform

2023-10-17T13:05:00Z

Admin: Admin moved page Voror Discovery Wiki to Voror Discovery Knowledge Base

{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
__TOC__

These articles describe the Voror Discovery Data Service; 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.

=Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

Voror Health Platform

2023-10-17T13:04:44Z

Admin: Admin moved page Voror Discovery Knowledge Base to Voror Discovery Wiki without leaving a redirect: revert

{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
__TOC__

These articles describe the Voror Discovery Data Service; 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.

=Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

Voror Health Platform

2023-10-17T13:03:41Z

Admin: Admin moved page Voror Discovery Wiki to Voror Discovery Knowledge Base without leaving a redirect

{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
__TOC__

These articles describe the Voror Discovery Data Service; 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.

=Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

Voror Health Platform

2023-10-17T13:01:32Z

Admin:

{{DISPLAYTITLE:Welcome to the Voror Discovery knowledge base}}
__TOC__

These articles describe the Voror Discovery Data Service; 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.

=Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

File:Voror tree new small.png

2023-10-17T12:50:21Z

Admin:

Voror Health Platform

2023-09-12T12:57:19Z

Admin:

{{DISPLAYTITLE:Welcome to the London Discovery Data Service knowledge base}}
__TOC__

These articles describe the London Discovery Data Service; 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.

=London Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= London Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

Voror Health Platform

2023-09-12T12:56:49Z

Admin: typo

{{DISPLAYTITLE:Welcome to the London Discovery Data Service knowledge base}}
__TOC__

These articles describe the London Discovery Data Service; 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. 3

=London Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= London Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

Voror Health Platform

2023-09-12T12:20:19Z

Admin: fixed typo

Voror Health Platform

2023-09-12T12:19:15Z

Admin: typo

{{DISPLAYTITLE:Welcome to the London Discovery Data Service knowledge base}}
__TOC__

These articles describe the London Discovery Data Service; 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. 1

=London Discovery Data Service status=

* The data service is live.
* It currently stores and processes the data from 39 million linked organisational patient records in the UK.
* It contains long term records on 15.7 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).
* Data on individuals are held in a single common data model with data values represented by a super ontology composed of the world's leading health ontologies.
* Data in Discovery is submitted by health providers who provide primary, secondary, and urgent care services to patients or clients.
* Data is kept up to date in close to real time - at worst within 24 hours; see [[Latency of extract data feeds]] for more details.

= London Discovery overview =

These articles provide background to the ideas, philosophies and approaches that have resulted in the Discovery Data Service. They cover the original objectives, the approach to collaboration and shared tenancy, and the information governance rules that underpin the way privacy and sharing are balanced.

*[[What_is_Discovery|What is Discovery]]? - This article describes what Discovery is and how it is conceptualised at a very high level.
*[[Case studies]] - An overview of some initial projects that access and utilise data from Discovery; information includes the applicant, project summary, and the latest status (Development/Live).
*[[Latest news]] - The latest information for all Discovery Data Service releases and changes, plus known issues and updates from system suppliers and other third parties.
*[[Current_data_sets|Current data sets]] - the broad types of data received from various systems.
*[[Current published data]] - provides the latest data publisher information by sector, geographical area, service, and system provider.

= Information model topics =

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:

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.

= Publishers and subscribers =
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data.

* [[Publishers]] - includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
* [[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 in the Discovery Data Service.

= Services and applications =

These articles provide information about the services and applications provided by the Discovery information services.

* [[Discovery Query|Sextant]] - A data set distribution service with an option to post the data directly into the recipients database.
*[[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.
*[[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.

= 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 [[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]] - 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.

= Wiki tips =

*[[Adding a new page to the wiki]]
*[[Adding tables from word documents]]
*[https://www.mediawiki.org/wiki/Help:Tables Mediawiki Help:Tables]
*[[Creating a DDS wiki watchlist]]
*[[Creating a new user]]
*[https://en.wikipedia.org/wiki/Help:List Wikipedia Help:Lists]
*[[Test page]]

MediaWiki:Mainpage

2020-04-21T12:49:53Z

Admin:

Welcome to the Discovery Data Service knowledge base

Voror Health Platform

2020-04-21T12:46:47Z

Admin: Admin moved page Welcome to the Discovery Data Service resource library to Welcome to the Discovery Data Service knowledge base without leaving a redirect

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.

*[[Secure publication to the DDS]]
*[[Basic health data categories]]
*[[Current data sets]]
*[[Core health data]]
*[[Generic data properties]]
*[[Generic publisher system data requirements]]

Voror Health Platform

2020-04-09T15:45:42Z

Admin:

Health event

2020-04-09T15:41:22Z

Admin:

A health event is an abstract class that refers to any entity type that represents something that has happened, or could happen, at a point in time, or over a period.
It can be considered separate to a 'state' in that the relevant date and time is significant.

{| class="wikitable"
! colspan="2" style="font-weight:bold; background-color:#c0c0c0;" | Health Event
|-
| style="font-weight:bold; background-color:#efefef;" | Field
| style="font-weight:bold; background-color:#efefef;" | Description
|-
| Start date/time
| The start date and time of the event. It might be unknown, or imprecise (for example a year or month). It might be a point in time or a period of time (such as an encounter lasting 15 minutes or a hospital encounter lasting several days). 
For events that take place over a period of time this refers to the start of the event.
|-
| End date/time
| Optional, if recorded at the end of the event.
|-
|}

Health event

2020-04-09T15:07:58Z

Admin:

A health event is an abstract class that refers to any entity type that represents something that has happened, or could happen, at a point in time, or over a period.
It can be considered separate to a 'state' in that the relevant date and time is significant.

{| class="wikitable"
! colspan="2" style="font-weight:bold; background-color:#c0c0c0;" | Provenance
|-
| style="font-weight:bold; background-color:#efefef;" | Field
| style="font-weight:bold; background-color:#efefef;" | Description
|-
| Start date/time
| The start date and time of the event. It might be unknown, or imprecise (for example a year or month). It might be a point in time or a period of time (such as an encounter lasting 15 minutes or a hospital encounter lasting several days). 
For events that take place over a period of time this refers to the start of the event.
|-
| End date/time
| Optional, if recorded at the end of the event.
|-
|}

Observation

2020-04-09T15:06:06Z

Admin:

An observation is considered a type of [[Health event]] that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication. 
An observation in the DDS is much broader than an observation in FHIR and because observations can be highly specialised, like [[Encounter]]s, only the generic properties are illustrated in this article. 
The type of observation is deduced from the observation concept itself, and can be linked at any level of nesting. 
In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, and the other for the result.
The Discovery observation model differs from the FHIR model, which includes both test and result in the same observation. 
For example, a blood pressure would be modelled as 3 observations as follows: 
Observation 1 Blood pressure 
Observation 2 Systolic blood pressure value= 120, part of observation 1 
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Health event

2020-04-09T15:03:14Z

Admin:

A health event is an abstract class referring to any entity type that represents something that has happened, or may happen, at a point in time, or over a period.
It can be considered separate to a “state” in that the relevant date and time is of significance.

{| class="wikitable"
! colspan="2" style="font-weight:bold; background-color:#c0c0c0;" | Provenance
|-
| style="font-weight:bold; background-color:#efefef;" | Field
| style="font-weight:bold; background-color:#efefef;" | Description
|-
| Start date/time
| The start date and time of the event. It might be unknown, or imprecise (for example a year or month). It might be a point in time or a period of time (such as an encounter lasting 15 minutes or a hospital encounter lasting several days). 
For events that take place over a period of time this refers to the start of the event.
|-
| End date/time
| Optional, if recorded at the end of the event.
|-
|}

Health event

2020-04-09T14:58:13Z

Admin: Created page with "A health event is an abstract class referring to any entity type that represents something that has happened, or may happen, at a point in time, or over a period. It can be co..."

Observation

2020-04-09T14:57:52Z

Admin:

An observation is considered a type of [[Health event]] that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication.
An observation in the DDS is much broader than an observation in FHIR. Because observations may be highly specialised, like [[Encounter]]s, only the generic properties are illustrated in this article.
The type of observation is deduced from the observation concept itself.
Observations can be linked at any level of nesting. In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, and the other for the result.
The Discovery observation model differs from the FHIR model, which includes both test and result in the same observation. 
For example, a blood pressure would be modelled as 3 observations as follows: 
Observation 1 Blood pressure 
Observation 2 Systolic blood pressure value= 120, part of observation 1 
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Observation

2020-04-09T14:57:10Z

Admin:

An observation is considered a type of health event that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication.
An observation in the DDS is much broader than an observation in FHIR. Because observations may be highly specialised, like [[Encounter]]s, only the generic properties are illustrated in this article.
The type of observation is deduced from the observation concept itself.
Observations can be linked at any level of nesting. In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, and the other for the result.
The Discovery observation model differs from the FHIR model, which includes both test and result in the same observation. 
For example, a blood pressure would be modelled as 3 observations as follows: 
Observation 1 Blood pressure 
Observation 2 Systolic blood pressure value= 120, part of observation 1 
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Observation

2020-04-09T14:56:55Z

Admin:

An observation is considered a type of health event that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication.
An observation in the DDS is much broader than an observation in FHIR. Because observations may be highly specialised, like [[Encounter]]s, only the generic properties are illustrated in this article.
The type of observation is deduced from the observation concept itself.
Observations can be linked at any level of nesting. In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, and the other for the result.
The Discovery observation model differs from the FHIR model, which includes both test and result in the same observation. 
For example, a blood pressure would be modelled as 3 observations as follows: 
Observation 1 Blood pressure 
Observation 2 Systolic blood pressure value= 120, part of observation 1 
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Observation

2020-04-09T14:54:07Z

Admin:

An observation is considered a type of health event that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication.
An observation in the DDS is much broader than an observation in FHIR. Because observations may be highly specialised, like [[Encounter]]s, only the generic properties are illustrated in this article.
The type of observation is deduced from the observation concept itself.
Observations may be linked at any level of nesting. In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, the other for the result. This varies the Discovery observation model from the FHIR model that includes both test and result in the same observation.
For example, a blood pressure would be modelled as 3 observations as follows:
Observation 1 Blood pressure
Observation 2 Systolic blood pressure value= 120, part of observation 1
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Observation

2020-04-09T14:53:25Z

Admin:

An observation is considered a type of health event that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication.
An observation in the DDS is much broader than an observation in FHIR. Because observations may be highly specialised, like [[encounter]]s, only the generic properties are illustrated in this article.
The type of observation is deduced from the observation concept itself.
Observations may be linked at any level of nesting. In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, the other for the result. This varies the Discovery observation model from the FHIR model that includes both test and result in the same observation.
For example, a blood pressure would be modelled as 3 observations as follows:
Observation 1 Blood pressure
Observation 2 Systolic blood pressure value= 120, part of observation 1
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Observation

2020-04-09T14:52:45Z

Admin: Created page with "An observation is considered a type of health event that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events..."

An observation is considered a type of health event that records some characteristic of the patient or some procedure performed on the patient, but excludes specialised events such as medication.
An observation in the DDS is much broader than an observation in FHIR. Because observations may be highly specialised, like [[encounters]], only the generic properties are illustrated in this article.
The type of observation is deduced from the observation concept itself.
Observations may be linked at any level of nesting. In particular, tests and concept results observations are considered as 2 separate but linked observations, one for the test, the other for the result. This varies the Discovery observation model from the FHIR model that includes both test and result in the same observation.
For example, a blood pressure would be modelled as 3 observations as follows:
Observation 1 Blood pressure
Observation 2 Systolic blood pressure value= 120, part of observation 1
Observation 3 Diastolic blood pressure value= 80, part of observation 2

Encounter

2020-04-09T14:48:29Z

Admin:

An encounter is an interaction between a patient and healthcare provider for the purpose of providing care, including assessment of care needs. Encounters are the mainstay of care provision and the concept covers encounters in any care domain. For example, a GP consultation is an encounter and an in-patient stay is an encounter.
Encounters are often defined according to the publisher’s definition or even the nature of the IT system in use.
In the DDS, an encounter model is a superset of the different encounter models from the different domains and systems. The different patterns are differentiated by the use of Encounter types or archetypes.
For example, a hospital stay would be considered an encounter. The admission and discharge events are also considered an encounter, subsidiary to the hospital stay encounter.
Similarly, an accident and emergency attendance may have a subsidiary encounter for the initial assessment.
The additional properties relating to encounter types (such as method of admission, or critical care function type) are considered as non-core and are referenced via the information model concepts. Each property type has a concept and each value class is considered concept. Consequently these are not specified in this document but are available via the ontology.

{| class="wikitable"
! colspan="2" style="font-weight:bold; background-color:#c0c0c0;" | Encounter: (inherits patient event)
|-
| style="font-weight:bold; background-color:#efefef;" | Field
| style="font-weight:bold; background-color:#efefef;" | Description
|-
| Encounter type
| The overall nature of the encounter mapped to the encounter type ontology.
|-
| Completion status
| Concept: The status of the encounter when the event is sent. It can be completed, ongoing, or planned. In some systems, encounters are created before they start.
|-
| End date/time
| The date or time that the encounter ended.
|-
|Duration
|The duration can be estimated in the absence of an explicit start and end time.
|-
|Providing organisation/services or departments
|Additional department and/or services that define the encounter more fully than the main organisation. For example, an entry could have a main organisation of Royal London, but the encounter took place in the Royal London A&E department.
|-
|Location
|Actual location of the encounter such as a physical building, wing, ward, or room/bed. In most cases this may not be known because the organisation itself implies a location. 
For example, a branch surgery of a GP practice or bed 1, Ward 10.
|-
|colspan="2" style="font-weight:bold; background-color:#efefef; align:left;" | Links
|-
|Linked appointment
|The appointment related to this encounter.
|-
|Subsidiary of
|The encounter that this encounter is part of.
|-
|Linked care episodes
|The care episode that this encounter is linked to.
|-
|Additional practitioners
|Additional practitioners other than the main attributed practitioner involved in this encounter.
|}

Encounter

2020-04-09T14:30:12Z

Admin:

Encounter

2020-04-09T14:27:28Z

Admin:

Encounter

2020-04-09T14:21:05Z

Admin: Created page with "An encounter is an interaction between a patient and healthcare provider for the purpose of providing care, including assessment of care needs. Encounters are the mainstay of..."

Generic publisher system data requirements

2020-04-09T14:15:16Z

Admin:

The Discovery Data Service accepts data in any supplier format, and with any properties (fields) or terminology. However, the data is subject to the following conditions:
#Data submitted to the DDS closely represents the data that is entered into the provider system by the user.
#The provider system supports an event based approach to modelling data such as an [[Encounter]] or [[Observation]].
#The provider system generates indicators of deleted data as well as added data.
#Data submitted to the DDS is internally consistent, including any referential integrity.
#The meaning of field names and values is self-evident or documented.
#Patients, organisations, and health professionals have a reliable internal identifier for tracking the data.
#Patients have been assigned NHS numbers within the publisher environment, or will be assigned NHS numbers in the near future after initial transmission.
#The data is exported at least once a day.

Generic publisher system data requirements

2020-04-09T14:13:20Z

Admin: Created page with "The Discovery Data Service accepts data in any supplier format, and with any properties (fields) or terminology. However, the data is subject to the following conditions: #Dat..."

The Discovery Data Service accepts data in any supplier format, and with any properties (fields) or terminology. However, the data is subject to the following conditions:
#Data submitted to the DDS closely represents the data that is entered into the provider system by the user.
#The provider system supports an event based approach to modelling data such as an encounter or observation.
#The provider system generates indicators of deleted data as well as added data.
#Data submitted to the DDS is internally consistent, including any referential integrity.
#The meaning of field names and values is self-evident or documented.
#Patients, organisations, and health professionals have a reliable internal identifier for tracking the data.
#Patients have been assigned NHS numbers within the publisher environment, or will be assigned NHS numbers in the near future after initial transmission.
#The data is exported at least once a day.

Voror Health Platform

2020-04-09T13:35:59Z

Admin:

Current data sets

2020-04-09T08:45:49Z

Admin:

The following table shows the data sets that are currently published to the DDS by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col" width="8.3%" |Data sets
!colspan="2" width="16.6%" |EMIS Web
!colspan="2" width="16.6%" |SystmOne
!scope="col" width="8.3%" |Vision
!scope="col" width="8.3%" |Adastra
!colspan="4" width="32%" |Cerner Millenium
!scope="col" width="8.3%" |Rio
|-align="center"
! scope="row" |
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Out of hours
| style="width:8.3%" |A&E
| style="width:8.3%" |Inpatient
| style="width:8.3%" |Outpatient
| style="width:8.3%" |ADT Feed
| style="width:8.3%" |Community
|-align="center"
! scope="row"| Allergies
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Appointments
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Care episodes
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Diagnoses
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Documents
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Encounters/consultations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Family history
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Follow ups/diary recall
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Free text
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Immunisations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Inpatient activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Medication
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Non-scheduled activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Outpatient activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Patient demographics
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Problems
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Procedures
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Questions & answers
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Referrals
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Templates
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Test orders
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Test results/Pathology results
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-
|}

'''✔''' = Data sets available and published to the DDS 
'''✗''' = Data sets available but not published to the DDS 
'''!''' = Data sets coming soon 
'''–''' = Not applicable

==Notes==
<references />

Secure publication to the DDS

2020-04-08T16:47:02Z

Admin:

Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:

== SFTP Pull ==

GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.

== SFTP Push ==

The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

== HTTPS Post ==

The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

== MLLP Send ==

Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.

Current data sets

2020-04-08T16:12:50Z

Admin:

The following table shows the data sets that are currently published to the DDS by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col" width="8.3%" |Data sets
!colspan="2" width="16.6%" |EMIS Web
!colspan="2" width="16.6%" |SystmOne
!scope="col" width="8.3%" |Vision
!scope="col" width="8.3%" |Adastra
!colspan="4" width="32%" |Cerner Millenium
!scope="col" width="8.3%" |Rio
|-align="center"
! scope="row" |
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Out of hours
| style="width:8.3%" |A&E
| style="width:8.3%" |Inpatient
| style="width:8.3%" |Outpatient
| style="width:8.3%" |ADT Feed
| style="width:8.3%" |Community
|-align="center"
! scope="row"| Allergies
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Appointments
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Care episodes
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Diagnoses
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Documents
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Encounters/consultations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Family history
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Follow ups/diary recall
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Free text
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Immunisations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Inpatient activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Medication
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''<ref>non-coded</ref>
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Non-scheduled activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Outpatient activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Patient demographics
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Problems
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Procedures
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Questions & answers
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Referrals
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Templates
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Test orders
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Test results/Pathology results
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-
|}

'''✔''' = Data sets available and published to the DDS 
'''✗''' = Data sets available but not published to the DDS 
'''!''' = Data sets coming soon 
'''–''' = Not applicable

==Notes==
<references />

Current data sets

2020-04-08T16:07:14Z

Admin:

The following table shows the data sets that are currently published by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col" width="8.3%" |Data sets
!colspan="2" width="16.6%" |EMIS Web
!colspan="2" width="16.6%" |SystmOne
!scope="col" width="8.3%" |Vision
!scope="col" width="8.3%" |Adastra
!colspan="4" width="32%" |Cerner Millenium
!scope="col" width="8.3%" |Rio
|-align="center"
! scope="row" |
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Out of hours
| style="width:8.3%" |A&E
| style="width:8.3%" |Inpatient
| style="width:8.3%" |Outpatient
| style="width:8.3%" |ADT Feed
| style="width:8.3%" |Community
|-align="center"
! scope="row"| Allergies
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Appointments
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Care episodes
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Diagnoses
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Documents
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Encounters/consultations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Family history
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Follow ups/diary recall
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Free text
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Immunisations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Inpatient activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Medication
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''<ref>non-coded</ref>
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Non-scheduled activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Outpatient activity
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Patient demographics
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Problems
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Procedures
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Questions & answers
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Referrals
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Templates
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Test orders
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-align="center"
! scope="row"| Test results/Pathology results
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color:grey;" |'''–'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color:grey;" |'''–'''
|-
|}

'''✔''' = Data sets available and published to the DDS 
'''✗''' = Data sets available but not published to the DDS 
'''!''' = Data sets coming soon 
'''–''' = Not applicable

==Notes==
<references />

Current data sets

2020-04-08T15:53:16Z

Admin:

The following table shows the data sets that are currently published by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col" width="8.3%" |Data sets
!colspan="2" width="16.6%" |EMIS Web
!colspan="2" width="16.6%" |SystmOne
!scope="col" width="8.3%" |Vision
!scope="col" width="8.3%" |Adastra
!colspan="4" width="32%" |Cerner Millenium
!scope="col" width="8.3%" |Rio
|-align="center"
! scope="row" |
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Primary care community
| style="width:8.3%" |Primary care GP
| style="width:8.3%" |Out of hours
| style="width:8.3%" |A&E
| style="width:8.3%" |Inpatient
| style="width:8.3%" |Outpatient
| style="width:8.3%" |ADT Feed
| style="width:8.3%" |Community
|-align="center"
! scope="row"| Allergies
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Appointments
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Care episodes
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Diagnoses
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Documents
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Encounters/consultations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Family history
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Follow ups/diary recall
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Free text
| style="color: orange;" | '''!'''
| style="color: orange;" | '''!'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Immunisations
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Inpatient activity
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Medication
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''<ref>non-coded</ref>
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
|-align="center"
! scope="row"| Non-scheduled activity
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
|-align="center"
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Outpatient activity
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Patient demographics
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Problems
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Procedures
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
|-align="center"
! scope="row"| Questions & answers
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
|-align="center"
! scope="row"| Referrals
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: red;" |'''✗'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Templates
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Test orders
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
|-align="center"
! scope="row"| Test results/Pathology results
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
|-
|}

==Notes==
<references />

Current data sets

2020-04-08T15:35:58Z

Admin:

Current data sets

2020-04-08T15:19:50Z

Admin:

Current data sets

2020-04-08T15:15:11Z

Admin:

Current data sets

2020-04-08T15:05:19Z

Admin:

Current data sets

2020-04-08T15:03:00Z

Admin:

Current data sets

2020-04-08T14:59:15Z

Admin:

The following table shows the data sets that are currently published by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col" width="8%" | Data sets
!colspan="2" width="16%" | EMIS Web
!colspan="2" width="16%" | SystmOne
!scope="col" width="8%" | Vision
!scope="col" width="8%" | Adastra
!colspan="4" width="32%" | Cerner Millenium
!scope="col" width="8%" | Rio
|-align="center"
! scope="row" |
| Primary care GP
| Primary care community
| Primary care GP
| Primary care community
| Primary care GP
| Out of hours
| A&E
| Inpatient
| Outpatient
| ADT Feed
| Community
|-align="center"
! scope="row"| Allergies
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| style="color: red;" |'''✗'''
|-align="center"
! scope="row"| Appointments
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: red;" |'''✗'''
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| <nowiki>-</nowiki>
| style="color: green;" |'''✔'''
| style="color: green;" |'''✔'''
| style="color: orange;" | '''!'''
|-align="center"
! scope="row"| Care episodes
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Diagnoses
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Documents
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Encounters/consultations
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Family history
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Follow ups/diary recall
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Free text
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Immunisations
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Inpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Medication
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Non-scheduled activity
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Outpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Patient demographics
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Problems
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Procedures
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Questions & answers
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Referrals
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Templates
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Test orders
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Test results/Pathology results
|
|
|
|
|
|
|
|
|
|
|
|-
|}

==Notes==
<references />

Current data sets

2020-04-08T14:49:20Z

Admin:

The following table shows the data sets that are currently published by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col" width="8%" | Data sets
!colspan="2" width="16%" | EMIS Web
!colspan="2" width="16%" | SystmOne
!scope="col" width="8%" | Vision
!scope="col" width="8%" | Adastra
!colspan="4" width="32%" | Cerner Millenium
!scope="col" width="8%" | Rio
|-align="center"
! scope="row" |
| Primary care GP
| Primary care community
| Primary care GP
| Primary care community
| Primary care GP
| Out of hours
| A&E
| Inpatient
| Outpatient
| ADT Feed
| Community
|-align="center"
! scope="row"| Allergies
| ✔ style="color: green;"
| ✔
| ✔
| ✔
| ✔
| <nowiki>-</nowiki>
| ✔
| ✔
| ✔
| ✗
| ✗
|-align="center"
! scope="row"| Appointments
| y
| y
| y
| y
| y
| <nowiki>-</nowiki>
| y
| y
| y
| n
| n
|-align="center"
! scope="row"| Care episodes
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Diagnoses
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Documents
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Encounters/consultations
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Family history
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Follow ups/diary recall
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Free text
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Immunisations
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Inpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Medication
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Non-scheduled activity
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Outpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Patient demographics
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Problems
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Procedures
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Questions & answers
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Referrals
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Templates
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Test orders
|
|
|
|
|
|
|
|
|
|
|
|-align="center"
! scope="row"| Test results/Pathology results
|
|
|
|
|
|
|
|
|
|
|
|-
|}

==Notes==
<references />

Current data sets

2020-04-08T12:49:36Z

Admin:

The following table shows the data sets that are currently published by different supplier systems:

{| class="wikitable" align="center"
|-
!scope="col"| Data sets
!colspan="2"| EMIS Web
! colspan="2"| SystmOne
! scope="col"| Vision
! scope="col"| Adastra
! colspan="4"| Cerner Millenium
! scope="col"| Rio
|-
! scope="row"|
| Primary care GP
| Primary care community
| Primary care GP
| Primary care community
| Primary care GP
| Out of hours
| A&E
| Inpatient
| Outpatient
| ADT Feed
| Community
|-
! scope="row"| Allergies
| y
| y
| y
| y
| y
| y
| y
| y
| y
| y
| y
|-
! scope="row"| Appointments
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Care episodes
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Diagnoses
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Documents
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Encounters/consultations
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Family history
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Follow ups/diary recall
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Free text
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Immunisations
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Inpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Medication
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Non-scheduled activity
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Outpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Patient demographics
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Problems
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Procedures
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Questions & answers
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Referrals
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Templates
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Test orders
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Test results/Pathology results
|
|
|
|
|
|
|
|
|
|
|
|-
|}

==Notes==
<references />

Current data sets

2020-04-08T12:45:09Z

Admin:

The following table shows the data sets that are currently published by different supplier systems:

{| class="wikitable"
|-
!scope="col"| Data sets
!colspan="2"| EMIS Web
! colspan="2"| SystmOne
! scope="col"| Vision
! scope="col"| Adastra
! colspan="4"| Cerner Millenium
! scope="col"| Rio
|-
! scope="row"|
| Primary care GP
| Primary care community
| Primary care GP
| Primary care community
| Primary care GP
| Out of hours
| A&E
| Inpatient
| Outpatient
| ADT Feed
| Community
|-
! scope="row"| Allergies
|y
|y
|y
|y
|y
|-
|y
|y
|y
|n
|n
|
! scope="row"| Appointments
|y
|y
|y
|y
|n
|-
|-
|-
|y
|y
|?
|-
! scope="row"| Care episodes
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Diagnoses
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Documents
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Encounters/consultations
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Family history
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Follow ups/diary recall
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Free text
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Immunisations
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Inpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Medication
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Non-scheduled activity
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Observations<ref>includes signs, symptoms, biological values, and pathology.</ref>
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Outpatient activity
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Patient demographics
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Problems
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Procedures
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Questions & answers
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Referrals
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Templates
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Test orders
|
|
|
|
|
|
|
|
|
|
|
|-
! scope="row"| Test results/Pathology results
|
|
|
|
|
|
|
|
|
|
|
|-
|}

==Notes==
<references />