Alameda County Health Care Services Agency · 2008-06-25 · To run MICRS, start Visual Foxpro. The...

Alameda County Health Care Services Agency

Medically Indigent Care Reporting System

(MICRS)

SYSTEM REFERENCE

ALAMEDA COUNTY MEDICALLY INDIGENT CARE REPORTING SYSTEM

(MICRS)

SYSTEM REFERENCE

TABLE OF CONTENTS

STARTING MICRS ............................................................................................... 5 Running MICRS............................................................................................................5

Menu Reference ..................................................................................................... 6 The MICRS Menu.........................................................................................................6 Menu Reference.............................................................................................................7

LOADING PROVIDER DATA ............................................................................. 9 Types of Data .................................................................................................................9 Pre-load special procedures..........................................................................................9 Loading provider data to the holder – standard process.........................................11 Handling invoices without data..................................................................................14 Loading provider data to the holder – “Batch” load ...............................................15 Loading the holder to CMD .......................................................................................18

PROVIDER REPORTS ....................................................................................... 20 Printing Provider Reports ..........................................................................................20 Distributing Provider Reports ...................................................................................21 About Encryption........................................................................................................22 About Outlook Security ..............................................................................................22 Provider Error Corrections........................................................................................23

OTHER REPORTS.............................................................................................. 24 Other Provider Reports ..............................................................................................24 The Ad-Hoc Utilization Report ..................................................................................28

Revised 30 September 2005 of 69C:\Documents and Settings\cjmyers\Desktop\IRFQ\Exhibit F_OP


(MICRS)

SYSTEM REFERENCE

STATE REPORTS ............................................................................................... 30 Preparing to run state reports....................................................................................30 Running the calculation for a period.........................................................................35 Checking the calculations ...........................................................................................37 For more information about checking state reports ................................................39 Preparing the state diskette ........................................................................................39 Post-report processing ................................................................................................39

RELATED APPLICATIONS .............................................................................. 40 ELIGIBILITY.EXE – MEDI-CAL ELIGIBILITY CHECK SYSTEM ................40 ZIPLOOKUP.EXE – ZIP CODE VERIFICATION SYSTEM ..............................43 PHDATA.EXE – PUBLIC HEALTH DATA EXTRACTION ...............................44 ONE-E-APP DATABASE SNAPSHOT DOWNLOAD...........................................45

PERIODIC MAINTENANCE - MICRS............................................................. 46

MISCELLANEOUS SYSTEM MAINTENANCE.............................................. 47

API LIBLIBRARY REFERENCE...................................................................... 48 NSDPGP3.DLL v1.3....................................................................................................48 AZIP.DLL – PKZIP API ............................................................................................63

THE DEVELOPMENT ENVIRONMENT ........................................................ 65 The MICRS Environment ..........................................................................................65 Useful MICRS Utilities ...............................................................................................65 Source Control.............................................................................................................66 Miscellaneous Notes, tips, and tricks .........................................................................67



(MICRS)

SYSTEM REFERENCE

FIGURES

The Visual Foxpro IDE .................................................................................................................... 5 The MICRS Menu............................................................................................................................ 6 ACMC types of data......................................................................................................................... 9 Summary of Special Processing ..................................................................................................... 10 The Import Screen.......................................................................................................................... 12 The Data Integrity Compliance Report .......................................................................................... 13 ACMC file codes and extensions ................................................................................................... 15 The Set Up Batch Import screen .................................................................................................... 16 Import file type values.................................................................................................................... 17 Financial Class values .................................................................................................................... 17 The Load To CMD screen.............................................................................................................. 18 The Provider Reports selection screen ........................................................................................... 20 Summary of Report Distribution by Provider Type ....................................................................... 21 Procedures For Correcting Errors On Faxback Report................................................................... 23 The Provider Reports Selection screen........................................................................................... 24 The Demographic/Utilization/Charge Data Ad-Hoc Report Definition screen.............................. 28 Ad-hoc Utilization Report Sample SQL Queries ........................................................................... 29 State Reports - Title Form screen................................................................................................... 35 State Reports – Verify Calculation screen...................................................................................... 36 MCAL_EV Status Display............................................................................................................. 41 Medi-Cal Inquiry Response Display .............................................................................................. 41 Summary of Periodic Maintenance Functions................................................................................ 46 MICRS directories – where everything lives ................................................................................. 65 Useful MICRS utilities................................................................................................................... 65


ALAMEDA COUNTY MEDICALLY INDIGENT CARE REPORTING SYSTEM (MICRS)

OPERATING PROCEDURES

STARTING MICRS

Running MICRS MICRS does not run from an executable. You use the Visual Foxpro Integrated Development Environment to run MICRS. To run MICRS, start Visual Foxpro.

The Visual Foxpro IDE

Commands are entered into the Command Window. The Task Pane Manager is used to switch between projects. To start MICRS, enter the command DO ENTRY in the command window.

Revised 30 September 2005 of 69 C:\Documents and Settings\cjmyers\Desktop\IRFQ\Exhibit F_OPGUIDE.doc



Menu Reference

The MICRS Menu Import Operations

Pack Holder File Import Data To Holder Load Holder To CMD Set up Batch Import Run Batch Import View Loader Log View Import Status Summary View Holder File Administration User List Provider List Provider Contacts DIC Rules Post Med-Cal Status to CMD Clean CMD table Create SB12/612 Cross-Check File Create both Cross-Check Files Create new FY record sets Create Contract Merge XLS

State MICRS Reporting Title Form Display current table status Display state table status Display history table status Review MICRS Data & Tables Review Processed MICRS DATA Review Table 1A Review Table 15 Run Transfer/Calc Procedures Print Table Correspondence Check Print Period Comparison Report Print/Review Reports Print All Tables Print/Review Reports Create State Mandated Diskette MICRS History Operations Post MICRS Tables To History Review History MICRS Tables History Table 1A History Table 15 Print/Review Reports Other Reports Cost Analysis Provider Reports Federal Poverty Level Analysis Medi-Cal / CMSP Eligibility Demo/Utilization/Charge Data CBO Contract Compliance - Patients CBO Contract Compliance – Visits Tools Match to CMD Display open tables Register NSD Encryption Library

The MICRS Menu



MENU REFERENCE

Menu Reference Import Operations

Removes deleted records from IMP_H1 Pack Holder File Imports one received MICRS data file Import Data To Holder Loads all imported files to the master file Load Holder To CMD Allows selection of multiple received files for unattended importing

Set up Batch Import

Unattended importing of multiple MICRS data files

Run Batch Import

Log of files loaded View Loader Log Summary grid of file import status View Import Status Summary View Holder File Administration User security and password maintenance User List Maintain provider table PROV_FL Provider List Maintain provider contacts table PROVCONT Provider Contacts

DIC Rules Data Integrity Compliance Report Rules Post from MCAL_EV to CMD if ELIGIBILITY.EXE did not complete.

Post Med-Cal Status to CMD

On request from Public Health, creates SB12_612.TXT

Create SB12/612 Cross-Check File

On request from Public Health, creates AMR.TXT

Create AMR Cross-Check File

On request from Public Health, creates SB12_612.TXT and AMR.TXT

Create both Cross-Check Files

Creates new record sets in all FY-(fiscal year) related tables

Create new FY record sets

Updates PROV_FY.XLS Word merge data source for printing provider contracts

Create Contract Merge XLS

State MICRS Reporting Title Form View/update state report title information

Display current table status Display current contents of calc tables Display state table status Display current contents of history tables Display history table status Review MICRS Data & Tables View contents of calculated state tables Review Processed MICRS DATA Review Table 1A

Review Table 15 Build tables for state report Run Transfer/Calc Procedures

Print Table Correspondence Check Cross-check totals between tables to detect



MENU REFERENCE

calculation errors Side-by-side summaries of selectable periods

Print Period Comparison Report

Print/Review Reports Print contents of all calculated tables Print All Tables Selectively print contents of calculated tables

Print/Review Reports

Create diskette image file for transmission to state

Create State Mandated Diskette

MICRS History Operations Append contents of TABLE_xx tables to H_TBL_xx tables

Post MICRS Tables To History

View H_TBL_xx tables Review History MICRS Tables History Table 1A

History Table 15 Print any complete set of state table data from history

Print/Review Reports

Other Reports ACMC or CBO Cost/Charge comparison Cost Analysis Selectively print provider reports Provider Reports Federal Poverty Level Analysis Medi-Cal enrolled patients reported in MICRS as CMSP

Medi-Cal / CMSP Eligibility

Demographics / Utilization metrics Demo/Utilization/Charge Data Percent of contract metrics attained to date CBO Contract Compliance - Patients Percent of contract metrics attained to date CBO Contract Compliance - Visits Tools General “bump” utility: Check CMD for occurrence of specific patients

Match to CMD

Display open tables Required for encrypting reports for emailing, or on-the-fly decrypting of import data files. Use as required (e.g. when installing MICRS on a new computer).

Register NSD Encryption Library




LOADING PROVIDER DATA Data comes either via 3.5” diskette or via e-mail. Data is submitted with an original invoice. Do not process data until you have an original signed invoice. Loading provider data requires two steps. First you load the data to the holder and then you load the holder to CMD. Some files are loaded using a standard procedure, while other files require additional processing and/or options to be set before loading. There are two methods for loading provider data: One at a time, and “batch” – processing many files together. Types of Data Data from CBOs is loaded using standard procedures and no special options need to be set. There are currently seven different types of data from the ACMC, six of which require special handling and/or options to be set. The table below describes types of data from the ACMC: File Type File Format Description of files Standard Files MICRS std format OT1, OT2, and OT4 files OT3 MICRS std format OT3 file (E/R w/admit facility charges) ECD Excel spreadsheet or CSV Oakcare non-E/R pro fees from SutterConnect Big Valley Excel spreadsheet or CSV Oakcare ER & UC pro fees from Big Valley OMS Excel spreadsheet Contracted outside medical services PCN Excel spreadsheet Contracted pharmacy charges Unilab Special CSV format Contracted lab procedure charges

ACMC types of data

Pre-load special procedures Some data is submitted in Excel spreadsheet format. In most cases the data can be loaded directly from the XLS format file, but in some cases, the Excel file may need to be converted to a CSV (Comma Separated Variable) format before loading. In particular, the system may not correctly import date values. See the table of special processing tasks below for more information. The general procedure for converting Excel files is: 1. Copy the file to the correct month’s import directory under K:\IMPORT. Rename the file if

necessary so the name identifies the provider and reporting period. See the CMSP contract for file naming conventions. .

2. Remove all formatting from the amount column.



3. Verify that the date columns contain valid dates. Date columns entered as numbers or text in

