Peter Kranich

So, there are the following situations with @ext:MustUnderstand and the consumer does not understand the extension: Situation | Parent | Child | Rule 1.) | false | false | consumer can use parent and child element 2.) | false | true | consumer can use parent but must ignore child element 3.) | true | false | consumer must ignore the parent and child element 4.) | true | true | consumer must ignore the parent and child element (same as 3.) If this is the correct interpretation of TR1342, I'm fine...

That clarifies it for me. Thanks!

So, there are the following situations with @ext:MustUnderstand and the consumer does not understand the extension: Situation Parent Child Rule 1.) false false consumer can use parent and child element 2.) false true consumer can use parent but must ignore child element 3.) true false consumer must ignore the parent and child element 4.) true true consumer must ignore the parent and child element (same as 3.) If this is the correct interpretation of TR1342, I'm fine with it.

Thanks for the change - that makes the statement much clearer.

Not clear what the individual purposes in the list mean

This is not what I meant with "Describe response from provider.". What I meant is shall the provider just reject the connection, or shall it allow the connection, return a meaningful error code and then close the connection.

Note that the pysiological range has no direct relationship to the alert range but can be used as a guideline for it. In my opinion, the reason for the physiological range is mainly for display purposes (e.g. inital scaling of a trend diagram). Since the physiological range is dependent on the patient category, I could imagine 2 options: 1.) the physiological range will automatically change when the patient category is changed at the device 2.) each metric has a list of physiological ranges - one...

IEEE 11073-10101 not referenced