| 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 an import session, it was decided not to define annotation types for the latter two "`_Värde`" columns.[[BR]]f. Columns corresponding to list values in the INCA variable description, should be mapped to annotation types with value options set to the available values. However, except for the "`A030Sida_Beskrivning`" column used for laterality mapping, value options should only be set for integer "`_Värde`" columns, since the strings corresponding to these values in the INCA data files are not guaranteed to exactly match the descriptions strings in the INCA variable description.[[BR]]g. All INCA annotation types should belong to a new "INCA" annotation type category.[[BR]]h. 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 an import session.[[BR]]i. 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]]j. 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 an import session, it was decided not to define annotation types for the latter two "`_Värde`" columns.[[BR]]f. Columns corresponding to list values in the INCA variable description, should be mapped to annotation types with value options set to the available values. However, except for the "`A030Sida_Beskrivning`" column used for laterality mapping, value options should only be set for integer "`_Värde`" columns, since the strings corresponding to these values in the INCA data files are not guaranteed to exactly match the descriptions strings in the INCA variable description.[[BR]]g. All INCA annotation types should belong to a new "INCA" annotation type category.[[BR]]h. 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 an import session.[[BR]]i. 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]]j. An INCA annotation should only be updated if the value from the INCA data file at import differs from the current annotation value. However, annotations for the extra annotation types for the date that the INCA data was exported from the database, and the last date an INCA annotation was updated, should still be updated, to indicate that the INCA annotation values for the case item equals those of the latest INCA data file. |
