Skip to content

SDPi Editorial Planning and Versions

Jump to bottom
Todd "AFC!" Cooper edited this page Apr 14, 2023 · 2 revisions

SDPi Editorial Planning & Versions

SDPi Development Cycles & Versioning

This article addresses specific details about SDPi specification versions, both planned and historic. To get a more general perspective on the development process and co-working within the collaboration community, see the related article: Gemini Program Coordination & Co-Working Spaces.

What’s in a Version?

As seen in the release detail sections below (e.g., SDPi Version: 1.0 (Detail) ), each release integrates content from different sources:

  • Use Case Features / Capabilities (e.g., Smart Alarming)

  • Technical Capabilities (e.g., alert delegation)

  • Topics of Interest that have been resolved and are ready for implementation

  • Ecosystem Pathway Requirements (e.g., SES application)

  • RI+MC+RR (metadata) support

  • Corrections, Fixes …​

Major, Minor & Fix Versioning

Release versions have a major, a minor and a fix version number (e.g., 1.0.0), which is allocated as follows:

Major - Use Case + Technical Capabilities that represent significant additions to the SDPi ecosystem

Minor - Corrections / fixes, Topics of Interest integration, incremental scenario / technical capability support

Fix - ONLY Editorial corrections / fixes, providing for quick updates that cannot wait until the next Minor or Major release

Note
 Backwards Compatibility — For Minor & Fix revisions, backwards ("non-breaking") compatibility is ensured. For Major revisions, breaking changes may be introduced, but only if absolutely necessary.

As stated in the following section, major versions will generally be released annually. Of course, Major versions also integrate those enhancements that might otherwise be in the next Minor update release.

Development Cycles

Once SDPi 1.0 is published (see target "Date" in the SDPi Version Planning & History table below), development of subsequent versions is intended for a quarterly release cycle, as follows:

  1. (2 Months) Planning for the next release

  2. (3 Months) Development of content for next release

  3. (1 Month) IHE-HL7 Internal WG Review

  4. (1 Month) Public Comment & Resolution (Required for Major releases)

Completion of step (2) above will target the end of each calendar quarter.

Caution
 Alternatively, releases may be advanced in a 3-per-year cadence and aligned with the HL7 balloting cycle as well.

Although step (1) indicated that next release planning will happen on a quarterly basis, major version planning (e.g., 2.0, 3.0, 4.0, etc.) will generally occur on an annual basis, updating a multi-year roadmap. For more information, contact Todd Cooper / Program Manager.

SDPi Version Plan / History

The following SDPi Version Planning & History table provides SDPi specification version planning and history information:

Note
 Project details may be provided in the SDPi’s Smartsheet tool.
Table 1. SDPi Version Planning & History
Version Date Projects / Milestones Scope Comment

1.0

2023.04.07

[SDPi 1.0 Baseline Document (Ready for Review)]

Use Case Capabilities:

  • Remote viewing of patient data & alert events

  • Bedside / Central Station / Outside ICU or Isolation room

  • Basic SDPi-P, SDPi-R & SDPi-A

  • Basic V2 Gateways for DEC & ACM

See SDPi Version: 1.0 (Detail) for more information.

End Q1 2023 (31 March)

1.1

2023.06.30

Milestones: SDPi 1.1 Review

SDPi 1.1 Publication

Issues deferred from 1.0, and

  • NTP Support

  • Discovery Proxy

See SDPi Version: 1.1 (Detail) for more information.

Core content will be completed end Q2 2023 (June 30);

Some items are dependent on standard publication by IEEE

1.2

2023.09.30

Milestones: SDPi 1.2 Review

SDPi 1.2 Publication

Production Ready

Adding support for:

  • Context Management

  • Aggregators

  • Localization Service

  • Gateway ADT Service

See SDPi Version: 1.2 (Detail) for more information.

Core content will be completed end Q3 2023

Some items are pending completion of the July 2023 SDPi Workshop

2.0

2024.06.30

Alarm Management

Comprehensive support for device alerting, including:

  • Alert Delegation

  • Alert Delegation Chains & Multi-DAS/DIS Environments

  • Smart Alarm Systems

See SDPi Version: 2.0 (Detail) for more information.

Core content will be completed end Q2 2023;

Completion of the IEEE 11073-10702 Alert PKP standard is a prerequisite.

3.0

2025.06.30

Device Control

Add comprehensive support for device control.

See SDPi Version: 3.0 (Detail) for more information.

Core content will be completed end Q2 2023

Completion of the IEEE 11073-10703 Control PKP standard is a prerequisite.

SDPi Version: 1.0 (Detail)

Use Cases:

  • Remote View of patient data and alert events

    • At the bed side

      • Device data are displayed on other devices assigned to the same patient e.g. ventilation parameters, waves and alerts are displayed along with other vital signs parameter and alerts at the patient monitor.

    • Outside the ICU/isolation room

      • Device data are displayed at a hallway display in order to provide consolidated overview of the patient’s condition outside of the patient room.

    • At the central station

      • Device data are displayed at a central station providing a consolidated overview of the health condition of multiple patients.

  • PoC Device Data export to hospital information systems (e.g. EMR, alarm integrator, etc.)

    • Data export according IHE DEC und ACM Profiles

    • DIS (w/o Quiet / Silent ICU) with IHE ACM Profile

    • For SDPi 1.0, only outgoing gateway actors will be supported (SOMDS to Enterprise) and not incoming (e.g., patient demographics query)


