|
Elsmar Cove Forum Sidebar
|
|
|
|
Monitor the Elsmar Forum
|
| Monitor New Forum Posts
|
|
Follow Marc & Elsmar
|
|
|
Elsmar Cove Groups
|
|
|
Sponsor Links
|
|
|
|
|
|
Donate and $ Contributor Forum Access
|
 |
|
Sponsored Links
|
|
|
|
Courtesy Quick Links
|
 Links that Elsmar Cove visitors will find useful in your quest for knowledge:
Howard's International Quality Services
Atul's Symphony Technologies
Marcelo Antunes' SQR Consulting
Bob Doering's Correct SPC - Precision Machining
NIST's Engineering Statistics Handbook
IRCA - International Register of Certified Auditors
SAE - Society of Automotive Engineers
Quality Digest Portal
IEST - Institute of Environmental Sciences and Technology
ASQ - American Society for Quality
|
|
 |

3rd March 2010, 11:31 AM
|
|
Email Address Invalid or Rejected by Recipient System
Registration Date: Jan 2010
|
|
Posts: 15
Thanks Given to Others: 236
Thanked 4 Times in 2 Posts
Karma Power: 0 Karma: 30 
|
|
Medical Device Labelling requirements for Class II software
I have a question regarding the medical device labelling.
ISO 13485 did not mention the requirement for labeling in detail. However, FDA has a few regulations regarding labeling, such as 21CFR 801, General Device Labeling and 21 CFR 820 QMS. Since we are a software company, I am wondering how we should implement this part. To my understanding, we need to have the following components included in the label:
• Name of the software
• Name and address of manufacturer
• The identifier of the device, eg. A number to distinguish the device from others
• Indications for use
• CE mark (since we sell it to Europe)
• Rx sign
However, the fact that the company distributes its product through web server (does not sell packaged software) makes this question even trickier. I am not sure where and how we should “label” the software before they are distributed. Do you have any suggestions for me to implement this part?
Any help is appreciated! Thanks
Sue
|

3rd March 2010, 12:40 PM
|
 |
Involved in Discussions
Registration Date: Mar 2008
Location: Hartland, WI
|
|
Posts: 47
Thanks Given to Others: 5
Thanked 63 Times in 25 Posts
Karma Power: 26
|
|
|
Re: Medical Device Labelling for class II software
Good question Sue! I am not certain how to address this but I believe having the required labeling within the software would be sufficient (commonly in a Help - About menu) for software that is only distributed electronically. Also, you need to have instructions for use available with the software that should also have this labeling. These instructions can be provided electronically but must also be provided in print if requested by the user.
Between the instructions and other labeling in the software interface I think you can address all the requirements without issue.
|
|
Thank You to blewispunk for your informative Post and/or Attachment!
|
|

6th March 2010, 01:59 AM
|
|
Shaked
Registration Date: Feb 2005
Location: Israel
|
|
Posts: 76
Thanks Given to Others: 30
Thanked 25 Times in 11 Posts
Karma Power: 41 Karma: 135  
|
|
|
Re: Medical Device Labelling requirements for Class II software
Hi Sueliu,
Since the topic that you are asking about is very specific
I would like to present to you a path that could give
more "light" toward the need answer
In EN 62304:2006 the issue of Medical Software "stand alone" is covered but
the labeling issue is not covered totally.
You can use as an alternative the attached flow chart to study which information sources are suggested by the CE for your topic.
Nissim
|
|
Thank You to Nissim Shaked for your informative Post and/or Attachment!
|
|

9th March 2010, 01:14 PM
|
|
Email Address Invalid or Rejected by Recipient System
Registration Date: Jan 2010
|
|
Posts: 15
Thanks Given to Others: 236
Thanked 4 Times in 2 Posts
Karma Power: 0 Karma: 30 
|
|
|
Re: Medical Device Labelling requirements for Class II software
I have asked the same question to a friend who works in Germany. The following are his answers. Just want to share with people who have similar questions as me.
Labelling for the EU consists of 4 major parts:
1. In the SW itself (e.g. About Dialog with Manufacturers Adress CE Label , EU Rep and Notified Body ID in case of Class I* or higher, and a reference to the applicable MDD )
2. The packaging (meaning box and CD) contains Identifier of the SW, Manufacturers Adress CE Label , EU Rep and Notified Body ID -- Talk to you NB / EU Rep whether you will need to apply the symbols according to ISO 980. Each NB / EU Rep has a different oppion on that.
3. Accompanying document such as : The Declaration of Conformity (DoC). Release Notes
4. User Manual and Safety Instructions.
|
|
Thanks to sueliu - 2012 for your informative Post and/or Attachment!
|
|

20th April 2010, 06:41 AM
|
 |
S.Subramaniam, Chennai
Registration Date: Aug 2007
Location: India
|
|
Posts: 537
Thanks Given to Others: 196
Thanked 832 Times in 338 Posts
Karma Power: 86
|
|
|
Re: Medical Device Labelling requirements for Class II software
Quote:
In Reply to Parent Post by sueliu
I have a question regarding the medical device labelling.
ISO 13485 did not mention the requirement for labeling in detail. However, FDA has a few regulations regarding labeling, such as 21CFR 801, General Device Labeling and 21 CFR 820 QMS. Since we are a software company, I am wondering how we should implement this part. To my understanding, we need to have the following components included in the label:
• Name of the software
• Name and address of manufacturer
• The identifier of the device, eg. A number to distinguish the device from others
• Indications for use
• CE mark (since we sell it to Europe)
• Rx sign
However, the fact that the company distributes its product through web server (does not sell packaged software) makes this question even trickier. I am not sure where and how we should “label” the software before they are distributed. Do you have any suggestions for me to implement this part?
Any help is appreciated! Thanks
Sue
|
Hi Sue
Under Directive 2007/47/EC, when your software is classified as a medical device, it is subject to the same medical device requirements as under MDD 93/42/EEC. Therefore the language requirement of MDD 93/42/EEC applies as per Annex I, 13.3 (Information supplied by the manufacturer) that includes such documentation provided electronically as IFU, operators manuals, installation manuals, packaging and labeling to name a few. Additionally, for software classified as a medical device under Directive 2007/47/EC, “information” includes GUI (Graphical User Interface), menus, dialog boxes, and error and status messages.
Also, member states may require the information, which must be made available to the user and the patient in accordance with Point 13.3 of Annex I, to be in their national languages, when a device reaches the final user.
S. Subramaniam
|
|
Thank You to bio_subbu for your informative Post and/or Attachment!
|
|
Lower Navigation Bar
|
|
|
Do you find this discussion thread helpful and informational?
|
Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate Thread Content |
Linear Mode
|
|
Forum Posting Settings
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|