Hi back,
We are not a large hospital and we don't have nearly as many reports as
you do, but when we went with Meditech we started a log for custom
reports and decided on a naming convention for reports that would be run
by our end users.  
 
The log is simply a 3-ring binder with pages that are formatted in a
word processor that are hand written.  Down the left-hand side is a list
of numbers (we started out giving each application 100 numbers) and the
lines are spaced wide enough for a person to write the report name on. 
After the first time we had to modify a report we started noting the
Report DPM down the right-hand side of the page.  Number ranges were
assigned in alphabetical order, with 0000 to 0099 given to MIS, 0100 to
0199 given to ABS, 0200 to 0299 to ADM, etc.   
 
Any report that is put on a menu must be "numbered".  We decided that
in the name, right after "zcus" we would give a number denoted with a
lower case "r" for this purpose.  This report number is to be included
in the report header also, so if the user wanted a report to be modified
it, hopefully, would be easier to locate.  A report name is something
like ADM.PAT.zcus.r0203.er.log   Even though fragments change DPM's they
are named to match the calling report, usually something like:
BAR.PAT.zcus.r0203.frag   By only using zcus.r#### it is short enough to
use for names for compile formats and OE print formats.
 
The menu entry to call this report usually uses the last three digits
of this number, so the menu entry would look something like:
203. ER Log (r0203).
 
I look forward to seeing what others are using.
 
 
Lesa Gorman
Systems Analyst
Central Michigan Community Hospital
(989) 772-6852
[EMAIL PROTECTED] 

>>> "Susca, Rena" <[EMAIL PROTECTED]> 1/26/2007 9:16 AM >>>

Hi, all,
 
We have over 1,700 custom NPR Reports at the moment, and the number is
growing every day.  Most of these haven't been run for 3 years, and we'd
like to figure out how to manage our reports in a more efficient manner
so that we don't keep recreating the wheel everytime a request comes in.
 We have no doubt that many of our reports are duplicates, just created
by different people who didn't look for an existing report before
creating a new one.  Does anyone have a Reports Library of sorts, or any
way of managing their report requests, roll-out of reports and tracking
of who has what?  We desperately need to get this beast under control,
but haven't figured out the best way to do it.  Any suggestions would be
greatly appreciated.  Thanks!

 
Rena H. Susca
Sr. Systems Analyst
Gaylord Hospital
Phone: (203) 949-2122
Fax: (203) 294-8780
[EMAIL PROTECTED]
 
 
Our Mission is to preserve and enhance a persons health and function.
CONFIDENTIALITY NOTICE: This e-mail transmission message, together with
any other documents or attachments, is intended only for the use of the
individual or entity to which it is addressed and may contain personal
information that is subject to confidential privacy regulations such as
the Health Insurance Portability and Accountability Act of 1996 (HIPAA).
The authorized recipient of this information is STRICTLY PROHIBITED from
disclosing this information to any other party unless required to do so
by law or regulation and is required to destroy the information after
its stated need has been fulfilled. If you are not the intended
recipient, you are hereby notified that any disclosure, dissemination,
saving, printing, copying, or action taken in reliance on the contents
of these documents of this message, or any attachment, is strictly
prohibited. Please notify the original sender (only) immediately by
telephone or by reply E-mail and delete this message along with any
attachments, from your computer. Thank you. 






***Note: The information contained in this message may be 
privileged and confidential and protected from disclosure. 
If the reader of this message is not the intended recipient, 
or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify the Sender 
immediately by replying to the message and deleting it 
from your computer.
Thank you.  Central Michigan Community Hospital  
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
To subscribe or unsubscribe to the meditech-l, visit MTUsers.COM.

To check the status of the meditech-l, visit MTUsers.NET.

For help, email [EMAIL PROTECTED]
______________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l

Reply via email to