the format MMDDYYYY are preferred. Columns formatted as dates must be of the format MM/DD/YYYY. If necessary, reformat the dates to display in the format MM/DD/YYYY.

4. Save the spreadsheet as a Comma Separated Value (CSV) file type using File/Save As.

Name the file to indicate the file type and service month as described in the following table. The following table summarizes the processes required to pre-process special types of data: FILE TYPE SPECIAL PROCESSING OT3 No special preparation. Select the ACMC OT3 file type on the import screen. ECD Received file format is XLS. Import format is CSV.

1. Name the file ECDyymm.CSV. 2. Convert the Excel spreadsheet to CSV before import. 3. Select the ACMC ECD file type on the import screen.

Big Valley / SutterConnect

Received file format is XLS. Import format is XLS, or CSV if XLS fails. 1. The file is submitted either as 2 Excel files or as one file with two sheets.

To load the combined XLS file directly, supply the sheet name to be processed in addition to the filename. Run the procedure twice – once for each sheet in the file, specifying the correct sheet name each time.

2. Select the ACMC Big Valley file type on the import screen. 3. During the load-to-holder step, take care to inspect all fields, especially date

fields. If any date fields are blank or any fields are misaligned, abort the import and convert the spreadsheet to CSV format to re-import it correctly.

OMS

Received file format is XLS. Import format is XLS 1. Name the file OMSyymm.XLS. 2. No special preparation is required; however closely inspect all date fields, as

the data is manually entered and errors are common. 3. Select the ACMC OMS file type on the import screen.

PCN Received file format is XLS. Import format is XLS 1. Name the file PCNyymm.XLS. 2. No special preparation is required. 3. The dates are in the format YYYYMMDD. Don’t change the format. The

loader fixes the dates during loading. 4. Select the ACMC PCN file type on the import screen.

Unilab Received file format is SDF. Import format is SDF. 1. Name the file UNIyymm.TXT. 2. No special preparation is required. The loader automatically strips out any

heading lines. 3. Select ACMC Unilab file type on the import screen.

Summary of Special Processing


Loading provider data to the holder – standard process 1. Copy the file to the correct month’s import directory under K:\IMPORT, renaming the file if

necessary, except for ACMC files, which do not get renamed. The file naming convention is XXXyymm.TXT (or .DAT) where XXX is the provider’s file code from the PROV_FL table and . yymm is the month of service being processed.

2. If this is a resubmission, delete the previous record set using Import Operations/View Loader

Log – locate the record by provider and service date range. Note the IMP_UNIQ value. Press the delete button on the navigation bar. This deletes the Loader record and the associated IMP_H1 or CMD record set. Sometimes the IMP_H1 or CMD record set doesn’t get deleted, so check that the record set got deleted by performing the followinc commands in the Command window. USE IMP_H1 (or CMD) SEEK “<the IMP_UNIQ value>” (enclose value in quotes) SET DELETED OFF BROWSE Check that the delete indicator to the left of the record is black. If so, the set was deleted. SET DELETED ON If the record set was not deleted, not, delete the set manually: DELETE FROM IMP_H1 (or CMD) WHERE IMP_UNIQ=“<the IMP_UNIQ value>”

3. From the Import Operations menu, select Import Data to Holder. 4. Fill in the import screen.



The Import Screen

Choose the file type: Standard MICRS - All CBO and ACMC files not listed below ACMC OT3 - The ACMC OT3 file ACMC ECD - ACMC Oakcare non-E/R pro fees from EBMR ACMC Big Valley - ACMC Oakcare ER or UC pro fees from Big Valley ACMC OMS - ACMC Outside Medical Services ACMC PCN - ACMC contracted pharmacy charges ACMC Unilab - ACMC contracted lab procedure charges MHS/AOD - Mental Health or Alcohol & Drug charges from BHCS Std. Micrs XLS - Private hospitals and some CBOs. Std. Micrs CSV - Private hospitals and some ACMC formats Oak Care Delimited - Oakcare ER pro fees from MedAmerica prior to 10/1999 Click FILE to select the file to import. Navigate to the correct month’s directory under K:\IMPORT and select the file. For Big Valley XLS files, enter the sheet name to be processed.




“Reporting Period” is the date range of the file, which is usually monthly. The system attempts to calculate the reporting period based on the directory where the data is located. Verify the reporting period and change it if necessary. Special Instructions:

1. Un-check “Create Exception List” for private hospitals. 2. Leave Comments blank on this screen – add comments on the second page only.

6. Click Continue Import. The data is imported and displayed for review. Scan browse

window looking for obvious errors like misaligned columns, bogus dates, or blank or invalid values. If the data is ok, click CONTINUE. If not, click CANCEL to abort the process.

7. The data is imported and system runs the Data Integrity Check. When it finishes, the Data

Integrity Compliance Report (the DIC report) displays on-screen.

The Data Integrity Compliance Report




8. Print the DIC report. The second screen appears after printing completes.

Examine the DIC report to determine the overall data quality for the next step. Things to note on the DIC Report: - Look at lines 0010, 0080, 0100, 0130, 0150, 0180. Any X’s on these lines automatically makes the Data Quality “Medium” or “Low”. – Look at 0011. A number above 40% automatically makes the Data Quality “Medium”. – Look at 0230. If more than half the records are outside the reporting period, make sure you didn’t enter the wrong service date range, and check the data file to see if the provider sent the wrong file. – Ignoring X’s in 0190 – 0220, count the X’s. More than 2 X’s makes the Data Quality (second screen) “Medium”. More than 4 might make the Data Quality “Low”. Use your judgement. – Make sure “Total Records” on the second page agrees with the record count on the invoice.

9. Using the guidelines in the previous step, fill in the Data Quality on the second screen. The

Data Quality field is used to generate a paragraph in the Feedback letter regarding the overall quality of the data. Don’t choose “Low” unless the data is really bad and you have tried without success to get the provider to improve the data.

10. You can add comments about the DIC Report here, if necessary. Comments you enter here

appear as a paragraph in the Feedback Letter after the automatically generated individual comments about X’ed lines. Use complete sentences and explanations, but be succinct. . Don’t enter comments about lines with X’s – the system generates standard comments about lines with X’s. When finished, click ACCEPT DATA. This completes the data load process.

11. Update the Date Loaded and Number of Records columns in the MICRS LOG entry. 12. Complete the invoice, attach the original DIC report, and if the data is approved, forward the

invoice with DIC Report attached to Dee or Vana to be paid. If you don’t yet have an invoice, put the DIC report printout in the PENDING MICRS file folder until you receive the invoice. Once you receive the invoice, forward the completed invoice and DIC Report to Dee or Vana to be paid.

Handling invoices without data Sometimes you receive the invoice before you receive the data. Follow these steps:

1. Fill in the Date Invoice Received field on the invoice. 2. File the invoice in the “Pending MICRS Submittals” folder, to be processed after

the data arrives.




Loading provider data to the holder – “Batch” load To load several files at a time, use the “Batch Process” feature on the Import menu. This process uses a two-step process to mark and process a set of files without user intervention. Every file processed using the batch process should be named according to the standard naming convention and be located in a folder named according to the standard import directory structure. The standard file naming convention is: XXXyymm.ext where:

XXX is the provider’s standard 3 character filecode as defined in the PROV_FL table, or for ACMC files, the 3 or 4 character file type as coded in the GETIMPTYPE function in MICRLIB.PRG.

yymm is the 2-digit year and 2-digit month or 2-character quarter being reported .ext is the standard 3 character extension for the type of file

The standard directory naming convention is: For single-month files: K:\IMPORT\fy\yyyy-mm eg: K:\IMPORT\0102\2001-12 For quarterly files: K:\IMPORT\fy\fy-Qn eg: K:\IMPORT\0102\0102-Q1 The file code and valid extensions are:

Type of file File code Valid Extensions ACMC main files None OT1, OT2, OT3, OT4 ACMC Big Valley BVED, BVUC, BV XLS, CSV ACMC Oakcare ECD ECD, CMSP CSV ACMC OMS OMS XLS ACMC PCN PCN XLS ACMC Unilab UNI TXT, DAT CBOs Any TXT, DAT

ACMC file codes and extensions Do not express-load data for reporting periods other than single months or quarters! The standard import directory structure is: \IMPORT\FiscalYear\yyyy-mm. The fiscal year is 4 digits, and yyyy-mm is the reporting month. For example, import data for FY 2005-2006 is contained in the \IMPORT\0506\...directory structure. The structure is created using the “Create New FY Record Sets” function on the Administration menu. To utilize the batch process, follow steps 1-3 above in the section Loading provider data to the holder – standard process. Then continue with step 4 below:




4. From the Import Operations menu, select Set up Batch Import. In the Look In field, select

the reporting month directory, or if you have data from more than one reporting period to process, select the fiscal year directory. The dropdown list contains a history of directories you have previously accessed. When ready, click the FIND NOW button.

5. Select the files to process in the left hand file list window (use CTRL and Shift to select

multiple files) and drag them to the right window, or click the SELECT button. Note: The program will not allow you to select the same file twice (see ‘Tip’ on the next page).

The Set Up Batch Import screen

6. Navigate to other directories as necessary until you have selected all files to process 7. When you click the Create Batch button, a record is created in IMPBATCH for each file in

the Selected Files window, and then the Selected Files window is cleared. Click the Review Batches tab. Fill in the Date Received and Invoice Date columns for each file you selected. Review and correct the other fields as needed. Especially check the IMPORTTYPE and FINCLASS columns. If processing a Big Valley XLS file, fill in the sheet name. When you are satisfied that all records are correct, click the CLOSE button. The IMPORTTYPE column must contain one of the following values:




IMPORTTYPE

Column IMPORT FILE TYPE

1 Standard MICRS SDF 2 ACMC OT3 3 ACMC ECD 4 BIGVALLEY ED/UC 5 ACMC OMS 6 ACMC PCN 7 ACMC Unilab 10 Standard MICRS XLS 11 Standard MICRS CSV 12 BHCS (MHS or AOD)

Import file type values The FINCLASS column must contain one of the following values:

FINCLASS Column

Financial Class

I Indigent C ACMC Charity Care P ACMC Patient Pay

Financial Class values When processing ACMC Big Valley files, specify ED or UC in the XLSHEET column. Do this even if the file format is not XLS. The XLSHEET column is used to provide the correct SPCL_FL_NM column value in the LD_LOG table. 8. Choose Run Batch Import from the Import Operations menu. Review the batches again, then

answer Yes to the “Continue?” prompt. The files will be imported sequentially in the order they appear in the list. An Integrity report is printed for each file processed.

