Turn an xDT file (GDT, LDT or BDT) into a readable CSV of its fields - locally in the browser, with no upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
The German xDT family is the classic data interchange format between practice, lab and device software: GDT (device data carrier) for measuring devices, LDT (lab data carrier) for lab orders and results and BDT (treatment data carrier) for the practice record. All three are record- and field-based: each line is a field in the form "LLLFFFFcontent" - three digits of length, four digits of field identifier, then the content. That is precise, but barely readable as a raw file.
Drop your xDT file; the tool reads each line as a field (length, field identifier, content) and writes a flat CSV with one row per field: record number, field identifier, label and value. The common field identifiers (e.g. surname, first name, date of birth, patient number, version) get a plain-text label; unknown identifiers keep their four-digit code. A new record starts at field identifier 8000 (record type). You can drop several files at once.
Everything runs entirely locally in the browser (pure JavaScript, no server, no foreign library from a foreign CDN) - the practice data never leaves your device. Honest framing: this is a structural conversion of the fields into a table, not a clinical tool and not a full xDT validation. xDT files are historically encoded in ISO-8859-1 / Windows-1252; the tool reads them that way. The CSV is written with a UTF-8 BOM so umlauts show correctly in Excel.
| Input formats | GDT, LDT, BDT, TXT |
|---|---|
| Output format | CSV |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Reads an xDT file (GDT/LDT/BDT, record- and field-based: each line "LLLFFFFcontent" with three digits of length, four digits of field identifier, content) and outputs a flat CSV with one row per field: record number (a new record starts at field identifier 8000), field identifier, plain-text label (for the common identifiers; otherwise the code) and value. xDT files are read as ISO-8859-1/Windows-1252; the CSV is RFC 4180 with a UTF-8 BOM. It is a structural field listing for data exchange, not a clinical tool and not a full xDT validation; verify the result against a specific xDT version with your software.
No. Reading the xDT file and building the CSV run entirely locally in the browser (pure JavaScript, no server); the data never leaves your device.
GDT (device data carrier), LDT (lab data carrier) and BDT (treatment data carrier) - all three are record- and field-based and are read the same way.
Record number, field identifier, label (plain text for the common identifiers) and value - one row per xDT field.
Yes. xDT files are read as ISO-8859-1/Windows-1252 and the CSV is written with a UTF-8 BOM so umlauts show correctly in Excel.
No. It is a structural listing of the fields as a table, not a validator and not a clinical tool. Verify the result against your xDT version with your software.