Recent changes to ieee11073-10207

#413 SafetyClassification responsibility

Lukas Deichmann — Wed, 01 Apr 2026 08:21:38 -0000

Description has changed:

Diff:

--- old
+++ new
@@ -1,3 +1,3 @@
 We need to clarify what kind of responsibility and for whom is derived from SafetyClassification. For metrics and similar data, it is mostly a task for the provider, derived from the intended use of the data etc.

-For operations, it is the other way round, where the safety classification is &#34;intended&#34; to require the consumer to behave in a manner a certain manner to &#34;fulfill&#34; the specified SafetyClassification. The provider is eseentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer
+For operations, it is the other way round, where the safety classification is &#34;intended&#34; to require the consumer to behave in a manner a certain manner to &#34;fulfill&#34; the specified SafetyClassification. The provider is essentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer

SafetyClassification responsibility

Lukas Deichmann — Wed, 01 Apr 2026 08:21:27 -0000

We need to clarify what kind of responsibility and for whom is derived from SafetyClassification. For metrics and similar data, it is mostly a task for the provider, derived from the intended use of the data etc.

For operations, it is the other way round, where the safety classification is "intended" to require the consumer to behave in a manner a certain manner to "fulfill" the specified SafetyClassification. The provider is eseentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer

SafetyClassification responsibility

Lukas Deichmann — Wed, 01 Apr 2026 08:21:27 -0000

Ticket 413 has been modified: SafetyClassification responsibility
Edited By: Lukas Deichmann (ldeichmann)
Description updated:
--- description-old

+++ description-new

@@ -1,3 +1,3 @@

-For operations, it is the other way round, where the safety classification is "intended" to require the consumer to behave in a manner a certain manner to "fulfill" the specified SafetyClassification. The provider is eseentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer
+For operations, it is the other way round, where the safety classification is "intended" to require the consumer to behave in a manner a certain manner to "fulfill" the specified SafetyClassification. The provider is essentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer

#412 Table 14 Corrigendum incorrect names

Björn Andersen — Mon, 02 Mar 2026 09:56:57 -0000

labels: Table 14 --> Table 14, not breaking backward compatibility
status: unread --> accepted
assigned_to: Lukas Deichmann
Milestone: untriaged --> Revision

#336 B.324 revise/remove PatientType

Björn Andersen — Mon, 02 Mar 2026 09:51:08 -0000

assigned_to: Björn Andersen

#410 How to provide a display range

Björn Andersen — Mon, 02 Mar 2026 09:49:39 -0000

labels: --> not breaking backward compatibility
status: unread --> open
assigned_to: Björn Andersen
Milestone: untriaged --> Revision

#409 Supposed inconsistancy between SystemErrorReport/ReportPart/ErrorInfo and OperationInvokedReport/ReportPart/InfocationInfo/InvocationErrorMessage

Björn Andersen — Mon, 02 Mar 2026 09:46:55 -0000

labels: --> C.111, SystemErrorReport, breaking CONSUMER backward compatibility
status: unread --> open
assigned_to: Lukas Deichmann
Milestone: untriaged --> Revision

#404 multiple invocation states within one report

Björn Andersen — Mon, 02 Mar 2026 09:33:05 -0000

labels: InvocationState --> InvocationState, breaking PROVIDER backward compatibility
assigned_to: David

#114 Add extension that allows to classify errors

Björn Andersen — Mon, 02 Mar 2026 09:31:31 -0000

labels: Extension, OperationInvokedReport --> Extension, OperationInvokedReport, not breaking backward compatibility

#115 C.77 OperationInvokedReportPart and multi-state updates

Björn Andersen — Mon, 02 Mar 2026 09:29:56 -0000

labels: C.77, C.96 --> C.77, C.96, breaking CONSUMER backward compatibility