Note: If a file in the batch process fails for any reason, the PROCSTATUS column is set to “X” and the error message is posted to the STATMSG memo field. To re-run the file after correcting the error, set the IMPSTATUS field to blank and run the batch process again. Tip: To select the same file twice (e.g. if you want to process both Big Valley worksheets from the same XLS file) - On the NAME & LOCATION tab, select the file and click CREATE BATCH - On the REVIEW BATCHES tab, change the PROCSTATUS field of the selected file to X - On the NAME & LOCATION tab, select the file again and click CREATE BATCH again - On the REVIEW BATCHES tab, clear the X and fill in the two sheet names to process.




Loading the holder to CMD Once you review and approve all the Integrity reports, load the data to the CMD master table. Note: If you do not want to load a particular file to CMD, clear the file’s “Load to CMD” checkbox in the “View Loader Log” screen of the Import Operations menu.

1. Under Import Operations, click Load Holder to CMD. The screen shows all the pending record sets to be loaded. Examine the list and make sure you intend to load all the record sets listed. To prevent a record set from being loaded, Cancel, then click Import Operations/View Loader Log, find the loader record for the record set, and uncheck LOAD TO CMD.

The Load To CMD screen

The options on the screen are:

Express Load Doesn’t stop in the middle to ask if you want to continue. Use if you are reasonably sure the data format is correct.

Clean CMD during load Runs MICRCALC.CLN_CMD2 on the record set during the load process. This is highly recommended.




Pack Holder when done The Holder is empty after you finish, so packing it

is a good idea. Calculate demo/util when done Calculates standard current month and FYTD

Utilization for each provider and service month in the list..

Quit Application when done Terminates Visual Foxpro after all processing is complete. You can use this option to start a long load before leaving for the day.

2. Click CONTINUE to load the data. The process takes from several minutes to several

hours depending on the provider, time period, and the speed of the computer. Tip: Load ACMC data at the end of the day and let it run overnight.




PROVIDER REPORTS

Printing Provider Reports After you approve the data and load it to CMD, the provider is to receive reports either by email, QIC mail, or U.S. mail: From the Other Reports menu, select Provider Reports. Select the provider and reporting period. Check and uncheck boxes as necessary to get the reports you want. Note: Choose multiple providers using standard Windows multi-select keys (Ctrl-Click and Shift-Click)

The Provider Reports selection screen




Send the following reports to each type of provider:

ACMC

CBO Alameda Health

Consortium Private Hospital

Feedback letter √ * Consortium Summary Letter √ Data Integrity Compliance √ √ Current Period and YTD Utilizations √ √ √ Data Exceptions √∗∗∗ √∗∗∗ √ Match Exception Report/Spreadsheet √ ECD Exceptions ∗∗ Medi-Cal Status √ √

