NEW ZEALAND HEALTH INFORMATION SERVICE
Home > technical documentation
NZHIS File Processing and Error Messages
Contents
File processing
There are two processing phases before records are loaded into the databases. The description below is intended to be a high level overview of the processes. For a more detailed system specific description please refer to the File Specification documents.
Pre-processing
The pre-processor is responsible for checking the basic integrity of hospitals’ data files. Assuming that all the records can be read, the whole batch is checked along with the header and all errors and warnings are reported back to the originating facility in the error report.
Files are loaded in chronological order so that if an agency is sending an update to the same health event in consecutive files, all the earlier information will already be loaded. If the file passes the pre-processor it moves on to the processor.
The following checks are carried out:
- Firstly, the pre-processor identifies the format of the file and confirms that the file header is the first record and that it is readable.
- Several checks are carried out within the header record to ensure that the record type and processing environment are correct. These are checks on date sent, that health agency is a valid one and that it matches the abbreviation.
- The pre-processor then checks that the records accompanying the header record are correct record types and have the correct number of fields.
Editing and Loading
The contents of each data file are checked against the business rules and loaded it into holding tables. A record is also kept of the number of existing records that have been affected by this file – events inserted and deleted, number of records with errors and warnings, as well as other operating information such as processing time.
There are several fields stored in the data collections that are derived from other fields, including the DRG. These are calculated during this part of the editing process. The edit/error module also maps ICD-10-AM and ICD-9-CM-A diagnosis codes.
The data is then moved from the load tables into the databases
MHINC Error Messages
Error code | Description |
| 2012 | Field %1 : Service start date (%2) must be after birth date (%3) |
| 2014 | Field %1 : Client receiving Child, Adolescent and Family health services should be aged 19 or younger |
| 2015 | Field %1 : Service end date (%2) must be after service start date (%3) |
| 2016 | Field %1 : Death date (%2) must be after birth date (%3) |
| 2017 | Field %1 : Legal status date (%2) must be after birth date (%3) |
| 2018 | Field %1 : Diagnosis date (%2) must be after birth date (%3) |
| 2019 | Deleted. Replace by NZS1009. |
| 2020 | Field %1 : Referral date (%2) must be after birth date (%3) |
| 2021 | Field %1 : Service start date (%2) must be after referral date (%3) |
| 2022 | Field %1 : Reporting period date (%3) must be after service start date (%2) |
| 2023 | Field %1 : This date (%2) must be before the date that the file was sent (%3) |
| 2101 | Field %1 : This value ‘%2’ is not a valid service code for a Kaupapa Māori Facility |
| 2102 | Field %1 : This value ‘%2’ is not a valid service code for a Child, Adolescent or Family Health Facility |
| 2103 | Field %1 : This value ‘%2’ is not a valid service code for a Forensic Facility |
| 2104 | Field %1 : This value ‘%2’ is not a valid service code for an Alcohol and Drug Facility |
| 2110 | Field %1 : This value ‘%2’ is not a valid service code for a Non-government Agency |
| 2120 | Field %1 : Service start date (%2) must be after referral date (%3) for referral type ‘F’ |
| 2121 | Agency code ‘%3’ does not match acronym ‘%1’ in header record, should be ‘%2’ |
| 2122 | Field %1 : Agency code ‘%2’ does not match agency code ‘%3’ in header record |
| 2123 | Team code ‘%1’ does not match Agency code ‘%2’ |
| 2124 | Invalid combination of values: Diagnosis code ‘%1’, Clinical Coding System ‘%2’ and Diagnosis Type ‘%3’ |
| 2125 | Ethnic code field ‘%2’ must be specified before using ‘%1’ |
| 2127 | Invalid combination of values: Diagnosis Type code ‘%1’ is incompatible with Clinical Coding System ‘%2’ and Clinical Code ‘%3’ |
| 2128 | The date in field %1 (%2) is on or before the registered date of birth for this HCU (%3) |
| 2130 | This value ‘%1’ is not a valid service_code for team_code ‘%2’ of type ‘%3’ |
| 2131 | This value ‘%1’ is not a valid service_code for agency ‘%2’ of type ‘%3’ |
| 2132 | The AD records number of bed nights (%1) exceeds the maximum (%2) allowed by the %3 record |
| 2133 | Legal status records are only valid for users over 15 years |
| 2134 | Service provided for user younger than 15 |
| 2135 | Service provided for user older than 19 (CAF) |
| 2136 | Report Start Date and Report End Date must be in the same month |
| 2137 | AD Report %1 (%4) must be equal to or greater than SP Service %2 (%3) |
| 2138 | AD Report %1 (%4) must be equal to or less than SP Service %2 (%3) |
| 2139 | A Diagnosis of type (A) or (P) must precede this Diagnosis type (B) |
| 2140 | There must be only one Primary Diagnosis (Type A) per HCU per agency per day |
| 2141 | A matching Service Provided (SP) record cannot be found |
| 2142 | A Legal Status record (LS) for this HCU ID (%1) cannot be found |
| 2143 | A Diagnosis Details record (DD) for this HCU ID (%1) and agency code (%2) cannot be found |
| 2144 | A Diagnosis record could not be found for HCU (%1) and agency (%2) between the service start date (%3) and service end date (%4) |
| 2145 | If the %1 field is (%2) then the %3 field must also be (%2) |
| 2146 | The date psychiatric leave ended (%1) must be greater or equal to the %2 date (%3) |
| 2147 | This date (%1) is after the discharge date (%2) for the deceased HCU (%3) |
| 2148 | A warning was received from NMDS. The warning was ‘(%1) : (%2)’ |
| 2149 | An error was received from NMDS. The error was ‘(%1) : (%2)’ |
| 2150 | No matching SM record found in file (%1) for SP record with inpatient service code (%2) |
| 2151 | No matching SM record found in file (%1) for update or delete of record that had previously been used to generate NMDS data |
| 2152 | An SM record associated with the record has a team code (%1), a service code of (%2) and a service start date (%3) |
| 2153 | The value of this service record overlaps the values of this service record (%1) |
| 2154 | Record rejected because another service with this NHI number and health agency code has overlapping bed nights (%1) |
| 2155 | Inpatient service group rejected, because an SP, AD, or SM record with the same HCU, agency, with an inpatient service code has errors |
| 2156 | Diagnosis group for this HCU and Agency rejected, because a Diagnosis of type (B) would appear before a Diagnosis of type (A) or (P) |
| 2157 | At least one diagnosis on this date for this client must be a Mental Health Diagnosis |
| 2158 | Record rejected — another access details record with the same NHI number and health agency code has an overlapping reporting period (%1) |
| 2159 | Changing AD record causes the parent SP record to overlap. (%1) (%2) |
| 2160 | Community service group rejected, because a SP, or AD record with the same SP keys has errors |
| 2161 | Cannot delete record twice |
| 2162 | Service setting (%1) is invalid for bed night service code (%2) |
| 2163 | No diagnosis of type (A) or (P) on the same diagnosis date |
| 2164 | A %1 record related to this %2 record has been rejected — no %3 diagnosis exists for this HCU and agency |
| 2165 | %1 records submitted > %2 days after %3 start date must have a diagnosis for this HCU and agency |
| 2166 | Diagnosis type (%1) must be a Mental Health Diagnosis |
| 2167 | Cannot delete DD record without replacement diagnosis type A or P |
| 2168 | DD diagnosis date outside SP period |
| 2169 | The supplied domicile code (%1) is retired |
| 2170 | The NHI domicile code (%1) is retired |
| 2171 | The %1 must be equal to or less than %2 days |
| 2175 | The %1 value (%2) falls outside the team date range |
| 2176 | %1 indicates %2 but %3 not present |
NBRS Error Messages
The table below describes errors that can be reported from the file loading at NZHIS. The following information is given for each code:
Error number
This number consists of three parts – the application_code, the error_ID and the error_type.
- Application_code:
A three-letter code assigned by NZHIS to identify each software application (eg, MHS = mental health, NMS = NMDS). For the standard error message that applies to more than one software application, the application code is NHS (= NZHIS). - Error_ID:
This is a unique number (eg, 1003). - Error_type:
Severity of message (E = error, W = warning).
Error type description
A detailed description of the error and suggestions for why it may have arisen.
Error message
This is the message that is sent back to providers. It may contain substitution parameters (prefixed with ‘%’) which the program fills in with the particular value (eg, the value ‘%2’ is not a valid value for the field ‘%1’). Where the error message is listed as ‘to be assigned’, this error number is not currently used.
Note: An Excel version of this table(Excel, 17 KB) is also available.
Error number | Error message |
| NBR 4000 E | '%1' is not a valid header record (BH) |
| NBR 4001 E | The agency in the header record (%1) does not match the file acronym (%2) |
| NBR 4002 W | Unexpected status change from %1 to %2 |
| NBR 4003 E | Greater than 99999 records within file |
| NBR 4004 W | Data record accepted |
| NBR 4005 W | Data record rejected |
| NBR 4006 E | Part Of Rejected Group |
| NBR 4007 E | The Action code (%1) is not valid for the Booking Status Code (%2) |
| NBR 4008 E | %1 is not allowed when current status is %2 |
| NBR 4009 E | %1 is not allowed for non-existent Booking System Entry |
| NBR 4010 E | %1 (%2) is the same as, or earlier than the %3 (%4) on the last %5 |
| NBR 4011 E | HCU (%1) and HCU (%2) do not identify the same Health Care User |
| NBR 4012 E | The fields (%1, %2, %3) form a tuple |
| NBR 4013 E | Cannot change, delete, or erase a non-existent Booking System Entry |
| NBR 4014 E | Cannot change, a Booking System Entry that has status %1 |
| NBR 4015 W | Booking System Entry has been treated, but no discharge appears on NMDS |
| NBR 4016 W | Booking System Entry has exit category 'deceased', but no date of death recorded on the NHI |
| NBR 4017 W | Should use Book rather than Rebook here |
| NBR 4018 E | CPAC Assessment date is outside the valid date range for this CPAC Scoring system %1 |
| NBR 4019 E | Clinical code (%1, %2, %3) has no mapping to ICD-10-AM Clinical code |
| NBR 4020 E | Clinical code (%1, %2, %3) has no mapping to a Booked Procedure code |
| NBR 4025 W | Booked Procedure Code (%1) ignored since Clinical code (%2, %3, %4) specified |
| NBR 4026 E | Neither field '%1', nor fields '%2', '%3', '%4' supplied |
| NBR 4030 E | Input Health Specialty code %4 is inconsistent with Clinical code (%1, %2, %3) |
| NBR 4031 E | Parsing error |
| NBR 4032 E | Unexpected end of file |
| NBR 4033 E | %1 (%2) is earlier than the %3 (%4) on the last %5 |
| NBR 4034 E | Field %1 is present although the complementary field %2 is not present |
| NBR 4035 E | Value '%2' is not a legal value for field %1 from date '%3' |
| NBR 4036 E | Duplicate booking entry sequence |
| NBR 4037 E | %1 is not a normal status from which a patient would exit NBRS under exit code %2 |
| NBR 4038 E | Invalid version %1 of NBRS. Correct file version is 'v2.0 |
| NBR 4039 E | Invalid HS %1, CPAC %2, BP %3 combination |
| NBR 4040 E | You are trying to use a Change Record to update 'STATUS' information |
| NBR 4041 W | Change record contains the same 'NON-STATUS' values as currently held within the NBRS. No update occurred. |
NMDS Error Messages
The table below describes errors that can be reported from the file loading at NZHIS. The following information is given for each code:
Error number
This number consists of three parts – the application_code, the error_ID and the error_type.
- Application_code:
A three-letter code assigned by NZHIS to identify each software application (eg, MHS = mental health, NMS = NMDS). For the standard error message that applies to more than one software application, the application code is NHS (= NZHIS). - Error_ID:
This is a unique number (eg, 1003). - Error_type:
Severity of message (E = error, W = warning).
Error type description
A detailed description of the error and suggestions for why it may have arisen.
Error message
This is the message that is sent back to providers. It may contain substitution parameters (prefixed with ‘%’) which the program fills in with the particular value (eg, the value ‘%2’ is not a valid value for the field ‘%1’). Where the error message is listed as ‘to be assigned’, this error number is not currently used.
Note: An Excel version of this table(Excel, 17 KB) is also available.
Error number | Error type description | Error message |
| NZS1001 E | The NMDS looks at the record type to determine the number of fields (commas) to expect in the record. Where these do not match, the record is rejected. | Wrong number of fields: expected %1, found %2 |
| NZS1002 E | A null value or blank has been reported for a field where it is compulsory to report a value. | %1 is a mandatory field |
| NZS1003 E | The value reported for this field is not included in the NMDS code table and is therefore not valid. | 1% contains an invalid value – %2 |
| NZS1004 E | The value reported for this field is not in the correct format. Refer to the appropriate Data Dictionary for the correct format. | %1 should be in format %3, entered as %2 |
| NZS1005 E | The date in this field is not the correct format. It needs to be ccyymmdd. | Invalid date in field %1 |
| NZS1006 E | The date in this field is in the future. | Field %1 cannot be a future date (%2) |
| NZS1007 E | The date in this field is in the past. | Field %1 cannot have a date in the past |
| NZS1008 E | The value reported in this field is outside the range of values that are valid. | %2 is outside the valid range for %1 |
| NZS1009 E | This error is only valid for MHINC and NBSD records where a hospital is sending additional diagnosis information for a record that has already been sent in. The error indicates that the first health event (parent record) for this patient could not be found in the database. If the parent record should already be in the database, the most likely problem is an error somewhere in the five business key fields. | No parent record (%1) can be found |
| NZS1010 E | The record type that has been reported is not HD, HC, HE or HR. These are the only valid record type codes. | This value (%1) is not a valid record type |
| NZS1011 E | There is something wrong with the header record for this batch. Every batch must have a header record as the first record in the batch. | %1 is not a valid header record (HR) |
| NZS1012 E | The header record includes the total number of records in this file. However, when the pre-processor checked the file the total found did not match the total reported in the header. | Wrong number of fields: expected %1 found %2 |
| NZS1013 E | The header record includes the filename of the file. However, this does not match the name of the file which arrived. This is a check that the file has not been renamed, which might affect the order of processing. | HR filename and file sent did not match |
| NZS1014 E | The file had more than one header record. The NMDS is expecting only one header record for each file. | Only one header record is allowed |
| NZS1015 E | The code in the message function field (also called transaction type field in MHINC and NBSD) is incorrect. The valid values are A1 (Add), A2 (Add ignoring warnings) and D1 (Delete). | This value ‘%1’ is not a valid transaction type |
| NZS1016 E | This is only valid for mental health (MHINC) and Breast Cancer Screening (NBSD) records. A delete record transaction was received for a health event that also has one or more diagnosis records. These must be deleted first before the health event can be deleted. | Cannot delete parent record as dependent records exist |
| NZS1017 E | There is a field in the header record that reports if this file is a TEST file or a PROD file. This error indicates that a test file has been sent to the production environment, or a production file to the test environment, or the header record does not include this field. | Incorrect processing environment, file intended for %1 |
| NZS1018 E | This is only valid for mental health (MHINC) and Breast Cancer Screening (NBSD) records. A pair of records has been received for the same patient – the first was to delete the health event record and the second was to update the diagnosis information. | Cannot insert/update record (%1) after attempting to delete parent (%2) |
| NZS1019 E | The file sent in has no data records in it – just a header record. | A file with no data records after the header is invalid |
| NZS1020 E | The code used in this field is no longer valid – it has been retired. Suggest you refer to the Data Dictionary for valid codes. For example, this error will be generated if a record includes a 1991 domicile code that was replaced in the 1996 rewrite. | %2 is no longer valid for %1 at date %3 |
| NZS1021 E | Each agency sending data to the NMDS has an abbreviation that is reported as part of the header record. There is also an agency code in each record within the batch. This error indicates that the agency code included in the file does not refer to the same organisation as the abbreviation in the header record. | Agency code %3 does not match acronym %1 in header record |
| NZS1022 E | Each agency sending data to the NMDS has an abbreviation that is reported as part of the header record. Associated with this abbreviation is an indicator showing whether the agency is actively sending data to NZHIS. In this case the agency referred to in the heading is noted as inactive. Check that the agency abbreviation is correct, then contact the Help Desk and ask them to make this agency active. | The provider with acronym %1 is marked inactive |
| NZS1023 E | The NMDS was not able to find the record you want to delete. Suggest you check the business key fields, as these have to be exactly the same in both the delete record and the NMDS record. | Record cannot be deleted – key fields not found |
| NZS1024 E | The NMDS is not expecting this field to have spaces or tabs in it. Refer to the Data Dictionary for the required format. | Field %1 contains tabs or spaces |
| NZS1025 W | This is a warning that the value entered in this field is outside the range that was expected. Please check that the value is correct. If it is correct, then re-send the record with an A2 in the message function field. | Value in field %1 is outside the normal range |
| NZS1026 E | The NMDS checks on several date sequences within the patient record. This error indicates that one or more of the dates are out of sequence. Each error message is tailored to reflect the date details involved. | Date in field %1 is before the date %3 |
| NZS1027 E | The NMDS checks on several date sequences within the patient record. This error indicates that one or more of the dates are out of sequence. Each error message is tailored to reflect the date details involved. | Date in field %1 is after the date %3 |
| NZS1028 E | The NMDS checks some pairs of codes to ensure that the record is correct. This error means that one of those checks failed. For example, a diagnosis (disease) code does not require an operation/procedure date. | Value %1 is inconsistent with the value in %3 |
| NZS1029 E | The NMDS checks on sets of values to ensure that the record is correct. This error means that one of these checks failed. An example of this would be if the clinical coding system ID and the clinical code table type and the event clinical code type do not match with the diagnosis code. | Values %2 are not a valid combination for %1 |
| NZS1030 E | Check the record type field – this is not a valid code. | Line %1: This value %2 is not a valid record type |
| NZS1031 E | The NMDS checks the number of fields that it expects to get for each record type. This error reports there were either too many or too few fields in the record. | Line %1: Wrong number of fields – expected %2, found %3 |
| NZS1032 W | This batch has not been processed because of inconsistencies within the header record. | Line %1: Record ignored because of inconsistent file |
| NZS1034 E | The NMDS edit is expecting a specific range of values for this field and none of the valid values were found. | Value in field %1 is outside the expected range |
| NZS1035 E | The NMDS checks that there are no unprintable characters, such tabs or control characters, in any of the free text fields. This error indicates that these were present. | Unprintable characters were found in field %1 |
| NZS1036 E | The NMDS uses the first record in each file to determine the file format. Critical to this is whether the third character in the first record is a comma or a tab. This error indicates that it was neither a comma nor a tab, and therefore the file format (version 7,8 or 9) could not be determined. | Unable to determine file format version |
| NMS1045 W | One of the fields in an inter-field check for accident details does not contain the expected values. This check is between the purchaser code and the ACC form number. | %1 not consistent with %3 |
| NMS1046 W | The HMV field is populated in this record but there is no procedure code for hours on mechanical ventilation. | %1 indicates %2 but %3 not present |
| NZS1048 E | Fields in an inter-field check contain the same value. This check is between the three ethnic code fields on a health event. | Fields %1 and %2 cannot contain duplicate values |
| NMS3006 E | This error message is not currently being used. | |
| NMS3007 E | This error message is not currently being used. | |
| NMS3008 E | This error message is not currently being used. | |
| NMS3009 E | This error message is not currently being used. | |
| NMS3010 E | This record includes information about a birth event but the event type code is not BT. Either re-submit the record as a BT event or remove the birth-specific details. | Birth detail field %1 is not valid for event type %2 |
| NMS3012 W | This is a warning that the event leave days calculated for this patient are greater than the number of days that the patient stayed in hospital, using discharge date minus admission date. Correct or remove the event leave days field. | Event leave days may not be greater than or equal to length of stay |
| NMS3013 E | This error message is not currently being used. | |
| NMS3015 E | This field is mandatory for this type of event but has not been reported in this record. | Field %1 is mandatory for %2 events |
| NMS3016 E | Weight on admission is mandatory for neonates, but was not reported in this record. | Weight on admission is required for neonates aged 28 days or less |
| NMS3017 E | This error message is not currently being used. | |
| NMS3018 E | This error message is not currently being used. | |
| NMS3019 E | The field ‘message function’ has an invalid code. Valid codes are A1, A2 and D1. | %1 is not a valid value for message_function |
| NMS3020 E | The NMDS edit/error module checks all three parts of the health event record (HE, HD and HC). If there is a problem with any one of these then the whole event has to be returned. For example, if HE and HC pass but there is a problem with HD, then this error is generated. This error is not returned to hospitals. | Transaction failed |
| NMS3021 E | This is an HD or HC record but there is no HE record with the same business key fields in it. The NMDS could not load this information without a matching HE record. | HD or HC record without matching HE record |
| NMS3022 E | The NMDS is expecting a diagnosis code for this type of event, but none was reported. Usually generated when no event diagnosis type ‘A’ (primary diagnosis) is found. | A diagnosis of type %2 is mandatory for event type %1 |
| NMS3023 E | There are too many principal diagnosis codes for this event type. | Too many diagnoses of type %2 |
| NMS3024 E | The diagnosis code in this record is not valid for this type of event. | Diagnosis %2 is not legal for event type %1 |
| NMS3025 E | There is another event in the NMDS for this patient which occurred at the same time as this one. The other event may be for this HCU or for another that has been merged with this HCU. | Event cannot overlap existing event |
| NMS3026 W | Some of the business key fields for this event match with another event in the NMDS. This indicates that a similar event for this patient has already been reported. The other event may be for this HCU or for another that has been merged with this HCU. | Warning: similar event already exists |
| NMS3027 E | The event type code field indicates that this is a psychiatric event, but the legal status record (HC) has not been supplied. | Psychiatric (IM) event must have a legal status (HC) record |
| NMS3028 E | The NMDS was expecting a health event record for this patient but could not find one. | No health event (HE) record present in transaction unit |
| NMS3029 W | It is unusual for anyone in New Zealand to have this diagnosis. Please check that the code has been entered accurately. If it is correct, the event may be re-sent with an action code of A2. | This diagnosis %1 is not normal for NZ |
| NMS3030 W | It is unusual for anyone in New Zealand who is so young to have this diagnosis. Please check that the code has been entered accurately. If it is correct, the event may be re-sent with an action code of A2. | Diagnosis %1 is not normal for ages below %2 |
| NMS3031 W | It is unusual for anyone in New Zealand who is this old to have this diagnosis. Please check that the code has been entered accurately. If it is correct, the event may be re-sent with an action code of A2. | Diagnosis %1 is not normal for ages above %2 |
| NMS3032 W | It is unusual for someone of this sex to have this diagnosis. Please check that the code has been entered accurately. If it is correct, the event may be re-sent with an action code of A2. | Diagnosis %1 is not normal for sex %2 |
| NMS3033 W | This patient’s sex has been reported as unknown. Please report the specific sex. | Patient sex is reported as unknown |
| NMS3034 W | The Australian Coding Standards do not allow this code to be reported as a principal diagnosis. | %1 is not acceptable as a principal diagnosis |
| NMS3035 E | The patient has an operating room procedure, but the date on which it happened has not been reported. | Operation date field may not be null for this procedure |
| NMS3036 W | The diagnosis in this record indicates that there was an accident, but no external cause code has been reported. | No external cause code provided |
| NMS3037 E | This error message is not currently being used. | |
| NMS3038 W | The event end type code indicates that the patient died, but there were no diagnosis codes that would have caused death. | No fatal diagnoses provided |
| NMS3039 E | This error can arise from two sources. Firstly, if there is one HE record for this event, but there are two HD records with the same diagnosis number. Secondly, if there is one HE record and two HC records with the same legal status date and legal status code. | Duplicate – %2 already used |
| NMS3040 E | This error arises when the pre-processor recognises that the same record has come in twice within the batch file. For example, there were two HE delete records that had the same business key fields, or there were two HE insert records with the same business keys. | Badly formed transaction unit %1 |
| NMS3041 E | The NMDS is expecting the field date psychiatric leave ended to be reported only for patients with an event end type of DL (discharged on leave). This record includes a date in the field ‘date psychiatric leave ended’ but does not have a DL event end type code. | %1 can only be be reported for end-type DL |
| NMS3042 W | The NMDS carries out a check between mechanical ventilation hours and mechanical ventilation procedure codes. This warning indicates that there are one or more mechanical ventilation procedure codes reported but the mechanical ventilation hours field is empty. If the hours are not available to report, send the record back with an A2 in the message function field. | Mechanical ventilation procedure code but no hours reported |
| NMS3043 W | The hours on CPAP or HMV are greater than the total hours spent in hospital. | %1 exceeds the total hours of the Health Event |
| NMS3044 W | CPAP hours should only be reported for babies aged less than 29 days. This record is for an older patient and includes a value in the CPAP field. | %1 only required for perinatal conditions |
| NMS3045 W | Informal patients cannot be discharged to leave. DL can only be used for committed patients. | Latest Legal Status Code cannot be ‘I’ when end type = ‘DL’ |
| NMS3046 E | An end date check to ensure supplied codes are still valid for use. Generation of this error means that the key date provided is after the end date in the reference table for the code supplied in the collection file. An example of this type is where a Purchaser code or an Admission Type code has been used on an event where the event end date is after the end date for the code provided. | %1%2 is retired from use |
| NMS3047 E | A start date check to ensure supplied codes are valid for use. Generation of this error means that the key date provided is prior to the commencement date of the code supplied. An example of this is where a Legal Status code has been used on an event where the supplied Legal Status date is prior to the start date for the code provided. | %1%2 is not yet active for use |
NNPAC Error Messages
The table below describes errors that can be reported from the file loading at NZHIS. The following information is given for each code:
Error number
This number consists of three parts – the application_code, the error_ID and the error_type.
- Application_code:
A three-letter code assigned by NZHIS to identify each software applicationin this case NAP for the NNPAC datamart. - Error_ID:
This is a unique number (eg, 1003). - Error_type:
Severity of message (E = error, W = warning).Currently, there are no warnings in the NNPAC datamart validation.
Error type description
A detailed description of the error and suggestions for why it may have arisen. Lists of allowed values can be found in the file specification.
Error message
This is the message that is sent back to providers. It may contain substitution parameters (prefixed with ‘%’) which the program fills in with the particular value.
Note: AnExcel version of this table (Excel, 17 KB) is also available.
Error number | Error type description | Error message |
| NAP5000 E | No record found to delete with the same key (extract system identifier, client system identifier, PMS unique identifier) as requested. | COULD NOT FIND RECORD TO DELETE |
| NAP5001 E | Record type not in list of valid record types. | RECORD TYPE INVALID: $1 |
| NAP5002 E | NHI not allocated to a person in the NHI system. | NHI INVALID: $1 |
| NAP5003 E | Accident flag not one of the allowed values. | INVALID ACCIDENT FLAG: $1 |
| NAP5004 E | Attendance code not one of the allowed values. | INVALID ATTENDANCE CODE: $1 |
| NAP5005 E | Event type not one of the allowed values. | INVALID EVENT TYPE: $1 |
| NAP5006 E | Health provider type not one of the allowed values. | INVALID HEALTH PROVIDER TYPE: $1 |
| NAP5007 E | Service type not one of the allowed values. | INVALID SERVICE TYPE: $1 |
| NAP5008 E | Hours in the time of service is greater than 24 or not numeric. | INVALID HOURS IN TIME OF SERVICE: $1 |
| NAP5009 E | Minutes in the time of service is greater than 60 or not numeric. | INVALID MINUTES IN TIME OF SERVICE: $1 |
| NAP5010 E | Facility code is not in the list of facilities. | INVALID FACILITY: $1 |
| NAP5011 E | Agency code is not in the list of facilities. | INVALID AGENCY: $1 |
| NAP5012 E | The date of service is after the processing date. | DATE OF SERVICE IN THE FUTURE: $1 |
| NAP5013 E | The date of service is 20 years before the processing date. | DATE OF SERVICE TOO FAR IN THE FUTURE: $1 |
| NAP5014E | The date of service is not a valid date. | DATE OF SERVICE INVALID: $1 |
| NAP5015 E | The location code is not one of the allowed values. | LOCATION CODE INVALID: $1 |
| NAP5016 E | The equivalent purchase unit is not one of the allowed values for NNPAC (it may be valid in other datamarts). | EQUIVALENT PURCHASE UNIT INVALID: $1 |
| NAP5017 E | Purchaser code not one of the allowed values. | PURCHASER CODE INVALID: $1 |
| NAP5018 E | Health specialty not one of the allowed values. | HEALTH SPECIALTY UNIT INVALID: $1 |
| NAP5019 E | The value in the volume is not allowed for attendance codes, for example, DNA should have a volume of 0. | VOLUME: $1 INCOMPATIBLE WITH ATTENDANCE CODE: $2 |
| NAP5020 E | The client system identifier is not that agreed with NZHIS. | INVALID CLIENT SYSTEM IDENTIFIER: $1 |
| NAP5021 E | The PMS unique identifier is missing. | NO PMS UNIQUE IDENTIFIER |
Top Back