Standalone SDPi - Standard - 2.0
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
SDPi Standard document
Priority
- High: Important issue where there is major issue to be resolved. Requires discussion and debate.
Issue
Now that the primary (100+ files) merge of Standalone SDPi (SS) has been accomplished, additional tasks remain to add content and normalize it to standalone standard language.
Proposed Change
SDPi Standalone 2.0 tasks include:
- Add any HL7 SEP 2026 Ballot Comments for the Standard Document OR "standalone" standard (info) document
- Forward section needs to be fleshed out with new content + standard-ese (non-supplement) language
- Refactor Volume 3 content to be more standalone, pulling in content as needed from the IHE DEV TF-3 (see note at start of TF-3 including REVIEWER QUESTIONS)
- Refactor section labeling per conventions (e.g., #vol1_clause_ #vol1_appendix_, etc.) for content moved to non-volume sections
- Conformance-related Content reviewed and updated for clarity and consistence and completeness throughout the document
- Integrate Standard Forward Declarations into the new Terms, Definitions & Acronyms section, either as the current table or integrated to an existing table
- Refactor Joint IHE-HL7 Gemini SES+MDI Project Development into the Forward content
- Refactor RI+MC+RR language (as part of the new PnT Interop Requirements Management clause + maybe in the Foreword section too (proposed: Using ASCIIDoc for regulatory ready requirement and model specification)
- Review MBSE and related content for updating or elimination in the Requirements Management section
- Consider establishing a shared Referenced Standards section file between the STANDARD and SUPPLEMENT
- ...
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.
Research direction
Start with the Standalone SDPi Standard document and review open pull request #579 to understand the work already underway. Use the listed sections and checklist as the scope, including the Forward, Volume 3, conformance content, terminology, and requirements management. Done means the standalone content is added, normalized, reviewed, and all applicable tasks are resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100