A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Matrix linking barriers to change strategies addressing the barriers | |||||||||||||||||||||||||
2 | ||||||||||||||||||||||||||
3 | Barriers summary | count | ||||||||||||||||||||||||
4 | Team 1: Holly Witteman, François Lauzier, Rémi Blanchette | Lack of recognition for efforts in wiki/Perte de l'auteurship | 2 | |||||||||||||||||||||||
5 | Barriers | Change Strategies/Solutions | Scope creep | 1 | ||||||||||||||||||||||
6 | 1- Lack of recognition for efforts in wiki. | 1.1 Professional recognition (list on CV, director acknowledges & approves) | Difficult to use, difficult to access/Difficulté d'utilisation des ressources IT/Complexity of use/Usability | 5 | ||||||||||||||||||||||
7 | 1.2 Reputation systems (may need to consider issues related to power imbalances, roles, gender, etc.) | Fully bilingual system | 2 | |||||||||||||||||||||||
8 | 1.3 Feedback (116 people used your protocol, 7 people liked your comment, thank you notes: "I had a patient with this problem last week and your page was really helpful!") | Different needs | 1 | |||||||||||||||||||||||
9 | 1.4 Upvoting/downvoting (helps with 1.2 & 1.3 and may also help with validity of content) | Cost/Sustainability | 3 | |||||||||||||||||||||||
10 | 1.5 Gamification ("Level up!") | Legal issues/Liability | 3 | |||||||||||||||||||||||
11 | 2- Scope Creep | 2.1 Phase design & implemention | Control access to content (secure) | 1 | ||||||||||||||||||||||
12 | 2.2 Prioritize on acute care protocol sharing | Managing both open and closed access to content | 1 | |||||||||||||||||||||||
13 | 2.3 Focus on low hanging fruit and patient outcomes | Validity | 7 | |||||||||||||||||||||||
14 | 3- Difficult to use, difficult to access (hardware, network access, NEEDING TO LOG IN ALL THE TIME, cross-platform functionality, COST) | 3.1 User-centred design process (with users on board to test -> developers need access to health care professionals!) | No clear objectives | 1 | ||||||||||||||||||||||
15 | 3.2 Prioritize always-on (e.g., can always consult content without needing to log in) | Lack of added value | 1 | |||||||||||||||||||||||
16 | 3.3 Ensure good network access | Lack of time | 3 | |||||||||||||||||||||||
17 | 3.4 Consider hardware (e.g., mobile devices with biometric fast login) | Coordination | 1 | |||||||||||||||||||||||
18 | 4- Fully bilingual system (users may speak only one of French or English) | 4.1 Design user interface in both English and French | Competition/Reluctance to team work | 2 | ||||||||||||||||||||||
19 | 4.2 Provide content in both languages (machine translation?) | Cultural issues | 1 | |||||||||||||||||||||||
20 | 5-Different needs (roles, institution, platforms, etc.) which increase costs | 5-1 Standardization? (Holly hates mandated standardized hardware) | Too technical content | 1 | ||||||||||||||||||||||
21 | 5-2 Modular design (as per Mandl et al.) | Lack of motivation | 3 | |||||||||||||||||||||||
22 | 5-3 Multiple Apps might be necessary for each role | Editing wars/différence d'opinion entre professionnels | 2 | |||||||||||||||||||||||
23 | 6- | 6- | Crédibilité des auteurs | 2 | ||||||||||||||||||||||
24 | 7- | 7- | Boston | 1 | ||||||||||||||||||||||
25 | 8- | 8- | Need for ontology/semantic markup | 2 | ||||||||||||||||||||||
26 | 9- | 9- | Access to computer | 1 | ||||||||||||||||||||||
27 | 10- | 10- | frustration of having someby edit my content | 1 | ||||||||||||||||||||||
28 | Data silos to break to make interoperable/EMR integration | 2 | ||||||||||||||||||||||||
29 | Having to consult multiple ressources | 1 | ||||||||||||||||||||||||
30 | Team 2 - Jean-Luc, Amélie, Christian | Common user experience (UX)/WikiDesign/Visual experience | 3 | |||||||||||||||||||||||
31 | Technical Barriers | Change Strategies/Solutions | Complicated access rights management | 1 | ||||||||||||||||||||||
32 | 1- Complexity of use | 1- Respond to the needs of 1 or 2 group(s) (focus, less functionalities) | Need for page access restriction | 1 | ||||||||||||||||||||||
33 | 2- Control access to content (secure) | 2- identify the content to secure and peoples who has access to it | Management of multiple protocol versions | 1 | ||||||||||||||||||||||
34 | 3- Costs | 3- find existing tools that address most of the needs | IT access and support | 1 | ||||||||||||||||||||||
35 | 4- Managing both open and closed access to content | 4- toll must manage access. Gives support to users | Writing skills-self efficacy | 1 | ||||||||||||||||||||||
36 | 5- Validity of the resource | 5- to have a clear process of content generation : identify sources and peoples who edit, share | Challenge to autonomy | 1 | ||||||||||||||||||||||
37 | Organizational barriers | Technological literacy/Unfamiliarity with ICT | 2 | |||||||||||||||||||||||
38 | 6- No clear objectives | 6- Survey and/or focus group to keep a limited number of goals | Diffusion of innovations | 1 | ||||||||||||||||||||||
39 | 7- Lack of added value | 7- Link internal processes to Wikitrauma platform and output | Lack of Incentive | 2 | ||||||||||||||||||||||
40 | 8- Barrier language | 8- Content translated, available in french and english | Trust | 1 | ||||||||||||||||||||||
41 | 9- Lack of time | 9- Need to proove the gain in efficiency by using the Wikitrauma platform | Integrate in workflow | 1 | ||||||||||||||||||||||
42 | 10- Coordination | 10- Identify a leader and the tasks of every peoples involved | Server reliability | 1 | ||||||||||||||||||||||
43 | Personnal Barriers | Lack of organizational support | 1 | |||||||||||||||||||||||
44 | 11- Competition | 11- Begin with a theme (subject) complementary to everyone | Rapid decision making vs learning tool | 1 | ||||||||||||||||||||||
45 | 12- Reluctance to team work | 12- seeking a project (or a task) which will bring peoples together, users will meet each others | Discordance with guidelines | 1 | ||||||||||||||||||||||
46 | 13- Cultural aspects | 13- pilot project with early adapters and opinions leaders | ||||||||||||||||||||||||
47 | 14- Too technical content | 14- Simplified language used in content, explaining concepts (vulgarized) | ||||||||||||||||||||||||
48 | 15- Lack of motivation | 15- Support by the executives: gives time, recognition, feedback | ||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||
50 | Team 3 | |||||||||||||||||||||||||
51 | Barriers | Change Strategies/Solutions | ||||||||||||||||||||||||
52 | 1- Editing wars | 1- Établir des règles de discussions, limiter le nombre d'éditeurs possibles, intégration obligatoire des évidences disponibles, possibilité d'exclusion de certains éditeurs/utilisateurs à comportement inadéquat, identification d'un modérateur | ||||||||||||||||||||||||
53 | 2- Crédibilité des éditeurs | 2- Déclaration des conflits d'intérêt | ||||||||||||||||||||||||
54 | 3- Manque de temps des utilisateurs | 3- Stimuler l'intérêt des utilisateurs (behavior modification): en bout de ligne on sauvera du temps et les patients seront mieux soignés. | ||||||||||||||||||||||||
55 | 4- Différence d'opinion entre les différents professionnels utilisateurs | 4- Tenter de converger les différents intérêt des divers utilisateurs et inclures différentes sections dans le wiki (sectoin md, infirm, inhalo, patients) | ||||||||||||||||||||||||
56 | 5- Difficulté d'utilisation des ressources informatiques | 5- Audit d'utilisation pour indentifier les problèmes précocément et apporter solutions (les cycles !) | ||||||||||||||||||||||||
57 | 6- Difficulté d'utilisation des ressources informatiques | 6- Vidéos (tutoriels) pour utilisateurs et forums de discussion pour les utilisateurs | ||||||||||||||||||||||||
58 | 7- Manque de motivation | 7- Reconnaître le contribution des utilisatuers qui ajoute des éléments (utilisateur du mois!), l'inlcure comme activité de FMC: inclure les liens vers les sites de comptablilisation des "heures de FMC" | ||||||||||||||||||||||||
59 | 8- Perte de l'auteurship | 8- Garder l'historique des contribution des différents utilisateurs | ||||||||||||||||||||||||
60 | 9- Validité de l'information | 9- Intégration obligatoire des évidences cliniques lorsqu'elles sont disponible | ||||||||||||||||||||||||
61 | 10- Boston | 10- Gagner le 7eme match ! | ||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||
64 | Team 4 Tom, Mathieu, François et France | |||||||||||||||||||||||||
65 | Barriers | Change Strategies/Solutions | ||||||||||||||||||||||||
66 | 1- Technical - Legal issues | 1- Write a clear disclaimer and put it on a website + have offical bodies to support your wiki | ||||||||||||||||||||||||
67 | 2- Technical - Scientific Quality | 2- Mark validated and/or non-validated information + have offical bodies to support your wiki | ||||||||||||||||||||||||
68 | 3- Organizational -time constraints | 3-Try to show that overall time will be saved | ||||||||||||||||||||||||
69 | 4- An Ontology is needed to share the Knowledge representation in traumatology | 4- | ||||||||||||||||||||||||
70 | 5- personal: access to computer | 5-give access to computer at the work station | ||||||||||||||||||||||||
71 | 6-timely access to computer | 6-give access to computer in your pocket or in your glasses (eg googleglass) | ||||||||||||||||||||||||
72 | 7- legal issues | 7- ask advice to CPMA | ||||||||||||||||||||||||
73 | 8-frustration about having someone else edit personal contribution | 8- have an open forum space to discuss diverse opinions and identify a coordinator | ||||||||||||||||||||||||
74 | 9- Data silo need to be broken to make data integration possible | 9- | ||||||||||||||||||||||||
75 | 10- | 10- | ||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||
77 | Team 5 | |||||||||||||||||||||||||
78 | Barriers | Change strategies/Solutions | ||||||||||||||||||||||||
79 | Technical barriers | |||||||||||||||||||||||||
80 | 1- Having to consult many sources (e.g. EAST, INESSS, AQESSS) | 1- Concentrate relevant information as much as possible on one platform that is endorsed by recognized organization | ||||||||||||||||||||||||
81 | 2- Common User Experience (UX) | 2- Put in place rules or templates for a common GUI / page ergonomy | ||||||||||||||||||||||||
82 | 3- Access rights management can easily get complicated | 3- Assign users to groups and roles. | ||||||||||||||||||||||||
83 | 4- Is there a need for page access restriction? Wiki platform vs stakeholders requirements. | 4- Need to evaluate correctly the stakeholders needs and use case before chosing the wiki platform. How good, to what percentage can it address the requirements? Do a gap analysis between the requirements and the different platforms. | ||||||||||||||||||||||||
84 | 5- Management of the multiple versions of the same protocols | 5 -Feasability would need to be analyzed with specific uses cases (single or multiple database?). User needs to be directed to the right version for his hospital in an efficient manner. Dashboard per hospital linking to pages? Semantics? | ||||||||||||||||||||||||
85 | Personal barriers | 5- Need to evalute correctly the stakeholders needs and use case before chosing the wiki platform. How good can it address the requirements? | ||||||||||||||||||||||||
86 | 6- How to ensure credibility | 6- Endorsement of posted protocols-guidelines by recognized authorities - organizations | ||||||||||||||||||||||||
87 | Organizational barriers | 7- | ||||||||||||||||||||||||
88 | 8-Cost to develop, train, implement, maintain the platform - sustainability | 8-Proof the concept before wide implementation to demonstrate that it worth the efforts and money. | ||||||||||||||||||||||||
89 | 9- | 9- | ||||||||||||||||||||||||
90 | 10- | 10- | ||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | Team 6 | |||||||||||||||||||||||||
93 | Barriers | Change Strategies/Solutions | ||||||||||||||||||||||||
94 | 1- Validity of the resource | 1- Editorial committee: updates and reviews | ||||||||||||||||||||||||
95 | 2- Wiki Design (appearance, userfriendly format and organization | 2- Proper design and testing | ||||||||||||||||||||||||
96 | 3- IT access and support | 3- More computers and appropriate IT system | ||||||||||||||||||||||||
97 | 4- Lack of motivation | 4- Recognize contribution with incentives and rewards (scientific contribution); improve the body of evidence supporting the effectiveness of wiki utilization on outcomes and process-of-care improvement | ||||||||||||||||||||||||
98 | 5- Writing skills (self-efficacy) | 5- Editorial board and writing support | ||||||||||||||||||||||||
99 | 6-Challenge to autonomy | 6- Behaviour change and gradual implementation | ||||||||||||||||||||||||
100 | 6- | 7- |