Difference between revisions of "-180: Activity does not belong to Patient. Please Submit a Webfirst Ticket."
Jump to navigation
Jump to search
(-180 Error - first page) |
|||
| Line 1: | Line 1: | ||
=Description= | =Description= | ||
| − | This occurs when | + | 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= | ||
The Visit Number used is the Accession Number, plus the year of the results (based on date sent). If results are sent over as preliminary on Dec 29 and the final results come over on Jan 5. The year would be different, creating a different Visit Number (VisitNumberEXT). | The Visit Number used is the Accession Number, plus the year of the results (based on date sent). If results are sent over as preliminary on Dec 29 and the final results come over on Jan 5. The year would be different, creating a different Visit Number (VisitNumberEXT). | ||
Revision as of 16:25, 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
The Visit Number used is the Accession Number, plus the year of the results (based on date sent). If results are sent over as preliminary on Dec 29 and the final results come over on Jan 5. The year would be different, creating a different Visit Number (VisitNumberEXT).
Base Stored Procedure
ClinicalInterfaceChecking
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.