No edit summary |
No edit summary |
||
Line 18: | Line 18: | ||
There are two separate feeds of data that DDS sends to each RSD: | There are two separate feeds of data that DDS sends to each RSD: | ||
* '''Published Data''' '''Feed''' – this includes all patient data, plus some supporting data ( | * '''Published Data''' '''Feed''' – this includes all patient data, plus some supporting data (clinicians and organisations for example) that is sent into DDS by external publishers. | ||
* '''Reference Data''' '''Feed''' – this includes lookups and mappings for clinical codes ( | * '''Reference Data''' '''Feed''' – this includes lookups and mappings for clinical codes (Read2 to Snomed for example) that is not directly published into DDS but is updated in subscriber databases. | ||
Data for each feed is staged in a separate directory on the DDS SFTP server for each subscriber. The DDS Remote Filer application runs supports running in two different modes, one to download and process the '''Published Data Feed''' and the other to download and process the '''Reference Data Feed'''. | Data for each feed is staged in a separate directory on the DDS SFTP server for each subscriber. The DDS Remote Filer application runs supports running in two different modes, one to download and process the '''Published Data Feed''' and the other to download and process the '''Reference Data Feed'''. | ||
{{Warning| If you replace the Remote Filer application with an alternative solution it must support both feeds.}} |
Revision as of 09:07, 10 June 2021
This article describes how the Discovery Data Service makes data available for Remote Subscriber Databases (RSDs) and how the DDS Remote Filer application interacts with this to update an RSD. Although it is recommended that the Remote Filer application be used for updating RSDs, any other technical solution can be substituted provided it is able to match the Remote Filer behaviour as far as the points of interaction are concerned.
Subscriber database schema
DDS currently provides SQL scripts for creating subscriber databases, one for each of the two support database engines; the database scripts are the same no matter what configuration options are selected when setting up the feed from DDS (e.g. PI versus de-identified).
- MySQL
- SQL Server (or compatible, e.g. Azure SQL DB)
Please note the following:
|
Subscriber feeds
There are two separate feeds of data that DDS sends to each RSD:
- Published Data Feed – this includes all patient data, plus some supporting data (clinicians and organisations for example) that is sent into DDS by external publishers.
- Reference Data Feed – this includes lookups and mappings for clinical codes (Read2 to Snomed for example) that is not directly published into DDS but is updated in subscriber databases.
Data for each feed is staged in a separate directory on the DDS SFTP server for each subscriber. The DDS Remote Filer application runs supports running in two different modes, one to download and process the Published Data Feed and the other to download and process the Reference Data Feed.
If you replace the Remote Filer application with an alternative solution it must support both feeds. |