Skip to main content
Log in

“Remain Faithful to the Earth!”*: Reporting Experiences of Artifact-Centered Design in Healthcare

  • Published:
Computer Supported Cooperative Work (CSCW) Aims and scope Submit manuscript

Abstract

In this paper we report about two design experiences in the domain of healthcare information technology that shed light on the advantages of getting rid of complex and abstract representations of hospital work and of concentrating on the artifacts that practitioners habitually use in their daily practice. We ground our approach in the recent literature on the often unintended shortcomings exhibited by healthcare information systems and propose a lightweight method to support the phases of requirement elicitation and functional design. We then discuss the main requirements expressed in our recent research activity and provide examples of how to address them in terms of modular and reusable design solutions.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Figure 1
Figure 2

Similar content being viewed by others

Notes

  1. Likewise, ontologies are increasingly used to model concepts and relationships in human domains and how software components can collaborate to support such domains.

  2. Technology in working order. Studies of work, interaction, and technology (Eds: Button G), Routledge, London, 1993, cited in Goorman and Berg (2001).

  3. Suggestively, Orlikowski and Iacono (2001) define the IT artifacts as “those bundles of material and cultural properties packaged in some socially recognizable form such as hardware and/or software” [p. 121].

  4. Quite confusingly, in much literature especially from the Information Systems field (e.g., design research (Hevner et al. 2004)) also formal representations and models are denoted as artifacts (so that artifact-centered approaches are likened to rationalistic, top–down ones, cf. e.g. (Pentland and Feldman 2008)). To this respect, the artifacts we refer to are the material (but not necessarily tangible, as noted by Schmidt (2010, p. 283)), inscribed, symbolic, socially recognizable (Orlikowski and Iacono 2001) objects that actors use to perform and articulate their work, like, e.g., their documents and records.

  5. We are then not referring to the general meaning that “bottom–up” has in strategies that are mentioned in methodologies of either relational schemas drafting, model integration or procedural programming; in these contexts strategies are called bottom–up in that they, respectively, integrate small portions of a conceptual model into a bigger/more abstract one, or support the construction of complex software applications from smaller modules (as it is common in Object-Oriented programming).

  6. This has also to do with what Goguen (1992) denoted as a post-modern approach to requirement elicitation and with the reason why I defend the expression “artifact-centered” notwithstanding the double-cut paradox of centering something on artifacts instead of users or work itself.

  7. In a protocol analysis, users are invited to use their habitual artifacts in individual sessions and, while simulating some usual work task, to concurrently speak aloud to explain what they do. It is noteworthy to say that, differently from the earlier proponents of these talk-aloud protocols, we do not consider these methods as a structured way to get “a direct verbalization of specific cognitive processes” (Ericsson and Simon 1993, p. 16) or to delve into the more or less tacit reasons why artifacts are used the way they are. Rather, we agree with Goguen and Linde (1993) that protocol analysis cannot be taken as a model of human problem solving and that its value, especially in the ambit of an artifact analysis, comes mainly from the opportunity to artificially “slow down” the use of an artifact. In this way, analysts can be facilitated in seeing passages of usage that an external observer could just miss, or neglect. Moreover, in so doing analysts can also get a clue of what passages are considered the most important by the users themselves, and of what conventions are at play while they make use of the content that the artifact represents and conveys.

  8. For instance, situatedness of action and context, sociality of work, accountability and orderliness of the social world (Goguen 1996).

  9. Interestingly, a reviewer noted that an artifact-centered approach tends to focus more on the design of structures than to the design of interactions. This is a very subtle point in that this approach is imbued with the feeling that designers cannot but design just structures, and that the interactions that are mediated by these structures will simply follow, even in unpredicted and unintended ways, once a technology is appropriated by the users, as they adopt it and adapt themselves to its capabilities (Orlikowski 2000). This is a point that is thoroughly discussed and argued in the rich literature about the structurational models of technology design. Yet, the reviewer’s suggestion reminds me of some seminal ideas coming from the field of Design Research that an artifact is “structurally coupled” with its environment, much similar as its users are, according to Maturana and Varela (1992), on the basis of both their physical nature and their ontogenesis (i.e. personal memories, previous social interactions and experiences). And, to some extent, it also reminds me of the “law of requisite variety”, first formulated by Ashby in 1956 speaking of his first homeostats (Pickering 2004), where the problem of the design of sufficiently flexible and complex structures can be rephrased in the following terms: a system can support something else (another system or an actor) only to the extent that it has sufficient internal variety that can couple the variety of the other system.

  10. Discussing this conditional pattern would make it necessary to dwell on the details of rule-based programming (or on the specific artifact logic of partitioning) and would be out of the scope of this paper.

