Check duplicate patient: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) m →Log |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
| DIC_summary = there are no duplicate entries for the same patient ward admission on the laptop at send time | | DIC_summary = there are no duplicate entries for the same patient ward admission on the laptop at send time | ||
| DIC_related_concepts = PHIN; DOB; Chart number; First Name; Last Name; Service tmp entry; Dispo | | DIC_related_concepts = PHIN; DOB; Chart number; First Name; Last Name; Service tmp entry; Dispo DtTm | ||
| DIC_firmness = hard check | | DIC_firmness = hard check | ||
| DIC_timing = | | DIC_timing = | ||
| Line 10: | Line 10: | ||
}} | }} | ||
The same patient should not be on a laptop twice with overlapping | The same patient should not be on a laptop twice with overlapping admission periods. If there is a patient like that you will get an error and you will not be able to [[sending | send]] '''any''' patients. Function Overlap defines what it means for two timeframes to overlap. | ||
== Definition == | == Definition == | ||
Duplicates of the following with overlapping [[ | Duplicates of the following with overlapping first [[Service tmp entry]] / [[Dispo DtTm]]: | ||
* [[Chart number]] | * [[Chart number]] | ||
* [[PHIN]] (except 999999999 for [[PHIN_field#Location_Manitoba_and_no_PHIN]]) | * [[PHIN]] (except 999999999 for [[PHIN_field#Location_Manitoba_and_no_PHIN]]) | ||
| Line 19: | Line 19: | ||
== Log == | == Log == | ||
* 2022-03-31 - updated to use first [[Service tmp entry]] instead of | * 2022-03-31 - updated to use first [[Service tmp entry]] instead of ''Accept DtTm'' | ||
* 2021-01-22 - better labels and included the relevant dates right in the query listing. | * 2021-01-22 - better labels and included the relevant dates right in the query listing. | ||
* 2019-10-27 - changed to only include if recordstatus is complete or incomplete | * 2019-10-27 - changed to only include if recordstatus is complete or incomplete | ||
Latest revision as of 16:52, 21 April 2022
| Data Integrity Checks | |
| Summary: | there are no duplicate entries for the same patient ward admission on the laptop at send time |
| Related: | PHIN, DOB, Chart number, First Name, Last Name, Service tmp entry, Dispo DtTm |
| Firmness: | hard check |
| Timing: | |
| App: | CCMDB.accdb |
| Coding: | functions has_multiples() and overlap() and query Check_pt_multiples |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | date change was rolled out / first applied |
| Backlogged: | true |
The same patient should not be on a laptop twice with overlapping admission periods. If there is a patient like that you will get an error and you will not be able to send any patients. Function Overlap defines what it means for two timeframes to overlap.
Definition
Duplicates of the following with overlapping first Service tmp entry / Dispo DtTm:
- Chart number
- PHIN (except 999999999 for PHIN_field#Location_Manitoba_and_no_PHIN)
- combination of (DOB, First Name, Last Name)
Log
- 2022-03-31 - updated to use first Service tmp entry instead of Accept DtTm
- 2021-01-22 - better labels and included the relevant dates right in the query listing.
- 2019-10-27 - changed to only include if recordstatus is complete or incomplete
Related articles
| Related articles: |