Tag: Healthcare

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.

Documenting Chaos

It has surely been chaotic around the office lately!  I’ve been assisting with migrations on the healthcare side for companies using Misys EMR/Misys Tiger to Allscripts ProEHR and ProPM.

Making the change involves a LOT of work.  From the obvious software setup to hardware setup down to ActiveDirectory permissions on the new systems, user training, helpdesk support, etc.

This leaves me little time to document the process of installing and configuring systems.

Between a notepad with scribbled technobabble and a few dozen text documents floating around my desktop, USB drive, and sticky notes, things get confusing — fast!  The worst part is that the entire team depends on me to “show them the light”.  What once took me 2-3 hours to setup a single system, I now have down to less than 30 minutes from start to finish.

Today, I’m working on documentation.  I’ve used so many different tools to help me document things on the fly — Wiki on a Stick, text editors, voice notes, etc.  Probably the best tool so far that I’ve found is “The Guide”.  This is an invaluable piece of software, which is free I might add.

Check out “The Guide” at the SourceForge project page:  http://theguide.sourceforge.net/

Off to documenting…