QCPR Database Maintenance Function Reference · QuadraMed® CPR Database Maintenance Function Reference iv QuadraMed Corporation 20 - Wolters Kluwer Update Mapping RxNorm Codes Utility

QuadraMed® CPRDatabase Maintenance

Function Reference

Client Support

Government Program Support

WarningThe laboratory information system module of the QuadraMed CPR (QCPR) product is not designed for, nor is it intended for use in, a blood banking establishment. QuadraMed does not support, and disclaims any liability for, any use of the QCPR product for such purpose. This means that the intended use of QCPR does not include any blood banking functions whatsoever, which functions include by way of example, but are in no way limited to, the following:

Documentation – Including pre-transfusion testing (i.e., readings), outcome of testing (i.e., interpretations), transfusion of blood products, computer assisted evaluation of data, and unit number and blood type as they relate to any of the above documentations.

Inventory tracking units

Labels for blood products

Converting antibody/transfusion history card information

Donor processing

In no event will QuadraMed or any person or company acting on its behalf be liable for any direct, indirect, special, incidental, or consequential damages, loss (including, without limitation, loss of profit), or personal injury arising from the supply or use of QCPR to perform the above mentioned or any other blood banking functions or to support a blood banking establishment, or arising from the supply or use of any accompanying hardware and written materials for the purposes of supporting the above mentioned or any other blood banking functions.

Any questions regarding the use of QCPR should be directed to QCPR Customer Support.

QuadraMed Corporation Proprietary StatementThis material constitutes proprietary and trade secret information of the QuadraMed Corporation, and shall not be disclosed to any third party, nor used by the recipient except under the terms and conditions prescribed by the QuadraMed Corporation.

The trademarks, service marks, and logos of QuadraMed Corporation and others used herein are the property of QuadraMed or their respective owners.

QuadraMed Corporation Copyright StatementThis material is also protected by Federal Copyright Law and is not to be copied or reproduced in any form, using any medium, without the prior written authorization of the QuadraMed Corporation. However, the QuadraMed Corporation allows the printing of the Adobe Acrobat PDF files for the purposes of client training and reference.

Contents copyright © 2011 QuadraMed Corporation. All rights reserved.

Phone: 877.823.7263

E-Mail: [email protected]

Technical Support:

Phone: 800.257.0512


Application Training Support:

Phone: 800.257.0512


Software and PDFs of guides and other documentation are available for download on the client support website. CDs and printed materials are available for purchase. See http://www.quadramed.com/customer_service for more information.

QuadraMed Corporation iii

Revision List

The following list provides the most current revision number and date for each chapter in this manual.

CHAPTERREVISION NUMBER

DATE

01 - Application Database Initialization 5.0.0 5/06

02 - Procedure Transfer Out 5.3.10 3/92

03 - Procedure Transfer In 5.3.10 3/92

04 - Signon Message Editor 5.3.2 1/92

05 - Mass Procedure Security Modifier 5.3.40 10/92

06 - Table Editor for Specific Table 4.9.9 8/90

07 - Table Editor 5.0.14 3/91

08 - Mass Procedure Modifier 5.1.2 5/92

09 - Search for Menu Function 5.3.6 2/92

10 - Medical Code Load 5.5.24 10/93

11 - Screen Driver Color Editor 5.5.20 9/93

12 - Bogus Bed Initialization 5.5.4 5/93

13 - View WP Upload Transactions 5.0.0 5/06

14 - View Interface Transactions 5.9.8 9/95

15 - Load United Kingdom Mailing Codes 4.0.0 7/03

16 - Load HA/PCT of Residence 4.1.0 5/04

17 - Load UK Commissioning Data 5.0.2 4/07

18 - View Interface Transactions, Status & I/O 5.2.0 6/11

19 - Growth Chart Percentile Load Utility 5.2.0 6/11

QuadraMed® CPR Database Maintenance Function Reference

iv QuadraMed Corporation

20 - Wolters Kluwer Update Mapping RxNorm Codes Utility 5.2.0 6/11

CHAPTERREVISION NUMBER

DATE

Copyright © 2011 QuadraMed Corporation

Table of Contents

Revision List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Chapter 1 Application Database Initialization

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Initialize Entire Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Initialize Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Initialize Individual Visits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Procedure Transfer Out

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Directory Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Transfer Out Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3 Procedure Transfer In

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Directory Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14


vi QuadraMed Corporation

Mapping Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Load Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 4 Signon Message Editor

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Current Sign-on Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Standard Sign-on Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 5 Mass Procedure Security Modifier

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Modifying All Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Modifying Specific Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Mass Modifier Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 6 Table Editor for Specific Table

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Disable 'Live System' Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table of Contents

QuadraMed Corporation vii

Chapter 7 Table Editor

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Table Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 8 Mass Procedure Modifier

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Parameter Definition Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Mass Changes Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Mass Change Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 9 Search for Menu Function

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Function Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Menu Function Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Menu Tree Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 10 Medical Code Load

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


viii QuadraMed Corporation

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44View Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Add Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 11 Screen Driver Color Editor


Chapter 12 Bogus Bed Initialization


