| 3 | | * The INCA import wizard should perform an initial check of the INCA data file, after which the results are presented to the user:[[BR]][[BR]]a. If critical problems are encountered, import should be blocked.[[BR]]b. If problems with individual headers/data lines are encountered, the corresponding data columns/lines might be skipped during import; it is then the user's decision whether to fix the problems in the data file, or proceed with import of the eligible data.[[BR]]c. Basic results from the file check should be presented in the web form. In addition, it should be possible to open/download a text file with more detailed information from the file check by clicking on a button. The file should include the information presented in the web form, but also optional information on what headers or data lines problem were found with. |
| | 3 | * The INCA import wizard should perform an initial check of the INCA data file, after which the results are presented to the user:[[BR]][[BR]]a. If critical problems are encountered, import should be blocked.[[BR]]b. If problems with individual headers/data lines are encountered, the corresponding data columns/lines might be skipped during import; it is then the user's decision whether to fix the problems in the data file, or proceed with import of the eligible data.[[BR]]c. Basic results from the file check should be presented in the web form. In addition, it should be possible to open/download a text file with more detailed information from the file check by clicking on a button. The file should include the information presented in the web form, but also optional information on what headers or data lines problems were found with. Due to the sensitive type of information in the INCA data file, in the report file, temporary patient ID values should be used instead of personal numbers to identify entries in the INCA file. |
