After submitting a file to BMDW you will receive a processing report via email. This document describes explanations of warnings or errors as you may find them in the processing report.

In the explanations below you find references to various field from the file format for data delivery. For details on these fields and the file format click here.

All problems described below are preceded by "MESSAGE (n)" or "WARNING (n)". The "n" indicated the line number from the file you have submitted. This helps you find the problem line in the file you have sent, and hopefully helps you correct the problem.

FileError(1): Empty file or file without data.

Explanation: When the size of the received file is zero bytes, or no data could be read from the received file, this error is returned.

FileError(2): No ID or NR found in header

Explanation: Donors or CBU's in the file should either be send with a number of donors/CBU's per phenotype (NR), or be send with their donor/CBU identification number (ID).

FileError(3): Premature EOF; Invalid or no closing record found

Explanation: The file should end with a footer row. This error is returned, when the footer row is missing, or the footer row is incorrrectly formatted.

FileError(4): Invalid field name in header: [fieldname]

Explanation: This error is returned, when a field name is found in the header row, which is not listed in the file format specifications.

FileError(5): Number of records processed does not match the number of records specified in the footer record. The footer as found in the file: [footer]. The number of records processed: [rows processed]

Explanation: We validate if the number of rows as found in the data file, is identical to the number of rows as provided in the footer row in the file. A discrepancy between these numbers may be an indication of a corruption in the file.

RecordError(1): Invalid donor (or CBU) count and no ID specified

Explanation: If the donor or CBU count in the field NR is not a positive number (larger than 0) the record is rejected. If the field NR is not provided in the file, the ID field should be given, and should not be blank.

RecordError(2): "Net Volume Collected" (NVC) has an incorrect value

Explanation: The "Net Volume Collected" should be no less than 10, or more than 300 milliliters (ml).

RecordError(3): "Total Nucleated Cells" (TNC) has an incorrect value

Explanation: The "Total Nucleated Cells" should be no less than 10, or more than 999 (10^7).

RecordError(4): "Collected number of CD34+ cells" (CD34P) has an incorrect value

Explanation: The value provided for the CD34+ cell count is not a numeric value with decimal point in units of 10^6

RecordError(5): "Collected number of mononuclear cells" (MONONUC) has an incorrect value

Explanation: The value provided for the mononucleated cell count is rounded number of mononuclear cells in the units of 10^7

RecordError(6): TAB char(s) found in record. Record skipped.

Explanation: Data columns need to be separated by spaces, not by TAB characters, because the TAB character is interpreted differently, depending on the text editor being used to edit/view the file. Any donor/CBU record with a TAB character is rejected.

RecordError(7): Duplicate donor/CBU id. found

Explanation: Every donor or cord blood unit should be listed only once. If during processing of a file, a donor or cord blood ID is listed more than once, only the first occurrence is accepted.

RecordError(8): Invalid date format for field 'field name' given.

Explanation:This error may be returned for date fields. The format for dates field should be in the format YYYYMMDD.

RecordError(9): Donor is either too young or too old.

Explanation:The age limits of donors that BMDW adheres to, are set by the WMDA. Donor age outside range of 18-60 years are rejected.

RecordError(10): Invalid Gender value found (not "M" or "F").

Explanation: Gender of donors other than "M" (for Male) or "F" (for Female) are reported as an error.

RecordError(11): Invalid CMV Status value found.

Explanation: The CMV status provided is not one of the possible values for this field.

HLA/DNA-ERROR(1): Invalid allele value X found for DNA-"Allele".

Example:

A1   A2   B1   B2   D1   D2   NR   RB31  RB32  RB41  RB42  RB51  RB52
11   33   14   51   1    4    0001             01:01/
HLA/DNA-ERROR(1): Invalid allele value 01:01/ found for DNA-DRB4. DRB4 alleles blanked.

Explanation: The value for DRB4 contains a slash (/) which is invalid. If such a problem is found the allele values are blanked and processing of the record continues. So, this is a warning, and not an error that requires the record to be rejected!

Another examples might be an C*04:AVK (AVK is assigned bij the NMDP as 01/02/03/04/05/06) which is not valid since the C*04:02 is not assigned.

