Pharmacy Issues - Revision history

DavidWhitten: /* Files and Relationships */

2013-02-20T16:25:56Z

Files and Relationships

← Older revision		Revision as of 16:25, 20 February 2013
Line 14:		Line 14:
	<b>DRUG</b> file (file #50, ^PSDRUG()) holds all the drugs in the local formulary. This links to above. [[FILE 50]]		<b>DRUG</b> file (file #50, ^PSDRUG()) holds all the drugs in the local formulary. This links to above. [[FILE 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 50.7]]		<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 50.7]]
	<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>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 101.43]]
	<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,)) holds "quick order" entries. This links to above. [[FILE 101.44]]		<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,)) holds "quick order" entries. This links to above. [[FILE 101.44]]
	<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[FILE 52.41]]		<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[FILE 52.41]]

DavidWhitten: /* Keys Needed for Pharm. Setup */

2013-02-20T16:03:54Z

Keys Needed for Pharm. Setup

← Older revision		Revision as of 16:03, 20 February 2013
Line 5:		Line 5:
	=== Keys Needed for Pharm. Setup ===		=== 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:		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~\|CPRS]] ~~MED BUTTON~~, PSB INSTRUCTOR, PROVIDER, PSD TECH, PSDMGR, PSD BUMGR, PSD ERROR, PSD PARAM, PSD TRAN		[[SECURITY KEY PSA ORDERS\|PSA ORDERS]], [[SECURITY KEY PSAMGR\|PSAMGR]], [[SECURITY KEY PSJ RPWARN\|PSJ RPWARN]], [[SECURITY KEY PSB MANAGER\|PSB MANAGER]], [[SECURITY KEY PSB CPRS MED BUTTON\|PSB CPRS MED BUTTON]], [[SECURITY KEY PSB INSTRUCTOR\|PSB INSTRUCTOR]], [[SECURITY KEY PROVIDER\|PROVIDER]], [[SECURITY KEY PSD TECH\|PSD TECH]], [[SECURITY KEY PSDMGR\|PSDMGR]], [[SECURITY KEY PSD BUMGR\|PSD BUMGR]], [[SECURITY KEY PSD ERROR\|PSD ERROR]], [[SECURITY KEY PSD PARAM\|PSD PARAM]], [[SECURITY KEY PSD TRAN\|PSD TRAN]]

	----		----

DavidWhitten at 16:00, 20 February 2013

2013-02-20T16:00:36Z

