Difference between revisions of "-180: Activity does not belong to Patient. Please Submit a Webfirst Ticket."
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
=Description= | =Description= | ||
This occurs when trying to process a message where the patient is erroneously assigned an Accession Number that '''is not''' unique. | This occurs when trying to process a message where the patient is erroneously assigned an Accession Number that '''is not''' unique. | ||
| − | |||
=Common Scenario= | =Common Scenario= | ||
| − | + | This error will occur is more than one patient is assigned the same Acceccession Number. | |
| − | |||
| − | |||
=Fix= | =Fix= | ||
Ensure the Visit Number that's sent in through the interface will not differ when the same clinical data (e.g. results) are sent in. | Ensure the Visit Number that's sent in through the interface will not differ when the same clinical data (e.g. results) are sent in. | ||
*Work around: Invalidate the current Results, then re-file the updates results that had erred in ConnectR. | *Work around: Invalidate the current Results, then re-file the updates results that had erred in ConnectR. | ||
Revision as of 16:38, 16 February 2011
Description
This occurs when trying to process a message where the patient is erroneously assigned an Accession Number that is not unique.
Common Scenario
This error will occur is more than one patient is assigned the same Acceccession Number.
Fix
Ensure the Visit Number that's sent in through the interface will not differ when the same clinical data (e.g. results) are sent in.
- Work around: Invalidate the current Results, then re-file the updates results that had erred in ConnectR.