– National welfare technology program – benefits realization reports
– Welfare technology in central introduction of welfare technology in the city boroughs of Oslo (1/2)
– Welfare technology in central introduction of welfare technology
– Meld. St. no. 29 (2012-2013) “Tomorrow’s care” (regjeringen.no)
– Technical report on welfare technology
– NOU 2011: 11 “Innovation in care” (regjeringen.no)
– Future aging and new technologies (teknologiradet.no)
– Organization and Design of Response Center service (2016)
– Organization of alarm reception in Norway and abroad (2014)
Large-scale, potentially transformative, implementations of health information technology are now being planned and undertaken in multiple municipalities, 32 municipalities are part of the National Welfare program in Norway.
– Develop and test welfare technological solutions
– Create and disseminate knowledge
– Competence
– Establish standards and IT architecture
– 32 municipalities are part of the program
– Erfaringer fra pilotering av velferdsteknologi i Sarpsborg kommune, Høgskolen i Østfold, Oppdragsrapport 2015:4 – Cathahrina Bjørnquist
– Prioritering og kompetanse i bruk av velferdsteknologi i Telemark, Vestfold og Buskerud 2015. Høgskolen i Søst Øst Norge, Senter for omsorgsforskning, Per Gunnat Disch og Heidi Johansen
– Velferdsteknologi og hjemmeboende eldre, Høgskolen i Nord Trøndelag, Siri Andersen Devik og Ove Hellzen, Rapport 79 2013
– Velferdsteknologi – en studie knyttet til ledelsesmessige utfordringer ved implementering av velferdsteknologi innen helse og omsorg. Høgskolen i Trøndelag, 2015, Inger Lise Fiskvik
– Velferdsteknologi fra planer til prosjekt. NTNU, Desmber 2015, Gulizar Astroshi
– Implementering av velferdsteknologi i helse og omsorgstjenesten – Høgskolen i Sør Øst Norge, 2015, Janne Daugstad, Etty R. Nilsen, Monika K. Gullsett, Tom Eide og Hilde EideTechnical: usability, system performance, integration and interoperability, stability and reliability, adaptability and flexibility, cost, accessibility and adaptability of hardware
– That one of the biggest challenge in the development and deployment of welfare technology is communication gap between technicians and health professionals
– Competence and understanding of digitalization
– Change Challenges
– Change processes, Changing Culture
– Organizational challenges
– Organizational structure, Organizational culture and Organizational anchoring
– Strategic challenges
– Political Anchoring, Collaboration with private suppliers
– Management Challenges
– Change Management, Implementing and Competence
Wider socio-political: other healthcare organizations, industry, policy, professional groups, independent bodies, the wider economic environment, international developments
– Establishing the need for change
– Selecting a system
– Implementation planning
– Maintenance and evaluationFigure 1

1. Clarify what problem(s) the technology is designed to help tackle
Many welfare technology procurements are based on assumed benefits, which are often poorly specified. This can result in difficulties agreeing on a shared vision across the healthcare organization. While terms like ‘improved quality of care’ and ‘improved efficiency’ are often used, detailed outcomes resulting from specific functionality are hard to measure and to anticipate as most implementations require fundamental changes to operational processes and many organizations do not even attempt this. Thus, organizations often encounter difficulties conceptualizing the required short-, medium-, and long-term transformations.
A thorough mapping of existing work processes before implementation can mitigate this risk and help to identify existing problems as well as areas for improvement. In a business case in one of Norway largest municipalities my colleague was mapping the existing work process for the municipality. Then the work processes were redesign for the municipality. After the design of new work processes the process need to be implemented across different sectors in the health care of the municipality.
Professional, managerial, and administrative consensus needs to be built around the strategic vision, in addition to creating the means to support the realization of this vision. This may involve considering whether to aim for radical changes across the, or whether to focus on streamlining specific work processes, initially and then expanding functionality over time. Many authors in the field of organizational change have highlighted that high-level strategic leadership of senior management including both administrative and health care leaders is vital, and this is accurate, but it is also essential to involve and get the buy-in of different professional stakeholder groups (eg, doctors, nurses, administrative staff, managers) to facilitate co-ownership and ensure commitment. From our experience, this balance is best achieved through the creation of a high-level strategic group that not only includes senior managers, but also clinical and administrative leads who represent different end-user groups.
Once the need for a technological system has been established, it is important to commit adequate time and resources to thoroughly consider different options in terms of which system(s) to choose. We have found that this aspect of planning and the associated writing of business cases and procurement considerations are sometimes under-estimated and often rushed. Visiting other healthcare settings that have implemented similar technology can prove very helpful.
Once a decision on the basic type of system has been made, it is important to base the final choice not only on organizational, but also on clinical needs. A system should be both fit for organizational purpose and fit for health care practice. There are countless examples of systems that have been procured but never used or are deployed in unintended ways, which will then typically result in a failure to realize the hoped-for improvements
It takes both targeted and reflective efforts to plan for transformative organizational ventures of any kind. Although flexibility in strategy is required, there are some general pointers that tend to characterize effective preparation across organizations and technologies. These include the aforementioned necessity to engage extensively with potential suppliers and other organizations who have already implemented, but also the decision to prioritize the implementation of functionality that can bring benefits to the greatest number of end-users as early as possible. Other factors relate to the avoidance of ‘scope-creep’ and maintaining open channels of communication between management and users.
Developing the right infrastructure is an essential part of planning activity. If this is not afforded sufficient attention, then software systems may perform sub-optimally, or may be inaccessible to users altogether. Again, this increases the possibility that systems are not used at all or used in ways other than intended, potentially compromising benefits and increasing risks associated with technological systems.
Trained users tend to be more satisfied with new technologies than those who have not been adequately trained. In the municipality case, we first trained the deployment leaders, then the super users and then the super users trained 4000 end users.
Although it is now widely recognized that evaluation is important when considering new technologies, the reality is that it is still, more often than not, an afterthought as immediate implementation activities take priority. It is essential to capture user feedback about problems that are identified and respond to it in a timely manner.
Maintenance is in many ways related to all of the above points as these issues need to be re-visited periodically throughout the technology lifecycle. Nevertheless, maintenance deserves particular attention as it is often under-estimated in relation to associated activities and cost. This is not only the case in relation to on-going costs, but also costs relating to potential system changes as the strategic aims of organizations and therefore the capabilities of existing technological systems are likely to change over time
The benefits of major transformative programs are notoriously difficult to measure and may take a long time to materialize. However, this is not to say that they are non-existent, rather they need to be tracked by appropriate evaluation work assessing how the new system is used and re-invented locally. This also requires an appreciation of the timelines surrounding the realization of expected benefits, allowing enough time for technologies to embed and data to be exploited for secondary uses. Experience has shown that in many cases the expectations of organizations and individual users far exceed what is achievable in the short term. The managing of expectations is, therefore, important as otherwise there is a danger that stakeholders disengage with the initiative and negative attitudes may emerge.
Careful planning and on-going, critical evaluation of progress are central to the successful implementation of major health information technology. Taking a lifecycle perspective on the implementation of technological systems will, help organizations to avoid some of the all too commonly encountered pitfalls and improve the likelihood of successful implementation and adoption. It is, however, important to keep in mind that, although the stages and considerations discussed here were depicted in a linear manner, they may to some extent overlap.