Duplicate error messages: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
PTorres (talk | contribs)
will point collector to PHIN field for collection rule instead of workaround
TOstryzniuk (talk | contribs)
mNo edit summary
Line 10: Line 10:


==Problem sending==
==Problem sending==
{{Discussion}}
2018-06-01; Problem sending A4 Val Penner.
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.
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.  Solution ended up being to changed one PHIN to 123456789.   These are two different patients does not make sense why this need to be done in order to send.
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 you have MB province and no PHIN go to: [[PHIN field]]
*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.

Revision as of 16:23, 2018 June 1


Some error messages in CCMDB.mdb created by CCMDB Data Integrity Checks create more than one error message. These are based on the events used to trigger error messages.

  • I think I have eliminated most of them - collectors, please log here any that I may have missed. Ttenbergen 18:29, 2012 November 7 (EST)
    • no answers, assuming fixed Ttenbergen 11:49, 2014 September 10 (CDT)

One example dealt with in a different article is Multiple LOS errors. Ttenbergen 11:30, 2013 October 9 (CDT)


Problem sending

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.