dx.doi.org/10.1109/ICHI.2015.30

Preview meta tags from the dx.doi.org website.

Linked Hostnames

2

Thumbnail

Search Engine Appearance

Google

https://dx.doi.org/10.1109/ICHI.2015.30

Ecosphere Principles for Medical Application Platforms

A Medical Application Platform (MAP) enables multi-vendor heterogeneous medical devices to be integrated via network infrastructure and provides an application hosting facility that supports a wide range of clinical applications for data fusion, decision support, multi-device safety interlocks, workflow automations, and closed-loop control of actuating medical devices. The assurance of MAP components and systems is distributed across a broad group of stakeholders including medical device manufacturers, platform infrastructure providers, application vendors, third-party certification organizations, and regulatory agencies. Realization of the MAP vision requires that all stakeholders involved in developing, testing, certifying, regulating, purchasing, and using medical devices and applications operate and cooperate within a well-defined ecosphere. This paper presents a high-level overview of the organization of such an ecosphere. We focus on identifying stakeholder roles, responsibilities, artifacts, and interactions, we also indicate the contributions of each of these to the development and safety/security assurance of MAP-based systems.



Bing

Ecosphere Principles for Medical Application Platforms

https://dx.doi.org/10.1109/ICHI.2015.30

A Medical Application Platform (MAP) enables multi-vendor heterogeneous medical devices to be integrated via network infrastructure and provides an application hosting facility that supports a wide range of clinical applications for data fusion, decision support, multi-device safety interlocks, workflow automations, and closed-loop control of actuating medical devices. The assurance of MAP components and systems is distributed across a broad group of stakeholders including medical device manufacturers, platform infrastructure providers, application vendors, third-party certification organizations, and regulatory agencies. Realization of the MAP vision requires that all stakeholders involved in developing, testing, certifying, regulating, purchasing, and using medical devices and applications operate and cooperate within a well-defined ecosphere. This paper presents a high-level overview of the organization of such an ecosphere. We focus on identifying stakeholder roles, responsibilities, artifacts, and interactions, we also indicate the contributions of each of these to the development and safety/security assurance of MAP-based systems.



DuckDuckGo

https://dx.doi.org/10.1109/ICHI.2015.30

Ecosphere Principles for Medical Application Platforms

A Medical Application Platform (MAP) enables multi-vendor heterogeneous medical devices to be integrated via network infrastructure and provides an application hosting facility that supports a wide range of clinical applications for data fusion, decision support, multi-device safety interlocks, workflow automations, and closed-loop control of actuating medical devices. The assurance of MAP components and systems is distributed across a broad group of stakeholders including medical device manufacturers, platform infrastructure providers, application vendors, third-party certification organizations, and regulatory agencies. Realization of the MAP vision requires that all stakeholders involved in developing, testing, certifying, regulating, purchasing, and using medical devices and applications operate and cooperate within a well-defined ecosphere. This paper presents a high-level overview of the organization of such an ecosphere. We focus on identifying stakeholder roles, responsibilities, artifacts, and interactions, we also indicate the contributions of each of these to the development and safety/security assurance of MAP-based systems.

  • General Meta Tags

    12
    • title
      Ecosphere Principles for Medical Application Platforms | IEEE Conference Publication | IEEE Xplore
    • google-site-verification
      qibYCgIKpiVF_VVjPYutgStwKn-0-KBB6Gw4Fc57FZg
    • Description
      A Medical Application Platform (MAP) enables multi-vendor heterogeneous medical devices to be integrated via network infrastructure and provides an application
    • Content-Type
      text/html; charset=utf-8
    • viewport
      width=device-width, initial-scale=1.0
  • Open Graph Meta Tags

    3
    • og:image
      https://ieeexplore.ieee.org/assets/img/ieee_logo_smedia_200X200.png
    • og:title
      Ecosphere Principles for Medical Application Platforms
    • og:description
      A Medical Application Platform (MAP) enables multi-vendor heterogeneous medical devices to be integrated via network infrastructure and provides an application hosting facility that supports a wide range of clinical applications for data fusion, decision support, multi-device safety interlocks, workflow automations, and closed-loop control of actuating medical devices. The assurance of MAP components and systems is distributed across a broad group of stakeholders including medical device manufacturers, platform infrastructure providers, application vendors, third-party certification organizations, and regulatory agencies. Realization of the MAP vision requires that all stakeholders involved in developing, testing, certifying, regulating, purchasing, and using medical devices and applications operate and cooperate within a well-defined ecosphere. This paper presents a high-level overview of the organization of such an ecosphere. We focus on identifying stakeholder roles, responsibilities, artifacts, and interactions, we also indicate the contributions of each of these to the development and safety/security assurance of MAP-based systems.
  • Twitter Meta Tags

    1
    • twitter:card
      summary
  • Link Tags

    9
    • canonical
      https://ieeexplore.ieee.org/document/7349691/
    • icon
      /assets/img/favicon.ico
    • stylesheet
      https://ieeexplore.ieee.org/assets/css/osano-cookie-consent-xplore.css
    • stylesheet
      /assets/css/simplePassMeter.min.css?cv=20250701_00000
    • stylesheet
      /assets/dist/ng-new/styles.css?cv=20250701_00000

Links

17