Check duplicate patient: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 5: | Line 5: | ||
| DIC_app = CCMDB.mdb | | DIC_app = CCMDB.mdb | ||
| DIC_coding = functions ''has_multiples()'' and ''overlap()'' and query ''Check_pt_multiples'' | | DIC_coding = functions ''has_multiples()'' and ''overlap()'' and query ''Check_pt_multiples'' | ||
| DIC_status = | | DIC_status = needs review | ||
| DIC_implementation_date = date change was rolled out / first applied | | DIC_implementation_date = date change was rolled out / first applied | ||
}} | }} | ||
| Line 12: | Line 12: | ||
== Definition == | == Definition == | ||
Duplicates of the following with overlapping | Duplicates of the following with overlapping [[Arrive DtTm]] / [[Dispo DtTm]]: | ||
* [[Chart number]] | * [[Chart number]] | ||
* [[PHIN]] | * [[PHIN]] | ||
* combination of ([[DOB]], [[First Name]], [[Last Name]]) | * combination of ([[DOB]], [[First Name]], [[Last Name]]) | ||
{{Discuss | who=Tina | question = | |||
* Confirm whether Arrive or Accept DtTm is appropriate here, and what is implemented}} | |||
==Error scenario== | ==Error scenario== | ||
| Line 22: | Line 25: | ||
Serial# 15268 & 15306 no obvious problem other than MB Province both had PHIN# 999999999. Collector solution ended up being to changed one PHIN to 123456789. | Serial# 15268 & 15306 no obvious problem other than MB Province both had PHIN# 999999999. Collector solution ended up being to changed one PHIN to 123456789. | ||
*The correct data collection process if province is MB and no PHIN go to: [[PHIN field]]. Staff sent link to collection instructions & main office review also. | *The correct data collection process if province is MB and no PHIN go to: [[PHIN field]]. Staff sent link to collection instructions & main office review also. | ||
{{Discuss | who=Tina | question = | |||
* We need to accommodate the 99999999 used when [[PHIN_field#Location_Manitoba_and_no_PHIN]]. Ttenbergen 16:35, 2018 September 11 (CDT)}} | |||
== IT Instructions == | == IT Instructions == | ||
Revision as of 15:35, 11 September 2018
| Data Integrity Checks | |
| Summary: | there are no dupliate entries for the same patient ward admission on the laptop at send time |
| Related: | [[PHIN, DOB, Chart number, First Name, Last Name]] |
| Firmness: | hard check |
| Timing: | always |
| App: | CCMDB.mdb |
| Coding: | functions has_multiples() and overlap() and query Check_pt_multiples |
| Uses L Problem table: | not relevant for this app |
| Status: | needs review |
| Implementation Date: | date change was rolled out / first applied |
| Backlogged: | true |
The same patient should not be on a laptop twice with overlapping Arrive DtTm / Dispo DtTm. If there is a patient like that you will get an error and you will not be able to send any patients.
Definition
Duplicates of the following with overlapping Arrive DtTm / Dispo DtTm:
- Chart number
- PHIN
- combination of (DOB, First Name, Last Name)
|
|
Error scenario
2018-06-01; Problem sending A4 Val Penner. Error message Re: Duplicate patients......Screen shots of the error message sent to Pagasa. Copy of the csv file in Pagasa's C drive. Serial# 15268 & 15306 no obvious problem other than MB Province both had PHIN# 999999999. Collector solution ended up being to changed one PHIN to 123456789.
- The correct data collection process if province is MB and no PHIN go to: PHIN field. Staff sent link to collection instructions & main office review also.
|
|
|
IT Instructions
Uses functions has_multiples() and overlap() and query Check_pt_multiples.