#36 AbstractDeviceComponentState/PhysicalConnector of the virtual terminals / modeled instruments: Definition of mapping to actual ACTIVE OUTPUT TERMINAL

[Martin]

Is there any need to define the mapping of the physical connector to the actual physical plug/channel (how ever it might be called), e.g., in the IfU?

Suggestion:
An HF SURGICAL EQUIPMENT SHALL define the PhysicalConnectorInfo/@Number for each available ACTIVE OUTPUT TERMINAL in the IfU.

possible relations
[opensdc:p11073-10700-pre-ballot:#172]
[#62]
[#63]

[Stefan Schlichting]

From my point of view the PhysicalConnectorInfo/Label would usally be used for allowing an operator to identify the actual physical connector on the device.
The number is more for computing purposes.

[Stephan Klöckner]

So far any Olympus Surgical Generator has a fixed mapping between the physical connector and the channel for the mode definition. There are no interchangebal properties.

[Martin]

Consensus decision: following Stefan's suggestion: No additional requirement towards PhysicalConnectorInfo/@Number.

Depending on requirements towards PhysicalConnectorInfo/Label in the PKPs, we will have to decide whether we have to have a HF-specific requirement or whether the general requirements are suitable.

[Björn Andersen]

See [opensdc:p11073-10700:#2].

[Martin]

PKPs and DevSpec are aligned (in their current states).

See also R5038 for a human labeling requirement.