Instructions
...
| Child pages (Children Display) |
|---|
The data export section of RDMP allows you to link a cohort and a dataset(s) to extract only those records in a dataset that belong to patients in your cohort.
...
Finally the Data Export Manager supports longitudial versioning of extracts to ensure that changes in column/dataset definitions are rationalised when performing an extract over an extended period of time.
...
Extraction Configuration Model
...
Data Export Manager stores all it’s configuration data for projects in a relational Data Export database. This includes entities such as Projects, Extraction Configurations, Extraction/Release Logs etc. Performing a data extraction starts by identifying a cohort (See Cohort Manager) and importing it into a cohort database. From the perspective of the Data Export Manager tool, a cohort is fundamentally a list of private identifiers of patients which match those stored in your repository. In addition to a unique patient identifier, each patient should have a globally unique and project specific extraction identifier. This project identifier (aka release identifier) will be used as a substitute for the private identifier when the data is extracted and given to a researcher.
...