Update of D ID to include a laptop identifier: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) (Created page with "This page documents our move to a D_ID that contains a laptop identifier. == Why do we need to do this? == Our D_IDs consist of the site and location and the Pat I...") |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 6: | Line 6: | ||
** tedious for collectors; somewhat error prone, but since this will result in an error on sending rather than data corruption it is somewhat low risk | ** tedious for collectors; somewhat error prone, but since this will result in an error on sending rather than data corruption it is somewhat low risk | ||
** [[HSC EMIP]], | ** [[HSC EMIP]], | ||
* add "fake" locations with a post-fix to make the D_ID unique that way (eg HSC_H4Ha, see [[Property:Collection Location workload designation]] | * add "fake" locations with a post-fix to make the D_ID unique that way (eg HSC_H4Ha, see [[Property:Collection Location workload designation]], [[STB Medicine Workload splitting]]) | ||
{{Discuss | [[STB Medicine Workload splitting]]}} | {{Discuss | [[STB Medicine Workload splitting]]}} | ||
** this means we need additional entries in s_dispo for each laptop/location combination, and analysis of data is somewhat more messy than it needs to be | ** this means we need additional entries in s_dispo for each laptop/location combination, and analysis of data is somewhat more messy than it needs to be |
Revision as of 17:53, 2020 January 9
This page documents our move to a D_ID that contains a laptop identifier.
Why do we need to do this?
Our D_IDs consist of the site and location and the Pat ID/Serial number, e.g. HSC_A4-123. They must be unique. If two collectors wanted to enter for the same ward on two different laptops, we would need to make sure that there are no duplicate D_IDs used. Right now we use two methods for this.
- coordinate to not use same Pat ID/Serial numbers
- tedious for collectors; somewhat error prone, but since this will result in an error on sending rather than data corruption it is somewhat low risk
- HSC EMIP,
- add "fake" locations with a post-fix to make the D_ID unique that way (eg HSC_H4Ha, see Property:Collection Location workload designation, STB Medicine Workload splitting)
- this means we need additional entries in s_dispo for each laptop/location combination, and analysis of data is somewhat more messy than it needs to be
Relates to PatientFollow Project
Related articles
Related articles: |