← Older revision		Revision as of 16:00, 20 February 2013
Line 10:		Line 10:

	=== Files and Relationships ===		=== 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 PRODUCT</b> file (file #50.68, ^PSNDF(50.68,)) holds ALL possible drugs. Some people refer to this as the National Drug File. [[FILE 50.68]]
	*<b>VA GENERIC</b> file (file #50.6, ^PSNDF(50.6))		*<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>DRUG</b> file (file #50, ^PSDRUG()) holds all the drugs in the local formulary. This links to above. [[FILE 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>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 50.7]]
	<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>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~~]]		<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,)) holds "quick order" entries. This links to above. [[FILE 101.44]]
	<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[~~File Info 52dot41~~]]		<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[FILE 52.41]]
	<b>PRESCRIPTION FILE</b> file (file #52, ^PSRX()) holds prescriptions [[~~File Info~~ 52]]		<b>PRESCRIPTION FILE</b> file (file #52, ^PSRX()) holds prescriptions [[FILE 52]]

	[[Summary of Pharmacy File Linkages]]		[[Summary of Pharmacy File Linkages]]

DavidWhitten at 15:54, 20 February 2013

2013-02-20T15:54:13Z

← Older revision		Revision as of 15:54, 20 February 2013
Line 500:		Line 500:
	Select New Rx # for TEST,KEVIN:		Select New Rx # for TEST,KEVIN:

	''Initially I had a problem, but then got this working, after fixing a bug in my version of the PSO code. I kept getting a crash at ACP+6^PSOORNEW when I would enter a prescription number. I stepped through it and found that PSONEW("QFLG") was not being set, which then caused a "variable-doesn't-exist" error. I wrapped this in a $G() and the code was able to continue and complete the prescription. ... Another problem was that I didn't have the setting correct regarding automatically numbering prescriptions. I needed to set that ~~the~~ YES, and then give an upper and lower range and a last-prescribed value into a fields 27000...''		''Initially I had a problem, but then got this working, after fixing a bug in my version of the PSO code. I kept getting a crash at ACP+6^PSOORNEW when I would enter a prescription number. I stepped through it and found that PSONEW("QFLG") was not being set, which then caused a "variable-doesn't-exist" error. I wrapped this in a $G() and the code was able to continue and complete the prescription. ... Another problem was that I didn't have the setting correct regarding automatically numbering prescriptions. I needed to set that to "YES", and then give an upper and lower range and a last-prescribed value into a fields 27000...''

	Tracing through the code, I find the following stack (order of execution) (earliest calls on the bottom) when I break at the first [[prompt~\|Prompt]] after launching a FN finish.		Tracing through the code, I find the following stack (order of execution) (earliest calls on the bottom) when I break at the first [[prompt~\|Prompt]] after launching a FN finish.
Line 506:		Line 506:
	EN^PSON52 <-- create new entry in prescription file		EN^PSON52 <-- create new entry in prescription file
	ACP+10^PSOORNEW <-- Module: display orders from oerr		ACP+10^PSOORNEW <-- Module: display orders from oerr
	LOOP+6^XQOR1 <-- ~~listman~~ code		LOOP+6^XQOR1 <-- [[Kernel Unwinder]] code
	STAK+3^XQOR1 <-- ~~listman~~ code		STAK+3^XQOR1 <-- [[Kernel Unwinder]] code
	ASK+1^VALM <-- ~~listman~~ code		ASK+1^VALM <-- [[ListMan]] code
	EN+8^VALM <-- ~~listman~~ code		EN+8^VALM <-- [[ListMan]] code
	EN+1^PSOLMPO <-- starts ~~listman~~ session to allow FN to be chosen		EN+1^PSOLMPO <-- starts [[ListMan]] session to allow FN to be chosen
	PST+42^PSOORFI1 <-- shows order		PST+42^PSOORFI1 <-- shows order
	ORD+14^PSOORFIN <-- Module: finish [[cprs~\|CPRS]] orders		ORD+14^PSOORFIN <-- Module: finish [[cprs~\|CPRS]] orders

NeilArmstrong: Added a glossary link to CPRS~

2012-08-10T01:05:59Z

Added a glossary link to CPRS~

← Older revision		Revision as of 01:05, 10 August 2012
Line 5:		Line 5:
	=== Keys Needed for Pharm. Setup ===		=== 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:		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		PSA ORDERS, PSAMGR, PSJ RPWARN, PSB MANAGER, PSB [[CPRS~\|CPRS]] MED BUTTON, PSB INSTRUCTOR, PROVIDER, PSD TECH, PSDMGR, PSD BUMGR, PSD ERROR, PSD PARAM, PSD TRAN

	----		----
Line 31:		Line 31:
	set PSEDITNM=1 from the command-line, then DO D^DI to get into Fileman with vars intact.		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		In the MED ROUTE field, the input transform does not allow an input of "ORAL". (If left
	blank ORAL will be shown in CPRS)		blank ORAL will be shown in [[CPRS~\|CPRS]])
	This file can hold the synonyms of a drug etc.		This file can hold the synonyms of a drug etc.
	When this [[record~\|Record]] is created, for some reason it is automatically given the current		When this [[record~\|Record]] is created, for some reason it is automatically given the current
