Difference between revisions of "Data interchange format"

From ECHSA Congenital Database
Jump to navigationJump to search
m
(Info about factor list in full export removed.)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The fundamental format for data exchange in DataCollectionSoftware is '''XML'''.
+
The fundamental format for data exchange in [[EACTS Database Software]] is XML.
  
 
==Format Specification==
 
==Format Specification==
Line 5: Line 5:
 
This is a DTD (Document Type Definition) which can be used to validate an XML file.
 
This is a DTD (Document Type Definition) which can be used to validate an XML file.
  
* '''[[Media:CardiacDataExchange.dtd|CardiacDataExchange.dtd]]'''
+
* '''[http://www.eactscongenitaldb.org/viewcvs/ecbdc/ecdbc/trunk/pl/magnum2/ecdbc/export/CardiacDataExchange.dtd CardiacDataExchange.dtd]'''
 +
This DTD file defines the relations between patients, admissions, operations, etc. in the export file.
 +
 
 +
All dictionaries (wich factor codes) can be found in the [[source code]]. You can use a direct link to the [http://www.eactscongenitaldb.org/~ecdb/files/dictionaries.xls dictionaries file].
 +
 
 +
===Why an XML-based format?===
 +
 
 +
Our goal is to standardize the data submission procedure, using a portable XML format. It's implemented in our data collection software and on the server. The XML format is comprehensive, comparing to comma-delimited files, because it reflects the actual structure of the data. For example:
 +
 
 +
<Patient>
 +
  <Admission>
 +
    <Operation/>
 +
    <Operation/>
 +
  </Admission>
 +
</Patient>
 +
 
 +
This shows, how the patient, admission and operation objects are related to each other: Admission inside Patient and Operation inside Admission. Such way of describing the data is much less error-prone than the CSV files.
  
This DTD file defines the relations between patients, admissions, operations, etc. in the export file.
+
===Advantages of the XML format===
 +
 
 +
*Reflects the structure of the data (tables do not)
 +
*Self-describing: you can see the name of each field
 +
*Transparent, can be opened with a text editor
 +
*Less error-prone than CSV files
 +
*Portable, can transfer data across many software systems
 +
*Solves national character encoding problems (by declaring the encoding)
 +
*Widely known
 +
*Can be transformed, using an XSLT stylesheet, into any other text-based format such as HTML, RTF, CSV, LaTeX, or a custom format.
  
 
==Export to CSV==
 
==Export to CSV==
  
Please go to [[data export]] page to get information about export to CSV.
+
''see article: [[Export to CSV]]''
 +
 
 +
==Import from other databases==
 +
 
 +
''see article: [[Import from other databases]].
  
 
'''See also'''
 
'''See also'''

Latest revision as of 11:53, 10 July 2012

The fundamental format for data exchange in EACTS Database Software is XML.

Format Specification

This is a DTD (Document Type Definition) which can be used to validate an XML file.

This DTD file defines the relations between patients, admissions, operations, etc. in the export file.

All dictionaries (wich factor codes) can be found in the source code. You can use a direct link to the dictionaries file.

Why an XML-based format?

Our goal is to standardize the data submission procedure, using a portable XML format. It's implemented in our data collection software and on the server. The XML format is comprehensive, comparing to comma-delimited files, because it reflects the actual structure of the data. For example:

<Patient>
  <Admission>
    <Operation/>
    <Operation/>
  </Admission>
</Patient>

This shows, how the patient, admission and operation objects are related to each other: Admission inside Patient and Operation inside Admission. Such way of describing the data is much less error-prone than the CSV files.

Advantages of the XML format

  • Reflects the structure of the data (tables do not)
  • Self-describing: you can see the name of each field
  • Transparent, can be opened with a text editor
  • Less error-prone than CSV files
  • Portable, can transfer data across many software systems
  • Solves national character encoding problems (by declaring the encoding)
  • Widely known
  • Can be transformed, using an XSLT stylesheet, into any other text-based format such as HTML, RTF, CSV, LaTeX, or a custom format.

Export to CSV

see article: Export to CSV

Import from other databases

see article: Import from other databases.

See also