Activity for Björn Andersen
-
Björn Andersen created ticket #404
multiple invocation states within one report
-
At least one, non-empty. Not sure if we should put up any rules in addition to those we alredy imposed on the usage of pm:Identification. Subject to review, I would say.
-
B.99 rank is ambiguous
-
Proposal from today's discussion: introduce a coded value in the Revision that contains an "invocation state reason" that is applicable (not only) to failed operations. (We may want to express a reason, e.g., for cancelled operations, too.)
-
Proposal from today's discussion: introduce a coded value in the Revision that contains an "invocation state reason" that is applicable (not only) to failed operations. (We may want to express a reason, e.g., for cancelled operations, too.
-
Closed [#112] as duplicate. Original ticket text: In case an operation fails, there is only a limited amount of information to classify the error in a machine readable way. We should consider adding an extension that adds an optional (mustUnderstand=false) coded value to a failed operation result in order to classify the error for further processing.
-
Error types for operation results
-
Discussion continued in duplicate ticket [#114].
-
Typo in Clause 6.3.1 AlertSignalDescritpor -> AlertSignalDescriptor
-
Require strictly increasing descriptor versions per handle per MDIB sequence
-
Require strictly increasing descriptor versions per handle per MDIB sequence
-
Done in PR#329.
-
while ActivationState is not On, historic values may be provided
-
R5003 out of context
-
Removal of R0047 remains to be done, see overhaul document.
-
while ActivationState is not On, historic values may be provided
-
Done in PR#326.
-
Actually... this is solved in the new version of R0029, see PR#142.
-
Actually... this is solved in the new version of R0029, see PR#142.
-
R5047: Missing statement about localization service availability
-
Done in PR#262.
-
See [#401].
-
Prohibit any other state for AlertConditionState/@ActivationState = Off than Presence = false
-
while ActivationState is not On, historic values may be provided
-
while ActivationState is not On, historic values may be provided
-
while ActivationState is not On, historic values may be provided
-
Clarify scope of clause 6
-
No further action needed at this point.
-
Commas inside quotes change semantics
-
No further action needed at this point.
-
Prohibit any other state for AlertConditionState/@ActivationState = Off than Presence = false
-
To be discussed again in APKP WG. No urgent need for this rule. Plus: a provider may want to keep the last observed state, which may be presence=true, upon deactivation of condition monitoring.
-
Require strictly increasing descriptor versions per handle per MDIB sequence
-
Time-related attributes for metrics that are not measurements
-
Clarify definition of @DeterminationTime
-
DR1785: where to document the rationale?
-
Clarify ACK for visual alert signals
-
Wording for implied version numbers
-
Done in PR#322.
-
R0103: requirement text is misleading; the requirement does not add value
-
R0057: Delete or rephrase
-
ClockState@DateAndTime handling
-
B.196 CodedValue/Translation/@CodingSystem should get implied value
-
Wording for implied version numbers
-
Some changes had been lost in a merge. Thus re-operning this issue.
-
Note for allowed values of metrics
-
Fix capitalized requirement keywords where capitalization is pointless
-
R5001: Remove requirement, make it a definition
-
order of change/event occurrence
-
order of change/event occurrence
-
Define MdibVersion as the order of (real-world) events that are represented by the respective changes of the MDIB. (Sounds awful, needs better wording!)
-
C.77 OperationInvokedReportPart and multi-state updates
-
Split ticket! Corrigendum: Disallow more than one proposed context state. Revision: Revise the entire mechanism.
-
C.156 TransactionId
-
Done in PR#293.
-
Done in PR#293.
-
Time-related attributes for metrics that are not measurements
-
Clarify definition of @DeterminationTime
-
B.440 MeasurementValidity
-
remodelling of MetricCategory
-
B.141 BatteryState: requirements split & override of ActivationState
-
Clarify order of Samples within RealTimeSampleArrayMetricState
-
B.70 AbstractOperationDescriptor/@OperationTarget description contradiction
-
B.6 Operation target scope constraints
-
B.70 & B.6 Conflicting requirement texts
-
B.440 MeasurementValidity
-
Consider not touching Validity during the Corrigenda any further than in above-mentioned PR. Same for Qi. Remember the eighth commandment (of BICEPS): Thou shalt not bear false witness.
-
Proposal for Clc: time when value has been derived from calculation. Set: time when the setting took (full) effect. Preset: time when preset has been adjusted Rcmm: time when recommendation has been determined
-
Time-related attributes for metrics that are not measurements
-
Proposal for LifeTimePeriod: only reword to "determined value". Often not applicable to settings and presets. (cf. ActivationDuration)
-
Time-related attributes for metrics that are not measurements
-
Proposal for StartTime (StopTime and MaxMeasurementTime analogue): Clc: the point in time when the device starts to calculate Set: the point in time when the device begins to apply the setting, esp. for settings that cannot be applied instantly, e.g. the height of an operating table takes some seconds to adjust Preset: often not applicable. If present, point in time when the preset value starts to be determined Rcmm: point in time when the recommended value starts to be determined (similar to Msrmt...
-
MetricAvailability of settings and presets
-
Solved in MPKP:TR0136 and note.
-
Clarify definition of @DeterminationTime
-
Time-related attributes for metrics that are not measurements
-
C.111 pm:LocalizedTextType does not exist
-
B.365 ScoState/OperationGroup/Type - misspelling
-
MetricAvailability of settings and presets
-
Time-related attributes for metrics that are not measurements
-
Clarify definition of @DeterminationTime
-
B.440 MeasurementValidity
-
R5001: Remove requirement, make it a definition
-
B.141 BatteryState: requirements split & override of ActivationState
-
Done in PR#282.
-
Note for allowed values of metrics
-
Done in PR#280. @martinuro: Please review and approve!
-
Clarify order of Samples within RealTimeSampleArrayMetricState
-
Done in PR#278.
-
Done in PR#276.
-
C.111 pm:LocalizedTextType does not exist
-
Done in PR#276.
-
B.365 ScoState/OperationGroup/Type - misspelling
-
B.189 & B.190: ISO/IEC 11073-10101
-
Instance Identifier comparison fix
-
B.124 AlertSystemState/@LastSelfCheck rephrase
-
B.120 SelfCheckPeriod is not solely sufficient for checking the alert system operational status
-
Clarify documentation of ClinicalInfo
-
B.446 QualityIndicator with regard to the validity level
-
B.365 ScoState/OperationGroup/Type - misspelling
1 >