2015-09-06
396
Figure 5 shows a brief scenario. Initially, a user logs into the on-line production portal. After
selecting the target menu group, i.e., HIS (as described in 4.3.1), the portal server will parse
the HIS configuration file, as enclosed in the upper rectangular block of Figure 5, to generate
the linkage web URLs. In the group, there are two menus: OutPatientSystem and
InPatientSystem. PatientRegistration, Clinics, and Billing are the sub-menus of
OutPatientSystem. In Clinics and Billing, there are two access capabilities which are kept in
the check property: MIS and showTestENV (indicated in the pink boxes). If a user cannot
pass either of the two checks, these menus will not be visible on the web page, as depicted at
the right hand side of menu selections. On the other hand, when a user passes both checks
of MIS and shownTestENV, the result is shown as the left hand side of menu selections. The
menu selections are visible to the user. The menu, in green, means it is active. When it is
active, one click will trigger the redirection to the menu’s web URL.
A medical staff logs onto the PatientRegistration of the Outpatient Information System (OIS)
under the on-line production environment as indicated in the middle part of Figure 5. The
link property has outpatWeb as its value. Based on the value, the Portal Service retrieves the
OIS server URL, http://online.outpat.ntuh.gov.tw, concatenates it with the
PatientRegistration default page, /WebApplication/Clinics/Default.aspx, and constructs
the OIS PatientRegistration URL. Finally, the user access key, provided by Auth-WS, is
appended at the end of PatientRegistration web URL, indicated at the bottom of Figure 5.
A Dynamic Healthcare Portal Design and Enhancements 41
The last property is target control. The value “_self” means that the linked web page will be
displayed in the same browser window and our design default value is “_blank”, i.e.,
displaying in a new browser window. Therefore, the approach enables menu navigation
accurately and timely.
