Validation and Error Code Details

error type descriptions error type description warning does not fail file or row error fails row error it is associated with fatal fails entire file load, nothing is processed patient file load validations and errors load status type description 01 n/a file loaded correctly 02 warning file loaded with errors and/or warnings 03 fatal failed to load file no data was processed patient response file errors code type description comment 100 warning record count in the trailer does not match the actual number of records in file actual \<recordcount> expected \<trailercount> make sure number of rows in file matched what was reported in the trailer 101 fatal no valid contracts exist customer is missing contract for \<recordtypecode (pnm, pma, pat)> 103 error trailer not present 104 error incorrect number of fields for row type \<rowtype> expected \<expectednnumber>, actual \<actualnumber> example sdt|1242||||e|104|incorrect number of columns for row type pnm expected 19, actual 20 105 error rows exist after trailer 106 error multiple header rows encountered 107 error required field \<fieldname> is missing 108 error maximum length for field \<fieldname> exceeded maximum length \<maximumnumber>, actual length \<actualnumber> 109 error invalid npi value \<npi> 110 error invalid format for \[time, date] field \<fieldname> expected \<expectednumber> digits in the \<expectedlayout> format actual \<actualnumber> used on date/time checks example invalid format for date field date of birth expected 8 digits in the ccyymmdd format actual 01/15/98 113 error expected value for field \<fieldname> not found expected \<expectednnumber> actual \<actualnumber> transmission action and fileschedule are both conditional, as a result the file will not fail if this does not exist for example, receiverid must be s00000000000006 114 error incorrect length for field \<fieldname> expected length \<expectednnumber>, actual length \<acutalnumber> used for npi 115 error date for field \<fieldname> must be in the past actual date \<date from file> used for dateofbirth validation note this field takes the time into consideration when that field is included 116 error the sender id \<senderid> provided in the header does not match the customer id \<userid> in the activation form 117 error field \<fieldname> must contain ascii characters between 32 and 126 invalid characters found \<actual> the actual value \<actual> will display the unicode escaped response (u+hex \u0020) showing the character detected example field state must contain ascii characters between 32 and 126 invalid characters found \u0baf\u0bbe 118 error the sender password provided in the fileload is different than the password provided in the customer activation form 119 error the notification type(s) provided \<requestednotificationtypes> are not in your list of contracted notification type(s) \<validnotificationtypes> a list of alerts was included on the patient record, but none of them were contracted the patient was not loaded 122 warning you have specified a prescription notification type for a panel only patient your specified notification types of \<requestednotificationtypes> will be ignored 123 error value provided \<actual> is not in range must be between \<min> and \<max> example value provided 13 is not in range must be between 1 and 12 124 error the npi provided is valid but the nppes registration is missing the provider first or last name which prevents processing this row the nppes registry will need to be updated data mapping issue if this error appears, contact surescripts support with error code and description to resolve 125 error the npi provided is valid but the nppes registration is missing the facility name which prevents processing this row the nppes registry will need to be updated data mapping issue if this error appears, contact surescripts support with error code and description to resolve 126 error field \<fieldname> does not meet minimum length must be at least \<min> characters actual \<actual> 127 error two of a person's names (last name, first name, middle name) must have 2 or more characters 128 error field end monitoring date must be a date in the future or empty actual \<actual> 129 fatal the file \<currentfilename> was not loaded a file \<previousfilename> with the same detail information was processed on \<yyyy mm dd hh\ mm\ ss,sss> duplicate panel file to resolve this error, make changes to the details in the file that you are loading, change the lookback period, or wait at least 24 hours to reload it 131 fatal the unr record type is not allowed in the same file with \[pma, pat, pnm] record types 132 error field postal code must consist of 5 digits, an optional hyphen ( ), and up to 4 additional digits actual value \<passedinzipcode> 133 error value for field \<fieldname> must be a positive integer actual \<actual> 134 warning blank row ignored on line number %s 135 error requestrangestart must be earlier than requestrangeend 136 error date range cannot be more than %s months 137 error invalid phone number 138 fatal med history health plan participant must be configured with flat file output 139 fatal med history health plan participant must be configured with version mhv4 applicable header row error codes the following table lists the possible error codes that could occur for each field please be aware that over time, surescripts may continue to modify, add, or remove applicable field error code listings as error information is updated, the table below is subject to change, and this implementation guide will be revised to provide all of the necessary details for displaying accurate error information within a timely manner note all header errors are fatal and will fail the entire file load field # field name possible error code(s) 0 record type 113 1 version 113 117 2 sender id 114 116 117 118 3 sender password 114 117 118 4 receiver id 113 114 117 5 transmission control number 107 108 117 6 transmission date 107 110 117 7 transmission time 107 110 117 8 transmission file type n/a 9 transmission action 113 117 10 extract date 107 110 117 11 usage indicator 113 117 12 patient population id 107 108 117 13 file schedule 108 113 117 14 look back period in months 117 123 applicable enrollment detail row error codes the following table lists the possible error codes that could occur for each field please be aware that over time, surescripts may continue to modify, add, or remove applicable field error code listings as error information is updated, the table below is subject to change, and this implementation guide will be revised to provide all of the necessary details for displaying accurate error information within a timely manner field # field name possible error code(s) 0 record type 101 113 1 record sequence number 107 108 117 133 2 assigning authority 107 108 117 3 patient id 107 108 117 4 last name 107 108 117 127 5 first name 107 108 117 127 6 middle name 108 117 127 7 prefix 108 117 8 suffix 108 117 9 address line 1 108 117 10 address line 2 108 117 11 city name 108 117 126 12 state 117 118 13 postal code 107 117 132 14 date of birth 107 110 115 117 15 gender 113 117 16 npi 107 109 114 117 124 125 17 end monitoring date 110 128 18 notification requested for this patient 108 119 122 applicable unenrollment detail row error codes the following table lists the possible error codes that could occur for each field please be aware that over time, surescripts may continue to modify, add, or remove applicable field error code listings as error information is updated, the table below is subject to change, and this implementation guide will be revised to provide all of the necessary details for displaying accurate error information within a timely manner field # field name possible error code(s) 0 record type 113 1 record sequence number n/a 2 product 113 3 end monitoring date 107 128 applicable trailer row error codes the following table lists the possible error codes that could occur for each field please be aware that over time, surescripts may continue to modify, add, or remove applicable field error code listings as error information is updated, the table below is subject to change, and this implementation guide will be revised to provide all of the necessary details for displaying accurate error information within a timely manner note all footer errors are warnings field # field name possible error code(s) 0 record type 113 1 total records 100 107 129