Instructions for importing a batch of DSM Data: Difference between revisions
No edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 13: | 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 and also | ### 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) | |||
** That is correct, I add a line in my SAS code to change the unmatched D_ID between the DSM dumped data versus the L_LOG D_IDs. Pagasa was instructed to list down in the L_Problems_D_ID those D_ID she had changed during her data processing task if these D_IDs had already been for DSM request. There will be no entry in the L_Problems_D_ID if any change in D_ID happens before sending a DSM request. So far, SAS finds zero of such case. If in case, SAS finds any record in the requestor not in L_LOG, that is only the time the SAS code assigns a new D_ID to the dumped DSM D_ID so as to be consistent with the L_Log D_ID. --[[User:JMojica|JMojica]] 10:38, 17 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 '''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]]. | ||