• Int J Med Inform · Mar 2014

    User participation in healthcare IT development: a developers' viewpoint in Finland.

    • Susanna Martikainen, Mikko Korpela, and Tuija Tiihonen.
    • School of Computing, University of Eastern Finland, Kuopio, Finland. Electronic address: susanna.martikainen@dnainternet.net.
    • Int J Med Inform. 2014 Mar 1; 83 (3): 189-200.

    Background And PurposeRecent research showed that physicians in Finland were highly critical of their information technology (IT) systems. They were also critical of the methods of collaboration with the developers of the health IT systems (HITS) in use at the time of the questionnaire. This study turned the set-up around and asked systems developers the same questions about collaboration. What is developers' view on end user participation in HITS development at the moment? How would developers wish end users to participate in systems development? Do the developers' views differ from the physicians' (end users') views of the current state of collaboration in developing IT systems?MethodsA web-based questionnaire study was conducted in one of the major HITS provider companies in Finland among all developers, including software developers and customer support and sales personnel. Both quantitative and free-text questions of a previous study were adapted for the purpose. The responses were analyzed with qualitative and basic quantitative methods.ResultsThe response rate of the questionnaire was 37% and 136 responses were received. The developers who responded were experienced workers; 81% of the respondents had 6 years or more of work experience in IT systems development and 35% of them had 6 years or more of work experience in the healthcare domain. Almost three-quarters (72%) of the respondents agreed with the statement 'I work with users'. Almost all the developers (90%) thought that they are interested in user feedback and also 81% thought that they take the end users' opinions and experiences into account when developing software. A majority of the developers (57%) considered that corrections and modifications are currently not implemented quickly enough. The most popular means of user participation were that 'users would present their work and needs related to it in their workplace' (76%), followed by user groups (75%). The developers suggested many traditional user-centered and usability design methods, too. The developers' views were compared to the views of the physicians who primarily used the case company's products. The views were in direct opposition on whether developers are interested in end users' views (90% of the developers agreed, vs. 60% of the physicians disagreed) and take them into account (81% of the developers agreed, vs. 63% of the physicians disagreed), as well as on user groups (favored by 75% of the developers vs. 14% of the physicians). The majority of the respondents, both developers (57%) and physicians (74%), were dissatisfied with the pace of implementation of corrections and modifications.ConclusionsBoth physicians and developers seem to be "willing but not able" to collaborate with each other. Possible reasons for the differences in views include the fact that there is no return channel of communication on what happened to the end users' feedback, and that developers collaborate with customer representatives who are not end users. It is obvious that there are one or more spots along the route between the "end developers" and end users where there is a breakdown of the information flow.Copyright © 2013 Elsevier Ireland Ltd. All rights reserved.

      Pubmed     Full text   Copy Citation     Plaintext  

      Add institutional full text...

    Notes

     
    Knowledge, pearl, summary or comment to share?
    300 characters remaining
    help        
    You can also include formatting, links, images and footnotes in your notes
    • Simple formatting can be added to notes, such as *italics*, _underline_ or **bold**.
    • Superscript can be denoted by <sup>text</sup> and subscript <sub>text</sub>.
    • Numbered or bulleted lists can be created using either numbered lines 1. 2. 3., hyphens - or asterisks *.
    • Links can be included with: [my link to pubmed](http://pubmed.com)
    • Images can be included with: ![alt text](https://bestmedicaljournal.com/study_graph.jpg "Image Title Text")
    • For footnotes use [^1](This is a footnote.) inline.
    • Or use an inline reference [^1] to refer to a longer footnote elseweher in the document [^1]: This is a long footnote..

    hide…

What will the 'Medical Journal of You' look like?

Start your free 21 day trial now.

We guarantee your privacy. Your email address will not be shared.