Summary of Report Distribution by Provider Type * CBOs who receive printed reports also receive a feedback letter. CBOs receiving reports via email do not need a feedback letter. ** The ECD Exception report is sent only on demand, and only in PDF format via email, since it can be very long. *** For ACMC, uncheck the “w/fax header” checkbox. For CBOs, check the checkbox. Distributing Provider Reports HIPAA rules do not allow transmission of identifiable patient information (PHI) via unencrypted email. Two reports, the Exception report and the Medi-Cal report, contain PHI. These two reports must either be encrypted or sent via postal mail. To send with PGP encryption to those providers identified as PGP-encryption (“P” in the ENCRYPT column of the provider list perform the following steps:

1. Select the providers and reports 2. Check EMAIL for the Presentation 3. Verify the PERIOD Date range and other options 4. Click RUN REPORTS

The system automatically emails each user the reports the user is configured to receive. User report configuration is stored in the PROVCONT table.

Tip: To speed up the report distribution process, first run the Demographic/Utilization reports (both this month and FYTD) Checking the CALCULATE and NO OUTPUT options. Then print all reports for distribution, unchecking the CALCUALATE option. That way the Demographic/Utilization report will print from stored values. The report calculation can run unattended, and then the report distribution (which you need to monitor) will go faster.




About Encryption HIPAA and other privacy regulations require that Patients’ private health information may not be sent via unencrypted email. MICRS uses PGP encryption to encrypt those MICRS reports that contain confidential patient data. Therefore the computer used to email MICRS reports must have PGP encryption installed, and a public key must exist for every user to receive any encrypted report. Of course, this implies that every user who receives one of the encrypted reports must also have PGP encryption installed so they can decrypt the reports they receive. About Outlook Security Beginning with Outlook 2000 SP2, Outlook detects and traps software that tries to send email programmatically. A dialog box appears requiring manual intervention to allow software-generated email to proceed. Thus, when emailing reports, you must respond to the Outlook security prompt once for each email recipient. There are free utilities available that handle this situation automatically. One such utility, “ClickYes” has been installed on the MICRS computer. Occasionally the email process will still stall and issue a prompt indicating that Outlook is busy. When this occurs, click “Switch to” and follow the prompts to allow MICRS to continue sending emails. The Utilization Report The “New Clients This Month” metric is calculated by subtracting the prior month’s FYTD (fiscal YTD) number of patients from the current month’s FYTD number of patients. Therefore, if the utilization for a prior month needs to be recalculated for any reason, the utilization for every month from that month through and including the latest month must be recalculated. It is good practice to always recalculate the TM (This Month) utilization any time the FYTD utilization is calculated.


Provider Error Corrections One of the provider reports, the Data Exception Faxback report, allows providers to provide you with corrected data values. This allows you to correct errors in the CMD table data manually, resulting in cleaner data and fewer rejected charges. This is important because the data that goes into the system today will be used to generate many different types of statistics for years into the future. When a provider faxes you a filled in Data Exception Faxback report, you correct the errors in the CMD table (see the table) and log the receipt of the fax.

Procedures For Correcting Errors On Faxback Report

Error Message Error Correction Procedure Patient City or Zip invalid

If the address indicates a county resident, correct the error and make sure CMD.RESIDENT is set to ‘Y’. If not a county resident, no action required.

Family size blank or invalid

If the correct family size is 1, no action is required. If not, correct the value and re-compute CMD.PCTFPL (see below)

Patient residence outside the County

If the address indicates a county resident, correct the address and change CMD.RESIDENT to ‘Y’. If not, no action is required

Family income above 200% FPL

If the income is corrected, correct value in CMD and re-compute CMD.PCTFPL (see below).

Family income greater than 4000

If the income is changed, change value in CMD and re-compute CMD.PCTFPL (see below).

Family size greater than 10

If the family size is changed, change value in CMD and re-compute CMD.PCTFPL (see below).

Procedures For Correcting Errors On Faxback Report You must compute the percentage FPL (CMD.PCTFPL) whenever the income or family size changes. Here is how to do it:

1. Browse CMD and click on the record to be changed 2. In the command window, type the following commands:

SET PROCEDURE TO MICRLIB ? FPL(CMD.MTHLY_INC,CMD.FMLY_SIZE,<fy>) where <fy> is the numeric 4-digit fiscal year of the date of service (i.e. 0102 for fiscal year 2001-2002).

3. Enter the value displayed into CMD.PCTFPL. 4. File the faxes and complete the grid in TRACKING.XLS:Data Corrections.



OTHER REPORTS

Other Provider Reports All provider reports are listed on the Provider Reports screen:

The Provider Reports Selection screen




Presentation Options

• Display Prints the report in PREVIEW mode • Print Paper Prints the report to the default printer • Email Generates PDF files and emails them to contacts indicated in

PROVCONT. PDF target directory is defined in system variable gcPDFDir. Requires Adobe Acrobat and MS Outlook.

• Create PDF Same as Email, but doesn’t email the files and doesn’t check the provider’s report type. Requires Adobe Acrobat.

• No Output For Utilization reports only. Calculates report values and stores them in the DEMOUTIL table for later printing, but generates no output. Use to speed up report distribution by calculating stats prior to distribution.

Utilization Report options:

Financial Class • Indigent – CMSP for all providers • Charity Care & Patient-Pay – Non-CMSP for ACMC only

Report:

• Charges – report as submitted • Costs – Adjust charges using the cost-charge ratio in PROV_FY.

Other Utilization Report Options: Calculate Normally checked. If unchecked, the Utilization report

is printed using the most recently calculated data stored in the DEMOUTIL table. If unchecled, the report runs faster but does not include any data added since the DEMOUTIL record was created

Include Non-resident By default, these categories are excluded from indigent Include over 200% FPL utilization reports. Check to include in utilization

report Include M-Cal enrolled Generate 4-report set Used only for ACMC, this option produces 4 reports:

- ACMC Combined - Highland - Fairmont - Freestanding Ambulatory Clinics combined





WHERE clause footer Prints at the bottom of the report the WHERE clause

that was used to select the data on which the report is based

Update FY Stats Enabled only if the period ending date is June. If

checked, utilization statistics in PROV_FY will be updated with figures calculated now



OTHER REPORTS

Revised 30 September 2005 of 69C:\Documents and Settings\cjmyers\Desktop\IRFQ\Exhibit F_OPGUIDE.doc

Report Description Foxpro Report Filename Notes Feedback letter

Letter to the provider’s Executive Director listing ‘X’ items from the Data Integrity report.

LETSINGL – Single month LETMULTI-Multi-month LETCAROL – ACMC

The HCSA logo and sender’s signature are included so this is ready for mailing. Send by QIC mail if a QIC code is listed in the heading

Consortium Summary Letter

Letter to Ralph Silber summarizing ‘X’ items from the Data Integrity report for all consortium CBO’s.

LET_RALPH

Data Integrity Compliance

Summarizes errors for 1 data file submittal.

DIC2 Reports all submitted files with services dates in the range specified, one file per page. Prints an ‘X’ next to errors which exceed contract metrics.

Utilization Statistical breakdown of a service period. This is the most used report in the system. Report Name: R_INT1

‘FYTD’ reports fiscal YTD for the ending date specified. To run a period other than one month or FYTD choose ‘This Period’ and enter the desired date range. Checking CALC for either report causes the system to calculate the report from the CMD table. Clearing CALC causes the system to read report data from the DEMOUTIL table for the most recently calculated report, which runs faster but won’t reflect data added since the last calculated report for the period requested.

Data Exceptions

Details errors for one period by location within provider.

Data Exceptions: EXCLIST1 Faxback: EXCLIST2

Detail and Faxback reports are identical except the Faxback reports prints a ‘Fax to HCSA’ section at the end of the report.

ECD Data Exceptions

‘Match’ errors on ECD, OMS, PCN, UNI and BV by TOS within ACMC location.

EXCLISTC Used for Acmc only, Match Exceptions can be created both as a report and as a spreadsheet.

Medi-Cal Status

Charges submitted to MICRS for patients found to be Medi-Cal enrolled.

If run from the Provider Reports screen, reports patients verified as MC enrolled in the last 45 days. If run from the Medi-Cal Status Report menu option, you can configure the entire report.



The Ad-Hoc Utilization Report You can print the Utilization report with specifiable selection parameters to produce statistics for a wide range of criteria using the Demographic/Utilization/Charge Data menu option from the Other Reports menu. For example, you can run the report for

• A specific ACMC service location • Med-Cal, Non-Resident, or other non-eligible charges normally excluded from the report • Specific age groups, ethnicities, or geographical areas • Any other criteria based on fields defined in the CMD table

You select charges to be included in the report by specifying a supplemental WHERE clause for the main SQL statement that selects the record set from which the report statistics are calculated. See the field definitions for the CMD table for the list of fields you can use in the supplemental SQL statement. If you specify a criteria that the system would normally exclude (such as non-residents) the system automatically replaces its own WHERE clause for that criteria with yours.

The Demographic/Utilization/Charge Data Ad-Hoc Report Definition screen


Here are some common criteria you might specify in the Supplemental Where Clause: To print a utilization report for: Supplemental Where Clause Medi-Cal enrollees with MICRS charges CMSPOK<>”Y” Medi-Cal enrollees at CBOs with MICRS charges

CMSPOK<>”Y” AND BETWEEN(PROV_ID,19.28)

Non-County Residents with MICRS charges

RESIDENT<>”Y”

Children AGE < 19 Charity Care (i.e., not CMSP): FINCLASS==”C” Charity Care and Patient Pay combined: FINCLASS<>”I”

Ad-hoc Utilization Report Sample SQL Queries Notes: Enclose text literals in double quotes. You can specify dates in the standard Foxpro format {^yyyy-mm-dd} or using the character-to-date conversion function CTOD(“mm/dd/yyyy”)

STATE REPORTS

Preparing to run state reports 1. Before running the first state calculation for a period, Make sure all providers have submitted

data for the period by selecting VIEW IMPORT STATUS SUMMARY from the IMPORT OPERATIONS menu. For quarterly reports, all CBOs and the ACMC must have data for all months in the reporting period. For ACMC, only the OT1-OT4 files must be present for all months in the period. Data from Alcohol & Drug and private hospitals is not required for quarterly reports.

2. Make sure the prior calculation has been posted to history viewing table status using

DISPLAY STATE TABLE STATUS and DISPLAY HISTORY TABLE STATUS from the STATE MICRS REPORTING/DISPLAY CURRENT TABLE STATUS menu. If the two displays do not show the same dates, run the POST MICRS TABLES TO HISTORY process from the STATE MICRS REPORTING menu. This adds the records from the current state tables (TABLE_*) to the history tables (H_TBL_*).

3. Make sure all corrections reported on the MICRS DATA EXCEPTION reports received from

providers for the period being reported have been made. Zip codes: Enter the following command into the command window: SELECT * FROM cmd WHERE fy=<fy> AND resident='Y' AND zip<99995 AND (zip<94501 OR zip>94720) If there are any, they must be fixed. One method is to copy the query to a different file, for example: COPY TO work\badzips and edit the file manually to correct the zip codes. Once the work file has been corrected, replce the records in CMD as follows: DELETE FROM cmd WHERE fy=<fy> AND resident='Y' AND zip<99995 AND (zip<94501 OR zip>94720) SELECT cmd APPEND FROM work\badzips USE

Notes:

• In the sample code above <fy> is the 4-digit fiscal year • If the CITY or ADDRESS fields contain “HOMELESS”, set the zip code to 99995.

• If the CITY or ADDRESS fields contain “UNKNOWN or “UNK”, set the zip code to

99998.

Non-residents: Set the CMD order to CITY. Browse CMD and cross-check the CITY and RESIDENT fields. Make sure cities not in Alameda County have RESIDENT=”N” and cities in Alameda county have RESIDENT=”Y”. At the same time, correct misspellings in-county city names. Birth Date: Set the CMD order to DOB. Browse the beginning and end of CMD and check the DOB field for empty or invalid values. Usually the AGE field is zero in any invalid records. Correct any invalid values, then correct the AGE, AGEGRP and AGEGRP2 fields with this commands: PUBLIC aCodeAge SELECT * FROM codeage INTO ARRAY aCodeAge UPDATE CMD SET ; AGE=(BEG_SVC_DT-DOB)/365.25, ; AGE_GRP_CD=INT((BEG_SVC_DT-DOB)/365.25), ; AGE_GRP = aCodeAge[ASCAN(aCodeAge, ; INT((BEG_SVC_DT-DOB)/365.25),1,ALEN(aCodeAge,1),1,8),2], ; AGE_GRP2 = aCodeAge[ASCAN(aCodeAge, ; INT((BEG_SVC_DT-DOB)/365.25),1,ALEN(aCodeAge,1),1,8),3] ; WHERE AGE=0 AND BETWEEN(dob,{^1907-01-01},{^1999-12-31}) Family Size: Type the following command in the command window: SELECT * FROM CMD WHERE FMLY_SIZE > 15 Correct any invalid family sizes by using your judgment. BROWSE the CMD table to locate other records for the same patient. If you can find any, set the invalid FMLY_SIZE to the value found in other records. If you can’t find any, set FMLY_SIZE to 1.



Mental Health: Check mental health data to make sure only JOHN GEORGE INPATIENT has TOS=1 or 3. Other providers should be TOS=2 and OUTPAT_TOS=1. Make sure no records exist for any provider with "CRIMINAL" or “GUIDANCE CLINIC" in the name. These are not MICRS-eligible. If you find any, delete them.


Cost to Charge Ratios (effective FY 2001-2002): Open and browse the PROV_FY table. This table contains a record for each provider for each fiscal year, plus a record for each ACMC ambulatory clinic for each fiscal year. Make sure all records exist and that, at a minimum, the following fields contain data: In these records: These fields must contain data:

prov_id, cont_fy, RCC1, RCC2,RCC3 The ACMC record with the blank prov_loc: prov_id, cont_fy, act_pats, act_pvisit, act_allow, fqhc

The ACMC Ambulatory Clinic records (prov_id=1 and non-blank prov_loc):

prov_id, cont_fy, and either the annual and act_allow fields or the RCC2_state field

All CBO records:

Note: Other MICRS functions require that additional fields be populated, so you should always fill in all the fields you can. In particular, the cont_num, cont_pats, annual, monthly, and act_pats fields are required for other reports and procedures in the system, so these fields should always be filled in for non-Clinic (i.e. blank prov_loc) records. Records are not required for other providers such as private hospitals or BHCS providers. The state calculation routine will use an RCC of 1.0 for any missing records. To calculate the value for the RCC2_STATE field in PROV_FY for ACMC freestanding clinics and CBOs,

1. In OTHER REPORTS / PROVIDER REPORTS, run the FYTD Demographic/Utilization report (uncheck all other reports) with the following options: Providers: Select all ACMC freestanding clinics and all CBOs Period: last month of the fiscal year (June) Calc checkbox: checked Presentation: No Output Utilization Report options: Financial Class: Indigent, Report: Charges, Update FY Stats: checked, All other options: unchecked

2. After the reports are complete, for ACMC freestanding clinics, browse the PROV_FY table and set the value for RCC2_PC and RCC2_STATE for each freestanding clinic by positioning record pointer and entering: REPLACE rcc2_pc WITH act_pvisit*fqhc_pc/act_allow REPLACE rcc2_state WITH act_pvisit*fqhc_pc/act_allow

3. To update the fields for CBOs in one step, in the command window, enter: UPDATE prov_fy SET rcc2_state = act_allow/annual WHERE BETWEEN(prov_id,32,48) AND cont_fy=<fy> where <FY> is the 4-digit fiscal year, e.g. 0405.

Remove non-qualifying records from CMD Run the following procedure to remove non-qualifying records from CMD. The procedure archives charges for non-residents, Medi-Cal-enrollees, and over 200% FPL patients from CMD and stores them in CMD_DELE.DBF. If you are doing a quarterly report, type in the command window: DO PURGE_CMD IN SRC\MICRCALC WITH <FY> , <Qtr> If you are doing an annual report, type in the command window: DO PURGE_CMD IN SRC\MICRCALC WITH <FY> , 0 <FY> is the 4-digit fiscal year and <QTR> is the 1 digit quarter number. To purge non-qualifying records for the entire fiscal year, specify a quarter number of zero.



Running the calculation for a period Choose RUN TRANSFER/CALC PROCEDURES from the STATE MICRS REPORTING menu. The following screen appears:

State Reports - Title Form screen Modify the Title Form to indicate the period for which the calculation will be run.

a) Quarters are numbers according to the fiscal year: Quarter 1 is 7/1 – 9/30 Quarter 3 is 1/1 – 3/31 Quarter 2 is 10/1 – 12/31 Quarter 4 is 4/1 – 6/30

b) Set the Estimated/Actual and Entire FY fields as follows:

Type of Run ESTIMATED/ACTUAL field ENTIRE FY checkbox

Quarterly run ACTUAL Unchecked Preliminary Annual ESTIMATED Checked Final Annual ACTUAL Checked

Click FLAG ALL TABLES, then click SAVE REPORT DATA, then click the RETURN TO PRIOR SCREEN icon in the upper left corner. The following screen appears:




State Reports – Verify Calculation screen

Options: Clean CMD - check this box if this is the first time you are calculating this period or if you changed any CMD data. If this is not the first run, you can uncheck the box to save time. Exclude ambulatory surgery charges over $20,000 - normally, you check this box. If the ACMC certifies that all Ambulatory Surgery charges over $20,000 are valid, or if you previously removed invalid Ambulatory Surgery charges, you can uncheck the box. Limit ACMC cost to charges submitted – This option allows you to control the application of the cost-to-charge ratios supplied by the ACMC. The objective is to report to the state a total dollar amount as close as possible to the county’s indigent contract payments. Normally you check this box. If the Total Expenditures figure on the Table Correspondence Check report is too low, you can uncheck this box, which will cause calculated expenditures to be higher . Click CONTINUE. Make sure this is what you want to do – the calculation starts after you click CONTINUE!




Another message that could appear is:

This message indicates that the PROV_FY table is not correctly populated. See the prior section titled Cost to Charge Ratios for information about populating the PROV_FY table. If you want to correct the PROV_FY information, answer NO to this question. If you want to proceed without the information, answer YES. It is recommended that you correct the PROV_FY table if you can, so that the state report will be as correct as possible. Checking the calculations 1. Print the following reports and from the STATE MICRS REPORTING menu.

