All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
#1) DDC does not show / when report includes fragment call, also
crashes.
I experience this problem also and I do not know the reason. I tend to
avoid fragments (slow) but when I do have a report with a fragment and
need to see slash, I will sometimes put an MV array on my main report
temporarily and I load the temp data into the MV array to check it.
#2) Going to PHA.PAT fragment to get allergies in LIVE is slow.
Make sure you pass the field @patient from OE to your report in PHA.PAT
and select in that report
[EMAIL PROTECTED]/R.FRAG.ARG1,%Z.rw.fragment("PHA.PAT.zcus.is.your.fragment.h
ere.R","PHA."_(@.db#"1."))
pha.patient EQ
/R.FRAG.ARG1
When you have a report with a fragment that runs okay in TEST but is
slow in LIVE, chances are you are not using an index efficiently on the
fragment report. Since TEST has few records, the report runs fine in
that directory, but is very slow in LIVE.
PS: The program PHA.MAR.allergies will return an array of allergies for
you. You could call that program in the fragment.
The arguments are:
;
; A or /patient - patient
; B - max line length (defaults to 92)
; C - ^[structure to write to] for allergies (defaults to ^/MV["AL"])
; D - field number, if MV region for allergies
; E - ^[structure to write to] for adrs (defaults to ^/MV["AD"])
; F - field number, if MV region for adrs
;
So if you called it in the fragment like this:
%PHA.MAR.allergies(@pha.patient,92,^/R.FRAG.VAL["ALL"],1)
You would get a list of all the patient's allergies in
/R.FRAG.VAL["ALL",1,1] = first line of allergies, concatenated with
commas
/R.FRAG.VAL["ALL",2,1] = second line (if needed)
Back in the main report you could do this to move your data into an MV
array,
M(/R.FRAG.VAL,/MV)
If you make the "C" argument in your call to %PHA.MAR.allergies the
field number of you MV array in the main report, and use
MV=ALL in your MV line attribute, your MV will work properly.
--Your original message-- (posted in HTML)
Hi all NPR report writers,
I have a report in OE.ORD that calls a fragment from a start macro to
PHA.PAT for allergy/adr information. I can't print directly from the
fragment so I am returning my data via array -/R.FRAG.VAL["ALL"] which I
process in the macro. The report runs quickly in TEST and returns the
expected data. In LIVE, I eventually get the correct data but the report
is extremely slow.
I am trying to call the debugger in the macro to see what is happening.
%Z.ddc("X"). If I call the debugger before the fragment call, it works
fine, but if I call it anytime after that, when I type / at Node, I get
no stack. Then if I hit return to get out of the debugger, there is a
delay and then I get the ? prompt which I can only get out of with
HALT(0) which sends me to goodbye. I have not run into this problem
when debugging in other reports.
If anyone out there has run into a similar problem, I would appreciate
any advice or suggestions you could provide.
Thanks in advance,
Marcia Locke
Clinical Programmer/Analyst
Samaritan Health Services
[EMAIL PROTECTED]
Joe Cocuzzo
Vice President
NPR Services
Iatric Systems, Inc.
Phone/Fax: (978) 805-4115
Email: [EMAIL PROTECTED]
Web: www.iatric.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marcia Locke
Sent: Wednesday, April 26, 2006 1:31 PM
To: [email protected]
Subject: [MEDITECH-L] Help with NPR report debugger after fragment call
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
