KIDS Drug File - Revision history

Shabiel: /* Deliverables */

2012-05-16T22:37:19Z

Deliverables

← Older revision		Revision as of 22:37, 16 May 2012
Line 26:		Line 26:
	* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/vw_drug_file_source_ic_0100.kids.tgz Example Drug File Source IC]		* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/vw_drug_file_source_ic_0100.kids.tgz Example Drug File Source IC]
	* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/vw_drug_file_source_w.kids.tgz Example Drug File Source W]		* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/vw_drug_file_source_w.kids.tgz Example Drug File Source W]
			* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/trunk/vw_drug_file_source_hakeem_0100-clean.kid.tgz Example Drug File Source H]
	* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/README.txt README]		* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/README.txt README]

2012-04-18T19:33:31Z

Administration Schedules

← Older revision		Revision as of 19:33, 18 April 2012
Line 314:		Line 314:
	</pre>		</pre>

	To edit Administration Schedules, ~~use the menu option under menu~~ Pharmacy Data Management ~~<code>~~[PSS MGR]~~</code~~>: Standard Schedule Management ... ~~<code>~~[PSS SCHEDULE MANAGEMENT]~~</code>.~~		To edit Administration Schedules, nagivate to XUCORE > Pharmacy Data Management [PSS MGR] > Standard Schedule Management ... [PSS SCHEDULE MANAGEMENT]

	== Remarks on Broken Pointers ==		== Remarks on Broken Pointers ==

2012-04-18T19:31:39Z

Limitations

@@ Line 208: / Line 208: @@
 == Limitations ==
-* If the Administration Schedules from the originating system and destination system don't match, you need to either change the schedules on the orderable items, or make the schedules on the destination system the same as the ones from incoming drug file, otherwise, the problems you run into is this:
+* If the Administration Schedules from the originating system and destination system don't match, you need to either change the schedules on the orderable items, or make the schedules on the destination system the same as the ones from incoming drug file, otherwise, the problems you run into is this (see below for how to investigate the issue):
 ** Orders do not calculate frequency correctly if the schedule is not present in the destination system. This means that the proper number of pills cannot be calculated.
 ** In Outpatient Pharmacy, Schedules do not expand into patient readable instructions
@@ Line 217: / Line 217: @@
 ** CLOZAPINE LAB TEST:LAB TEST MONITOR field
 ** CLOZAPINE LAB TEST:SPECIMEN TYPE field
 == Remarks on Broken Pointers ==

2012-04-18T19:22:02Z

Limitations

← Older revision		Revision as of 19:22, 18 April 2012
Line 213:		Line 213:
	* If the National Drug Files are not up to date in the destination system, there will be some broken pointers. All you have to do is update the NDF with the latest patches.		* If the National Drug Files are not up to date in the destination system, there will be some broken pointers. All you have to do is update the NDF with the latest patches.
	* If some drugs are linked with lab tests, these need to be re-linked. Preferably, these should be removed prior to transporting the drug file. You can print the Lab-related fields on the Drug File to see if there is data. The fields are:		* If some drugs are linked with lab tests, these need to be re-linked. Preferably, these should be removed prior to transporting the drug file. You can print the Lab-related fields on the Drug File to see if there is data. The fields are:
			** LAB TEST MONITOR field.
			** SPECIMEN TYPE field.
			** CLOZAPINE LAB TEST:LAB TEST MONITOR field
			** CLOZAPINE LAB TEST:SPECIMEN TYPE field

	== Remarks on Broken Pointers ==		== Remarks on Broken Pointers ==

2012-04-18T19:20:51Z

Limitations

← Older revision		Revision as of 19:20, 18 April 2012
Line 212:		Line 212:
	** In Outpatient Pharmacy, Schedules do not expand into patient readable instructions		** In Outpatient Pharmacy, Schedules do not expand into patient readable instructions
	* If the National Drug Files are not up to date in the destination system, there will be some broken pointers. All you have to do is update the NDF with the latest patches.		* If the National Drug Files are not up to date in the destination system, there will be some broken pointers. All you have to do is update the NDF with the latest patches.
	* If some drugs are linked with lab tests, these need to be re-linked. Preferably, these should be removed prior to transporting the drug file.		* If some drugs are linked with lab tests, these need to be re-linked. Preferably, these should be removed prior to transporting the drug file. You can print the Lab-related fields on the Drug File to see if there is data. The fields are:

	== Remarks on Broken Pointers ==		== Remarks on Broken Pointers ==

2012-04-18T19:14:47Z

Remarks on Broken Pointers

← Older revision		Revision as of 19:14, 18 April 2012
Line 234:		Line 234:
	** MEDICATION ROUTES (additions are allowed, not deletions)		** MEDICATION ROUTES (additions are allowed, not deletions)

	The National Drug Files are Standardized. However, a system may be out of date. If you do not have the latest National Drug Files, you have will broken pointers if the source of your drug files has a more recent National Drug File. For best results, the source system and the destination system should ~~have a commensurate NDF~~ patch level.		The National Drug Files are Standardized. However, a system may be out of date. If you do not have the latest National Drug Files, you have will broken pointers if the source of your drug files has a more recent National Drug File. For best results, the source system and the destination system should be patched up to the latest patch level.

	To check for broken pointers, use the VERIFY FIELDs option in Fileman.		To check for broken pointers, use the VERIFY FIELDs option in Fileman.

2012-04-18T19:14:02Z

How to use?

← Older revision		Revision as of 19:14, 18 April 2012
Line 42:		Line 42:
	On the Origin System:		On the Origin System:
	* Create a KIDS build that calls the following:		* Create a KIDS build that calls the following:
	# ~~This~~ Routine ~~Name~~ to call from top is the Environment Check for the Build		# Routine VWPSSXPD to call from top is the Environment Check for the Build
	# PRE is the Pre-Init for the Destination System		# PRE^VWPSSXPD is the Pre-Init for the Destination System
	# POST is the Post-Init for the Destination System		# POST^VWPSSXPD is the Post-Init for the Destination System
	# TRAN is the Pre-Transport Routine for your originating system drug data		# TRAN^VWPSSXPD is the Pre-Transport Routine for your originating system drug data
	* Generate the KIDS Build. The file will have all the Drug Data from the Origin System.		* Generate the KIDS Build. The file will have all the Drug Data from the Origin System.

2012-04-17T17:37:41Z

2012-04-17T16:56:37Z

← Older revision		Revision as of 16:56, 17 April 2012
Line 28:		Line 28:
	* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/README.txt README]		* [https://trac.opensourcevista.net/svn/pharmacy-utils/drug-file-cleanup/tag/20120417/README.txt README]

	== ~~Example of KIDS file~~ ==		== How to use? ==
			{\|
			\|style="background:red; color:white; font-weight: bold" \| WARNING
			\|}

2012-04-17T16:50:17Z

Solution

@@ Line 9: / Line 9: @@
 == Solution ==
 A MUMPS routine was written to work with KIDS to distribute a drug file for installation on new systems. In addition, drug files were extracted and placed into an open office spreadsheet for comparison.
 == Deliverables ==