Changes between Version 9 and Version 10 of Ticket #525, comment 10


Ignore:
Timestamp:
Mar 7, 2016, 9:48:28 AM (8 years ago)
Author:
olle

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #525, comment 10

    v9 v10  
    2626|| Number of patient lateralities without database reference || Data lines skipped at import ||
    2727
    28  * INCA import annotation types:[[BR]][[BR]]a. All annotation types are coupled to `Case` items.[[BR]]b. Data in all columns in the two INCA example files except the temporary patient ID should be imported to annotations.[[BR]]c. The name of the annotation type corresponding to a data column should equal prefix "`INCA_`" plus the name of the header for the column.[[BR]]d. The value type of an annotation type should be one of `Type.DATE`, `Type.STRING`, `Type.INT`, `Type.BOOLEAN`, or `Type.FLOAT`, corresponding to the type of the corresponding column in the INCA data file, according to the description of the variables in the INCA database from 2014-01-01.[[BR]]e. INCA example file two contained two headers, "`BN20_Sida_Beskrivning`" and "`BP20_Sida_Beskrivning`", without the corresponding "value" headers, "`BN20_Sida_Värde`" and "`BP20_Sida_Värde`", respectively. In order to be able to check if some INCA data annotation types are missing in a import session, it was decided not to define annotation types for the latter two "`_Värde`" columns.[[BR]]f. Two extra annotation types, not coupled to columns in the INCA data file, should be added, one for the date that the INCA data was exported from the database, and one for the last date an INCA annotation was updated.[[BR]]g. At import, a data line in the INCA data file should be mapped to the `Case` item corresponding to a patient with the same personal number as in the line, and where the `Case` item has a laterality matching the laterality description in the line.[[BR]]h. An INCA annotation should only be updated if the value from the INCA data file at import differs from the current annotation value.
     28 * INCA import annotation types:[[BR]][[BR]]a. All annotation types are coupled to `Case` items.[[BR]]b. Data in all columns in the two INCA example files except the temporary patient ID should be imported to annotations.[[BR]]c. The name of the annotation type corresponding to a data column should equal prefix "`INCA_`" plus the name of the header for the column.[[BR]]d. The value type of an annotation type should be one of `Type.DATE`, `Type.STRING`, `Type.INT`, `Type.BOOLEAN`, or `Type.FLOAT`, corresponding to the type of the corresponding column in the INCA data file, according to the description of the variables in the INCA database from 2014-01-01.[[BR]]e. INCA example file two contained two headers, "`BN20_Sida_Beskrivning`" and "`BP20_Sida_Beskrivning`", without the corresponding "value" headers, "`BN20_Sida_Värde`" and "`BP20_Sida_Värde`", respectively. In order to be able to check if some INCA data annotation types are missing in a import session, it was decided not to define annotation types for the latter two "`_Värde`" columns.[[BR]]f. Two extra annotation types, not coupled to columns in the INCA data file, should be added, one for the date that the INCA data was exported from the database, and one for the last date an INCA annotation was updated. These two annotation types should be excluded, when checking if some INCA data annotation types are missing in a import session.[[BR]]g. At import, a data line in the INCA data file should be mapped to the `Case` item corresponding to a patient with the same personal number as in the line, and where the `Case` item has a laterality matching the laterality description in the line.[[BR]]h. An INCA annotation should only be updated if the value from the INCA data file at import differs from the current annotation value.