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

(17 intermediate revisions by 2 users not shown)

Line 2:

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

== Instructions Using SAS ==

The ACCESS Import program stopped working after Feb 9,2024 and a temporary solution using SAS was suggested.

=== Step 1- done by Julie ===

# In the batch folder of the current DSM data, create a subfolder labeled JM and save the SAS program labeled DSM_import_version2.sas

# Run the SAS program and the outputs are ~~as follows~~:

# Run the SAS program and the following outputs are generated:

## an excel file containing New labs is exported. The list has to be emailed to Allan Garland for confirmation. If new labs appear, Julie will add them to the SAS codes and re-run the SAS program.

## an excel file containing the matching DSM labs using the criteria that either the LAB dttm or Collect dttm is between the [[Admit date and time]] and [[Dispo DtTm]].

## an excel file containing the matching DSM labs using the criteria that either the LAB dttm or Collect dttm is between the [[Admit date and time]] and [[Dispo DtTm]] in worksheet '''MatchDSM'''.

## 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. ~~Thus, those~~ with ~~longer~~ LOS >~~= 3d is going~~ to be ~~included~~ on the next batch of sending to confirm if really has no lab data.

### 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 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 ===

# Open the DSM_Labs_data.accdb

Line 26:

Line 30:

#* make a new local directory

#* Put the following into the directory

#** [[Centralized_data.~~mdb~~]]

#** [[Centralized_data.accdb]]

#** [[DSM_Labs_Consistency_check.accdb]]

#** [[DSM Labs data.accdb]]

Line 123:

Line 127:

[[Category: DSM Labs Extract]]

[[Category:DSM Labs Extract]]

@@ Line 2: / Line 2: @@
 We receive data from DSM that needs to be imported into our main repository.
 == Instructions Using SAS ==
 The ACCESS Import program stopped working after Feb 9,2024 and a temporary solution using SAS was suggested.
 === Step 1- done by Julie ===
 # In the batch folder of the current DSM data, create a subfolder labeled JM and save the SAS program labeled DSM_import_version2.sas
-# Run the SAS program and the outputs are as follows:
+# Run the SAS program and the following outputs are generated:
 ## an excel file containing New labs is exported. The list has to be emailed to Allan Garland for confirmation. If new labs appear, Julie will add them to the SAS codes and re-run the SAS program.
-## an excel file containing the matching DSM labs using the criteria that either the LAB dttm or Collect dttm  is between the [[Admit date and time]] and [[Dispo DtTm]].
+## an excel file containing the matching DSM labs using the criteria that either the LAB dttm or Collect dttm  is between the [[Admit date and time]] and [[Dispo DtTm]] in worksheet '''MatchDSM'''.
 ## 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. Thus, those with longer LOS >= 3d  is going to be included on the next batch of sending to confirm if really has no lab data.
+### 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 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 ===
 # Open the DSM_Labs_data.accdb
@@ Line 26: / Line 30: @@
 #* make a new local directory
 #* Put the following into the directory
-#** [[Centralized_data.mdb]]
+#** [[Centralized_data.accdb]]
 #** [[DSM_Labs_Consistency_check.accdb]]
 #** [[DSM Labs data.accdb]]
@@ Line 123: / Line 127: @@
 {{Related Articles}}
-[[Category: DSM Labs Extract]]
+[[Category:DSM Labs Extract]]