Technical Scope:

  • SDPi-P (Plug-and-trust Interoperability)

    • SDC Discovery

    • Time Synchronisation

      • Options of synchronizing the real-time clock of the device with the local wall clock time using a NTP time server

    • Connection and Data Exchange Handling and Timing Requirements

      • Connection Time delay (ToI topic)

      • Initial MDIB request, MDIB versioning, and general description of MDIB compression with http

      • Event report subscriptions (timeouts, renewal requirements, etc.) – informal description of expectations; renewal already part of DPWS

      • Event reports (guidelines which kind of reports to be used, missing report detection, timeouts, etc.) – general description of background and context

      • Certificate handling– encryption mandatory, for 1.0 leave open how certificates are distributed

    • System Context Usage

      • Pairing of devices and systems based on one or more system contexts (e.g. ensemble context, patient context, location context, etc.) by leveraging the principles as laid out in BPKP

  • SDPi-R (medical data Reporting)

    • Vital signs parameter and wave data reporting (time alignment not part of 1.0)

    • Mapping from SDC to IHE DEC for data export to EMR - Semantic and syntax mapping

  • SDPi-A (medical device Alerting)

    • Alert event reporting in the DIS context (no alarm delegation, just display)

    • Mapping from SDC to IHE ACM for alert event export to alarm manager - Semantic and syntax mapping

  • Topics of Interest


SDPi Version: 1.1 (Detail)

Completion of issues deferred from the SDPi 1.0 release(s).

Additional capabilities to be added include:

  • NTP support

  • Discovery Proxy

See SDPi 1.1 Review Issues for a complete list.

Consult also the Topics of Interest table for items marked as 1.1 or later.

Additionally, two of the ISO/IEEE 11073-1070x Participant Key Purposes standards should be published by the end of 2022 and may be applied, namely:

  • 11073-10700 Base PKP (applies primarily to the SDPi-P profile) - Pending publication of the IEEE standard

  • 11073-10701 Metric PKP (applies primarily to the SDPi-R profile) - Pending publication of the IEEE standard

  • TF-1 Appendix B Standards Conformance support information (e.g., IEEE 11073 ICS Tables)


SDPi Version: 1.2 (Detail)

Focus is the addition of any specifications required to ensure enabling Production Ready product implementations.

This includes adding support for:

  • Context Management (including LocationContext, EnsembleContext, PatientContext)

  • Aggregator systems (including infusion pump aggregators and multi-component physiological monitors)

  • Localization Service

  • Gateway ADT Service (providing SOMDS CONSUMER actors with access to remote patient demographics information)

Completion of issues deferred from the SDPi 1.1 release(s).

See SDPi 1.2 Review Issues for a complete list.

Consult also the Topics of Interest table for items marked as 1.2 or later.

SDPi Version: 2.0 (Detail)

Focus: Alarm Management

Comprehensive support for device alerting, including:

  • Alert Delegation

  • Alert Delegation Chains & Multi-DAS/DIS Environments

  • Smart Alarm Systems

The key use case based capabilities to be added in SDPi 2.0 will be determined after completion of the SDPi 1.0 supplement. In general, though, the following capabilities are under consideration:

  • Silent ICU & Smart Alarming Support (including alert delegation & full DAS & cDAS)

  • Device-specific Use Cases (e.g., infusion pumps, ventilators, physiologic monitors, anesthesia workstations, etc.)

  • Basic External Control (SDPi-xC)

  • FHIR Gateway (for metrics)

  • Bidirectional Gateways (for bringing information into a SOMDS) These use cases and technical features will be evaluated by the Gemini SES+MDI program management "Roadmap" team. For more information, contact Todd Cooper / Program Manager.

Note: This release is highly dependent on the completion and publication of the IEEE 11073-10702 Alert PKP standard.

SDPi Version: 3.0 (Detail)

Focus: External Control

Support for device external control, including use cases for:

  • Infusion Pump Dose Rate Tritation

  • Closed-loop control (in an ensemble)

Note: This release is highly dependent on the completion and publication of the IEEE 11073-10703 Control PKP standard.

SDPi Editorial Team

Development of any significant specification requires the active and focused involvement of a team of experts, and this is the case for SDPi! In table below, the editorial roles for this project are described, along with the groups and individuals who are involved in each editorial function. For a more detailed description of how these teams and communities coordinate their work within the Gemini SES+MDI program, see the related article: Gemini Program Coordination & Co-Working Spaces.


Note
 The individuals and focus area assignments in the following SDPi Editorial Roles & Team table are dynamic and indicate those currently working on the SDPi specification version. For current (in the moment!) activities, including individual’s assignments, see the detail in the DEV.SDPi github projects, as described in the article: Managing SDPi Development Using GitHub Projects.

info (emails) are provided for specific individuals; however, for general questions please contact either Todd Cooper / Gemini SES+MDI program manager, or John Rhoads / IHE DEV Technical Program Manager.


Table 2. SDPi Editorial Roles & Team
Role Description Team Focus Area

Editor

Creates AsciiDoc content for the specification and wiki articles

Todd Cooper

SDPi TF (Overall + TF-0, TF-1 & TF-3)

David Gregorczyk

SDPi TF-2

Ken Fuchs

SDPi TF-1 Appendix C: Use Cases

Peter Kranich

SDPi Alerting; V2 Gateways

Javier Espina

SDPi (general)

John Rhoads

IHE DEV Technical Program Manager

Kathrin Pia Reich

SDPi Transaction Support

Content Contributors

Develop content that is edited into the SDPi TF; either in AsciiDoc, MS Word or other

Editors +

Tobias Klotz

General

Martin Kasparick

Alerting, Device Specializations

Björn Andersen

General

Subject Matter Experts (SME)

Resolve Topics of Interest; Detailed content review; Specific subtasks

IHE-HL7 SDPi Community Participants

Reviewers

General review of content

IHE-HL7 DEV WGs; OR.NET; Health Informatics (public) community



Gemini SES+MDI Program

Gemini SES+MDI Program articles …​

Clone this wiki locally