Changing D IDs: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 2: | Line 2: | ||
== Why you might change a D_ID == | == Why you might change a D_ID == | ||
* patient was sent with wrong [[Service/Location]] | |||
*For incorrect location ICU can catch through TISS. | *For incorrect location ICU can catch through TISS. | ||
{{Discuss | who=Pagasa | question = | {{Discuss | who=Pagasa | question = | ||
Revision as of 23:35, 6 February 2019
The D ID field links all our data for a single patient ward-stay together. When it needs to be changed, the change needs to be done to several different places to make sure everything stays connected.
Why you might change a D_ID
- patient was sent with wrong Service/Location
- For incorrect location ICU can catch through TISS.
|
For Medicine you can catch through linking error checks by the Previous location and Dispo field, but if single admission no way of knowing .
|
Instructions
|
If the D ID field is changed anywhere, it needs to be changed in the other locations as well:
- L_Log table in Centralized data.mdb (this will automatically change the related L-tables
- L_PHI table in PHI.mdb
|
How about L TISS Form table, L TISS Item table and L Labs DSM table? Are there others I am not thinking about ? Ttenbergen 22:20, 2019 February 6 (CST) |
Related articles
| Related articles: |