Table Correspondence Check Period Comparison reports Print/Review Reports / Print All Tables For the Period Comparison report, if processing a quarter, compare to the prior two quarters plus the same quarter last year. If processing a preliminary annual, compare to the prior two final annuals. If processing a final annual, compare to the same year preliminary annual and the prior two final annuals.

2. Print Utilization reports from the PROVIDER REPORTS screen (Other Reports menu) for

the following providers: ACMC Mental Health Combined CBO All Providers


3. Table Correspondence Check report: Make sure all tests on the report say PASS. 4. Period Comparison report: Look for any large quarter-to-quarter or year-to-year percentage

changes. 5. Individual table reports:

Table 1A: Fix invalid zip codes in CMD by BROWSing with the order set to ZIP.

Only zip codes in the range 94501 - 94720, 99995, 99998, and 99999 are valid.

Table 2: Check for income $4,000+. Often this is mental health reporting $20,000. Change to zero. The State will question a significant # of patients over $4,000.

Table 4: Make sure <21 category contains small numbers. Table 10: Other/unknown should be a low percentage of total expenditures Table 12: Check ambulatory surgery and other/unknown, ensuring not too high.

Check distribution for primary care and specialty care



For more information about checking state reports See the annotated reports in the State Report Edit Check Procedures section. Preparing the state diskette 1. Review the reports with Vana. 2. Re-run the reports as many times as necessary to get numbers Vana is comfortable with. 3. Once the reports are satisfactory, create the state file. Choose Create State Mandated

Diskette from the STATE MICRS REPORTING menu. 4. The procedure creates a file called DISK.TXT in K:\FOXMICRS. Rename the file to

ALMDxxxx.TXT where “xxxx” is: For quarterly: yyQq fiscal year ending year, the letter Q, the quarter number For Prelim Annual: yyPA fiscal year ending year followed by the letters PA For Final Annual: yyAA fiscal year ending year followed by the letters AA

5. Prepare the cover letter. Keep the letter short. Explain discrepancies the state is likely to

question by referencing lack of data or new data not reported before. 6. Email the letter and diskette to the state contact. Post-report processing 1. Once the report has been approved by the state, run the Post MICRS Tables To History

process from the STATE MICRS REPORTING menu. This adds the records from the TABLE_* tables to H_TBL_*.

2. Run ZIPSTATE.BAT at a DOS prompt from the K:\FOXMICRS directory. This saves the

state report tables and state diskette file to K:\FOXMICRS\STATE


SUPPORTING APPLICATIONS

RELATED APPLICATIONS

ELIGIBILITY.EXE – MEDI-CAL ELIGIBILITY CHECK SYSTEM

What it is The Medi-Cal Eligibility Check application cross-checks patients submitted to the MICRS system to see if they are enrolled in Medi-Cal. Because patients enrolled in Medi-Cal are not eligible for CMSP-funded services, patients found to be enrolled in Medi-Cal are removed from CMSP reports. How it works The application, ELIGIBILITY.EXE, consists of one program file, ELIGIBILITY.PRG , and supporting library files IEBROWSER.PRG, MEDILIB.PRG, MICRLIB.PRG, and HCSALIB.PRG . The MCAL_EV table drives the application. One MCAL_EV record is created for each patient & service month when data is loaded to the CMD table via form LD_CMD. ELIGIBILITY.EXE controls Internet Explorer as an automation server to query the Medi-Cal web site once per month for each record on file. Medi-Cal responses are stored in MCAL_EV and summary status us posted back to CMD.CMSPOK. Records for non-enrollees are dropped one year after the service month, as Medi-Cal will not reimburse for charges incurred after one year. Records for Medi-Cal enrollees are kept for historical purposes. Processing Details The program runs on the MICRS computer via the Job Scheduler. It runs every evening. It runs until all new records and records aged more than 30 days have been processed. It pauses during the night to allow files to be backed up and because the Medi-Cal system is unavailable from midnight to 2am. After processing all records, it performs two post-processing tasks: It computes the total CMSP charges for every patient found to be enrolled in Medi-Cal, and it sets the CMSPOK flag in CMD to “N” for each Medi-Cal-enrolled patient to indicate the charge is not CMSP-eligible. It creates a log file named MCEV_<dayname>.LOG in the LOGS subdirectory. The Medi-Call Enrollment Status Report The Medi-Cal Enrollment Status Report may be run from either the FEEDBACK form Menu OTHER REPORTS/PROVIDER REPORTS, or the Medi-Cal report configuration screen (menu OTHER REPORTS/MEDI-CAL STATUS REPORT). The report is part of the standard report package sent to providers each month.



Screenshots

MCAL_EV Status Display

Medi-Cal Inquiry Response Display




Checking non-MICRS data for Medi-Cal Enrollment By loading data directly into the MCAL_EV table, data from sources other than MICRS can be checked for Medi-Cal enrollment. To check non-MICRS data, utilize provider 2 – TEST PROVIDER, and append data directly to MCAL_EV. The fields required for successful Medi-Cal enrollment checking are: SSN DOB Service Month In addition, the LOCKED and CMSPOK fields need to be populated with “N” and “Y” respectively in order for the ELIGIBILITY program to work correctly.


ZIPLOOKUP.EXE – ZIP CODE VERIFICATION SYSTEM What it is The Zip Code Verification application checks addresses submitted to the MICRS system against the USPS Zip Code Lookup web site. It captures and stores the Postal Standard address, city and zip code, or flags the address as invalid if the USPS web site so indicates. It also populates the RESIDENT field in the ADDRESS table. How it works The application, ZIPLOOKUP.EXE, consists of one program file, ZIPLOOKUP.PRG , and supporting library files HIEBROWSER.PRG and HCSALIB.PRG . The ADDRESS table drives the application. One unique ADDRESS record is created for each patient when data is loaded to the CMD table via form LD_CMD’s RUN button. The address record is linked to each charge and to the client record when the address record is created. ZIPLOOKUP.EXE controls Internet Explorer as an automation server to the same way the Medi-Cal verification system does, except that address are checked only once whereas Medi-Cal records are checked each month for one year. Processing Details The program runs on the MICRS analyst PC via the Job Scheduler. It runs every evening. For each address not previously verified, if the USPS web site indicates the address is valid, the application captures the street, city, and 9-digit zip code and stores this data in the ADDRESS table record. The result of the lookup is stored in the UP_STATUS field in the ADDRESS table. The values for UP_STATUS are: (G)ood – The address is valid (B)ad – The address is not valid (S)kipped – The address is not verifiable or was previously determined to be out-of-county. (U)ndetermined – An unknown error occurred during verification. Check the log files ZIPLOOKUP_<dayname>.LOG and ZIPLOOKUP.LOG in the LOGS directory to see the processing status of the previous night’s run.

PHDATA.EXE – PUBLIC HEALTH DATA EXTRACTION

What it is How it works Processing Details Check the log files PHDATA_<date>.LOG in the LOGS directory to see the processing status of the previous run.



ONE-E-APP DATABASE SNAPSHOT DOWNLOAD

What it is One-E-App is the enrollment system of record for CMSP starting in August 2005. Demographic data that once came to MICRS in provider data submissions is now obtained from a snapshot copy of the One-E-App SQL Server database. The Snapshot Download retrieves a weekly snapshot of the One-E-App database to be used offline by MICRS. How it works The FTP client WS-FTP is used in “synchronize” mode to mirror Alameda County’s download are on the One-E-App FTP Server. The synchronize runs daily from the MICRS analyst PC via the Windows job scheduler. The GPG file (encrypted public domain PGP encryption system) is stored in the K:\OEA\DATABASE\SNAPSHOT directory. Currently the database is restored to SQL Server manually. Note: Even though the database snapshot is created weekly, the synchronize is run daily because the snapshot may not be created on the same day each week, and is only guaranteed to be present in the FTP area for 24 hours. Processing Details There is no logging feature in the synchronize function in WS-FTP. Check the directory K:\OEA\DATABASE\SNAPSHOT daily for the existence of new GPG files



SYSTEM MAINTENANCE

PERIODIC MAINTENANCE - MICRS Certain tables require periodic maintenance. Federal Poverty Level

Prior to processing April data, add a new record to FPLDEF2 containing the correct 100% FPL amounts for family sizes 1-10 plus the incremental amount for each family member above 10, for the new federal FY (4/1-3/30). Obtain the schedule from Vana or Dee.

Provider Contracts

About June 1, obtain the new contracted patient counts and dollars from Vana or Dee and update PROV_FL and PROV_FY. This must be done prior to printing new master contracts, which access the numbers via mail merge.

Data Compliance Percentage

About July 1, add one new record set to the DIC_PCT table for each type of provider. Normally the percents don’t change, but a new record set is needed anyway. The numbers have to be in place prior to importing any data for the new FY, because R_INT1.FRX prints them and uses them in calculations.

Import File Directories

About August 1, set up a new fiscal year directory structure under K:\IMPORT to store provider data for the new FY.

Statistics In September or October, after the 2nd ACMC reconciliation run is complete and verified, Re-calculate demographic utilization for all providers and update the STAT HISTORY worksheet in STATS.XLS. Update other sheets in the workbook also, as appropriate.

DEMOUTIL table Maintenances

At least once a year, remove old records from DEMOUTIL. Old records are identified by the value “N” in the MOSTRECENT field.

Resident City Lists

At least once a year, pull misspelled cities from CMD (query RESIDENT=Y and CITY not in CITYNAME) and add to the CITYCORR table.

Prior year CMD Data

Once the final annual state report for a fiscal year has been approved, move CMD records for the FY into SQL Server and remove them from CMD. This is usually 2 years after the FY ending date. Pack CMD when done. Warning: Packing CMD can take several hours. NOTE: BACK UP CMD BEFORE ARCHIVING DATA!

Prior years’ import Data

Every other year, archive the oldest 2 years’ import data to CDR and remove from network disk.

Summary of Periodic Maintenance Functions



SYSTEM MAINTENANCE

MISCELLANEOUS SYSTEM MAINTENANCE

TAPE BACKUP The network administrator normally performs this function, but you are the backup to the system administrator. The tape backup runs from HCSA-S1. There are two agents that run on HCSA-S2: The Windows Server agent and the SQL Server agent. They don’t have user interfaces, you just have to know they are there. Insert the weekly tape on Friday, and the daily tapes on Monday-Thursday. If a new tape is required, initialize it with an expiration date 5 years in the future. ELIGIBILITY & ZIP CODE LOOKUP These programs run on the MICRS computers each night. They can take anywhere from 5 minutes to 24 hours depending on the amount of data to process. They maintain their own log files, and no action is required on your part. If you need to disable one or both of them for some reason, they runs from the Job Scheduler (Accessories/System Tools). ELIGIBILITY runs on the MICRS computer and ZIPLOOKUP runs on the MICRS Analyst computer. MICRS STATISTICS Most statistics are kept in the file K:\FOXMICRS\DOC\TRACKING\STATS.XLS. The scheme is that you enter data into the first worksheet (‘StatHistory’) and the data is referenced from all the other worksheets. Here are the worksheets you might need: Stat History Statistics calculated from MICRS Stat Hist Graphs Graphs of Selected CBOs and the ACMC Contract History Historical comparison of patients actually seen to

