M
Mr_medtech
I have taken a look at the other threads which are very useful but i don't feel like anyone has explicitly asked and answered this question.
We are building a pure software medical device and need to implement iso 13485. Is it feasible to implement this standard on our own without prior experience in ISO standards / implementing a QMS. There are literally two of us in the company and will need to undertake other business related activities. One of us can take the lead on the design and implementation.
I have read through the standards clause by clause and read about each clause, although i would say that claiming i "understand" or have internalised each clause would be a leap. It feels like this process is very much something that is learned by doing. Would attending a BSI training course on implementing the standard be useful? We have a very limited budget and i don't want to waste money on something that won't add value.
Furthermore, there seem's to be a plethora of eQMS systems online. Are there any that anyone could vouch for in terms of cost & quality for a smaller team?
Is it an issue that there are only two of us in the company and we are both new to ISO standards? For example, training is part of the standard. I assuming if i undertook an implementation course i can then train my co-founder on the importance of working to this standard and what it means for us as an organisation and all the processes we use/follow.
Finally, in terms of quality manual, quality policy and SOPs. I'm wondering if there is some sort of ISO specific way this stuff should be laid out - i understand the content but i'm wondering if we don't create these documents in a certain way will it look like we are complete amateurs if we have an external audit / once we go for the certificate.
I will add that i actually really do see the value in doing this from a product realisation perspective and a lot of the things the standard asks for we are already doing, we just need to formalise the processes and start to document things. I'm slightly worried that the "continuous improvement" side of things could be a pain, but i'm thinking we could start to include potential QM/S improvements in our weekly retrospective.
Thanks
We are building a pure software medical device and need to implement iso 13485. Is it feasible to implement this standard on our own without prior experience in ISO standards / implementing a QMS. There are literally two of us in the company and will need to undertake other business related activities. One of us can take the lead on the design and implementation.
I have read through the standards clause by clause and read about each clause, although i would say that claiming i "understand" or have internalised each clause would be a leap. It feels like this process is very much something that is learned by doing. Would attending a BSI training course on implementing the standard be useful? We have a very limited budget and i don't want to waste money on something that won't add value.
Furthermore, there seem's to be a plethora of eQMS systems online. Are there any that anyone could vouch for in terms of cost & quality for a smaller team?
Is it an issue that there are only two of us in the company and we are both new to ISO standards? For example, training is part of the standard. I assuming if i undertook an implementation course i can then train my co-founder on the importance of working to this standard and what it means for us as an organisation and all the processes we use/follow.
Finally, in terms of quality manual, quality policy and SOPs. I'm wondering if there is some sort of ISO specific way this stuff should be laid out - i understand the content but i'm wondering if we don't create these documents in a certain way will it look like we are complete amateurs if we have an external audit / once we go for the certificate.
I will add that i actually really do see the value in doing this from a product realisation perspective and a lot of the things the standard asks for we are already doing, we just need to formalise the processes and start to document things. I'm slightly worried that the "continuous improvement" side of things could be a pain, but i'm thinking we could start to include potential QM/S improvements in our weekly retrospective.
Thanks