Chapter 13 View WP Upload Transactions

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Facility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Document Options Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Select Document to View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Specify View by Visit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Header Line Fields Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Interface(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Facility(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Employee(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Include Unknown? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Default Current User? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Table of Contents

QuadraMed Corporation ix

Chapter 14 View Interface Transactions

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Select Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Current Operational Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Interface(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 15 Load United Kingdom Mailing Codes

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Loading the Complete File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Loading the Update File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 16 Load HA/PCT of Residence

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 17 Load UK Commissioning Data

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81


x QuadraMed Corporation

Chapter 18 View Interface Transactions, Status, and I/O

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Select Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Select Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Interface Message Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Validate Output File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

How to …Validate an output file using a hash file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Push Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Interface(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Allow Interface Up/Down? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Allow Message Resubmit/Resend? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Enable Device Access? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Initial Display Errors Only?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Force Up/Down Comment? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Allow Mark as Reviewed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 19 Growth Charts Percentile Load Utility

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Percentile Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

How to …Run Percentile Load Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

How to …Set up the Growth Charts Percentile Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 20 Wolters Kluwer Update Mapping RxNorm Codes Utility

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Running Wolters Kluwer Update Mapping RxNorm Codes Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

How to …Run the Wolters Kluwer Update Mapping RxNorm Codes Utility . . . . . . . . . . . . . . . . . . . . . . . 104

Table of Contents

QuadraMed Corporation xi

Viewing the Output for Wolters Kluwer Update Mapping RxNorm Code Utility . . . . . . . . . . . . . . . . . . 105How to …

View the Output for Wolters Kluwer Update Mapping RxNorm Code Utility. . . . . . . . . . . . . . . . 105

Push Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106


xii QuadraMed Corporation

QuadraMed Corporation 1

Chapter 1

Application Database Initialization

OverviewThe Application Database Initialization menu function is used to delete all or portions of the patient database. This process is commonly referred to as an ainit. The patient database is the information that has been entered into the QuadraMed Computerized Patient Records (QCPR) System that relates to a patient’s registration, visit, and event data. The patient database is divided into the following hierarchical levels:

Registration informationVisit informationEvent information

The patient database on a non-Production, non-live System is created for the purposes of demonstration, education, database building, and System validation. Unlike the patient database generated on a live System, which contains actual patient records, the database created for a non-live System is strictly fictitious and may need to be deleted periodically due to disc space limitations, application enhancements, or database update considerations. This menu function defines the set of patient information that is to be deleted.

Function Attributes

Once information is deleted using this menu function, it cannot be retrieved or restored. Therefore, this menu function should be run only on non-live Systems.

Table Relationship Links TO other tables FROM Application Database Initialization menu function:

None

Patient Identification Menu Function

Not required


2 QuadraMed Corporation

DescriptionOnce the Applications Database Initialization menu function is accessed, the System displays the following window that allows the entire database, a specific area, or an individual visit to be initialized as shown below.

The following buttons display on the AINIT Option Screen:

Department Usage Information ServicesInformation services use this menu function to delete patient information in order to prepare for database enhancements or updates or to increase disc space. This menu function is considered an internal utility and should be accessed only by Database System Managers and QuadraMed personnel.

BUTTON DESCRIPTION

(E) Initialize Entire Database Deletes all information. Refer to Initialize Entire Database on page 3.

(A) Area Deletes all information for all patients on a specific unit. Refer to Initialize Area on page 3.

(V) Individual Visit Deletes individual patient information. Refer to Initialize Individual Visits on page 4.



Initialize Entire DatabaseAll the patient registration, visit, and event information defined in the database can be deleted by clicking the (E) Initialize Entire Database button. When this button is clicked, the System prompts whether to delete all registration demographic information. The System defaults to no. Clicking (Y) Yes at this prompt causes the System to delete the registration, visit, and event information for all patients in the database. Once the initialization is accepted and completed, no patient records exist on the System. This process, relative to other initialization (that is, ainit) processes, takes the most time to complete and deletes the most data.

Choosing not to delete all registration information (that is, clicking (N) No at the prompt) causes the System to delete only visit and event information for all patients. The registration information for all patients remains intact. Once the initialization is accepted and completed, only patient registration information remains in the database.

Initialize AreaThe patient information defined for all patients on a specific unit can be deleted by clicking the (A) Area button. This initialization process is facility-specific. When the user chooses to initialize an area, the System prompts for an initialization location to be entered. Clicking the Expand button displays a list of area locations that have beds defined. Only those locations that have the Area Table, âfa, Sub-area or Sub-sub-area level, Lookup Flags field, Bed? subfield defined as yes display. When an area is selected, the System prompts whether the transaction mode is disabled during the ainit. The System defaults to no, which enables the transaction mode.

When the transaction mode is enabled, the System performs the deletion process without actually deleting any data from the disc. Once the process is complete, all the data from the disc is deleted at one time.

When the transaction mode is disabled, all deletions occur directly from the disc. If an error occurs during the initialization, the System stops the ainit. In this case, there is a risk that some of the data that was supposed to be deleted, is not completely deleted. Therefore, it is recommended that the transaction mode be enabled whenever this menu function is run.

When the transaction mode is either enabled or disabled, the System prompts whether to delete visit or order comm event information.

When the entire database is deleted, the System also deletes any templates created for a resource in the Resource Schedule Maintenance menu function. All templates must be re-defined and activated after the initialization is complete.



The following buttons are available:

When the initialization is accepted, the System deletes the specified data.

Initialize Individual VisitsA specific patient’s information can be deleted by clicking the (V) Individual Visit button. This initialization process is facility-specific and takes the least amount of time to complete. When the user chooses to delete an individual visit, the System prompts for a patient and visit to be identified. Visits can only be deleted one at a time. When a visit is selected, the System prompts whether the transaction mode is disabled during the ainit. The System defaults to no, which enables the transaction mode.

When the transaction mode is enabled, the System performs the deletion process without actually deleting any data from the disc. Once the process is complete, all the data from the disc is deleted at one time.

When the transaction mode is disabled, all deletions occur directly from the disc. If an error occurs during the initialization, the System stops the ainit. In this case, there is a risk that some of the data that was supposed to be deleted is not completely deleted. Therefore, it is recommended that the transaction mode be enabled whenever this menu function is run.

When the transaction mode is either enabled or disabled, the System prompts whether to delete visit information or order comm events. The following buttons are available:

When the initialization is accepted, the System deletes the specified data.

BUTTON DESCRIPTION

(D) Delete Visit Causes the System to delete both the visit and event information for the patients in the specified area.

(E) Delete Order Comm Events Causes the System to delete the orders, events, and result documentation for non-admit events for the patients in the specified area. The patient visit information is left intact.

BUTTON DESCRIPTION

(D) Delete Visit Causes the System to delete both the visit and event information for the patient.

(E) Delete Order Comm Events Causes the System to delete the orders, events, and result documentation for non-admit events for the patient. The patient’s visit information is left intact.



Push ParametersNone




Chapter 2

Procedure Transfer Out

OverviewThe Procedure Transfer Out menu function is used to copy and transfer procedure-related portions of a QuadraMed® CPR database from one facility to another. Specifically, this menu function copies the database and creates an AOS file. This AOS file can be transferred by magnetic tape or over the network to another QuadraMed CPR System. After the information is transferred to the other facility, the Procedure Transfer In menu function is used to integrate the AOS file into the recipient QuadraMed CPR database. For procedures to be transferred from one facility to another, the QuadraMed CPR revision numbers and UMOS® revision numbers must be exactly the same on both Systems.

The process of performing a procedure transfer out involves the following steps:

Identify the facility from which procedures are copied.

Identify the directory into which procedures are copied.

Identify procedures to be copied.

Function AttributesTable Relationship Links TO other tables FROM Procedure Transfer Out menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to copy procedures from one facility on a customer system to another facility, facilitating the database development process.



DescriptionOnce the Procedure Transfer Out menu function is accessed, the QuadraMed CPR System displays a list of Facility Options. Facility Options are defined in the Facility Table, âff. The System prompts for selection of the facility from which the procedure-related database should be transferred.

Directory IdentificationOnce a facility is selected, the System displays the Directory Options Screen as shown below. This screen displays a list of previously defined Product/Subdirectory Options. These Product/Subdirectory Options are directories that have already been created for transfer out procedures. The following processing options are available:

Select product/subdirectoryAllows procedures to be added or deleted from the selected directory. When a product/subdirectory is selected, the System displays the Procedure Options Screen. The following processing options are available:

Add – Allows a procedure(s) to be added to the list. When this processing option is chosen, the System prompts for the internal procedure code(s) to be entered. When the procedure code is entered, the System displays the internal number and procedure name on the Procedure Options Screen. Procedures are defined in the Procedure Table, ^t. The System automatically assigns an internal number to each procedure defined in the Procedure Table, ^t. The selected procedures display in alphabetical order.



Pressing the EXPD key allows procedures to be identified by a partial name match. When a partial name match is entered, the System displays all procedures that match the entered partial name. When a procedure(s) is selected, the System displays the internal number and procedure name on the Procedure Options Screen.

DeleteAllows a procedure(s) to be deleted from the list. Each delete request must be verified. After verification, the procedure(s) is removed from the Procedure Options Screen.

AddAllows a new directory to be created. When this processing option is chosen, the System prompts for the new product/subdirectory name. This name is entered as free-text. After the name is entered, pressing the ENTER key causes the System to display a Creating new directory! message. When the new directory is created, the System displays the Procedure Options Screen. For a complete description of the processing options available on this screen, refer to the add and delete processing options above.

DeleteAllows an existing directory to be deleted from the list of Product/Subdirectory Options. Each delete request must be verified. After verification, the System displays a Deleting directory! message and the option number of the selected directory flashes. The System removes the product/subdirectory from the Directory Options Screen.



Transfer Out ProcessingAfter the procedure(s) has been identified, pressing the ENTER key causes the System to display a Building cross reference message and begin the process of copying the procedures, some related database components, and cross references. The System displays a message as it copies each component showing exactly what is being performed.

During this process, the System is copying certain tables or table entries linked to the identified procedure(s). The following tables are copied completely and do not need to be mapped in the Procedure Transfer In menu function:

Equivalent Result Table, ^nt("er")

Generic Table Table, ^ntt

Order Entry Profile Table, ^nt("op")

Procedure Table, ^t

Result Entry Profile Table, ^nt("rp")

Result Storage Table, ^nt("rs")

Selection Screen/Tree Table, ^nts

When a table is copied, the System moves the entire result profile, order profile, and flag settings associated with the procedure being transferred out. Because these tables are copied, entries with the same name on the System to which these procedures are transferred are duplicates. When this occurs, the System displays a timestamp next to the new entry (e.g., X/General – Chest 013092001) on the receiving System.



A list of tables that cannot be copied but must be mapped when the procedure(s) is transferred onto another System is also created. Mapping allows table elements from the host System to be matched with elements on the receiving System. These entries can be viewed on the Procedure Transfer In menu function, Mapping Screen. Depending on the identified procedure(s), the following tables can display for mapping:

Anatomical Pathology Stain Table, ^nt("aps")

Assessment Screen Table, ^nt("as")

Auto DC Group Table, ^nt("adc")

Charge Category Table, ^nt("cc")

Charge Table, ^nt("c")

Chart Review Group Table, ^nt("cg")

Condition Selection Screen Table, ^nt("ocs")

Dosage Selection Screen Table, ^pt("d")

Duplicate Procedure Group Table, ^nt("dp")

Face Sheet Table, ^nt("fs") – displays on the Procedure Transfer In menu function, Mapping Screen as ^nt("fs") and ^nt("fs,o")

Folder Type Table, ^nt("trf")

Frequency Selection Screen Table, ^nt("f")



Kardex Group File Table, ^nt("kg")

Limited Scheduling Procedure Group Table, ^nt("rcpg")

Microbiology Workcard Batch Type Table, ^nt("mwbt")

Microbiology Workcard Planting Activity Table, ^nt("mwap")

Order Queue Routing Table, ^nt("oqr")

Order Schedule Group Table, ^nt("osg")

Product Category Table, ^pt("pc")

Product Table, ^pt("p")

Productivity Workload Code Table, ^nt("pw")

Resource Type Table, ^nt("rct")

Result Report Route Table, ^nt("rrr")

Result Verification Queue Table, ^nt("rq")

Route Table, ^pt("ro")

Scheduling Queue Table, ^nt("rcq")

Specimen Table, ^nt("sp")

Specimen Accession Label Table, ^nt("spl")

Specimen Collapsing Group Table, ^nt("spg")

Specimen Department Number Table, ^nt("spd")

Specimen Receiving Area Table, ^nt("spa")

Word Processor Selection Screen Table, ^nt("wps")

Work Count Group Table, ^nt("wcg")

Work Queue Table, ^nt("wq")

Workstation Table, ^nt("spw")

When the System has copied all the components to be transferred out, the System displays a Moving cross reference file. message and redisplays the Directory Options Screen.

Push ParametersNone


Chapter 3

Procedure Transfer In

OverviewThe Procedure Transfer In menu function is used to receive procedure-related portions of an QuadraMed CPR database from another facility. This menu function integrates an AOS file created in the Procedure Transfer Out menu function into a recipient QuadraMed CPR database. For procedures to be transferred from one facility to another, the QuadraMed CPR revision numbers and UMOS® revision numbers must be exactly the same on both Systems.

The process of performing a procedure transfer in involves the following steps:Identify the facility to which procedures are transferredIdentify the directory from which procedures are transferredBuild cross referenceLoad procedures

Function AttributesTable Relationship Links TO other tables FROM Procedure Transfer In menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to copy procedures from one facility or QuadraMed CPR System to another facility or QuadraMed CPR System, facilitating the database development process.



DescriptionOnce the Procedure Transfer In menu function is accessed, the QuadraMed CPR System displays a list of Facility Options. Facility Options are defined in the Facility Table, âff. The System prompts for selection of the facility to which the procedure-related database should be transferred.

Directory IdentificationOnce a facility is selected, the System displays the Directory Status Screen as shown below. This screen displays a list of directories created in the Procedure Transfer Out menu function, along with the current status of the directory. The following processing options are available:

Process directoryAllows the cross reference to be built for the selected directory or procedures/profiles to be loaded. When a directory is selected to process, and the current status is cross reference not loaded, the System prompts for verification to load the cross reference. The System defaults to no. When the user chooses to load the cross reference, the System displays a Loading cross reference! message. When this process is complete, or a directory is selected to process that has any other current status, the System displays the Process Options Screen as shown below. The load procedures/profiles Process Option displays starred out ( *** ) until the cross reference has been built.

When the user selects to build the cross reference, the System displays the Mapping Screen as shown below. This screen displays the following information:

INFORMATION DESCRIPTION

Table Name Displays the global name of the table from which database components were copied in the Procedure Transfer Out menu function.

Description Displays the table long name.

# Elements Displays the number of database components that need to be mapped for each procedure identified in the Procedure Transfer Out menu function for each table.

# Mapped Displays the number of database components that have been mapped.





All table elements must be mapped before they can be loaded onto the receiving System. For a complete description of mapping, see Mapping Table Entries on page 16.

DeleteAllows a directory to be deleted from the list of directory options. Each delete request must be verified. After verification, the System removes the directory from the Directory Status Screen.

Mapping Table EntriesMapping allows table elements from the host System to be matched with elements on the receiving System. For example, the host System contains a chart review group called X/Chest. When the receiving System has a chart review group called X/Chest, the elements can be mapped exactly. However, when the receiving facility uses a chart review group called X/Radiology, the X/Chest element from the host System can be mapped to the X/Radiology element on the receiving System. In addition, a new chart review group can be created on the receiving System to match the chart review group on the host System. When a table entry is selected to map, the following processing options are available:

Select element to mapWhen an element is selected, the System displays the Table Element Screen as shown below. This screen displays a list of table elements that need to be mapped for each procedure identified in the Procedure Transfer Out menu function. Selecting one of the elements to map causes the System to display a list of table elements that reside on the receiving System. The options that display depend on which table is being mapped.



When an equivalent option is chosen, the System redisplays the Table Element Screen with the chosen element under the Mapped Element column. When all elements on this screen have been mapped, pressing the ENTER key causes the System to redisplay the Mapping Screen. When all elements in a table have been mapped, that table displays in dim text on the Mapping Screen, indicating the mapping process is completed.

Table entryAllows the user to create a new element rather than using an existing element. When this processing option is chosen, the System accesses the particular table on the receiving System that was copied from the host System.

Once all elements have been mapped and all entries on the Mapping Screen display in dim text, pressing the ENTER key redisplays the Process Options Screen. The load procedures/profiles Process Option can now be selected.

Load ProceduresThe load procedures/profiles Process Option allows the procedures to be loaded onto the receiving System. When this Process Option is selected, the System prompts to verify the load of procedures/profiles. After verification, the System begins the process of loading the procedures. The System displays a message as it appends each table, displaying exactly what is being performed as shown below.



When all procedures/profiles have been loaded, the System exits this menu function and displays the menu options.

Push ParametersNone

The procedures are not available for use until the Order Entry Profile Table, ^nt("op"), order profile screens and the Result Entry Profile Table, ^nt("rp"), result profile screens have been rebuilt. The rebuild process is initiated automatically and is scheduled to be run according to System parameters defined in the System Parameter Table, ^%z, General Parameters level, Background Job Run Time field. For a complete description of rebuilding screens, see Chapter 3, Screen Drivers in the Introduction to CPR Tables.


Chapter 4

Signon Message Editor

OverviewThe Signon Message Editor menu function is used to display a message to all users when they sign onto the System. Messages can be created, stored and reused.

Function Attributes

DescriptionOnce the Signon Message Editor menu function is accessed, the QuadraMed® CPR System displays two Message Options (i.e., current and standard) and prompts for one to be selected.

Current Sign-on MessageThe current sign-on message displays to all users when they sign onto the System. When this option is selected, the System displays the Current Sign-on Message Screen (see figure below). The message can be changed or a new message can be created. The following processing options are available:

Table Relationship Links TO other tables FROM Signon Message Editor menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to define messages to alert users of changes to the System. Some facilities place their logo on the screen, while others display holiday-specific messages or facility news items.



Copy standardAllows a pre-defined (i.e., standard) message to be copied to the current message.

Selecting this processing option displays a list of Standard Message Options. Standard Message Options are defined under the Standard Sign-on Message(s) Option in this menu function. Once a message option is selected, the System displays the associated message along with a KEEP prompt. The message can be edited. Pressing the KEEP key copies and displays the selected standard message as the current sign-on message. Once copied, the System redisplays the Current Sign-on Message Screen.

Edit currentAllows the current message to be modified. When this processing option is chosen, the System moves the cursor to the message text. The current message can be edited using word processing editing tools. Pressing the KEEP key exits the word processor and returns to the Current Sign-on Message Screen.

Edit new messageSelecting this processing option removes the current sign-on message and allows a new sign-on message to be defined. The new current sign-on message is created using word processing editing tools. Pressing the KEEP key exits the word processor and returns to the Current Sign-on Message Screen.

The current sign-on message must be rebuilt before it displays to users when signing onto the System.

Chapter 4 Signon Message Editor


Standard Sign-on MessagesAllows sign-on messages to be created and maintained for future use. This feature is particularly useful for defining messages that are reused (e.g., messages that alert users of a recurring hospital activity).

Some facilities create holiday messages that display each year at the appropriate time, while others create the facility's logo.

Once the standard message option is chosen, the System displays a list of previously defined Standard Sign-on Message Options. The following processing options are available:

Select messageAllows an existing message to be edited. The message text is edited using word processing editing tools. Pressing the KEEP key exits the word processor and returns to the message display.

AddAllows a new standard message to be created. When this processing option is chosen, the System prompts for a message name. Once a message name is defined, the message text can be created using word processing editing tools. Pressing the KEEP key exits the word processor. The System prompts for acceptance of the new Standard Sign-on Message Option.

DeleteAllows an existing message to be deleted. Each delete request must be verified. After verification, the message is removed from the list of Standard Sign-on Message Options.

The Standard Sign-on Message must be rebuilt before it becomes available for use as the Current Sign-on Message.

Push ParametersNone




Chapter 5

Mass Procedure Security Modifier

OverviewThe Mass Procedure Security Modifier menu function is used to add or delete one or more security positions on groups of procedures defined in the Procedure Table, ^t. Order securities are arranged in the following hierarchical format, from lowest to highest:

Order entry

Take order

Originate order

Originate order w/active

Sign order

Any user that has take order security, or higher, automatically has the ability to perform the lower securities. For example, users who have take order security can also enter an order on behalf of another user; users who have originate order security can take and enter orders; and users who have sign order security can also originate, take, and enter orders.

Result securities are not arranged in a hierarchical format. Security can be assigned differently for each option.

Function AttributesTable Relationship Links TO other tables FROM Mass Procedure Security Modifier menu function:

None


Not required



DescriptionOnce the Mass Procedure Security Modifier menu function is accessed, the QuadraMed® CPR System displays a list of Facility Options and prompts for one to be selected. Facility Options are defined in the Facility Table, âff. After a facility has been selected, the System prompts to add or delete security. When adding or deleting security positions, the System prompts to modify all procedures or specific procedures.

Modifying All ProceduresChoosing to modify all procedures causes the System to apply the security changes defined in this menu function to all procedures in the Procedure Table, ^t, for the selected facility. When this processing option is chosen, the System displays the Procedure Security Definition Screen. This screen displays the following fields:

Department Usage Information ServicesInformation services use this menu function to implement security position changes on large numbers of procedures.

FIELD DESCRIPTION

Order Entry Security Defines the security position(s) that can enter a written order on behalf of another user, but cannot take a verbal order.

Take Order Security Defines the security position(s) that can take a verbal or telephone order.

Originate Order Security Defines the security position(s) that can write (i.e., author) an order, but cannot sign (i.e., activate) the order.

Originate Order w/Active Security

Defines the security position(s) that can write an order for this procedure which is active and can be performed, but the order is still required to be co-signed by a user with sign order security.

Sign Order Security Defines the security position(s) that can write an active order or sign (i.e., activate) an order written by someone with originate order security.

Result Security Defines the security position(s) that can result or document a procedure.

Cancel Security Defines the security position(s) that can cancel a procedure.

Cancel Reversal Security Defines the security positions that can reverse cancel (i.e., uncancel) a procedure.

Resolve Security Defines the security position(s) that can resolve a procedure. Resolving a procedure involves clearing an undocumented event/procedure from a work queue and the patient schedule, without performing the event.

Resolve Reversal Security Defines the security positions that can reverse a resolved (i.e., unresolve) procedure.



When one of these fields is selected, the System displays a list of Security Position Index Options. When a security position index is selected, the System displays the subindex or Security Position Options defined for the selected index. Multiple security positions can be selected. Security positions are defined in the Security Position Table, âet("sp"), and indexed in the Security Position Index Table, âet("spi").

Modifying Specific ProceduresChoosing to modify specific procedures allows the user to create a list of procedures to be modified. When this processing option is chosen, the System displays the Procedure Selection Definition Screen. The following fields can display on this screen:

Selection TypeDefines the identification method for identifying procedures in this menu function. This field can be defined as follows:

Procedures – Allows individual procedures to be selected for modification. Displays the Procedure(s) field for definition. The System defaults to procedure.

No Show Security Defines the security position(s) that can status an event as "no show". For a complete description of each field, see chapters, Order Security Screen and Documentation Security Screen, in the Procedure Table Reference.

FIELD DESCRIPTION



Chart review groups – Allows all procedures linked to the selected chart review group(s) to be modified. Displays the Chart Review Group(s) field for definition.

Kardex groups – Allows all procedures linked to the selected kardex group(s) to be modified. Displays the Kardex Group(s) field for definition.

Procedure(s)Allows securities to be modified for all procedures identified in this field. Procedures can be added by entering a partial procedure word(s) or procedure code. When a partial word is entered, the System displays all procedures matching the entered word(s). Once a procedure(s) is selected, it is added to the Procedure Selection Definition Screen. When the procedure code (i.e., internal number) is entered, the procedure is added to Procedure Selection Definition Screen. Procedures are defined in the Procedure Table, ^t. A procedure code is assigned by the System when a procedure is created in the Procedure Table, ^t. This procedure code displays in parentheses following the procedure name once the procedure is selected in the Procedure Table, ^t.

Chart Review Group(s)Allows securities to be modified for all procedures in the selected chart review group(s). When adding chart review groups, the System prompts for a partial name. When a partial name is entered, the System displays all chart review groups matching the entered name(s). Once a chart review group(s) is selected, it is added to Procedure Selection Definition Screen. Chart review groups are defined in the Chart Review Group Table, ^nt("cg"), and linked to each procedure in the Procedure Table, ^t, Chart Review Information Screen, Chart Review Group(s) field.



Kardex group(s)Allows securities to be modified for all procedures linked to the selected kardex group(s). When adding kardex groups, the System prompts for a partial name. When a partial name is entered, the System displays all kardex groups matching the entered name(s). Once a kardex group(s) is selected, it is added to the Procedure Selection Definition Screen. Kardex groups are defined in the Kardex Group File Table, ^nt("kg"), and linked to each procedure in the Procedure Table, ^t, Department Processing Screen, Kardex Group field.

When the list of procedures, chart review groups, or kardex groups is accepted, the System displays the Procedure Security Definition Screen. For a complete description of this screen, see Modifying All Procedures on page 24.

Mass Modifier CompletionWhen all security positions are defined and accepted, the System initiates a background job that implements the new securities for each procedure included on the list. When adding a security position(s), the System appends the selected security position(s) to the securities already defined for the procedure. When deleting a security position(s), the System searches for the security position(s) and only deletes the security when it is defined for the procedure.

For example, when a security position should be added to the No Show Security field of all procedures on the list, the System adds that security position to the securities already defined in the Procedure Table, ^t, Documentation Security Screen, No Show Security field. When the selected security position is already defined in the No Show Security field for a particular procedure, there is no change.

Similarly, when a security position should be deleted from the No Show Security field, the System only deletes the security position from the No Show Security field when it is defined for the procedure.

When a security field does not have a security position(s) defined, no additions or deletions are made to that security field. All security definitions for a procedure(s) cannot be cleared in this menu function.

Push ParametersNone




Chapter 6

Table Editor for Specific Table

OverviewThe Table Editor for Specific Table menu function is used to provide and/or limit database specialists' and users' access to specific database tables.

Function AttributesTable Relationship Links TO other tables FROM Table Editor for Specific Table menu function:

Table Editor Definition Table, âet


Not required

Department Usage Medical StaffMedical Staff can be given the responsibility of maintaining Physician information. They can maintain all or portions of the following tables:

Employee/Provider Table, âe Physician Group Table, âet("pg")Physician Service/Department/Specialty Table, âet("ps")Resident Service Table, âet("rs")

In order to provide appropriate security and control over these tables, each table can be linked to this menu function and placed on the medical administration menu as a separate menu option for authorized user access.

PersonnelPersonnel can be given the responsibility of maintaining the information in the Employee/Provider Table, âe. In order to provide appropriate security and control over this table, the Employee/Provider Table, âe, can be linked to this menu function and placed on the personnel menu for authorized user access.



DescriptionOnce the Table Editor for Specific Table menu function is accessed, the QuadraMed CPR System displays the first screen of the table that is linked to this menu function in the Table push parameter as shown below.

Normally, tables are maintained on a customer's Database System in order to prevent accidental changes on a Live System. When this menu function is accessed on a Live System, and the Disable 'Live System' Warning push parameter of this menu function is defined as no, the System displays a warning message. The user can then exit by pressing the BACK UP Key or proceed to the first screen of the table.

From the first screen of the table, all of the creation, editing and deletion options associated with the table can be performed.

Push Parameters

Table

Defines which table can be accessed using this menu function. Table Options are defined in the Table Editor Definition Table, âet, which is a QuadraMed-maintained table.

Chapter 6 Table Editor for Specific Table


Disable 'Live System' Warning

Defines whether or not the Live System Warning Message is disabled when this menu function is accessed on a Live System. Accepting the default value of no causes the System to display the Live System Warning Message when this menu function is accessed on a Live System. When this push parameter is defined as yes, the System suppresses the Live System Warning Message.




Chapter 7

Table Editor

OverviewThe Table Editor menu function is used to access the tables necessary to build and maintain the QuadraMed CPR System database. It allows database specialists to edit or view any table for which they have the appropriate security. The list of tables that display within this menu function varies according to the securities defined in the Table Editor Site Specific Security Table, âtes.

Function Attributes

DescriptionOnce the Table Editor menu function is accessed, the QuadraMed CPR System prompts for the identification of a table.

Table Relationship Links TO other tables FROM Table Editor menu function:

None


Not required

Command Key Menu Function?

Yes

Department Usage Information ServicesInformation Services use this menu function to access the tables to build and maintain the QuadraMed CPR System database.



Table IdentificationEach table is identified by a table name and a description. The table name is the actual QuadraMed CPR file identifier (e.g., ̂ nt("sp")). The description is composed of one or more words that describe the contents of the table. A table can be identified by entering a complete or partial name match on the table identifier (e.g., nt-). The System prompts for a table to be selected.

After a table has been selected, the System displays the contents of the table and allows it to be edited. Each table prompts for a set of processing options that are dependent upon the structure and contents of the table. For a complete description of each table, refer to the appropriate chapter(s) in the Table Reference Library.

Processing OptionsThe following processing options are available:

Push ParametersNone

The System displays those tables that the database specialist has security to edit or view. When no security is defined for a table, it can be edited.

PROCESSING OPTION DESCRIPTION

Edit Allows a defined table to be selected and edited. Some tables can only be edited by one database specialist at a time. The System locks the table and only allows another database specialist to view its contents. Some tables allow multiple database specialists to make edits on separate sections simultaneously. The System locks only those sections being edited.

Rebuild Allows the inverted file(s) and any screen(s) associated with a table to be rebuilt. Once the option is selected, the System prompts for the identification of a table. A table can be identified by entering the complete or partial table identifier name. After the table has been identified, the System prompts to specify what parts of the table definitions are to be rebuilt. The inverted files, screens or both can be specified to be rebuilt.

View Allows the contents of a table to be viewed. Once the option is chosen, the System prompts for the identification of a table. A table can be identified by entering the complete or partial table name. After the table has been identified, the System displays the contents of the table. When the partial name is used, the ENTER key can be pressed to return to the list of tables. The option numbers associated with the table are starred out ( *** ), preventing the fields from being accessed for editing.


Chapter 8

Mass Procedure Modifier

OverviewThe Mass Procedure Modifier menu function is used to change one or more fields for groups of similar procedures in the Procedure Table, ^t. This functionality is used to speed database development.

This menu function does not create new procedures. For a complete description of creating procedures, see the Procedure Table Reference.

Function Attributes

DescriptionOnce the Mass Procedure Modifier menu function is accessed, the System prompts for selection of a facility. Once a facility is selected, the System displays the Mass Procedure Modifier Parameter Definition Screen as shown below.

Table Relationship Links TO other tables FROM Mass Procedure Modifier menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to generate a procedure definition change on a large number of procedures at one time (e.g., when a large number of procedures are activated/inactivated).



Parameter Definition ScreenOnce the Mass Procedure Modifier Parameter Definition Screen displays, the System prompts the user to create a list of procedures to be modified. Each list is defined by a name that identifies the mass change procedure, a list of procedures to be changed and a print queue to which the list of modified procedures can be sent when the modifications are complete.

The list of procedures is maintained in the order in which the procedures were added. Procedures can be added to the list by any combination of methods accessed through the following processing options:


Procedure word(s) When a partial procedure word is entered, procedures matching the entered word(s) display. A procedure can be selected to be added to the list. Procedures names are defined in the Procedure Table, ^t.

Procedure code When the procedure code (i.e., internal number) for a procedure is entered, the procedure is added to the list. Procedure codes are assigned when the procedure is created in the Procedure Table, ^t.

Chart review group Displays a list of chart review groups for selection. When a chart review group is selected, all the procedures linked to that chart review group displays. One or more of these procedures can be selected to add to the list. Chart review groups are defined in the Chart Review Group Table, ^nt("cg"). For a complete description of chart review groups, see Chapter 1, Chart Review in the Patient Data Review Tables Reference.

Kardex group Displays a list of kardex groups for selection. When a kardex group is selected, the System displays a list of all the procedures linked to that kardex group. One or more of these procedures can be selected to add to the list. Kardex groups are defined in the Kardex Group File Table, ^nt("kg"). For a complete description of kardex groups, see Chapter 5, Kardex Group File Table, ^nt("kg") in the Order Entry Tables Reference.

Chapter 8 Mass Procedure Modifier


Mass Changes DefinitionOnce the list of procedures to be changed has been defined, the screens that define a procedure in the Procedure Table, ^t, display. The System uses the first procedure on the list as a template to define the changes to be made for all the procedures on the list. Changes made to the first procedure are implemented in all the listed procedures, when the changes are accepted.

Screens can be edited in the following manner:

AddAdding data to an empty field places the defined data in that field for all the listed procedures. When data is added to a field that is not empty in some of the listed procedures, the new data overwrites the data currently in that field in those procedures.

EditEditing the data in an already defined field imposes the changes on that field for all procedures. For example, if the order profile for the displayed procedure is P/Medications, and it is changed to P/IV Medications, it will become P/IV Medications in all procedures in the list.

DeleteDeleting the data from a field causes the field to be cleared in all procedures on the list, regardless of the data contained in that field. The first procedure on the list must have data in the field to be cleared.



Mass Change CompletionWhen all changes are defined and accepted, the System initiates a background job to file the changes on each procedure. A list of the procedures that were changed prints from the print queue specified when the list of procedures was defined. The System then prompts the user to indicate whether another mass change is to be initiated. When answered yes, the System restarts the change process; otherwise, the System returns to the menu from which it was selected.

Push ParametersNone


Chapter 9

Search for Menu Function

OverviewThe Search for Menu Function menu function is used to locate all occurrences of a specific menu function within a menu tree.

Function Attributes

DescriptionOnce the Search for Menu Function menu function is accessed, the QCPR System prompts for a menu function to be identified by selecting a function level or entering a partial name.

Table Relationship Links TO other Tables FROM Search for Menu Function menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to search for specific menu functions that are located on menu trees at their facility. This process allows all occurrences of a specific menu function to be located, for updating when new functionality is released.



Function LevelEach menu function is categorized based on the type of processes it can perform. These categories are called function levels. Within each function level, sublevel options further classify related menu functions. Additional sub-sublevels can also exist, with the final level ending at a menu function. Function levels, sublevels and sub-sublevels are defined in the Menu Function Table, âsmf. The System prompts for a menu function to be identified by selecting a function level. At any level, a partial name match can be entered.

Menu Function NameWhen the name of the menu function is known, it can be accessed directly by entering its name. A menu function can also be identified by a partial name match, where only a part of the menu function name is entered. A dash ( – ) replaces the unspecified portion of the name. A partial name match can include any portion of the menu function name. For example, when "-batch-" is entered, the System displays all menu functions that contain "batch" (that is, Batch Processor, Film/Chart Batch Request, Resource Schedule Batch, and so on).

Menu Tree IdentificationOnce a menu function is identified, the System prompts for the identification of the type of menu tree to be searched. The following types can be chosen:

QCPR (U)

Applications Utilities (A)

System Utilities (S)

Command Key (C)

The System defaults to uasc, which searches all menu types.

When the QCPR or Command Key menu type is chosen, the System prompts for a facility to be selected. Facilities are defined in the Facility Table, âff. Multiple facilities can be selected. After a facility is selected or when the Applications Utilities or System Utilities menu type is selected, the System scans the menus. Once the menu function has been located, the System displays the Menu Function Location Screen. This screen displays all locations of the identified menu function.

Every occurrence of the menu function displays. The location of the menu function in the menu tree hierarchy is displayed by a list of progressively indented menu options representing the menu hierarchy. The first item on the list is underlined, indicating the menu tree. Each subsequent level is indented and preceded by the number associated with the menu option at that level.

Paging icons indicate the PREV PAGE and/or NEXT PAGE keys can be pressed to view additional screens. The next page and/or previous page icons only display when there are more locations than can fit on one screen. Pressing the ENTER key terminates the menu location display.

Chapter 9 Search for Menu Function


Push ParametersNone




Chapter 10

Medical Code Load

OverviewThe Medical Code Load menu function is used to load new ICD-9 diagnosis/procedure tapes onto the QCPR System. In addition, effective start and stop dates for each ICD-9 diagnosis and/or procedure code can be defined in this menu function.

The ICD-9 system is a disease and procedure classification system developed to standardize the method by which health information is maintained. This classification system is widely accepted and utilized by all health care providers to provide a mechanism to retrieve data for research purposes as well as statistical analysis. The intention of the ICD-9 system is to provide a tool for use in the analysis of health services provided to patients in hospitals, clinics, departments, etc. For reimbursement purposes, the information contained on the tapes may be "grouped" against the facility's case mix provided by the Federal government.

The ICD-9 diagnosis system is used for statistical purposes and to index hospital records by disease and operations. The ICD-9 procedure system is a classification of therapeutic, diagnostic, and prophylactic procedures in medicine, covering surgery, radiology, laboratory, and other procedures.

The Medical Code Load menu function should be run on Development Systems and the files rolled to Production Systems.



Function Attributes

DescriptionOnce the Medical Code Load menu function is accessed, QCPR displays the Medical Code Load Screen. The Medical Code Load Screen displays the following information:

DateDisplays the date the load was created.

DescriptionDisplays the free-text description of the medical code load.

Status

Table Relationship Links TO other Tables FROM Medical Code Load menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to load new ICD-9 diagnosis/procedure tapes onto the QCPR System.



Displays the current status of the medical code load. A load can be viewed or added.

View LoadWhen the user selects a load to view, the System displays the Load Description Screen. This screen displays the load's status and audit trail information. The following fields display on this screen:

Last Edit IDDisplays the name of the employee who last edited the load information. This field is updated automatically by the System.

Last Edit TimeDisplays the date/time the load information was last edited. This field is updated automatically by the System.

DescriptionDisplays the free-text description of the medical code load.

Loader TypeDisplays the loader type. When adding a load, the System displays a list of hard-coded Loader Options. When this field is defined, the System displays the following additional fields for definition:

AOS NAME – Long Names

AOS NAME – Short Names

Initial Load?

Effective Date



StatusDisplays the status of the load. This field is updated automatically by the System. The following statuses can display:

In progress – Indicates the ICD-9 procedure/diagnosis tapes are currently being loaded onto QCPR.

Error – Indicates the load did not complete properly.

Complete – Indicates the load completed properly.

AOS NAME – Long NamesDisplays the host OS long name.

AOS NAME – Short NamesDisplays the host OS short name.

Initial Load?Displays whether the load is the initial load for the selected loader type. When adding a load, the System defaults to no.



Effective DateDisplays the effective date (either start or end date) for the ICD-9 procedure/diagnosis codes.

Add LoadWhen the user chooses to add a load, the System displays the Load Description Screen. For a complete description of this screen, see View Load on page 45.

Once all load information is complete, the System creates a background job, which merges the information on the new ICD-9 procedure/diagnosis tape with the existing ICD-9 procedure/diagnosis file. New procedure/diagnosis codes are effective on the date defined in the Effective Date field. Old procedure/diagnosis codes (that is, codes that will no longer be used) are no longer effective on the date defined in the Effective Date field minus one day.

Push ParametersNone




Chapter 11

Screen Driver Color Editor

OverviewThe Screen Driver Color Editor menu function is used to define screen display attributes (e.g., dim reverse text, underlined text). This menu function allows screen driver display attributes to be edited for use on non-English Systems when the non-English text is longer than the English text and overruns the screen driver display attribute definitions.

Function Attributes

DescriptionOnce the Screen Driver Color Editor menu function is accessed, the QuadraMed CPR System prompts to enter a screen driver name. The programming name for the screen driver must be entered (e.g., ae%%1 indicates the screen driver at the Employee-specific level of the Employee/Provider Table, âe). The screen driver name can be found using the Scan Components menu function, screen drivers processing option.

When a screen driver name is entered, the System displays the screen driver along with a screen driver grid of 19 lines and 79 columns. The System prompts to enter the row (y) position. Once a row position is entered, the System prompts to enter the column (x) position(s). The System defaults to 1-79 (i.e., the entire row).

Table Relationship Links TO other tables FROM Screen Driver Color Editor menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function to edit screen display attributes for non-English Systems.



Once the column position(s) is entered, the System prompts to choose one of the following colors/modes:

BlinkDimReverseUnderline

These attributes can be applied in any combination. When no attributes are specified, the System displays the field or heading in normal text.

Once all fields have been defined and accepted, the System files the information and prompts to build the new program. The System defaults to no. Building the new program allows the screen driver to be rebuilt, which allows display attribute definitions to be viewed by all users. Screen building is performed by a low priority background job that is scheduled to run at midnight. When the screen needs to be rebuilt sooner, it can be rescheduled using the Queue Display menu function.

Push ParametersNone


Chapter 12

Bogus Bed Initialization

OverviewThe Bogus Bed Initialization menu function is used to delete all bogus beds that have been assigned, from testing or training scenarios, prior to go-live. A bogus bed is a bed that does not actually exist on the QuadraMed CPR System (i.e., not defined in the Area Table, âfa). Some facilities require a patient be checked into a bed immediately upon visit activation (i.e., admission) for interface purposes. When a visit is activated, the System automatically associates the patient with a bogus bed until he/she is actually checked into a QuadraMed CPR bed. Once the patient is checked into a QuadraMed CPR bed, the bogus bed returns to the bogus bed pool to be reused.

This menu function clears the bogus bed file, and cannot be run on a Production System.

Function Attributes

DescriptionOnce the Bogus Bed Initialization menu function is accessed, the QuadraMed CPR System displays a Beware!! warning message and prompts to verify the bogus bed initialization.

Table Relationship Links TO other tables FROM Bogus Bed Initialization menu function:

None


Not required

Department Usage Information ServicesInformation services use this menu function in preparation for live operation of QuadraMed CPR. Bogus bed initialization is an activity that must be performed if the customer uses bogus beds, and is identified as part of the installation transition plan.



When the bogus bed initialization is verified, the System deletes all visit and location pointers. Once all pointers are deleted, the System builds the Bogus Bed Pool Table, ^ygenafa, bogus bed pools.

Push ParametersNone


Chapter 13

View WP Upload Transactions

OverviewThe View WP Upload Transactions menu function is used by multiple facility enterprises to monitor word processing upload transactions. This menu function allows customers with multiple facilities to view only the word processing upload transactions for the facility(s) defined in the Facility(s) push parameter of this menu function.

When the View WP Upload Transactions menu function uses the WP Document Inbound (sfile) interface program, the user can restrict the display of WP interface upload messages on the Document Options Screen to specified user(s). The term sfile indicates sequential file and reflects the capacity to allow a single directory to be created that holds an unlimited number of sequential files to be uploaded.

The user(s) for whom messages can display can be specified in the Employee(s) push parameter. The Interface(s) push parameter determines what WP upload transactions can be viewed in this menu function.The Default Current User? push parameter specifies whether WP interface upload messages can display for the current user. In addition, the Include Unknown? push parameter specifies whether messages pertaining to undefined users can display. If no users are indicated, the View WP Upload Transactions menu function displays messages for all users for whom WP upload transactions have been generated.

Function AttributesTable Relationship Links FROM other Tables TO View WP Upload Transactions menu function:

Employee/Provider Table, âeFacility Table, âffInterface Table, ât(“i”)


Not required



DescriptionOnce the View WP Upload Transactions menu function is accessed, the QuadraMed CPR System can display the following, depending on how the Facility(s) push parameter is defined:

A list of facility optionsThe Document Options Screen

Facility OptionsFacility options display only when more than one facility is defined for viewing in the Facility(s) push parameter of this menu function. Once a facility is selected, the System displays the Document Options Screen as shown below.

When only one facility is defined in the push parameter, the System automatically displays the Document Options Screen for the facility. When the Facility(s) push parameter is not defined, the System displays word processing upload transactions for all the enterprise facilities.

Document Options ScreenThe Document Options Screen displays a list of documents that errored upon upload. Errors can include both document and Kermit upload errors. Documents with Kermit upload errors are starred out ( *** ) and cannot be selected for viewing. Clicking Expand from the Document Options Screen displays a complete list of all word processing transactions. Clicking Goto allows the user to view a transaction for a specific date and time.

Department Usage TranscriptionMedical records, pathology, or radiology transcription departments use this menu function to view word processing upload transactions between QuadraMed CPR and word processing upload interfaces.



A document can be selected to view, a patient visit can be specified, or the following buttons are available:

BUTTON DESCRIPTION

(R) Resubmit For Filing Allows documents with errors to be resubmitted after error correction. Clicking (R) Resubmit For Filing causes the System to prompt the user to select a document(s) for filing. Only documents with errors other than Kermit upload errors can be selected for resubmission.

(A) View by Accession Number Allows a document to be selected for viewing by accession number. Clicking (A) View By Accession Number causes the System to prompt for an accession number. Accession numbers in the word processing upload header line are optional and can be defined as laboratory department numbers. Once a number is entered, the System displays the upload transaction(s) associated with the specified number.



Select Document to ViewSelecting a document to view causes the System to display the Header Line Fields Screen as shown below.

Specify View by VisitChoosing this option prompts the user for a visit identification number or partial patient name. Once a visit or patient is identified, the System displays the Document Options Screen.

Header Line Fields ScreenWhen a document from the Document Options Screen is selected, the Header Line Fields Screen displays as shown above. The following information displays on this screen:


Accession Number Displays the accession number, specimen number, or laboratory department number.

Visit Number Displays the visit number or medical record number.

Patient Number Displays the patient number.



Header fields may be starred out and not available for selection, depending on the error types associated with the document transaction selected for viewing.

Push Parameters

Transcriptionist ID Displays the identification number of the person who transcribed the document. Identification numbers are defined in the Employee/Provider Table, âe, Facility-specific level, Employee Number(s) field.

Read-by ID Displays the identification number of the physician who dictated the document.

Procedure Code Displays the identification code associated with the procedure. Procedure identification codes are defined in the Procedure Table, ^t, Procedure Identification Screen, Interface Code field, WP Upload Result ID subfield.

Line 2 Displays the optional second line containing non-word processing result profile field information.

Document Displays the text of the uploaded word processing document.

Dictated Date/Time Displays the date/time the document was dictated.

Transcribed Date/Time Displays the date/time the document was transcribed.

DOS File Name Displays the name of the DOS file created by the foreign word processor.

Alternate Provider ID Displays the name of another provider that must be documented in the event.

Resulting Facility ID Displays the identification of the facility that resulted the procedure. Facility ID is defined in the Facility Table, âff, Interface Code field.

Interface(s)

Purpose Defines the interface(s) that determines what WP upload transactions can be viewed in this menu function.

Input Add/Delete Editor

Multiple selection

Links from the Interface Table, ât(“i”)

Required

System Use Determines the interface(s) for which the WP upload transactions display.




Facility(s)

Purpose Defines the facility(s) for which WP upload transactions can be viewed in this menu function. Only active facilities can be defined in this push parameter.


Facility-specific

Multiple selection

Links from the Facility Table, âff

System Use Displays the Facility Options Screen and the Document Options Screen when more than one facility is defined.

Displays the Document Options Screen without displaying the Facility Options Screen when only one facility is defined in this push parameter or when a facility is not defined. The System automatically defaults to the facility of the current device.

Employee(s)

Purpose Defines the employee(s) who performed the transcription and for whom WP interface upload messages display on the Document Options Screen. This field displays only when a program defined in the Interface(s) push parameter is defined as sequential (sfile).


Partial word match

Single selection

Links from the Employee/Provider Table, âe

Expand

System Use Displays the messages for the specified user(s). If no employees are defined, the menu function displays all users for whom WP upload messages have been generated.

Expand – Allows the provider to be identified using standard employee identification methods. For a complete description of these methods, see Chapter 1, Employee/Provider Identification in the Employee/Provider Function Reference.

Include Unknown?

Purpose Defines whether WP interface upload messages pertaining to undefined users display as a result of performing a WP upload. This field displays only when a program defined in the Interface(s) push parameter is defined as sequential (sfile).

Input Yes/No

Defaults to no



System Use Yes – Displays messages pertaining to undefined users on the Document Options Screen.

No – Does not display messages pertaining to undefined users on the Document Options Screen.

Default Current User?

Purpose Defines whether WP interface upload messages pertaining to the current user display as a result of performing a WP upload. This field displays only when a program defined in the Interface(s) push parameter is defined as sequential (sfile).

Input Yes/No

Defaults to no

System Use Yes – Displays messages pertaining to the current user on the Document Options Screen.

No – Does not display messages pertaining to the current user on the Document Options Screen.

Include Unknown? (Continued)




Chapter 14

View Interface Transactions

OverviewThe View Interface Transactions menu function is used to monitor specific interface transactions and support the string and array storage methods. This menu function is used to view most interface transactions except Word Processing Upload transactions. Word Processing Upload transactions are viewed separately through the View WP Upload Transactions menu function. For a complete description of the View WP Upload Transactions menu function, see Chapter 13, View WP Upload Transactions.

Function Attributes

DescriptionOnce the View Interface Transactions menu function is accessed, the QuadraMed CPR System displays a list of Interface Options. The Interface Options that display are defined in the Interface Table, ât("i"), and linked to the Interface(s) push parameter of this menu function. Active interfaces display in bright text, while inactive ones display in dim text. An interface can be selected or the current operational status can be viewed.

Table Relationship Links FROM other Tables TO View Interface Transactions menu function:

Interface Table, ât("i")


Not required

Department Usage Information ServicesInformation services use this menu function to view the interface transactions between QuadraMed CPR and foreign interfaces.



Select InterfaceWhen an interface is selected, the System displays the Interface Transactions Screen as shown below. This screen displays interface information (e.g., messages or transactions) for the selected interface. The information that displays varies depending on the interface selected.

For example, the figure below displays information that can be viewed for an SMS interface. The following interface information can display, depending on the selected interface:


Created by Displays the name of the person who created the transaction.

Date (options) Displays the interface transaction date.

Created Displays the date and time the transaction was created.

Date/time Displays the date and time the transaction was created.

Transaction identifier(s) Displays the unique identifier for each transaction. Depending on the interface selected, the following can represent the transaction identifier:

Message

Message number

Code

Control number

Number of lines Displays the number of lines associated with the interface transaction.

Number of records Displays the number of records associated with the interface transaction.

User Displays the user who created the transaction. When the user is other than a QuadraMed employee, the System displays the internal code for the user. The user's internal code is automatically assigned by the System when an employee is defined in the Employee/Provider Table, âe. When the user is a Per-Se employee, this column displays the initials defined for the employee in the Per-Se Employee Table, ^%hds, Initials field.



The processing options available depend on the interface selected. Not all processing options are available for all interfaces. For some interfaces (e.g., SMS), the Interface Transactions Screen displays only errored transactions. The EXPD key can be pressed to view all transactions. All transactions display in reverse chronological order, with the most recent transaction(s) displaying first. The following processing options can display:

Create tapeAllows a sequentially numbered block of transactions with the same date to be copied to tape. When this processing option is chosen, the System generates a sequential file for the oldest date for which a tape has not previously been created. Based on the dates which have been previously copied, the System begins the new copying session at the next available, uncopied date block. Once the sequential file is generated, the System prompts for a tape to be mounted. Once the tape is mounted, the ENTER key can be pressed to copy the interface information to the tape. If a tape is mounted incorrectly or not present, the System generates a warning message. A message with the current number of the tape being generated displays during the copying sequence. Tapes are automatically numbered in sequential order.

Once the copying process is finished, the System prompts whether to delete the temporary AOS file. The System defaults to yes. When the user chooses to delete the temporary sequential file, the System deletes the temporary duplicate file created for the copying to tape process. The tape(s) can be viewed by choosing the view by tape processing option.

ResubmitAllows an errored message option(s) to be resubmitted for filing.



SearchAllows a partial word search for a document(s).

Select message (code) to viewAllows a message or message code to be viewed.

Select storage dateAllows an interface transaction to be viewed by storage date.

Select storage optionAllows an interface transaction to be viewed by storage option. In addition, the date needed to identify the transaction to a foreign interface is stored with this storage option information.

View by accession numberAllows interface transactions to be viewed by accession number. When this processing option is chosen, the System prompts to enter an accession number.

View (lookup) by interface IDAllows interface transactions to be viewed by interface event ID. When this processing option is chosen, the System prompts for an interface event procedure/order ID number to be entered. This identification number is assigned when a transaction is flagged for transfer to an outbound interface. Interface ID number assignment(s) depends on how the Procedure Table, ^t, Documentation Information Screen, Monitor/Interface Definition field, Interface ID Assignment subfield is defined.

View by patientAllows interface transactions to be viewed by patient. When this processing option is chosen, the System prompts for a patient to be identified. A patient can be identified only by a partial name match.

View by tapeAllows interface transactions to be viewed by ordered tape number. When this processing option is chosen, the System displays the following interface information:


Tape Displays the tape number assigned by the System when the tape was created. Tapes are numbered sequentially according to date of creation.

Messages Displays the message numbers associated with the selected tape.

Tape created Displays the date and time the tape was created.



The following processing options are available:

View (lookup) by visitAllows interface transactions to be viewed by visit. When this processing option is chosen, the System prompts for a visit to be identified. A visit can be identified by a partial name, visit number, or medical record number.

View errorsAllows a transaction error(s) to be viewed. Depending on the interface, the System can prompt to enter a date when this processing option is chosen. The System defaults to the current date. The following interface information can also display:

View transactionsAllows transactions associated with the selected interface to be viewed. When this processing option is chosen, the System prompts to enter a date. The System defaults to the current date. The System then displays a list of transactions for the selected date to be viewed.

Current Operational StatusThe current operational status of each interface can be viewed by choosing the view current operational status processing option when this menu function is accessed. When this processing option is chosen, the System displays the Current Operational Status Screen as shown below.

Activity Displays the date of the message transaction activity.


Select tape number to view Allows all transactions contained on a tape to be viewed. The System automatically assigns the tape number when the tape is created. Each tape message option can be selected for detailed review.

Recreate tape Allows a tape to be recreated. The process for recreating tapes is similar to the original tape creation process. This processing option serves as an error check in case the original tape was corrupted during the creation process. For a complete description of creating a tape, see Create tape on page 63.


Date Displays the date and time the error occurred.

Error Displays a brief description explaining the type of error that occurred.




This screen displays the following information:

Pressing the ENTER key causes the System to update the information on the Current Operational Status Screen. The System automatically refreshes the screen every 15 seconds.


Interface Displays the name of the interface.

Status Displays the current interface status. The interface status displays as running or not running. The current interface status can be toggled between running and not running using the Interface Up/Down menu function.

Messages/Minute Displays the number of transaction messages per minute being transmitted through the interface when the interface is running. Transaction volume is tracked and monitored primarily during peak hours. This information is used to determine transmission scheduling efficiency and productivity.



Push Parameters

Interface(s)

Defines the interface(s) that can be viewed in this menu function. Interface Options are defined in the Interface Table, ̂ at("i"). Only active interfaces can be defined in this push parameter. The System does not display inactive options for selection.

In addition, the System does not allow selection of word processing upload interfaces in this push parameter. Word processing upload interfaces do not display for selection. They can be selected only in the View WP Upload Transactions menu function, Interface(s) push parameter. For a complete description of the View WP Upload Transactions menu function, see Chapter 13, View WP Upload Transactions.

When this push parameter is not defined, all Interface Options (i.e., active and inactive) defined in the Interface Table, ât("i"), display when this menu function is accessed. Interface Options with the Interface Table, ât("i"), Active? field defined as no display in dim text when this menu function is accessed. When the Interface Table, ât("i"), Active? field is defined as yes or transmission disabled for the interface option, the interface option displays in bright text when this menu function is accessed.




Chapter 15

Load United Kingdom Mailing Codes

OverviewThe Load United Kingdom Mailing Codes menu function provides a utility to read the information contained in the United Kingdom PAF (Postal Address File) (CD ROM), and populate the Mailing Code Table, ^rt(“mc”). As a result of the use of this menu function, the Mailing Code Table, ^rt(“mc”), United Kingdom Postcode subfile is populated with UK postcodes and the corresponding addresses/mailing information linked to the individual postcodes.

Postcode information can be loaded, if defined, into the following Mailing Code Table, ^rt(“mc”), United Kingdom Postcode subfile fields and subfields:

Postal CodeLocation(s)OrganisationSub-building NameBuilding NameBuilding NumberDependent StreetStreetDependent LocalityLocalityPost TownCountry

It is strongly suggested that the full postcode data be loaded and placed on PROD prior to go-live and all subsequent monthly updates be run on PROD. This global rt(“mc”) should never be rolled to any System. The finished file can be over 10GB and moving such a large file using xin/xout will take too long for any roll process.



Function Attributes

DescriptionOnce the Load United Kingdom Mailing Codes menu function is accessed, the System prompts the user to click one of the following buttons:

Loading the Complete FileOnce the (C) Load Complete File is clicked or OK is clicked to accept the default, the System prompts the user to add or delete a Host OS filename. Clicking (A) Add prompts the user to enter the Host OS file name to load. In order to load a complete set of postal codes, enter the path in which the files are located (/usr/opt/hds_sw/…) followed by *.*.

Clicking (D) Delete prompts the user to select the Host OS file name to delete. Deletions can be made during the process of adding files for a complete load in the case of user error while naming a path to add, etc. Once a file is selected to delete, the System prompts to verify the deletion.

Once the files are identified and confirmed, the user clicks (A) Accept Mailing Code Load and the loading process will begin.

Loading the Update FileOnce (U) Update File is clicked, the System prompts the user to add or delete. Clicking (A) Add prompts the user to enter the Host OS file name to load. In order to load an updated set of postal codes, enter the path in which the files are located (/usr/opt/hds_sw/…) followed by *.*.

Table Relationship Links FROM other Tables TO Load United Kingdom Mailing Codes menu function:

None


Not required

BUTTON DESCRIPTION

(C) Load Complete File Indicates the complete UK PAF File is loaded and populates the Mailing Code Table, ^rt(“mc”), United Kingdom Postcode subfile. The System defaults to c.

(U) Update File Indicates the UK PAF File is updated with the latest postcode information.

The files must be added in order (e.g., fpcompst.c01-fpcompst.c13) at one time (e.g., the user cannot add one or two, accept the load and go back to add more or a System error will occur).

Chapter 15 Load United Kingdom Mailing Codes


Once one file is added, the user clicks (A) Accept Mailing Code Load and waits until the load is complete. Then the next file can be added.

Clicking (D) Delete prompts the user to select the Host OS file name to delete. Deletions can be made during the process of adding files for an update in the case of user error while naming a path to add, etc. Once a file is selected to delete, the System prompts to verify the deletion.

Push ParametersNone

These files must be run individually with each file completed before running the next load.




Chapter 16

Load HA/PCT of Residence

OverviewThe Load HA/PCT of Residence menu function provides a utility to load the United Kingdom Health Authority (HA) and Primary Care Trust (PCT) information from the Organisation Codes Service (OCS) file and populate the Mailing Code Table, ^rt(“mc”). Health Authority and Primary Care Trust information is based on the geographical location of the patient. It is collected and stored with the patient’s registration information and required by the NHS for reporting purposes.

Before the Health Authority and Primary Care Trust information is loaded into the Mailing Code Table, ^rt(“mc”), the Load HA/PCT of Residence menu function validates the Health Authority (HA) code and the Primary Care Trust (PCT) code against the codes contained in the Commissioning Table, ^rt(“ct”), Health Authority Code and Primary Care Trust Code fields.

Once this menu function is executed, the Mailing Code Table, ^rt(“mc”), United Kingdom Postcode subfile is populated with Health Authority (HA) and Primary Care Trust (PCT) information. This information is linked to the individual postcodes. HA and PCT information can be loaded in the following Mailing Code Table, ^rt(“mc”), United Kingdom Postcode subfile, Mailing Code level fields:

HAPCT

Function Attributes

The Commissioning Table, ^rt(“ct”), must be loaded first before running this menu function.

Table Relationship Links FROM other Tables TO Load HA/PCT of Residence menu function:

None


Not required



DescriptionOnce the Load HA/PCT of Residence menu function is accessed, the System displays a list of current loads to view. The following information displays as a header/column for each load:

The System prompts the user to select a load to view or to click (A) Add to add a load. When (A) Add is clicked, the System prompts the user to define the following fields:

Once this information is defined and accepted, the loading process begins. Once the load is completed, the System displays the date, description and status of the load.

Push ParametersNone


Date Displays the date the load was started.

Description Displays the name of the load.

Status Displays the status information of that load. The statuses are as follows:

Complete – Indicates the load is complete.

Error – Indicates the load completed with errors or aborted due to errors.

In Progress – Indicates the load is running.

FIELD DESCRIPTION

Description Defines the description of the load that displays under the Description column. The user can enter free-text with a 100-character limit. This is a required field.

Host OS File Name Defines the Host OS File name that will be loaded. For example: /sun1/uk_addresses/commissioning/pcodeall.csv. The user can enter free-text with a 100-character limit.


Chapter 17

Load UK Commissioning Data

OverviewThe Load UK Commissioning Data menu function provides the ability to load the necessary commissioning files into the appropriate tables on the QuadraMed CPR System. These files are provided by the Organisation Codes Service (OCS).

The Health Authorities (HA), Primary Care Trusts/Groups (PCT) and GP Practices are loaded into the Commissioning Table, ^rt(“ct”).

The General Medical Practitioners and General Dental Practitioners practicing in the UK are loaded into the Employee/Provider Table, âe.

Function Attributes

DescriptionOnce the Load UK Commissioning Data menu function is accessed, the System displays a list of current loads to view. The following information displays as a header/column for each load:

Table Relationship Links FROM other Tables TO Load UK Commissioning Data menu function:

None


Not required


Date Displays the date the load was started.

Description Displays the name of the load.



The System prompts the user to select a load to view or click (A) Add to add a load. When (A) Add is clicked, the System prompts the user to define the following fields as shown below:

DescriptionDefines the description of the load that displays under the Description column. The user can enter free-text with a 100-character limit. This is a required field.

Health AuthoritiesDefines the Host OS file name that corresponds to the OCS Health Authority file to be loaded, for example: /sun1/UK_addresses/ Commissioning/eauth.csv. The user can enter free-text with a 100-character limit.

Primary Care TrustsDefines the Host OS file name that corresponds to the Primary Care Trust file to be loaded; for example: /sun1/UK_addresses/ Commissioning/epctcur.csv. The user can enter free-text with a 100-character limit.

GP PracticesDefines the Host OS file name that corresponds to the OCS General Medical Practitioner Practices file to be loaded; for example: /sun1/UK_addresses/ Commissioning/epraccur.csv. The user can enter free-text with a 100-character limit.

General Medical PractitionersDefines the Host OS file name that corresponds to the OCS GMP file to be loaded; for example: /sun1/UK_addresses/ Commissioning/egpcur.csv. The user can enter free-text with a 100-character limit.

Practice MembershipDefines the Host OS file name that corresponds to the OCS Practice Membership file to be loaded; for example: /sun1/UK_addresses/ Commissioning/epracmem.csv. The user can enter free-text with a 100-character limit.

Status Displays the status information of that load. The statuses are as follows:

Complete – Indicates the load is complete.

Error – Indicates the load completed with errors or aborted due to errors.

In Progress – Indicates the load is running.




Care TrustsDefines the Host OS file name that corresponds to the OCS Care Trust file to be loaded; for example: /sun1/UK_addresses/ Commissioning/ ecare.csv. The user can enter free-text with a 100-character limit.

Primary GroupsDefines the Host OS file name that corresponds to the OCS Primary Care Group file to be loaded, for example: /sun1/UK_addresses/ Commissioning/epcgcur.csv. The user can enter free-text with a 100-character limit.

Dental PracticesDefines the Host OS file name that corresponds to the OCS Dental Practices file to be loaded; for example: /sun1/UK_addresses/ Commissioning/egdpprac.csv. The user can enter free-text with a 100-character limit.

Dental PractitionersDefines the Host OS file name that corresponds to the OCS Dental Practitioners file to be loaded; for example: /sun1/UK_addresses/ Commissioning/egdp.csv. The user can enter free-text with a 100-character limit.



Scotland PurchasersDefines the Host OS file name that corresponds to the OCS Scotland Purchasers file to be loaded; for example: /sun1/UK_addresses/ Commissioning/scotpur.csv. The user can enter free-text with a 100-character limit.

Scotland Practice & GPDefines the Host OS file name that corresponds to the OCS Scotland Practice and General Practitioner file to be loaded; for example: /sun1/UK_addresses/Commissioning/scotgp.txt. The user can enter free-text with a 100-character limit.

N. IrelandDefines the Host OS file name that corresponds to the OCS Northern Ireland file to be loaded; for example: /sun1/UK_addresses/Commissioning/ ni.csv. The user can enter free-text with a 100-character limit.

N. Ireland PracticesDefines the Host OS file name that corresponds to the OCS Northern Ireland Practices file to be loaded; for example: /sun1/UK_addresses/ Commissioning/npraccur.csv. The user can enter free-text with a 100-character limit.

N. Ireland GPDefines the Host OS file name that corresponds to the OCS Northern General Practitioners file to be loaded; for example: /sun1/UK_addresses/ Commissioning/ngpcur.csv. The user can enter free-text with a 100-character limit.

Employee Link DataDefines the information to be defaulted into the Employee/Provider Table, âe, for the General Practitioners being loaded. When this field is accessed, the following subfields display for definition as shown below:

FIELD DESCRIPTION

Employee Secondary Number Defines the employee secondary number field that is used to define the UK GP code. This is a required field and must be defined in order to ensure there are no duplicate GPs loaded in subsequent loads. This field is facility-specific and displays options from the Employee External Number Type Table, âet(“en”). The option selected populates the Employee/Provider Table, âe, Facility-specific level, Employee Number(s) field.

GP Specialties Defines the GP specialty(s) that is used to populate the Employee/Provider Table, âe, Facility-specific level, Specialty(s) field. This field is facility-specific. The System displays options from the Physician Service/Department/ Specialty Table, âet(“ps”), for selection.



GP Title Defines the title used to populate the Employee/Provider Table, âe, Employee-specific level, Title field. This field is facility-specific. The System displays options from the Title Table, ^rt(“tt”), for selection.

GP Employee Type(s) Defines the employee type(s) used to populate the Employee/Provider Table, âe, Facility-specific level, Employee Type(s) field. When this field is accessed, options from the Employee Type Table, âet(“et”), display for selection.

Dentist Specialties Defines the specialty(s) used to populate the Employee/Provider Table, âe, Facility-specific level, Specialty(s) field for the General Dental Practitioners. This field is facility-specific. The System displays options from the Physician Service/Department/Specialty Table, âet(“ps”), for selection.

Dentist Title Defines the title used to populate the Employee/Provider Table, âe, Employee-specific level, Title field for the General Dental Practitioners. This field is facility-specific and options from the Title Table, ^rt(“tt”), display for selection.

Dentist Employee Type(s) Defines the employee type(s) used to populate the Employee/Provider Table, âe, Facility-specific level, Employee Type(s) field for the Dental General Practitioners. When this field is accessed, options from the Employee Type Table, âet(“et”), display for selection.

FIELD DESCRIPTION



Once this information is defined and accepted, the loading process begins. The initial load takes approximately 2-4 days to load. Once the load is complete, the System displays the date, description and status of the load. After loading, the user can view a load by selecting it from the list of current loads. The System displays the fields and file names to the user as shown below.

This load utility should only be used with the official OCS file provided by the customer site. The loader needs to be flexible due to the fact that the OCS file can have a different format from year to year. Updates are received by the facility every 3 months.

First, the loader must be run for the Health Authorities, Primary Care Trusts, GP Practices, Scotland Purchasers, N. Ireland and N. Ireland Practices. Once this load is complete, then the loader must be run again for the GP’s.

The GP’s must be run on Production and the following must occur before the load is started:The UK Mailing Code Loader must be complete. Due to the structure of the GP addresses that are included in the data files from the OCS, in order to ensure an accurate address in the Employee Table, âe for each GP, the loader performs a check against the Mailing Code Table, ^rt(“mc”), to find the appropriate address.The Mailing Code Table, ^rt(“mc”) files must be loaded and rolled to Production.There are approximately 40,000 General Practitioners (Medical and Dental) that will be loaded into the Employee Table, âe. It is highly recommended that an x-out of the Employee Table, âe be performed prior to running the load. This will provide the ability to restore the Employee Table, âe back to its original state, if necessary.



Push ParametersNone




Chapter 18

View Interface Transactions, Status, and I/O

OverviewThe View Interface Transactions, Status, and I/O menu function is used to monitor interface transactions and provide information on each interface and interface message. This menu function can also be used to troubleshoot and provide additional information for system administrators when an interface is not operating properly.

Function Attributes

The Input/Output (I/O) functionality is available only when the Device Table, âd, Enable Ring Capture field is defined as yes. However, the field displays only for QuadraMed employees. Thus, the I/O functionality in this menu function is available only with the help of QuadraMed employees.

Table Relationship Links FROM other Tables TO View Interface Transactions, Status, and I/O menu function:

Interface Table, ât(“i”)Interface Transmitter Table, âid


Not required

Department Usage All DepartmentsAll departments use this menu function to view the interface transactions between QuadraMed CPR and foreign interfaces. For example, Laboratory uses this menu function to view and monitor orders and results.



DescriptionOnce the View Interface Transactions, Status, and I/O menu function is accessed, QCPR displays the Active Interface Options Screen with a list of Interface Options. The Interface Options that display are defined in the Interface Table, ât(“i”), and linked to the Interface(s) push parameter of this menu function. Active interfaces display in bright text, while inactive ones display in dim text.

The Active Interface Options Screen displays the name of the interface and the program under which it is running. This information is helpful to QuadraMed employees for investigating an interface error. An interface can be selected or the current list of interfaces can be refreshed.

Select InterfaceWhen an interface is selected from the Active Interface Options Screen, the System displays the Interface Transactions Screen as shown below, depending on the selected interface. The interface messages that display when an interface is selected depend on the definition of the menu function’s Initial Display Errors Only? push parameter. When the push parameter is defined as yes, the System displays a list of interface message errors when an interface is selected. When the push parameter is defined as no, the System displays a list of all interface messages, both errors and successes, after selecting an interface.



The Interface Transactions Screen displays interface information (e.g., messages or transactions) for the selected interface. The information that displays depends on the type of interface. The following table describes the interface information that can display:

The processing options available from this screen depend on the interface selected. Not all processing options are available for all interfaces. All transactions display in reverse chronological order, with the most recent transaction(s) displaying first. The following processing options can display:


Message Displays the interface message number.

Transmit Time (Outbound) Displays the date and time the interface message was sent.

Receive Time (Inbound) Displays the date and time the interface message was received.

Creation Time (Outbound) Displays the date and time the interface message was created.

Date (Options) Displays the interface message date.

Type Displays Health Language Seven (HL7) message and event types (e.g., AO1, AO3).

Visit Displays the visit number to which the message applies.

Patient Name Displays name of the patient to which the message applies.




(I) Index Enables the user to perform an indexed search by visit or patient number or patient name depending on the type of interface selected.

(S) Status Displays the current status of the selected interface. Choosing this option displays interface information defined in the Interface Table, ât(“i”), the transmitter definition for the selected interface from the Interface Definition Table, âid, and information of the device running the interface. For more information, see Interface Message Status on page 87.

(R) Refile / (R) Retransmit Enables the user to resubmit an interface message(s) to its defined destination. This option displays only when the Allow Message Resubmit/Resend? push parameter of this menu function is defined as yes.

(V) Validate Output File Enables the user to validate an output file created by the selected interface using a Secure Hash Algorithm file. This processing option displays only for interfaces using the Core Generic File Writer transmitter. For more information on this processing option, see Validate Output File on page 90.

(M) Mark as Reviewed? Enables the user to move specific interface message errors from the error list to the main message list. This option displays while viewing the interface transaction error list when the Allow Mark as Reviewed? push parameter defined as yes.

Expand Displays a list of interface message errors or a list of all interface messages depending on how the Initial Display Errors Only? push parameter of this menu function is defined. When the Initial Display Errors Only? push parameter is defined as yes, clicking this option displays all interfaces messages. When the Initial Display Errors Only? push parameter is defined as no, clicking this option displays only interface messages errors.

Goto Enables the user to enter a specific date and time to view interface messages, or to select the (M) Goto Message Code processing option to allow the user to go to a specific message code.



Select MessageWhen a specific interface message is selected for an interface, the System displays more details about the transaction (see figure below). Clicking Expand returns the user to the Interface Transactions Screen (see page 85).

From the raw message display, the user can further view segments of the message or choose the (R) Retransmit processing option to resend the message. This option does not display for all interfaces.

Interface Message StatusAfter selecting an interface from the Active Interface Options Screen and clicking (S) Status, the System displays the current status of the selected interface on the Interface Configuration Screen (see figure below).



The Interface Configuration Screen displays the following information from the Interface Table, ât(“i”), Transmitter Definition Table, âid, and the device through which the interface is implemented

Interface Code Table, ât(“i”)

Interface Code

Interface Name

Activation Status

Last Edit

Archive Time

Interface Definition Table, âid

Transmitter Code

Transmitter Name

Last Edit

Storage Method

Program

Inbound?

TSD Screen



Device

Device Number

IP Address

Interface Code

Channel Status

Interface Status

The processing options available on the Interface Configuration Screen depend on the transmitter and device definition. The following processing options can display on the screen:


(S) Interface Stop Enables the user to stop an active interface. This option displays only when the Allow Interface Up/Down? push parameter of this menu function is defined as yes. When the Force Up/Down Comment? push parameter is also defined as yes, the System requires the user to enter a comment for stopping an active interface.

(S) Interface Start Enables the user to start an inactive interface. This option displays only when the Allow Interface Up/Down? push parameter of this menu function is defined as yes. When the Force Up/Down Comment? push parameter is also defined as yes, the System requires the user to enter a comment for starting an inactive interface.

(D) Device Status Enables the user to view the status of the device on which the interface is run. This option displays when the Enable Device Access? push parameter of this menu function is defined as yes.

Clicking this option displays the following options:

(S) Channel Status – Displays information on the key parameters and channel on which the interface is run.

(R) I/O Rings – Displays input and output information. This functionality is only available with the assistance of QuadraMed employees.

(T) Transmitter Data Enables the user to view transmitter-specific data defined for the selected interface in the Interface Table, ât(“i”), Transmitter-specific Data field. This option displays only for inbound interfaces that use a device with transmitter-specific data defined in the Interface Table, ât(“i”), Transmitter-specific Data field. The information that displays after selecting this option differs for each selected interface.



Validate Output FileIn addition to monitoring interfaces, the View Interface Transactions, Status, and I/O menu function also enables system administrators to create and validate Secure Hash Algorithm (SHA) files against specific interface messages through the (V) Validate Output File processing option. QCPR provides SHA-1 based dataset hash value services (dataset signature or digest services) to generate and compare hash values to ensure the integrity of datasets exchanged with other systems. The SHA-1 hash algorithm produces a 20-byte hash of the contents of a file using U.S. Secure Hash Algorithm 1 (SHA-1). For more information on SHA-1, see Federal Information Processing Standards Publication 180-2 and Internet Engineering Task Force Request for Comments 3174.

The Validate Output File functionality is a security measure within QCPR that can be used to validate the integrity of exported files when a live interface connection does not exist. For example, a facility can use this menu function to create HL7-formatted files for transfer (FTP, e-mail, etc.) to the Centers for Disease Control and Prevention or similar public health organizations when a live interface connection is not available.

How to ...

Validate an output file using a hash fileTo validate an interface output file using a hash file, follow the steps below:

1. From the Active Interface Options Screen, select an interface created using the Core Generic File Writer transmitter. The Interface Transaction Screen displays a list of interface messages.

2. From the Interface Transactions Screen, click (V) Validate Output File. The System displays a list of files that can be validated.

The Validate Output File option is available only for interfaces created using the Core Generic File Writer transmitter in the Interface Definition Table, âid.

Default directory where the System looks for the output file.

http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf

http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf

http://tools.ietf.org/html/rfc3174



3. Select the directory in which the output file is stored, and click OK.

4. Select the output file to validate, and click OK. The System displays the path of the output file next to the File To Validate field on screen.

5. Select the hash file against which to validate the selected output file. The System defaults a selection in the text box based on the output file selected. Click OK.

a. To create a new hash file, click (C) Create Hash File. The System prompts for a file name for the new hash file. Click OK to continue.



6. The System displays the output and hash files on screen in the File to Validate and Hash File fields respectively. Click OK to validate the two selected files.

When the output file is validated, the following screen displays:

When the output file is not validated (e.g., wrong hash file or invalid value in the hash file), the following screen displays:



Push Parameters

Interface(s)

Purpose Defines the interface(s) that can be viewed in this menu function. When this push parameter is not defined, all Interface Options (i.e., active and inactive) defined in the Interface Table, ât(“i”), display when this menu function is accessed.

Input Multiple selection

Links from the Interface Table, ât(“i”)

The System does not display word processing upload interfaces for selection in this push parameter. They can be selected only in the View WP Upload Transactions menu function, Interface(s) push parameter. For a complete description of the View WP Upload Transactions menu function, see Chapter 13, View WP Upload Transactions.

System Use Determines the interface(s) viewed in this menu function.

Allow Interface Up/Down?

Purpose Defines whether the menu function allows control over starting or stopping an interface(s) linked in this menu function

Input Yes/No

Defaults to no

System Use Yes – Displays the (S) Interface Stop and (S) Interface Start processing options that enable the user to manually start or stop an interface linked in this menu function.

No – Does not display the (S) Interface Stop and (S) Interface Start processing options, thus not allowing the interface to be manually started or stopped.

Allow Message Resubmit/Resend?

Purpose Defines whether the user can resubmit or resend interface transaction errors from the interface.

Input Yes/No

Defaults to no

System Use Yes – Displays the (R) Refile processing option in the menu function. This processing option displays only for outbound interfaces.

No – Does not display the (R) Refile processing option in the menu function, thus not allowing interfaces transactions to be resubmitted or resent.



Enable Device Access?

Purpose Defines whether the menu function displays information about the device or channel through which the interface uses.

Input Yes/No

Defaults to no

System Use Yes – Displays the (D) Device Status processing option that displays information about the device and channel used by the interface.

No – Does not display the (D) Device Status processing option, thus not allowing the information regarding the device and channel used by the interface to be viewed.

Initial Display Errors Only?

Purpose Defines whether the menu function only displays interface transactions errors after an interface is selected to be viewed.

Input Yes/No

Defaults to no

System Use Yes – Displays only interface transactions errors for an interface when an interface is selected to be viewed in the menu function.

No – Displays all interface transactions, errors and successes, when an interface is selected to be viewed in the menu function.

Force Up/Down Comment?

Purpose Defines whether the System requires a comment to be entered when an interface is forced to start or stop.

Input Yes/No

Defaults to no

System Use Yes – Requires a comment to be entered when an interface is brought up or down manually in this menu function.

No – Does not require a comment to be entered when an interface is brought up or down manually in this menu function.



Allow Mark as Reviewed?

Purpose Defines whether the user can move interface transaction errors from the error list to the main interface transaction list.

Input Yes/No

Defaults to no

System Use Yes – Displays the (M) Mark as Reviewed processing option that enables the user to move interface transaction errors from the error list to the main interface transaction list.

No – Does not display the (M) Mark as Reviewed processing option, thus not allowing the interface transaction errors to be moved from the error list to the main interface transaction list.




Chapter 19

Growth Charts Percentile Load Utility

OverviewThis Growth Charts Percentile Load Utility menu function is used to load the correct Growth Chart Percentile Data supplied by the Centers for Disease Control and Prevention (CDC), into the Growth Charts Percentile Table, ^nt(“gcp”). This utility eliminates the need to manually enter the data points for each percentile for a growth chart.

Function Attributes

Percentile Data FilesThe Growth Chart Percentile Data files are supplied by the CDC and are available on the CDC web site. Once these files are downloaded and saved to the appropriate location, this load utility can be run. The following steps describe the process to download the data files and run the percentile load utility.

Table Relationship Links TO other Tables FROM Growth Charts Percentile Load Utility:

None


Not Applicable

Department Usage IT DepartmentThe IT staff uses the data provided by the CDC to populate the data points on the Growth Charts. This utility needs to be run only once, unless the data is updated by the CDC.



How to ...

Run Percentile Load Utility

1. Navigate to the URL, http://www.cdc.gov/growthcharts/percentile_data_files.htm.

The CDC web page displays as shown below.

2. Select a Percentile Data file.

The File Download screen displays.

3. Click Save.

The Save As dialog box displays.

Percentile Data Files in Excel format

http://www.cdc.gov/growthcharts/percentile_data_files.htm



4. Download all the files and save them on the local machine with a .CSV extension.

5. Once all the files are saved to the local machine, upload the CSV files into the application server using an appropriate file transfer methodology, and make a note of the path where the files are saved.

6. Access the Clinical Desktop and double-click the Growth Chart Percentile Loader application to launch the utility.

The Growth Chart Percentile Loader screen displays.

Growth Chart Percentile Loader



7. Select the Growth Chart Percentile for which you want to load the percentiles.

8. Specify the location of the saved .CSV file at the Enter Host file: prompt.

If there is no Growth Chart Percentile entry in the Growth Charts Percentile Table, ^nt("gcp"), an entry needs to be manually created for both male and female percentiles.

Select the growth chart percentile



9. Click OK.

The System displays the message Sucessfully Loaded Percentiles.

How to ...

Set up the Growth Charts Percentile Loader

1. Access the Desktop Application Table, ât(“dta”).

A list of all available application options display.



2. Choose (A)Add.

The Application Definition screen displays.

3. Define the following standard fields:

Application Name

Alias Name(s)

Window Title

Access Security

4. Define the Desktop Application Class field as Ultiview.

5. Define the Non-Facility Parameters field, Liteview Function(s) subfield as Growth Chart Percentile Load Utility.

6. Click OK.

7. Add Growth Chart Percentile Load Utility to desktop to run.


Chapter 20

Wolters Kluwer Update Mapping RxNorm Codes Utility

OverviewThe Wolters Kluwer Update Mapping RxNorm Codes Utility is used to update the RxNorm Mapping Table, ^pt("rxn"). This utility needs to be run after each update to the RxNorm flat file or whenever a new RxNorm flat file is released.

Medi-Span® provides QuadraMed with an updated RxNorm flat file every month and these files are made available to the clients who are using RxNorm Codes.

Function Attributes

The Wolters Kluwer Update Mapping RxNorm Codes Utility updates only the RxNorm Mapping Table, ^pt("rxn"), not the RxNorm flat file.

Table Relationship Links FROM other Tables TO Wolters Kluwer Update Mapping RxNorm Codes Utility:

None


Not Applicable

Department Usage Information ServicesInformation Services use this menu function to update the RxNorm Mapping Table, ^pt("rxn") with new one to many, and many to many code relationships. The new relationships can be mapped manually in the RxNorm Mapping Table, ^pt("rxn").



DescriptionThis section describes how to perform the following:

Running Wolters Kluwer Update Mapping RxNorm Codes Utility

Viewing the Output for Wolters Kluwer Update Mapping RxNorm Code Utility

Running Wolters Kluwer Update Mapping RxNorm Codes Utility

How to ...

Run the Wolters Kluwer Update Mapping RxNorm Codes Utility

1. Access the Wolters Kluwer Update Mapping RxNorm Codes Utility.

The Wolters Kluwer Update Mapping RxNorm Codes Utility screen displays as shown below:

2. Choose (Y) Yes to run the utility.

The utility runs in the background and takes 10 to 20 minutes to complete.

3. The system sends an e-mail to the user once utility run completes.

Chapter 20 Wolters Kluwer Update Mapping RxNorm Codes Utility


Viewing the Output for Wolters Kluwer Update Mapping RxNorm Code UtilityWhenever the Wolters Kluwer Update Mapping RxNorm Code Utility is run, the system generates information about the updates or changes made to the RxNorm Mapping Table, ^pt("rxn").

How to ...

View the Output for Wolters Kluwer Update Mapping RxNorm Code Utility

1. Type the qdisplay command in the Command Executor window and press ENTER.

The Background Job Display screen displays.

2. Select Completed processing option to view the completed jobs.

A list of completed jobs displays.

3. Select the Update mapped RxNorm data for DDIDs/GPIs pointing to more than 1 RxNorm Codes job from the list.

The output appears as shown in the figure below.

The output is not generated when the utility is run for the first time, because all records in the RxNorm Mapping Table, ^pt("rxn") are added and are new. The output contains only changes to the RxNorm Mapping Table, ^pt("rxn"), thus the output is generated when the utility is run second time onwards.



Push ParametersNone