VistApedia - User contributions [en]

User:DavidWhitten

2015-10-22T07:50:55Z

NeilArmstrong:

'''David Whitten''' is one of the founders of WorldVistA. A longtime VA employee, he has been using MUMPS since 1981 in many different enviroments.
These include in the Department of Veterans Affairs, at MD Anderson Cancer Center with the Protocol Data Management System, as a contractor to the Department of Defense (CHCS) and using standalone FileMan projects.

He is one of the administrators of the VistApedia Wiki, and may be reached by telephone at 713-870-3834.

Here is a useful link to Recent Changes that gives you a LOT of info about what has changed recently on the wiki :

http://www.vistapedia.net/index.php?title=Special:Recentchanges&hideminor=0&hideliu=0&hidebots=0&limit=1500&days=150&limit=1500

[[Category:HomePage]]

Hello David, at long last I've put my HP laptop back to perfect working order again. A friend ordered the cables I needed and I did the

labor and apparently I did a good job as everything is in perfect working order now. I would like it very much to start earning a living

again, I hate handouts and will do my best to do all I can and am able to for you as you have done for me. Thanks for being my friend

and also being as patient and understanding as you are. The Hospitals aren't doing much even after going through hoops to get the required

paperwork. what a nightmare this has turned out to be for me and my life too. I am in such bad shape that by the time they finally do the

procedures it may just kill me. The lawyer decided that I'm also needing to get on treatment of some kind to help them win my case. Since

when do people who obviously have a real need for SSDI need to to start taking meds. that aren't guaranteed to help and may speed up the

process of my illness just so a lawyer can make an easy 7000 dollars. I;m about to tell them to fly a kite. I have made it this long

without government cheese and I believe that I can make it longer without it too. I'm probably doing in my heart what is right but to

others may seem foolish or stupid. I believe that its also my life so It's my choice alone that really matters and not what others may

seem is wrong. Call me when you get this message please. Thanks David, Bye for now......

User:DavidWhitten

2015-10-22T07:48:14Z

NeilArmstrong:

'''David Whitten''' is one of the founders of WorldVistA. A longtime VA employee, he has been using MUMPS since 1981 in many different enviroments.
These include in the Department of Veterans Affairs, at MD Anderson Cancer Center with the Protocol Data Management System, as a contractor to the Department of Defense (CHCS) and using standalone FileMan projects.

He is one of the administrators of the VistApedia Wiki, and may be reached by telephone at 713-870-3834.

Here is a useful link to Recent Changes that gives you a LOT of info about what has changed recently on the wiki :

http://www.vistapedia.net/index.php?title=Special:Recentchanges&hideminor=0&hideliu=0&hidebots=0&limit=1500&days=150&limit=1500

[[Category:HomePage]]

Hello David, at long last Ive put my HP laptop back to perfect working order again. A friend ordered the cables I needed and I did the

labor and apparently I did a good job as everything is in perfect working order now. I would like it very much to start earning a living

again, I hate handouts and will do my best to do all I can and am able to for you as you have done for me. Thanks for being my friend

and also being as patient and understanding as you are. The Hospitals aren't doing much even after going through hoops to get the required

paperwork. what a nightmare this has turned out to be for me and my life too. I am in such bad shape that by the time they finally do the

procedures it may just kill me. The lawyer decided that I'm also needing to get on treatment of some kind to help them win my case. Since

when do people who obviously have a real need for SSDI need to to start taking meds. that aren't guaranteed to help and may speed up the

process of my illness just so a lawyer can make an easy 7000 dollars. I;m about to tell them to fly a kite. I have made it this long

without government cheese and I believe that I can make it longer without it too. I'm probably doing in my heart what is right but to

others may seem foolish or stupid. I believe that its also my life so It's my choise alone that really matters and not what others may

sem is wrong. Call me when you get this message please. Thanks David, Bte for now......

User:DavidWhitten

2015-10-22T07:43:24Z

NeilArmstrong:

'''David Whitten''' is one of the founders of WorldVistA. A longtime VA employee, he has been using MUMPS since 1981 in many different enviroments.
These include in the Department of Veterans Affairs, at MD Anderson Cancer Center with the Protocol Data Management System, as a contractor to the Department of Defense (CHCS) and using standalone FileMan projects.

He is one of the administrators of the VistApedia Wiki, and may be reached by telephone at 713-870-3834.

Here is a useful link to Recent Changes that gives you a LOT of info about what has changed recently on the wiki :

http://www.vistapedia.net/index.php?title=Special:Recentchanges&hideminor=0&hideliu=0&hidebots=0&limit=1500&days=150&limit=1500

[[Category:HomePage]]

Hello David, at long last Ive put my HP laptop back to perfect working order again. A friend ordered the cables I needed and I did the labor and apparently I did a good job as everything is in perfect working order now. I would like it very much to start earning a living again, I hate handouts and will do my best to do all I can and am able to for you as you have done for me. Thanks for being my friend and also being as patient and understanding as you are. The Hospitals aren't doing much even after going through hoops to get the required paperwork. what a nightmare this has turned out to be for me and my life too. I am in such bad shape that by the time they finally do the procedures it may just kill me. The lawyer decided that I'm also needing to get on treatment of some kind to help them win my case. Since when do people who obviously have a real need for SSDI need to to start taking meds. that aren't guaranteed to help and may speed up the process of my illness just so a lawyer can make an easy 7000 dollars. I;m about to tell them to fly a kite. I have made it this long without government cheese and I believe that I can make it longer without it too. I'm probably doing in my heart what is right but to others may seem foolish or stupid. I believe that its also my life so It's my choise alone that really matters and not what others may sem is wrong. Call me when you get this message please. Thanks David, Bte for now......

User talk:DavidWhitten

2014-10-10T11:07:16Z

NeilArmstrong:

User:NeilArmstrong

2014-10-10T11:02:54Z

NeilArmstrong:

Hello users and members my name is Neil and I'm here to assist with the development of the encyclopedia.

I'm also here to make the site more accessable for all visitors, and members so they can efficiently access

info regarding medical treatment or other options Thank you for choosing vistapedia.com as your

knowledgeable source of information, We are a team of dedicated individuals,who are working towards

a faster and more reliable system for veterans hospitals and in the future hopefully all hospitals as they

notice the improved methods and saved time as well as storage capacity for their computers being better

utilized to maximize space and be efficiently accessed.

[[Category:HomePage]]

Lexicon

2014-07-31T22:19:14Z

NeilArmstrong: Created page with "= Lexicon = The Lexicon is a standardized reference for clinical terminology across VHA that enables clinical information to be recorded, transmitted, retrieved, and analyzed..."

= Lexicon =

