Instructions for importing a batch of DSM Data

see Instructions for requesting a batch of data from DSM for counterpart

We receive data from DSM that needs to be imported into our main repository.

Instructions

Prep

1. 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
     • DSM_Labs_Consistency_check.accdb
     • DSM Labs data.accdb
     • PHI not needed - PHI.mdb is not needed during import because it matches by D_ID
2. copy the newly received batch of data from DSM_Lab_Extract#File_Share to a different local directory that contains only those filesnot the requestor file.
3. open DSM_Labs_Consistency_check.accdb

Check for new labs

1. Open DSM_Labs_Consistency_check.accdb
2. Click the "Check DSM .csv for new labs " button
3. pick the directory with the new data files
4. wait for the check to complete, about half an hour
5. if the program tells you there are new labs, review them and ask Trish or Allan if any of them should be considered as part of our counts; click "No" for this
   • open the following queries (they are based on labs imported within the last hour)
     • s_group, sort by "added_dt" and review today's only
     • s_mapping_lab, sort by "date_listed" and review today's only
   • If any of the new ones are identified by Trish or Allan as needing to be counted then you have to ask Tina or Julie to add them to the list;
     • the step to add them is to put the name of the lab they will be counted as into the S_group table or S_mapping_lab table as appropriate, but we need to confirm first that this would not result in a double-count
     • if a lab is added, update DSM_data#DSM_results_we_store
   • If NO additional lab, just close it.

actual data import

If the above listed no new labs, or the new labs were resolved, click the "Import DSM .csv" button and follow essentially the same steps as above to import the actual data. Close the file

Run consistency checks

• Open DSM_Labs_Consistency_check.accdb
• Open query Import_request_matcher
• Get the Number of D_ID with no match lab DSM by following the steps below.
  • Go to design view and add the Import DtTm
  • SentDtTm column on criteria put the date you want to ran and change the covered date (Ex Between Mar 27, 2019 and May 13, 2019)
  • Go to pivot table
  • Go to Datasheet view and sort lowest to highest then filter to blanks only
  • Go to External Data then click excel
  • Go to X CCMDB DSM Lab imports Archive_raw then to the folder you want to save
  • Click Export data with formatting and layout then rename Ex. (No_Match_DSM_450.xlsx) then save.

Cleanup

Move files to their permanent homes. Make sure you do all of these!

1. Make a new directory in \\Hsc1msfp0001\med_ccmed\CCMDB\DSM Labs Imports\archive_processed and call it e.g. DSM_2019-03-27
   1. copy (not move) DSM_Labs_Consistency_check.accdb to that new directory
   2. copy (not move) DSM Labs data.accdb to that new directory
2. move (not copy) DSM_Labs_Consistency_check.accdb and DSM Labs data.accdb from your computer to \\Hsc1msfp0001\med_ccmed\CCMDB\DSM Labs Imports\ (not the archive) - this is the master version.
3. move (not copy) the folder of data you processed from the directory it arrived where we share with DSM to the archive_raw directory in the same folder (these are big so they really should be moved, not copied and left in two places)

Log import

Update the log at Instructions for requesting a batch of data from DSM#Log.

Data Integrity Checks (automatic list)

	App	Status
Query Import request matcher	DSM Labs Consistency check.accdb	needs review

queries for which we have no page yet

D_ID related Problems

Duplicate RequestNo for the Incompletes Profiles who are included in the requestor list and send multiple times more than one batch result Same patient has one or more D_ID because

1. there are changes made in the location affecting the D_ID after the requestor list has been sent to DSM
2. the D_ID format has been changed to include Laptop Identifier. Because we are sending the incompletes, the earlier batch has D_ID with laptop ID and when the profile becomes completes and send again, that profile now has Laptop-identifier. This result if duplicate RequestNo

Missing Lab data

Found cases where the range of dates used is between Arrived_DtTm and Dispo_DtTm and not Accept_DtTm and Dispo_DtTm

Known issues

None at this time

How does it work

• Lab identification in the DSM data

Log

Update the log at Instructions for requesting a batch of data from DSM#Log.