Imagine my surprise to see this today since we just reported the IST job issue 
yesterday. Fortunately, our response from Meditech was:
 
Duffy,Bill (MEDITECH) - Jun 19, 2007 - 1754 EDT:  

The IST is aborting on a PHA transaction, we're trying to kill a data node but
the "/" prefix is not open.  I'll ask PHA apps to take a look.

                    IST Abort Information for Segment A

Last transaction read from segment C Index number 203905
Seg A                                Date 07/06/19              Time 16:50:42
OSRN P81OSAL_8KS.05/19/06.16:01:01 Pgm Blk 2586852 Err Blk 2586852
First Line PHA.DRUG.price.update,AD,P5.5.MIS,5.5,05.12.02.1709,"COLOR",
Error Line   K(/TF[tf]VV),""^tfVQ,"Def buf V",

Error Location (Decimal) 4238425  (Hex) 40AC59  (Octal) 20126131

Prefixes
# = Closed
$ = A RAD 638R
% = A RAD 481997R
& = Closed
* = C RAF 3N1271R
? = A RAF 1220R
\ = A RAF 46876R
/ = Closed
: = C RAD 3N667R
! = Closed

Moran,Jennifer (MEDITECH) - Jun 19, 2007 - 1803 EDT:  Hi Steve - can you
investigate? Tahnk you! 

Gehm,Stephen (MEDITECH) - Jun 19, 2007 - 1922 EDT: The IST job on the A machine
is crashing due to a problem transaction from PHA.  

PHA DTS 7315 addresses this issue.  We need permission to add this change. 
Since the IST job is already dead, the only way to correct this, is to add the
change to TEST and LIVE, and restart the IST job.  

There really isn't any way for this DTS to be tested by users on site.  I will
add this change INHOUSE.  Let me know when we have Change Control to add to TEST
and LIVE.

I hope this may be of some help,
Paul
 

Paul Goedicke 
IT Analyst III 
Jackson County Memorial Hospital 
1200 E.Pecan, Altus, OK 73521 
Phone: (580) 477-7485 
Fax: (580) 477-7366 
Email: [EMAIL PROTECTED] 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Haynes, Dan
Sent: Wednesday, June 20, 2007 8:28 AM
To: MEDITECH-L@MTUsers.com
Subject: Re: [MEDITECH-L] Medical Necessity Requirements Dictionary



We are having this problem also with no help from Meditech.

 

Dan Haynes

Applications Coordinator

Magnolia Regional Health Center

611 Alcorn Dr

Corinth, MS 38834

662-293-1127


  _____  


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carol Higley
Sent: Wednesday, June 20, 2007 7:54 AM
To: Jay Gilmore; MEDITECH-L
Subject: Re: [MEDITECH-L] Medical Necessity Requirements Dictionary

 

CONTACT MEDITECH!!!!

 

We have been having this issue for a year or more and have been dealing with 
Meditech constantly.  They have recently put a group on this because apparently 
more of you are contacting them and they realize they are having a problem.  

 

At first they kept blaming our network but finally they are looking at this in 
a broader picture.  

 

They will dial in and shadow the jobs but have not come up with much yet.  We 
either see high CPU or the IST problem when this is happening.  Also, have 
found many schedule reports running but nothing positive yet.

 

Good luck.

 

Carol

 

 

Carol L. Higley
Data Systems Analyst
Howard Regional Health System
765-453-8140


The opinions expressed in this e-mail message are those of the author and may 
not be representative of Howard Regional Health System or affiliates.  This 
e-mail message and attachments, if any, may contain confidential or privileged 
information.  If you are not the addressee or authorized to receive this 
message for the addressee, you must not use, copy, disclose, or take any action 
based on this message, any attachments to this message, or any information 
herein.  If you have received this message in error, please advise the sender 
immediately by reply e-mail and delete this message in its entirety.



>>> "Jay Gilmore" <[EMAIL PROTECTED]> 6/19/2007 10:05 AM >>>

I am curious if anyone else has problems when during and after the filing of 
the MIS Medical Necessity Requirements dictionary.

 

Our Patient Accounting manager is the one in charge of this dictionary.  She 
usually updates this dictionary in the middle of the night from home, because 
it appears to have such an impact on system functionality.  There used to be a 
major decrease in response time throughout the system when this dictionary was 
filed.  This does not appear to be an issue anymore, as the Patient Accounting 
manager accidentally filed this dictionary one day last week.

 

However, it seems that the other MIS dictionaries when the Medical Necessity 
Requirements dictionary is filed.  I was setting up a user, and then went to 
Copy Access Dictionaries, and the new user I set up was not available in the 
lookup.  I also went to the Nurse Dictionary in NUR to initialize this user 
there, and the user was not available in that lookup either.  The Patient 
Accounting manager also noticed that she had entered a new insurance into the 
MIS Insurance dictionary, but was unable to see it in the lookup in one of her 
BAR dictionaries.

 

Not only did these things happen, but the filing of the Medical Necessity 
Requirements dictionary generated errors on the caretaker:

 

BACKGROUND JOB A * IST NOT FUNCTIONING PROPERLY

 

There were also messages for Job B and D as well.  MEDITECH said that 
everything was fine.  “The CPT dictionary is being updated causing the IST's to
run a bit slower but they are moving. Once this completed the IST's will go 
back to idling.”

 

Does anyone else have problems with this besides us?  Has anyone found a 
solution to this problem, or does anyone know of a DTS that could possibly 
correct this issue?  Any responses are greatly appreciated.

 

Thanks,

 

 

Jay Gilmore

 

Systems Analyst

Crisp Regional Hospital

(229) 276-3173

[EMAIL PROTECTED]

 



  _____  

This email has been scanned by the JCMH McAfee Webshield appliance and has been 
cleared for delivery. If you have any concerns or questions, call the IT 
Helpdesk at x2646. 





The documents accompanying this transmission contain confidential information, 
belonging to the sender, that is legally privileged.  This information is 
intended only for the use of the individual or entity named above.  The 
authorized recipient of this information is prohibited from disclosing this 
information after its stated need has been fulfilled.

If you are not the intended recipient, you are hereby notified that any 
reading, disclosure, copying, distribution, or action taken in reliance on the 
contents of these documents is strictly prohibited.  Violators may be 
prosecuted.  If you have received this email in error, please notify the sender 
immediately and destroy the transmitted information.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
To subscribe or unsubscribe to the meditech-l, visit 
http://mtusers.com/mailman/listinfo/meditech-l_mtusers.com

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

For help, email [EMAIL PROTECTED]

Please visit and add information to the MTUsers WikiPedia at MTUsers.NET/mwiki
______________________________________
meditech-l mailing list
meditech-l@MTUsers.com
http://mtusers.com/mailman/listinfo/meditech-l_mtusers.com

Reply via email to