Instructions for importing a batch of DSM Data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →Instructions: header |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 6: | Line 6: | ||
== Instructions == | == Instructions == | ||
=== Prep === | |||
# copy files to local, they are large and won't work well on a share. | # copy files to local, they are large and won't work well on a share. | ||
#* make a new local directory | #* make a new local directory | ||
| Line 11: | Line 12: | ||
#** [[Centralized_data.mdb]] | #** [[Centralized_data.mdb]] | ||
#** [[DSM_Labs_Consistency_check.accdb]] | #** [[DSM_Labs_Consistency_check.accdb]] | ||
#** [[DSM Labs data.accdb]] | |||
#** not needed - [[PHI.mdb]] is not needed during import because it matches by D_ID | #** not needed - [[PHI.mdb]] is not needed during import because it matches by D_ID | ||
# copy the newly received batch of data from [[DSM_Lab_Extract#File_Share]] to directory | # copy the newly received batch of data from [[DSM_Lab_Extract#File_Share]] to a '''different local directory that contains '''only those files''' | ||
=== Check for new labs === | |||
# Open [[DSM_Labs_Consistency_check.accdb]] | # Open [[DSM_Labs_Consistency_check.accdb]] | ||
# | # Click the "Check DSM .csv for new labs " button | ||
# pick the directory with the new data files | |||
# pick the | # wait for the check to complete, about half an hour | ||
# | # 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 | ||
#* If so talk to Tina, we can document that process when it next happens. It involves editing table s_mapping_labs or s_group to accommodate the new data. | |||
=== actual data import === | |||
# Move | 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. | ||
# | |||
=== Cleanup === | |||
# Move files back to their master directories | |||
#** [[DSM_Labs_Consistency_check.accdb]] - only need to move if new labs were found | |||
#** [[DSM Labs data.accdb]] | |||
# enter import date in log below | # enter import date in log below | ||
== Integrity checks after import == | == Integrity checks after import == | ||
Please note here if any are needed. | |||
=== D_IDs in CFE for which no DSM labs exist === | === D_IDs in CFE for which no DSM labs exist === | ||
| Line 40: | Line 48: | ||
=== Duplicate RequestNo === | === Duplicate RequestNo === | ||
Should never happen due to how import works, but can check anyway. | Should never happen due to how import works, but can check anyway. | ||
== Known issues == | == Known issues == | ||
None at this time | |||
== How does it work == | == How does it work == | ||
| Line 53: | Line 59: | ||
<nowiki>* ~~~~~ - imported batch</nowiki> | <nowiki>* ~~~~~ - imported batch</nowiki> | ||
* 17:47, 2018 April 9 (CDT) - imported batch 2016-10-17 and 2018-01-25 | |||
[[Category: DSM Labs Extract]] | [[Category: DSM Labs Extract]] | ||
Revision as of 16:47, 9 April 2018
Preliminary information, this is not active yet
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
- 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
- not needed - PHI.mdb is not needed during import because it matches by D_ID
- copy the newly received batch of data from DSM_Lab_Extract#File_Share to a different local directory that contains only those files
Check for new labs
- Open DSM_Labs_Consistency_check.accdb
- Click the "Check DSM .csv for new labs " button
- pick the directory with the new data files
- wait for the check to complete, about half an hour
- 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
- If so talk to Tina, we can document that process when it next happens. It involves editing table s_mapping_labs or s_group to accommodate the new data.
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.
Cleanup
- Move files back to their master directories
- DSM_Labs_Consistency_check.accdb - only need to move if new labs were found
- DSM Labs data.accdb
- enter import date in log below
Integrity checks after import
Please note here if any are needed.
D_IDs in CFE for which no DSM labs exist
This could happen if
- we have a bad MRN / PHIN
- we change/fix a D_ID after we request data
Template:DiscussionThis could also be true where no labs were sent for, eg a patient who dies shortly after arrival. In the past we would have entered a "no labs" for these. Do we want to do something similar? It would have to be Pagasa that does it. Might be a lot of extra work. Need to review. (ex. wrong D_ID when exported but found it error and so fixed it before the data for import comes back).
D_IDs in DSM data for which no CFE record exists
Could happen if we change/fix a D_ID after requesting. Problem is, we can find if one doesn’t exist, but not if one was changed, but the one that was in the export is actually in present now. Not sure how we would catch that.
Duplicate RequestNo
Should never happen due to how import works, but can check anyway.
Known issues
None at this time
How does it work
Log
eg copy/paste and fill in the following: * ~~~~~ - imported batch
- 17:47, 2018 April 9 (CDT) - imported batch 2016-10-17 and 2018-01-25