<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>When Public Information System Procurement Meets Open Ecosystems: Experiences from Finland</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sinna Pirinen</string-name>
          <email>sinna.e.pirinen@student.jyu.fi</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Samuli Pekkola</string-name>
          <email>samuli.j.pekkola@jyu.fi</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tommi Mikkonen</string-name>
          <email>tommi.j.mikkonen@jyu.fi</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Information Technology, University of Jyväskylä</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Proceedings EGOV-CeDEM-ePart conference</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Public sector organisations serve citizens and firms through networked services. Developing these services is a complex task, as all actors want to keep their data to themselves and not to share it with the others. In this paper, we present a case study on Finnish electronic health and social services, particularly its open data ecosystem called Kanta. We study how the characteristics of open data ecosystems: data, its sharing, cooperation, and their value, influence the public procurement of annexed information systems (IS). As the new system specifications are defined by the open data ecosystem and not by the procurement unit, the procurement is not completely managed by the procuring organisation. Our results suggest that utilising the open data ecosystem definitions has no direct impacts on the IS procurement project per se, but they solve some procurement challenges: the lack of expertise, understanding the target system, and complexity.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;public sector procurement</kwd>
        <kwd>information system procurement</kwd>
        <kwd>open data ecosystem 1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Public sector organisations provide services to citizens and firms [33]. This service
provision is in a flux due to changing political and economic environment, pressures to cut costs,
and switching governmental management isms. The organisations thus try to exploit digital
technologies, such as information systems, in their services and service provision.</p>
      <p>
        To make this digital transformation possible, information systems (IS) use large amounts
