Unique Identification of SaMD Instances

Migrated for the discontinued Topics of Interest page:

The UDI of software-only devices does not have to be unique per instance but per version. For deployments in which it is necessary to identify multiple instances of the same software, the SYSTEM OWNER and/or ADMINISTRATOR must be assigned the responsibility to deal with this issue.

The "Glue" SDC core standard (IEEE 11073-20701) revision shall include a requirement for the MANUFACTURER to delegate this responsibility wherever appropriate (see also SDC / 11073-20701 Amendments, Corrigenda & Errata / #64 unique identification of SaMD instances (sourceforge.net)). However, if a solution is required in a shorter timeframe, the solution should be described in SDPi as an interim step and later moved to the "Glue" SDC core standard (IEEE 11073-20701).

Challenge is how to assign identifiers to app instances (e.g. when running on virtual machines)

Start by reviewing the migrated Topics of Interest context and the linked IEEE 11073-20701 issue #64. Clarify how app instances, including virtual-machine deployments, should be identified and whether the solution belongs in SDPi as an interim step or in the Glue SDC core standard; done means a decided, documented identifier approach.