DavidStables (talk | contribs) No edit summary |
DavidStables (talk | contribs) No edit summary |
||
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Service information == | == Service information == | ||
Please note that the Discovery data service is maintained by North East London CCG. These articles represent the state as of 2019. | |||
*[[Current data sets|data sets as of 2020]] - the broad types of data received from various systems as of 2020 | |||
*[[Current published data|published data as of 2020]] - provides the latest data publisher information by sector, geographical area, service, and system provided | |||
*[ | |||
*[ | |||
=Publishers and subscribers= | =Publishers and subscribers= | ||
These articles provide some brief high level information for organisations that send data to Discovery and those that use that data. | These articles provide some brief high level information for organisations that send data to Discovery and those that use that data. | ||
*[ | *[[Publishers]] - as of 2020 includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services. | ||
*[ | *[[Subscribers]] - as of 2020 includes set up, data mapping, and schema information. | ||
*[ | *[[Latency of extract data feeds]] includes information on the time between entry into source systems and the availability via the service. | ||
== Example APIs == | == Example APIs == | ||
[ | [[NHS 111 Discovery frailty flagging|NHS 111 Discovery flagging]] / [[Frailty algorithm]] which provides decision support for the NHS 111 service | ||
[[HL7v2 API]] - Send HL7v2 ADT and ORU (clinical events) data to Discovery. | |||
=Application help= | =Application help= | ||
*[ | *[[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. | *: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. | ||
*:[ | *:[[Jira]] - Jira is an effective way to share and track information and helps to make sure that tasks and issues are completed, and signed off, by all relevant teams. | ||
<br /> | <br /> |
Latest revision as of 10:59, 6 January 2022
Service information
Please note that the Discovery data service is maintained by North East London CCG. These articles represent the state as of 2019.
- data sets as of 2020 - the broad types of data received from various systems as of 2020
- published data as of 2020 - provides the latest data publisher information by sector, geographical area, service, and system provided
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 - as of 2020 includes technical interface information, FHIR mapping, system requirements, and how to make changes to publishing services.
- Subscribers - as of 2020 includes set up, data mapping, and schema information.
- Latency of extract data feeds includes information on the time between entry into source systems and the availability via the service.
Example APIs
NHS 111 Discovery flagging / Frailty algorithm which provides decision support for the NHS 111 service
HL7v2 API - Send HL7v2 ADT and ORU (clinical events) data to Discovery.
Application help
- 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.
- Jira - Jira is an effective way to share and track information and helps to make sure that tasks and issues are completed, and signed off, by all relevant teams.