XDT is a group of data exchange formats that are used in the German health care system in the field of medical practitioners. They were commissioned by the National Association of Statutory Health Insurance Physicians. The formats have a common text-based syntax, in which each field is written as a row in the file, and a common field directory. They define different message classes that are specified for each of the required and optional fields from the field list.

Billing data transfer ( ADT)

This first xDT interface was published in 1987 under the name of " payroll data carrier " - it was intended for use with disks. The payroll data transfer is used to transmit the information relevant for the cash accounting data to the Ambulatory Health Association on the basis of the German § 296 SGB V. Transfer content: sickness certificates, coded diagnoses and fees digits. The ADT is created at the end of each quarter of the practice software and can be done online or by disk ( floppy simple enough for practice) will be sent by post to the accounting office.

Treatment data transfer ( BDT)

The BDT was developed in the early 90s from the ZI ( the Central Research Institute of Ambulatory Health Care ) to facilitate the exchange of complete records between practice programs from different manufacturers. In addition, system changes are relieved, because in addition to billing data and other content, such as the entire tab of the patient can be transferred with history, examination findings and history information. Software vendors can integrate this interface for the exchange of data treatment. However, this is not always the case - often free of charge, and since the record description contains many "can" fields, the result of a data exchange is often surprising. Even the definition of "must " fields is often interpreted differently. Thus, as a rule for everyday work in practice useful, but not necessarily medically relevant information, usually not be transmitted via the BDT export and import. Examples include physician addresses, e -mail addresses, phrases, practice their own billing numbers, and scanned or embedded medical reports, etc.

Furthermore, the export and import does not re usable data such as the patient's own medication lists ( "Repeat Order") or the possibility of old form contents in the new practice program display (eg old remedies regulations with full text). Such information must be interpreted according to the target system. The large number of variants of word processing ( program -owned or commercial products such as MS- Word) impede the takeover of written letters and other documents.

In practice, additional programming work on the data port are almost always required when data is to be exchanged between programs from different vendors. Also, the software vendors make it difficult sometimes consciously, sometimes unconsciously, one hundred percent perfect data transfer. Does the target system to eg specific program features, it therefore can not display (eg, percentiles, growth curves, to-do lists) and some legacy data.

Device data transfer ( GDT)

The GDT interface is intended for system- independent data transfer between medical instruments or external programs and practice software. These specifications are approved by the Medical Software quality ring. The data transfer is done via files, the serial interface or direct program - to-program communication.

Typically, the requesting system ( practice program ) is written a GDT -IN file, for example, contains at fixed fields, the patient data. The target program (eg ECG software ) reads this file and provides the data passed for further processing. Eg This eliminates re- entering the Patienstammdaten and thus the avoidance of incorrect entries ( " Meier or Maier "). The system writes after viewing or editing a GDT -OUT file which is usually automatically read by the requesting system. Usually appears in the patient record now to note that external data are available.

This technique can display on the screen such as " paperless " practices from the practice routine examination data directly from external programs (ECG, scans, lung function, long-term blood pressure, etc.). The usual paper expression is no longer necessary.

Using an HL7 GDT converter can gauges with GDT interface into hospital information systems using the HL7 standard are included.

Laboratory data carrier (LDT )

The LDT is used to request laboratory tests and to communicate the results of these investigations.


A bridge to the HL7 standard has created the SCIPHOX project by it has transformed the contents of some XDT specifications in the Clinical Document Architecture.