The Lexicon is a standardized reference for clinical terminology across VHA that enables clinical information to be recorded, transmitted, retrieved, and analyzed in a precise and consistent manner independent of clinic or medical center.

The Lexicon provides a comprehensive Application Program Interface (API) that enables any application that needs to use standardized terminology to be able to interface. At its inception in the early 1990s, the scope of the Lexicon was limited to expressing diagnostic clinical problems in easy-to-understand terminology and associating terms to coding systems such as International Classification of Diseases (ICD), Clinical Modification (ICD-9-CM), Diagnostic and Statistical Manual of Mental Disorders (DSM), and the North American Nursing Diagnosis Association (NANDA).

Over the years, this scope broadened to provide a general purpose utility that serves the terminology needs of many packages, including Problem List (standardized using SNOMED CT), Encounter Forms, Text Integration Utility (TIU), Event Capture, Federal Health Information Exchange (FHIE), and the Laboratory Data Sharing Interoperability (LDSI) project. A number of other VistA applications that need the versioned terminology that Lexicon can provide may be added to this list in the near future.

In addition to providing terminology, the Lexicon provides a coding system update deployment mechanism. This update deployment mechanism is now used to update coding systems that are represented in the Lexicon, in addition to updating standard VistA reference files for the same coding systems that fall outside the Lexicon namespace. Additionally, the same mechanism is used to update coding systems that do not form part of the Lexicon. A large number of applications, packages, and services (VistA and external) are now dependent on the quarterly updates provided by this deployment mechanism. The dependent packages include Integrated Billing, Fee Basis, Automated Information Collection System (AICS), Laboratory, Dental, Prosthetics, Mental Health, Radiology, Surgery, Registration, Patient Care Encounter (PCE), Event Capture, Quality: Audiology and Speech Analysis and Reporting (QUASAR), Home Based Primary Care, Clinical Reminders, Text Integration Utility (TIU), Laboratory Data Sharing Interoperability (LDSI), and standardized Problem List.

All of the functionality and services provided by the Lexicon are expected to be replaced by a broader and deeper range of services through VA Enterprise Terminology Services (VETS) applications in the near future.

= Features =

* Provides a basis for a common language of terminology, so that all members of a health care team can communicate with each other.

* Provides a concept-based terminology that is well defined, understandable, and encodable by multiple coding schemes.

* Provides for site modification of term definitions. These modifications are captured by the software and transmitted to the Lexicon team for ratification and possible inclusion in future updates.

* Provides the ability to deploy updates to code systems from Standards Development Organizations (SDOs) that are required by statute, mandated by an oversight body, or required by VHA business needs. The current systems include CPT, HCPCS, CPT modifiers, ICD-9 Diagnoses, ICD-9 Procedures, and SNOMED CT.

* Provides for user definable (user, specialty, or clinic) controlled views of vocabulary through the use of subsets that may be based on a combination of semantic types and code sources.

* Accepts the provider term if a search of the dictionary does not find a match.

* These terms (otherwise known as unresolved narratives) are captured by the software and forwarded to the Lexicon team for analysis and possible inclusion in future updates.

* Allows abbreviations or shortcuts to provide quick access to frequently used definitions.

* Supports CPT, HCPCS, ICD-9-CM Diagnoses, DoD DMIS-IDs, and SNOMED CT coding systems.

* Optimizes search results by placing the most frequently-used terms near the start of the list.

* Supports coding system versioning, activation history, and code text history.

* Supports assignment of a VA Unique Identifier (VU ID) to a concept.

* Supports code stratification and merging.

* Supports synonyms, lexical variants, plural forms, abbreviations, word order variants, keywords, and excluded words.

* Supports inter-coding system mappings.

User:NeilArmstrong

2014-03-11T23:44:33Z

NeilArmstrong: minor edit to summary homepage

Hello users and members my name is Neil and I'm here to assist with the development, and expansion of the encyclopedia.

I'm also here to make the site more accessable for all visitors, and members so they can efficiently access info regarding medical treatment or other options.

Thank you for choosing vistapedia.com as your knowledgeable source of information, We are a team of dedicated individuals,who are working towards a faster

and more reliable system for veterans hospitals and in the future hopefully all hospitals as they notice the improved methods and saved time as well as storage

capacity for their computers being better utilized to maximize space

[[Category:HomePage]]

User:NeilArmstrong

2014-02-12T12:05:39Z

NeilArmstrong:

Hello users and members my name is Neil and I'm here to assist with the development, and expansion of the encyclopedia.

I'm also here to make the site more accessable for all visitors, and members so they can efficiently access info regarding medical treatment or other options.

Thank you for choosing vistapedia.com as your knowledgeable source of information, We are a team of dedicated individuals,who are working towards a faster

and more reliable for veterans hospitals and in the future hopefully all hospitals as they notice the improved methods and saved time as well as storage

capacity for their computers being better utilized to maximize space

[[Category:HomePage]]

User:NeilArmstrong

2014-02-12T12:01:08Z

NeilArmstrong:

Hello users and members my name is Neil and I'm here to assist with the development, and expansion of the encyclopedia.

I'm also here to make the site more accessable for all visitors, and members so they can efficiently access info regarding medical treatment or other options.

Thank you for choosing vistapedia.com as your knowledgeable source of information, We are a team of dedicated individuals,who are working towards a faster

and more reliable for veterans hospitals and in the future hopefully all hospitals as they notice the improved methods and saved time as well as storage capacity

for their computers being better utilized to maximize space capacity.

[[Category:HomePage]]

User:NeilArmstrong

2014-02-12T12:00:02Z

NeilArmstrong: Changed homepage intro details

Hello users and members my name is Neil and I'm here to assist with the development, and expansion of the encyclopedia.

I'm also here to make the site more accessable for all visitors, and members so they can efficiently access info regarding medical treatment or other options.

Thank you for choosing vistapedia.com as your knowledgeable source of information, We are a team of dedicated individuals,who are working towards a faster and more reliable for veterans hospitals,

and in the future hopefully all hospitals as they notice the improved methods and saved time as well as storage capacity for their computers being better utilized to maximize space capacity.

[[Category:HomePage]]

User talk:DavidWhitten

2014-02-03T11:22:22Z

NeilArmstrong: added a personal note to David Whitten

VISTA~

2014-01-27T12:15:34Z

NeilArmstrong: added a glossary link to VISTA~

