×

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

Section 1h: Cross-paradigm/Domain Analysis Models
Section 2: Clinical and Administrative Domains
Section 3: Implementation Guides
Section 4: Rules and References

HL7-IHE Gemini Standard: Service-oriented Device Point-of-care Interoperability (SDPi) Technical Framework, Edition 1

DESCRIPTION

Standard for device-to-device plug-and-trust interoperability optimized for acute care medical devices (e.g., infusion pumps, ventilators, physiological monitors, etc.) utilizing the ISO/IEEE 11073 Service-oriented Device Communication (SDC) family of standards. This is a joint HL7-IHE Gemini specification that supports device plug-and-trust connectivity, medical data reporting, medical alerting, and device-external control, as well as gateway specifications from SDC to HL7 FHIR and to IHE V2-based device messaging profiles for the IHE Device-Enterprise Communication (DEC) profile, and the Alert Communication Management (ACM) profile.

ALTERNATIVE NAMES

HL7-IHE Gemini Standard: Service-oriented Device Point-of-care Interoperability (SDPi) Technical Framework, Edition 1 may also go by the following names or acronyms:

"HL7/IHE SDPi, Edition 1",,SDPi

BENEFITS

  • Enables standards-based high granularity, high frequency, device data integration without the need for adaptors and translators.
  • Supports seamless integration from the device interface to enterprise applications.
  • Enables use cases that require an ecosystem of interoperable plug-and-trust devices, such as Silent ICU, where alarms can be delegated to systems away from the patient's bedside, reducing the noise in the care environment.
  • Improves overall safety, technology effectiveness, security, quality and efficiency related to the use of health device technologies.
  • Supports implementation of next generation clinical applications, including control algorithms, decision support, analytics, and other intelligent technologies that require high quality and high fidelity patient data.

IMPLEMENTATIONS/CASE STUDIES

  • Medical Device Vendors (e.g., B.Braun, Dräger, Philips), consortia like OR.NET, university research labs, hospitals, and other organizations such as JHU/APL in the U.S., have conducted many research, prototyping and public demonstration projects
  • Product demonstrations at public events such as the HIMSS annual conference, DMEA (in Berlin), and recently the European Society for Intensive Care Medicine (ESICM) in Munich, Germany.

DEVELOPMENT BACKGROUND

This SDPi device interoperability specification grows out of 20+ years of close collaboration between device communication standards organizations in IEEE, ISO and CEN. The HL7 and IHE devices expert groups have worked have also worked closely during this same time, and in 2020 started the joint HL7-IHE Gemini device interoperability program that has resulted in the creation of this specification. Therefore, this specification builds on medical device communication standards that have been developed over the last 40 years, ensuring continuity with existing device integration solutions, as well as enabling next generation use cases that have been an aspirational vision for decades, but are only now becoming a reality with this specification.

RELATED DOCUMENTS

HL7-IHE Gemini Standard: Service-oriented Device Point-of-care Interoperability (SDPi) Technical Framework, Edition 1

STU DOCUMENTS

HL7-IHE Gemini Standard: Service-oriented Device Point-of-care Interoperability (SDPi) Technical Framework, Edition 1 (Submit Feedback on STU)

(Download)

TOPICS

  • Cardiology
  • Care Provision
  • Community-Based Health
  • Decision Support
  • Emergency Management
  • Healthcare Devices
  • Laboratory
  • Materials Management
  • Medical Records
  • Patient Administration
  • Patient Care
  • Public Health
  • Regulated Products
  • Security and Privacy

BALLOT TYPES

  • STU

STATUS DATE

2025-12-10

RESPONSIBLE WORK GROUP

Devices

PRODUCT TYPES

  • Clinical Information Model
  • Document
  • Domain Analysis Model
  • Domain Content Model
  • Encoding Syntax
  • Functional Model
  • Functional Profile
  • Implementable Transport Specification
  • Implementation Guide
  • Services
  • Standard Reference Materials
  • Structures
  • Transport(ebxml, cd, mllp)
  • XML Schemas

STAKEHOLDERS

  • Clinical and Public Health Laboratories
  • Clinical Decision Support Systems Vendors
  • EHR, PHR Vendors
  • Emergency Services Providers
  • Equipment Vendors
  • Health Care IT Vendors
  • Healthcare Institutions
  • HIS Vendors
  • Lab Vendors
  • Local and State Departments of Health
  • Payors
  • Regulatory Agency
  • Standards Development Organizations (SDOs)

FAMILY

  • Cross-paradigm

CURRENT STATE

  • Active

REALM

  • Universal