×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 
Return to Search

Health Services Platform Marketplace - release 2

Return to Search

Basics

Health Services Platform Marketplace - release 2

1436
Ballot - STU


V3 Services-Web Services (OMG)

Create New Standard

Details

This project will provide a vendor-agnostic Health Services Platform (HSP) Marketplace specification for publication, curation, discovery, and distribution of interoperable service implementations. This specification will be completely agnostic to programming language/frameworks, database, and I/O technologies, as well as account for SMART-on-FHIR client applications that require on-site deployment. Existing work by HSPC and ASU will be brought in to HL7 to formalize and steward the specification itself. Deliverables include:

1. REST JSON API (Representation State Transfer JavaScript Object Notation Application Programming Interface) and platform-independent model (PIM) of specified objects, fully compatible with the OAuth 2-based nature of SMART-on-FHIR.

2. Exemplar HSPC reference implementation of the Marketplace Service and Web UI/Client. The reference implementation will be supporting material, not directly part of the balloted standard.

3. Reference database schema for relational database management systems.


The Health Services Marketplace 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. In broad strokes, it is the 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. The design principles are inspired by the business processes that made other computing ecosystems, such as the (all proprietary) Apple, Google, and Amazon app stores successful. This 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.



Informative Ballot of the interface specification - Target: 2019 Jan STU Ballot of the interface specification - Target: 2019 Sept Normative Ballot of the interface specification- Target: 2021 May Project End Date (all objectives have been met) - Target: 2021 Sept


Supporting project documents, deliverables, ballot reconciliation work and other project information will be kept at the SOA confluence page: https://confluence.hl7.org/display/SOA/Services+Oriented+Architecture

How much content for this project is already developed? 60% Was the content externally developed (Y/N)? Yes, HSPC and Arizona State University (ASU)

None

Standards Development Organizations (SDOs), Other (specify in Misc. Notes below),N/A,EHR, PHR; Health Care IT; Clinical Decision Support Systems

1) Health Services Platform Consortium 2) Telstra AU

Need for common, interoperable EHR marketplaces standards and lack of service exchange standards. Related to external Open Container Initiative for service packaging. TODO explain Open Container Initiative for service packaging compatibility in Linux, Windows, and macOS.

Health Services Platform Marketplace HSP Marketplace, HSPM, Service Store, Service Exchange, Service Registry, App Store

No HL7 lineage. Project was started at HSPC and needs to be stewarded by an SDO.


N/A

No

2024 June: From analysis by Vince McCauley: It was discovered that the STU publication request for Health Services Platform (HSP) Marketplace Release 2 STU 2 had fallen through the cracks; when found, it was sent to TSC. PMO attached the Joint Project Plan (JPP) in Project Insight. The JPP indicates approval for Joint Copyright, hence no 'Joint Copyright Letter of Approval' is needed. 2019 October: TSC approved STU Publication Request for HL7 Health Services Platform (HSP) Marketplace Release 2 STU 2019 June: TSC approved Informative Publication Request for HL7 Version 3 Standard: Health Services Platform (HSP) Marketplace, Release 1 2019 June: CDS voted to participate as an Interested Party. External Drivers: Need for common, interoperable EHR marketplaces standards and lack of service exchange standards. Related to external Open Container Initiative for service packaging. TODO explain Open Container Initiative for service packaging compatibility in Linux, Windows, and macOS.
Organization & Realm

Universal

People

Preston Lee, Vincent McCauley



Orchestration, Services, and Architecture Work Group

Implementable Technology Specifications Work Group

Status & Dates

Active

STU - Test Period/Accepting Comments

03/30/2020

09/01/2026

2026 Sept WGM/Ballot

09/01/2026

2026 Sept WGM/Ballot

2022 Jan Ballot Cycle Info: STU Ballot results: Met basic vote requirements. 3 Negatives has completed reconciliation and a publication request was submitted. Document Name: HL7 Health Services Platform (HSP) Marketplace, Release 2 STU 1 (See Jira Ballot Dashboard) 2019 Sept Ballot Cycle Info: STU Ballot results: Did not meet basic vote requirements. 13 Negatives to reconcile Document Name: HL7 Health Services Platform (HSP) Marketplace, Release 2 STU 1 2019 Jan Ballot Cycle Info: INFORMATIVE Ballot results: Did not meet basic vote requirements. 26 Negatives to reconcile Document Name: HL7 Version 3 Standard: Health Services Platform (HSP) Marketplace, Release 1
Approvals

11/26/2018


Not Needed


Not Needed




System Info



View Ballot Items (with NIBs)




Return to Search