Please select user.
There are no topics yet.
I was hoping to get some more information in regards to the 3.1 Creation and identification of documents section in the Procedure for Document and Record Control.
There is a bullet that says:
Records are coded in the following way: [describe the organization’s standard practice].
To the best of my knowledge we have never “coded” any records in any particular way so I’m working on creating the logic for this.
The paper offers an example of adding a numerical number after the procedure’s document code but I’m not sure what I’m supposed to do with that record code after we’ve assigned it.
· Does that code need to be on the record?
· If so, how does that work with forms and their code?
o For example, say we have a procedure on logging non-conforming material. The procedure is coded “PR-001”, we have a form the employee needs to fill out coded “PR-001-F”, the employee fills it out and now it’s considered a “record” so what should the record be coded and does that now need to be written on the record itself?
· Also, how does that code need to appear on things that are run automatically like for example, backup logs? Do we just add that code to the file name of the backup?
I realize all of this is up to our discretion and I may be WAY overcomplicating this, but I’m drawing a blank on how to set it up.
My question is about MDSAP. I like to know what additional requirement to ISO13485 hqs to be addressed for MDSAP.
How to fulfil documentation requirements of ISO 13485 and MDR in one Quality Management System and how to demonstrate this in a matrix
My company sells blue light blocking glasses in the EU. I now want to sell them in the US. I understand they are a Class 1 medical device hence need FDA registration.
As part of FDA compliance I understand I must have and follow a QMS. I understand my QMS is regulated by 21 CFR part 820 and if I understand correctly an ISO 13485:2016 QMS would be compliant with this. Is that correct?
I am therefore interested in your ISO 13485:2016 template which I can use to create my 21 CFR part 820 compliant QMS.
Firstly, how would the pack apply to Software as a Medical Device (SaMD)? Looking at the preview there is a lot that seems unnecessary as it is focused on the development of a physical product?
Secondly, on the software front where would Software Requirements be specified (e.g SRS Doc) is this kept as an external doc and referenced? On a similar line, what about Software Testing (e.g. unit testing, user testing)? Would you again keep an external record and link to it in the “Record of Software Validation”?
IN the toolkit we have purchased, I cant seam to find a section about intended use. Which document caters for that? What ive found so far is just technical file, but not to the extent I thought was required.
I want to ask about clause 7.3 of ISO 13485:2016. If we produce a medical device that is equivalent to another device in the market but make some changes to it, is clause 7.3 applicable for us?
1. Hello, Could you advise on defining the resolution timeline for closing Critical, Major and Minor NC ? The product is '' image viewer software ''?
2. Could you advise if the company preparing for MDR transition from MDD needs to register for UDI/ EUDAMED if they will not be placing the product on the EU market?
I would be interested in the process of meeting the regulatory requirements according to ISO 13485:2016. What are the mandatory documents ? How to handle the review process for all standards/ legislation and other regulatory documents in the company ?
I am looking for some help on Health Canada requirements for SAMD ( software as Medical Device) for a Dental radiology software. I feel it is classified as class II.
Please let me know if you have any knowledge on this- which clauses of ISO 13485 can be excluded>