contracted patients for all providers ACMC Charge Analysis % change in patients and charges from 97-98 forward CBO Charge Analysis CBO charges by type of charge over time Private Hosp Files Log file of data received from Private hospitals You can ignore all the other worksheets in the file. They are out-of-date or obsolete. MAPS On the desktop of the MICRS computer, there is a folder called MAP INFO. Within that folder, there is another folder called PROVIDER NETWORK MAPS. This contains shortcuts to the most common maps you might need to print. For other maps, do the following: In the plastic tray on top of the bookcase are samples of maps. Each map either has the filename listed at the bottom of the map or on a post-it note attached to the map. In the MAP INFO folder, run the “Files Named @.WOR” file search. Locate the map you need by filename and double-click it to open it.


API LIBRARY REFERENCE


API LIBLIBRARY REFERENCE NSDPGP3.DLL v1.3 COM Wrapper for PGP 8

Freeware. Freely distributable. Copyright (c) 2003, Gerard R Thomas. email:<[email protected]><[email protected]> http://community.wow.net/grt/nsdpgp.html

This program is "freeware" and may be used and copied, without fee or obligation, for private or commercial use. See the file license.txt for license information. If you do use it for commercial purposes, you may wish to contribute to the further development. You can send an online gift certificate from http://www.amazon.com to Gerard R Thomas [email protected] Installation: Please uninstall any previous versions of NSDPGP3.DLL before installing this version. The nsdpgp3.zip file contains these files: file_id.diz (package information) license.txt (license) nsdpgp3.dll (COM Wrapper DLL for PGP version 8) nsdpgp3.dll.sig (PGP signature) readme.txt (program information)

1. Copy the nsdpgp3.dll file to the \System32 directory (Windows XP/2K/NT4) or the \System directory (Windows ME/98/95).

2. Register the file by typing into the Start | Run: "REGSVR32 NSDPGP3.DLL"

Uninstall: Unregister the file by typing into the Start | Run: "REGSVR32 /U NSDPGP3.DLL" Delete the nsdpgp3.dll file. Operation: NSDPGP3.DLL is a COM In-Process Automation Server that wraps various functions of PGP version 8. Its COM Object provides a simplified interface to clients such as ASP, the Windows Scripting Host, Visual Basic, MS Office VBA, Java, Delphi, Visual C++ etc. It was built using Visual C++ 7.0 (Visual C++.NET) and tested with PGP 8.0.2 (Freeware) on Windows 2000 Professional (SP4) using ASP (IIS5), VB6, VC6 and WSH.



Function Reference: The Object has thirty seven methods. It returns a standard COM HRESULT (either S_OK or E_FAIL) with error information provided via the COM interface ISupportErrorInfo. This error interface is automatically used by scripting clients such as ASP and WSH and they transparently return the error information to the user. The error information can also accessed with a try..catch statement (JScript/WSH). With Visual Basic, the built in error object Err has to be used (with an error handler). With Visual C++, the _com_error type can be used (with an exception handler). See the example code for more information on this. Most methods take a KeyID as input. Convenience methods are provided to give the KeyID of a key from a supplied UserID (the email address), the UserID from the KeyID and the KeyIDs of all the valid keys on the keyring. Many of the File methods allow selection of input or output filetypes (text or binary). The String methods output data in standard PGP ASCII Armor text format. Many of the String methods use the File methods internally (i.e. they are convenience functions). Any temporary files used are wiped before the methods return. (1) List all the valid keys on the keyring keylist = ListKeys ( pubkeyring, privkeyring ) (2) Obtain the KeyID of a key from its UserID keyid = GetKeyIDFromUserID ( pubkeyring, privkeyring, userid ) (3) Obtain the UserID of a key from its KeyID userid = GetUserIDFromKeyID ( pubkeyring, privkeyring, keyid ) (4) Generate a new key pair keyid = GenerateKey ( pubkeyring, privkeyring, keyalg, bits, name, passphrase ) (5) Revoke a key pair RevokeKey ( pubkeyring, privkeyring, keyid, passphrase ) (6) Delete a key DeleteKey ( pubkeyring, privkeyring, keyid ) (7) Enable a public key EnableKey ( pubkeyring, privkeyring, keyid ) (8) Disable a public key DisableKey ( pubkeyring, privkeyring, keyid ) (9) Import a public key from a file ImportKeyFromFile ( pubkeyring, privkeyring, infile ) (10) Export a public key to a file ExportKeyToFile ( pubkeyring, privkeyring, outfile, keyid ) (11) Import a public key from a KeyServer via its UserID

UserIDImportKeyFromKeyServer ( pubkeyring, privkeyring, userid, keyserver )

(12) Import a public key from a KeyServer ImportKeyFromKeyServer ( pubkeyring, privkeyring, keyid, keyserver )




(13) Export a public key to a KeyServer ExportKeyToKeyServer ( pubkeyring, privkeyring, keyid, keyserver ) (14) Import a public key from a string ImportKeyFromString ( pubkeyring, privkeyring, instring ) (15) Export a public key to a string outstring = ExportKeyToString ( pubkeyring, privkeyring, keyid ) (16) Analyze a file datastatus = AnalyzeFile ( infile ) (17) Encrypt a file using a conventional cipher ConventionalEncryptFile ( infile, outfile, infiletype, outfiletype, cipheralg,

passphrase ) (18) Encrypt a file using a public key EncryptFile ( pubkeyring, privkeyring, infile, outfile, infiletype, outfiletype,

rcptkeyid ) (19) Encrypt and sign a file using keys EncryptAndSignFile ( pubkeyring, privkeyring, infile, outfile, infiletype,

outfiletype, rcptkeyid, alg, signkeyid, passphrase ) (20) Decrypt a file DecryptFile ( pubkeyring, privkeyring, infile, outfile, passphrase ) (21) Decrypt and verify a file DecryptAndVerifyFile ( pubkeyring, privkeyring, infile, outfile, siginfofile,

passphrase ) (22) Clear sign a text file ClearSignFile ( pubkeyring, privkeyring, infile, outfile, alg, signkeyid, passphrase

) (23) Opaque sign a file OpaqueSignFile ( pubkeyring, privkeyring, infile, outfile, infiletype, outfiletype,

alg, signkeyid, passphrase ) (24) Sign a file with a detached signature file SignFile ( pubkeyring, privkeyring, infile, sigfile, sigfiletype, alg, signkeyid,

passphrase ) (25) Verify a signed file VerifySignedFile ( pubkeyring, privkeyring, infile, siginfofile ) (26) Verify a file with a detached signature file VerifyFile ( pubkeyring, privkeyring, infile, sigfile, siginfofile ) (27) Verify an encrypted file VerifyEncryptedFile ( pubkeyring, privkeyring, infile, siginfofile, passphrase ) (28) Wipe a file WipeFile ( infile ) (29) Analyze a string datastatus = AnalyzeString ( instring ) (30) Encrypt a string using a conventional cipher outstring = ConventionalEncryptString ( instring, cipheralg, passphrase ) (31) Encrypt a string using a public key outstring = EncryptString ( pubkeyring, privkeyring, instring, rcptkeyid ) (32) Encrypt and sign a string using keys outstring = EncryptAndSignString ( pubkeyring, privkeyring, instring, rcptkeyid,




alg, signkeyid, passphrase ) (33) Decrypt a string outstring = DecryptString ( pubkeyring, privkeyring, instring, passphrase ) (34) Clear sign a string outstring = ClearSignString ( pubkeyring, privkeyring, instring, alg, signkeyid,

passphrase ) (35) Opaque sign a string outstring = OpaqueSignString ( pubkeyring, privkeyring, instring, alg, signkeyid,

passphrase ) (36) Verify a string siginfostring = VerifyString ( pubkeyring, privkeyring, instring ) (37) Verify an encrypted string siginfostring = VerifyEncryptedString ( pubkeyring, privkeyring, instring,

passphrase ) parameters: (a) keylist is a string into which the KeyIDs (delimited by commas) of all the valid keys on the keyring are written. (b) pubkeyring is a string giving the filename (including full path) of the PGP public keyring. UNC paths may be used. (c) privkeyring is a string giving the filename (including full path) of the PGP private keyring. UNC paths may be used. (d) keyid is a string giving the KeyID (e.g. "0x9DBCDE7D") of the PGP key to be used. (e) userid is a string giving the UserID (typically the email address) (e.g. "[email protected]") of the PGP key. (f) keyalg is is an integer that indicates the desired PGP key pair type to be created. Valid values are 0 - 1 0 - RSA 1 - DH_DSS Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. DH_DSS rather than 1).


(g) bits is an integer giving the size of the key pair to be created. Valid range is 1024 to 4096 bits (h) name is a string giving the name and email address (e.g. "John Doe <[email protected]>") of the key pair to be created. (i) passphrase is a string giving the conventional passphrase or the PGP keyring passphrase. (j) infile is a string giving the filename (including full path) of the input file. UNC paths may be used. (k) outfile is a string giving the filename (including full path) of the output file. UNC paths may be used. Note that outfile and infile should NOT be the same. This will work for small files but fails with larger ones (with PGP deleting the file). (l) keyserver is an integer that indicates the keyserver to be used. Valid values are 0 - 3 0 - KEYSERVER_PGP_COM 1 - EUROPE_KEYS_PGP_COM 2 - SEARCH_KEYSERVER_NET 3 - PGPKEYS_MIT_EDU Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. KEYSERVER_PGP_COM rather than 0). (m) instring is a string with the input data to be processed. (n) outstring is a string into which the output data is written. (o) datastatus is a string into which the status of the input data will be written.



This will be one of the following data status strings: DATASTS_ENCRYPTED DATASTS_SIGNED DATASTS_DETACHED_SIGNATURE DATASTS_KEY DATASTS_UNKNOWN DATASTS_X509_CERTIFICATE (p) infiletype is an integer that indicates whether the input file is text or binary. Valid values are 0 -1 0 - TEXT_FILE 1 - BINARY_FILE Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. BINARY_FILE rather than 1). (q) outfiletype is an integer that indicates whether the output file is ASCII armored text or binary. Valid values are 0 -1 0 - TEXT_FILE 1 - BINARY_FILE Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. BINARY_FILE rather than 1). (r) cipheralg is an integer that indicates the desired PGP conventional cipher algorithm. Valid values are 0 - 5 0 - IDEA 1 - TripleDES 2 - CAST5 3 - AES128