Line 65:		Line 65:
	"Package code" should be the IEN on the PHARMACY ORDERABLE ITEM (#50.7)		"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:		4. '''101.44 (ORDER QUICK VIEW)''' For meds to show up in the dialog box in [[CPRS~\|CPRS]], it must have a entry like this:
	Again, this entry should have been created automatically when the PHARMACY ORDERABLE ITEM		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,		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.		the drug will not appear in [[CPRS~\|CPRS]]. So this must be manually supplied.

	file: 101.44 (ORDER QUICK VIEW);		file: 101.44 (ORDER QUICK VIEW);
Line 74:		Line 74:
	subfile: SET MEMBER (101.442)		subfile: SET MEMBER (101.442)
	[[record~\|Record]]: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here		[[record~\|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.		DISPLAY TEXT: "A name to appear in [[CPRS~\|CPRS]] appears here.
	[[record~\|Record]]: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here		[[record~\|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.		DISPLAY TEXT: "A name to appear in [[CPRS~\|CPRS]] appears here.
	[[record~\|Record]]: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here		[[record~\|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.		DISPLAY TEXT: "A name to appear in [[CPRS~\|CPRS]] appears here.
	[[record~\|Record]]: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here		[[record~\|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.		DISPLAY TEXT: "A name to appear in [[CPRS~\|CPRS]] appears here.

	=== Example of Data===		=== Example of Data===
Line 178:		Line 178:

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


Line 270:		Line 270:


	=== Steps to Adding One Drug / Making Available in CPRS ===		=== Steps to Adding One Drug / Making Available in [[CPRS~\|CPRS]] ===

	GTM>set PSEDITNM=1		GTM>set PSEDITNM=1
Line 430:		Line 430:
	d		d

	=== Completion of CPRS drug orders ===		=== Completion of [[CPRS~\|CPRS] drug orders ===
	The menu option for completing a medication order entered in CPRS is PSO LMOE FINISH		The menu option for completing a medication order entered in [[CPRS~\|CPRS]] is PSO LMOE FINISH

	This menu option causes execution of code: DO ^PSOORFIN		This menu option causes execution of code: DO ^PSOORFIN
Line 441:		Line 441:
	-------older stuff below------------		-------older stuff below------------

	This is a debug trace. First, I entered a drug in CPRS, but didn't sign it....		This is a debug trace. First, I entered a drug in [[CPRS~\|CPRS]], but didn't sign it....

	CPRS gets name of drug order (unsigned) via		[[CPRS~\|CPRS]] gets name of drug order (unsigned) via

	ORWORR GETTXT		ORWORR GETTXT
Line 462:		Line 462:
	...		...

	I then signed the order in CPRS. It is now displayed on the medications tab. Here is the RPC that got that:		I then signed the order in [[CPRS~\|CPRS]]. It is now displayed on the medications tab. Here is the RPC that got that:

	ORWPS ACTIVE		ORWPS ACTIVE
Line 472:		Line 472:


	After a drug is entered in CPRS, it is put into:		After a drug is entered in [[CPRS~\|CPRS]], it is put into:
	file 52.41 - PENDING OUTPATIENT ORDERS		file 52.41 - PENDING OUTPATIENT ORDERS

Line 483:		Line 483:
	From there I am taken into a screenman form where I can view and		From there I am taken into a screenman form where I can view and
	update the patient information. I press ENTER twice, and then I am		update the patient information. I press ENTER twice, and then I am
	shown the prescription that is pending (i.e. signed in CPRS).		shown the prescription that is pending (i.e. signed in [[CPRS~\|CPRS]]).

	I am able to edit the prescription. And then I enter FN to finish the		I am able to edit the prescription. And then I enter FN to finish the
Line 512:		Line 512:
	EN+1^PSOLMPO <-- starts listman session to allow FN to be chosen		EN+1^PSOLMPO <-- starts listman session to allow FN to be chosen
	PST+42^PSOORFI1 <-- shows order		PST+42^PSOORFI1 <-- shows order
	ORD+14^PSOORFIN <-- Module: finish cprs orders		ORD+14^PSOORFIN <-- Module: finish [[cprs~\|CPRS]] orders
	OK^PSOORNE5		OK^PSOORNE5
	NEWSEL+2^PSOORNE2		NEWSEL+2^PSOORNE2
Line 612:		Line 612:
	After the drug is completed in the Terminal, it is removed from File 52.41 holds PENDING OUTPATIENT ORDERS.		After the drug is completed in the Terminal, it is removed from File 52.41 holds PENDING OUTPATIENT ORDERS.

	However, from CPRS, it is still the same RPC call [ORWPS ACTIVE] that gets the list of active medications--both those Pending (await terminal-mode completion, meaning that they are in the PENDING OUTPATIENT ORDERS) and those that are completed.		However, from [[CPRS~\|CPRS]], it is still the same RPC call [ORWPS ACTIVE] that gets the list of active medications--both those Pending (await terminal-mode completion, meaning that they are in the PENDING OUTPATIENT ORDERS) and those that are completed.

	=== Prescription Auto-Finishing ===		=== Prescription Auto-Finishing ===

NeilArmstrong: Added glossary link to Record~

2012-03-10T21:31:27Z

Added glossary link to Record~

NeilArmstrong: Added glossary link to Prompt~

2012-03-05T02:37:35Z

Added glossary link to Prompt~

← Older revision		Revision as of 02:37, 5 March 2012
Line 502:		Line 502:
	''Initially I had a problem, but then got this working, after fixing a bug in my version of the PSO code. I kept getting a crash at ACP+6^PSOORNEW when I would enter a prescription number. I stepped through it and found that PSONEW("QFLG") was not being set, which then caused a "variable-doesn't-exist" error. I wrapped this in a $G() and the code was able to continue and complete the prescription. ... Another problem was that I didn't have the setting correct regarding automatically numbering prescriptions. I needed to set that the YES, and then give an upper and lower range and a last-prescribed value into a fields 27000...''		''Initially I had a problem, but then got this working, after fixing a bug in my version of the PSO code. I kept getting a crash at ACP+6^PSOORNEW when I would enter a prescription number. I stepped through it and found that PSONEW("QFLG") was not being set, which then caused a "variable-doesn't-exist" error. I wrapped this in a $G() and the code was able to continue and complete the prescription. ... Another problem was that I didn't have the setting correct regarding automatically numbering prescriptions. I needed to set that the YES, and then give an upper and lower range and a last-prescribed value into a fields 27000...''

	Tracing through the code, I find the following stack (order of execution) (earliest calls on the bottom) when I break at the first prompt after launching a FN finish.		Tracing through the code, I find the following stack (order of execution) (earliest calls on the bottom) when I break at the first [[prompt~\|Prompt]] after launching a FN finish.

	EN^PSON52 <-- create new entry in prescription file		EN^PSON52 <-- create new entry in prescription file

Kdtop: /* Prescription Auto-Finishing */

2009-04-27T23:10:18Z

Prescription Auto-Finishing

Show changes

Kdtop: /* Prescription Auto-Finishing */

2009-04-27T23:08:01Z

Prescription Auto-Finishing

← Older revision		Revision as of 23:08, 27 April 2009
Line 618:		Line 618:
	This section got too long. So moved to a separate page.		This section got too long. So moved to a separate page.

	[Prescription Auto-Finishing]		[[Prescription Auto-Finishing]]

	This section will hold information as I investigate the HUI autoprescription code that I was given at one point. I will note that this was beta code, and there are likely better versions now.		This section will hold information as I investigate the HUI autoprescription code that I was given at one point. I will note that this was beta code, and there are likely better versions now.

Kdtop: /* Prescription Auto-Finishing */

2009-04-27T23:06:48Z

Prescription Auto-Finishing

← Older revision		Revision as of 23:06, 27 April 2009
Line 616:		Line 616:
	=== Prescription Auto-Finishing ===		=== Prescription Auto-Finishing ===

	[[Prescription Auto-Finishing]]		This section got too long. So moved to a separate page.

			[Prescription Auto-Finishing]

	This section will hold information as I investigate the HUI autoprescription code that I was given at one point. I will note that this was beta code, and there are likely better versions now.		This section will hold information as I investigate the HUI autoprescription code that I was given at one point. I will note that this was beta code, and there are likely better versions now.

← Older revision		Revision as of 16:25, 20 February 2013
Line 14:		Line 14:
	<b>DRUG</b> file (file #50, ^PSDRUG()) holds all the drugs in the local formulary. This links to above. [[FILE 50]]		<b>DRUG</b> file (file #50, ^PSDRUG()) holds all the drugs in the local formulary. This links to above. [[FILE 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 50.7]]		<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 50.7]]
	<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>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 101.43]]
	<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,)) holds "quick order" entries. This links to above. [[FILE 101.44]]		<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,)) holds "quick order" entries. This links to above. [[FILE 101.44]]
	<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[FILE 52.41]]		<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[FILE 52.41]]

← Older revision		Revision as of 16:00, 20 February 2013
Line 10:		Line 10:

	=== Files and Relationships ===		=== 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 PRODUCT</b> file (file #50.68, ^PSNDF(50.68,)) holds ALL possible drugs. Some people refer to this as the National Drug File. [[FILE 50.68]]
	*<b>VA GENERIC</b> file (file #50.6, ^PSNDF(50.6))		*<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>DRUG</b> file (file #50, ^PSDRUG()) holds all the drugs in the local formulary. This links to above. [[FILE 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>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 50.7]]
	<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>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~~]]		<b>ORDER QUICK VIEW</b> file (file #101.44, ^ORD(101.44,)) holds "quick order" entries. This links to above. [[FILE 101.44]]
	<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[~~File Info 52dot41~~]]		<b>PENDING OUTPATIENT ORDERS</b> file (file #52.41, ^PS(52.41,)) holds prescription requests entries, to be approved by pharmacist [[FILE 52.41]]
	<b>PRESCRIPTION FILE</b> file (file #52, ^PSRX()) holds prescriptions [[~~File Info~~ 52]]		<b>PRESCRIPTION FILE</b> file (file #52, ^PSRX()) holds prescriptions [[FILE 52]]

	[[Summary of Pharmacy File Linkages]]		[[Summary of Pharmacy File Linkages]]

← Older revision		Revision as of 21:31, 10 March 2012
Line 24:		Line 24:

	1. '''File 50.7 (PHARMACY ORDERABLE ITEM):'''		1. '''File 50.7 (PHARMACY ORDERABLE ITEM):'''
	**A record in this file should be created first.		**A [[record~\|Record]] in this file should be created first.
	.01 field should be the generic name of the drug.		.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.		When the [[record~\|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.)		Also, a [[record~\|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,		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.		set PSEDITNM=1 from the command-line, then DO D^DI to get into Fileman with vars intact.
Line 33:		Line 33:
	blank ORAL will be shown in CPRS)		blank ORAL will be shown in CPRS)
	This file can hold the synonyms of a drug etc.		This file can hold the synonyms of a drug etc.
	When this record is created, for some reason it is automatically given the current		When this [[record~\|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		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.		go back and edit the [[record~\|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.		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		"10;99PSP" <---- 10 is IEN in file #50.7
Line 41:		Line 41:
	TO #50.7 (via file #50's field 2.1(PHARMACY ORDERABLE ITEM)). HOWEVER, File #50's		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.		"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		^PSDRUG("ASP",IEN_in_50.7,*), contains list of linked [[record~\|Record]]s in file #50


	2. In '''file# 50 (DRUG, ^PSDRUG):'''		2. In '''file# 50 (DRUG, ^PSDRUG):'''
	This file will hold a separate record for every different medication/tablet size.		This file will hold a separate [[record~\|Record]] for every different medication/tablet size.
	For example, there will be one for AMOXICILLIN 250, and another for AMOXICILLIN 500.		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,		Both of the above [[record~\|Record]]s would be linked to one [[record~\|Record]] in the PHARMACY ORDERABLE ITEM,
	i.e. an AMOXICILLIN record.		i.e. an AMOXICILLIN [[record~\|Record]].
	The link should be in field 2.1 (the PHARMACY ORDERABLE ITEM field), which will		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)		hold a pointer to file 50.7 (PHARMACY ORDERABLE ITEM file)
Line 57:		Line 57:

	file 101.43		file 101.43
	record: .01 NAME = LISINOPRIL		[[record~\|Record]]: .01 NAME = LISINOPRIL
	2 ID = "Unique identifier, created from primary key passed in the		2 ID = "Unique identifier, created from primary key passed in the
	Orderable Items update message from each package; it will be		Orderable Items update message from each package; it will be
Line 71:		Line 71:

	file: 101.44 (ORDER QUICK VIEW);		file: 101.44 (ORDER QUICK VIEW);
	record: ORWDSET O RX;		[[record~\|Record]]: ORWDSET O RX;
	subfile: SET MEMBER (101.442)		subfile: SET MEMBER (101.442)
	record: SET MEMBER: _IEN_ pointer to 101.43 (ORDERABLE ITEM) ... a drug would go here		[[record~\|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.		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		[[record~\|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.		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		[[record~\|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.		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		[[record~\|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.		DISPLAY TEXT: "A name to appear in CPRS appears here.

Line 191:		Line 191:
	ANOTHER ONE:		ANOTHER ONE:
	STANDARD CAPTIONED OUTPUT? Yes// (Yes)		STANDARD CAPTIONED OUTPUT? Yes// (Yes)
	Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)		Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and [[Record~\|Record]] Number (IEN)

	NUMBER: 1		NUMBER: 1
Line 213:		Line 213:
	ANOTHER ONE:		ANOTHER ONE:
	STANDARD CAPTIONED OUTPUT? Yes// (Yes)		STANDARD CAPTIONED OUTPUT? Yes// (Yes)
	Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)		Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and [[Record~\|Record]] Number (IEN)

	NUMBER: 774		NUMBER: 774
Line 257:		Line 257:
	ANOTHER ONE:		ANOTHER ONE:
	STANDARD CAPTIONED OUTPUT? Yes// (Yes)		STANDARD CAPTIONED OUTPUT? Yes// (Yes)
	Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Number (IEN)		Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and [[Record~\|Record]] Number (IEN)

	NUMBER: 2		NUMBER: 2