RESOURCE AND PATIENT MANAGEMENT SYSTEM

IHS RPMS
FOIA Distribution Version

Configuration Guide - Addendum I

Version 1.0 March 2010

Office of Information Technology (OIT) Division of Information Resource Management Albuquerque, New Mexico

IHS RPMS FOIA Distribution Version

Version 1.0

Preface
This document is part of the distribution package for the Indian Health Services (IHS) Freedom of Information Act (FOIA) release of the RPMS system. In order to comply with policies and laws concerning patient privacy and commercial software licensing, it has been necessary to remove certain parts of the system. This document identifies those areas that have been modified, as well as identifying areas where it will be necessary for the user of this system to make additional modifications in order for the system to perform properly. This document will not tell the user how to fix any issues that will arise in implementing this system, but rather indicates areas where modifications have been made. Because this system is a combination of the Veterans Administration VistA system and the IHS RPMS system, there are some areas that are not used by IHS. These areas have been identified and should be ignored by the user.

Configuration Guide Addendum I March 2010

Preface

ii

IHS RPMS FOIA Distribution Version

Version 1.0

Table of Contents
Introduction to Installation .................................................................................1 Documentation for the System ..........................................................................2 Interfaces between IHS M Environment and Other Systems...........................3 Interfaces Within IHS ..................................................................................3 Interfaces Within the Database Not Used by IHS .....................................10 Remote Procedure Calls (RPCs) .............................................................11 Routines Modified for FOIA ..............................................................................13 Imbedded Telephone Numbers ................................................................13 Imbedded Email Addresses ......................................................................14 Imbedded IP Addresses ...........................................................................15 Imbedded DNS Addresses .......................................................................15 Security Hashing ......................................................................................16 Cleaned Data Files (Globals) ............................................................................17 Nodes .....................................................................................................19 Other Modifications...........................................................................................20 Security ....................................................................................................20 MailMan ....................................................................................................20 Appendix I. VueCentric .....................................................................................21 Licensing ..................................................................................................21 Collaboration ............................................................................................23 Contact Information ..........................................................................................24

Configuration Guide Addendum I March 2010

Table of Contents

iii

IHS RPMS FOIA Distribution Version

Version 1.0

Introduction to Installation
The basic installation of the IHS RPMS Medical System requires that the Intersystems Inc. CACH be on the system where the environment will reside. Use the Version 2008.2 or later. Instructions for installing this environment are available from the Intersystems Inc. web site, http://www.intersystems.com/ under their standard licensing agreements. Contact Intersystems directly for information about purchasing this licensed product. Once the CACH environment is established, the steps in the installation guide can be followed to install the M portion of this system.

Configuration Guide - Addendum I March 2010

Introduction to Installation

IHS RPMS FOIA Distribution Version

Version 1.0

Documentation for the System

There are a number of manuals on the various parts of the Indian Health Service (IHS) system. These can be found at the following sites: View the following Web site for RPMS for other embedded links. http://www.ihs.gov/Cio/RPMS/index.cfm?module=home&option=documents From the Web site, click on the list box and select from a variety of documents about the system including User Manuals, Technical Manuals and Installation Guides. Home of Hard Hats of the World, at http://www.hardhats.org/ is a source of all the manuals and information about the M (MUMPS) programming language. This site contains manuals for programmers using native M and for FileMan. Documentation on the Intersystem Inc. CACH system is available from their web site at http://www.intersystems.com/.

Configuration Guide - Addendum I March 2010

Documentation for the System

IHS RPMS FOIA Distribution Version

Version 1.0

Interfaces between IHS M Environment and Other Systems

The IHS database was originally built for the Veterans Administration (VA). Therefore it contains code that is not used by IHS. This includes HL7 interfaces and Remote Procedure Calls (RPCs). Rather than trying to eliminate these VA only interfaces, IHS has decided to ignore them, as they are not used. However, the software still resides in the database and may cause some confusion as to why they exist within the database. The following two sections identify those interfaces that are utilized by IHS and those used only by the VA.

Interfaces Within IHS

