[MT-L] Fw: 5.66 change to sig.out field

0 views
Skip to first unread message

Bill Mullins

unread,
Nov 5, 2013, 5:10:39 PM11/5/13
to medit...@mtusers.com
FYI...
 
Sincerely,
 
William A Mullins RN
Health Care IT Consultant

----- Forwarded Message -----
From: Bill Mullins <wmulli...@yahoo.com>
To: "Douglas...@LPNT.net" <Douglas...@LPNT.net>; Kevin <Kevin....@LPNT.net>; "Rhond...@LPNT.net" <Rhond...@LPNT.net>; "Christ...@LPNT.net" <Christ...@LPNT.net>; Sherry Weaver <swe...@visionconsulting-llc.com>; "wk...@aol.com" <wk...@aol.com>
Sent: Tuesday, November 5, 2013 4:51 PM
Subject: 5.66 change to sig.out field

FYI...
 
On our EDM Scripts report and our Med Reconcile reports written in the DPM of RXM.RX, we had issues after converting last week from 5.64 to 5.66.
 
In 5.64 I wrote the Med Rec reports with this VAL statement and they worked fine for a year:
 
xx.dosage.sig
DAT=FREE
LEN=40
JFY=L
 
5.64
 
DPM.element   RXM.RX.sig.out
Physical
Data Type  FREE                             Length    24               Local
Segment    rxm.rx.additional.info.3         Pointer
Attributes
 
-----------------------------------------------------------------------------------------------------------
Now in 5.66 this same field has thes attributes in this standard RXM.RX field:
 
DPM.element   RXM.RX.sig.out
Physical
Data Type  FREE                             Length    24
Segment    rxm.rx.additional.info.3         Pointer
Attributes
 VAL=@sig_" "_IF{"Y"=@sig.prn "PRN"}
 
 
So, here is the new VAL statement I am using in 5.66 LIVE:
 
 
 
What was happening to our reports was when they used the sig of DAILY for example,
 
This printed out as DAILY AS NEEDED for non-prn sigs...
---------------------------------------------------------------------------------------------------------
 
Sincerely,
 
William A Mullins RN
Health Care IT Consultant


Reply all
Reply to author
Forward
0 new messages