Table Of Contents
Implementing the Cisco Imatis Mobile Care Solution
Communications Manager Configuration
Creating XML Speed Dial Services
IMATIS Mobile Nurse Call Voice Callback Configuration
XML Services Redundancy on CUCM
Creating Extension Mobility Users
Configuring Speed Dial Button for IMATIS Medical Team Assembly
IMATIS Portal for System Administrator
IMATIS Mobile Nurse Call Integration
IMATIS Floor Plan and Bedroom Assignment
IMATIS Portal—System Administrator
IMATIS Portal for User Assignment—User
Receiving and Answering a Text Message
IMATIS Hospital Orderly Request
IMATIS Portal for System Administration
IMATIS Hospital Orderly Request Interface
IMATIS Portal for System Administration
IMATIS Medical Team Assembly Request
IMATIS Medical Team Assembly Workflow
IMATIS Scalability Considerations
Implementing the Cisco Imatis Mobile Care Solution
This chapter provides implementation details for the services enabled by Cisco Unified Communications, Cisco Unified Wireless Network, and IMATIS for the Mobile Care services. This section describes the steps required to configure features across the components to enable the services. Some design concepts and limitations are provided that you should keep in mind during implementation.
Network Topology
Figure 6-1 provides a frame of reference as you implement the solution. Figure 6-1 should be referred to as you implement the infrastructure steps outlined in Chapter 5, "Designing the Cisco Imatis Mobile Care Solution" and the application components in this chapter. There are many components in this solution and the placement of these components as it pertains to the places in the network helps to ensure better performance, availability, and security for the solution.
Figure 6-1 Network Topology
Configuration Task List
Configuration of the Cisco Imatis Mobile Care solution is a multi-step process that involves components across the network infrastructure, Cisco Unified Communications, Cisco Unified Wireless, the IMATIS servers, and a range of hospital equipment. The goal of this implementation checklist is to provide a list of key areas to cover to achieve a successful implementation. The checklist outlines the key steps to enable Cisco Imatis Mobile Care services, in addition to pointers to several foundational design guides that should be leveraged.
1.
Unified Communications
a.
–
–
–
–
b.
2.
3.
a.
b.
c.
d.
4.
a.
b.
c.
d.
e.
f.
g.
h.
Note
Note
Cisco Unified Communications
Communications Manager Configuration
Configuration of the Communications Manager is outlined in this section. The following provides a detailed checklist of key items to configure to enable Cisco Imatis Mobile Care services.
Summary of CUCM Configurations
1.
a.
b.
2.
3.
a.
b.
c.
d.
e.
4.
a.
b.
Note
Creating System Users
Creating users for predefined functions is required for system-level functions. This configuration only needs to be performed during the initial installation. These users provide IMATIS the user permission to perform the following two functions. Configuring individual users for Cisco Imatis Mobile Care services is outlined in Services Configuration.
•
•
To add a Communications Manager User:
Step 1
Step 2
Step 3
Figure 6-2 Adding a Communications Manager User
Step 4
Note
Step 5
Step 6
Figure 6-3 Device Association Configuration
Step 7
Step 8
Note
To add an Extension Mobility User and AXL interface system user:
Step 1
Step 2
Figure 6-4 Application User Configuration
Step 3
Note
Step 4
Figure 6-5 Adding User Groups
Step 5
Step 6
Figure 6-6 Application User Configuration Complete
SNMP Configuration
SNMP configurations must be defined so that the IMATIS server receives periodic updates when changes to phone states or configurations occur for the phones used for the Cisco Imatis Mobile Care service.
Step 1
Step 2
Step 3
Step 4
Step 5
Figure 6-7 SNMP Community String Configuration
a.
b.
c.
d.
e.
Step 6
Step 7
Step 8
Step 9
Figure 6-8 SNMP Notification Destination Configuration
a.
b.
c.
d.
e.
f.
Check that the IMATIS server filename IMATIS Ccm Integration Service.exe.config is configured accordingly. In this file the IP addresses, Community String, frequency for traps, and other fields are defined for the SNMP interface. The current recommendation is that SNMP traps are pulled from CUCM every 30 seconds. This is the lowest recommended setting. In addition to the periodic pulling of SNMP traps for the changes that have occurred, also configure the system to perform a full SNMP update once a day during a low traffic volume timeframe. The full update clears any conflicts that may occur between the IMATIS server and CUCM database.
Creating XML Services
XML services running on the Cisco IP phone enable the Cisco Imatis Mobile Care services. These services require an initial system level configuration before any of the users and phones can subscribe to these services. This section covers the initial configuration required on the CUCM system.
Note
IMATIS Login/Logout
Figure 6-9 IMATIS Login/Logout
This service on IMATIS provides the user with single sign-on. Through this login on the IMATIS server, a proxy login to extension mobility is created. More details are provided in the User ID Management section.
Under the Service URL: http://imatis-server/ImatisIpWebService/ImatisLogInOut/ImatisLogInOut.asp?device=#DEVICENAME#
Text Messaging
This service definition enables the text messaging service between users of the system.
Figure 6-10 Text Messaging
Under the Service URL: http://imatis-server/ImatisIpWebService/ImatisMelding/ImatisMelding.asp
IMATIS Medical Team Assembly
This service definition enables the IMATIS Medical Team Assembly service.
Figure 6-11 IMATIS Medical Team Assembly
Under the Service URL: http://imatis-server/ImatisIpWebService/ImatisTilkalling/ImatisTilkalling.asp
IMATIS Hospital Orderly Request
This service definition enables the IMATIS Hospital Orderly Request service.
Figure 6-12 IMATIS Hospital Orderly Request
Under the Service URL: http://imatis-server/ImatisIpWebService/ImatisPortoer/ImatisPortoer.asp
IMATIS Main Menu
This definition enables the user to access the IMATIS main menu from the XML Services menu.
Figure 6-13 IMATIS Main Menu
Under the Service URL: http://imatis-server/ImatisIpWebService/ImatisGetMessageId.asp
The other services, IMATIS Mobile Nurse Call and IMATIS Mobile Alerts, do not require an XML Service Menu definition. These services send alerts to users that are assigned in the roles definition in the IMATIS interfaces for User Management and the IMATIS Mobile Nurse Call IMATIS portal. More details on this configuration are provided in Services Configuration.
Creating XML Speed Dial Services
IMATIS enables a Medical Team Assembly service which can be more easily accessed by mapping the request into a speed dial key on the phone to send a URL request. In order to create this mapping to the speed dial key, the service must be defined. The following provides an example of defining a sample service. This service is later mapped to a speed dial button on a Cisco IP phone.
Figure 6-14 IP Phone Services Configuration
Under the Service URL enter: http://imatis-server/ImatisIpWebService/ImatisTilkalling/ImatisTilkallingSpeedRollePre.asp?Avd=Emergency%20Dept.&Rolle=Emergency%20Doctor
The syntax for requesting a "role" is based on http://imatis-server/ImatisIpWebService/ImatisTilkalling/ImatisTilkallingSpeedRollePre.asp?Avd=/&Rolle=/
Where the name for the department as defined in the IMATIS system administration portal is the name for the role. For example: = Emergency%20Dept. and = Emergency%20Doctor.
The syntax for request a "team" is based on http://imatis-server/ImatisIpWebService/ImatisTilkalling/ImatisTilkallingSpeedTeamPre.asp?Team=/
And is equal to the name of the team as defined in the IMATIS system administration portal. For example: the name for the cardiac arrest team is Cardiac%20Arrest%20Team.
Note
IMATIS Mobile Nurse Call Voice Callback Configuration
For the IMATIS Mobile Nurse Call service, a voice callback to the patient room may be needed. The voice callback may route the call to another IP-based phone. In that case, no extra configuration is required. If the callback is to interface to legacy-wired connections, such as FXS or PRI connections, the CUCM requires an H.323 voice gateway and possibly a H.323 gatekeeper if the dial plans become more complex. The example provided here shows a sample configuration using an ISR with Gatekeeper and Gateway functions combined.
For simplicity, the dial plan shown in this example shows extension 1061 and 1062 as the POTS line extensions for the FXS extensions to integrate with the IMATIS Mobile Nurse Call System. The extension of 105x are extensions on the CUCM Cisco IP phones.
Step 1
gatekeeperzone local mc-gk isemcca.local 10.1.1.22zone local mc-gk-cm isemcca.localzone prefix mc-gk-cm 105.zone prefix mc-gk 106.gw-type-prefix #1* default-technologyno shutdownStep 2
dial-peer voice 101 potsdestination-pattern 1061port 0/3/0!dial-peer voice 102 potsdestination-pattern 1062port 0/3/1Step 3
dial-peer voice 1050 voipdestination-pattern 105.session target ras
Note
Step 4
interface FastEthernet0?/0ip address 10.1.1.22 255.255.255.128duplex autospeed autoh323-gateway voip interfaceh323-gateway voip id mc-gk ipaddr 10.1.1.22 1719h323-gateway voip h323-id mc-voip-gwStep 5
Figure 6-15 Gatekeeper Configuration
Step 6
Figure 6-16 Trunk Configuration 1
Figure 6-17 Trunk Configuration 2
Step 7
Figure 6-18 Route Pattern Configuration
Step 8
Note
XML Services Redundancy on CUCM
The XML services or extension mobility defined for a phone typically is configured with a specific Communications Manager IP address. This presents a single point of failure for the service. As a best practice implement a highly-available XML service by using one of the following three methods:
•
•
•
A sample configuration for the first method is described below. Figure 6-19 shows a view of the redundancy configuration.
Figure 6-19 Redundancy Configuration
Step 1
Step 2
! probe to check for the availability of the serverip slb probe MY-PROBE tcpaddress 10.2.2.22port 8080! define a equally balanced access to CUCM serversip slb serverfarm MOBILECARE1-0nat serverprobe MY-PROBE!real 10.2.2.20weight 1inservice!real 10.2.2.21weight 1inservice! define the virtual serverip slb vserver MOBILECAREvirtual 10.2.2.22 tcp 8080serverfarm MOBILECARE1-0inserviceStep 3
Figure 6-20 Enterprise Parameters Configuration
User Management
This section describes the configuration of individual Cisco Imatis Mobile Care users. Use the following checklist to create the individual users.
Summary of key items:
•
•
IP Phone Configuration
The two Cisco IP phones that are tested and supported with Cisco Imatis Mobile Care are the 7921 and 7971G phones. The 7921 is only supported in SCCP mode and the 7971 is supported with SCCP and SIP mode.
To create a phone usable with Cisco Imatis Mobile Care Services:
Step 1
Step 2
Step 3
Step 4
Step 5
A sample of what you should enter is shown in Figure 6-21.
Figure 6-21 Sample IP Phone Configuration
Step 6
Step 7
Step 8
Adding Services to the Phone
Now that the phone has been defined, services can be added to the Cisco IP phone. Follow these instructions if extension mobility is not used for the phone. If extension mobility is used, then only IMATIS Login/Logout should be defined on the IP phone. If Extension Mobility is not used, then add all the relevant services including the IMATIS Login/Logout service.
Step 1
Step 2
Step 3
Figure 6-22 IP Phone Services Information
Step 4
Figure 6-23 Subscribed IP Phone Services
Repeat this step for all the services you want on the main phone. If Extension Mobility is used, the majority of the services should be reserved for the device profile associated with the EM User.
Creating Extension Mobility Users
The process of creating an extension mobility user is similar to that of creating a phone. You are creating a pointer to a device profile that is then applied to a physical phone after the extension mobility user has logged into a physical phone. To create an extension mobility user:
Step 1
Step 2
Figure 6-24 Device Profile Configuration
The Device Profile Name is used in the next step.
Step 3
Figure 6-25 End User Configuration
Step 4
Note
Step 5
Step 6
This user is now available for use within IMATIS for user login.
Configuring Speed Dial Button for IMATIS Medical Team Assembly
The service for IMATIS Medical Team Assembly may benefit from having speed dials provisioned on phones. This speed dial allows a function such as IMATIS Medical Team Assembly to summon a nurse or emergency doctor by the press of a speed dial button. To achieve this, the setting should be defined for both the main IP phone and the extension mobility user. To configure speed dial buttons for this service:
Step 1
Step 2
Figure 6-26 Phone Button Template Configuration
Step 3
Step 4
Step 5
Figure 6-27 Reorder Phone Button Configuration
Step 6
Step 7
Note
Services Configuration
This section describes the configuration required to enable the Cisco Imatis Mobile Care Services. Detailed IMATIS configurations can be obtained through IMATIS. This section covers general areas around IMATIS configurations to enable the IMATIS Mobile Care services with Cisco.
Summary of Cisco Imatis Mobile Care configurations:
•
IMATIS System Configuration
IMATIS recommends that each server be configured with redundancy where each server performs these main functions:
•
•
•
For instructions on installing IMATIS, check with Imatis. The IMATIS system utilizes Internet Information Services, ASP.NET, COM+ Access, and DTC Access services from Microsoft Windows Server.
After installing the servers in a redundant fashion, a few steps should be performed.
•
Figure 6-28 IMATIS Users
Once these users are present in the IMATIS database, these users are ready to utilize Cisco Imatis Mobile Care services.
•
Note
•
Inside the directory structure of the IMATIS system there are names that are translated as follows:
•
•
•
•
•
User ID Management
There are Extension Mobility users created in CUCM that provide the user a specific directory number and there is also an IMATIS user created through the active directory integration. These users should be identical to enable the proxy login from the IMATIS login. Figure 6-29 shows the flow of operations during a user login. With this implementation, the user only needs to log in through the IMATIS login to be automatically logged into to CUCM extension mobility.
Figure 6-29 User ID Management
Note
IMATIS Portal for System Administrator
On the IMATIS server, the system administrator is provided with a portal for administration of several key parameters that are required for each Cisco Imatis Mobile Care service. This application can be found on the IMATIS server through the path C:\Program Files\CARDIAC\IMATIS\Portal\IMATIS Portal.exe. Initial configurations for users, floor plans, team groups, and many other areas are configured by the system administrator through this tool.
IMATIS Worklist and INBOX
The services appear on the Cisco IP phones as messages and alerts that are organized into worklist and inbox. A worklist stores messages from IMATIS Mobile Nurse Call, Order Entry Alerts, Mobile Alerts, Hospital Orderly, and Medical Team Alerts. Text messages are stored in the INBOX retrieved by accessing the text messaging service.
Orderly worklists are unique as they serve a different role in a hospital and would not typically receive the other services.
The worklist is also ordered by priority, so Medical Team Assembly is always on top of the list, followed by Urgent nurse call and Normal nurse call. If the messages have the same priority, the messages are ordered by timestamp, with the oldest on top.
The alerts in the worklist are also clearly marked with certain tags to indicate the type of message. A normal nurse call has text such as "Bed 201 07:30" to indicate the location is the bedside or "WC 201 7:30" to indicate the location is the bathroom. An urgent call would be "URGENT 201 07:30". Messages from Medical Team Assembly also differ regarding the text using, for example, "**Alarm**, 201" or "*Cardiac Arrest*, 201".
IMATIS Mobile Nurse Call
This section describes several key steps required for integration with nurse call system vendors and a few configuration steps required to set up nurse call alerts to be received by nurses.
IMATIS Mobile Nurse Call Integration
The nurse call system manufactured by Best uses an RS-232 interface to report alerts generated by nurse call stations in a patient room. The RS-232 interface physically connects to an OPC server built by Imatis. Typically the physical location of the nurse call server may not be the same as the OPC server. The recommended implementation is to use RS-232 to IP adapters support the flow of messages from the nurse call system to the IMATIS server via the IP network. For best practices on implementing the RS-232 to IP adapter, refer to Quality of Service in Chapter 5, "Designing the Cisco Imatis Mobile Care Solution."
Using an adapter built by Imatis, these alerts are then passed from the OPC server to the IMATIS server via XML. The alert is then routed to the assigned nurse for the room that the alert originated from based on the business rules implemented by IMATIS. The alerts are sent to IMATIS in the form of OPC messages. OPC specifications can be found at http://www.opcfoundation.org/Default.aspx/01_about/01_whatis.asp?MID=AboutOPC.
For other nurse call system integrations, contact Imatis for more information.
IMATIS Floor Plan and Bedroom Assignment
The integration with nurse call systems requires a floor play layout with room assignments for patients. National Instruments is integrated with IMATIS to create the floor plan design for each hospital setting. This design should be performed in conjunction with building facilities. After this layout has been created, a floorplan will been available in the IMATIS portal. To start the IMATIS portal, use the following http query; enter the proper actual address for the IMATIS server:
http://imatis-server/imatispa
Click on the Bed Area and select a bed area to view. Figure 6-30 provides a sample floorplan layout for a hospital setting.
Figure 6-30 Sample Floorplan Layout
IMATIS Portal—System Administrator
After the floor plan and room layouts have been assigned, the floors and rooms need to be added. The administrator should select "User Manager". Under the directory tree of PA, floors and beds per floor can be defined.
Figure 6-31 Floors and Beds Per Floor
IMATIS Portal for User Assignment—User
Once the users have been added through the active directory integration, the defined users automatically appear within the IMATIS user portal. This portal is the one seen by the users of the system, not the portal used by the system administrator. Figure 6-32 shows the IMATIS portal used to manage the nurse call user assignment to patient rooms.
Figure 6-32 IMATIS Portal for Assignment to Patient Rooms
Click on "Call Plan". On the left is a list of the employees that can be assigned to the nurse call service. On the right side is a list bedrooms on a particular floor. This floorplan has been created in the previous step. To assign a nurse to a bedroom, click on a user from the list on the left that is shown to be online and click on an area on the right side. Click the set of double arrows pointing to the right and this assignment is created. Once the assignment is created, the location has a user shown after the list, as in example Bed 101 and 102. For areas that are not assigned a nurse, Bed 103 shows an example. Once a patient is assigned to Bed 103, a nurse should be assigned to that location.
Alarm Types
Once the nurses are assigned to the bed locations, the system is ready for use. When an alarm is generated from a patient room via the nurse call bedside stations, the alert is sent to the nurse station as the primary alert system. As a secondary alert, the IMATIS Mobile Nurse Call Server sends the alert to the IMATIS server, which forwards the alert to the Cisco IP phone based on the defined business rules. The following example is a walk through with sample screen shots of a few possible paths through a nurse call workflow.
1.
Figure 6-33 Nurse Call Sent to Phone
2.
3.
Figure 6-34 Option to Callback
4.
Figure 6-35 Alert Received by Nurse From Restroom Area
5.
Figure 6-36 Nurse View of Outstanding Worklist Items
6.
Figure 6-37 Icons on Portal
7.
When nurse call alerts go unattended, the business rules in IMATIS force escalations, with escalation rules following the building structure as defined in the IMATIS portal for system administration. Messages that get escalated from a nurse in a particular bed area would escalate to other nurses assigned to that bed area. Once all the nurses in that bed area are exhausted, the next escalation would find other nurses on the same floor. This method of escalation ensures that no nurse call alerts go unattended due to unforeseen circumstances.
8.
Urgent alerts may also be generated by the IMATIS Mobile Nurse Call system. A patient would not initiate this urgent request. Instead, this urgent request may be created by the nurse that walks into the patient room. There are several methods that a nurse can use to originate an urgent request:
•
•
•
When the urgent request is sent, the business rule creates an alert for all nurses attending that bed area. Other users can also be added to this team.
IMATIS Order Entry Alerts
Ancillary System Integration
The integration with ancillary systems for order entry alerts that lab results are available requires HL7 integration. This HL7 adapter is performed through the BizTalk server. The HL7 alert is received from hospital information systems. Based on the business rules applied to the parameters received through the HL7 interface, the message is then sent to the appropriate user. One critical business rule is based on the confidentiality of patient information. If this flag allows patient information to be sent, then the test results and patient name may be passed onto the alert. Otherwise, the alert only indicates that results are ready for review. Another parameter determines if the lab results are urgent or normal priority. There may be other fields that are deemed important as part of the integration that IMATIS may apply to the business rules.
User Assignment
The ordering system for the laboratory request contains an ordering physician's name. The physician's name is a required field to pass across the HL7 interface into IMATIS, along with the laboratory results message. The name is looked up in Active Directory to match a userID that is used as the unique identifier for IMATIS to determine to whom to send the laboratory results message.
Figure 6-38 shows a few samples of normal/urgent alerts and patient/no patient data.
Figure 6-38 Samples of Alerts and Patient Data
Text Messaging
The implementation of text messaging is automatically available once users are defined through the active directory integration. Users are then able to use text messages.
Main Menu Screen and INBOX
Figure 6-39 shows the main menu when entering the text message service. The service is similar to text messaging using SMS on cellular networks. This service is located within the hospital domain and delivered over the Cisco Unified Wireless Network network. An inbox keeps a list of all received messages until they are deleted.
Figure 6-39 Main Text Message Service Menu
Composing a Text Message
To compose a message to a user, there are several options for finding a user.
•
•
•
•
•
Figure 6-40 Email Options
Once an extension is entered, the user is ready to write the text message.
Figure 6-41 Ready for Text to be Entered
Receiving and Answering a Text Message
Figure 6-42 shows an example of a user receiving a text message. Once this message is read, Figure 6-42 shows a few predefined options for how the text message can be answered. A few predefined messages are created to easily answer the text message or a custom message can be typed. Another option allows a voice call back from the message originator.
Figure 6-42 Example of User Receiving a Text Message and Options for Answering Message
IMATIS Hospital Orderly Request
IMATIS Portal for System Administration
From the IMATIS portal on the IMATIS server used by the system administrator, the orderly groups can be defined. The administrator should select "User Manager". Under the directory tree of OppDrag, individual orderly teams can be defined. A special note on the role attributes is a field called Attended. When this field is set to "1", that means the role is 24x7 and can never be unattended. This setting prevents users from un-enrolling before a new user enrolls to take on that shift.
Figure 6-43 IMATIS Portal
IMATIS Hospital Orderly Request Interface
The Hospital Orderly Request tool as seen by a hospital staff user is retrieved via the http link http://imatis-server/ImatisOrderOrderly/AjaxOrderPage.aspx. This interface provides many options for hospital locations, request types, and the request message. Filling out this form lets hospital staff make a request to an orderly.
Figure 6-44 Hospital Orderly Request Tool
Once the order has been placed, the staff can view the current status of that request. Changes can be made to the request through this same interface. Figure 6-45 shows the order status interface after the order has been placed.
Figure 6-45 Reviewing Requests
This orderly request is they sent to the hospital dispatcher to assign a person to the task.
IMATIS Dispatcher
The dispatcher sees a different interface that allows the dispatcher to see all tasks (incoming, currently unassigned, assigned, and other states) and a list of enrolled orderly staff to which the work can be dispatched. This interface should only be used by the dispatcher. To start this interface, the IMATIS application name is ImatisTransporter.exe. Figure 6-46 is a sample of the interface seen by the dispatcher.
Figure 6-46 Sample IMATIS Dispatcher Interface
Hospital Orderly Workflow
The orderly staff users carry a Cisco 7921 IP phone to facilitate their daily workflow as they move abut the hospital. Through this interface, the staff can sign in and resign from a role, set the status for their role if they are busy or out to lunch, for example, and also receive requests and notify the dispatcher of their progress in handling the request. Figure 6-47, Figure 6-48, and Figure 6-49 show a few phone interfaces as seen by the staff for invoking these work flow states.
Figure 6-47 Main Menu and Enrolling
Figure 6-48 Setting Orderly State
Figure 6-49 Receiving Orderly Request and Acknowledge
IMATIS Medical Team Assembly
IMATIS Portal for System Administration
From the IMATIS portal on the IMATIS server used by the system administrator, the set of teams can be defined for each hospital setting. The administrator should select "User Manager". Under the directory tree of Tikalling -> Team, individual teams and roles can be defined. A special note on the role attributes is a field called Attended. When this field is set to "1", that means the role is 24x7 and can never be unattended. This setting prevents users from un-enrolling before a new user enrolls to take that shift. You can define individual roles, teams, and departments. After these teams and roles are defined, the system can be used to create summons and have users enroll.
Figure 6-50 IMATIS Portal for System Administration
The process for creating the hierarchical structure for these teams is to start with a department. Under the department, there may be various teams that are defined. Then under the teams, define specific roles for these teams. The attributes for these departments, teams, and roles should be defined.
IMATIS Medical Team Assembly Request
After these roles have defined, the system is ready to send summons to users of the system. There are several methods to create a summons:
•
•
•
IMATIS Mobile Nurse Call integration for critical summons that has a predefined business rule from IMATIS for that specific alarm generation.
The IMATIS summon tool is shown in Figure 6-51 to illustrate the interface a nurse station might see to request an emergency doctor in room 201. The user may choose to send a summons to a team, an individual role, or a group function. These are specified when the teams and roles are defined by the system administrator. To access this request page, use the following link http://imatis-server/imatisamk/resmon.asp
Figure 6-51 IMATIS Summon Tool
IMATIS Medical Team Assembly Workflow
As a user initially signs onto their shift, they would also enroll in a particular role. If the user is taking over a 24x7 role shift, a message is sent to the current person in the role.
Figure 6-52 Message to Current Person in Role
Using the phone, a request can also be made to summon a particular role or a team.
Figure 6-53 Message to Summon a Particular Role or Team
When a message is received on the phone, the user can ack the request or call 911 to request help.
Figure 6-54 Options for Responding to Message
IMATIS Mobile Alerts
The integration with fire and building alarm systems for alerts requires integration with the building systems. IMATIS uses ESPA 4.4.4 as one standard for this integration. The ESPA adapter is performed through the BizTalk server. The building alert is received from alarm systems. Based on the business rules applied to the parameters received through the ESPA interface, the message is then sent to the appropriate user. IMATIS uses the parameters received to apply business rules. One business rule may be based on whether the received alert is an emergency or just an equipment malfunction. If the alert is an emergency, the user may be presented with an option for immediately calling emergency 911.
User Assignment
Assignment of these alerts to a user is defined by the roles within the IMATIS system administrator portal. A role that is associated with a technical department or emergency department may be created. Users are assigned to these roles and receive building or fire alarm alerts when sent from the ESPA system.
Figure 6-55 Assignment of Alerts
Figure 6-56 shows a sample of three screens with alerts received for fire alarms or building technical problems.
Figure 6-56 Alerts for Fire, Building, and Technical Problems
IMATIS Scalability Considerations
As the deployment of Cisco Imatis Mobile Care services grows and the number of users expands, the scalability of the IMATIS Hospital Communication System is achieved by installing the application over several servers. Using several SQL Servers, the databases and tables can be shared among additional hardware. Microsoft BizTalk is designed to be able to increase performance either by running several servers or by moving components on various servers. The IMATIS servers can run Microsoft Network Load Balancing (NLB) to increase performance or, if necessary, the components can be allocated to different servers.
