The active_stations table keeps a list of workstations that are in use. The station identifier is defined in the nextgen.ini file. When a user logs into the application, an entry is created in this table. When accessing the NextGen® application via a Citrix- or Terminal-server environment, the ICA- or RDP-session ID would be appended to the machine name, such that each user connection would be distinguished by a unique station_id, even when logged into the same server.
For example:
station_id os_user_name
CITRIX001:ICA-tcp#138 gdanzig
CITRIX001:ICA-tcp#013 lsibbles
CITRIX001:ICA-tcp#077 ddekker
This is a dynamic table and data will automatically delete when logging out of the NextGen® application. In a thin client environment, it is important to have synced session and application auto-logout times. It is also very important to logout of the application before exiting the thin session. If an improper logout occurs, you run the risk of an entry being stuck in the table.
Besides the station_id what are some other fields or data held in the active_stations table?
| STATION_ID | Station identifier. This is a unique identifier for each workstation and is the primary key for this table. |
| ENTERPRISE_ID | The enterprise identifier |
| PRACTICE_ID | Practice identifier. |
| PERSON_ID | Patient account identifier. |
| USER_ID | User identifier which can be joined to the user_mstr table |
| ENC_ID | Encounter identifier which can be joined to the patient_encounter table. |
| PROVIDER_ID | Provider identifier. |
| PRODUCT_ID | Product ID assigned to the running application |
| LOCATION_ID | Location identifier. |
| ENCOUNTER_DATE | Encounter date which can be joined to the patient_encounter table. |
| ITEM_ID | Is used to store a unique number for items that are actively in use, for example, the template_id of open templates. |
| ITEM_TYPE | Renaming the template_id column to use it to store different item_id’s and adding an item type column to determine the types. |
| OS_USER_NAME | The user login to the workstation’s operating system |
| HWND | This column will hold the specific product’s windows handle to allow users to switch to another NextGen® application by clicking a button. |
| CREATE_TIMESTAMP | When the row was created |
| MODIFY_TIMESTAMP | When the row was last updated. |
| ROW_TIMESTAMP | |
| FUNCTION_TYPE | Type of function to display for the application. Currently the only values are “template” or “module” |
| FUNCTION_NAME | Name of the function to display. |
What happens if user sessions are improperly logged out and entries are stuck in the active_stations table?
A user may login later that day or the following day and automatically see the same patient opened that they last had opened.
What can be done to avoid this?
1) There is a setting in the System Administrator application.
System Administrator > View > Universal Preferences > General Options > Delete All Active Stations records greater than 24 hours old
Note: This will only clear entries >24 hours. It will not clear everything every 24 hours.
2) Logout of the NextGen® application before exiting your thin client session.
What if I want to delete everything from active_stations instead of just items that are > 24 hours old or delete items in less time?
What if I want to delete specific items?
Caution: These options should be executed by NextGen Healthcare Client Support or your Database Administrator.
1) For specific items (best option during peak hours), run an SQL statement against the appropriate database.
Delete from active_stations where user_id = ‘enter user_id here’
2) Add a statement into your daily/nightly SQL job.
Delete from active_stations
3) Modify the active_stations stored procedure (highlighted changes) to delete with a lesser time of everything greater than eight hours.
SET
@datetodelete = dateadd (hh,-8,getdate ()) — select dateadd (hh,-8,getdate ()) = 2014-10-22 13:36:25.850
DELETE FROM ACTIVE_STATIONS
WHERE modify_timestamp <=@datetodelete