The following table shows the variety of interfaces that exist within the IHS database. The first column shows those interface activities that are current within IHS. The second column indicates the type of interface that is used by the activity: HL7 is a standard for sending medical data between systems and is done through M code to either an M environment, an external application, or to an external host file; GUI indicates that the interface is between a Graphical User Interface and the M environment and passes data by Remote Procedure Calls (RPCs). There is a third type, HOST, in which an external file is built from either an M environment or from a GUI environment. This file can then be transferred via FTP to some external system. For GUI environments as well as for non-M artifacts, the language the artifact was created in is included, as well as the version number of that language. Since it will be necessary to compile some of these artifacts, the user must purchase the appropriate license(s) from the product owners. The third column provides a short description of what the interface does within the system.
IHS Interfaces HL7/GUI Use

Internal M Interfaces PCC Suite of programs. (Patient Care Component) HL7 Using a link between RPMS and MS Word, produces a real-time customized encounter form.

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

IHS Interfaces

HL7/GUI

Use

PIMS ADT or Scheduling

HL7

Can send ADT (Admissions, Discharge, Transfer) to data warehouse. The National Data Warehouse (NDW) project is upgrading the Indian Health Service's (IHS) national data repository, the National Patient Information Reporting System (NPIRS), to a new, state-of-the-art, enterprise-wide data warehouse environment. This is the Generic Interface System that is used by IHS to transport HL7 messages within the environment and outside the environment Clinical Health Record The GUI version of the software contains most of the existing functionality of the traditional roll and scroll FRPMS application, including patient management, register maintenance, running reports, and running the Diabetes Audit.

Data Warehouse

HL7

BHL IHS Interfaces with GIS

HL7/GUI C# .NET

IHS RPMS CHR System Diabetes Management System (DMS)

HL7 via FTP/Kermit GUI Visual Basic .NET and iCare Population Management GUI

Pharmacy-Automated Dispensing Interface System (BOP)

HL7 via TCP/IP

The Automated Dispensing System interface sends RPMS patient data and orders to the Automated Dispensing System in real-time, as transactions occur.

External COTS Interfaces TIU Dictation Support HL7 Uploads and downloads dictation service files.

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

IHS Interfaces

HL7/GUI

Use

Reference Lab Inbound Messages DynaCare LabCore Inbound Messages Sonora Quest Lab Inbound Messages Quest Lab Inbound Messages

HL7

Interfaces to DynaCare Laboratory.

HL7 HL7

Interfaces to LabCore Laboratory. Interfaces to Sonora Quest Laboratory.

HL7

Interfaces to Quest Laboratory. Interfaces to Quest Diagnostics Laboratory. Interfaces to RML Laboratory. Interfaces to SCC Laboratory. Interfaces to Unilab Laboratory. Creates a Host file to be sent to IMMServe - commercial software called ImmServe, distributed by Medical Decisions Associates, Inc. (MDA). This software is an immunization forecasting utility. Written in C. Transmits billing information to external billing system.

Quest Diagnostics Lab Inbound HL7 Message RML Lab Inbound Messages SCC Lab Inbound Messages Unilab Lab Inbound Messages ImmServe File formatting HL7 HL7 HL7 HL7/HOST

3M Coder Interface 3rd Party HOST Billing

Interfaces to hardware Pyxis Medication dispensers OmniCell Medication dispensers Script pro (APSS) dispensing system HL7 HL7 Medication dispensing machine. Medication dispensing machine.

Data to a printer

Medication label to a printer.

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

IHS Interfaces

HL7/GUI

Use

MedLog Interface to Bar Code readers Lab I-Linker Bi directional interface

HL7

Interface to bar code readers.

LSI (Large Scale Interface) Device interface HL7 HL7

Bi-directional interface to laboratory equipment.

CHR Pen based messages Automated Lab Instruments

Interface to pen based system. Transfers medical information from a lab instrument to the database. Interface through bar code readers.

Bar Code Administration BCMA

HL7

External Interfaces Not to COTS Products Lab HL7 Receive file of CHR transactions from a remote computer. The extract menu option collects and forwards CDMIS data to the Area office, and is consolidated and forwarded to Division of Data Processing Services (DDPS) by the close of business on the 25th of the month after the quarter ends. This interface, while an IHS interface, is not appropriate for other organizations and should not be utilized when downloaded. Exports immunization records to national database. Extracts data from the National Drug file for use inside the system.