4 - AES256 5 - Twofish256 Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. CAST5 rather than 2). (s) rcpkeyid is a string giving the KeyID (e.g. "0x9DBCDE7D") of the recipient's public key. Note that if the public key has an associated ADK, the ADK will be ignored. Multiple recipients can be specified (delimited by commas) (e.g. "0x9DBCDE7D,0xFF7155A2,0x05804E46"). (t) alg is an integer that indicates the desired PGP hash algorithm. Valid values are 0 - 2 0 - MD5 1 - SHA1 2 - RIPEMD160 Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. MD5 rather than 0). (u) signkeyid is a string giving the KeyID (e.g. "0x9DBCDE7D") of the signing key. (v) siginfofile is a string giving the filename (including full path) of the text file into which the signature status information should be written. UNC paths may be used. The status information will include one of the following signature status strings: SIGSTS_NOTSIGNED SIGSTS_VERIFIED SIGSTS_NOTVERIFIED SIGSTS_BADSIG SIGSTS_VERIFIED_UNTRUSTED


The first line of the signature information file will be the date/time of the operation. This is followed by the signature status, the signer, the signing date and time and the signing KeyID. The data status and signature status strings follow. Finally the date and time of the signing and the full 64 bit KeyID are written. Typical file contents: Nsdpgp3 2003/10/03 19:19:14 Good signature. Signed by Gerard R Thomas <[email protected]> Sun Sep 28 2003 10:43:11 AM. KeyID: 0xFF7155A2. DATASTS_ENCRYPTED SIGSTS_VERIFIED 2003/09/28 10:43:11 0x5B3C2165FF7155A2 (w) sigfile is a string giving the filename (including full path) of the detached signature (.SIG) file. UNC paths may be used. (x) sigfiletype is an integer that indicates whether the detached signature file is text or binary. Valid values are 0 -1 0 - TEXT_FILE 1 - BINARY_FILE Clients that can access the built in typelib of the DLL can use the enum variable name instead of the integer value (e.g. BINARY_FILE rather than 1).



Usage examples: (WSH, ASP, Visual Basic, Visual C++ and command line [via WSH]) (1) using the Windows Scripting Host and JScript //test.js var pubring = "c:\\rings\\pubring.pkr"; var privring = "c:\\rings\\secring.skr"; var passphrase = "my secret phrase"; var recipientid = "0xFF7155A2"; var signingid = "0x9DBCDE7D" var test = "Test of the PGP COM Object"; var inputfile = "d:\\data\\photo.jpg"; var outputfile = "d:\\upload\\photo.jpg.pgp"; var infofile ="c:\\temp\\siginfo.txt"; var encrypted; var decrypted; var siginfo; var status; shellobj = WScript.CreateObject("WScript.Shell"); pgpobj = WScript.CreateObject("Nsdpgp3Lib.PGP"); try{ shellobj.Popup("starting tests", 3); shellobj.Popup("some file tests", 3); pgpobj.EncryptFile(pubring,privring, "d:\\data\\report.doc", "d:\\upload\\scrambled.pgp", 1, 0, "0x9DBCDE7D,0x05804E46,0x6CFC73BA"); pgpobj.EncryptAndSignFile(pubring,privring, inputfile, outputfile, 1, 1, recipientid, 3, signingid, "my secret phrase"); status = pgpobj.AnalyzeFile(outputfile); shellobj.Popup(status, 3); pgpobj.DecryptAndVerifyFile(pubring,privring, outputfile, inputfile, infofile, passphrase); shellobj.Popup("some string tests", 3); encrypted = pgpobj.EncryptAndSignString(pubring,privring,test,"0xFF7155A2", 2,"0x9DBCDE7D", "secret"); shellobj.Popup(encrypted, 3); decrypted = pgpobj.DecryptString(pubring, privring, encrypted, "secret"); shellobj.Popup(decrypted, 3); siginfo = pgpobj.VerifyEncryptedString(pubring,privring,encrypted,"secret"); shellobj.Popup(siginfo, 3); shellobj.Popup("done", 3); } catch(err) { shellobj.Popup(err.description, 5); }


(2) using .ASP on IIS5 <html> <head> <title> test.asp </title> </head> <body> <% dim pubring dim privring dim infile dim outfile dim pass dim instr dim outstr dim signid dim recipient set pgpobj = server.createobject("Nsdpgp3Lib.PGP") instr = "Test of the PGP COM Object" pubring = "c:\\rings\\pubring.pkr" privring = "c:\\rings\\secring.skr" pass = "my secret phrase" recipient = "0xFF7155A2" signid = "0x9DBCDE7D" infile = "d:\\data\\january.xls" outfile = "d:\\upload\\jan.xls.pgp" if isobject(pgpobj) then response.write("running tests ") response.write("input string... ") response.write(instr & " ") response.write("clearsign test... ") response.write("<PRE>") outstr = pgpobj.ClearSignString( pubring, privring, instr, 2, signid, pass ) response.write(outstr) response.write("</PRE>") response.write("encrypting and signing file test... ") pgpobj.EncryptAndSignFile pubring, privring, infile, outfile, 1, 1, recipient, 2, signid, pass response.write("all done ") else response.write("Error creating object") end if set pgpobj = nothing %> </body> </html>



(3) using Visual Basic (a) choose Standard EXE project (b) choose Project | References and check the "PGP v8 COM Interface" checkbox. (c) place a commandbutton control on Form1 (d) enter the following code Private Sub Command1_Click() On Error GoTo errhandler Dim keyid As String Dim inputstring As String Dim outputstring As String Dim decrypted As String Dim password As String Dim pubring As String Dim privring As String Dim recipientid As String Dim signid As String Dim uncfile As String inputstring = "Test of the PGP COM wrapper" password = "my secret phrase" pubring = "c:\rings\pubring.pkr" privring = "c:\rings\secring.skr" recipientid = "0xFF7155A2" signid = "0x9DBCDE7D" uncfile = "\\server2\backup\jan.xls.pgp" Dim myref As Nsdpgp3Lib.PGP Set myref = CreateObject("NSDPGP3Lib.PGP") keyid = myref.GetKeyIDFromUserID(pubring, privring, "[email protected]") MsgBox keyid, 0, "PGP test" Call myref.EncryptAndSignFile(pubring, privring, "d:\data\photo.jpg", "d:\upload\photo.jpg.pgp", BINARY_FILE, BINARY_FILE, "0xFF7155A2", SHA1, "0x9DBCDE7D", password) Call myref.EncryptAndSignFile(pubring, privring, "d:\data\january.xls", uncfile, BINARY_FILE, TEXT_FILE, "0xFF7155A2", SHA1, "0x9DBCDE7D", password) Call myref.DecryptAndVerifyFile(pubring, privring, "c:\download\feb.doc.pgp", "d:\data\feb.doc", "c:\temp\infosig.txt", password) MsgBox inputstring, 0, "PGP test" outputstring = myref.EncryptString(pubring, privring, inputstring, recipientid) MsgBox outputstring, 0, "PGP test" decrypted = myref.DecryptString(pubring, privring, outputstring, password) MsgBox decrypted, 0, "PGP test" MsgBox "all done", 0, "PGP test" Set myref = Nothing Exit Sub errhandler: MsgBox Err.Description, 0, "PGP test" Resume Next End Sub


(4) using Visual C++ //test.cpp #import "C:\WINNT\System32\nsdpgp3.dll" no_namespace #include <iostream.h> void main() { _bstr_t password = "my secret phrase"; _bstr_t inputfile = "c:\\data\\report.doc"; _bstr_t outputfile = "d:\\upload\\report.doc.pgp"; _bstr_t recipient = "0xFF7155A2"; _bstr_t signid = "0x9DBCDE7D"; _bstr_t pubring = "c:\\rings\\pubring.pkr"; _bstr_t privring = "c:\\rings\\secring.skr"; CoInitialize(NULL); try { IPGPPtr myRef(__uuidof(PGP)); cout << "running test" << endl; myRef->EncryptAndSignFile( pubring, privring, inputfile, outputfile, BINARY_FILE, TEXT_FILE, recipient, SHA1, signid, password ); cout << "done" << endl; myRef = NULL; } catch(_com_error err) { cout << err.Description() << endl; } CoUninitialize(); } //end of file



(5) using the command line (via WSH) Here is a short guide to using the COM object from the command line via WSH. The WSH (the Windows Scripting Host) is included in Windows 98 and later OSes (ME/2K/XP etc). NT4 and 95 users can download the "Windows Script 5.1" package from MS. WSH includes both WSCRIPT.EXE and CSCRIPT.EXE executables (for GUI and Console mode running of scripts). Here we use the command prompt window so CSCRIPT.EXE and a script file (Jscript) are needed. As an example, we will encrypt a file to a public key. The EncryptFile method of the object has several parameters. Some parameters (e.g the keyring files) may be specified in the .JS or .VBS script itself or all may provided on the command line. For convenience, we will specify the keyring paths in the script file and pass the input file, output file and the recipient user ID via the command line. A delimiter character is needed and we arbitrarily choose the # character. We have a file report.doc (located in the c:\data folder) that we wish to encrypt to the UserID "[email protected]". The input file is c:\data\report.doc The output file is c:\upload\report.doc.pgp The UserID is [email protected] Here is the command line: > echo c:\data\report.doc#c:\upload\report.doc.pgp#[email protected] | cscript /B c:\bin\pgp.js The redirected echo sends the parameter list to the CSCRIPT executable which invokes the script file PGP.JS (located in the c:\bin folder). The /B switch simply suppresses the banner text It is the script file which invokes the COM Object. The script has to process its standard input (the parameter list) and call the COM Object method. This encrypts the file. Here is the script file PGP.JS. It is placed in the specified directory. Hopefully the included comments // make the script easy to understand. // pgp.js




// // encrypt a file // example command line usage: // >echo c:\data\report.doc#c:\upload\report.doc.pgp#[email protected] | cscript /B c:\bin\pgp.js // variables var line, work, loc1, loc2, regexp; var infile, outfile, userid, keyid; var pubring = "c:\\rings\\pubring.pkr"; var privring = "c:\\rings\\secring.skr"; // first we read in from standard input line = WScript.StdIn.ReadLine(); // we use the # character to delimit the parameters // example: // c:\data\report.doc#c:\upload\report.doc.pgp#[email protected] // // we use regular expression: /pattern/flags // so pattern = # and flags = i (ignore case) regexp = /#/i; //find locations of the # characters loc1 = line.search(regexp); work = line.slice(loc1+1); loc2 = work.search(regexp); // cut the string into pieces // the +"" ensures proper termination of the strings we pass to the COM object infile = line.slice(0,loc1)+""; userid = work.slice(loc2+1)+""; outfile = work.slice(0,loc2)+""; // we output result strings to standard output to check all is well // the +"\n" causes each to be output on a new line WScript.StdOut.Write(infile+"\n");


