--- title: Validation and Error Code Details slug: medhistory-populations-patient-file-load/guide/validation-and-error-code-details docTags: createdAt: 2026-06-10T15:15:34.733Z --- ## 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: \ Expected: \. | 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 \. | | | 103 | Error | Trailer Not Present. | | | 104 | Error | Incorrect number of fields for row type \. Expected: \, Actual: \. | **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 \ is missing. | | | 108 | Error | Maximum length for field \ exceeded. Maximum Length: \, Actual Length: \. | | | 109 | Error | Invalid NPI value: \. | | | 110 | Error | Invalid format for \[time, date] field \. Expected: \ digits in the \ format. Actual: \. | 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 \ not found. Expected: \. Actual: \. | 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 \. Expected Length: \, Actual Length: \. | Used for NPI | | 115 | Error | Date for field \ must be in the past. Actual Date: \. | Used for DateOfBirth validation.
**Note:** This field takes the time into consideration when that field is included. | | 116 | Error | The Sender ID \ provided in the header does not match the Customer ID \ in the activation form. |   | | 117 | Error | Field \ must contain ASCII characters between 32 and 126. Invalid characters found: \. | The actual value \ 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 \ are not in your list of contracted notification type(s) \. | 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 \ will be ignored. | | | 123 | Error | Value provided \ is not in range. Must be between \ and \. | **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 \ does not meet minimum length. Must be at least \ characters. 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: \ | | | 129 | Fatal | The file \ was not loaded. A file \ with the same detail information was processed on \. | 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: \. | | | 133 | Error | Value for field \ must be a positive integer. 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. :::hint{type="info"} **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. :::hint{type="info"} **Note: **All footer errors are warnings. ::: | Field # | Field Name | Possible Error Code(s) | | ------- | ------------- | ---------------------- | | 0 | Record Type | 113 | | 1 | Total Records | 100
107
129 |