From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <git@vger.kernel.org>
Cc: "'agi'" <agnes.pasztor@omixon.com>
Subject: RE: ISO 13485
Date: Tue, 17 Jun 2014 11:30:17 -0400 [thread overview]
Message-ID: <0368137BF4DA4E798A17D74DAFE30FEF@black> (raw)
In-Reply-To: <53A05766.7060502@omixon.com>
> -----Original Message-----
> From: agi
> Sent: Tuesday, June 17, 2014 10:58
>
> Hi Jason,
>
> Thanks for the speedy reply. We are in the process of trying
> to make our
> software product ISO13485 compatible and we are assessing all systems
> that we use.
> Do you have a validation document for git that could provide
> information
> on how to use it in order to comply with ISO legislations?
That would be customized to your QA process. A generalized document would be too
vague. I am sure any process consultant could draft that up for you.
(disclaimer: I have been paid to do things like this before)
Maybe you could start by searching with things like
https://www.google.com/search?q=using+QA+with+Git or contacting Atlassian about
their QA product suite integration with Git.
Maybe you could find a process consultant to do it cheaper if you release it out
to the FOSS community?
The "nice" (read as less effort) thing about ISO 13485 is it does not have a
continual improvement requirement so as long as "defects" are detected and
remediated you are good. Please note git does not detect defects, git does not
remediate defects. What git does is ensure the approved artifact is unchanged in
any attribute to maintain the exact level of quality from first inspection of
that artifact for an unlimited amount of iterations. Git has built in "digital
signatures" on the artifacts stored in its repository.
> Any additional information or material you can think of is more than
> welcome.
>
> Thanks in advance for your help!
>
>
> Best Regards,
> Agnes Pasztor
>
> Senior Test Engineer
> Omixon Biocomputing Ltd.
>
>
> On 06/16/2014 05:20 PM, Jason Pyeron wrote:
> >> -----Original Message-----
> >> From: agi
> >> Sent: Monday, June 16, 2014 11:14
> >>
> >> Hello,
> >>
> >> I would like to ask a question about GIT v. 1.7
> >>
> >> Is it compatible with ISO 13485 (quality management system)?
> >> Can it be
> >> used for developing a medical diagnostic software?
> > Yes.
> >
> > Now, do you have a specific question about how to use Git
> in your QA process?
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
next prev parent reply other threads:[~2014-06-17 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 15:14 ISO 13485 agi
2014-06-16 15:20 ` Jason Pyeron
2014-06-17 14:57 ` agi
2014-06-17 15:30 ` Jason Pyeron [this message]
2014-06-17 20:03 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0368137BF4DA4E798A17D74DAFE30FEF@black \
--to=jpyeron@pdinc.us \
--cc=agnes.pasztor@omixon.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).