<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="1612" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://socictopen.socict.org/items/show/1612?output=omeka-xml" accessDate="2026-04-18T20:26:07+00:00">
  <fileContainer>
    <file fileId="1612">
      <src>https://socictopen.socict.org/files/original/1d7eed6d4c493e4ef76b361459365d41.pdf</src>
      <authentication>4f7108bae62211ff84f72ef332444e6e</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="15428">
              <text>Healthcare Digitalization and Pay-For-Performance Incentives in Smart Hospital Project Financing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="15429">
              <text>Roberto Moro Visconti, Donato Morea</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="15430">
              <text>This study aims to explore the impact of healthcare digitalization on smart hospital project financing (PF) fostered by pay-for-performance (P4P) incentives. Digital platforms are a technology-enabled business model that facilitates exchanges between interacting agents. They represent a bridging link among disconnected nodes, improving the scalable value of networks. Application to healthcare public–private partnerships (PPPs) is significant due to the consistency of digital platforms with health issues and the complexity of the stakeholder’s interaction. In infrastructural PPPs, public and private players cooperate, usually following PF patterns. This relationship is complemented by digitized supply chains and is increasingly patient-centric. This paper reviews the literature, analyzes some supply chain bottlenecks, addresses solutions concerning the networking effects of platforms to improve PPP interactions, and investigates the cost–benefit analysis of digital health with an empirical case. Whereas diagnostic or infrastructural technology is an expensive investment with long-term payback, leapfrogging digital applications reduce contingent costs. “Digital” savings can be shared by key stakeholders with P4P schemes, incentivizing value co-creation patterns. Efficient sharing may apply network theory to a comprehensive PPP ecosystem where stakeholding nodes are digitally connected. This innovative approach improves stakeholder relationships, which are re-engineered around digital platforms that enhance patient-centered satisfaction and sustainability. Digital technologies are useful even for infectious disease surveillance, like that of the coronavirus pandemic, for supporting massive healthcare intervention, decongesting hospitals, and providing timely big data.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="15431">
              <text>2020</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="15432">
              <text>public–private partnerships, internet of medical things, digital innovation, healthcare sustainable development, patient-centered care, mhealth</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="15433">
              <text>DOI: 10.3390/ijerph17072318</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="15434">
              <text>International Journal of Environmental Research and Public Health</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="15435">
              <text>MDPI AG</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="15436">
              <text>Medicine</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="15437">
              <text>EN</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