; VistA
: Veterans Health Information Systems and Technology Architecture (VISTA), formerly Decentralized Hospital Computer Program ([[DHCP~|DHCP]]) of the Veterans Health Administration (VHA), Department of Veterans Affairs ([[VA~|VA]]). VistA software, developed by VA, is used to support clinical and administrative functions at VA Medical Centers nationwide. It is written in [[MUMPS~|M]] and, via the [[VA Kernel~|Kernel]], runs on all major M implementations regardless of vendor. VistA is composed of packages which undergo a [[verification~|Verification]] process to ensure conformity with [[namepacing~|namespacing]] and other VistA standards and conventions.

Source: '''Spinal Cord Dysfunction V. 2.0 User Manual'''
----
[[Category:Spinal Cord Dysfunction]]

; VistA
: Acronym for Veterans Health Information Systems and Technology Architecture, the new name for Decentralized Hospital Computer Program (DHCP).

Source: '''Outpatient Pharmacy V. 7.0 Technical Manual/Security Guide'''
----
[[Category:Pharm: Outpatient Pharmacy]]

; VistA
: Veterans Health Information Systems and Technology Architecture.

Source: '''[[Clinical Procedures~|Clinical Procedures]] V. 1.0 User Manual'''
----
[[Category:Clinical Procedures]]

; VistA
: Veterans Health Information Systems and Technology Architecture

Source: '''Beneficiary Travel User Manual Version 1.0'''
----
[[Category:Beneficiary Travel]]

; VistA
: Veterans Health Information System and Technology Architecture

Source: '''[[Clinical Case Registries~|Clinical Case Registries]] V. 1.0 User Manual'''
----
[[Category:Clinical Case Registries]]

; VistA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Immunology Case Registry v.2.1 User Manual'''
----
[[Category:Immunology Case Registry]]

; VistA
: Veterans Information Systems Technology Architecture, the new name for DHCP.

Source: '''CPRS Read-Only User Guide'''
----
[[Category:Computerized Patient Record System (CPRS)]]

; VistA
: The name for the VHA program responsible for installing an integrated computer system in all VHA medical facilities.

Source: '''Health Summary V. 2.7 Technical Manual'''
----
[[Category:Health Summary]]

; VistA
: Veterans Information System Technology Architecture, the VHA computer program used in VA facilities.

Source: '''Problem List V. 2.0 User Manual'''
----
[[Category:Problem List]]

; VistA
: Veterans Health Information Systems and Technology Architecture

Source: '''Laboratory V. 5.2 Patch LR*5.2*259 AP Electronic Signature User Manual'''
----
[[Category:Lab-Anatomic Pathology]]
; VISTA
: Veterans Health Information Systems and Technology Architecture

Source: '''Incomplete Records Tracking Technical Manual V. 1.0'''
----
[[Category:Incomplete Records Tracking]]

; VISTA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Intake and Output V. 4.0 Technical Manual'''
----
[[Category:Intake and Output]]

; VISTA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Medicine V. 2.3 Technical Manual'''
----
[[Category:Medicine]]

; VISTA
: Veterans Health Information Systems and Technology Architecture

Source: '''MHA 2 Patch YS*5.01*76 User Manual'''
----
[[Category:Mental Health]]

; VISTA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Nursing V. 4.0 Technical Manual and Package Security Guide'''
----
[[Category:Nursing]]

; VISTA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Technical Manual and Package Security Guide Version 2.11'''
----
[[Category:Oncology]]

; [[VISTA~|VISTA]]
: Veterans Information System Technology Architecture, the new name for DHCP.

Source: '''Patient Care Encounter V. 1.0 Technical Manual and Visit Tracking V. 2.0 Technical Manual'''
----
[[Category:Patient Care Encounter]]

; VISTA
: Veterans Health Information Systems and Technology Architecture.

Source: '''BCMA V. 3.0 Manager’s User Manual'''
----
[[Category:Pharm: Bar Code Medication Administration (BCMA)]]

; VISTA
: Acronym for Veterans Health Information Systems and Technology Architecture.

Source: '''CMOP V. 2.0 Technical Manual'''
----
[[Category:Pharm: Consolidated Mail Outpatient Pharmacy]]

; VISTA
: Veterans Health Information Systems and Technology Architecture

Source: '''Controlled Substances V. 3.0 Inspector’s User Manual'''
----
[[Category:Pharm: Controlled Substances]]

; VISTA
: Acronym for Veterans Health Information Systems and Technology Architecture.

Source: '''Drug Accountability/Inventory Interface V. 3.0 Technical Manual/Security Guide'''
----
[[Category:Pharm: Drug Accountability]]

; VistA
: Veterans Health Information Systems and Technology Architecture

Source: '''LEDI III Implementation and User Guide V. 5.2'''
----
[[Category:Lab-Electronic Data Interchange]]

; VistA
: Veterans Health Information Systems and Architecture

Source: '''Laboratory Point of Care Interface Installation and User Guide V. 5.2'''
----
[[Category:Lab-Point of Care]]

; VistA
: Veterans Health Information System and Technology Architecture

Source: '''Nutrition and Food Service Outpatient Meals User Manual v.5.5'''
----
[[Category:Nutrition and Food Service]]

; VistA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Pharmacy Benefits Management V. 4.0 Technical Manual/ Security Guide'''
----
[[Category:Pharm: Benefits Management (PBM)]]

; VistA
: Veterans Health Information Systems and Technology Architecture.

