Developing for Discovery

From Discovery Data Service
Revision as of 13:12, 14 May 2021 by JoC (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

See Working with Discovery if you want to work with Discovery and need to know where to start.

Other useful topics include:

Services and applications

These articles provide information about the services and applications provided by the Discovery Data Service and the underlying functionality.

  • 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.
  • Information model manager - an application designed to provide a view of the common information model, and support the authoring of the content of the model.
  • Information model services - the technical services that enable the common information model to be used.
  • 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 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.