jansayshello
Starting to get Involved
Hello,
I have questions which I hope someone with similar experience of this situation can help answer.
The company I work for is involved in the development of several medical devices which are intended to be placed on the GB market, and could be placed on the EU market subsequently.
We are mindful that current GB Medical device regulations (UK MDR 2002, transposing requirements from 93/42EC, as amended) may change in the near future to align more closely to requirements from the EU MDR 2017/745, and as such, are ensuring that our UDI systems are in place – now.
Many of these "devices" are "systems" comprised of a piece of hardware (a product making physical contact with a patient) which is wirelessly connected to software (required for the device to deliver the system's intended medical purpose) installed on a separate, supplied, mobile device such as a locked-down tablet pc (accessory).
The hardware may also have a charging unit as an accessory to the system.
We design and manufacture the hardware (and its firmware), app software, and supply the mobile device together in a carry kit.
For the purpose of my questions, let's also make the following assumptions:
Jan
I have questions which I hope someone with similar experience of this situation can help answer.
The company I work for is involved in the development of several medical devices which are intended to be placed on the GB market, and could be placed on the EU market subsequently.
We are mindful that current GB Medical device regulations (UK MDR 2002, transposing requirements from 93/42EC, as amended) may change in the near future to align more closely to requirements from the EU MDR 2017/745, and as such, are ensuring that our UDI systems are in place – now.
Many of these "devices" are "systems" comprised of a piece of hardware (a product making physical contact with a patient) which is wirelessly connected to software (required for the device to deliver the system's intended medical purpose) installed on a separate, supplied, mobile device such as a locked-down tablet pc (accessory).
The hardware may also have a charging unit as an accessory to the system.
We design and manufacture the hardware (and its firmware), app software, and supply the mobile device together in a carry kit.
For the purpose of my questions, let's also make the following assumptions:
- The combination of these "products" are only intended to be sold together as one system (i.e. system components are not sold individually).
- However, some system components may be supplied to a customer only as a replacement in the event of a fault with that component (e.g. replacement charging unit).
- The "system" has a Product Code, which is based on the manufacturing assembly number.
- The "system" has a GTIN (13-digit with a leading 0 to make 14 digits) as a (Basic) UDI-DI.
- Each "loose" system component - i.e. the hardware, charging unit, tablet PC, software has a product code which is based on its manufacturing assembly/part number.
- Does each "loose" system component require its own unique (Basic) UDI-DI (i.e. a GTIN number) and labelling, where the whole system is also "packaged" with a label containing the system UDI-DI?
- Or does each system component require a label, but this label contains the same content as its parent system?
- If the answer to 1. is yes, does this only apply to the system components which are intended to be supplied as spare/replacement components, or does it apply to all components?
Jan