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

(7 intermediate revisions by 2 users not shown)

Line 13:

## 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 '''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 ~~they are~~ to be written in the [[L_Problems_D_ID table]].

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

~~{{DJ |~~

* Thanks for updating, but I don't understand... I thought the ~~whole idea with having them in L_Problems_D_ID would be that that is the actual data used~~ to do the ~~translation from one ID to~~ the ~~other. Do you mean you actually hard-code it in~~ SAS ~~instead? I ask because you say you need to modify the SAS program to incorporate the change~~. ~~[[User:Ttenbergen|Ttenbergen]] 21:47, 14 March 2025 (CDT)~~

}}

### 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]].

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

Line 33:

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 130:

Line 127:

[[Category: DSM Labs Extract]]

[[Category:DSM Labs Extract]]

@@ Line 13: / Line 13: @@
 ## 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 '''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 they are to be written in the [[L_Problems_D_ID table]].
+### 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.
-{{DJ |
-* Thanks for updating, but I don't understand... I thought the whole idea with having them in L_Problems_D_ID would be that that is the actual data used to do the translation from one ID to the other. Do you mean you actually hard-code it in SAS instead? I ask because you say you need to modify the SAS program to incorporate the change. [[User:Ttenbergen|Ttenbergen]] 21:47, 14 March 2025 (CDT)
-}}
 ### 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]].
+### 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 ===
@@ Line 33: / 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 130: / Line 127: @@
 {{Related Articles}}
-[[Category: DSM Labs Extract]]
+[[Category:DSM Labs Extract]]