We previously published instructions how you can manually upload your XML files with data to the BMDW data upload service.
We now published also instructions for automatic data submission to the service via REST API mechanisms. You can find the instructions on the following page: How to automate data upload/download with the REST API. Please be aware that currently the instructions point to the staging server/ environment of the data upload service. Once we switch to the production environment, you need to make changes to direct to the correct server.
In the XSD files, you can already find a lot of field requirements and we also validate your data according to these definitions. However, BMDW also has set some additional rules for validation. These rules are called BMDW business validation rules. You can now find these rules in the tab 'Data Validation: Errors and warnings in processing report' on the page with Search & Match Service Data submission information.
If you have any questions, please don't hesitate to contact us by sending an email to support@bmdw.org
Our developers worked very hard to implement all our requirements and validation rules. The first version of the pipeline that can process all the data is now ready and we are currently performing many tests to identify as many problems before this procedure will be tested with the three large organization, NMDP/Be the Match, ZKRD and Anthony Nolan.
Until further notice, we would like to ask you to only upload test files with a maximum of 1000 records. Larger files will negatively influence the velocity of our testing period.
Once we will be focusing more on performance during processing of larger files, we will approach you again to help with uploading of larger files.
Thank you for your cooperation and if you experience any problems or receive error/warning messages that you do not understand or didn’t expect, please send an email to support@bmdw.org
The last weeks, the WMDA office tried to contact all BMDW listing organisations that
- have NOT responded to the survey "Moving to XML" last May
- have NOT requested an account for our BMDW data upload service for uploading their test XML file
- provided a test XML file before, but the quality/ structure of the file was NOT good enough
Unfortunately, we were not able to reach all organisations.
If you haven't been in contact with the WMDA office before on your status of moving to the XML format for data submission to BMDW, please contact us at your earliest convenience by sending an email to support@bmdw.org.
You can also contact us if you would like to get explanation on the requirements for an XML file or support from our ICT specialists. All information and requirements are described on the BMDW data submission information pages.
The end of our development work is approaching!!
The last month, BMDW and our developers worked very hard to implement all the validation rules that are necessary to properly validate all data fields that can be provided in the XML files.
The big testing phase will start tomorrow. We will perform first many tests ourselves. During this period, you can also still upload your test files. We expect that the reports that will be generated upon uploading your file, will be much more accurate than before. However, if you experience any problems or find strange or unexpected error/warning messages, please contact us by sending an email to support@bmdw.org and we can determine together whether a mistake was made during implementation of a certain validation rule or that there was an inconsistency in your data file.
Together we can test and improve our new data processing pipeline!!
From October on, we will start testing with three larger organisations: Be the Match/NMDP, ZKRD, and Anthony Nolan. If all tests succeed and the system performs as expected, we will start the production system at the beginning of November.
If you have created also a test XML file and want to join the BMDW data upload service, please send us email to support@bmdw.org to get your account details.
We have been testing XML files from several organisations for the last months and we would like to share the common mistakes found in the files.
On file level:
- File name incorrect: The correct file naming is ION-1234-D.xml.pgp or ION-1234-C.xml.pgp
- Wrong public key used for encryption: For the XML files you have to use the new BMDW public key.
- File is signed: The file should not be signed; only encrypted with the BMDW public key.
- Encoding in the top line: we recommend to add the encoding in the top line: <?xml version=”1.0” encoding=”utf-8”?>
We would recommend to create the XML file not as one line of data. For better readability, you should use line endings and indentations.
On record level:
- CREATION_TIIME and SNAPSHOT_TIME: These values should look like 2016-08-23T13:16:48Z; so no fractions of seconds and a 'Z' to reflect UTC time.
- SCHEMA_VERSION is missing: This element was added in the last version of the XSD files. We prefer to add this already.
- BIRTH_DATE: Correct format should be YYYY-MM-DD and this is a mandatory field.
- GRID: GRID is only applicable for DONORs and nor for CBUs.
- POOL: POOL is no longer an element within <DONOR> or <CBU>, but should be within <INVENTORIES>
- HLA values: DNA values should not be added to the <SER> (serological) value fields.
- Order of the elements: The data should be delivered in the correct order of the elements. Otherwise you will receive messages that a certain elements is not expected.
- VOL versus VOL_FRZN: VOL represent the volume of a cord at time of the collection. VOL_FRZN is the volume after processing and before freezing. VOL_FRZN is comparable with NVC in DOT20 files.
- TNC versus TNC_FRZN: TNC represent the total number of nucleated cells of a cord at time of the collection. TNC_FRZN is the number of cells after processing and before freezing. TNC_FRZN is comparable with TNC in DOT20 files. Also be aware that the units of these elements are different in DOT20 and XML. For DOT20 for example you used 300 and this was in units E7; for XML you should use the real number, e.g. 3.0E9
- CD34PC versus CD34PC_FRZN: CD34PC represent the number of CD34+ cells of a cord at time of the collection. CD34PC_FRZN is the number of CD34+ cells after processing and before freezing. CD34PC_FRZN is comparable with CD34P in DOT20 files. Also be aware here that the units are different.
If you haven't started to create your XML test file, please take the above mentioned mistakes into account. If you have any questions, please contact us by sending an email to support@bmdw.org
Is your organisation ready to implement the new BMDW file format with extended data on November 1, 2017? Many organisations have sent their test files and are ready to go.
However, some organisations have not contacted the WMDA to inform us when they will sent the test file in the new XML format.
Let us know when you are able to send the test file, you can read all details here.
If you are not able to send a test file before November 1, 2017 contact our ICT specialists at support@bmdw.org. During an hour free consultation, they can investigate the likely effort and costs that are required to implement the changes in your organisation.