Standalone SDPi - Supplement - 2.0
Open
Comment Review
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
SDPi Supplement Specification
Priority
- Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.
Issue
After the initial separation of SDPi into standard and supplement specifications (1.0), additional work is needed to update each so that they are truly "standalone" and are fit for purpose. In the case of the SDPi supplement, that includes understanding how much detail to include in the supplement that will facilitate integration with the IHE DEV TF once the content becomes normative as Final Text. This issue captures the next level of considerations to advance the specifications maturity.
Proposed Change
The following issues and tasks for the SDPi Supplement should be addressed:
- Add any HL7 SEP 2026 Ballot Comments for the "standalone" supplement (info) document
- TF-1A - Is that included in the supplement, and if so, what level of detail and where
- TF-2 - what level of transaction information should be included in the supplement, if any?
- To support IHE Gazelle testing, what content is required to be IN the IHE DEV TF (via this supplement) vs. in the standard and integrated directly from there?
- TF-2x - which appendices should be included and to what level of detail? Only place holders like profiles in Volume 1, or more detail?
- Add support for TF-2 Discovery Proxy and History Service ? Simply summary?
- Add TF-3:8.7 Device specialization content modules for BICEPS extensions?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.