Changing D IDs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ttenbergen (talk | contribs) m Text replacement - "Centralized data.mdb" to "Centralized data.accdb" |
||
| Line 6: | Line 6: | ||
== Instructions == | == Instructions == | ||
If the [[D ID field]] is changed anywhere, it needs to be changed in the other locations as well: | 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. | * [[L_Log table]] in [[Centralized data.accdb]] (this will automatically change the related [[L-tables]] | ||
* [[L_PHI table]] in [[PHI.mdb]] | * [[L_PHI table]] in [[PHI.mdb]] | ||
Revision as of 13:41, 23 July 2025
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
This used to be a common occurrence following certain patterns, but is only done ad-hoc in rare and unique scenarios now.
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.accdb (this will automatically change the related L-tables
- L_PHI table in PHI.mdb
For older records, the following would also need to be changed:
Related articles
| Related articles: |