Re: Revision control

[M -dot- Vina-Baltsas -at- mindray -dot- com]

Since you put this information in your footers and covers, how do you 
handle the verbiage for maintenance releases or patches? 


________________________________________________________________

Michelle Viña-Baltsas
Senior Technical Writer

Mindray North America
800 MacArthur Blvd.
Mahwah, NJ 07430

Tel: 201-995-8350
m -dot- vina-baltsas -at- mindray -dot- com

STRICTLY PRIVATE & CONFIDENTIAL.This email may contain confidential and 
proprietary material for the sole use of the intended recipient. Any 
review or distribution by others is strictly prohibited. If you are not 
the intended recipient please contact the sender and delete all copies.



From:
Gene Kim-Eng <techwr -at- genek -dot- com>
To:
M -dot- Vina-Baltsas -at- mindray -dot- com
Cc:
techwr-l -at- lists -dot- techwr-l -dot- com
Date:
12/07/2011 11:42 AM
Subject:
Re: Revision control



We put SW version on the cover and on the footer of every page.  Users 
often print or copy single pages from our manuals to use in the field, and 
since there may be units in the field with different SW builds, it's 
essential for the user to be able to match instruction to unit build.

The doc revision is less important to us, since our doc revisions roll 
with the SW builds.  There's a revision block inside the front cover that 
lists not only the current rev but all revs of the document and which SW 
build each rev is/was for.

It seems to me that you have a 21CFR820 compliance problem if you can't 
cross-check your document revisions against their associated device 
versions.

Gene Kim-Eng


On Wed, Dec 7, 2011 at 7:52 AM, <M -dot- Vina-Baltsas -at- mindray -dot- com> wrote:
I write Ops manuals for a medical device manufacturer. We use revision
control for our manuals but we do not indicate anywhere in the manual
which version of the software the manual relates to.  So, when a client
calls our Service department or one of our clinical educators and says
that they need an additional manual, we don't know which manual to send
them because that history is not maintained anywhere in the manual.

How do the rest of you manage this?


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.
http://www.doctohelp.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com