Search results

This article provides the latest data publisher information by sector, geographical area, service, and system pro '''Total number of distinct person records in the Discovery Data Service = 16,004,157'''

...t organisational data and either patient identifiable data or deidentified data dependent on your permissions. These are controlled by your local administr ...es that let you drill down at practise level and view patient identifiable data from queries that you build.

..., in context e.g. a value set in VM Viewer to definition in ontology and data model property range to value set etc === Data model module ===

This Discovery data storage architecture is described in this article. The model presented here ...objective of the storage architecture is to align the physical aspects of data storage to the governance and ownership arrangements in a way that enables

...segment various segment definitions may be refined to take account of the data needed to complete the business function associated with the message. More ...ter case it is recommended that publishers take note of the suggested code sets as in the future it might be that these fields are interpreted by DDS and t

...ment specifies the technical details for accessing and using the Discovery Data Service FHIR® Care Connect API, for the use by interoperability system sup ...om combined primary, secondary, unscheduled and community health care data sets (https://discoverydataservice.org/Content/Overview.htm)

...ment specifies the technical details for accessing and using the Discovery Data Service HL7v2 API, for the use by interoperability system suppliers develop ...om combined primary, secondary, unscheduled and community health care data sets (https://discoverydataservice.org/Content/Overview.htm)

Here the data that is published already contains the core DDS codes i.e. the mapping sche Here the mapping scheme is applied when your data reaches the DDS i.e. local codes leave your system and are pushed in to DDS

This article describes the DDS inbound pipeline that takes raw data from publishers and transforms them to a standard format. '''Input''': CSV, TSV, fixed-width, HL7v2 data from multiple publishers.

...et data sets conform to a data model. Either the source or the destination data models (or both) may be implemented as either relational or graph or both. ...he maintenance of data maps themselves and the applications that transform data. As well as the technical separation it separates the business of map produ

|Canonical Data Model ...form. It is a design pattern which allows communication between different data formats. ''Canonical'' form describes the simplest representation of an obj

...tabase management systems  in its main population patient record data stores. A third option is to consider a model whereby the model of the data is conceptualised as a graph (or perhaps an OWLY graph to accommodate subsu

...ts that are supported by the DDS Publisher API. The majority of these code sets have previously been published by NHS Digital as part of the [https://isd.d |Encapsulated Data

The language is used to support some of the data access authorisation processes as described in the specification - [[Identi ...iscovery/InformationManager/tree/master/datafiles/json information manager data files folder]

The Discovery Data Service (DDS) enables access to data the data having been sent to Discovery by providers of healthcare services. ...e data is sensitive personal data. In order to protect the privacy of that data, DDS operates a ''triple lock'' approach, which can be summarised as follow

...cal implementation of any new inbound transform of data into the Discovery Data Service (DDS), specifically for non-transactional flat file formats. * How will the source data be sent to DDS? Will it be an SFTP push or pull? Will the files be encrypte

This article describes the mapping of EMIS published data into the intermediate FHIR store. ! scope="col" width="15%" |Data/Coding Type

Discovery Data Service contains health and care-related data. These articles describe the nature of the types of data currently held by the data service