Static or dynamic alert texts?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
TF-2:B.4.4.7.2
Priority
Martin's list
Issue
For the B.4.4.7.2 Event Identification OBX Segment and Table TF-2:B.4.4.7.2.2-116. OBX Event Identification Mapping - Physiological Alert Event, the alert text can be static and sourced by the AlertConditionDescriptor, or dynamic when the source is changing the alert text (Cause Info). This is missing and also the description what shall be used. This also applies to Table TF-2:B.4.4.7.2.3-117. OBX Event Identification Mapping - Technical Alert Event.
Proposed Change
Decide if we need to use static or dynamic texts and document accordingly.
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 Section TF-2:B.4.4.7.2 and Tables TF-2:B.4.4.7.2.2-116 and TF-2:B.4.4.7.2.3-117. Review how AlertConditionDescriptor and Cause Info are defined and used, then document the selected static or dynamic alert-text behavior and its description for both physiological and technical alert events.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100