Source: '''Pharm: National Drug File V. 4.0 Technical Manual'''
----
[[Category:Pharm: National Drug File (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

Analyte~

2013-11-25T08:17:25Z

NeilArmstrong:

; [[Analyte~|Analyte]]
: A substance undergoing analysis.

Source: '''National Laboratory Tests *5.2* Technical, Installation, and User Guides'''
----
[[Category:Lab-National Laboratory Tests]]
{{Category:Glossary}}
[[Category:Glossary]]

User:NeilArmstrong

2013-11-02T20:53:58Z

NeilArmstrong: edited homepage

I'm here to assist with the development, and expansion of the encyclopedia.

I'm also here to make the site more accessable for all visitors, and members.

Thank you for choosing vistapedia.com as your knowledgeable source of information,

We are a team of dedicated individuals,who are working towards a reliable,

and more efficient way of accessing medical data.

[[Category:HomePage]]

User talk:DavidWhitten

2013-10-12T16:02:11Z

NeilArmstrong:

David, would it be inappropriate to add some info about Serenji on the [[Debugging with GT.M]] page? I don't know how non-commercial and open source you want to keep things on this wiki? BTW are there any areas where you think I could help [[User:Georgej|Georgej]] 03:28, 12 May 2005 (CDT)

Sure, put as much information as you want. The trick is to have an active community working together.
I'd suggest you create a page [[Debugging with Serenji]] page, since that would be useful to folks running GT.M as well as other MUMPS-like systems.

Hello David it's Neil I have figured out my problem on the macbook and am now back on the site. Sorry I've been so caught up with school to be much help but my English class is finished in one week and I will only have one class to manage for 8 weeks so I'll have ample time to work on the wiki. I expect I will get no less than a 3.0 g.p.a. for the English and probably same or higher in learning frameworks. It's been crazy taking an accelerated college class but I did well I think considering my 24 year gap from high school and college. The professor said I am a brilliant writer and I should think about writing a book based on my experiences in life, it seemed to fascinate her all the things I've gone through. Anyway I wanted you to know that I am doing very well in school and that I believe it's the smartest decision I've made in my entire life. By the way the macbook pro is some kind of laptop like no other! It has no ethernet or hard drive with moving parts or an optical drive which is why it can run so fast, no moving parts to run makes a huge difference in performance as well as battery life. I can use it for about 7-8 hours on battery saver mode without cord plugged in. The optical drive issue was pre solved before i bought it I had a light-on optical drive w/micro usb so when I want or need to use it to install software or save backups I can. I can say that me paying 2,500 dollars for a laptop was not crazy, I believe that it was a very smart decision for what its capable of and how well it's made. The computer will still be as nice or nicer than anything dell,toshiba,asus, or anyone else builds in 4 years from now unless they start using titanium cases to stop theirs from falling to pieces. I will have my phone on as always for you to call me if you need to David, take care and God bless.

Calc Stop Date~

2013-08-09T14:10:13Z

NeilArmstrong: aqddedb gllssary linnk to cprs~

; Calc Stop Date
: Calculated Stop Date. This is the date that would have been the default Stop Date/Time for an order if no duration was received from [[CPRS~|CPRS]]. Due to the existence of a duration, the default Stop Date/Time of the order becomes the expected first dose plus the duration.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

Calc Start Date~

2013-08-09T14:08:23Z

NeilArmstrong: aqddedb gllssary linnk to cprs~

; Calc Start Date
: Calculated Start Date. This is the date that would have been the default Start Date/Time for an order if no duration was received from [[CPRS~|CPRS. Due to the existence of a duration, the default Start Date/Time of the order becomes the expected first dose.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

User:NeilArmstrong

2013-08-09T13:59:52Z

NeilArmstrong: updated userpage

I'm here to assist with the development and expansion of the encyclopedia and make site more accessable for all visitors and members.

Thank you for choosing VistaPedia.com as your knowledgeable source of information,

We are a team of dedicated individuals who are working towards a quicker and more efficient way of accessing medical data.

[[Category:HomePage]]

CPRS Installation

2013-08-09T13:51:40Z

NeilArmstrong: aqddedb gllssary linnk to cprs~

__TOC__

This page [[record~|Record]]s the process of installation of the [[CPRSComputerized Patient Record System]] Graphical User Interface client program on the [[Microsoft Windows OS]].

=== [[CPRS~|CPRS]] Versions ===

This table will list links for the various [[CPRS~|CPRS]] versions. (The most current version is at the top)

{| class="grey" border="1" cellpadding="2"
|+ [[CPRS~|CPRS]] Versions
|-
! Version Number
! Distribution File
! Availability
! Date
|-
| version 1.0.27.90
| OR-3_SEQ-273_PAT-296.ZIP
| [https://downloads.va.gov/files/FOIA/Software/Patches_By_Application/OR-ORDER%20ENTRY_RESULTS%20REPORTING/ Download folder on VA site]
| 8/2009
|-
| version 1.0.27.83
| OR_30_304.ZIP
| [https://downloads.va.gov/files/FOIA/Software/Patches_By_Application/CPRS%20GUI%20FILES/CPRS%20VERSION%2027/ Download folder on VA site]
| 11/2008 Emergency Correction of Patient Safety Issues
|-
| version 1.0.27.77
| OR_30_243.ZIP
| [https://downloads.va.gov/files/FOIA/Software/Patches_By_Application/CPRS%20GUI%20FILES/CPRS%20VERSION%2027/ Download folder on VA site]
| 08/2008
|-
| version 1.0.26.69
| OR_30_270.zip
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server] or
[https://downloads.va.gov/files/FOIA/Software/VistA_FOIA_Historical_Files/VISTA_FOIA_RELEASES_BEFORE_2008/OR-Order%20Entry-Results%20Reporting/ Download folder on VA site]
|-
| version 1.0.26.69
| for WorldVistA EHR
| on the Sourceforge WorldVistA EHR site and http://opensourcevista.net:8888/NancysVistAServer
| (dated June 2007)

|-
| version 1.0.26.68
| OR_30_258.zip
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| Note Below (NB):(dated July 17, 2006)
|-
| version 1.0.25.42
| OR_30_235.zip
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated July 09, 2005) <br>Note: Replace .25.40 with .25.42 for patient safety
|-
| version 1.0.25.40
| OR_30_231.zip
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated May 06, 2005)
|-
| version 1.0.25.28
| OR_30_195.zip
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated Feb 09, 2005)
|-
| version 1.0.24.27
| OR_30_224.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated Sep 03, 2004)
|-
| version 1.0.24.26
| OR_30_190.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated Aug 02, 2004)
|-
| version 1.0.23.15
| OR_30_187.ZIP
| *Sourceforge WorldVistA and [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated about 02/04)
|-
| version 1.0.22.16
| OR_30_206.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated about 01/04)
|-
| version 1.0.20.21
| OR_30_148.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated about 11/02)
|-
| version 1.0.20.21
| OR_30_148.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
|(dated about 11/02)
|-
| version 1.0.19.7
| OR_30_132.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated about 05/02)
|-
| version 1.0.18.2
| OR_30_125.ZIP
| [http://opensourcevista.net:8888/NancysVistAServer Nancy's VistA Server]
| (dated about 12/01)
|}

----

=== version change trick ===
NB: There is a trick to making version 1.0.26.68. It is done for you in CPRSDir.zip which can be found along with the instructions for creating it at:

http://downloads.opensourcevista.net/VADemo9-26-06

To find out which version to use, look next to the option [[OPTION OR CPRS GUI CHART|named "OR CPRS GUI CHART"]] like this example where [[~|CPRS~|CPRS]] version 1.0.23.15 was needed:

D Q^DI

VA FileMan 22.0
Select OPTION: 5 INQUIRE TO FILE ENTRIES

OUTPUT FROM WHAT FILE: DEVICE// OPTION
1 OPTION (10126 entries)
2 OPTION SCHEDULING (116 entries)
CHOOSE 1-2: 1 OPTION (10126 entries)
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.23.15
ANOTHER ONE:

To use a particular version of [[CPRS~|CPRS]], the server-side software code must match. The files are found at ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ and the source code is in the "Programs" subdirectory of this directory

Thus:

[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]

The Delphi source code for each of these (e.g. OR_30_235_SRC.ZIP) will be found in the subdirectory
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]

