Difference between revisions of "Patient List"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 11: Line 11:
  
 
Patient lists can also be interfaced with a hospital registration system to bring over patients from a provider's rounding list.
 
Patient lists can also be interfaced with a hospital registration system to bring over patients from a provider's rounding list.
 +
 +
The patient list workspace is also used for downloading data returned from Panel Queries found in TWAdmin - Reports VTB.
  
 
==Managing Patient Lists==
 
==Managing Patient Lists==
 
Patient Lists can be created at the Enterprise, Organization, and User level.  This allows the administrator to limit visibility of patient lists to only those users that need access.  When a list is created Enterprise, it becomes available to all users when they try to 'Manage Lists'.  When managing their lists, a user can see only the lists that his/her Org or User allows.  They can then select the lists they will use and add them to their available Patient Lists.
 
Patient Lists can be created at the Enterprise, Organization, and User level.  This allows the administrator to limit visibility of patient lists to only those users that need access.  When a list is created Enterprise, it becomes available to all users when they try to 'Manage Lists'.  When managing their lists, a user can see only the lists that his/her Org or User allows.  They can then select the lists they will use and add them to their available Patient Lists.

Revision as of 21:41, 31 December 2009

Designed for rounding and charge capture, Patient Lists can be built in the EHR that capture specified hospital's census (ADT) lists and display a select group of patients that a provider can reference when conducting rounds.


Patient List Setup (TW v10)

Patient Lists are designed in TWAdmin under the Pt List VTB.

Patient lists are the product of filters. Based on a variety of different parameters, a Patient List can be developed that is customized to the needs of a doctor, practice, or medical team.

For example, if a practice with three providers (Bob, Don, & Ann) wanted to share a Patient List for Hospital ABC, they could set up the Patient List to filter based on the Location of Hospital ABC, the admitting provider, and Visit Status (Admitted, Transferred, etc.). Constructing the filters doesn't have to be complicated, but can become so when trying to design dynamic parameters.
Many times, there will be a patient list available for each provider, filtering to display the patients they admitted or are related to in some way. In the case that the provider code in the hospital system and the ambulatory EMR are different, dummy users will need to be created in the abulatory system that identifies with the hospital's provider code. The dummy user will never be a traditional user of the system, but rather just exist in the background. When filtering is being designed, instead of filtering by the actual provider, the dummy provider associated to their hospital ID will be the filtering criteria. This will enable the filter to look at the census list that was passed to the EMR and filter in the values related to that provider in the ambulatory system.

Patient lists can also be interfaced with a hospital registration system to bring over patients from a provider's rounding list.

The patient list workspace is also used for downloading data returned from Panel Queries found in TWAdmin - Reports VTB.

Managing Patient Lists

Patient Lists can be created at the Enterprise, Organization, and User level. This allows the administrator to limit visibility of patient lists to only those users that need access. When a list is created Enterprise, it becomes available to all users when they try to 'Manage Lists'. When managing their lists, a user can see only the lists that his/her Org or User allows. They can then select the lists they will use and add them to their available Patient Lists.