Chemical Dependency

HOST

Cloverleaf for the Joslin Vision HL7 Network (JVN)

Host File for Immunization Records - ImmServer NATIONAL DRUG FILE

HL7/HOST

HL7

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

IHS Interfaces

HL7/GUI

Use

NATIONAL PATIENT CARE HOST DATABASE (BXP)

The Area Data Consolidation Export System (BXP) is designed to consolidate and merge data sent to the National Patient Information Reporting System (NPIRS) in Albuquerque, New Mexico. The facilities send the unprocessed data to the Area Office where it is processed and sent on to NPIRS to be merged and consolidated. Electronic Health Record system Windows-based graphical interface that helps providers manage all aspects of patient care.

EHR

GUI - VueCentric Framework, using the following: Delphi v7, RoboHelp X5 v13.10.801, AuthorIT 4.1, Visual Basic 6.0, C# (VS 2003), Medsphere OpenSource, Mozilla Public License 1.1, Larcom & Young, Raize Software, Dart Communications, FreeVBcode.com, Clever Components GUI Microsoft .NET v 2.0

ICare

Population Management (BQI) Allows providers to create and manage their own personalized panels (populations) of patients with user-defined common characteristics - HIV Management System merged into iCare. Creates Encounter forms.

VEN

GUI MS Visual Studio, .NET Framework with RPC calls GUI Visual CRS, Visual Basic .NET

CRS

Clinical Reporting System (BGP) Allows sites and Areas to review and report on local RPMS clinical data for GPRA and developmental performance indicators.

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

IHS Interfaces

HL7/GUI

Use

Scheduling

GUI - Microsoft .NET v Schedules patient visits (BSDX). 2.0 GUI - Visual Basic through RPC calls GUI - Windows .NET Displays a patients chart (BPC).

Patient Chart

Diabetes (BDM)

Diabetes-specific patient management tool. Exports patient registration and visit data to the IHS National Data Warehouse. This is not useful for nonIHS sites. To various third party billing environments. The Pharmacy Auto Refill system enables RPMS to interact with a commercial automated telephone system (AudioCare) to refill prescriptions. The system will also check on prescription status and provide feedback to patients who are calling to have prescriptions refilled. Creates 5 of the 10 reports required for IHS sites receiving grants administered by the Bureau of Primary Health Care (BPHC). The reports are manually sent to BPHC. Creates a UB-92 Electronic Claim File. Helps providers make clinical decisions about immunizations and follow up with patients and communities with low immunization coverage to ensure they are protected.

Data Warehouse Export System (BDW)

HL7

Pharmacy Point of Sale (ABSP) Pharmacy Auto Refill System (BEX)

HOST

AudioCare automated telephone refill system

Uniform Data System (BUD)

Host file

Third Party Billing (ABM) Immunization Module

Host file HL7 and ImmServe

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

IHS Interfaces

HL7/GUI

Use

Immunization Data Exchange

HL7 -HL7 Communications Bridge application on the STC Web site