The wget(1) utility is capable of fetching the files from this server

AceFTP is a freeware FTP program that works, if needed
http://software.visicommedia.com/en/productsfreeware/

''(In the past this FTP site could not be reached with Mozilla/Firefox. That has been corrected.)''
----

=== 1.0.26.69 (and TMG-CPRS) spoof --> 1.0.26.76 ===

Since the changes between 1.0.26.69 and 1.0.26.76 are relatively minor, in this case, version can be used by changing the option in the option file like this:

D P^DI

VA FileMan 22.0

Select OPTION: 1 ENTER OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: OPTION//
EDIT WHICH FIELD: ALL//

Select OPTION NAME: OR [[CPRS~|CPRS]] GUI CHART [[CPRS~|CPRS]]Chart version 1.0.26.76
NAME: OR CPRS GUI CHART//
MENU TEXT: CPRSChart version 1.0.26.76 Replace 76 With 69
Replace
CPRSChart version 1.0.26.69
----
When using TMG-CPRS, another way of reaching the exact same result is to add ''' "SPOOF-VER=1.0.26.76" ''' to the end of the Windows shortcut to [[CPRS~|CPRS]] like so:

... S=192.168.xxx.xxx P=92xx CCOW=DISABLE SPOOF-VER=1.0.26.76