HLA/DNA-ERROR(2): DNA triplet found for "Allele"

Example:

A1   A2   B1   B2   D1   D2   NR   DA1   DA2   DB1   DB2   DC1   DC2
1    3    8    7    3    4    1    01:AB
A*01:01/01:02/01:03/01:07 A*03:01/03:04/03:08
HLA/DNA-ERROR(2): DNA triplet found for DNA-A

Explanation: This record contains three DNA-A allele values: the first is given in the field DA1, the second and third come from the DNA strings on the line below the phenotype: the A*01:01/01:02/01:03/01:07 is translated to A*01:DBG and the A*03:01/03:04/03:08 is translated to A*03:CK.

HLA/DNA-ERROR(3): Invalid DNA string found: "some string"

Example:

A1   A2   B1   B2   D1   D2   NR   DA1   DA2   DB1   DB2   DC1   DC2
1    3    8    7    3    4    1    03:CK
A*01:01/01:02/01:03/01:04
HLA/DNA-ERROR(3): Invalid DNA string found: A*01:01/01:02/01:03/01:04

Explanation: The DNA string given A*01:01/01:02/01:03/01:04 is not valid since the A*01:04 does not exist. Another reported problem may be that a ambiguity in the format of A*01:01/02/03 is invalid.

HLA/DNA-ERROR(4): Invalid HLA antigen "some value" found for field "field name".

Example:

A1   A2   B1   B2   D1   D2   NR
1    30/3 8    7    3    4    1
HLA/DNA-ERROR(4): Invalid HLA antigen "30/3" found for HLA-A.

Explanation: The antigen or search determinant value "30/3" for HLA-A in this example is invalid.

HLA/DNA-ERROR(6): Incomplete typing found: HLA-A and HLA-B are required.

Explanation: At least one HLA-A and -B antigen or search determinant should be available to be able to match the record. If no HLA-A or -B values (either on DNA level or on serological level) are available the record is rejected.

HLA/DNA-ERROR(7): "DNA allele values" does not match "serology (or search determinants)". Equivalents for DNA alleles are ...

Example:

A1   A2   B1   B2   DA1    DA2    DB1   DB2      RB11    RB12      NR
11        75   62   11            15:02 15:26N   04:06   12:02     1
HLA/DNA-ERROR(7): DNA-B*15:02,15:26N does not match HLA-B75,62.
Equivalents for the DNA-B alleles are: 75(15)

Explanation: The serology (or search determinants) and DNA values provided, are validated separately, but also matched. If there is no match between the provided serology (or SD's) and the provided DNA, the record is reported.

HLA/DNA-ERROR(9): Number of alleles for DRB3/4/5 is more than 2; DRB3/4/5 blanked.

Example:

A1   A2   B1   B2   D1   D2   RB11  RB12  RB31  RB32  RB41  RB42  RB51  RB52
2    33   13   63   7    13   13:02       03:01 03:02 01
HLA/DNA-ERROR(9): Number of alleles for DRB3/4/5 is > 2; DRB3/4/5 blanked.

Explanation: Only two allele values are allowed for DRB3, DRB4 and DRB5 combined.

HLA/DNA-ERROR(10): DRB3 (or DRB4 or DRB5) does not match HLA-DR "values". DRB3 (or DRB4 or DRB5) blanked.

Example:

A1   A2   B1   B2   D1   D2   RB31   RB32   RB41   RB42  RB51  RB52
25   31   18   39   4    11                              01:XX
HLA/DNA-ERROR(10): DRB5 does not match HLA-DR 4,11. DRB5 blanked.

Explanation: DRB5 is associated with DR2, DR15(2), DR16(2) or DR1(rare). Likewise, DRB3 is associated with DR3, DR5, DR6, DR11(5), DR12(5), DR13(6), DR14(6), DR1403, DR1404, DR17(3), DR18(3); and DRB4 with DR4, DR7, DR9.

BMDW - Bone Marrow Donors Worldwide * Plesmanlaan 1b * 2333 BZ Leiden * The Netherlands