> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:hardhats-
> [EMAIL PROTECTED] On Behalf Of Kevin Toppenberg
> Sent: Monday, January 10, 2005 7:55 PM
> To: [email protected]
> Subject: RE: [Hardhats-members] Transcriptionist crediting system
> 
> Under the menu option:
> TIU STATISTICAL REPORTS
> is the following menu:
> 
> Select Text Integration Utilities (MIS Manager)
> Option: 5  Statistical Reports
> 
> 
>    TR     TRANSCRIPTIONIST Line Count Statistics
>    AU     AUTHOR Line Count Statistics
>    SVC    SERVICE Line Count Statistics
> 
> 
> I am wondering how the system works that generates
> these statistics, and where it is documented.
> 
> Kevin
[TLP]
The statistics (I use) are not a part of VistA, though easily added to
FileMan. I do the modules as a ScreenMan "POP_UP" and access is on almost
every screen. Discover an error or omission, go to QA field and hit <ENTER>
and set of fields (driven by MJA taxonomy) allow anyone to add the QA note
on the fly. These are sorted and printed monthly, or at least every 2-3
months. The print actually goes to disk then imported to Excel (any favorite
spreadsheet), graphed, and displayed in staff break-room.  Graphs are used
to decide staff training ...tx/t  


> 
> --- Thurman Pedigo <[EMAIL PROTECTED]> wrote:
> 
> > Some lines are one word (2 or more characters), some
> > are half a line. Those
> > who use this method have a funky little transparent
> > measuring card to count
> > lines, though those I have watched usually over
> > estimate. The transcription
> > firms know how to do character counts, and would
> > adopt the method if it paid
> > better.
> >
> > I am still not sure what you want. The count isn't
> > part of VistA (is it?).
> > Of course, one does need access to some sort of WP
> > to do the count. It is
> > minimal work to create a print option that prints
> > all today's work and the
> > fields one wants to count. Then usually only 2-3
> > minutes at the end of the
> > day to get the count. I have used that option very
> > effectively.
> >
> > Since physicians are doing most of the input, we
> > don't do (embarrassing)
> > character counts. However, we capture a complete
> > battery of performance
> > measures. For instance, we count per team member,
> > new patents registered,
> > number drug screens, patient nurse setups (by type
> > of visit), errors (using
> > the MJA taxonomy), and include minutes/task on most
> > activities. VistA is
> > super for all these activities, and as I learn new
> > ones, many times several
> > others follow.
> > MJA link:
> >
> http://www.mja.com.au/public/issues/177_02_150702/mak10269_fm.pdf
> >
> > Long post, but I think performance measure not
> > matched by any system I have
> > seen.
> >
> > Thanks,
> >
> > thurman
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > [mailto:hardhats-
> > > [EMAIL PROTECTED] On Behalf Of
> > Kevin Toppenberg
> > > Sent: Monday, January 10, 2005 5:40 PM
> > > To: [email protected]
> > > Subject: RE: [Hardhats-members] Transcriptionist
> > crediting system
> > >
> > > Thurman,
> > >
> > > I think we are doing about the same thing.  I say
> > > "line" counts, because most transcription services
> > > that we have contacted have given us a price per
> > line.
> > >  But a "line" is really just a set number of
> > > characters (i.e. 60 I think).
> > >
> > > It sounds like VistA is not giving this value
> > > automatically?
> > >
> > > Thanks
> > > Kevin
> > >
> > > --- Thurman Pedigo <[EMAIL PROTECTED]> wrote:
> > >
> > > > If the goal is measuring production, character
> > count
> > > > is the most equitable
> > > > way to assess transcription. Line counts, though
> > > > commonly used, are fraught
> > > > with irregularities that make it hard to get a
> > good
> > > > production measure. We
> > > > started character counts in the early 70's when
> > IBM
> > > > began (for a price) to
> > > > install "stroke counters" on type machines.  The
> > > > transcriptionists printed
> > > > their stroke count report each day. That was a
> > real
> > > > eye opener.
> > > >
> > > > Now there are several ways to accomplish the
> > same
> > > > goal. The easiest, and
> > > > probably most efficient, I have discovered is
> > print
> > > > the days work to a file
> > > > then use one of the word processors (WP) to do
> > the
> > > > character count. If you
> > > > want words/minute divide by five (or use WP
> > count)
> > > > and then the number of
> > > > minutes on the clock may give interesting
> > numbers.
> > > > Manage other issues, such
> > > > as transcription quality, differently.
> > > > Thanks,
> > > >
> > > > thurman
> > > >
> > > > > -----Original Message-----
> > > > > From:
> > [EMAIL PROTECTED]
> > > > [mailto:hardhats-
> > > > > [EMAIL PROTECTED] On Behalf
> > Of
> > > > Kevin Toppenberg
> > > > > Sent: Monday, January 10, 2005 4:03 PM
> > > > > To: [email protected]
> > > > > Subject: RE: [Hardhats-members]
> > Transcriptionist
> > > > crediting system
> > > > >
> > > > > This is all fine and good, but what I need it
> > > > > documentation about how **VISTA** does this,
> > not
> > > > > standards that the transcriptionist union
> > publish
> > > > > about fair reimbursement.
> > > > >
> > > > > What I need to know is how to determine that
> > > > > trascriptions A has typed X number of lines
> > over
> > > > the
> > > > > last period of time.
> > > > >
> > > > > Thanks
> > > > > Kevin
> > > > >
> > > > > --- "A. Forrey" <[EMAIL PROTECTED]>
> > wrote:
> > > > >
> > > > > > That should be "E-1959-98" the year of the
> > > > latest
> > > > > > version.
> > > > > >
> > > > > > On Mon, 10 Jan 2005, Beza, Fil wrote:
> > > > > >
> > > > > > > I hope that 1959 in "ASTM -1959 Guide for
> > > > RFPs"
> > > > > > does not indicate the
> > > > > > > year the guide was produced?  ;-).
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From:
> > > > [EMAIL PROTECTED]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [mailto:[EMAIL PROTECTED]
> > > > > > On Behalf Of A.
> > > > > > > Forrey
> > > > > > > Sent: Monday, January 10, 2005 8:26 AM
> > > > > > > To: [email protected]
> > > > > > > Subject: Re: [Hardhats-members]
> > > > Transcriptionist
> > > > > > crediting system
> > > > > > >
> > > > > > > RFP - Request for Proposal a procurement
> > term
> > > > used
> > > > > > to solicit Suppliers
> > > > > > > for products and services. This is an ASTM
> > > > > > standards found in the vol
> > > > > > > 14.01 of the ASTM Book of Standards
> > usually
> > > > > > located in technical
> > > > > > > (sections of) libraries. It was put
> > together
> > > > by
> > > > > > the American Association
> > > > > > > of Transcriptionists and is included with
> > > > other
> > > > > > Electronic Health Record
> > > > > > > Standards that apply to VistA.
> > > > > > >
> > > > > > > On Sun, 9 Jan 2005, Kevin Toppenberg
> > wrote:
> > > > > > >
> > > > > > >> I have just gotten around to looking for
> > this
> > > > > > file.  I can't find it.
> > > > > > >
> > > > > > >> Is it on the VistA Documentation Library
> > web
> > > > > > site?
> > > > > > >>
> > > > > > >> Thanks
> > > > > > >> Kevin
> > > > > > >>
> >
> === message truncated ===
> 
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Hardhats-members mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hardhats-members



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to