Kernel
Assigning Person Class to Providers
User Guide
Patch Supplement: XU*8.0*27, 377, and 531
Version 8.0
August 1996
Revised February 2014
Department of Veterans Affairs (VA)
Office of Information and Technology (OIT)
Product Development (PD)
iii
Revision History
Table 1. Documentation revision history
Date / Revision / Description / Author /02/10/2014 / 4.0 / Tech Edits:
· Reformatted document to follow current template and style guide.
· Updated/Merged procedural steps in the "Enter/Edit Person Class Data" section.
· Added the "Identify Providers with Inactive Person Class Entries" section.
· Added the "Special Handling—Correcting Person Class Data" section.
· Added tables for Kernel Patch XU*8.0*531 in "Appendix A—Person Class Codes: New, Updated, Inactivated, and Reactivated."
· Added new "Appendix B—Printing VA Person Class Data."
· Added references to Kernel Patch XU*8.0*531 throughout.
· Added references to other Taxonomy Code websites throughout.
· Deleted the "Developer's Guide" section from this document, since that same information is included in the Kernel Developer's Guide.
· Deleted the "Systems Management Guide", "Implementation and Maintenance," and "Software Product Security" sections from this document, since that information is included in the Kernel Technical Manual. / · Enterprise System Engineering (ESE): P. H.
· Developer: B. T.
· Technical Writer: T. B.
05/31/2006 / 3.1 / Assigning Person Class to Providers Patch Supplement renamed and updated based on Kernel Patch XU*8.0*377 and feedback from developer, Ba Tran.
This version also includes content updates as per E. F.
NOTE: The original Person Class Kernel Patch was XU*8.0*27 released on 08/14/1996. / Maintenance Development Team, Oakland, CA OIFO:
· Project Manager: J. Sch.
· Developer: B. T.
· SQA: G. S.
· Technical Writer: T. B.
01/27/2005 / 2.0 / Reformatted document to follow ISS Style Guide.
Reviewed document and edited for the "Data Scrubbing" and the "PDF 508 Compliance" projects.
Data Scrubbing—Changed all patient/user TEST data to conform to HSD&D standards and conventions as indicated below:
· The first three digits (prefix) of any Social Security Numbers (SSN) start with "000" or "666."
· Patient or user names are formatted as follows: KRNPATIENT,[N] or KRNUSER,[N] respectively, where the N is a number written out and incremented with each new entry (e.g.,KRNPATIENT, ONE, KRNPATIENT, TWO, etc.).
· Other personal demographic-related data (e.g.,addresses, phones, IP addresses, etc.) were also changed to be generic.
PDF 508 Compliance—The final PDF document was recreated and now supports the minimum requirements to be 508 compliant (i.e.,accessibility tags, language selection, alternate text for all images/icons, fully functional Web links, successfully passed Adobe Acrobat Quick Check). / Technical Writer: T. B.
08/1996 / 1.0 / Initial Assigning Person Class to Providers Patch Supplement (i.e.,Kernel Patch XU*8.0*27) documentation creation. / Kernel Development Team, San Francisco, CA OIFO
Patch Revisions
For the current patch history related to this software, see the Patch Module on FORUM.
v
February 2014 Assigning Person Class to Providers, Supplement to Patch Description
Kernel Patches XU*8.0*27 & 377
Contents
Contents
Revision History iii
Figures and Tables ix
Orientation xi
1 Introduction 1
1.1 Overview 1
1.2 HCFA Provider Codes 2
1.3 Interfaces 2
2 Enter/Edit Person Class Data 3
2.1 Identify All Active Providers 3
2.1.1 Overview 3
2.1.2 Procedure 4
2.2 Identify Providers with Inactive Person Class Entries 5
2.2.1 Overview 5
2.2.2 Procedure 5
2.3 Assign Person Class to Providers 6
2.3.1 Overview 6
2.3.2 Procedure 6
2.4 Deactivate/Reactivate a User 10
3 Special Handling—Correcting Person Class Data 11
3.1 Removing Person Class Entries 11
3.2 Reactivating Person Class Entries 12
3.2.1 Overview 12
3.2.2 Procedure 12
3.3 Editing Reactivated Person Class Data 15
4 Appendix A—Person Class Codes: New, Updated, Inactivated, and Reactivated 17
4.1 Person Class Code Changes 17
4.2 New Person Class Codes 18
4.2.1 Patch XU*8.0*377 18
4.2.2 Patch XU*8.0*531 36
4.3 Updated Person Class Codes 37
4.4 Inactivated Person Class Codes 39
4.4.1 Patch XU*8.0*377 39
4.4.2 Patch XU*8.0*531 55
4.5 Reactivated Person Class Codes 56
5 Appendix B—Printing VA Person Class Data 57
5.1 Report Sorted by Provider Type 57
5.2 Report Sorted by VA Code 60
5.3 Report of Classifications Only 62
Glossary 63
Index 65
August 1996 Assigning Person Class to Providers, Supplement to Patch Description xv
Revised February 2014 Kernel Patches XU*8.0*27, 377, and 531
Contents
Figures and Tables
Figures
Figure 1. User PC build Print option—Sample user dialogue and report 4
Figure 2. List Inactive Person Class Users option—Sample user dialogue and report 5
Figure 3. Person Class Edit option—Sample user dialogue 6
Figure 4. Edit of Person Class ScreenMan form—Displaying current Person Class data for a provider 7
Figure 5. Edit of Person Class ScreenMan form—Adding a new specialty (1 of 3) 8
Figure 6. Edit of Person Class ScreenMan form—Adding a new specialty (2 of 3) 9
Figure 7. Edit of Person Class ScreenMan form—Adding a new specialty (3 of 3) 9
Figure 8. Retrieving the IEN for the Person Class file entry to be reactivated 12
Figure 9. Setting Person Class file entry to "a" (Active) 12
Figure 10. Stuffing the X12 CODE and deleting the DATE INACTIVATED fields 13
Figure 11. Adding the entry using the Person Class Edit option 13
Figure 12. Editing the entry fields: STATUS, DATE INACTIVATED, and X12 CODE 14
Figure 13. Edit an Existing User option (Screen 3)—Sample user dialogue 15
Figure 14. Printing Person Class File Entries—Sorted by Provider Type: Sample user dialogue 58
Figure 15. Person Class List—Sample report 59
Figure 16. Printing Person Class File Entries—Sorted by VA Code: Sample user dialogue 61
Figure 17. Printing Person Class File Entries—Classification codes: Sample user dialogue 62
Tables
Table 1. Documentation revision history iii
Table 2. Documentation symbol descriptions xii
Table 3. New Person Class Codes—Kernel Patch XU*8.0*377 18
Table 4. New Person Class Codes—Kernel Patch XU*8.0*531 36
Table 5. Updated Person Class Codes—Kernel Patch XU*8.0*531 37
Table 6. Inactivated Person Class Codes—Kernel Patch XU*8.0*377 39
Table 7. Inactivated Person Class Codes—Kernel Patch XU*8.0*531 55
Table 8. Reactivated Person Class Codes—Kernel Patch XU*8.0*377 56
August 1996 Assigning Person Class to Providers, Supplement to Patch Description xv
Revised February 2014 Kernel Patches XU*8.0*27, 377, and 531
Orientation
Orientation
How to Use this Manual
Throughout this Assigning Person Class to Providers User Guide (i.e.,Patch Supplement for Kernel Patches XU*8.0*27, 377, and 531), advice and instructions are offered regarding the use of the Assigning Person Class to Providers and the functionality it provides for Veterans Health Information Systems and Technology Architecture (VistA).
REF: Consult the Kernel documents for the following information related to the Assigning Person Class to Providers software (i.e.,Kernel Patches XU*8.0*27, 377, and 531):
· Kernel Technical Manual—Implementation and maintenance for Assigning Person Class to Providers (e.g., routines, files, options, interfaces, software product security)
· Kernel Developer's Guide—Application Program Interfaces (APIs).
All Kernel documentation is available on the VA Software Document Library (VDL) at: http://www.va.gov/vdl/application.asp?appid=10
Intended Audience
The intended audience of this manual is the following stakeholders:
· Users responsible for assigning person class to providers.
· Product Development (PD)—VistA legacy development teams.
· Information Resource Management (IRM)—System administrators at Department of Veterans Affairs (VA) sites who are responsible for computer management and system security on the VistA M Servers.
· Product Support (PS)—Personnel who support Kernel-related products.
Legal Requirements
CAUTION: To protect the security of VistA systems, distribution of this software for use on any other computer system by VistA sites is prohibited. All requests for copies of Kernel and Kernel-related products for non-VistA use should be referred to the VistA site's local Office of Information Field Office (OIFO).
Otherwise, there are no special legal requirements involved in the use of Kernel.
Disclaimers
This manual provides an overall explanation of the use, maintenance, and implementation of the Assigning Person Class to Providers software (Kernel Patches XU*8.0*27, 377, and 531); however, no attempt is made to explain how the overall VistA programming system is integrated and maintained. Such methods and procedures are documented elsewhere. We suggest you look at the various VA home pages on the Internet and VA Intranet for a general orientation to VistA. For example, go to the Office of Information and Technology (OIT) VistA Development Intranet Website.
DISCLAIMER: The appearance of any external hyperlink references in this manual does not constitute endorsement by the Department of Veterans Affairs (VA) of this Website or the information, products, or services contained therein. The VA does not exercise any editorial control over the information you may find at these locations. Such links are provided and are consistent with the stated purpose of this VA Intranet Service.
Documentation Conventions
This manual uses several methods to highlight different aspects of the material:
· Various symbols are used throughout the documentation to alert the reader to special information. The following table gives a description of each of these symbols:
Table 2. Documentation symbol descriptions
Symbol / Description // NOTE/REF: Used to inform the reader of general information including references to additional reading material.
/ CAUTION/RECOMMENDATION/DISCLAIMER: Used to caution the reader to take special notice of critical information.
· Descriptive text is presented in a proportional font (as represented by this font).
· Conventions for displaying TEST data in this document are as follows:
o The first three digits (prefix) of any Social Security Numbers (SSN) will begin with either "000" or "666".
o Patient and user names will be formatted as follows: [Application Name]PATIENT,[N] and [Application Name]USER,[N] respectively, where "Application Name" is defined in the Approved Application Abbreviations document and "N" represents the first name as a number spelled out and incremented with each new entry. For example, in Kernel (KRN) test patient and user names would be documented as follows: KRNPATIENT,ONE; KRNPATIENT,TWO; KRNPATIENT,THREE; etc.
· "Snapshots" of computer commands and online displays (i.e.,screen captures/dialogues) and computer source code, if any, are shown in a non-proportional font and may be enclosed within a box.
· Sample HL7 messages, "snapshots" of computer online displays (i.e.,roll-and-scroll screen or character-based screen captures/dialogues) and computer source code, if any, are shown in a non-proportional font and enclosed within a box.
· User's responses to online prompts will be bold typeface and highlighted in yellow (e.g.,<Enter>).
· Emphasis within a dialogue box will be bold typeface and highlighted in blue (e.g.,STANDARD LISTENER: RUNNING).
· Some software code reserved/key words will be bold typeface with alternate color font.
· References to "<Enter>" within these snapshots indicate that the user should press the <Enter> key on the keyboard. Other special keys are represented within < > angle brackets. For example, pressing the PF1 key can be represented as pressing <PF1>.
· Author's comments are displayed in italics or as "callout" boxes.
NOTE: Callout boxes refer to labels or descriptions usually enclosed within a box, which point to specific areas of a displayed image.
· This manual refers to the M programming language. Under the 1995 American National Standards Institute (ANSI) standard, M is the primary name of the MUMPS programming language, and MUMPS will be considered an alternate name. This manual uses the name M.
· Descriptions of direct mode utilities are prefaced with the standard M "" prompt to emphasize that the call is to be used only in direct mode. They also include the M command used to invoke the utility. The following is an example:
D ^XUP
· All uppercase is reserved for the representation of M code, variable names, or the formal name of options, field/file names, and security keys (e.g.,the XUPROGMODE security key).
Documentation Navigation
This document uses Microsoft® Word's built-in navigation for internal hyperlinks. To add Back and Forward navigation buttons to your toolbar, do the following:
1. Right-click anywhere on the customizable Toolbar in Word 2007 (not the Ribbon section).
2. Select Customize Quick Access Toolbar from the secondary menu.
3. Press the drop-down arrow in the "Choose commands from:" box.
4. Select All Commands from the displayed list.
5. Scroll through the command list in the left column until you see the Back command (green circle with arrow pointing left).
6. Click/Highlight the Back command and press Add to add it to your customized toolbar.
7. Scroll through the command list in the left column until you see the Forward command (green circle with arrow pointing right).
8. Click/Highlight the Forward command and press Add to add it to your customized toolbar.
9. Press OK.
You can now use these Back and Forward command buttons in your Toolbar to navigate back and forth in your Word document when clicking on hyperlinks within the document.
NOTE: This is a one-time setup and will automatically be available in any other Word document once you install it on the Toolbar.
How to Obtain Technical Information Online
Exported VistA M Server-based software file, routine, and global documentation can be generated through the use of Kernel, MailMan, and VA FileMan utilities.
NOTE: Methods of obtaining specific technical information online will be indicated where applicable under the appropriate section.
REF: For further information, see the Kernel Technical Manual.
Help at Prompts
VistA M Server-based software provides online help and commonly used system default prompts. Users are encouraged to enter question marks at any response prompt. At the end of the help display, you are immediately returned to the point from which you started. This is an easy way to learn about any aspect of VistA M Server-based software.
Obtaining Data Dictionary Listings
Technical information about VistA M Server-based files and the fields in files is stored in data dictionaries (DD). You can use the List File Attributes option on the Data Dictionary Utilities submenu in VA FileMan to print formatted data dictionaries.
REF: For details about obtaining data dictionaries and about the formats available, see the "List File Attributes" chapter in the "File Management" section of the VA FileMan Advanced User Manual.
Assumptions
This manual is written with the assumption that the reader is familiar with the following:
· VistA computing environment: