Changing D IDs: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
PTorres (talk | contribs)
No edit summary
PTorres (talk | contribs)
No edit summary
Line 1: Line 1:
[[D_ID]]s might need to be changed ...when?  
[[D_ID]]s might need to be changed ...when?  
**Incorrect D_ID that already sent I can crossed checks through Tiss. For Med. you can catch through linking error checks but if single admission no way of knowing it that is incorrect serial number.
**Incorrect D_ID that already sent I can crossed checks through Tiss. For Med. you can catch through linking error checks by using the Previous location and Dispo field, but if single admission no way of knowing it that is incorrect serial number.
**To fixed it go to L_Log change it to "D_ID" then to the Pat_ID.
**To fixed it go to L_Log change it to "D_ID" then to the Pat_ID.
**Then you have to go to L_PHI and change to D_ID.   
**Then you have to go to L_PHI and change to D_ID.   

Revision as of 08:23, 1 June 2018

D_IDs might need to be changed ...when?

    • Incorrect D_ID that already sent I can crossed checks through Tiss. For Med. you can catch through linking error checks by using the Previous location and Dispo field, but if single admission no way of knowing it that is incorrect serial number.
    • To fixed it go to L_Log change it to "D_ID" then to the Pat_ID.
    • Then you have to go to L_PHI and change to D_ID.

Template:Discussion Are they ever changed once originally entered? If so, what are the steps to make sure that noting in e.g. TISS or DSM data is left behind? Need to discuss with Pagasa and Julie. Ttenbergen 11:59, 2017 September 18 (CDT)

  • Yes there are errors with location and sometimes serial number after collectors sent that I catch when I am cleaning.PTorres
    • Then we need the steps here, since it has to be done in many places so that DSM and TISS and PHI (and more?) don't get disconnected. Ttenbergen 16:47, 2018 May 31 (CDT)