of data [12]. Often, open data is seen as means to utilise the organisation’s external
resources [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], [37]. The IS are developed in ecosystems where a group of organisations
collaborate [25]. The ecosystem is thus not only providing the data but also creating shared
value [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [16] and promoting innovation [34]. The open data ecosystem concept
emphasises data sharing through public licenses within software ecosystems [37].
      </p>
      <p>The challenges of public IS procurement are well known [14], [30]. For example,
acquiring large systems are often unique so the procurement unit may lack experiences. They may
thus fail e.g. in eliciting the system requirements [27]. Public IS procurement is a complex
process [17]. This means that when the governments promote digital transformation, they
seek international solutions and best practices [8]. This requires aggregation of public
organisations, their digital transformation and IS procurement, and open data ecosystems.</p>
      <p>In this paper, we study the relationship between an open data ecosystem, its
characteristics, and the public IS procurement. We answer the research question: “How do the
characteristics of the open data ecosystem impact on IS procurement in the public sector?” We
present a case study of public procurements to the electronic social and health services
(Kanta services) in Finland. We suggest that the open data ecosystem characteristics have
no direct impacts on the procurement process from the laws and regulations points of view,
but they help to cope with the lack of expertise and understanding the procurement target.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <sec id="sec-2-1">
        <title>2.1. Open data ecosystem</title>
        <p>The creation, exchange, and use of data have evolved with technologies, leading to the
emergence of data ecosystems where entities share valuable information [34]. Open data
ecosystems have several characteristics contributing to their challenges and benefits [37]: value
of data, relationships between entities, legal issues, data quality, data acquisition, maturity,
value of collaboration and competition. This study focuses on three key themes: (i) political,
legal, and cultural factors; (ii) lack and discrepancy of standards, and (iii) data costs. Figure
1 illustrates the open data characteristics in themes as they appear in the literature.</p>
        <p>In the political, legal and cultural factors theme, the value of the data lies in
understanding the business models and costs related to data collection and interpretation. The
challenges with the value of data characteristics include mutual hardware and domain models,
and explicitly clarified business value. The value of data characteristics can also help to
uncover new market insights and end users [37], which can benefit decision-making and drive
innovation within the ecosystem.</p>
        <p>The relationships characteristics belongs to the political, legal and cultural factors
theme. It refers to the relationships between actors in the ecosystem. The lack of
communication between them causes challenges [6]. As building stable relationships between the
actors can be difficult, it is essential to involve a trustworthy party, such as a public actor,
to support the partnerships [37].</p>
        <p>The theme also includes the legal characteristics, referring to legislation on data and
licensing [37]. Legal challenges include the data producers’ rights if the data contains
personal information on users. The challenges are also ethical as individual data producers
should have the possibility to manage their own data [39] and know who is responsible for
the system operations [6]. Different licenses complicate data sharing [20], [37]. There are
also differences in legislation between countries, hindering cooperation [39]. The lack of
political commitment can also hinder the development of common methods and standards
[31].</p>
        <p>The lack and discrepancy of standards theme includes the data quality
characteristics. They focus on data quality and the factors impacting the quality. The challenges arise
from the growing data volume, and its impacts on costs and quality criteria [37]. Validating
the data quality is a challenge, with certifications and the limitations to import data into the
ecosystem [19]. Sharing the costs and standardising the processes are beneficial [37].</p>
        <p>Data acquisition includes data intermediary services and acquisition. It is part of the lack
and discrepancy of standards theme. The challenges include the need for joint data
collection. Resource disparities among actors can lead to variations in data quality [37].</p>
        <p>The maturity of the ecosystem from the competence and standardisation point of views
is also related to data standadisation. Maturity challenges include the lack of capacity and
technical requirements in sharing the data. The standardisation of the processes is essential
to ensure consistent data sharing practices [37]. Establishing standards early guarantee
interoperability across various regions and countries [20].</p>
        <p>The value of the collaboration is related to the data costs theme. It refers to the impacts
that arise from different actors collaborating around the data [37]. For example, later
joining parties often initiate new expenses as the data collecting and sharing costs may then rise
[20]. Joining to an ecosystem also requires changes in the organisational cultures and
processes [6]. In addition, some might not want to share their data as it can be seen as
competitive advantage [37]. This causes data lock-in situations. Collaboration benefits however
stem from the potential to create new markets, products, and services [37]. For example,
cloud-based open data ecosystems offer opportunities for solutions that enhance the
scalability and capacity of services [20]. Shared data collection costs enable smaller actors to join
the ecosystem [37]. However, the open data ecosystems do not operate on exact reciprocity
since the advantages arise indirectly through the systems [35].</p>
        <p>The competition characteristics characteristics also belong to the data costs theme. It
denotes the competitive dynamics among the data sharing actors in the ecosystem.
Competition can cause concurrent activities and competition. Organisations may however
complement each other’s resources by promoting the creation of technological innovations [15].</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Public information system procurement</title>
        <p>The process of public procurement entails public sector organisations acquiring goods and
services through the act of buying or purchasing. It involves the acquisition of necessary
resources to meet the needs and objectives of these entities [18]. Rules and regulations are
essential for organising public sector purchasing, distinguishing it from the more-free
private sector practices [41].</p>
        <p>Purchasing IS is different from other types of public procurements. The procurement
unit must compare alternative solutions that work together with existing systems [29]. At
the same time, these systems have significant impact on organisations’ processes [38]. This
emphasises the importance of timely and coherent decision-making. In this paper, the
public IS procurement is presented in two themes: the process orientation of procurement, and
the procurement planning, vendor, and contract management complexity.</p>
        <p>The public procurement processes are highly regulated. In the European Union (EU), the
process is regulated by both the EU directives and national laws [30]. The EU directives aim
to promote transparency, equality, and fair competition. The directives control the member
states to act in accordance with national laws and obligations [7].</p>
        <p>The procurement process typically has six phases. The first phase is the recognition of
the procurement needs, followed by the call for tenders [17]. The call for tenders must be
announced publicly, either nationally or across the EU, if its value exceeds threshold values.
In open procedure, all vendors can submit their offers, while in restricted procedure the
number of vendors is limited by the procurement unit [30]. In the open procedure, the
vendors can ask questions from procurement units, but not negotiate [17] which takes place
later in the negotiation phase. After the negotiations, the winning vendor is selected. The
fifth phase starts with a procurement contract, followed by the acceptance phase [17].</p>
        <p>
          Some challenges are associated with public IS procurement. Standard software is usually
not suitable for the public sector, so the system is customised [40]. Large systems and their
requirements are challenging to define, especially if the stakeholders have conflicting
interests [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], [27]. In addition, public organisations often struggle with insufficient in-house
expertise [30] and resources [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. This leads to challenges with missing functionalities and
system quality assessment [27].
        </p>
        <p>Various technologies and integrations are essential in the IS procurements. It is critical
that the technologies are compatible with existing architectures [36]. Despite careful
planning, specifications, and negotiations, incompatibilities often emerge post-contract signing.
[29]. Sometimes system compatibility result in vendor dependency and lock-in situations
when the system switches are expensive. This means there is no de facto competition [5].
Competition can however be restricted in the public procurement process. The
procurement unit must follow regulated procedures [28], which leads to long and expensive
procurement practices at the vendors’ side. As a result, smaller vendors may opt out or be left
out due to financial reasons [29]. Also, standard contracts may limit vendor competition
and reduce options [30].</p>
        <p>Public entities adhere to regulations by focusing on the system selection rather than
vendors. However, the vendor experience can be considered as a relevant criterium [30]. It has
also been noticed that the procurement unit’s capacity to produce highly specific
specifications might preclude vendors from effectively demonstrating their capabilities [14], [29].</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Research methods and settings</title>
      <p>We study Kanta services, that comprise electronic social and health services in Finland [23].
Legislation enforces social and healthcare providers to upload the patient’s health data to
Kanta [23]. This means the provider's systems must be compatible with Kanta. Technically
Kanta services form an ecosystem that includes myriad services [22].</p>
      <p>In the public sector, the main developer parties of Kanta services are the Social Insurance
Institution (Kela), the Finnish Institute for Health and Welfare (THL) and the Ministry of
Social Affairs and Health (STM). Kela is responsible for technical development, support,
project planning and customer cooperation. THL serves as the preeminent authority in
information management, being responsible for the requirements specification while STM is
responsible for the funding, strategic direction and monitoring the results of Kanta services.
In addition, STM is responsible for drafting legislation concerning Kanta services [24]. The
social and healthcare enterprise architecture group (Sote EA group) at STM coordinates and
guides Kanta information management [42]. Other public actors contributing to Kanta
services are the National Supervisory Authority for Welfare and Health and the Digital and
Population Data Services Agency. The former provides attribute and role services while the
latter is accountable for the ID and certificate services [24]. In addition, numerous private
healthcare and IT organisations have joined or contributed to the ecosystem.</p>
      <p>Gaia-X is a European-wide initiative that builds a common data infrastructure to enable
data flows across Europe, foster innovation, ensure compliance with data protection laws,
and maintain trust through transparent standards [10]. Although Gaia-X includes various
ecosystems [9], our focus is solely on the health domain.</p>
      <p>We collected our data through semi-structured interviews by interviewing the main
stakeholders. First, we contacted the enterprise architecture group (Sote EA group) to gain
understanding about the Kanta services development. We then contacted Kela, responsible
for the technical development of Kanta services and its public procurement. We then
conducted interviews at the vendor side and in THL. Table 1 lists our interviewees.
The interviews were held in MS Teams application due to Covid restrictions. They were
audio-recorded and transcribed. The interviews focused on themes derived from grouping
open data ecosystem and public IS procurement characteristics from literature. The
questions also addressed the compatibility of the Kanta services with the open data ecosystem,
using Gaia-X as an example.</p>
      <p>We analysed the data through thematic analysis. The data was compared to the
preselected themes. All occurrences matching with the themes were identified and selected as
the descriptions of the theme. Altogether 105 instances (occurrences) were identified.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Findings</title>
      <p>Our findings show that the interviewees were mainly concerned about legal, political, and
cultural issues. The next most common themes were the procurement process, the
complexity of procurement planning, and supplier and contract management. The least focused
answers were the lack and discrepancy of standards and data costs. Table 2 presents the
themes and their descriptions in the order of their prevalence in the interviews.</p>
      <sec id="sec-4-1">
        <title>Finnish national laws should be modified to enable Kanta’s participation in the external ecosystem.</title>
      </sec>
      <sec id="sec-4-2">
        <title>Existing projects that aim to enable cross-border information exchange.</title>
      </sec>
      <sec id="sec-4-3">
        <title>Process ori</title>
        <p>entation of
procurement
Political,
legal &amp; cultural The goals of information sharing would certainly work.
factors Ethical challenges.</p>
        <p>Finding common consensus is slow.</p>
        <p>Challenges related to information and national security.</p>
        <p>Ownership related challenges.</p>
        <p>The roles of Kela, THL and STM.</p>
        <p>The importance of the regulated procurement process.</p>
      </sec>
      <sec id="sec-4-4">
        <title>The impact of national regulations to the procurement process of Kanta.</title>
      </sec>
      <sec id="sec-4-5">
        <title>The procurements for Kanta services are not seen as direct procurements.</title>
        <p>Procurement Lack of procurement expertise and understanding of the target.
planning,
vendor, &amp;
contract
management
complexity</p>
      </sec>
      <sec id="sec-4-6">
        <title>Common procedures are needed to maintain information security.</title>
      </sec>
      <sec id="sec-4-7">
        <title>Difficulty to plan procurements in the longer term for Kanta services.</title>
      </sec>
      <sec id="sec-4-8">
        <title>Procurement units want to purchase systems from familiar vendors.</title>
      </sec>
      <sec id="sec-4-9">
        <title>Lack &amp; discrepancy of standards</title>
      </sec>
      <sec id="sec-4-10">
        <title>Data costs</title>
      </sec>
      <sec id="sec-4-11">
        <title>The Gaia-X model addresses information security challenges.</title>
      </sec>
      <sec id="sec-4-12">
        <title>Gaia-X is not directly suitable for handling sensitive data.</title>
      </sec>
      <sec id="sec-4-13">
        <title>The data quality of patient information systems in Finland is disparate.</title>
      </sec>
      <sec id="sec-4-14">
        <title>Obtaining and processing personal data for publication is costly and inconvenient.</title>
      </sec>
      <sec id="sec-4-15">
        <title>Utilising data acquired with public funds would be beneficial.</title>
        <p>The theme of political, legal, and cultural factors underscores the Finnish legislative
framework as a significant obstacle in integrating Kanta services into an external ecosystem.
Specifically, the Client Data Act and the monopoly on the secondary use of healthcare data were
seen as the key factors. The interviewees agreed in unison that the legislation is currently
the main barrier when considering the integration of Kanta services into an external
ecosystem. I2 put this as follows: “It [ecosystem integration] requires changes in the attitudes
and laws in Finland. If we want to use health data, it should be completely possible.”</p>
        <p>The findings illustrate also other projects with similar goals to health data, such as
European Health Data Space (EHDS). With these projects, the European Commission obligates
the EU member states to join an open data ecosystem. It compels them to ensure
compatibility of their health domains with the EHDS and appropriate standards. The interviewee I1
described this: “The European Commission is currently running the EHDS project where these
somehow similar things are defined as in Gaia-X. The EU legislation is also defined here. It is
thus possible that at some point of time, they are applied also to Kanta services.”</p>
        <p>The interviewees argued that the goals of Gaia-X should be reasonable and aligned with
the future information sharing needs. They experienced that the Gaia-X ecosystem
facilitates information exchange in Europe, thus promoting the development of Kanta services.
They mentioned ethical and security issues, and the fact that advancing shared development
targets at the European level is very slow. The interviewee I4 had experiences from working
in international projects. The interviewee stated that “10 years is a really short time”.</p>
        <p>The process orientation of procurement and the division of labour between Kela, THL
and STM were emphasised in every interview. The interviewees said that Kela is making the
final decisions related to technical requirements, technologies, and procurement decisions,
THL is responsible for functional requirements definitions, and STM is responsible for
funding and prioritisation. The roles were thus well-defined - in principle: “STM and THL set the
framework which Kela must follow. But the final decisions are always made by Kela.” (I2)</p>
        <p>The interviewees however pointed out that sometimes such strict division of labour gets
blurry: “THL is responsible for the functional specifications. However, Kela is also making
them sometimes”. (I4)</p>
        <p>The procurement process unifies the procuring. Standardising roles streamlines the
operations as the actors’ potentially conflicting views are harmonised towards the common
target. Also, when procuring various subsystems, the procurement process was regulated
not only by the procurement target itself, but also by the procurement regulations and the
national legislation. The interviewee I5 referred to national legislation: “There are very
detailed requirements that have to be taken into account and it takes resources.”</p>
        <p>The complexity of the procurement planning, and the vendor and contract management
reveal that utilising the open data ecosystem in the requirement specification phase could
help in dealing with the lack of appropriate procurement expertise and resources. An open
data ecosystem helps in defining the IS requirements, streamlines the requirement
specification phase, and mitigates the impact of insufficient competences and understanding of the
procurement target. The interviewee I2 expressed their concerns: “There is no expertise to
define procurement requirements that would reach the best outcome. And on top of that, we
must deal with all sorts of vendor lock-in situations.”</p>
        <p>The difficulty of long-term planning of Kanta services was a shared concern. The
interviewee I4 expressed the funding challenges: “In Kanta services, it is said that we have a far
too short-sighted funding model. For example, you could handle it in a planned way and with
a long-term vision. It should be managed systematically and with a long-term vision.”
Currently the government set funding pace does not match with the purchasing needs. This
complicates budgeting. If an ecosystem guides the Kanta service’s development, it would
also promote and secure long-term funding and procurement planning.</p>
        <p>Concerns related to the lack and discrepancy of standards were evenly distributed. An
open data ecosystem model, such as Gaia-X, aims to create common standards to
information security. These common principles and standards were seen to help in considering
the sensitivity of health data. However, the interviewees brought up that Gaia-X is not
suitable in handling sensitive health data as it should not be published outside the Kanta
ecosystem. Also, the data model was incomparable and unstable as such standards have not
been used in Finland before. I2 stated that: “The bigger problem is with these old-type
[information systems], which the provinces still use. Those are not based on recording structural
data, it’s all in text format.” Thus, the uniformity in processes and standards ultimately
affects the quality and incomparability of the data in Finland.</p>
        <p>The data costs was the least prominent theme. Most occurrences emphasised the costs
and discomfort in anonymising the data before publishing it in the ecosystem. The current
legislation makes it expensive and time consuming to get hold of secondary data.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>
        Our findings suggest that to connect Kanta services to external ecosystems, they need to be
obliged by the level of the European Commission. This aligns with Runeson et al. [37] who
saw the public actor’s involvement in the ecosystem is essential as they facilitate
collaboration and act as a trustable party. Also, the benefits of joining the ecosystem were difficult to
distinguish. This parallels with Gelhaar and Otto [13]: the actors usually acknowledge the
benefits from joining an ecosystem but are hesitant due to the fear of revealing their data to
their competitors. In our case, the concerns pertained to the dissemination of the citizens'
personal data to unidentified entities in the ecosystem, raising apprehensions about
potential data misuse. Due to these fears, the Kanta service specialists were against the
integration to Gaia-X, the external ecosystem. Therefore, the European Commission's role in the
development of the ecosystem becomes central since building trust among the actors and
resolving challenges related to cultural barriers [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] is critical and time consuming.
      </p>
      <p>The benefits from the ecosystem to the public procurement are obtainable only after a
heavy process where the solutions are discovered, and the member states’ legislations
reshaped. This is in line with Runeson et al. [37] who argued that different regions and
national legislations are a challenge when operating in the open data ecosystem. However,
improved communication can help the actors to better understand different views on the
procurement target. This would ultimately lead to better outcomes.</p>
      <p>
        The ecosystem enforces standardisation and stabilises the public actor’s roles and the
processes. For example, when procuring Kanta service ISs, three public sector actors, Kela,
THL and STM, were central. They had unaligned views on the needs and targets; Kela
prioritised technical issues, focusing on existing infrastructure while STM had not scrutinised
such concerns with equal precision in funding allocations. This supports literature on the
challenge of conflicting interests between involved actors [27], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The actors and their
responsibilities were standardised up to some certain degree, although Kela occasionally
participated in the requirement specification, not being their usual role. The literature does not
consider whether changing roles are challenging or beneficial. Alanne et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] however
discovered that when knowledge is distributed among the actor network, it necessitates
cooperative skills to achieve desired outcomes. This notion, with the myriad specialists from
various public sector agencies participating in the Kanta IS procurement, emphasises intensive
collaboration and dependency on the individuals' capabilities to cooperate effectively.
      </p>
      <p>
        Ultimately the actors are purchasing systems with similar specifications. This offers
benefits in terms of increasing knowledge in the procurement units. Our findings suggest that
currently the level of procurement expertise is insufficient in the public sector. The
procuring units do not know how to elicit and specify the needs for the system they are purchasing
(see also [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [27], [30]). The lack of expertise is often seen as a challenge in the requirement
specification. Pre-defined requirements reduce the possibility of human errors, which
result from an insufficient level of expertise or communication between the actors. This is in
line with Runeson et al. [37] that knowledge-sharing is as an enabler for achieving value
from collaboration in the open data ecosystem. Sharing experiences across countries may
increase the awareness of factors leading to successful procurement.
      </p>
      <p>Increased knowledge-sharing may improve procurement planning or limit competition.
This issue arises because the procurement regulations empower the units to impose
restrictions on tender participants [30]. It is possible that selecting the vendors takes place
before the tendering phase [14], leading to dominating vendors in the market [21].</p>
      <p>
        Common requirement specifications are also an answer to the scarcity of resources in
the procurement planning phase. Alanne et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] has defined this as a challenge.
Capitalising the ecosystem in the procurement planning phase, means that the actors do not need to
use their resources on defining the procurement target. On the other hand, the procurement
unit must still carry out the procurement process, i.e. the ecosystem does not directly
eliminate the need for procurement expertise. It reduces the need for expertise and consulting
related to the defining the procurement target.
      </p>
      <p>An open data ecosystem guiding the Kanta service development helps in securing
longterm funding and procurement planning. Currently they are short-sighted. The notion of
goals of longer-term planning and its benefits are in line with previous research where both
the procurement strategy and the long-term planning are seen essential to successful
procurements [32]. In the future this will result in significant changes in Kela’s role as technical
requirements would emerge from the ecosystem. This also poses the questions about
ownership and responsibilities (see also [6], [37]). Our findings support Runeson et al. [37]
observations about the significance of a legal framework to steer the actors in the ecosystem.</p>
      <p>Both the sensitiveness of the health data and the common processes were not
emphasised in the study. This was unexpected. Interviewees experienced the Gaia-X goals
beneficial from the information security perspective, but they could not see the framework being
suitable for storing and processing health data. Since the national legislation significantly
influences the procurement process and the target, the open data ecosystem was not seen
as an alternative. Despite the challenges related to the secondary use of health data, both its
primary and secondary use [11] are to be supported via the Gaia-X ecosystem. With the
Kanta services, the lack of motivation did not promote the secondary use of data. This is
consistent with Vikström et al. [43], where the lack of motivation resulted from the
challenges of the data anonymisation process, affecting also to the value of data.</p>
      <p>When the open data ecosystem sets the public IS procurement targets, the data costs
should be considered at the ecosystem level. The interviewees emphasised the costs and
difficulty in obtaining data as the main challenges when trying to utilise health data for
secondary purposes. As health data contains protected health information [26], it requires
anonymisation prior to publication. This kind of data processing should thus be provided
by the ecosystem. This supports the literature where one of the main elements in the open
data ecosystem is to provide data processing tools [44].</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>In this paper, we presented a case study where the open data ecosystem characteristics are
utilised in public IS procuring. We found that the integration of Kanta into the open data
ecosystem relies on the European Commission's obligation, positioning it as a trustworthy
facilitator within the ecosystem. This integration not only clarifies the roles among the
parties in the IS procurement but also fosters cooperation. Moreover, leveraging the ecosystem
during the requirement specification phase enhances procurement competences and
reduces the resource needs. Lastly, the ecosystem supports long-term planning in terms of
securing funding and enforcing strategic approaches.</p>
      <p>The paper contributes to theory by examining a less-explored scenario – open data
ecosystem characteristics and the public IS procurement. The intersection of these two topics
have not been studied before. We thus contribute to research, in addition to small insights
and notions, by providing a new perspective on literature. In practice, the study introduces
possibilities to utilise ecosystem characteristics in the procurement context.</p>
      <p>Our study has certain limitations. First, although we interviewed main actors, the
number of interviews is very small. Only one interviewee was from Kela, the owner of Kanta
services. In addition, only one interviewee was working in the private sector, so the vendor’s
perspectives are narrow. Additionally, the interviewees’ roles regarding Kanta services
were not considered. Therefore, the effects of the open data ecosystem characteristics on
public IS procuring should be further studied from the vendor perspective, and from the
procurement unit’s point of view to enhance generalisability.
[5] L. DeNardis, J. Morris, S. Baird, L. Garcia, B. Kuerbis, M. L. Mueller, R. Ghosh, N. Tsilas, J.</p>
      <p>S. Wilson, P. Samuelson, Opening Standards: The Global Politics of Interoperability, MIT
Press, Cambridge, London, England, 2011.
[6] W. F. Donker, B. van Loenen, How to assess the success of the open data ecosystem?,</p>
      <p>International journal of digital earth (2017) 284–306.
[7] EU, Directive 2014/24/EU of the European Parliament and of the Council of 26th Feb.</p>
      <p>2014 on public procurement and repealing Directive 2004/18/EC, J. of EU 2014.
[8] F. Forchielli, M. Fusco, E. A. Pessina, W. Domeniconi. W. Ricciardi, Patient Mobility in
the European Union - Study on Legislative Proposals on Patients’ Rights in
Cross-Border Health Care, Policy Department. European Parliament (2008).
[9] GAIA X, Gaia-X Ecosystems. URL: https://gaia-x.eu/who-we-are/vertical-ecosystems/.
[10] GAIA-X, Gaia-X Hub Finland. URL: https://www.gaiax.fi/about-us/.
[11] Gaia-X, Enable the future of healthcare: federated, citizen-centric and insight-driven!,</p>
      <p>Gaia-X, (2022).
[12] A. Gandomi, M. Haider, Beyond the hype: Big data concepts, methods, and analytics,</p>
      <p>International journal of information management (2015) 137 –144.
[13] J. Gelhaar, B. Otto, Challenges in the Emergence of Data Ecosystems, in: Proc. of 23rd.</p>
      <p>PACIS 2020, Dubai, UAE, 2020, pp. 1–14.
[14] R. Ghezzi, T. Mikkonen, Public Procurement of ICT Systems: Stakeholder Views and</p>
      <p>Emerging Tensions, in: Proc. of Intern. Conf. on Software Business, 2024, pp. 61–76.
[15] D. R. Gnyawali, B. Park, Co-opetition between giants: Collaboration with competitors
for technological innovation, Research policy (2011) 650–663.
[16] A. Hein, M. Schreieck, T. Riasanow, D. S. Setzke, M. Wiesche, M. Böhm, H. Krcmar, Digital
platform ecosystems, Electronic markets (2020) 87–98.
[17] A. Holma, J. Vesalainen, A. Söderman, J. Sammalmaa, Service specification in pre-tender
phase of public procurement - A triadic model of meaningful involvement, Journal of
purchasing and supply management (2020) 100580.
[18] L. Hommen, M. Rolfstam, Public procurement and innovation: Towards a taxonomy,</p>
      <p>Journal of public procurement (2008) 17–56.
[19] A. Immonen, E. Ovaska, T. Paaso, Towards certified open data in digital service
ecosystems, Software quality journal (2017)1257–1297.
[20] A. Immonen, M. Palviainen, E. Ovaska, Requirements of an Open Data Based Business</p>
      <p>Ecosystem, IEEE access (2014) 88–103.
[21] L. K. Johannessen, A. Obstfelder, A. T. Lotherington, Scaling of an information system in
a public healthcare market—Infrastructuring from the vendor's perspective,
International journal of medical informatics (2012) e180–e188.
[22] V. Jormanainen, Large-scale implementation and adoption of the Finnish national
Kanta services in 2010–2017: a prospective, longitudinal, indicator-based study,
Finnish Journal of eHealth and eWelfare (2018) 381–395.
[23] V. Jormanainen, K. Parhiala, A. Niemi, M. Erhola, I Keskimäki, M. Kaila, Half of the
Finnish population accessed their own data: Comprehensive access to personal health
information online is a cornerstone of digital revolution in Finnish health and social care,
Finnish Journal of eHealth and eWelfare (2019) 298–310.
[24] Kanta, Kanta Partners. URL: https://www.kanta.fi/en/partners.
[25] T. Kähkönen, A. Alanne, S. Pekkola, K. Smolander, Explaining the challenges in ERP
development networks with triggers, root causes, and consequences, Communications of
the Association for Information Systems (2017) 249–276.
[26] S. M. Meystre, Ó. Ferrández, F. J. Friedlin, B. R. South, S. Shen, M. H. Samore, Text
deidentification for privacy protection: A study of its impact on clinical text information
content, Journal of biomedical informatics (2014)142–150.
[27] C. E. Moe, Research on Public Procurement of Information Systems: The Need for a
Process Approach, Communications of the Association for Information Systems (2014), 78.
[28] C.E. Moe, M. Newman, M. K. Sein, The Public Procurement of Information Systems:
Dialects in Requirements Specification, European J. of IS (2017) 143–163.
[29] C. E. Moe, T. Päivärinta, Challenges in Information Systems Procurement in the Public</p>
      <p>Sector, Electronic journal of e-government (2013), 308.
[30] C. E. Moe, A. C. Risvand, M. K. Sein, Limits of Public Procurement: Information Systems</p>
      <p>Acquisition, in: Proc. of EGOV 2006, Springer, 2006, pp. 281-292.
[31] A. Musa, P. Ðurman, Status of Open Data (Sub)Ecosystem in Croatia: National Open Data</p>
      <p>Portal, in: Proc. of MIPRO ICT and Electronics Convention, Croatia, 2023, 1515–1520.
[32] L. Nyiri, D. Osimo, R. Özcivelek, C. Centeno, M. Cabrera, Public Procurement for the
Promotion of R&amp;D and Innovation in ICT, I. for Prospective Tech. Studies (2007) 1–45.
[33] OECD, OECD Science, Technology and Innovation Outlook 2016, Enhanced Credo ed.,</p>
      <p>OECD Publishing, Paris, France, 2016.
[34] M. I. Oliveira, G. D. F. Barros Lima, B. Farias Lóscio, Investigations into Data Ecosystems:</p>
      <p>A systematic mapping study, Knowledge and information systems (2019) 589–630.
[35] A. Poikola, P. Kola, K. A. Hintikka, Public Data - an introduction to opening information
resources, Ministry of Transport and Communications (2011) 24.
[36] E. Riihimäki, S. Pekkola, Public buyer's concerns influencing the early phases of
information system acquisition, Government information quarterly (2021) 101595.
[37] P. Runeson, T. Olsson, J. Linåker, Open Data Ecosystems — An empirical investigation
into an emerging industry collaboration concept, The JSS (2021) 111088.
[38] T. Saarinen, A. P. Vepsäläinen, Procurement Strategies for Information Systems, Journal
of management information systems (1994) 187–208.
[39] T. Sharon, F. Lucivero, The expansion of the health data ecosystem – Rethinking data
ethics and governance, Big data &amp; society (2019) 205395171985296.
[40] C. Singh, S. Pekkola, Reasons for customizing packaged enterprise systems: a case study
on an enterprise asset management system, JITCAR (2023) 159–186.
[41] J. Stentoft Arlbjørn, P. Vagn Freytag, Public procurement vs private purchasing: Is there
any foundation for comparing and learning across the sectors?, International journal of
public sector management (2012) 203–220.
[42] THL, Sote kokonaisarkkitehtuuri. URL:
https://thl.fi/aiheet/tiedonhallinta-sosiaali-jaterveysalalla/tiedonhallinnan-ohjaus/sote-kokonaisarkkitehtuuri.
[43] A. Vikström, H. Moen, S. R. Moosavi, T. Salakoski, S. Salantera, Secondary use of
electronic health records: Availability aspects in two Nordic countries, Health Information
Management Journal (2019) 144–151.
[44] A. Zuiderwijk, M. Janssen, C. Davis, Innovation with open data: Essential elements of
open data ecosystems, Information Polity (2014) 17–33.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Adner</surname>
          </string-name>
          ,
          <article-title>Ecosystem as Structure: An Actionable Construct for Strategy</article-title>
          ,
          <source>Journal of management</source>
          (
          <year>2017</year>
          )
          <fpage>39</fpage>
          -
          <lpage>58</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Alanne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Hellsten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pekkola</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Saarenpää</surname>
          </string-name>
          ,
          <article-title>Three positives make one negative: public sector IS procurement</article-title>
          ,
          <source>in: Proc. of the Electronic Government 14th. IFIP WG8</source>
          .5 Conference, EGOV 2015, Springer, Thessaloniki, Greece,
          <year>2015</year>
          , pp.
          <fpage>321</fpage>
          -
          <lpage>333</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J.</given-names>
            <surname>Attard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Orlandi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Scerri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          ,
          <article-title>A systematic review of open government data initiatives, Government information quarterly (</article-title>
          <year>2015</year>
          )
          <fpage>399</fpage>
          -
          <lpage>418</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>S. S.</given-names>
            <surname>Dawes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Helbig</surname>
          </string-name>
          , Information Strategies for Open Government:
          <article-title>Challenges and Prospects for Deriving Public Value from Government Transparency</article-title>
          ,
          <source>in: Proc. of 9th. IFIP WG 8.5 Intern</source>
          . Conf.,
          <source>EGOV</source>
          <year>2010</year>
          ,
          <year>2010</year>
          , pp.
          <fpage>50</fpage>
          -
          <lpage>60</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>