×

HL7's new AMS is live!   We are working with Fonteva to resolve log in issues. My Account

Section 1h: Cross-paradigm/Domain Analysis Models
Section 3: Implementation Guides

HL7 Health Services Platform (HSP) Marketplace, Release 2

DESCRIPTION

The Marketplace API specification serves as a building block for orchestrating the exchange of such services and executable knowledge. Products deployed in an enterprise architecture are constituent building blocks in a larger information technology (IT) ecosystem. The deployment and runtime characteristics of each individual building block as well as underlying infrastructure naturally vary across organizations, requiring each service deployment to be further tailored to local IT needs. The process of doing so also varies and is generally considered a normal part of "implementation time" and total cost of ownership (TCO) calculations for incorporating a new service into the enterprise. This lack of infrastructure pre-coordination can result in extremely long IT implementation cycles for any capability to be added to, or changed within, an architecture, especially when underlying infrastructure is completely proprietary to the local institution and/or vendor platform. Burdens of local implementation are confounded by the rise of interest in portable declarative clinical knowledge such as HL7 CDS Knowledge Artifacts and Fast Healthcare Interoperability Resources (FHIR) Clinical Reasoning, as well as libraries of directly executable clinical knowledge such as HL7 Clinical Quality Language (CQL). Any potential reduction to time spent in discovery, evaluation, update, and other changes to enterprise service oriented architectures (SOAs) – thereby increasing the agility of the organization -- is of great value to the HIT community. For organizations willing to enable deployment of these individual knowledge artifacts, direct savings could be substantial.

 

The specification is available online at http://hl7.org/standards/hsp-marketplace/index.html

ALTERNATIVE NAMES

HL7 Health Services Platform (HSP) Marketplace, Release 2 may also go by the following names or acronyms:

"HL7 Health Services Platform (HSP) Marketplace, R2 STU1", "HL7 Health Services Platform (HSP) Marketplace, R1", "HL7 V3: Health Services Platform (HSP) Marketplace, R1", Health Service Marketplace, HSP, Marketplace

TARGETS

  • Standards Development Organizations (SDOs)
  • EHR, PHR Vendors
  • Health Care IT Vendors
  • Clinical Decision Support Systems Vendors

 

BENEFITS

  • Addresses the problem of exchanging backend service implementations in a vendor-neutral manner, which is necessary to exchange executable artifacts interoperably to plug-n-play across SOAs
  • Creates a server-side equivalent of SMART-on-FHIR (SoF), as SoF only concerns client-side app integration and also does not address client-side deployment requirements of web applications, not uncommon in health IT (HIT) enterprise
  • Employs design principles inspired by the business processes that made other computing ecosystems, such as the (all proprietary) Apple, Google, and Amazon app stores successful
  • Allows:
    • HIT orgs to search for new services across *all* participating vendors, and deploy them in a 100% automated fashion into on-prem, cloud, and/or hybrid infrastructure, using 1 or more Marketplace instances in any public/private combination
    • Developers to directly submit new (and update existing) service builds
    • Marketplace operators to curate, review, and publish vendor submissions
    • Compliance validators to automate certification activities
    • All parties to optionally authenticate with existing SSO credentials needed for SoF apps/architectures

IMPLEMENTATIONS/CASE STUDIES

  • Logica Health (formerly HSPC) holds a reference implementation of both the Service specification and optional front end client application.

DEVELOPMENT BACKGROUND

The Marketplace specification has been developed agnostic to the underlying service and content standards with a flexible metadata format. Long term, this should allow independent software vendors and content authors to submit works across competitive distribution channels more easily than proprietary app stores. Likewise, providers and HIT stakeholders should be able to discover and deploy those products more fluidly and consistently than existing disjoint methods.

RELATED DOCUMENTS

HL7 Health Services Platform (HSP) Marketplace, Release 2
HL7 Health Services Platform (HSP) Marketplace, Release 1 (View Brief)

(Download) (1.14 MB)

STU DOCUMENTS

HL7 Health Services Platform (HSP) Marketplace, Release 2 STU 1 The spec is online here.
Expiration Oct 2022

TOPICS

  • Decision Support
  • Regulated Products
  • Security and Privacy

BALLOT TYPES

  • STU

STATUS DATE

2019-10-31

RESPONSIBLE WORK GROUPS

Implementable Technology Specifications

Services Oriented Architecture

PRODUCT TYPES

  • Services
  • Transport(ebxml, cd, mllp)

STAKEHOLDERS

  • Clinical Decision Support Systems Vendors
  • EHR, PHR Vendors
  • Health Care IT Vendors
  • Standards Development Organizations (SDOs)

FAMILY

  • Cross-paradigm

CURRENT STATE

  • Active

REALM

  • Universal