Scientific Concept of the National Cohort (status ... - Nationale Kohorte
Scientific Concept of the National Cohort (status ... - Nationale Kohorte
Scientific Concept of the National Cohort (status ... - Nationale Kohorte
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
A.5<br />
A.5 Methods for quality assurance and quality control<br />
All diagnoses will be coded according to <strong>the</strong> ICD version being effective at <strong>the</strong> start <strong>of</strong> <strong>the</strong><br />
study. Revisions and/or diagnostic progress will be considered as add-on diagnoses, if<br />
deemed appropriate. Information that leads to a specific ICD code will be stored electronically<br />
such that later revisions can be used with only minimal additional effort.<br />
The feedback from <strong>the</strong> expert assessments to <strong>the</strong> study centers will enhance <strong>the</strong> diagnostic<br />
quality and comparability <strong>of</strong> <strong>the</strong> diagnoses across centers and over time.<br />
The results <strong>of</strong> <strong>the</strong> abovementioned benchmarking process, quality indicators comparing<br />
study center-based diagnoses with <strong>the</strong> results from <strong>the</strong> experts’ assessments, and <strong>the</strong> number<br />
<strong>of</strong> events stratified by study center will be disseminated on an annual basis.<br />
A.5.9 quality assurance and quality control <strong>of</strong> data management<br />
High standards for data acquisition, data processing, and data storage will be enforced by<br />
implementing quality assurance and quality control procedures in data management.<br />
A.5.9.1 quality assurance <strong>of</strong> data management<br />
Quality assurance during <strong>the</strong> system analysis phase<br />
A system specification document will specify <strong>the</strong> following points:<br />
� Overall project aims:<br />
– “Must” criteria: performance parameters that <strong>the</strong> future data management system<br />
will comply with (see Sect. A.4.2);<br />
– “Can” criteria: it is not absolutely necessary to fulfill <strong>the</strong>se criteria, but will be<br />
strived for if sufficient resources are available.<br />
– “Borderline” criteria: parameters and functions beyond <strong>the</strong> reach <strong>of</strong> <strong>the</strong> anticipated<br />
s<strong>of</strong>tware system (e.g., quality control <strong>of</strong> <strong>the</strong> data at <strong>the</strong> level <strong>of</strong> <strong>the</strong> competence<br />
unit for data management can be individually performed with o<strong>the</strong>r statistical<br />
programs and <strong>the</strong>refore is not part <strong>of</strong> this solution).<br />
� Product application:<br />
– Application domain: <strong>the</strong> system to be created will be used only for <strong>the</strong> <strong>National</strong><br />
<strong>Cohort</strong>. It is possible that a similar system could be used for o<strong>the</strong>r future studies,<br />
but this is beyond <strong>the</strong> scope <strong>of</strong> <strong>the</strong> current project.<br />
– Target groups: <strong>the</strong> main target group for this system consists <strong>of</strong> study personnel<br />
from individual study centers.<br />
– Working conditions: <strong>the</strong> system will run as a web application on servers in <strong>the</strong><br />
integration centers, with permanent surveillance <strong>of</strong> IT systems, data items, and<br />
data flow by central data administrators.<br />
� Product functions: exact and detailed descriptions <strong>of</strong> each function (see Sect. A.4.2)<br />
� Product data: <strong>the</strong> data that need to be stored over a longer period <strong>of</strong> time, seen from<br />
a user’s point <strong>of</strong> view.<br />
� Product performance: specifications concerning processing time and data accuracy,<br />
simultaneous updates on all servers.<br />
� User interface: <strong>the</strong> s<strong>of</strong>tware will be designed for both keyboard and touch screen use.<br />
In addition, a concept for a role-based access model will be defined.<br />
� Nonfunctional requirements: external rules and laws that will be respected by <strong>the</strong> s<strong>of</strong>tware,<br />
security requirements, and platform dependencies. The system will work with<br />
pseudoanonymous data. Access to personalized data will be restricted to a limited<br />
number <strong>of</strong> persons; <strong>the</strong> components that manage personalized data will be specially<br />
protected.<br />
164