The system supports tracking the user’s reading location. When active, a user must select a reading location from a configured list before he/she is able to create a clinical report. The following sections provide details on enabling, configuring and selecting reading locations.
Enable Reading Locations
By default, reading locations are disabled. They can be enabled for the entire system, for specific user groups or for individual user accounts.
Configure the default reading location for all users and groups as follows:
Override the system default for a group account as follows:
, for the group account you want
to edit.
Override a group account default for an individual user account as follows:
, for the user account you want
to edit.
Configure Reading Locations
Reading locations are selected from a list of configured records. Add and modify reading locations as follows:
.
To edit an existing reading location, click the Edit button,
. In
both cases, the reading location edit page is displayed.
. These are
the users who will have this reading location available as an option
when they log in.
,
and then the Remove button,
, to remove this
reading location from the associated user account.
An alternative method for populating the reading location table is to upload a comma-separated file. Each line in the file will create a single reading location record.
To
remove a reading location, click the Delete button,
,
from the reading location table.
Reading location table changes automatically proliferate to all servers in the dotcom.
Select Reading Location
A reading location is selected when logging into the system. When enabled, the reading location field appears on the login page after the user enters a user ID. The field is populated with the reading locations assigned to the user account.
When the user selects his or her reading location, the value appears at the top of the web pages, above the tab row.
You can change your reading location without logging out as follows:
The user always has the option to select No Location in which case no reading location is declared for the user session. However, when no reading location is declared, reporting is disabled.
When a report is created, the reading location is stored in the report object. A separate reading location is stored for each report component (i.e., the initial report and each addendum).
The reading location can be displayed on the report provided the report template includes the field. The reading location is not displayed on any built-in report template. Refer to the eRAD Layout XML Customization Manual for template details.