Appendix A: Formats
From Silverstone Matchmaker
Data File Format
Matchmaker gets it data by importing a properly formatted data file. Data files should be created as CSV files organized according to the specification outlined in this chapter. A CSV file is a simple text file (no text formatting, like bold or special fonts or indentation) where each piece of data is separated by a comma.
To help you verify a properly formatted file, make a copy of the sample data files provided with Matchmaker and open them in a simple text editor (like Notepad or Wordpad) and in a spreadsheet program like Microsoft Excel. In the text editor, you'll see each data element is separated by a comma. In the spreadsheet, you'll see how each row represents the data for a patient or pair.
File Format: CSV comma separated values
- Line one of the file must contain the column headings
- The column headings are case sensitive and must exactly match. This is required to validate the input file
- Every row must contain the same number of columns as the header.
- Ideally there would be no NULL values in any of the fields listed below.
- Fields are separated by commas, text values may be quoted but it is not required.
- If any cell contains a quote within data value the quote must be escaped by inserting an extra quote.
- File should contain text characters only - no control codes or unprintable characters
(except the end of line characters)
- Each record is stored as one line in the file (lines ending in newline (unix) or, CRLF (windows)
- CSV File Format Information: http://en.wikipedia.org/wiki/Comma-separated_values
- CSV File Format RFC: http://tools.ietf.org/html/rfc4180
External Site Notes
If you do not have data for any optional column (see required column below) just leave it out of your file entirely Your Field Names (in the column headings of your file) do not have to match our field names but they should be similar so we can perform the mapping. Exact match will speed up our process. Try to use the same general layout that we have specified below, it will make the importing process easier.
Download file format in a PDF document
Section |
# |
Field Name |
Format |
Description |
RECIPIENT |
1 |
HospitalID |
alphanumeric |
Hospital reference number for recipient (or pair) |
2 |
UNOSListingID |
alphanumeric |
UNOS Unique Identifier for Patient |
|
3 |
DOB |
date |
Date of Birth |
|
4 |
lastnm |
alphanumeric |
Last Name |
|
5 |
firstnm |
alphanumeric |
First Name |
|
6 |
ABOcd |
alphanumeric |
Blood Type (A, B, AB, O may include subtype like A1, on import the subtype should be dropped, for example A1 should be imported as A) |
|
7 |
UNOSlistedDt |
date |
UNOS Listing Date Establish Time on List |
|
8 |
ClassIPeakPRAAmt |
numeric |
Class 1 Peak PRA amount (099) |
|
9 |
ClassIIPeakPRAAmt |
numeric |
Class 2 Peak PRA amount (099) |
|
10 |
SiteDomain |
alphanumeric |
The domain name of the site. For example: cpmc.org |
|
DONOR |
11 |
lastnm |
alphanumeric |
Donor Last Name |
12 |
firstnm |
alphanumeric |
Donor First Name |
|
13 |
ABOcd |
alphanumeric |
Donor Blood Type (A,B,AB,O may include subtype like A1, on import the subtype should be dropped, for example A1 should be imported as A) |
|
14 |
DOB |
date |
Donor Date of Birth |
|
RECIP_HLA |
15 |
A1Cd |
alphanumeric |
Recipient HLA Data (See notes below) |
16 |
A2Cd |
alphanumeric |
||
17 |
B1Cd |
alphanumeric |
||
18 |
B2Cd |
alphanumeric |
||
19 |
BW1Cd |
alphanumeric |
||
20 |
Bw2Cd |
alphanumeric |
||
21 |
Cw1Cd |
alphanumeric |
||
22 |
Cw2Cd |
alphanumeric |
||
23 |
dq1cd |
alphanumeric |
||
24 |
dq2cd |
alphanumeric |
||
25 |
DR1Cd |
alphanumeric |
||
26 |
DR2Cd |
alphanumeric |
||
27 |
drw1cd |
alphanumeric |
||
28 |
drw2cd |
alphanumeric |
||
DONOR_HLA |
29 |
A1Cd |
alphanumeric |
Donor HLA Data (same as recipient HLA data) |
30 |
A2Cd |
alphanumeric |
||
31 |
B1Cd |
alphanumeric |
||
32 |
B2Cd |
alphanumeric |
||
33 |
BW1Cd |
alphanumeric |
||
34 |
Bw2Cd |
alphanumeric |
||
35 |
Cw1Cd |
alphanumeric |
||
36 |
Cw2Cd |
alphanumeric |
||
37 |
dq1cd |
alphanumeric |
||
38 |
dq2cd |
alphanumeric |
||
39 |
DR1Cd |
alphanumeric |
||
40 |
DR2Cd |
alphanumeric |
||
41 |
drw1cd |
alphanumeric |
||
42 |
drw2cd |
alphanumeric |
||
RECIP_ANTIGEN |
43 |
CL1AntibodyTxt |
alphanumeric list delimited by spaces |
List of unacceptable antigens for recipient (class 1) |
44 |
CL2AntibodyTxt |
alphanumeric list delimited by spaces |
List of unacceptable antigens for recipient (class 2) |
Silverstone Solutions professional services group can also work with you to support a custom data file format and design a workflow to create, update, and manage your data files.
