Difference between revisions of "-178: External Visit Number is invalid. Please Submit a Webfirst Ticket."
m (moved -178: External Visit Number is not invalid. Please Submit a Webfirst Ticket. to -178: External Visit Number is invalid. Please Submit a Webfirst Ticket.: double negative confused the issue)
Revision as of 22:03, 6 January 2011
This occurs when existing clinical data are found (e.g. Results on FileResult_CMS) and the visit that's looked up during the filing of the clinical data does not match the visit associated to the existing clinical data.
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
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.