VistApedia - User contributions [en]

Projects

2007-06-27T13:31:06Z

Kdtop3:

<h3>Welcome to the WorldVistA "Brainstorming" Projects Page</h3>
<p>The Projects page is the working directory of WorldVistA project ideas. All
project concept are welcome - new and old.</p>
<h3>The Process</h3>
<ol>
<li>Project ideas and description will be collected and published on this
page.
<li>High-level benefit analysis will be applied.
<li>Suggestions will be reviewed, prioritized and endorsed by the WorldVistA
leadership.
<li>Funding will be sought and teams will be organized for projects that are
determined to be of high value and show promise of successful completion.</li>
</ol>
<h3>Brainstorming Rules:</h3>
<ol>
<li>Offer and collect as many ideas as possible. 
<li>All ideas are valuable, the more the better. One crazy idea spawns three
rational ideas. 
<li>Don't spend time discussing details during brainstorming phase. Ideas
submitted will be analyzed  and deconstructed at length later...
<li>Do not be critical of ideas, it stifles the process and make creative
thinkers go back into the box.
<li>Build on other ideas. Linking one idea to another is powerful.
<li>Capture all ideas and make them visible.
<li>Set a time limit. This iteration closes on 07/06/2007.</li>
</ol>
<h3>Please supply the following:</h3>
<ul>
<li>Project title
<li>Brief description
<li>Benefit provided
<li>Your name (so we know who to ask for clarification -- anonymous posts are
accepted.)
<li>Email address (optional)</li>
<li>link to projects.worldvista.org Project page if exists</li>
</ul>
<p>(If you would rather submit your project ideas via email -- send them to
webmaster@members.worldvista.org with the subject line: WorldVistA Projects) </p>
<h3>Please add your project suggestion(s) here:</h3>
<p><b>Chris Richardson </b>(to be detailed)</p>
<ul>
<li>Training Ideas - Tools, Teachers, and Techniques</li>
<li>I18N (Internationalization) - Issues and Answers</li>
<li>Transport of Medical and Health Records</li>
<li>Post-Traumatic Stress Disorder - Developments and Impacts</li>
<li>New Organizations, MDC (new) and VDC (even newer)</li>
<li>Ontologies and how VistA fits in with them.</li>
</ul>