The Immunization Data Exchange Interface is a two-way Generic Interface System (GIS) HL7 interface that allows the exchange of immunization data for children from birth (0) to 19 years of age with State immunization registries. The Indian Health Service (IHS) Computerized Public Health Activity Data System (CPHAD) application provides for the entry of public health activity being performed by clinicians or other providers of public health activities. This software application will work in conjunction with the existing Resource and Patient Management (RPMS) applications. Automated data transfer to the Referred Care Information System (RCIS). Electronic Explanation Of Benefits Report (EOBR) transmission. Medical data with automated transfer to the Patient Care Component (PCC). The PCC Data Transmission system is designed to process and transmit Patient Registration and clinical data to the IHS Division of Data Processing Services in Albuquerque, New Mexico, for national statistical reporting purposes. Generic interfaces to outside Radiology Reporting packages. Report entry can be done through vendor-supplied voice recognition units with an HL7 interface provided partially by this package and partially by the vendor (MedSpeak, PowerScribe, TalkStation, and so on.

Computerized Public Health Activity Data System CPHAD

GUI Visual Basic .NET

Contract Health Management Information System (CHS/MIS)

HOST

PCC DATA TRANSMISSION HOST SYSTEM

Radiology and Nuclear Medicine

HL7

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

IHS RPMS FOIA Distribution Version

Version 1.0

Interfaces Within the Database Not Used by IHS

Non-IHS (VistA) Interfaces Internal M Interfaces HL7 Supply Interface HEC Health Eligibility Center MST Military Sexual Trauma Registration patent record flag (PRF) 10-10T Registration Dietetics Order Entry/RR EHR Electronic Health Record Surgery Master File ADT Messages to other facilities RADIOLOGY BCMA Bar Code Medication Administration External COTS interfaces COTS Pharmacy system RAI/MDS Residential Assessment Instrument National PRF(Patient Record Flag) Software MAS Software Interfaces to hardware VIC ID card machine

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

10

IHS RPMS FOIA Distribution Version

Version 1.0

Non-IHS (VistA) Interfaces CAREVUE - CARELIFE LIFELOG External Interfaces Not to COTS Products CPRS Registration National Flag Assignment IFC event Capacity Management RUM NATIONAL DATA BASE

Remote Procedure Calls (RPCs)

Remote Procedure Calls (RPCs) are used in an M environment to let external applications query into the M global structure and extract data by running M Routines to collect the data and then return the appropriate data to the calling application. This activity requires three distinct parts to succeed: A calling application that sends a request to execute an M routine. An M routine that collects data and returns it to the calling application. Internal M structures that permit the user to activate the external call and then validate that the M routine is a valid one.

The establishment of the permissions is covered in the Remote Procedure Call Manual at http://www4.va.gov/vdl/application.asp?appid=23. This manual explains in detail all of the necessary permissions that must be established, as well as how to use RPCs. The M structure that must be built to handle RPCs is in a global called Remote Procedure and currently contains 2,631 entries that cover the entire VA and IHS RPC environment. This file is used as a repository of server-based procedures in the context of the Client/Server architecture. By using the RPC broker, applications running on client workstations can invoke (call) the procedures in this file to be executed by the server and the results will be returned to the client application. Each remote procedure entry is associated with an entry point (ROUTINE with optional TAG). Calls to these procedures can include parameters of different value types. The resulting value of the call can be either a string, a list of strings or a word processing string as indicated by the RETURN VALUE TYPE field (.04).
Configuration Guide - Addendum I March 2010 Interfaces between IHS M Environment and Other Systems

11

IHS RPMS FOIA Distribution Version

Version 1.0

A PRINT of this file can show the Name, Routine, Tag and Description of the call. An example is given in the table below.
Name Routine Tag Description

ORQORB SORT

ORQORB

SORT

ORQPT

ORQPTQ3

ATTPRIM

ORQPT CLINIC PATIENTS

ORQPTQ2

CLINPTS

ORQPT CLINICS ORQPT DEFAULT CLINIC DATE RANG

ORQPTQ2 ORQPTQ2

CLIN CDATRANG

ORQPT DEFAULT LIST SORT ORQPT DEFAULT LIST SOURCE

ORQPTQ11

DEFSORT

ORQPTQ11

DEFSRC

Returns the notification sort method for user/division/system/pkg. Returns a patient's attending physician and primary provider. Returns patients with appointments at a clinic between start and stop dates. Function returns a list of clinics. Returns default start and stop dates for clinics in the form: start^stop. Start and stop are free text and are not in FM format. Returns the current user's default patient selection list SORT ORDER setting. Function returns the source of the current user's default patient list.

Configuration Guide - Addendum I March 2010

Interfaces between IHS M Environment and Other Systems

12

IHS RPMS FOIA Distribution Version

Version 1.0

Routines Modified for FOIA

Imbedded Telephone Numbers
There were a significant number of M routines that contained imbedded phone numbers which would only be applicable to IHS. These phone numbers were removed manually and replaced with 999-999-9999. If there was a comment concerning a particular phone number, the phrase was changed to read ...contact the Help Desk, where appropriate. The table below shows the routines where the phone numbers were changed. ABSPOSAE ACDNOTE ACHS3112 ACHS3115 ACHS31P7 ACHSEOB ACHSTV ACMBUL7 AGSSLTXT AMHNAVRP AUM4101 AUT98P10 AUT98P13 AUTP6PRE AZHLRER BDMBULP1 BLRAPRE BLRP24PC BLRPRE1 BLRPRE19 ABSPOSFX ACHS3110 ACHS3113 ACHS31P5 ACHS31P8 ACHSPOSM ACHSVAR ACPT27FX AGTXALL1 APCLM1 AUM4103 AUT98P11 AUTP4PRE AUTP7 BARPT18 BDWDDR BLRKIDSU BLRP25PC BLRPRE17 BLRPRE20 ABSPOSN3 ACHS3111 ACHS3114 ACHS31P6 ACHS31P9 ACHSPRE ACMBUL6 AGSSLETR AMERENV1 APSGMSG AUM9115 AUT98P12 AUTP5PRE AVAPCHK BDMBUL6 BGU15E BLRP22PC BLRPRE BLRPRE18 BLRPRE21
Routines Modified for FOIA

Configuration Guide - Addendum I March 2010

13

IHS RPMS FOIA Distribution Version

Version 1.0

BLRPRE22 BMC4P0 BMC4P3 BMXE01 BSDX2E IBINI00O IBINI00Y PSOTPCLW ZIBENVCK

BLRPRE24 BMC4P1 BMC4P4 BPC15E BVCONV IBINI00S IBINI010 PSOTPHL1 ZIBPKGF

BLRPRE25 BMC4P2 BMCP4 BRNPTCH2 IBINI00L IBINI00V KLASTIM XBHFMAN2 ZIBRPI2

Imbedded Email Addresses

There were a significant number of M routines that contained imbedded e-mail addresses which would only be applicable to IHS. These e-mail addresses were changed manually to @DOMAIN.NAME. The table below shows the routines where the e-mail addresses were changed. APC3INIS APC7INIS AZHNINIS BKUCW2KV DG53293B DGVREL2 FHINIS HLEVSRV IBDEINIS KMPRBD01 LEXEDF1 LR302POA OCXOCMPV ORY109 APC4INIS AUP6INIS BCH1INIS BWINIS DG53334B DICE GMP1INIS HLEVSRV4 IBINI02S KMPRBD02 LEXLGM LRIPOSXM OCXOPOST ORY116 APC5INIS AUT98P12 BCH2INIS BZSMINIS DGEN339 DIFROM7 GMPLINIS IB20PT5 IBINI0E2 KMPSGE LEXPL LRSRVR OR3CONV1 ORY120 APC6INIS AVAPINIS BCHEXTAP DG53244U DGEN408 DIPKINIS GMTSXPS1 IBARXEC2 IBINIS LEXAR7 LEXXST MCARPCS4 OR3POST ORY125

Configuration Guide - Addendum I March 2010

Routines Modified for FOIA

14

IHS RPMS FOIA Distribution Version

Version 1.0

ORY131 ORY85 PSJVINIS PSOCLUTL PSSDINT SD53P234 SR54UTL XMAH1CP XMR1 XPDCUST XTINEND XUCSRV

ORY132 PSBSAGG PSN4P4 PSOCPBAK PSUTL1 SDHPIB SROATCM2 XMDIR1A XMRPCTS1 XPDIST XTINITY XUPSPD1

ORY141 PSGWINIS PSO55FX2 PSOCPIB3 PXICLN1 SDOQMP VALMINIY XMDIR1B XMS1 XQABGEN XU8343R

ORY148 PSJIPST PSO55FX3 PSOTPPOS SCMSP0 SDWLCU1 XGKB1 XMGAPI3 XMS2 XTCMFILN XUCMNIT4

Imbedded IP Addresses
There were a significant number of M routines that contained imbedded IP addresses which would only be applicable to IHS. These IP addresses were manually changed to a standard dummy IP value. The table below shows the routines where the IP addresses were modified. ABSPOSAB BARPT18 BDW1VBLI VENPCCM1 ABSPOSJ1 BARPT172 BDWCVAR XLFNSLK AZFMENV BARPT173 BDWDDR XMR0BLOB BAREISS BARPT174 BDWDWPX1 XWBTCPZ

Imbedded DNS Addresses

The DNS addresses in the table below had IHS.GOV replaced by DOMAIN.NAME. ACHS3114 APCL3023 AUM9115A BAREV184 BARPT18 ACHS3115 ASUWSND1 BAREV181 BAREV185 BDWPRE AGTXALL AUM4101 BAREV182 BAREV186 BGOPOST APCHPWH4 AUM4103 BAREV183 BAREV189 BHLPID
Routines Modified for FOIA

Configuration Guide - Addendum I March 2010

15

IHS RPMS FOIA Distribution Version

Version 1.0

BJPC1P1 XBTRK

BKUCW2KV

BPXRMP4I

XB3P9

Security Hashing
Routines containing content associated with the secure transmission of access and verify codes have been sanitized. The consumer of the FOIA product(s) will need to provide their own encryption/decryption algorithms. Security Hashing - Access and Verify code are not hashed. The following routines will need your own hashing code added in the appropriate places: XUSHSH XUSHSHP

Configuration Guide - Addendum I March 2010

Routines Modified for FOIA

16

IHS RPMS FOIA Distribution Version

Version 1.0

Cleaned Data Files (Globals)

There were a number of M globals that contained data which would not have been appropriate for distribution with the FOIA release. A particularly important file is the list of CPT codes used by the system. Anyone wishing to use CPT codes in their implementation must buy the rights to the codes from the American Medical Association (AMA). The table below lists which globals were cleaned. ^AUTTIMM IMMUNIZATION (file #9999999.14) - This file is a list of Immunizations and associated codes developed specifically for use in the IHS. This file contains a full descriptive name for each Immunization, plus a shortened name of Ten Characters which is used on the Health Summary and on reports where space is limited, plus a Two Digit Code for each Immunization. Contains a node for HL&-CVX code, CPT code, ICD Diagnosis Code, and ICD Procedure Code. ^BITMP Not a FileMan file contains patient identifier information. ^BITN - BI IMMUNIZATION TABLE HL7/CVX STANDARD (file #9002084.94) - - There are 126 records in the file. Contains CPT codes and HL7/CVX codes and ICD Diagnosis Codes, and ICD Procedure Codes. ^DGEN(27.17 - CATASTROPHIC DISABILITY REASONS - THIS FILE SHOULD NOT BE MODIFIED BY USERS! Per the Enrollment Phase II SRS (section 6.8.1.2), this file has been added to store the acceptable reasons why a veteran may be classified as catastrophically disabled. ^HL(772 - HL7 MESSAGE TEXT FILE - This file contains information related to the processing of all incoming and outgoing messages. ^HLCS(870 - HL LOGICAL LINK FILE (file #870) - This file serves two purposes. It is a FileMan-compatible transmission log. The Low Layer Protocols write and read directly from this file. (See routines HLCSDR1 and HLCSDR2) This file stores parameters that govern the behavior of the Low Layer Protocols. Fields like: READ TIMEOUT, ACK TIMEOUT, LLP START BLOCK, and LLP END BLOCK, are fields that govern how long the finite state machine waits for data to come down the line (READ TIMEOUT), how long it waits for a lower level acknowledgement (ACK TIMEOUT), and which control characters define the beginning and end of a message (LLP START BLOCK and LLP END BLOCK). This file also stores information that drives the SYSTEMS LINK MONITOR display option. Fields like, IN QUEUE FRONT POINTER, IN QUEUE BACK POINTER are used to manage the data flow in the queues but they are also displayed on the SYSTEMS LINK MONITOR under the alias's MESSAGES PROCESSED and MESSAGES RECEIVED. Fields like STATE and DEVICE TYPE are also used to drive the SYSTEMS LINK MONITOR. These fields are updated by the lower layer protocols in order to give real-time feedback as to what is occurring on a link. For example, when a message is received (see HLCSDR1) the state transitions from IDLE to READING.

Configuration Guide - Addendum I March 2010

Cleaned Data Files (Globals)

17

IHS RPMS FOIA Distribution Version

Version 1.0

^HLEV(776 - HL7 MONITOR JOB file With each Monitor Master Job run, the master job checks every monitor entry in the HL Event Monitor file (#776.1). If it is time for the monitor to be queued, a background job is queued to run that monitor. At the time of queuing an entry is created in this file holding (among other values) the internal entry number of the monitor entry in file 776.1. The IEN is stored in the Monitor field (#3), and this M cross-reference holds the IEN of the monitor. Note: The Monitor field does not point to the monitor, strictly speaking, because this field is a free-text field. However, since it holds the IEN, it is a functional pointer to the monitor file. (The field was created this way to enable monitors to be deleted at will without worry about dangling pointers.) ^HLEV(776.1 - HL7 MONITOR file. Under HL7 Main Menu Option -> Message Management Options - > Purge Messages This option should be run to purge the listed messages. This job utilized the AI cross-reference to purge records in file 772 and 773 with maximum efficiency. It is not guaranteed to purge all records that need purging, but should quickly purge the vast majority of such records. Its main limitation is that it limits itself to messages that have a status of Successfully Completed. There are two Fast Purge jobs. This one is the main job, in that it should be running nearly continuously. The second job will be started less frequently, and if there is no work to do will go back to sleep for several hours. Its purpose is to prevent purging from getting backed up when the messaging system is under very heavy load. ^HLEV(776.2 - HL7 MONITOR MASTER JOB FILE On a parameter-controlled frequency, a master job is run to determine whether individual monitors should be run. When these master jobs start, an entry is made in the HL Event Master Job file (#776.2). The .01 field of this file is Creation Time, and this B xref is created based on the date/time value in this field. ^HLEV(776.3 - HL7 MONITOR EVENT TYPE FILE - It appears that this file keeps track of error events that occur during message sending. ^HLEV(776.4 - HL7 MONITOR EVENT file It appears that this file is ordered by date and could therefore be specific to actions that have occurred in the past. ^HLEV(776.5 - HL7 MONITOR EVENTS PROFILE FILE ^HLEV(776.999 - HL7 MONITOR PARAMETERS FILE ^HLMA( - HL7 MESSAGE ADMINISTRATION FILE - This file is used to create and maintain unique message IDs. It also contains a date/time when each ID was created.

Configuration Guide - Addendum I March 2010

Cleaned Data Files (Globals)

18

IHS RPMS FOIA Distribution Version

Version 1.0

^INRHD - INTERFACE DESTINATION - This file holds the information necessary to route a transaction to its appropriate location. For outgoing transaction either a Transceiver Routine or a Mail Recipient is defined. For incoming transactions a Transaction Type is defined. ^INXPORT Not a FileMan File structure. - IN GIS Package Exporter - BHL IHS Interfaces with GIS - this routine will take all components of a package and export to transport global ^INXPORT. This global will then get moved to the remote system and get imported into GIS. This will act as a replacement to the KIDS data install. ^LAHM(62.94 This file is used to store the messages that are sent or received by the Lab Messaging system. This file is populated by application routines and should not be edited by users.

Nodes
The nodes in ^BAR indicated below should be modified to reflect the appropriate information. ^BAR(90052.03,2,1,4,0)=" [enter organization description here]" ^BAR(90052.03,2,1,5,0)=" [enter division description here]" ^BAR(90052.03,2,1,6,0)=" [enter site here]" ^BAR(90052.03,2,1,7,0)=" [enter office here]" ^BAR(90052.03,2,1,19,0)=" [enter phone number here] We appreciate your cooperation." ^BAR(90052.03,2,1,24,0)=" [enter name here]" ^BAR(90052.03,6,1,1,0)=" [enter organization description here]" ^BAR(90052.03,6,1,2,0)=" [enter division description here]" ^BAR(90052.03,6,1,3,0)=" [enter site here]" ^BAR(90052.03,6,1,4,0)=" [enter office here]" ^BAR(90052.03,6,1,16,0)=" [enter phone number here]. We appreciate your cooperation." ^BAR(90052.03,6,1,21,0)=" [enter name here]" ^BAR(90052.03,10,1,15,0)=" ~W !?6,""DEPOSIT#: "",$G(BARSCHED)" ^BAR(90052.03,10,1,23,0)=" ~W !,""Transaction number:___________________________""" ^BAR(90052.03,11,1,13,0)=" ~W !?6,""DEPOSIT #: "",$G(BARSCHED)" ^BAR(90052.03,11,1,20,0)=" ~W !!,""Entry by:____________________________________ ^BAR(90052.03,13,1,13,0)=" ~W !?6,""DEPOSIT #: "",$G(BARSCHED)"

Configuration Guide - Addendum I March 2010

Cleaned Data Files (Globals)

19

IHS RPMS FOIA Distribution Version

Version 1.0

Other Modifications
Security
The following Access and Verify Codes are pre-set for the database for the initial installation: User: ADAM,ADAM Access Code: ADAM.01 Verify Code: USER.001 User: MANAGER,SYSTEM Access Code: SYSTEM.01 Verify Code: USER.001

MailMan
The MailMan Domain Name must remain as IHS.GOV.

Configuration Guide - Addendum I March 2010

Other Modifications

20

IHS RPMS FOIA Distribution Version

Version 1.0

Appendix I. VueCentric
Medsphere VueCentric Copyright (c) 2004-2010 Medsphere Systems Corporation VueCentric is a framework designed to support providers across a variety of care settings. It is used in the EHR component of the RPMS system.

Licensing
VueCentric includes software developed by Medsphere, Copyright (C) 2004-2010 Medsphere Systems Corporation. VueCentric is open source, but different pieces of VueCentric use 3rd party licensing terms. The details of all the pieces are laid out below. Reference 1 Vendor MSC Usage Prod none Dev none Redistribution Binary none Source none License Terms Reference IHS contract # GS-35F0240R; Response to SOW and Addendums for license terms. Reference IHS contract # GS35F-0240R; Response to SOW and Addendums for license terms.

MSC

Prod none Dev none

Binary none Source none

Borland Software Corporation Indian Health Service JEDI

Prod none Dev license Prod none Dev none

Binary none Source proprietary Binary none Source none Open Source Mozilla Public License 1.1.
see http://sourceforge.net/projects/jcl see http://www.borland.com

under FOIA regulation

Prod none Dev none

Configuration Guide - Addendum I March 2010

Appendix I. VueCentric

21

IHS RPMS FOIA Distribution Version

Version 1.0

Reference 6

Vendor Indy Components IDE Generated

Usage Prod none Dev none

Redistribution Open Source

License Terms Mozilla Public License 1.1

see http://www.indyproject.org/

Prod none Dev none

Binary none Source n/a Binary none Source proprietary Binary none Source proprietary Binary none Source proprietary Binary none Source proprietary Binary none Source proprietary Binary none Source none

n/a

Larcom & Young

Prod none Dev license

see http://www.lyoung.com

Raize Software

Prod none Dev license

see http://www.raize.com

10

Dart Communication s Microsoft Corporation

Prod none Dev license Prod none Dev none

see http://www.powertcp.com

11

12

ComponentOne

Prod none Dev license

see http://www.componentone.com

13

FreeVBcode.co m

Prod none Dev none

see http://www.freevbcode.com/Show Code.Asp?ID=5904

14

AuthorIT Software Corporation

Prod none Dev none

Binary none Source none

n/a

Configuration Guide - Addendum I March 2010

Appendix I. VueCentric

22

IHS RPMS FOIA Distribution Version

Version 1.0

Reference 15

Vendor Adobe (Macromedia RoboHelp) Clever Components

Usage Prod none Dev none Prod none

Redistribution Prod none Dev none Binary none

License Terms n/a

16

Purchase of the source code includes royalty free licensing.

See http://www.clevercomponents.com

Dev License

Source proprietary

Collaboration
VueCentric will be part of larger open source projects. Aspects of the design, requirements definition, development, and testing may be done in the community. Medsphere.org will be the central location for this collaborative development process.

Configuration Guide - Addendum I March 2010

Appendix I. VueCentric

23

IHS RPMS FOIA Distribution Version

Version 1.0

Contact Information
If you have any questions or comments regarding this distribution, please contact the OIT Help Desk (IHS).
Phone: (505) 248-4371 or (888) 830-7280 (toll free) Fax: Web: (505) 248-4363 http://www.ihs.gov/GeneralWeb/HelpCenter/Helpdesk/index.cfm

Email: [email protected]

Configuration Guide - Addendum I March 2010

Contact Information

24