IHE / IHE/DEV.SDPi

Add detail to SDPi-A Remote Alert Signaling Option

Open
#468 0 comments 0 reactions 1 assignee View on GitHub

@ToddCooper is already working on this.

Since Aug 8, 2025.

Comment Review
Dominant language
Kotlin
Stars
17
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Section Number

1:12.2.3

Priority

  • Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.

This should be scheduled for a release before the end of 2025, noting that it will enable IHE Connectathon testing of the gateway testing.

Issue

With the increasing updates to the SDPi specification related to alerting, including preparation for the 11073-10702 Alert PKP standard in preparation, this "Remote Alert Signaling" actor options for the SDPi-A profile should be detailed. Currently, it only has a placeholder note. Formalizing this option will enable testing of the ACM Gateway capabilities.

Proposed Change

Provide content in alignment with similar actor options, such as the SDPi-P Managed Discovery Option or the Gateway Direction Option. Determine IF an option is needed for the ACM gateway (bidirectional) OR if a similar approach to the SDPi-R DEC gateway may be used, where the actor alone is sufficient and no additional options are needed.

Also determine whether this option includes both ACM (HL7 V2) and FHIR gateway options, in addition to directionality. This would be handled similarly to the directionality settings. If so, the actor model should be updated to include a FHIR Alerting Gateway actor as well.

NOTE: This issue should be resolved AFTER merging of the #454 "Vienna" PR, since that PR addresses foundational actor options, including gateway directionality and how that applies to the SDPi-R DEC gateway directionality option.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.