Instructions for requesting a batch of data from DSM
This article describes how to generate the requestor file for the DSM Lab Extract. The file is stored on a file share that DSM can access. See Instructions for importing a batch of DSM Data for the related import process.
How frequently to request
We will request quarterly.
Initially our DSM contact had concerns about workload and wanted a lower frequency, but then he said "Send on the ‘requestor’ file as often as you want to see the output and I will make the time." (as per email from Alun Carter, Monday, February 06, 2017 10:50)
Instruction/steps for requesting data
|
1 I have to make/fix a connector module for this. |
- copy files to local, they are large and won't work well on a share.
- make a new local directory
- Put the following into the directory
- Centralized_data.mdb -the last one has been fully checked for links
- DSM_Labs_Consistency_check.accdb
- PHI.mdb
- DSM Labs data.accdb
- open DSM Labs Consistency check.accdb
- Reconnect all the tables
- right click L_Log and then click Linked Table Manager
- Click Select all then OK.
- All the tables will need to be connected to the directory you downloaded the files to.
- 0_D_RawData -> dsm_Labs_data.accdb
- 1_C_requester_cc -> dsm_Labs_data.accdb
- 1_D_format_limit -> dsm_Labs_data.accdb
- L_Labs_DSM -> dsm_Labs_data.accdb
- L_Log -> centralized_data
- L_PHI -> PHI.mdb
- s_Dispo -> CCMDB.mdb
- s_group -> dsm_Labs_data.accdb
- s_mapping_lab -> dsm_Labs_data.accdb
- s_mapping_locaitons -> dsm_Labs_data.accdb
- Version1 -> dsm_Labs_data.accdb
- Once you linked all the tables it will tell you" All selected linked tables were successfully refreshed".
- click the "Export requestor file" button
- follow the wizard, which will export a file to the shared folder and start an email to DSM
- close Access and delete files you had copied
- enter at the top of the log below when you requested data, and for what range
missing dispo dates
if at import time a dispo dttm is still missing it will be replaced with Now().
Dependencies
The request process asks for all, and the import process de-duplicates, so there should be no gaps or overlaps.
Requesting Lab DSM
- Need to send quarterly
Log
Put newest entry at the top
| Request Date | SendDtTm range start | SendDtTm range end | Date Imported to Database | Comments |
|---|---|---|---|---|
| 10:03, 2019 March 28 (CDT) | 2019-01-23 | 2019-03-27 am | 2019-4-10 | |
| 16:04, 2019 January 23 (CST) | 2018-10-31 | 2019-01-23 am | 2019-3-9 | |
| 12:00, 2018 October 31 (CDT) | 2018-07-11 | 2018-10-31 am | 2019-3-9 | |
| 14:48, 2018 July 11 (CDT) | 2018-06-19 | 2018-07-11 am | 2019-3-9 | |
| 13:36, 2018 June 19 (CDT) | 2018-04-05 | 2018-06-19 am | 2019-4-10 | |
| 14:29, 2018 April 5 (CDT) | 2018-01-25 | 2018-04-05 am | 2018-5-18 | |
| 14:26, 2018 January 25 (CST) | 2017-10-26 | 2018-01-25 am | 2018-4-9 | |
| 13:51, 2017 October 26 (CDT) | 2016-12-31 | 2017-10-26 am | 2018-4-9 | |
| 14:10, 2017 March 14 (CDT) | 2016-08-30 | 2016-12-31 am | 2017-4-12 ? |
Early requests that followed a different pattern:
- 16:05, 2016 October 17 (CDT) || 2016-08-01 (but use 1980-01-01 for import because first one) until 2016-08-30
- 2015-12-?? - Discharge date 2015-04-01 - 2015-04-30
Related articles
| Related articles: |