(This method has the (admittedly dubious) advantage of allowing ''both'' a CPRS v1.0.26.68 ''and'' a v1.0.26.76 to connect without changing the server side.

'''Caution:''' One needs to know that the two versions truly are compatible or be willing to risk nasty side-effects, perhaps even damage to the server's database.
----
=== SSH Tunnel ===
Communications between CPRS and the VistA server are not encrypted by default. Access/Verify Codes and all patient data are transmitted in the clear. However, these can be protected by setting up an encrypted "tunnel" between client and server.

[[Setting up an SSH Tunnel between CPRS & VistA]]
----
=== Automatic Windows Installer ===

The [http://sourceforge.net/projects/worldvistaautoi/files Astronaut] suite of automatic installers includes cprs, tmg-cprs and many other clients, available in point-click windows .exe installers. IP address and port number are entered by the user.
----
=== Wine/Crossover compatability ===

[[Wine/Crossover]]

Category:CPRS

2013-07-30T04:41:59Z

NeilArmstrong: aqddedb gllssary linnk to cprs~

[[CPRS~|cprs]]
Computerized Patient Record System

Helpful EMails

2013-07-05T22:01:39Z

NeilArmstrong: Added a glossary link to file~

-----------------------------------------------------------------------
I want to interface the lab in my office into VistA. The suggestion
that I was given was to get the equipment to send HL-7 messages to
VistA.

Here is what we have:
1. Beckman Coulter Synchron CX5 delta
http://www.beckman.com/products/instrument/genchem/cx5delta.asp
This is our chemistries machine
...
Our machines save RS232 ports.
Would I have to manually create "drivers" for these devices?
--Kevin T.
-----------------------------------------------------------------------
Look at the web sites: http://www.datainnovations.com/
and http://www.dawning.com/
...
Both of these companies sell PC's that consolidate data
from various lab instruments and transmit it to a Hospital Information
System. We use a Data Innovation Lab Instrument Manager. It is licensed by the
number of drivers you need. Each instrument needs its own driver and
there is a driver for the VISTA system which speaks HL-7.
--Charles G Lambrecht
-----------------------------------------------------------------------
Those devices basically pool multiple character streams into one. Two and a
half decades ago systems were not very fast so we (Wally and I) programmed a
PDP-11 (the single card version smaller than the 11/03) in RT-11 assembly
code to buffer the data so the 11/70 could keep up. Take a look at the ^LAB
routine. On today's systems you could just as easily Job the routine to a
separate port (serial line?) for each instrument. The definitions for how
the instrument lays out the data are in the AUTO INSTRUMENT [[file~|file]] 62.4.
--Cameron Schlehuber
-----------------------------------------------------------------------
Are you saying that the protocol for communicating with the macine is
stored in [[file~|file]] 62.4?
--Kevin T
-----------------------------------------------------------------------
At least for some machines, yes.
--Cameron Schlehuber
-----------------------------------------------------------------------
In the past direct connect interfaces would be written to accept the data
stream from each device, push it into the ^LA global. The listening
interface would then parse it into the ^LAH global in an acceptable pattern.
Each interface depended on a listener connected to a device in the device
[[file~|file]]. Each instrument would read the barcode label on the specimen
container and send (by serial originally) the test results with the barcode
- which was unique to this patient's test request.
With the ^LA global set appropriately, the lab techs would enter the lab
options to verify auto-instrument data and would verify each result.
The Load/Worklist and AutoInstrument [[file~|file]]s were set accordingly for each
instrument.

We now use Data Innovations for all but 4 of our interfaces. Paying for DI
results in a stable environment that doesn't depend on having programming
expertise on board. Also, writing local direct connect interfaces -
although fun - is a never ending job as the labs continue to purchase new
instrumentation. Nonetheless, it may be that interfaces written for similar
equipment for VA labs may run with little modification in instances where
avoiding annual license fees are an issue. (DI = [DataInnovations])
--Larry Carlson
-----------------------------------------------------------------------
Kevin, simply interfacing the devices into a Data Innovations or Dawning
system would "do the trick", of course there may be so interface writing but
that is not too terribly complex.
At our site in the VHA we use Dawning, if collects the results from the
modalities and then sends HL7 to VistA.
-- Roy Gaber
-----------------------------------------------------------------------
The lab package comes prepared for instrument interfaces - which are just M
routines (and not really all that complicated). The ones I put together (or
stole, or modified stolen code) used LAT serial connections.
...
I did have a one interface moved to TCP/IP by using a JetDirect box before
Cache. Just had to change the Kernel open command on the M routine as the
MAXM still thought it was connected serially.
We are now in the process of moving the remaining direct connects to
Lantronix boxes in the closet which behave much like JetDirect except a TNA
type VMS connection is suppose to allow them to still use LAT-type commands
on the M side. I will know more about whether this works in a few weeks.
We have a Vitek, Bactec, and blood gas machines still on direct connect.

We also put together an HL7 interface with Roche glucose meters. The Roche
system has an MAS HL7 interface so I only needed to write the necessary M
handling routines in VistA. The meters send the patient's SSN, glucose
result, date/time of test, DUZ of user, and comments. My processing routine
hops on the old FASTLAB options that allow ordering and resulting of tests
on the fly (I had to pull out the routines into my namespace and take care
of all previously interactive pieces) then returns to Roche the patient's
name and the accession number of the [[file~|file]]d test. We are switching to the
recently released national POC HL7 interface that will have national support
and does a much more thorough job of confirming correct patient (clinic
appointment for the day etc). Nonetheless, the project demonstrated that an
HL7 lab interface is not too difficult. BTW I presume John McCormack's
group's POC interface is available as part of VistA now.
--Carlson, Larry G
-----------------------------------------------------------------------

HFS Device

2013-07-05T21:48:37Z

NeilArmstrong: Added a glossary link to file~

The entry in the DEVICE [[File~|file]] named HFS is used by [[KIDS]] to load a distribution.

HFS stands for "Host [[File~|file]] System", ie: the operating system that provides hosting to the MUMPS/Cache/GT.M sytem. Examples of a HFS are: MacOS, BSD, Microsoft Windows, Linux, VMS, VOS, etc.

Computed Field~

2013-07-05T21:46:25Z

NeilArmstrong: Added a glossary link to file~

; Computed Field
: This field takes data from other fields and performs a predetermined mathematical function (e.g., adding two columns together). You will not, however, see the results of the mathematical calculation in the [[file~|file]]. Only when you are printing or displaying information on the screen will you see the results for this type of field.

Source: '''Laboratory V. 5.2 Anatomic Pathology User Manual'''
----
[[Category:Lab-Anatomic Pathology]]
{{Category:Glossary}}
[[Category:Glossary]]
----

; Computed Field
: This field takes data from other fields and performs a predetermined mathematical function (e.g., adding two columns together). You will not, however, see the results of the mathematical calculation in the [[file~|file]]. Only when you are printing or displaying information on the screen will you see the results for this type of field.

Source: '''Laboratory V. 5.2 Technical Manual'''
----
[[Category:Laboratory]]
{{Category:Glossary}}
[[Category:Glossary]]

Disposition/Close of EWL entry~

2013-07-05T21:42:57Z

NeilArmstrong: Added a glossary link to file~

; Disposition/Close of EWL entry
: Changing the Current Status field of open EWL entry from ‘open’ into ‘closed’. There are several coded reasons, identified by the Disposition field of the SD WAIT LIST [[file~|file]].

Source: '''[[Electronic Wait List~|Electronic Wait List]] Patch SD*5.3*327 User Manual'''
----
[[Category:Electronic Wait List]]
{{Category:Glossary}}
[[Category:Glossary]]

GT.M pipe for print DEVICE:

2013-07-05T21:36:16Z

NeilArmstrong: Added a glossary link to file~

With the introduction of the pipe device to GT.M (version V5.3-003) this simpler, more secure, even elegant method can be used:

NAME: HP-PHOTOSMART
$I: <pipe>
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""
POST-CLOSE EXECUTE: X "c ""p"""
SUBTYPE: P-OTHER80
TYPE: OTHER

Note: We use TYPE:Other rather than Host [[File~|file]] Server. No host [[file~|file]] needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. Thus one could do:

PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""

In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103" with the previously mentioned details set, and then set IO to that device." FileMan will then send his output to IO. Finally the POST-CLOSE just closes the pipe. No Linux /tmp/print.txt [[file~|file]] to clean up. No fuss, no muss. '''What's not to love?!?!'''

--[[User:JohnLeoZ|gra'pa Z]] 06:40, 13 Aug 2009 (EDT)

Comma Separated Values

2013-07-05T21:32:41Z

NeilArmstrong: Added a glossary link to file~

Comma Separated Values [[Files~|file]] are [[Host Operating System Files]] that store the data in a spreadsheet or the entries in a FileMan [[File~|file]].
The format was created by Lotus-123.

The values of each column (field) are separated by commas. When the value is a string of characters, the values are surrounded by double quotes. (double quote is the [[ASCII Characters]] number 34).

----
[[Category:Glossary]]

Episode 60 Example of setting Institution file Station Number

2013-07-05T21:19:43Z

NeilArmstrong: Added a glossary link to file~

This is apparently needed for lab and pharmacy.

Find the name of the Default Institution: Kernel system
parameters-->Default Institution-->Example Institution Hospital Name

Then go to the Institution [[file~|file]] station number for that Institution.

<pre>
GTM>S XUMF=1 D Q^DI

MSC FileMan 22.1036

Identity = 1 Administrator,System SA
...OK? Yes// (Yes)

Select OPTION: 1 ENTER OR EDIT [[FILE~|file]] ENTRIES

Input to what [[File~|file]]: INSTITUTION// (68 entries)
EDIT WHICH FIELD: ALL// 99 STATION NUMBER
THEN EDIT FIELD:

Select INSTITUTION NAME: EXAMPLE INSTITUTION HOSPITAL NAME TX
STATION NUMBER: 100

Select INSTITUTION NAME:

Select OPTION:
</pre>

FILE 3.5

2013-07-05T21:14:08Z

NeilArmstrong: Added a glossary link to file~

The DEVICE File (#3.5) is stored in the global root of ^%ZIS(1,
and each entry corresponds to a name for I/O (Input and Output) in the VistA system. Generally speaking characters are sent to and received from an I/O device in most computer systems as a normal part of interaction with a user.

The devices in VistA are segmented by the TYPE Field which has the following values:
{| border=2
|-
| *INTERNAL ABBREVIATION*
| *EXTERNAL VALUE*
| *Intended use*
|-
| TRM
|TERMINAL
| hard connected terminals such as consoles
|-
| OTH
|OTHER
|
|-
| MT
|MAGTAPE
| sequential magnetic tape
|-
| SDP
|SDP
| unused- was Sequential Disk Processing - MUMPS-as-OS disk storage
|-
| SPL
|SPOOL
| unused - was in-MUMPS disk/printer spooling
|-
| BAR
|BARCODE READER
|
|-
| HFS
|HOST [[FILE~|file]] SERVER
| commonly used - [[File~|file]]system storage, print spooling, etc.
|-
| VTRM
|VIRTUAL TERMINAL
| soft connect terminals over the network
|-
| HG
|HUNT GROUP
| providing for banks of "alike" devices
|-
| RES
|RESOURCES
| synchronization and limiting background processes
|-
| CHAN
|NETWORK CHANNEL
| devices attached with TCP/IP addresses and ports
|-
| IMPC
|IMAGING WORK STATION
|}

National Drug File Package or National Drug File Software~

2013-07-02T18:42:51Z

NeilArmstrong: Added a glossary link to file~

; National Drug File Package or National Drug File Software
: This software package attempts to match the National Drug files entries with local DRUG [[file~|File]] (#50) entries using both automatic matching and manual matching. The automatic matching is by NDC number only.

Source: '''Pharm: National Drug File V. 4.0 User Manual'''
----
[[Category:Pharm: National Drug File (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

VA DRUG CLASS File (50.605)~

2013-07-02T18:41:47Z

NeilArmstrong: Added a glossary link to file~

; VA DRUG CLASS File (50.605)
: This [[file~|File]] contains the VA Drug Classification codes and their descriptions. Each product has one of these codes assigned to it and stored with it.

Source: '''Pharm: National Drug File V. 4.0 Technical Manual'''
----
[[Category:Pharm: National Drug File (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

NATIONAL DRUG TRANSLATION File (50.612)~

2013-07-02T18:40:56Z

NeilArmstrong: Added a glossary link to file~

; NATIONAL DRUG TRANSLATION File (50.612)
: A temporary [[file~}File]] that is created by the NDF software. This [[file~|File]] will contain information on drugs that have been matched, or for which a match was attempted.

Source: '''Pharm: National Drug File V. 4.0 Technical Manual'''
----
[[Category:Pharm: National Drug File (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

NATIONAL DRUG File (50.6)~

2013-07-02T18:40:01Z

NeilArmstrong: Added a glossary link to file~

; NATIONAL DRUG File (50.6)
: This [[file~|File]] contains a list of available drug products. It includes specific information for each product, including trade name, NDC number, manufacturer, VA Drug Class code, dosage form, route of administration, strength, units, ingredients, ingredient strength and units, package code, package size, package type, VA Product Name, and VA generic name. NDF software attempts to match products from this [[file~|File]] with products in the local DRUG [[file~|File]] (#50)

Source: '''Pharm: National Drug File V. 4.0 Technical Manual'''
----
[[Category:Pharm: National Drug File (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

Local DRUG File (50)~

2013-07-02T18:38:01Z

NeilArmstrong: Added a glossary link to file~

; Local DRUG File (50)
: This [[file~|File]] contains the local GENERIC NAME (#.01), INACTIVE DATE (#100), DEA, SPECIAL HDLG (#3), and NDC fields, as well as others. NDF software attempts to match products from this [[file~|File]] with products in the VA GENERIC [[file~|File]] (#50.6) and the VA PRODUCT [[file~|File]] (#50.58).

Source: '''Pharm: National Drug [[File~|File]] V. 4.0 Technical Manual'''
----
[[Category:Pharm: National Drug [[File~|File]] (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

Linux Idea userid

2013-06-10T17:48:38Z

NeilArmstrong: Added a glossary link to file

Both Linux and Unix have the idea of a '''userid'''. This is a short name, associated with [[Linux Idea Filesystem|files]] and [[Linux Idea process|processes]], that identifies the user who owns them. The userid is stored in a [[file~|file]] named /etc/passwd, which has more information about the user, such as their full name and office location.

Many MUMPS implementations associate the Linux userid with the [[MUMPS Idea Job|jobs]] that run on the host operating system.

Within VistA, this idea is expressed as the value of the local variable DUZ. The DUZ is a numeric value used to index the {{FILE|NEW PERSON}}. This [[file~|file]] keeps track of many details about a person, including their full name and office location. The value of a person's DUZ is associated with the [[Vista Idea Task|tasks]] and [[FileMan File]]s they have created and modified.

-----
[[Category:Linux Idea]] [[Category:VistA Local Variable Explanation]]
[[Category:Linux]] [[Category:Unix]]

Configuration How To HOME DEVICE DOES NOT EXIST

2013-06-10T17:47:04Z

NeilArmstrong: Added a glossary link to file

__TOC__
== Description ==
A common problem that people have who are trying to configure VistA is a message:

HOME DEVICE DOES NOT EXIST IN THE DEVICE [[FILE~|file]]
PLEASE CONTACT YOUR SYSTEM MANAGER!

This means that VA Kernel ran into a problem when trying to output information to a $IO device.

The most common situation is that the [[configuration~|Configuration]] did not have a proper setup in the {{FILE|DEVICE}}, specifically for the current MUMPS level $IO device.

== Troubleshooting ==

Make sure you have all of the devices listed on the [[Standard VistA Devices]].
A VistA based system requires all of them to be setup properly.

=== Step by Step ===

# login using the device
# enter programming mode (if not part of login process)
# use the MUMPS command
## <mcode>WRITE "<<",$IO,">>",!</mcode>
# go into programmer's FileMan
## <mcode>DO P^DI</mcode>
# lookup the device specified in the {{FILE|DEVICE}}.
## VA FileMan 22.0
## Select OPTION: INQUIRE TO [[FILE~|file]] ENTRIES
## OUTPUT FROM WHAT [[FILE~|file]]: NEW PERSON// DEVICE (32 entries)
## Select DEVICE NAME:
# input the name of the device printed above (between the << and >> )
# if it is found, make sure the field SIGN-ON/SYSTEM DEVICE: is set to YES
# if it is not found, decide if the DEVICE should be a virtual device or not, and then add it to the {{FILE|DEVICE}}.

== Technical Details ==

This message occurs because the device name fails in a ^DIC lookup in the DEVICE [[file~}file]]. Normally, devices have the field SIGN-ON/SYSTEM DEVICE set to YES, and they are virtual devices. So the code progressively takes letters off the end of the lookup variable storing the device name, and tries to find them in the G crossref of the DEVICE [[File~|file]], ie: ^%ZIS(1,"G","SYS.."_something

VA FileMan DO^DIC1

2013-06-10T17:44:48Z

NeilArmstrong: Added a glossary link to file

=== File Information Setup ===
The <mentry>DO^DIC1</mentry> entry point retrieves a [[file~|file]]'s [[file~|file]] header node, code to execute its identifiers and its screen (if any), and puts them into local variables for use during lookup into a [[file~|file]].

If $DATA(DO) is greater than zero, <mentry>DO^DIC1</mentry>x will QUIT immediately. If DIC("W") is defined before calling <mentry>DO^DIC1</mentry>, it will not be changed.

VA FileMan DIC

2013-06-10T17:43:34Z

NeilArmstrong: Added a glossary link to file

The '''VA FileMan ^DIC''' [[API]], is used to find an entry in a FileMan [[File~|file]].

there are several main entry points:
== Classic FileMan ==
These routines use local variables in the symbol table as the parameter passing style.
=== Lookup/Add ===
Given a lookup value, these entry points search the requested Index(es) on a [[file~|file]] and either
# find a matching entry,
# add an entry to the [[file!|file]], or
# return a condition indicating that the lookup was unsuccessful.

There are three APIs to lookup an entry in a [[file~|file]], they only differ in the way they use cross-references to do lookup. The three entry points perform lookups as follows:

* <mrou>DIC</mrou> : Starts with the B cross-reference, or uses only the B cross-reference [unless K is passed in DIC(0)].
* <mentry>IX^DIC</mentry> : Starts with the cross-reference you specify, or uses only the cross-reference you specify.
* <mentry>MIX^DIC1</mentry> : Uses the set of cross-references you specify.

FILE 19

2013-04-22T17:06:05Z

NeilArmstrong: aDDED A GLOSSARY LINK TI FILE ~

Information in this [[FILE~|FILE]]is used to drive the menu system. Options are
created, associated with others on menus, locked, set out-of-order, assigned
prohibited times or devices, or given entry/exit actions. The Edit Options of
Menu Management should be used (instead of VA FileMan) so that the global root
(DIC) and other such fields are given the correct values. Options may be
tailored by setting FileMan variables via this [[file~|FILE]]. The Order Enter/Results
Reporting package is accessed by using the appropriate option type. It is
cross-referenced by name, menu text, uppercase menu text, type, item, synonym,
help frame, out-of-order message, lock, prohibited times, restricted devices,
and priority.

[[Category: FILE]]

FILE 200

2013-04-20T17:26:21Z

NeilArmstrong: Added a glossary link to File~

This [[file~|File]] contains data on employees, users, practitioners, etc. who were
previously in [[File~|File]]s 3,6,16 and others.

---

Packages must check with the KERNEL developers to see that a given
number/namespace is clear for them to use.

* Field numbers 53-59.9 reserved for Pharm. & Nodes and X-ref 'PS*'.
* Field numbers 70-79.9 reserved for Radiology & Nodes and X-ref 'RA*'.
* Field numbers 720-725 reserved for DSSM & Nodes and X-ref 'EC*' and 'AEC*'.
* Field numbers 740-749.9 reserved for QA & Nodes and X-ref 'QA*'.
* Field numbers 654-654.9 reserved for Social work & Node 654 and X-ref 'SW*'.
* Field numbers 500-500.9 reserved for mailman & Node 500 and X-ref 'XM*' and 'AXM*'.

[[Category: FILE]]

I installed Vista under Microsoft Windows using InterSystems Cache using a CACHE.DAT file. Do I now have the CPRS program?

2013-04-18T21:01:08Z

NeilArmstrong: Added a glossary link to File~

I installed Vista under Microsoft Windows using InterSystems Cache using a CACHE.DAT [[file~|File]]. Do I now have the [[CPRS~|CPRS]] program?

No.

{{:CPRS Executable Details}}

[[Category:FAQ]]

DRUG INGREDIENTS File~

2013-04-10T16:43:29Z

NeilArmstrong: Added a glossary link to file~

; DRUG INGREDIENTS [[File~|file]]
: [[File~|file]] #50.416. A [[file~|file]] that contains individual generic drugs which are components of various drug products.

Source: '''Pharm: National Drug [[File~|file]] V. 4.0 Technical Manual'''
----
[[Category:Pharm: National Drug File (NDF)]]
{{Category:Glossary}}
[[Category:Glossary]]

CLINIC DEFINITION File~

2013-04-10T16:41:16Z

NeilArmstrong: Added a glossary link to file~

; CLINIC DEFINITION [[File~|file]]
: [[File~|file]] #53.46. This [[file~|file]] is used in conjunction with Inpatient Medications for Outpatients (IMO) to give the user the ability to define, by clinic, default stop dates, whether to auto-dc IMO orders, and whether to send IMO orders to BCMA.

Source: '''Inpatient Medications V. 5.0 Pharmacist’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

WARD LOCATION File~

2013-04-10T16:39:53Z

NeilArmstrong: Added a glossary link to file~

; WARD LOCATION [[File~|file]]
: [[File~|file]] #42. This [[file~|file]] contains all of the facility ward locations and their related data, i.e., Operating beds, Bed section, etc. The wards are created/edited using the Ward Definition option of the ADT module.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

WARD GROUP File~

2013-04-10T16:38:49Z

NeilArmstrong: Added a glossary link to file~

; WARD GROUP [[File~|file]]
: [[File~|file]] #57.5. This [[file~|file]] contains the name of the ward group, and the wards included in that group. The grouping is necessary for the pick list to be run for specific carts and ward groups.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

PHARMACY SYSTEM File~

2013-04-09T17:48:15Z

NeilArmstrong: Added a glossary link to file~

; PHARMACY SYSTEM [[File~|file]]
: File #59.7. This file contains data that pertains to the entire Pharmacy system of a medical center, and not to any one site or division.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

MEDICATION ROUTES File~

2013-04-09T17:46:56Z

NeilArmstrong: Added a glossary link to file~

; MEDICATION ROUTES [[File~|file]]
: File #51.2. This file contains medication route names. The user can enter an abbreviation for each route to be used at their site. The abbreviation will most likely be the Latin abbreviation for the term.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

MEDICATION INSTRUCTION File~

2013-04-09T17:45:29Z

NeilArmstrong: Added a glossary link to file~

; MEDICATION INSTRUCTION [[File~|file]]
: File #51. This file is used by Unit Dose and Outpatient Pharmacy. It contains the medication instruction name, expansion, and intended use.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

MEDICATION ADMINISTERING TEAM File~

2013-04-09T17:43:58Z

NeilArmstrong: Added a glossary link to file~

; MEDICATION ADMINISTERING TEAM [[File~|file]]
: File #57.7. This file contains wards, the teams used in the administration of medication to that ward, and the rooms/beds assigned to that team.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

IV STATS File~

2013-04-09T17:42:54Z

NeilArmstrong: Added a glossary link to file~

; IV STATS [[File~|file]]
: [[File~|file]] #50.8. This [[file~|file]] contains information concerning the IV workload of the pharmacy. This [[file~|file]] is updated each time the Compile IV Statistics option is run and the data stored is used as the basis for the AMIS (IV) report.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]

IV SOLUTIONS File~

2013-04-09T17:40:48Z

NeilArmstrong: Added a glossary link to file~

; IV SOLUTIONS [[File~|file]]
: [[File~|file]] #52.7. This [[file~|file]] contains drugs that are used as primary solutions in the IV room. The solution must already exist in the DRUG [[file~|file]] (#50) to be selected. Data in this [[file~|file]] includes: drug generic name, print name, status, drug information, synonym(s), volume, and electrolytes.

Source: '''Inpatient Medications V. 5.0 Nurse’s User Manual'''
----
[[Category:Pharm: Inpatient Medications]]
{{Category:Glossary}}
[[Category:Glossary]]