Instructions for importing a batch of DSM Data: Difference between revisions

JMojica (talk | contribs)
JMojica (talk | contribs)
 
(11 intermediate revisions by 2 users not shown)
Line 2: Line 2:


We receive data from DSM that needs to be imported into our main repository.  
We receive data from DSM that needs to be imported into our main repository.  
== Instructions Using SAS ==
== Instructions Using SAS ==
The ACCESS Import program stopped working after Feb 9,2024 and a temporary solution using SAS was suggested.
The ACCESS Import program stopped working after Feb 9,2024 and a temporary solution using SAS was suggested.
Line 11: Line 13:
## an excel file containing the unmatched D_IDs
## an excel file containing the unmatched D_IDs
### the worksheet '''DSM_NoDID''' contains the D_ID where PHIN or chart number are not present in the dumped DSM data file.
### the worksheet '''DSM_NoDID''' contains the D_ID where PHIN or chart number are not present in the dumped DSM data file.
### the worksheet '''Log_NoDID''' contains the D_ID in the requestor list but not found in the L_LOG table of CFE.  This happens when the D_ID has been changed for some reason after the request has been sent already. if no D_ID label changing happens, then the worksheet will be empty. If not empty, then the SAS program must be modified to incorporate the D_ID label change.
### the worksheet '''Log_NoDID''' contains the D_ID in the requestor list but not found in the L_LOG table of CFE.  This happens when the D_ID has been changed for some reason after the request has been sent already. if no D_ID label changing happens, then the worksheet will be empty. If not empty, then the SAS program must be modified to incorporate the D_ID label change and  also has to be written in the [[L_Problems_D_ID table]] if not entered yet. Presumably the entry to the L_Problems_D_ID table must precede the SAS output.  
### the worksheet  '''nomatchDSMLab''' contains the D_ID present in the dumped but no LAB dttm or Collect dttm  fall  between the [[Admit date and time]] and [[Dispo DtTm]].  The file has the same columns with the requestor list plus the LOS sorted from highest to lowest.  Shorter LOS (<=2days) may possibly have no lab requests but those with longer LOS may have just missed.  
### the worksheet  '''nomatchDSMLab''' contains the D_ID present in the dumped but no LAB dttm or Collect dttm  fall  between the [[Admit date and time]] and [[Dispo DtTm]].  The file has the same columns with the requestor list plus the LOS sorted from highest to lowest.  Shorter LOS (<=2days) may possibly have no lab requests but those with longer LOS may have just missed.  
### the worksheet '''LOSgt2_resend''' contains the D_IDs with  LOS > 2d to be resent on the '''next batch''' of sending to confirm if really has no lab data.
### the worksheet '''LOSgt2_resend''' contains the D_IDs with  LOS > 2d to be resent on the '''next batch''' of sending to confirm if really has no lab data following the [[Instructions for requesting a batch of data from DSM]].  This step of resending has stopped  07March2025 because the resent profiles still showed no Lab data on the next batch.


=== Step 2 - done by Pagasa ===
=== Step 2 - done by Pagasa ===
Line 28: Line 30:
#* make a new local directory
#* make a new local directory
#* Put the following into the directory
#* Put the following into the directory
#** [[Centralized_data.mdb]]  
#** [[Centralized_data.accdb]]  
#** [[DSM_Labs_Consistency_check.accdb]]
#** [[DSM_Labs_Consistency_check.accdb]]
#** [[DSM Labs data.accdb]]
#** [[DSM Labs data.accdb]]
Line 125: Line 127:
{{Related Articles}}
{{Related Articles}}


[[Category: DSM Labs Extract]]
[[Category:DSM Labs Extract]]