<p><b>Peter Bodtke </b>(to be detailed)</p>
<ul>
<li>Internationalization (support foreign languages, i.e. Spanish) 
<li>Patch stream updating system (does this project need assistance?)
<li>Marketing and Public Relations: WorldVistA organization and WorldVistA EHR
VOE V1.0 software package
<li>Installers (WorldVistA EHR VOE w/Registration GUI, VistA/G.TM/Linux)
<li>Integration - localization interface wizards
<li>Achieve United Nations NGO status
<li>Standard Development Architect and Tools
<li>VistA Documentation Repository
<li>Educational materials / training materials / book
<li>VistA Demo Appliance V1.2 (next iteration, including "VistA
link", Vitals, Patient Registration GUI)
<li>Community surveys (members skills and needs, adopters registry,
integrators registry)</li>
</ul>
<p><b>Project topic found on VistApedia (anonymous and other sources) </b>(to be
detailed)</p>
<ul>
<li>OpenForum (not sure what this project team had in mind)
<li>Pediatrics Package (will IHS templates suffice?)
<li>OB/GYN Package (will IHS templates suffice?)
<li>Billing Package
<li>Configuration and Installation
<li>Ambulatory Care Data Capture
<li>WorldVistA EHR / VOE FAQs need to be updated
<li>An information / press kit is needed with key articles, links to demos,
etc.
<li>WorldVistA.org links to software need to be edited
<li>Combine and edit SourceForge sites (VOE project, WorldVistA EHR,
WorldVistA, and VistAOutreach) Add abstract/index and improve naming
conventions for software</li>
</ul>
<p><b>Kevin Toppenberg (kdtop) </b></p>
<ul>
<li>Multiple language support (I am working on this) 
<li>Server data "Save As"... i.e. ability to export site-specific data, for import into another installation. This would make VistA analogous to Word, which could open, close, transfer, share etc. data sets.
<li>Better installation and configuration tools
<li>Enable CPRS to run on Linux
</ul>

Pharmacy Issues

2007-01-11T05:31:51Z

Kdtop3: /* RPC Calls */

This page will contain notes to work out pharmacy programming issues.

Initiated by K. Toppenberg 4/2005

=== Keys Needed for Pharm. Setup ===
We searched pharmacy routines and found keys that were needed for some of the pharmacy setup routines. Here are the keys that were found:
PSA ORDERS, PSAMGR, PSJ RPWARN, PSB MANAGER, PSB CPRS MED BUTTON, PSB INSTRUCTOR, PROVIDER, PSD TECH, PSDMGR, PSD BUMGR, PSD ERROR, PSD PARAM, PSD TRAN

----

=== Files and Relationships ===
*<b>VA PRODUCT</b> file (file #50.68, ^PSNDF(50.68,*)) holds ALL possible drugs. Some people refer to this as the National Drug File. [[File Info: 50dot68]]
*<b>VA GENERIC</b> file (file #50.6, ^PSNDF(50.6))
*<b>DRUG</b> file (file #50, ^PSDRUG(*)) holds all the drugs in the local formulary. This links to above. [[File Info: 50]]
*<b>PHARMACY ORDERABLE ITEM</b> file (file #50.7, ^PS(50.7,*)) holds things that can be ordered from the pharmacy. This links to above. [[File Info 50dot7]]
*<b>ORDERABLE ITEM</b> file (file #101.43, ^ORD(101.43,*)) holds things that can be ordered, including labs and drugs. This links to above. [[File Info 101dot43]]
*<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,*)) holds "quick order" entries. This links to above. [[File Info 101dot44]]

[[Summary of Pharmacy File Linkages]]

What I Have Learned so Far

1. '''File 50.7 (PHARMACY ORDERABLE ITEM):'''
**A record in this file should be created first.
.01 field should be the generic name of the drug.
When the record is created, an entry in fle 101.43 (ORDERABLE ITEM) will automatically be made.
Also, a record in in ORDER QUICK VIEW will also be created (but it is incomplete--see below.)
Note: new drugs may not be added unless PSEDITNM>0. So to setup a drug in fileman,
set PSEDITNM=1 from the command-line, then DO D^DI to get into Fileman with vars intact.
In the MED ROUTE field, the input transform does not allow an input of "ORAL". (If left
blank ORAL will be shown in CPRS)
This file can hold the synonyms of a drug etc.
When this record is created, for some reason it is automatically given the current
date in the INACTIVE DATE field--meaning it is created in an inactive state. One must
go back and edit the record a second time to remove the entry from this field.
File 101.43 (ORDERABLE ITEM), field ID holds a text pointer to this file, e.g.
"10;99PSP" <---- 10 is IEN in file #50.7
There is no pointer field from file 50.7 up to file 50. The link is FROM file #50
TO #50.7 (via file #50's field 2.1(PHARMACY ORDERABLE ITEM)). HOWEVER, File #50's
"ASP" cross-reference for the field "PHARMACY ORDERABLE ITEM (#2.1) i.e.
^PSDRUG("ASP",IEN_in_50.7,*), contains list of linked records in file #50

2. In '''file# 50 (DRUG, ^PSDRUG):'''
This file will hold a separate record for every different medication/tablet size.
For example, there will be one for AMOXICILLIN 250, and another for AMOXICILLIN 500.
Both of the above records would be linked to one record in the PHARMACY ORDERABLE ITEM,
i.e. an AMOXICILLIN record.
The link should be in field 2.1 (the PHARMACY ORDERABLE ITEM field), which will
hold a pointer to file 50.7 (PHARMACY ORDERABLE ITEM file)

3. In '''file 101.43 (ORDERABLE ITEM)''' an entry for the drug must exist like this:
This entry should have been made automatically when the PHARMACY ORDERABLE ITEM was
created.

file 101.43
record: .01 NAME = LISINOPRIL
2 ID = "Unique identifier, created from primary key passed in the
Orderable Items update message from each package; it will be
in the form of 'package code;99XXX' where XXX indicates the
package table originating this item (i.e. RAP,LRT,etc.)
[e.g. in my system, then entry for DILTIAZEM TAB is 1;99PSP]
"Package code" should be the IEN on the PHARMACY ORDERABLE ITEM (#50.7)

4. '''101.44 (ORDER QUICK VIEW)''' For meds to show up in the dialog box in CPRS, it must have a entry like this:
Again, this entry should have been created automatically when the PHARMACY ORDERABLE ITEM
was created. But for some reason, the DISPLAY TEXT field is not filled in. Without this,
the drug will not appear in CPRS. So this must be manually supplied.

file: 101.44 (ORDER QUICK VIEW);
record: ORWDSET O RX;
subfile: SET MEMBER (101.442)
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.

=== Example of Data===
<pre>
File 101.44 (ORDER QUICK VIEW)
.01-NAME : ORWDSET O RX
6-LAST UPDATE : 60414,61441
20-SET MEMBER :
-snip-
Multiple Entry #15 <--- notice that there are no doses
.01-SET MEMBER : SILDENAFIL TAB <-- pointer to 101.43
2-DISPLAY TEXT : SILDENAFIL TAB
-snip-
Multiple Entry #17 <--- notice that there are no doses
.01-SET MEMBER : SILDENAFIL TAB <-- pointer to 101.43
2-DISPLAY TEXT : VIAGRA <SILDENAFIL TAB>
-snip-
||
||
\/

File 101.43 (ORDERABLE ITEM)
.01-NAME : SILDENAFIL TAB
1-SYNONYMS :
Multiple Entry #1
.01-SYNONYM : VIAGRA
1.1-PACKAGE NAME : SILDENAFIL TAB
2-ID : 4;99PSP <--- pointer to IEN=4 in 50.7
5-DISPLAY GROUP : PHARMACY
9-SET MEMBERSHIP :
Multiple Entry #1
.01-SET : RX
-snip-
||
||
\/

File 50.7 (PHARMACY ORDERABLE ITEM)
.01-NAME : SILDENAFIL
.02-DOSAGE FORM : TAB
.05-DAY (nD) or DOSE (nL) LIMIT : 2L
.07-SCHEDULE TYPE : FILL ON REQUEST
2-SYNONYM :
Multiple Entry #1
.01-SYNONYM : VIAGRA <-- free text
7-PATIENT INSTRUCTIONS : [Do not take with nitroglycerin]
||
||
\/

ASP index in file 50 allows link from 50.7 --> 50
^PSDRUG("ASP",4,7118) = IEN# 4 in 50.7 --> IEN# 7118 in 50
||
||
\/

File 50 (DRUG file) (some noncontributory fields edited)
.001-NUMBER : 7118
.01-GENERIC NAME : SILDENAFIL (Viagra) 50MG TAB
2.1-PHARMACY ORDERABLE ITEM : SILDENAFIL
9-SYNONYM :
Multiple Entry #2
.01-SYNONYM : VIAGRA
1-INTENDED USE : TRADE NAME
14.5-DISPENSE UNIT : TAB
20-NATIONAL DRUG FILE ENTRY : SILDENAFIL
21-VA PRODUCT NAME : SILDENAFIL CITRATE 50MG TAB
22-PSNDF VA PRODUCT NAME ENTRY : SILDENAFIL CITRATE 50MG TAB
101-MESSAGE : Use for 25mg dose only
215-QUANTITY DISPENSE MESSAGE : MAX 4 DOSE/MO-CONTRAINDICATED WITH NITRATES
901-STRENGTH : 50
902-UNIT : MG
903-POSSIBLE DOSAGES :
Multiple Entry #1
.01-DISPENSE UNITS PER DOSE : 1
2-PACKAGE : IO
Multiple Entry #2
.01-DISPENSE UNITS PER DOSE : .5
2-PACKAGE : O
Multiple Entry #3
.01-DISPENSE UNITS PER DOSE : 1
1-DOSE : 50
2-PACKAGE : IO
Multiple Entry #4
.01-DISPENSE UNITS PER DOSE : 2
1-DOSE : 100
2-PACKAGE : IO

</pre>
----

=== Example Entry ===

Here is an example of entering the drug the "proper" way, via menu options:
[[Drug Entry Edit Example]]

Here is a sample inquirery of one successfuly added drug: furosemide
(NOTICE: in this system, there is only 1 orderable drug from CPRS)

OUTPUT FROM WHAT FILE: NEW PERSON// 50.7 PHARMACY ORDERABLE ITEM
(1 entry)
(NOTE: reformatted for easier reading)
Select PHARMACY ORDERABLE ITEM NAME: ?
Answer with PHARMACY ORDERABLE ITEM NAME, or SYNONYM, or OI-DRUG TEXT ENTRY:
FUROSEMIDE FUROSEMIDE TAB

Select PHARMACY ORDERABLE ITEM NAME: furOSEMIDE TAB
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)

NUMBER: 1
NAME: FUROSEMIDE
SYNONYM: LASIX
DOSAGE FORM: TAB

Select PHARMACY ORDERABLE ITEM NAME:

OUTPUT FROM WHAT FILE: 101.43 ORDERABLE ITEMS//
(NOTE: reformatted for easier reading)
Select ORDERABLE ITEMS NAME: furose
1 FUROSEMIDE
2 FUROSEMIDE TAB
CHOOSE 1-2: 1 FUROSEMIDE
ANOTHER ONE: furo
1 FUROSEMIDE
2 FUROSEMIDE TAB
CHOOSE 1-2: 2 FUROSEMIDE TAB
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)

NUMBER: 774
NAME: FUROSEMIDE
ID: 828;99LRT
DISPLAY GROUP: LABORATORY
PACKAGE NAME: FUROSEMIDE
SYNONYM: LASIX
SET: LAB
TYPE: both

NUMBER: 1659
NAME: FUROSEMIDE TAB
ID: 1;99PSP <---- x;99PSP x=IEN in file# 50.7 (PHARMACY ORDERABLE ITEM)
DISPLAY GROUP: PHARMACY
PACKAGE NAME: FUROSEMIDE TAB
SET: RX
SET: UD RX
SET: O RX
INPATIENT MED: YES
OUTPATIENT MED: YES
IV BASE: NO
IV ADDITIVE: NO
SUPPLY: NO
NON-FORMULARY: NO
NON-VA MEDS: NO

Select ORDERABLE ITEMS NAME:

OUTPUT FROM WHAT FILE: 101.44 ORDER QUICK VIEW
(2 entries)
(NOTE: reformatted for easier reading)
Select ORDER QUICK VIEW NAME: ?
Answer with ORDER QUICK VIEW NAME
Choose from:
ORWDQ PKG35 DO
ORWDSET O RX

Select ORDER QUICK VIEW NAME: orwdset O RX
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)

NUMBER: 2
NAME: ORWDSET O RX
LAST UPDATE: 60201,74282
SET MEMBER: FUROSEMIDE TAB
DISPLAY TEXT: FUROSEMIDE TAB

Select ORDER QUICK VIEW NAME:

=== Other Important Pharmacy Files and Relationships ===

=== Steps to Adding One Drug / Making Available in CPRS ===

GTM>set PSEDITNM=1
GTM>D D^DI

VA FileMan 22.0
Select OPTION: enter OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: DRUG// 50.7 PHARMACY ORDERABLE ITEM
(3 entries)
EDIT WHICH FIELD: ALL//

Select PHARMACY ORDERABLE ITEM NAME: VIAGRA
Are you adding 'VIAGRA' as a new PHARMACY ORDERABLE ITEM (the 4TH)? No// Y
(Yes)
PHARMACY ORDERABLE ITEM DOSAGE FORM: tab
1 TAB
2 TAB,BUCC,SA
3 TAB,BUCCAL
4 TAB,CHEWABLE
5 TAB,CHEWG GUM
Press <RETURN> to see more, '^' to exit this list, OR
CHOOSE 1-5: 1 TAB
PHARMACY ORDERABLE ITEM INACTIVE DATE:
DOSAGE FORM: TAB// (No Editing)
IV FLAG:
INACTIVE DATE:
DAY (nD) or DOSE (nL) LIMIT: ??
Type a whole number between 0 and 99, 0 decimal digits, followed by either
a "D" (for NUMBER OF DAYS) or an "L" (for DOSE LIMIT).
DAY (nD) or DOSE (nL) LIMIT: 2L
MED ROUTE:
SCHEDULE TYPE: r FILL ON REQUEST
SCHEDULE:
SUPPLY:
Select SYNONYM: VIAGRA
Are you adding 'VIAGRA' as a new SYNONYM (the 1ST for this PHARMACY ORDERABLE ITEM)? No// Y (Yes)
Select SYNONYM:
Select OI-DRUG TEXT ENTRY:
PATIENT INSTRUCTIONS: [Do not take with nitroglycerin]

[Do not take with nitroglycerin]
OTHER LANGUAGE INSTRUCTIONS:
NON-VA MED:

Select PHARMACY ORDERABLE ITEM NAME:

Select OPTION:

Note: You have to go back and edit the INACTIVE DATE, and delete the value.

------------------------------------------------------------------------------
Now create link from #50, field 2.1 --> 50.7
------------------------------------------------------------------------------
Select OPTION: eNTER OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: DRUG// 50 DRUG (5173 entries)
EDIT WHICH FIELD: ALL// pharmACY ORDERABLE ITEM
THEN EDIT FIELD:

Select DRUG GENERIC NAME: viagra
1 VIAGRA SILDENAFIL (Viagra) 50MG TAB GU900 Use for 25mg dose only
2 VIAGRA SILDENAFIL (Viagra) 100MG TAB GU900 ONLY 4 DOSES PER MONTH ALLOWED
CHOOSE 1-2: 1 SILDENAFIL (Viagra) 50MG TAB GU900 Use for 25mg dose only
PHARMACY ORDERABLE ITEM: viagra TAB 04-25-2005 <--- Date is an INACTIVE data. Delete value in 50.7

Select DRUG GENERIC NAME: viag
1 VIAGRA SILDENAFIL (Viagra) 50MG TAB GU900 Use for 25mg dose only
2 VIAGRA SILDENAFIL (Viagra) 100MG TAB GU900 ONLY 4 DOSES PER MONTH ALLOWED
CHOOSE 1-2: 2 SILDENAFIL (Viagra) 100MG TAB GU900 ONLY 4 DOSES PER MONTH ALLOWED
PHARMACY ORDERABLE ITEM: viagra TAB 04-25-2005 <--- Date is an INACTIVE data. Delete value in 50.7

Select DRUG GENERIC NAME:

Select OPTION:

... to be continued later.....

=== Relevent Menu Options ===

Here is a pharmacy option/menu setup I gathered:

ADD Drug Enter/Edit [PSS DRUG ENTER/EDIT]
cv Protocol Conversion Utilities ... [ORCM CONVERSION UTILITIES]
EOI Edit Orderable Items [PSS EDIT ORDERABLE ITEMS]
Mgr Pharmacy Data Management ... [PSS MGR]
NDF National Drug File Menu ... [PSNMGR]
Out Outpatient Pharmacy Manager ... [PSO MANAGER]
xxx Enter/Edit a Drug [PSA DRUG ENTER/EDIT] <--- don't use this one
Drug Accountability Menu ... [PSA DRUG ACCOUNTABILITY MENU]
Drug Receipt History Review [PSA DRUG HISTORY]
Drug Transaction History [PSA DRUG DISPLAY]
Inquire/Compare DRUG file/ITEM MASTER file [PSA DRUG INQUIRE]

----

=== Emails Regarding Adding Drugs ===
Moved here: [[Pharmacy Setup Emails]]

=== Instructions for entering a drug through menus ===
Helpful post here: [[Instructions for New Drug Entry]]

=== RPC Calls ===
ORWUL^FVSUB -- gets the list of drugs to display in the box.

ORWDXA ISACTOI

ORWDPS1 FAILDEA

ORWOR PKISITE

When a drug is selected in the new medicine dialog, the following RPC's are called:

ORWDPS2 OISLCT
example params: 1158,0,1,Y,N

Remote procedure file details for this:
OISLCT^ORWDPS2(LST,OI,PSTYPE,ORVP,NEEDPI,PKIACTIV)

This returns defaults for ordering

Example:
Params ------------------------------------------------------------------
literal 1158
literal O
literal 1
literal Y
literal N

Results -----------------------------------------------------------------
~Medication
d1158^ACYCLOVIR CAP,ORAL
~Verb
dTAKE
~Preposition
dBY
~PtInstr
~AllDoses
i200MG^5671^200&MG&1&CAPSULE&200MG&5671&200&MG
i400MG^5671^400&MG&2&CAPSULES&400MG&5671&200&MG
NOTE: format-- iDrugName^Strength^NF^TDose&Units&U/D&Noun&LDose&Stren^
DoseText^CostText^MaxRefills^DispUnits^CanSplit
~Dosage
iACYCLOVIR 200MG^200MG^^200&MG&1&CAPSULE&200MG&5671&200&MG^200MG^^11^CAP
iACYCLOVIR 200MG^200MG^^400&MG&2&CAPSULES&400MG&5671&200&MG^400MG^^11^CAP
NOTE: format-- iDrugName^Strength^NF^TDose&Units&U/D&Noun&LDose&Stren^
DoseText^CostText^MaxRefills^DispUnits^CanSplit
~Dispense
i5671^200^MG^ACYCLOVIR 200MG^0
NOTE: format-- DrugIEN^Strength^Units^Name^Splict
~Route
i1^ORAL^PO^MOUTH^0
~Schedule
~Guideline
~Message
~DEASchedule
d

Pharmacy Issues

2007-01-11T03:50:08Z

Kdtop3: /* RPC Calls */

This page will contain notes to work out pharmacy programming issues.

Initiated by K. Toppenberg 4/2005

=== Keys Needed for Pharm. Setup ===
We searched pharmacy routines and found keys that were needed for some of the pharmacy setup routines. Here are the keys that were found:
PSA ORDERS, PSAMGR, PSJ RPWARN, PSB MANAGER, PSB CPRS MED BUTTON, PSB INSTRUCTOR, PROVIDER, PSD TECH, PSDMGR, PSD BUMGR, PSD ERROR, PSD PARAM, PSD TRAN

----

=== Files and Relationships ===
*<b>VA PRODUCT</b> file (file #50.68, ^PSNDF(50.68,*)) holds ALL possible drugs. Some people refer to this as the National Drug File. [[File Info: 50dot68]]
*<b>VA GENERIC</b> file (file #50.6, ^PSNDF(50.6))
*<b>DRUG</b> file (file #50, ^PSDRUG(*)) holds all the drugs in the local formulary. This links to above. [[File Info: 50]]
*<b>PHARMACY ORDERABLE ITEM</b> file (file #50.7, ^PS(50.7,*)) holds things that can be ordered from the pharmacy. This links to above. [[File Info 50dot7]]
*<b>ORDERABLE ITEM</b> file (file #101.43, ^ORD(101.43,*)) holds things that can be ordered, including labs and drugs. This links to above. [[File Info 101dot43]]
*<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,*)) holds "quick order" entries. This links to above. [[File Info 101dot44]]

[[Summary of Pharmacy File Linkages]]

What I Have Learned so Far

1. '''File 50.7 (PHARMACY ORDERABLE ITEM):'''
**A record in this file should be created first.
.01 field should be the generic name of the drug.
When the record is created, an entry in fle 101.43 (ORDERABLE ITEM) will automatically be made.
Also, a record in in ORDER QUICK VIEW will also be created (but it is incomplete--see below.)
Note: new drugs may not be added unless PSEDITNM>0. So to setup a drug in fileman,
set PSEDITNM=1 from the command-line, then DO D^DI to get into Fileman with vars intact.
In the MED ROUTE field, the input transform does not allow an input of "ORAL". (If left
blank ORAL will be shown in CPRS)
This file can hold the synonyms of a drug etc.
When this record is created, for some reason it is automatically given the current
date in the INACTIVE DATE field--meaning it is created in an inactive state. One must
go back and edit the record a second time to remove the entry from this field.
File 101.43 (ORDERABLE ITEM), field ID holds a text pointer to this file, e.g.
"10;99PSP" <---- 10 is IEN in file #50.7
There is no pointer field from file 50.7 up to file 50. The link is FROM file #50
TO #50.7 (via file #50's field 2.1(PHARMACY ORDERABLE ITEM)). HOWEVER, File #50's
"ASP" cross-reference for the field "PHARMACY ORDERABLE ITEM (#2.1) i.e.
^PSDRUG("ASP",IEN_in_50.7,*), contains list of linked records in file #50

2. In '''file# 50 (DRUG, ^PSDRUG):'''
This file will hold a separate record for every different medication/tablet size.
For example, there will be one for AMOXICILLIN 250, and another for AMOXICILLIN 500.
Both of the above records would be linked to one record in the PHARMACY ORDERABLE ITEM,
i.e. an AMOXICILLIN record.
The link should be in field 2.1 (the PHARMACY ORDERABLE ITEM field), which will
hold a pointer to file 50.7 (PHARMACY ORDERABLE ITEM file)

3. In '''file 101.43 (ORDERABLE ITEM)''' an entry for the drug must exist like this:
This entry should have been made automatically when the PHARMACY ORDERABLE ITEM was
created.

file 101.43
record: .01 NAME = LISINOPRIL
2 ID = "Unique identifier, created from primary key passed in the
Orderable Items update message from each package; it will be
in the form of 'package code;99XXX' where XXX indicates the
package table originating this item (i.e. RAP,LRT,etc.)
[e.g. in my system, then entry for DILTIAZEM TAB is 1;99PSP]
"Package code" should be the IEN on the PHARMACY ORDERABLE ITEM (#50.7)

4. '''101.44 (ORDER QUICK VIEW)''' For meds to show up in the dialog box in CPRS, it must have a entry like this:
Again, this entry should have been created automatically when the PHARMACY ORDERABLE ITEM
was created. But for some reason, the DISPLAY TEXT field is not filled in. Without this,
the drug will not appear in CPRS. So this must be manually supplied.

file: 101.44 (ORDER QUICK VIEW);
record: ORWDSET O RX;
subfile: SET MEMBER (101.442)
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.
record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here
DISPLAY TEXT: "A name to appear in CPRS appears here.

=== Example of Data===
<pre>
File 101.44 (ORDER QUICK VIEW)
.01-NAME : ORWDSET O RX
6-LAST UPDATE : 60414,61441
20-SET MEMBER :
-snip-
Multiple Entry #15 <--- notice that there are no doses
.01-SET MEMBER : SILDENAFIL TAB <-- pointer to 101.43
2-DISPLAY TEXT : SILDENAFIL TAB
-snip-
Multiple Entry #17 <--- notice that there are no doses
.01-SET MEMBER : SILDENAFIL TAB <-- pointer to 101.43
2-DISPLAY TEXT : VIAGRA <SILDENAFIL TAB>
-snip-
||
||
\/

File 101.43 (ORDERABLE ITEM)
.01-NAME : SILDENAFIL TAB
1-SYNONYMS :
Multiple Entry #1
.01-SYNONYM : VIAGRA
1.1-PACKAGE NAME : SILDENAFIL TAB
2-ID : 4;99PSP <--- pointer to IEN=4 in 50.7
5-DISPLAY GROUP : PHARMACY
9-SET MEMBERSHIP :
Multiple Entry #1
.01-SET : RX
-snip-
||
||
\/

File 50.7 (PHARMACY ORDERABLE ITEM)
.01-NAME : SILDENAFIL
.02-DOSAGE FORM : TAB
.05-DAY (nD) or DOSE (nL) LIMIT : 2L
.07-SCHEDULE TYPE : FILL ON REQUEST
2-SYNONYM :
Multiple Entry #1
.01-SYNONYM : VIAGRA <-- free text
7-PATIENT INSTRUCTIONS : [Do not take with nitroglycerin]
||
||
\/

ASP index in file 50 allows link from 50.7 --> 50
^PSDRUG("ASP",4,7118) = IEN# 4 in 50.7 --> IEN# 7118 in 50
||
||
\/

File 50 (DRUG file) (some noncontributory fields edited)
.001-NUMBER : 7118
.01-GENERIC NAME : SILDENAFIL (Viagra) 50MG TAB
2.1-PHARMACY ORDERABLE ITEM : SILDENAFIL
9-SYNONYM :
Multiple Entry #2
.01-SYNONYM : VIAGRA
1-INTENDED USE : TRADE NAME
14.5-DISPENSE UNIT : TAB
20-NATIONAL DRUG FILE ENTRY : SILDENAFIL
21-VA PRODUCT NAME : SILDENAFIL CITRATE 50MG TAB
22-PSNDF VA PRODUCT NAME ENTRY : SILDENAFIL CITRATE 50MG TAB
101-MESSAGE : Use for 25mg dose only
215-QUANTITY DISPENSE MESSAGE : MAX 4 DOSE/MO-CONTRAINDICATED WITH NITRATES
901-STRENGTH : 50
902-UNIT : MG
903-POSSIBLE DOSAGES :
Multiple Entry #1
.01-DISPENSE UNITS PER DOSE : 1
2-PACKAGE : IO
Multiple Entry #2
.01-DISPENSE UNITS PER DOSE : .5
2-PACKAGE : O
Multiple Entry #3
.01-DISPENSE UNITS PER DOSE : 1
1-DOSE : 50
2-PACKAGE : IO
Multiple Entry #4
.01-DISPENSE UNITS PER DOSE : 2
1-DOSE : 100
2-PACKAGE : IO

</pre>
----

=== Example Entry ===

Here is an example of entering the drug the "proper" way, via menu options:
[[Drug Entry Edit Example]]

Here is a sample inquirery of one successfuly added drug: furosemide
(NOTICE: in this system, there is only 1 orderable drug from CPRS)

OUTPUT FROM WHAT FILE: NEW PERSON// 50.7 PHARMACY ORDERABLE ITEM
(1 entry)
(NOTE: reformatted for easier reading)
Select PHARMACY ORDERABLE ITEM NAME: ?
Answer with PHARMACY ORDERABLE ITEM NAME, or SYNONYM, or OI-DRUG TEXT ENTRY:
FUROSEMIDE FUROSEMIDE TAB

Select PHARMACY ORDERABLE ITEM NAME: furOSEMIDE TAB
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)

NUMBER: 1
NAME: FUROSEMIDE
SYNONYM: LASIX
DOSAGE FORM: TAB

Select PHARMACY ORDERABLE ITEM NAME:

OUTPUT FROM WHAT FILE: 101.43 ORDERABLE ITEMS//
(NOTE: reformatted for easier reading)
Select ORDERABLE ITEMS NAME: furose
1 FUROSEMIDE
2 FUROSEMIDE TAB
CHOOSE 1-2: 1 FUROSEMIDE
ANOTHER ONE: furo
1 FUROSEMIDE
2 FUROSEMIDE TAB
CHOOSE 1-2: 2 FUROSEMIDE TAB
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)

NUMBER: 774
NAME: FUROSEMIDE
ID: 828;99LRT
DISPLAY GROUP: LABORATORY
PACKAGE NAME: FUROSEMIDE
SYNONYM: LASIX
SET: LAB
TYPE: both

NUMBER: 1659
NAME: FUROSEMIDE TAB
ID: 1;99PSP <---- x;99PSP x=IEN in file# 50.7 (PHARMACY ORDERABLE ITEM)
DISPLAY GROUP: PHARMACY
PACKAGE NAME: FUROSEMIDE TAB
SET: RX
SET: UD RX
SET: O RX
INPATIENT MED: YES
OUTPATIENT MED: YES
IV BASE: NO
IV ADDITIVE: NO
SUPPLY: NO
NON-FORMULARY: NO
NON-VA MEDS: NO

Select ORDERABLE ITEMS NAME:

OUTPUT FROM WHAT FILE: 101.44 ORDER QUICK VIEW
(2 entries)
(NOTE: reformatted for easier reading)
Select ORDER QUICK VIEW NAME: ?
Answer with ORDER QUICK VIEW NAME
Choose from:
ORWDQ PKG35 DO
ORWDSET O RX

Select ORDER QUICK VIEW NAME: orwdset O RX
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)

NUMBER: 2
NAME: ORWDSET O RX
LAST UPDATE: 60201,74282
SET MEMBER: FUROSEMIDE TAB
DISPLAY TEXT: FUROSEMIDE TAB

Select ORDER QUICK VIEW NAME:

=== Other Important Pharmacy Files and Relationships ===

=== Steps to Adding One Drug / Making Available in CPRS ===

GTM>set PSEDITNM=1
GTM>D D^DI

VA FileMan 22.0
Select OPTION: enter OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: DRUG// 50.7 PHARMACY ORDERABLE ITEM
(3 entries)
EDIT WHICH FIELD: ALL//

Select PHARMACY ORDERABLE ITEM NAME: VIAGRA
Are you adding 'VIAGRA' as a new PHARMACY ORDERABLE ITEM (the 4TH)? No// Y
(Yes)
PHARMACY ORDERABLE ITEM DOSAGE FORM: tab
1 TAB
2 TAB,BUCC,SA
3 TAB,BUCCAL
4 TAB,CHEWABLE
5 TAB,CHEWG GUM
Press <RETURN> to see more, '^' to exit this list, OR
CHOOSE 1-5: 1 TAB
PHARMACY ORDERABLE ITEM INACTIVE DATE:
DOSAGE FORM: TAB// (No Editing)
IV FLAG:
INACTIVE DATE:
DAY (nD) or DOSE (nL) LIMIT: ??
Type a whole number between 0 and 99, 0 decimal digits, followed by either
a "D" (for NUMBER OF DAYS) or an "L" (for DOSE LIMIT).
DAY (nD) or DOSE (nL) LIMIT: 2L
MED ROUTE:
SCHEDULE TYPE: r FILL ON REQUEST
SCHEDULE:
SUPPLY:
Select SYNONYM: VIAGRA
Are you adding 'VIAGRA' as a new SYNONYM (the 1ST for this PHARMACY ORDERABLE ITEM)? No// Y (Yes)
Select SYNONYM:
Select OI-DRUG TEXT ENTRY:
PATIENT INSTRUCTIONS: [Do not take with nitroglycerin]

[Do not take with nitroglycerin]
OTHER LANGUAGE INSTRUCTIONS:
NON-VA MED:

Select PHARMACY ORDERABLE ITEM NAME:

Select OPTION:

Note: You have to go back and edit the INACTIVE DATE, and delete the value.

------------------------------------------------------------------------------
Now create link from #50, field 2.1 --> 50.7
------------------------------------------------------------------------------
Select OPTION: eNTER OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: DRUG// 50 DRUG (5173 entries)
EDIT WHICH FIELD: ALL// pharmACY ORDERABLE ITEM
THEN EDIT FIELD:

Select DRUG GENERIC NAME: viagra
1 VIAGRA SILDENAFIL (Viagra) 50MG TAB GU900 Use for 25mg dose only
2 VIAGRA SILDENAFIL (Viagra) 100MG TAB GU900 ONLY 4 DOSES PER MONTH ALLOWED
CHOOSE 1-2: 1 SILDENAFIL (Viagra) 50MG TAB GU900 Use for 25mg dose only
PHARMACY ORDERABLE ITEM: viagra TAB 04-25-2005 <--- Date is an INACTIVE data. Delete value in 50.7

Select DRUG GENERIC NAME: viag
1 VIAGRA SILDENAFIL (Viagra) 50MG TAB GU900 Use for 25mg dose only
2 VIAGRA SILDENAFIL (Viagra) 100MG TAB GU900 ONLY 4 DOSES PER MONTH ALLOWED
CHOOSE 1-2: 2 SILDENAFIL (Viagra) 100MG TAB GU900 ONLY 4 DOSES PER MONTH ALLOWED
PHARMACY ORDERABLE ITEM: viagra TAB 04-25-2005 <--- Date is an INACTIVE data. Delete value in 50.7

Select DRUG GENERIC NAME:

Select OPTION:

... to be continued later.....

=== Relevent Menu Options ===

Here is a pharmacy option/menu setup I gathered:

ADD Drug Enter/Edit [PSS DRUG ENTER/EDIT]
cv Protocol Conversion Utilities ... [ORCM CONVERSION UTILITIES]
EOI Edit Orderable Items [PSS EDIT ORDERABLE ITEMS]
Mgr Pharmacy Data Management ... [PSS MGR]
NDF National Drug File Menu ... [PSNMGR]
Out Outpatient Pharmacy Manager ... [PSO MANAGER]
xxx Enter/Edit a Drug [PSA DRUG ENTER/EDIT] <--- don't use this one
Drug Accountability Menu ... [PSA DRUG ACCOUNTABILITY MENU]
Drug Receipt History Review [PSA DRUG HISTORY]
Drug Transaction History [PSA DRUG DISPLAY]
Inquire/Compare DRUG file/ITEM MASTER file [PSA DRUG INQUIRE]

----

=== Emails Regarding Adding Drugs ===
Moved here: [[Pharmacy Setup Emails]]

=== Instructions for entering a drug through menus ===
Helpful post here: [[Instructions for New Drug Entry]]

=== RPC Calls ===
ORWUL^FVSUB -- gets the list of drugs to display in the box.

ORWDXA ISACTOI

ORWDPS1 FAILDEA

ORWOR PKISITE

When a drug is selected in the new medicine dialog, the following RPC's are called:

ORWDPS2 OISLCT
example params: 1158,0,1,Y,N

Remote procedure file details for this:
OISLCT^ORWDPS2(LST,OI,PSTYPE,ORVP,NEEDPI,PKIACTIV)

This returns defaults for ordering

Example:
Params ------------------------------------------------------------------
literal 1158
literal O
literal 1
literal Y
literal N

Results -----------------------------------------------------------------
~Medication
d1158^ACYCLOVIR CAP,ORAL
~Verb
dTAKE
~Preposition
dBY
~PtInstr
~AllDoses
i200MG^5671^200&MG&1&CAPSULE&200MG&5671&200&MG
i400MG^5671^400&MG&2&CAPSULES&400MG&5671&200&MG
~Dosage
iACYCLOVIR 200MG^200MG^^200&MG&1&CAPSULE&200MG&5671&200&MG^200MG^^11^CAP
iACYCLOVIR 200MG^200MG^^400&MG&2&CAPSULES&400MG&5671&200&MG^400MG^^11^CAP
~Dispense
i5671^200^MG^ACYCLOVIR 200MG^0
~Route
i1^ORAL^PO^MOUTH^0
~Schedule
~Guideline
~Message
~DEASchedule
d

TMGTPSTP.m

2005-04-18T22:13:19Z

Kdtop3:

;"------------------------------------------------------------
;"------------------------------------------------------------
;"
;" GT.M STEP TRAP
;"
;" K. Toppenberg
;" 4-13-2005
;" License: GPL Applies
;"
;" This code module will allow tracing through code.
;" It is used as follows:
;"
;" set $ZSTEP="do STEPTRAP^TMGTRSTP($ZPOS) zstep into zcontinue"
;" zstep into
;" do ^MyFunction ;"<--- put the function you want to trace here
;"
;" set $ZSTEP="" ;"<---turn off step capture
;" quit
;"
;"
;" Dependencies:
;" Uses TMGTERM
;"
;"Notes:
;" This function will be called inbetween lines of the main
;" program that is being traced. Thus is function can't do
;" anything that might change the environment of the main
;" program. This includes accessing global variables --
;" because it will mess up the "naked reference".
;"------------------------------------------------------------
;"------------------------------------------------------------

STEPTRAP(Pos)
;"Purpose: This is the line that is called by GT.M for each zstep event.
;" It will be used to display the current code execution point, and
;" query user as to plans for future execution: run/step/ etc.

new tpBlankLine
new tpAction
new tpKeyIn
new tpRunMode,tpStepMode
new tpI
new tpDone
new result set result=1 ;1=step into, 2=step over

;"Run modes: 0=running mode
;" 1=stepping mode
;" 2=Don't show code
;" 3=running SLOW mode
;" -1=quit

set tpRunMode=$get(TMGRunMode,1)
set tpStepMode=$get(TMGStepMode,"into")

new ScrHeight,ScrWidth
set ScrHeight=$get(TMGScrHeight,10)
set ScrWidth=$get(TMGScrWidth,80)

set tpBlankLine=" "
for tpI=1:1:ScrWidth-1 set tpBlankLine=tpBlankLine_" "

do VCUSAV2^TMGTERM
if tpRunMode'=2 do
. do ShowCodePos(Pos,ScrWidth,ScrHeight)
else do
. do CUP^TMGTERM(1,2)
write tpBlankLine,!
write tpBlankLine,!
do CUU^TMGTERM(2)

if (tpRunMode=0)!(tpRunMode=3)!(tpRunMode=2) do
. write tpBlankLine,!
. do CUU^TMGTERM(1)
. write "(Press any key to pause)",!
. read *tpKeyIn:0
. if (tpKeyIn>0) set tpRunMode=1
. else if tpRunMode=3 hang 1

if tpRunMode=2 goto SPDone ;"Don't showmode --> goto SPDone

set tpDone=0
if tpRunMode=1 for do quit:tpDone=1
. new DefAction set DefAction="O"
. do ShowCodePos(Pos,ScrWidth,ScrHeight)
. do CUP^TMGTERM(1,ScrHeight+4) ;"Cursor to line (x,y)
. write tpBlankLine,!
. do CUU^TMGTERM(1)
. write "Action (? for help): "
. if tpStepMode="into" write "step INTO// " set DefAction="I"
. else write "step OVER// " set DefAction="O"
. read tpAction,!
. if tpAction="" set tpAction=DefAction
. if "rR"[tpAction do quit
. . set tpRunMode=0
. . set tpDone=1
. if "lL"[tpAction do quit
. . set tpRunMode=3
. . set tpDone=1
. if "mM"[tpAction do quit
. . write tpBlankLine,!
. . do CUU^TMGTERM(1)
. . new tpLine
. . read " enter M code: ",tpLine,!
. . xecute tpLine
. if "iI"[tpAction do quit
. . set tpStepMode="into"
. . ;"set $ZSTEP="do STEPTRAP^TMGTPSTP($ZPOS) zstep into zcontinue"
. . set tpDone=1
. if "Oo"[tpAction do quit
. . set tpStepMode="over"
. . ;"set $ZSTEP="do STEPTRAP^TMGTPSTP($ZPOS) zstep over zcontinue"
. . set tpDone=1
. if "Hh"[tpAction do quit
. . set tpRunMode=2
. . set tpDone=1
. else do quit
. . new tpNLines
. . for tpNLines=1:1:5 write tpBlankLine,!
. . do CUU^TMGTERM(5)
. . write " L -- run in sLow mode",!
. . write " M -- enter any line of M code",!
. . write " O -- step OVER line",!
. . write " I -- step INTO line",!
. . write " R -- run",!
. . write " H -- Hide debug code",!

SPDone
do VCULOAD2^TMGTERM
set TMGRunMode=tpRunMode
if tpStepMode="into" set result=1
else set result=2
set TMGStepMode=tpStepMode
quit result

ErrTrap(Pos)
;"Purpose: This is the line that is called by GT.M for each ztrap event.
;" It will be used to display the current code execution point

new ScrHeight,ScrWidth
set ScrHeight=$get(TMGScrHeight,10)
set ScrWidth=$get(TMGScrWidth,70)

do VCUSAV2^TMGTERM
do ShowCodePos(Pos,ScrWidth,ScrHeight)

ETDone
do VCULOAD2^TMGTERM
quit

ShowCode(Pos,ScrWidth,ScrHeight,Wipe)
;"Purpose: This will display code at the top of the screen
;"Input: Pos -- string like this: X+2^ROUTINE[$DMOD]
;" ScrWidth -- width of code display (Num of columns)
;
;" Wipe -- OPTIONAL. if 1, then code area is wiped blank

new i
new Routine,Label,Offest,s
new LastRou,LastLabel,LastOffset
new dbFGColor,bBGColor,nlFGColor,nlBGColor
new BlankLine
new StartOffset

set ScrWidth=$get(ScrWidth,80)
set ScrHeight=$get(ScrHeight,10)

set nlFGColor=$get(TMGNlFGColor,3)
set nlBGColor=$get(TMGNlBGColor,0)
set dbFGColor=$get(TMGDbFGColor,0)
set dbBGColor=$get(TMGDbBGColor,3)

set BlankLine=" "
for i=1:1:ScrWidth-1 set BlankLine=BlankLine_" "

do VCOLORS^TMGTERM(dbFGColor,dbBGColor)

do CUP^TMGTERM(1,1) ;"Cursor to line (1,1)
write BlankLine,! ;"This is needed for some reason...
do CUU^TMGTERM(2)

if $get(Wipe)=1 do goto SCDone
. do VCOLORS^TMGTERM(nlFGColor,nlBGColor)
. for i=0:1:ScrHeight+1 write BlankLine

set s=$piece(Pos,"$",1) ;"e.g. X+2^ROUTINE$DMOD-->X+2^ROUTINE
set Routine=$piece(s,"^",2)
set Label=$piece(s,"^",1)
set Offset=+$piece(Label,"+",2)
set Label=$piece(Label,"+",1)

set s="=== Routine: ^"_Routine_" " write s
for i=1:1:ScrWidth-$length(s) write "="
write !

if Offset>(ScrHeight) do
set StartOffset=(Offset-ScrHeight)
else set StartOffset=0

for i=StartOffset:1:(ScrHeight+StartOffset) do
. new line,Bl,ref,LoopOffset
. set ref=Label_"+"_i_"^"_Routine
. set line=$text(@ref)
. if (i=Offset) do
. . do VCOLORS^TMGTERM(nlFGColor,nlBGColor)
. . write ">"
. else write " "
. if $length(line)>(ScrWidth-1) do
. . write $extract(line,1,ScrWidth-4),"...",!
. else do
. . write $extract(line,1,ScrWidth-1)
. . write $extract(BlankLine,1,ScrWidth-$length(line)-1),!
. if (i=Offset) do VCOLORS^TMGTERM(dbFGColor,dbBGColor)

for i=1:1:ScrWidth write "~"
write !

SCDone
;"do VCULOAD^TMGTERM
do VCOLORS^TMGTERM(nlFGColor,nlBGColor)

;"do CUD^TMGTERM(2)

quit

TMGIDE.m

2005-04-18T22:12:34Z

Kdtop3:

TMGIDE.m

2005-04-18T22:09:26Z

Kdtop3:

TMGIDE.m

2005-04-18T22:03:57Z

Kdtop3:

Debugging with GT.M

2005-04-14T22:26:05Z

Kdtop3: /* Simple 'IDE' with GT.M */

=== Simple 'IDE' with GT.M ===

This is a simple (pre pre alpha) IDE created with GT.M debugging commands:

It will currently show the source code, with the current line highlighted, as it steps through the code.

Here are the modules
[[TMGIDE.m]]
[[TMGTERM.m]]
[[TMGTPSTP.m]]

To invoke:
do ^TMGIDE

K. Toppenberg

=== GT.M Debugging commands ===
This information is from the GT.M Programmer's Manual. I'll just summarize a few points.

* $ECODE
This is a list of past errors, separated by commas.
Subsequent errors are added to the end of the list.
Example:
GTM>w $ECODE
,M6,Z150373850,
Errors beginning with: "M" are standard errors
"U" are user errors
"Z" are GT.M errors

* $ZSTATUS
This is detail about the most recent error.
Example:
GTM>w $ZSTATUS
150373850,SubName+3^MyFunct,%GTM-E-UNDEF, Undefined local variable: Jxack

* $ZMESSAGE(x)
This will give a text message for a given error number.
Example: To get details about the error number, 150373850, given above...
GTM>w $ZMESSAGE(150373850)
%GTM-E-UNDEF, Undefined local variable: !AD

* ZPRINT x (e.g. ZPRINT SubName+3^MyFunct)
This will display the line that cause the program exception.
The 'x' may be obtained from $ZSTATUS, or from $ZPOS (see below)

* $ZPOSITION (OR $ZPOS)
Shows the current position of the current line of execution
(or the last line exececuted in case of an error)

* ZWRITE
Shows the entire variable table, displaying all defined variables.

* ZBREAK address
Toggles a break point at address
It is possible to have the breakpoint execute code, and then resume. See manual.

* ZSTEP x
Will execute the program one line at a time. I think this would be typically
used after a ZBREAK drops command back to GT.M> prompt.
ZSTEP INTO -- start execution at current execution point, and stops at
next line (even if that line is in a subroutine).
ZSTEP [OVER] -- start execution at current exec. point, and stop at the
next line at the same level on the invocation stack.
ZSTEP OUTOF -- ??

* ZCONTINUE
Continue execution from break point.

* $STACK AND $ZLEVEL
$STACK starts at 0 and each DO inc's the value, each QUIT dec's it
$ZLEVEL is $STACK+1

.. More later

TMGTERM.m

2005-04-14T22:24:31Z

Kdtop3:

;"--------------------------------------------------------------
;"Terminal interface
;"ANSI Standard (X3.64) Control Sequences for Video Terminals and Peripherals
;" in alphabetic order by mnemonic

EscN(Num,N2,Cmd)
write $char(27,91)_Num
if $data(N2) write ";"_N2
if $data(Cmd) write Cmd
quit

CBT(Pn) ;"CBT Cursor Backward Tab Esc [ Pn Z
do EscN(.Pn,,"Z")
quit

CCH ;"Cancel Previous Character Esc T
write $char(27)_"T"

CHA(Pn) ;"Cursor Horzntal Absolute Esc [ Pn G
do EscN(.Pn,,"G") quit

CHT(Pn) ;"Cursor Horizontal Tab Esc [ Pn I
do EscN(.Pn,,"I") quit

CNL(Pn) ;"Cursor Next Line Esc [ Pn E
do EscN(.Pn,,"E") quit

CPL(Pn) ;"Cursor Preceding Line Esc [ Pn F
do EscN(.Pn,,"F") quit

CPR(Pn,P2) ;"Cursor Position Report Esc [ Pn ; Pn R VT100
do EscN(.Pn,.P2,"R") quit

CTC(Pn) ;"Cursor Tab Control Esc [ Ps W
do EscN(.Pn,,"W") quit

CUB(Pn) ;"Cursor Backward Esc [ Pn D VT100
do EscN(.Pn,,"D") quit

CUD(Pn) ;"Cursor Down Esc [ Pn B VT100
do EscN(.Pn,,"B") quit

CUF(Pn) ;"Cursor Forward Esc [ Pn C VT100
do EscN(.Pn,,"C") quit

CUP(X,Y) ;"Cursor Position Esc [ Pn ; Pn H VT100
do EscN(.Y,.X,"H") quit

HOME ;"Cursor Home Esc [ H
w $char(27,91)_"H" quit

CUU(Pn) ;"Cursor Up Esc [ Pn A VT100
do EscN(.Pn,,"A") quit

CVT(Pn) ;"Cursor Vertical Tab Esc [ Pn Y
do EscN(.Pn,,"Y") quit

DCH(Pn) ;"Delete Character Esc [ Pn P
do EscN(.Pn,,"P") quit

DL(Pn) ;"Delete Line Esc [ Pn M
do EscN(.Pn,,"M") quit

EA(Pn) ;"Erase in Area Esc [ Ps O
do EscN(.Pn,,"O") quit

ECH(Pn) ;"Erase Character Esc [ Pn X
do EscN(.Pn,,"X") quit

ED(Pn) ;"Erase in Display Esc [ Ps J VT100
do EscN(.Pn,,"J") quit

EF(Pn) ;"Erase in Field Esc [ Ps N
do EscN(.Pn,,"N") quit

EL(Pn) ;"Erase in Line Esc [ Ps K VT100
do EscN(.Pn,,"K") quit

EPA ;"End of Protected Area Esc W
w $char(27)_"W" quit

ESA ;"End of Selected Area Esc G
w $char(27)_"G" quit

FNT(Pn,P2) ;"Font Selection Esc [ Pn ; Pn Space D
do EscN(.Pn,P2,"D") quit

GSM(Pn,P2) ;"Graphic Size Modify Esc [ Pn ; Pn Space B
do EscN(.Pn,P2,"B") quit

GSS(Pn) ;"Graphic Size Selection Esc [ Pn Space C
do EscN(.Pn,,"C") quit

HPA(Pn) ;"Horz Position Absolute Esc [ Pn `
do EscN(.Pn,,"`") quit

HPR(Pn) ;"Horz Position Relative Esc [ Pn a
do EscN(.Pn,,"a") quit

HTJ ;"Horz Tab w/Justification Esc I
w $char(27)_"I" quit

HTS ;"Horizontal Tab Set Esc H VT100
w $char(27)_"H" quit

HVP(Pn,P2) ;"Horz & Vertical Position Esc [ Pn ; Pn f VT100
do EscN(.Pn,P2,"A") quit

ICH(Pn) ;"Insert Character Esc [ Pn @
do EscN(.Pn,,"@") quit

IL(Pn) ;"Insert Line Esc [ Pn L
do EscN(.Pn,,"L") quit

IND ;"Index Esc D VT100
w $char(27)_"D" quit

NEL ;"Next Line Esc E VT100
w $char(27)_"E" quit

NP(Pn) ;"Next Page Esc [ Pn U
do EscN(.Pn,,"U") quit

PP(Pn) ;"Preceding Page Esc [ Pn V
do EscN(.Pn,,"V") quit

IS ;"Reset to Initial State Esc c
w $char(27)_"c" quit

RM(Pn) ;"Reset Mode Esc [ Ps l VT100
do EscN(.Pn,,"l") quit

SD(Pn) ;"Scroll Down Esc [ Pn T
do EscN(.Pn,,"T") quit

SL(Pn) ;"Scroll Left Esc [ Pn Space @
do EscN(.Pn,," @") quit

SM(Pn) ;"Select Mode Esc [ Ps h VT100
do EscN(.Pn,,"h") quit

SPA ;"Start of Protected Area Esc V
w $char(27)_"V" quit

SPI(Pn,P2) ;"Spacing Increment Esc [ Pn ; Pn Space G
do EscN(.Pn,P2," G") quit

SR(Pn) ;"Scroll Right Esc [ Pn Space A
do EscN(.Pn,," A") quit

SA ;"Start of Selected Area Esc F
w $char(27)_"F" quit

ST ;"String Terminator Esc \
w $char(27)_"\" quit

SU(Pn) ;"Scroll Up Esc [ Pn S
do EscN(.Pn,,"S") quit

TBC(Pn) ;"Tab Clear Esc [ Ps g VT100
do EscN(.Pn,,"g") quit

VPA(Pn) ;"Vert Position Absolute Esc [ Pn d
do EscN(.Pn,,"d") quit

VPR(Pn) ;"Vert Position Relative Esc [ Pn e
do EscN(.Pn,,"e") quit

VCULOAD ;"Unsave Cursor ESC [ u
w $char(27,91)_"u" quit

VCUSAV2 ;"Save Cursor & Attrs ESC 7
w $char(27)_"7" quit

VCULOAD2 ;"Restore Cursor & Attrs ESC 8
w $char(27)_"8" quit

VTATRIB(n) ;"Set Text attributes <ESC>[{attr1};...;{attrn}m
;"0-Reset all attributes
;"1-Bright
;"2-Dim
;"4-Underscore
;"5-Blink
;"7-Reverse
;"8-Hidden
do EscN(n,,"m") quit

VFGCOLOR(n) ;"Set Text Foreground Color <ESC>[{attr1};...;{attrn}m
set n=n+30
do EscN(n,,"m") quit

;"--------------------------------------------------------------
;"VT100 specific calls
;"Terminal interface

VCEL ;"Erase from cursor to end of line Esc [ 0 K or Esc [ K
do EscN("0",,"K") quit

VCBL ;"Erase from beginning of line to cursor Esc [ 1 K
do EscN("1",,"K") quit

VEL ;"Erase line containing cursor Esc [ 2 K
do EscN("2",,"K") quit

VCES ;"Erase from cursor to end of screen Esc [ 0 J or Esc [ J
do EscN("0",,"J") quit

VCBS ;"Erase from beginning of screen to cursor Esc [ 1 J
do EscN("1",,"J") quit

VCS ;"Erase entire screen Esc [ 2 J
do EscN("2",,"J") quit

VCUSAV ;"Save Cursor ESC [ s
w $char(27,91)_"s" quit

VCULOAD ;"Unsave Cursor ESC [ u
w $char(27,91)_"u" quit

VCUSAV2 ;"Save Cursor & Attrs ESC 7
w $char(27)_"7" quit

VCULOAD2 ;"Restore Cursor & Attrs ESC 8
w $char(27)_"8" quit

VTATRIB(n) ;"Set Text attributes <ESC>[{attr1};...;{attrn}m
;"0-Reset all attributes
;"1-Bright
;"2-Dim
;"4-Underscore
;"5-Blink
;"7-Reverse
;"8-Hidden
do EscN(n,,"m") quit

VFGCOLOR(n) ;"Set Text Foreground Color <ESC>[{attr1};...;{attrn}m
set n=n+30
do EscN(n,,"m") quit

VBGCOLOR(n) ;"Set Text Background Color <ESC>[{attr1};...;{attrn}m
set n=n+40
do EscN(n,,"m") quit

VCOLORS(FG,BG) ;Set Text Colors <ESC>[{attr1};...;{attrn}m
set FG=FG+30
set BG=BG+40
do EscN(FG,BG,"m") quit
quit

SetGlobals
set TMGcBlack=0
set TMGcRed=1
set TMGcGreen=2
set TMGcYellow=3
set TMGcBlue=4
set TMGcMagenta=5
set TMGcCyan=6
set TMGcWhite=7

quit

KillGlobals
kill TMGcBlack
kill TMGcRed
kill TMGcGreen
kill TMGcYellow
kill TMGcBlue
kill TMGcMagenta
kill TMGcCyan
kill TMGcWhite

quit

TMGTERM.m

2005-04-14T22:24:04Z

Kdtop3:

TMGTPSTP.m

2005-04-14T22:15:56Z

Kdtop3:

TMGIDE.m

2005-04-14T22:12:28Z

Kdtop3:

;"------------------------------------------------------------
;"------------------------------------------------------------
;"
;" GT.M Debug Tracer
;"
;" K. Toppenberg
;" 4-13-2005
;" License: GPL Applies
;"
;"
;" This program will launch a shell for the TMG STEP TRAP debugger
;" It provides the user with a prompt, like this:
;"
;" (^ to quit) IDE>
;"
;" Any valid M code may be entered here. To use the tracing
;" ability, launch a function, like this:
;"
;" (^ to quit) IDE>do ^MyFunction
;"
;"
;" Dependancies:
;" Uses TMGTRSTP,TMGTERM
;"
;"------------------------------------------------------------
;"------------------------------------------------------------

Start
new ScrHeight set ScrHeight=10 ;"defined in ShowCode also
new ScrWidth set ScrWidth=70 ;"defined in ShowCode also

set ^TMP("TMGIDE",$J,"ScrWidth")=ScrWidth
set ^TMP("TMGIDE",$J,"ScrHeight")=ScrHeight

do SetGlobals^TMGTERM
set ^TMP("TMGIDE",$J,"Normal Foreground Color")=TMGcYellow
set ^TMP("TMGIDE",$J,"Normal Background Color")=TMGcBlack
set ^TMP("TMGIDE",$J,"Debug Foreground Color")=TMGcBlack
set ^TMP("TMGIDE",$J,"Debug Background Color")=TMGcWhite

;"write # ;"formfeed
;"do CUP^TMGTERM(1,ScrHeight+1)
for i=1:1:80 write !
write !,"Welcome to the TMG debugging environment",!
write "Enter any valid M command...",!
set $ZTRAP="write !,""This is a ZTRAP line"",! break"
set $ZSTATUS=""

;"Run modes: 0=fast mode 1=slow mode 2=Don't show code
set ^TMP("TMGIDE",$J,"Run Mode")=0
new BlankLine set BlankLine=" "
for i=1:1:ScrWidth-1 set BlankLine=BlankLine_" "

do Prompt
Done
do ShutDown
quit

;"-------------------------------------------------------------------

Prompt
new Line
write !,BlankLine,!
do CUU^TMGTERM(1)
read "(^ to quit) IDE>",Line

if Line="^" set $ZSTEP="" quit
set $ZSTEP="do STEPTRAP^TMGTRSTP($ZPOS) zstep into zcontinue"
zstep into
xecute Line
set $ZSTEP="" ;"turn off step capture
goto Prompt

ShutDown
;"do ShowCode("",1)
kill ^TMP("TMGIDE",$J)
do KillGlobals^TMGTERM
quit

TMGIDE.m

2005-04-14T22:11:25Z

Kdtop3:

Debugging with GT.M

2005-04-14T22:09:18Z

Kdtop3: /* Simple 'IDE' with GT.M */

=== Simple 'IDE' with GT.M ===

This is a simple (pre pre alpha) IDE created with GT.M debugging commands:

[[TMGIDE.m]]
[[TMGTERM.m]]
[[TMGTPSTP.m]]

=== GT.M Debugging commands ===
This information is from the GT.M Programmer's Manual. I'll just summarize a few points.

* $ECODE
This is a list of past errors, separated by commas.
Subsequent errors are added to the end of the list.
Example:
GTM>w $ECODE
,M6,Z150373850,
Errors beginning with: "M" are standard errors
"U" are user errors
"Z" are GT.M errors

* $ZSTATUS
This is detail about the most recent error.
Example:
GTM>w $ZSTATUS
150373850,SubName+3^MyFunct,%GTM-E-UNDEF, Undefined local variable: Jxack

* $ZMESSAGE(x)
This will give a text message for a given error number.
Example: To get details about the error number, 150373850, given above...
GTM>w $ZMESSAGE(150373850)
%GTM-E-UNDEF, Undefined local variable: !AD

* ZPRINT x (e.g. ZPRINT SubName+3^MyFunct)
This will display the line that cause the program exception.
The 'x' may be obtained from $ZSTATUS, or from $ZPOS (see below)

* $ZPOSITION (OR $ZPOS)
Shows the current position of the current line of execution
(or the last line exececuted in case of an error)

* ZWRITE
Shows the entire variable table, displaying all defined variables.

* ZBREAK address
Toggles a break point at address
It is possible to have the breakpoint execute code, and then resume. See manual.

* ZSTEP x
Will execute the program one line at a time. I think this would be typically
used after a ZBREAK drops command back to GT.M> prompt.
ZSTEP INTO -- start execution at current execution point, and stops at
next line (even if that line is in a subroutine).
ZSTEP [OVER] -- start execution at current exec. point, and stop at the
next line at the same level on the invocation stack.
ZSTEP OUTOF -- ??

* ZCONTINUE
Continue execution from break point.

* $STACK AND $ZLEVEL
$STACK starts at 0 and each DO inc's the value, each QUIT dec's it
$ZLEVEL is $STACK+1

.. More later

Debugging with GT.M

2005-04-14T22:09:03Z

Kdtop3: /* Simple 'IDE' with GT.M */

=== Simple 'IDE' with GT.M ===

This is a simple (pre pre alpha) IDE created with GT.M debugging commands:

[[TMGIDE.m]]
[TMGTERM.m]]
[[TMGTPSTP.m]]

=== GT.M Debugging commands ===
This information is from the GT.M Programmer's Manual. I'll just summarize a few points.

* $ECODE
This is a list of past errors, separated by commas.
Subsequent errors are added to the end of the list.
Example:
GTM>w $ECODE
,M6,Z150373850,
Errors beginning with: "M" are standard errors
"U" are user errors
"Z" are GT.M errors

* $ZSTATUS
This is detail about the most recent error.
Example:
GTM>w $ZSTATUS
150373850,SubName+3^MyFunct,%GTM-E-UNDEF, Undefined local variable: Jxack

* $ZMESSAGE(x)
This will give a text message for a given error number.
Example: To get details about the error number, 150373850, given above...
GTM>w $ZMESSAGE(150373850)
%GTM-E-UNDEF, Undefined local variable: !AD

* ZPRINT x (e.g. ZPRINT SubName+3^MyFunct)
This will display the line that cause the program exception.
The 'x' may be obtained from $ZSTATUS, or from $ZPOS (see below)

* $ZPOSITION (OR $ZPOS)
Shows the current position of the current line of execution
(or the last line exececuted in case of an error)

* ZWRITE
Shows the entire variable table, displaying all defined variables.

* ZBREAK address
Toggles a break point at address
It is possible to have the breakpoint execute code, and then resume. See manual.

* ZSTEP x
Will execute the program one line at a time. I think this would be typically
used after a ZBREAK drops command back to GT.M> prompt.
ZSTEP INTO -- start execution at current execution point, and stops at
next line (even if that line is in a subroutine).
ZSTEP [OVER] -- start execution at current exec. point, and stop at the
next line at the same level on the invocation stack.
ZSTEP OUTOF -- ??

* ZCONTINUE
Continue execution from break point.

* $STACK AND $ZLEVEL
$STACK starts at 0 and each DO inc's the value, each QUIT dec's it
$ZLEVEL is $STACK+1

.. More later

Debugging with GT.M

2005-04-14T22:07:59Z

Kdtop3: /* Simple 'IDE' with GT.M */

=== Simple 'IDE' with GT.M ===

This is a simple (pre pre alpha) IDE created with GT.M debugging commands:

[[GT.M IDE]]

=== GT.M Debugging commands ===
This information is from the GT.M Programmer's Manual. I'll just summarize a few points.

* $ECODE
This is a list of past errors, separated by commas.
Subsequent errors are added to the end of the list.
Example:
GTM>w $ECODE
,M6,Z150373850,
Errors beginning with: "M" are standard errors
"U" are user errors
"Z" are GT.M errors

* $ZSTATUS
This is detail about the most recent error.
Example:
GTM>w $ZSTATUS
150373850,SubName+3^MyFunct,%GTM-E-UNDEF, Undefined local variable: Jxack

* $ZMESSAGE(x)
This will give a text message for a given error number.
Example: To get details about the error number, 150373850, given above...
GTM>w $ZMESSAGE(150373850)
%GTM-E-UNDEF, Undefined local variable: !AD

* ZPRINT x (e.g. ZPRINT SubName+3^MyFunct)
This will display the line that cause the program exception.
The 'x' may be obtained from $ZSTATUS, or from $ZPOS (see below)

* $ZPOSITION (OR $ZPOS)
Shows the current position of the current line of execution
(or the last line exececuted in case of an error)

* ZWRITE
Shows the entire variable table, displaying all defined variables.

* ZBREAK address
Toggles a break point at address
It is possible to have the breakpoint execute code, and then resume. See manual.

* ZSTEP x
Will execute the program one line at a time. I think this would be typically
used after a ZBREAK drops command back to GT.M> prompt.
ZSTEP INTO -- start execution at current execution point, and stops at
next line (even if that line is in a subroutine).
ZSTEP [OVER] -- start execution at current exec. point, and stop at the
next line at the same level on the invocation stack.
ZSTEP OUTOF -- ??

* ZCONTINUE
Continue execution from break point.

* $STACK AND $ZLEVEL
$STACK starts at 0 and each DO inc's the value, each QUIT dec's it
$ZLEVEL is $STACK+1

.. More later

Debugging with GT.M

2005-04-14T22:07:04Z

Kdtop3:

=== Simple 'IDE' with GT.M ===

[[GT.M IDE]]

=== GT.M Debugging commands ===
This information is from the GT.M Programmer's Manual. I'll just summarize a few points.

* $ECODE
This is a list of past errors, separated by commas.
Subsequent errors are added to the end of the list.
Example:
GTM>w $ECODE
,M6,Z150373850,
Errors beginning with: "M" are standard errors
"U" are user errors
"Z" are GT.M errors

* $ZSTATUS
This is detail about the most recent error.
Example:
GTM>w $ZSTATUS
150373850,SubName+3^MyFunct,%GTM-E-UNDEF, Undefined local variable: Jxack

* $ZMESSAGE(x)
This will give a text message for a given error number.
Example: To get details about the error number, 150373850, given above...
GTM>w $ZMESSAGE(150373850)
%GTM-E-UNDEF, Undefined local variable: !AD

* ZPRINT x (e.g. ZPRINT SubName+3^MyFunct)
This will display the line that cause the program exception.
The 'x' may be obtained from $ZSTATUS, or from $ZPOS (see below)

* $ZPOSITION (OR $ZPOS)
Shows the current position of the current line of execution
(or the last line exececuted in case of an error)

* ZWRITE
Shows the entire variable table, displaying all defined variables.

* ZBREAK address
Toggles a break point at address
It is possible to have the breakpoint execute code, and then resume. See manual.

* ZSTEP x
Will execute the program one line at a time. I think this would be typically
used after a ZBREAK drops command back to GT.M> prompt.
ZSTEP INTO -- start execution at current execution point, and stops at
next line (even if that line is in a subroutine).
ZSTEP [OVER] -- start execution at current exec. point, and stop at the
next line at the same level on the invocation stack.
ZSTEP OUTOF -- ??

* ZCONTINUE
Continue execution from break point.

* $STACK AND $ZLEVEL
$STACK starts at 0 and each DO inc's the value, each QUIT dec's it
$ZLEVEL is $STACK+1

.. More later