Birgitta Weltermann1, Christine Kersting1. 1. Institute for General Medicine, University Hospital Essen, University of Duisburg-Essen, Hufelandstraße 55, 45147 Essen, Germany.
The study is designed as a mixed-methods study in primary care academic teaching practices of the University of Duisburg-Essen, Germany. Following recommendations on health information technology usability evaluation and the framework for the development of complex interventions, the software will be developed in three steps [13, 14]:Step 1: specification of the needs for the setting and usersA series of focus group sessions with primary care physicians and practice assistants as well as practice observations will be conducted to determine setting- and user-specific requirements. (Note: in the German health care system, the term ‘practice assistant’ refers to practice personnel who are typically graduates from a certified 3-year vocational training. They assume tasks in practice organization and patient management).Step 2: software developmentBased on the concept developed in the model practice and the requirements identified in the focus groups, a software prototype will be designed. This will be pretested by primary care physicians and practice assistants with subsequent modifications as indicated by the pretesting.Step 3: integration of the software into the settingTo test the new software prototype in routine primary care, a feasibility study will be performed in real-life practice scenarios. If the feasibility testing indicates the need for modification, the software will be refined accordingly.Figure 1 provides an overview of the objectives, tasks, and target groups for the three steps.
The software has two key features: a physician module (physician control center) and a patient-centered visualization strategy (patient management center).The first feature is a control center for the physician(s) responsible for practice management and the design of care processes. This control center is important to address potential physicians’ concerns regarding a loss of autonomy in clinical reasoning and/or decision-making power. The software offers choices for various settings in a higher-level structure which are based on epidemiologic data from our prior study, literature data on seniors’ care needs, and evidence-based recommendations. The options refer to the patients to be managed with the software (e.g., if the software is used for all seniors or special subgroups only), the spectrum of outcome-relevant conditions selected for management (e.g., if a physician prioritizes hypertension and diabetes care, while excluding other diseases), the degree of comprehensiveness (e.g., if disease-related and other aspects of care such as the availability of advanced directives or the involvement of a nursing service are included), the level of detail used for the patient-centered visualization (e.g., if chronic renal failure is presented as general information or detailed according to the stage of renal failure). An electronic tutorial will inform physicians about the software and its options and guide through the selection process for practice-specific configurations. This physician control center can be accessed at any time to newly define choices either by adding, refining, or removing options. For practices starting to use the software, an outcome-oriented ‘standard configuration’ is suggested. As the software leads to standardization and redesign of practice processes, it is important that the physician(s) in charge can determine the content and time sequence of quality processes suggested by the software. This helps to avoid excessive workloads and subsequent frustration of physicians and personnel using the software. For better system control in larger health care settings, a directory of setting-specific users’ rights and access codes will be integrated into the physician control center. The rights to access and edit information within the software will thus be structured hierarchically: physicians as administrators will define custom settings in the physician control center and assign user-specific rights depending on the professional and their individual role in practice care processes.The second key feature of the software is the patient management center which applies a patient-centered visualization strategy: the various aspects of patients’ care will be highlighted in a new graphical user interface with symbols which are a combination of a colored field and a short keyword (so-called flags). This strategy is based on the semiotic triangle (Fig. 2) [18], a concept which is well-known in the field of linguistics. Two types of flags will be used. Information flags will provide relevant, patient-centered information, e.g., relevant diagnoses and medications. Dynamic action flags will indicate quality deficits (e.g., if patients’ blood pressure is not controlled) and refer to upcoming preventive and/or therapeutic measures (e.g., preventive measures, monitoring of a medication blood level). Figure 3 provides an example for the patient-centered visualization strategy.
Step 1: specification of the needs for the setting and users
Practice recruitment
The first step of the study will be conducted in the teaching and research practice network of our institute consisting of 185 primary care practices located in North Rhine-Westphalia, Germany. All practices are requested to take part in one of the two network meetings of the institute yearly. At one of these practice meetings, physicians will be informed about the study which requires the participation in two focus group sessions and one practice observation. Physicians who are interested in participating will be asked to sign up during the meeting. Interested physicians will be contacted by phone. For the focus groups and practice observations, we will recruit six physicians with up to two practice assistants each. This number is reasonable because the practices are similar to other practices in size, aim, and content of their work [21] belonging to the Association of Statutory Health Insurance Physicians North Rhine and Westphalia-Lippe. No inclusion and exclusion criteria for the practices will be defined.
Based on the set of criteria defined in step 1, a prototype of the software will be developed by a company specialized in developing health information technology. The software will include an electronic interface which allows for interoperability with all certified practice administration software solutions available in Germany.
Pretesting
The software prototype will be tested by research team members of our institute and by the physicians and practice assistants who participated in step 1 of the study. The pretest will take place at our institute in Essen, Germany. Each participant will test the prototype for ten fictitious multimorbid seniors.
Data collection
After pretesting, each participant will complete the validated system usability scale (SUS) [22] providing information on software usability, practicability, and user-friendliness. Additionally, information regarding software aspects that need to be improved will be provided using free text items.The usability of the prototype will be analyzed by determining the SUS score. The score can assume values between 0 and 40. To interpret the result in percent, each score will be multiplied by the factor 2.5 [22, 23]. Single item scores and the average overall score will be calculated. According to the literature, an overall SUS score ≥70 % denotes good usability, while a score ≤50 % indicates a considerable need for improvement [23]. Pretesting will be judged as successful when a SUS score of ≥70 % is reached. The free text items will be structured in NVivo qualitative data analysis software, Version 10 (QSR International Pty Ltd., 2012). The items will be analyzed using a coding scheme which will be developed and refined over time by identifying categories directly from the free text answers. Simple frequencies will be calculated for these categories. All statistical analyses will be performed using IBM SPSS Statistics for Windows, Version 22.0 (Armonk, New York: IBM Corp.).
Quality controls will be conducted during all steps of the study. After recruitment, consent forms of all study participants will be checked for completeness. After each data collection, quality controls will be conducted to ensure that required data collection documents are complete. An identification number and the date of birth will be used to verify that study data of each study participant are merged correctly.Audio-recorded data of the interviews and the focus group sessions will be transcribed. Transcripts will be imported into NVivo qualitative data analysis software, Version 10 (QSR International Pty Ltd., 2012). Quantitative data will be entered manually in an access-restricted electronic database. To control for input errors, 10 % of data will be entered twice. An error rate of 5 % will be accepted; otherwise, all values will be entered twice. The data will be checked for plausibility using simple frequency testing.All data will be stored access-restricted at our institute.
Authors: Jean Yves Le Reste; Patrice Nabbe; Benedicte Manceau; Charilaos Lygidakis; Christa Doerr; Heidrun Lingner; Slawomir Czachowski; Miguel Munoz; Stella Argyriadou; Ana Claveria; Bernard Le Floch; Marie Barais; Peter Bower; Harm Van Marwijk; Paul Van Royen; Claire Lietard Journal: J Am Med Dir Assoc Date: 2013-02-12 Impact factor: 4.669
Authors: Patrick J O'Connor; Joann M Sperl-Hillen; William A Rush; Paul E Johnson; Gerald H Amundson; Stephen E Asche; Heidi L Ekstrom; Todd P Gilmer Journal: Ann Fam Med Date: 2011 Jan-Feb Impact factor: 5.166