Q
Hi there,
i am thinking about how far we have to go with UDIs on standalone software and medical apps.
We ship our software as download and as CD.
As far as i understand the regulation we have to create an UDI for each relase of the software and print this an the CD-Label as well as in the "about" screen inside the software.
But do we need to create an UDI for each installation of our software to pull the traceability from the build down to the installed software at the customer's servers?
And how to handle the UDI for medical apps that are distributed by app stores of google or apple?
I could think of an UDI for this in this form: DI + software-version (PI) + License-Key
i am thinking about how far we have to go with UDIs on standalone software and medical apps.
We ship our software as download and as CD.
As far as i understand the regulation we have to create an UDI for each relase of the software and print this an the CD-Label as well as in the "about" screen inside the software.
But do we need to create an UDI for each installation of our software to pull the traceability from the build down to the installed software at the customer's servers?
And how to handle the UDI for medical apps that are distributed by app stores of google or apple?
I could think of an UDI for this in this form: DI + software-version (PI) + License-Key