Category: Allscripts

ProEHR Refill Status Codes

I have been working on a report to indicate which refill requests will be coming in the future and I’ve had to do some digging in the database. Found this little nugget of information while working in the HPSITE.REFILL table.

This is HPSITE.REFILL table description followed by HPSITE.REFILL.RFL_STATUS description.

HPSITE.REFILL: This table stores the data related to ordering a refill of a patient’s medication.

HPSITE.REFILL.RFL_STATUS: This column indicates the current status of the refill. It equates to the dict_type of ‘RFLSTS’ in the dictionaries_master.

RFLSTS is found in the HPSITE.DICTIONARIES_VIEW

SELECT * FROM HPSITE.DICTIONARIES_VIEW WHERE DICT_TYPE='RFLSTS'
DICT_TYPE	DICT_CODE	DICT_DESCRIPTION	DICT_EXTRAINFORMATION	DICT_ORDER	DICT_TABLE	DICT_ARCHIVED
RFLSTS	0	Rejected Called In	 	0	 	0
RFLSTS	1	Approved Called In	Called In	1	 	0
RFLSTS	2	Requested	 	2	 	0
RFLSTS	3	Rejected	 	3	 	0
RFLSTS	4	Approved	Filed	4	 	0
RFLSTS	5	Approved Faxed In	Faxed	5	NULL	0
RFLSTS	6	Approved Printed	Printed	6	NULL	0
RFLSTS	7	Approved Transmitted	Transmitted	7	NULL	0
RFLSTS	9	Approved Dispensed	Dispensed	9	NULL	0

This is using current 9.3.034 version of Allscripts ProEHR.

FastClaims for Tiger in AIX

So I’ve discovered that FastClaims in Allscripts Tiger AIX servers are stored in the following location.

When a receipts are batched, they are stored in /m2/MF01/CLAIM499

When clicking on “Batch” -> Fast Claims, it then copies /m2/MF01/CLAIM499 to /src/APPS/ECONNECT/ARCHIVE/TS/CLAIM499_1.3101165443_20120131165507385. You will notice this filename is comprised of CLAIM499_[companynumber].ddmmhhmmss.yyyymmddhhmmssnnnn in gzip format.

The original /m2/MF01/CLAIM499 is renamed to /m2/MF01/oldCLAIM499.

The header of the file AA00000000 indicates start of each claim for company and the end is represented by ZA00000000 in the same file. Replace zeros with account number padded.

Note: When modifying claim file, use R in vi to replace instead of i to insert. It will void the length of the columns and cause all sorts of problems.

Misys Vision Slow to Load Fast Services Screen

I’ve seen that it takes >1hr to load the FastServices window after clicking on the FastServices button.

Here’s what I did to make this take less than 10 seconds to load.  It appears as though it does some type of parsing/processing of old log and inbox files.

# cd /Medic/APPS/fastsvc
# ls -l
total 264
drwxr-xr-x 4 dev medgrp 512 Dec 5 15:33 inbox
drwxr-xr-x 2 dev medgrp 512 Dec 5 15:31 logs
drwxrwxrwx 2 dev medgrp 512 Dec 5 15:14 outbox
drwxrwxrwx 2 dev medgrp 512 Dec 5 15:23 tmp

I moved log to logs.org and inbox to inbox.org.

# mv logs logs.org
# mv inbox inbox.org

After that, I created .fast_images directory in the inbox folder and also created .data directory in inbox.

# ls -l inbox
total 16
drwxr-xr-x 2 dev medgrp 512 Dec 5 15:33 .data
drwxr-xr-x 2 dev medgrp 512 Dec 5 15:33 .fast_images

Then, I chown’d the proper permissions.

# chown dev.medgrp inbox
# chown dev.medgrp inbox/.data
# chown dev.medgrp inbox/.fast_images
# chown dev.medgrp logs