WScript.StdOut.Write(outfile+"\n"); WScript.StdOut.Write(userid+"\n"); //instantiate the COM object pgpobj = WScript.CreateObject("Nsdpgp3Lib.PGP"); //invoke the method to encrypt the file //the try...catch block allows error information from the DLL to be obtained try{ keyid = pgpobj.GetKeyIDFromUserID( pubring, privring, userid); WScript.StdOut.Write("encrypting to\n"); WScript.StdOut.Write(keyid+"\n"); pgpobj.EncryptFile( pubring, privring, infile, outfile, 1, 1, keyid); WScript.StdOut.Write("done\n"); } catch(err) { WScript.StdOut.Write(err.description+"\n"); } // end of file Note: PGP version 8.0 or above must be installed on the system for this interface to work. It will not work with other versions of PGP. It is not a standalone encryptor but rather a COM wrapper to PGP. The actual cryptographic operations are performed by PGP itself. Note: The PGP signature may be used to verify the integrity of the executable. The executable is signed with my PGP DSS key [4096/1024 bit DH/DSS <[email protected]> <[email protected]> Key ID: 0xFF7155A2 Key fingerprint: 61DF 0468 0570 4615 8FF5 7530 5B3C 2165 FF71 55A2]. 2003 10 08 Gerard R Thomas Port of Spain Trinidad and Tobago



AZIP.DLL

AZIP.DLL – PKZIP API AZIP - procedure to zip files for Visual FoxPro using the AddZip AZIP32.DLL from shareware

Abri Technologies http://www.abri.com/foxpro.html REQUIREMENTS: AZIP32.DLL in your Windows\system directory or current directory USAGE: AZIP(lInitialize, sArchive, sInclFiles[, ZipParams]) EXAMPLE: AZIP(.T., "ZIPFILE", "*.DBF *.TXT Customer.doc -FoxUser.*") NOTE: Do not use '|' (vertical stroke) as file name separators - use only spaces. PARAMETERS: lInitialize: .T. first time & Done only once before or when starting file zip - .F.

afterward. Calling azip() with no params also initializes sArchive: Archive FileName with extension - Example "C:\THISFILE.ZIP" sInclFiles: String repr. file(s) to include, but excludes files with '-' in front.

Example1 "D:\CUSTDATA.DBF". Example2 "C:\CUSTOMER.DBF D:\*.TXT D:\DATABASES\*.*" (only single spaces in between)

ZIPparams: Some compression parameters [Optional] e(x) x = 'X' maximum compression x = '0' no compression (digital zero not letter O) x = 'S' minimal compression x = 'N' normal compression (default) P include directory entries & Span disks Spassword must be last part

RETURN VALUES: The number of files archived or -1 if archive name not specified.




AZIP.DLL

AUNZIP procedure to unzip files for Visual FoxPro using the AddZip AUNZIP.DLL's from shareware

Abri Technologies http://www.abri.com/foxpro.html REQUIREMENTS: AUNZIP32.DLL in your Windows\system directory or current directory USAGE: AUNZIP(lInitialize, sArchive sDir[, sExtractFiles[, UnZIPparams]]) PARAMETERS: lInitialize: .T. first time & Done only once beforeor when starting file zip - .F.

afterward. Calling azip() with no params also initializes sArchive: Archive FileName with extension - Example "C:\THISFILE.ZIP" sDir: destination directory string Example1 "D:\TEMP" sExtractFiles: (optional) string repr. file(s) or types to extract

Default is "*.*" Example1 "C:\CUSTOMER.DBF" Example2 "C:\CUSTOMER.DBF D:\*.TXT D:\DATABASES\*.*" - only single spaces in between

UnZIPparams: Some compression parameters [Optional] F freshen files - over older date/time or not existing D include directory information Overwrite: (This does not seem to work except OverwriteNone -

as of Aug. 1998 version). OA: overwrite all (default) O0: do not overwrite (letter O, digit zero) OU: ask user Spassword (Must be last part - works only with registered

version) RETURN VALUES: The number of files archived or -1 if archive name not specified.



DEVELOPMENT ENVIRONMENT

THE DEVELOPMENT ENVIRONMENT The MICRS Environment MICRS is accessed from the K: drive, which is mapped to the root of the MICRS share (currently \\hcsa-s2\data\hcsa\micrs). There are a few references in the code to the K: drive, although most have been removed through the years. The relevant folders are: FoxMicrs All MICRS production source and data DevMicrs One-time utilities, queries, special requests, and development tools, plus the

source control archive (see Source Control below). vfp Downloaded VFP tools, patches, examples, and libraries vfplib VFP library of common functions and forms used by MICRS and other VFP

applications developed in-house. import MICRS input data submitted by providers that has been or will be loaded into

the MICRS database. apps Support applications, usually written in VFP, that have been compiled into

stand-alone applications. MICRS directories – where everything lives

Tip: If MICRS can’t find its tables, forms or program code, click MICRS in the Manage Environments area of the Task Manager window. This will re-establish the MICRS directories and environment variables. Useful MICRS Utilities Some MICRS support utilities are included in the menu system and some are not. The following useful utilities, as well as many others, can be found in the UTIL sub-folder of FoxMicrs: calc_fy.PRG Calculates utilization for all providers for an entire fiscal year IndexAddress.PRG Indexes the ADDRESS table IndexCMD.PRG Indexes the CMD table indexMcalev.PRG Indexes the MCAL_EV table MCEV_SPREAD.PRG Displays the number of MCAL_EV records verified per day DeleteBatch.prg Deletes all data for one import batch from all tables in the

system packcmd.PRG Packs the CMD table (takes a long time) TAGS.PRG Lists all the tags in the current workarea taskpanefix.PRG Removes all the verbage from the top of the task pane so it

takes less screen real-estate Useful MICRS utilities


Source Control There is no commercial source control system for MICRS. When you modify a file in MICRS, use ARCHIVE.BAT to archive the current version before beginning to work. ARCHIVE.BAT maintains a generational backup of the past 30 versions of each file. The archive resides in the DEVMICRS\ARCHIVE folder. ARCHIVE.BAT itself resides in the FOXMICRS folder. To archive a file:

1. Open a DOS command window and change to the directory containing the file to archive. 2. At the DOS prompt, enter

\FOXMICRS\ARCHIVE <filename> <filename> may contain wild cards. For example, to archive the FEEDBACK form, open a DOS window and make \FOXMICRS\FORMS the current directory. Then enter: \FOXMICRS\ARCHIVE feedback.sc? or ..\ARCHIVE feedback.sc? To rollback changes you have made to the most recent archived version, use RESTORE.BAT, which resides in the DEVMICRS folder. RESTORE.BAT will “pop the stack”, that is, move all archives up one level, and overwrite the working version of a file with the copy in \DEVMICRS\ARCHIVE\OLD01. To restore a file,

1. Open a DOS command window and change to the directory containing the file to restore. 2. At the DOS prompt, enter

\DEVMICRS\ARCHIVE\RESTORE <filename> As with ARCHIVE.BAT , you can use wildcards. For example to restore the FEEDBACK form, enter: \DEVMICRS\ARCHIVE\RESTORE feedback.sc?



Miscellaneous Notes, tips, and tricks

Attempt to print to Adobe PDF driver does not display a filename dialog box:

MICRS works with the Adobe PDF printer driver to print reports that are emailed to providers. MICRS creates and supplies the filename to the Adobe PDF driver by setting a registry variable. Adobe PDF, upon detecting the presence of the registry variable, reads it, acquires the filename, and then deletes the variable. It often occurs that MICRS stes the registry variable is set but printing does not occur, causing the variable to remain in the registry. This results in the next attempt to print from Adobe Acrobat for any file, even files unrelated to MICRS, to use the filename stored in the variable. The result is that no dialog box is displayed. So if you try to print a document to the Adobe PDF driver from a MICRS computer and don’t get a dialog asking for a filename, just print it again. The second attempt will give you the dialog box.




How to write functions that open or use tables

If you develop a function that will change currently open area, you should preserve the incoming table state within the function. Sometimes it is only a matter of saving and then restoring the current area number, and sometimes it is more complicated. Two functions exist to assist with the second case: SaveAllSelect() and RestAllSelect(). They reside in HcsaLib.prg.

There are two approaches, depending on whether any open tables have filters set that reference local variables. If not, then you can encapsulate your function neatly as follows:

This approach works if there are no filters or if the filters do not reference local variables in the calling program.

**************************************************************** FUNCTION NewFunction(paramaterllist…) LOCAL aOpenTables DO setproclib IN \foxmicrs\src\micrlib && Enable HCSALIB DIMENSION aOpenTables[1] && Prepare the state storage array SaveAllSelect(@aOpenTables) && Save existing table state . . Remaining new function code . RestAllSelect(@aOpenTables) && Restore existing table state * Restore table filters if any FOR i=1 TO ALEN(aOpenTables,1) IF (aOpenTables[i,1]) AND !EMPTY(aOpenTables[i,4]) SET FILTER TO &aOpenTables[i,4]. IN (aOpenTables[i,2]) ENDIF NEXT i Return ****************************************************************

It gets more complicated if there are filters that reference local variables in the calling program because the variables are not in scope when your function is executing, and attempting to set a filter containing an undefined variable generates an error and clears the filter if it was set to begin with.




In this situation you need to save the table state directly in the calling program before calling your function: Then, after returning from your function, restore the table state and re-establish the filters using the information is recorded in the table state storage array by the SaveAllSelect() function.

.

. Existing calling program code

. DIMENSION aOpenTables[1] && Prepare the state storage array SaveAllSelect(@aOpenTables) && Save existing table state ReturnValue = NewFunction(paramaterllist) RestAllSelect(@aOpenTables) && Restore existing table state * Restore table filters if any FOR i=1 TO ALEN(aOpenTables,1) IF (aOpenTables[i,1]) AND !EMPTY(aOpenTables[i,4]) SET FILTER TO &aOpenTables[i,4]. IN (aOpenTables[i,2]) ENDIF NEXT i . . . . remaining main program code . . . Return **************************************************************** FUNCTION NewFunction(paramaterllist…) . . New function code . Return ****************************************************************


Alameda County Health Care Services Agency · 2008-06-25 · To run MICRS, start Visual Foxpro. The...

Documents

Transcript of Alameda County Health Care Services Agency · 2008-06-25 · To run MICRS, start Visual Foxpro. The...