References

  • Ackerman, M. S., & Halverson, C. (1999). Organizational memory: Processes, boundary objects, and trajectories. In HICSS’99: Proceedings of the IEEE Hawaii International Conference of System Sciences, Society Press.

  • Anderson, B. (1998). The Encyclopedia of Microcomputers, Vol. 20, Dekker, New York, USA, chap Work, Ethnography and System Design, pp. 159–183.

  • Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: the nature of patient care information system-related errors. JAMIA, 11(2), 104–112.

    Google Scholar 

  • Ash, J. S., Sittig, D. F., Poon, E. G., Guappone, K., Campbell, E., & Dykstra, R. H. (2007). The extent and importance of unintended consequences related to computerized provider order entry. JAMIA, 14(4), 415–423.

    Google Scholar 

  • Atkinson, C. J., & Peel, V. J. (1998). Transforming a hospital through growing, not building, an electronic patient record system. Methods of Information in Medicine, 37(3), 285–293.

    Google Scholar 

  • Balfour, D., Evans, S., Januska, J., Lee, H., Lewis, S., Nolan, S., et al. (2009). Health information technology - results from a roundtable discussion. Journal of Managed Care Pharmacy, 15(1), 10–17.

    Google Scholar 

  • Balka, E. (2003). Getting the big picture: the macro-politics of information system development (and failure) in a Canadian hospital. Methods of Information in Medicine, 42(4), 324–330.

    Google Scholar 

  • Bath, P. A. (2008). Health informatics: current issues and challenges. Journal of Information Science, 34(4), 501–518.

    Article  Google Scholar 

  • Batini, C., Ceri, S., & Navathe, S. B. (1992). Conceptual database design: an Entity-relationship approach. Redwood City: Benjamin-Cummings Publishing Co., Inc.

    MATH  Google Scholar 

  • Benson, T. (2002). Why general practitioners use computers and hospital doctors do not - part 1: incentives. British Medical Journal, 9(325), 1086–1089.

    Article  Google Scholar 

  • Berg, M. (1997). Of forms, containers, and the electronic medical record: some tools for a sociology of the formal. Science, Technology & Human Values, 22(4), 403–433.

    Article  Google Scholar 

  • Berg, M. (1998). Medical work and the computer-based patient record: a sociological perspective. Methods Inf Med, 37(3), 294–301.

    Google Scholar 

  • Berg, M. (1999). Patient care information systems and health care work: a sociotechnical approach. International Journal of Medical Informatics, 55(2), 87–101.

    Article  Google Scholar 

  • Berg, M. (2001). Implementing information systems in health care organizations: myths and challenges. International Journal of Medical Informatics, 64(2–3), 143–156.

    Article  Google Scholar 

  • Berg, M., & Toussaint, P. (2002). The mantra of modeling and the forgotten powers of paper: a sociotechnical view on the development of process-oriented ICT in health care. International Journal of Medical Informatics, 69(2–3), 223–234.

    Google Scholar 

  • Bower, A. G. (2005). The diffusion and value of healthcare information technology. The CERNER Quarterly, Q3, 16–26.

    Google Scholar 

  • Braithwaite, J., Runciman, W., & Merry, A. (2009). Towards safer, better healthcare: harnessing the natural properties of complex sociotechnical systems. Quality & Safety in Health Care, 18(1), 37–41.

    Article  Google Scholar 

  • Bringay, S., Barry, C., & Charlet, J. (2006). Annotations: A functionality to support cooperation, coordination and awareness in the electronic medical record. In: COOP’06: Proceedings of the 7th International Conference on the Design of Cooperative Systems, France, Provence.

  • Brooks, R. A. (1991). Intelligence without representation. Artificial Intelligence, 47, 139–159.

    Article  Google Scholar 

  • Cabitza, F., & Gesso, I. (2011). Web of active documents: an architecture for flexible electronic patient records. In A. Fred, J. Filipe, H. Gamboa (Eds.), BIOSTEC 2010, Communications in Computer and Information Science, vol 127, Springer 2011.

  • Cabitza, F., & Simone, C. (2006). “You taste its quality”: Making sense of quality standards on situated artifacts. In MCIS’06: Proceedings of the First Mediterranean Conference on Information Systems, Venice, Italy, Association for Information Systems.

  • Cabitza, F., & Simone, C. (2009a). Active artifacts as bridges between context and community knowledge sources. In: C&T2009: Proceedings of the 4th International Conference on Communities and Technologies. June 2009. Penn State University, PA, USA.

  • Cabitza, F., & Simone, C. (2009b). LWOAD: a specification language to enable the end-user development of coordinative functionalities. In V. Pipek, M. B. Rosson, B. E. R. de Ruyter, V. Wulf (Eds.), IS-EUD’09: Proceedings of the 2nd International Symposium on End-User Development, 2009, Siegen, Germany, March 2–4, 2009., Springer, Lecture Notes in Computer Science, vol. 5435, pp. 146–165.

  • Cabitza, F., & Simone, C. (2010). WOAD: a framework to enable the end-user development of coordination oriented functionalities. Journal of Organizational and End User Computing, 22(2).

  • Cabitza, F., Sarini, M., Simone, C., & Telaro, M. (2005). “When Once Is Not Enough”: The role of redundancy in a hospital ward setting. In GROUP’05: Proceedings of the 2005 International ACM SIGGROUP Conference on Supporting Group Work, ACM Press, Sanibel Island, Florida, U.S.A., pp. 158–167.

  • Cabitza, F., Simone, C., & Sarini, M. (2009). Leveraging coordinative conventions to promote collaboration awareness. CSCW, 18, 301–330.

    Google Scholar 

  • Cabitza, F., Simone, C., Zorzato, G. (2009b). ProDoc: an electronic patient record to foster process-oriented practices. In: ECSW’09: Proceedings of the European Conference on Computer Supported Cooperative Work. Vienna, Austria, September 9–11, 2009., Springer, pp. 119–138.

  • Campbell, E. M., Sittig, D. F., & Ash, J. S. (2006). Types of unintended consequences related to computerized provider order entry. JAMIA, 13(5), 547–556.

    Google Scholar 

  • Chaudhry, B., Wang, J., Wu, S., Maglione, M., Mojica, W., Roth, E., et al. (2006). Systematic review: Impact of health information technology on quality, efficiency, and costs of medical care. Annals of Internal Medicine, 144, 12–22.

    Google Scholar 

  • Chen, P. (1976). The entity-relationship model: toward a unified view of data. ACM Transactions on Database Systems, 1(1), 9–36.

    Article  Google Scholar 

  • Debono, D., Greenfield, D., Black, D., & Braithwaite, J. (2010). Workarounds: straddling or widening gaps in the safe delivery of healthcare? In: In the Proceedings of the 7th International Conference in Organisational Behaviour in Health Care (OBHC) - Mind the Gap: Policy and practice in the reform of health care (Birmingham, England: Society for the Study of Organising in Health Care, 11–14 April).

  • Denzin, N. K., & Lincoln, Y. S. (2003). Collecting and interpreting qualitative materials. SAGE.

  • Dykstra, R. H. et al. (2009). Persistent Paper: The Myth of “Going Paperless”. AMIA Annu Symp Proc. 2009.

  • Dyro, J. F. (2004). Clinical engineering handbook. Academic Press series in biomedical engineering Biomedical Engineering Series, Academic Press.

  • Ellingsen, G., & Monteiro, E. (2006). Seamless integration: standardisation across multiple local settings. CSCW, 15(5–6), 443–466.

    Google Scholar 

  • Ericsson, K. A., & Simon, H. A. (1993). Protocol analysis - Rev’d Edition: Verbal Reports as Data. The MIT Press.

  • Gadd, C. S., & Penrod, L. E. (2000). Dichotomy between physicians’ and patients’ attitudes regarding emr use during outpatient encounters. In Proceedings of AMIA Symposium, pp. 275–279.

  • Garfinkel, H. (1967). Studies in Ethnomethodology, Prentice-Hall, New Jersey, USA, chap “Good” organizational reasons for “bad” clinic records, pp. 186–2006.

  • Goguen, J. (1992). Information systems concepts, Elsevier, chap The dry and the wet, pp. 1–17.

  • Goguen, J. A. (1996). Formality and informality in requirements engineering. Requirements Engineering, IEEE International Conference on, pp. 102–109.

  • Goguen, J., & Linde, C. (1993). Techniques for requirements elicitation. In: Requirements Engineering, 1993., Proceedings of IEEE International Symposium on, pp. 152–164.

  • Goorman, E., & Berg, M. (2001). Modelling nursing activities: electronic patient records and their discontents. Nursing Inquiry, 7(1), 3–9.

    Article  Google Scholar 

  • Gorman, P., Ash, J., Lavelle, M., Lyman, J., Delcambre, L., Maier, D., et al. (2000). Bundles in the wild: managing information to solve problems and maintain situation awareness. Library Trends, 49(2).

  • Grimson, J. (2001). Delivering the electronic healthcare record for the 21st century. International Journal of Medical Informatics, 64, 111–127.

    Article  Google Scholar 

  • Grudin, J. (1988). Why CSCW Applications Fail: Problems in The Design And Evalutation of Organizational Interfaces. In: CSCW ’88: Proceedings of the International Conference on Computer Supported Cooperative Work, ACM Press, Portland, Oregon, USA, pp. 85–93.

  • Halbesleben, J., Wakefield, D., & Wakefield, B. (2008). Work-arounds in health care settings: literature review and research agenda. Health Care Management Review, 33(1), 2–12.

    Google Scholar 

  • Harrison, M. I., Koppel, R., & Bar-Lev, S. (2007). Unintended consequences of information technologies in health care - an interactive sociotechnical analysis. JAMIA, 14, 542–549.

    Google Scholar 

  • Hartswood, M., Procter, R., Slack, R., VoßA, B. M., Rouncefield, M., & Rouchy, P. (2002). Co-realisation: towards a principled synthesis of ethnomethodology and participatory design. Scandinavian Journal of Information Systems, 14(2), 9–30.

    Google Scholar 

  • Hartswood, M., Procter, R., Rouncefield, M., & Slack, R. (2003). Making a case in medical work: implications for the electronic medical record. CSCW, 12, 241–266.

    Google Scholar 

  • Heath, C., & Luff, P. (2000). Technology in action. Cambridge: Cambridge University Press.

    Book  Google Scholar 

  • Heeks, R. (2006). Health information systems: failure, success and improvisation. International Journal of Medical Informatics, 75, 125–137.

    Article  Google Scholar 

  • Hevner, A. R., March, S. T., Park, J., & Ram, S. (2004). Design science in information systems research. MIS Quarterly, 28(1), 75–105.

    Google Scholar 

  • Hollan, J., Hutchins, E., & Kirsh, K. (2000). Distributed cognition: toward a new foundation for human-computer interaction research. ACM Trans Comput-Hum Interact, 7(2), 174–196.

    Article  Google Scholar 

  • Hutchins, E. (1996). Cognition in the wild. Cambridge: The MIT Press.

    Google Scholar 

  • Illich, I. (2000). Medical nemesis, the expropriation of health. Marion Boyars Publishers Ltd, 1975.

  • Jones, M. (2003). Computers can land people on Mars, why can’t they get them to work in a hospital? Implementation of an Electronic Patient Record system in a UK Hospital. Methods of Information in Medicine, 42, 410–415.

    Google Scholar 

  • Kensing, F., Sigurdardottir, H., & Stoop, A. (2007). MUST - a participatory method for designing sustainable health IT. Studies in Health Technology and Informatics, 129(2), 1204–1208.

    Google Scholar 

  • Koppel, R., Metlay, J. P., Cohen, A., Abaluck, B., Localio, A. R., Kimmel, S. E., et al. (2005). Role of computerized physician order entry systems in facilitating medication errors. JAMIA, 293, 1197–1203.

    Article  Google Scholar 

  • Latour, B. (1999). Actor network theory and after. Wiley-Blackwell, chap On recalling ANT.

  • Lieberman, H., Paterno, F., & Wulf, V. (Eds.) (2006). End-user development. Springer.

  • Lincoln, Y., & Guba, E. (1985). Naturalistic inquiry. Sage Publications, Inc.

  • Maturana, H., & Varela, F. J. (1992). The tree of knowledge: The biological roots of human understanding. Boston: Shambhala Publications.

    Google Scholar 

  • Nemeth, C., Cook, R., O’Connor, M., & Klock, P. (2003). Using cognitive artifacts to understand distributed cognition. In: Systems, Man and Cybernetics, 2003. IEEE International Conference on, vol 2, pp. 1766–1771.

  • Nemeth, C., Nunnally, M., Connor, M., Klocka, P., & Cook, R. (2005). Getting to the point: developing it for the sharp end of healthcare. Journal of Biomedical Informatics, 38(1), 18–25.

    Article  Google Scholar 

  • Niesa, J., & Pelayo, S. (2009). From users involvement to users’ needs understanding: a case study. Int J Med Inform.

  • Norman, D. A. (1988). The design of everyday things. New York: Doubleday.

    Google Scholar 

  • Nowinski, C., Becker, S., Reynolds, K., Beaumont, J., Caprinia, C., & Hahn, E. (2007). The impact of converting to an electronic health record on organizational culture and quality improvement. International Journal of Medical Informatics, 76(1), 174–183.

    Article  Google Scholar 

  • Orlikowski, W. J. (2000). Using technology and constituting structures: a practice lens for studying technology in organizations. Organization Science, 11, 404–428.

    Article  Google Scholar 

  • Orlikowski, W. J., & Iacono, C. S. (2001). Desperately seeking the “it” in it research? A call to theorizing the it artifact. Information Systems Research, 12(2), 121–134.

    Article  Google Scholar 

  • Palmieri, P. A., & Peterson, L. T. (2008). Technological iatrogenesis: An expansion of the medical nemesis framework to improvemodern healthcare organization performance. In: Proceedings of the Western Academy of Management 2008 Annual Meeting, March 26–29 Oakland, California, USA.

  • Patton, M. (2002). Qualitative research and evaluation methods (3rd ed.). Sage

  • Pentland, B. T., & Feldman, M. S. (2008). Designing routines: on the folly of designing artifacts, while hoping for patterns of action. Information and Organization, 18, 235–250.

    Article  Google Scholar 

  • Pickering, A. (2004). The science of the unknowable: Stafford beer’s cybernetic informatics. Kybernetes, 33(3/4), 499–521.

    Article  MathSciNet  Google Scholar 

  • Poissant, L., Pereira, J., Tamblyn, R., & Kawasumi, Y. (2005). The impact of electronic health records on time efficiency of physicians and nurses: a systematic review. JAMIA, 12(5).

  • PricewaterhouseCoopers (2001). Patients or paperwork? The regulatory burden facing america’s hospitals. Tech. rep., American Hospital Association.

  • Robinson, M., & Bannon, L. (1991). Questioning representations. In: ECSCW’91: Proceedings of the 2nd European Conference on CSCW, Amsterdam, The Netherlands.

  • Sauer, C. (1993). Why information systems fail: a case study approach. Alfred Waller Ltd.

  • Scandurra, I., Haegglund, M., & Koch, S. (2008). From user needs to system specifications: multi-disciplinary thematic seminars as a collaborative design method for development of health information systems. Journal of Biomedical Informatics, 41(4).

  • Schmidt, D. (2006). Model-driven engineering. IEEE Computer, 39(2), 25–31.

    Article  Google Scholar 

  • Schmidt, K. (2010). ‘keep up the good work!’ - the concept of ‘work’ in cscw. In: COOP 2010: Proceedings of the 9th International Conference on Designing Cooperative Systems, May, 18–21, 2010, Aix-en-Provence, Springer, pp. 265–286.

  • Schmidt, K., & Wagner, I. (2004). Ordering systems: coordinative practices and artifacts in architectural design and planning. CSCW, 13(5–6), 349–408.

    Google Scholar 

  • Sidorov, J. (2006). It ain’t necessarily so: the electronic health record and the unlikely prospect of reducing health care costs. Health Affairs, 25(4), 1079–1085.

    Article  MathSciNet  Google Scholar 

  • Silverston, L. (2007). The data model resource book. Wiley.

  • Spolsky, J. (2004). Joel on software: and on diverse and occasionally related matters that will prove of interest to software developers, designers, and managers. Apress.

  • Strauss, A. (1985). Work and the division of labor. The Sociological Quarterly, 26(1), 1–19.

    Article  Google Scholar 

  • Strauss, A., Fagerhaugh, S., Suczek, B., & Wiener, C. (1985). The social organization of medical work. University of Chicago Press.

  • Suchman, L. A. (1987). Plans and situated actions: The problem of human-machine communication. Cambridge University Press.

  • Suchman, L., & Jordan, B. (1990). Interactional troubles in face-to-face survey interviews. Journal of the American Statistical Association, 85(409), 232–241.

    Article  Google Scholar 

  • Tierney, W., & McDonald, C. (1996). Testing informatics innovations: the value of negative trials. JAMIA, 3(5), 358–359.

    Google Scholar 

  • Verbeek, P. P. (2006). Acting artifacts. In A. Slob & P. P. Verbeek (Eds.), User behavior and technology development (pp. 53–60). Springer Netherlands.

    Chapter  Google Scholar 

  • Wasson, C. (2000). Ethnography in the field of design. Human Organization, 59(4), 377–388.

    Google Scholar 

  • Wears, R. L., & Berg, M. (2005). Computer technology and clinical work: still waiting for godot. JAMIA, 293(10), 1261–1263.

    Article  Google Scholar 

  • Wenger, E. (1998). Communities of practice: learning, meaning, and identity. Cambridge University Press.

  • Wieringa, R. J. (1996). Requirements engineering: frameworks for understanding. Addison-Wesley.

  • Winograd, T., & Flores, F. (1986). Understanding computers and cognition: A new foundation for design. Reading: Addison Wesley.

    MATH  Google Scholar 

  • Winthereik, B. R., & Vikkelso, S. (2005). Ict and integrated care: some dilemmas of standardising inter-organisational communication. CSCW, 14(1), 43–67.

    Google Scholar 

  • Wirth, N. (1971). Program development by stepwise refinement. Communications of the ACM, 14(4), 221–227.

    Article  MATH  Google Scholar 

Download references

Acknowledgements

I would like to express my gratitude to Carla Simone for the autonomy that she afforded me in conducting the studies described in this paper and for her constant encouragement about the points I made in Sections 1 and 2; to the MOHU and MAPU staff for the patience they showed me when I asked them all the silly questions outlined in Table 1; and to Stefano Corna and Iade Gesso for their valuable suggestions on the descriptions of the elementary operations outlined in Table 2.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Federico Cabitza.

Additional information

Friedrich W. Nietzsche, Thus Spoke Zarathustra. Cambridge University Press, 2006. Trans. A. Del Caro. Prologue, 3, p. 6 (orig. bleibt der Erde treu).

Rights and permissions

Reprints and permissions

About this article

Cite this article

Cabitza, F. “Remain Faithful to the Earth!”*: Reporting Experiences of Artifact-Centered Design in Healthcare. Comput Supported Coop Work 20, 231–263 (2011). https://doi.org/10.1007/s10606-011-9143-1

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10606-011-9143-1

Key words

Navigation