Software Technology for “High availability deployment in an off-site management software for digital cardiac electrocardiograms operated in an application service provider model.”

Digital Healthcare – Mark R. Kohls, Paul J. Herro, GE Medical Systems Global Technology Co LLC, GE Medical Systems Information Technologies Inc

Abstract for “High availability deployment in an off-site management software for digital cardiac electrocardiograms operated in an application service provider model.”

The preferred embodiment of this invention offers a system and method for remote, high-availability central data management. The preferred embodiment includes a primary remote data storage that stores medical data and a redundant remote data storage that stores a duplicate of the same data. Preferably, the system includes a primary server to store the medical data in primary remote central data storage. Preferably, the primary server stores the medical data in redundant remote central data storage. The system should include a redundant server to store the medical data in both the primary remote central data storage and the redundant remote data storage. In a preferred embodiment, the interface allows access to the system. The interface should be redundant and provide high availability access to remote data management systems.

Background for “High availability deployment in an off-site management software for digital cardiac electrocardiograms operated in an application service provider model.”

“The preferred embodiments are electrocardiogram management systems. In particular, they relate to a method for high availability (HA), deployment of an offsite management system for digital heart electrocardiograms. This system operates in an application service provider model (ASP).

An electrocardiogram (ECG, or EKG), is a graphic record of the electrical activity of a heart. ECGs are typically obtained during routine patient examinations. ECGs can be repeated and updated in order to keep a history of ECGs. A patient’s ECG history can be used to monitor and chart their health and cardiac function.

An electrode or electrocardiographic lead may be used to take an ECG reading. It can be placed in the arms, legs and chest of a patient to get it. An ECG table can be used to take ECG readings. A portable unit can also take ECG readings. A wearable monitor can also be used to record ECG data. ECGS are typically recorded electronically. ECGs can also be charted electronically using a stylus or a paper instrument.

It is essential to ensure that ECG information is available during diagnosis and treatment. ECG information is vital for monitoring a patient’s cardiac function and health during treatment and diagnosis. A healthcare professional (such as a doctor, nurse, assistant, technician or another medical professional) might use ECG trends to diagnose a patient’s cardiac condition. The healthcare provider may also prescribe treatment if the patient is aware of a cardiac condition.

“Quality is key to success in the medical devices market. An ECG management system might serve over thirty customers. Failure in the ECG Management System may lead to dissatisfaction with the ECG system and the company’s services. Dissatisfaction from customers can impact future business opportunities. To provide high quality service, it is important to reduce errors in ECG management systems. A high-availability ECG management system is needed to increase ECG management system availability and up-time. This will allow for better medical diagnosis and treatment.

In the event of an ECG management failure, a service technician will usually be dispatched to the customer’s site. Service calls to customer sites by a technician can be costly and time-consuming because of the location, nature and timing of the problem and the time it takes. To reduce the number of service technicians dispatched to customer sites, redundant high availability systems are necessary. Service calls that are reduced may result in lower service fees, particularly during high-priced periods like weekends, holidays, and nights.

A highly available system or high availability system can be defined as one that offers reliable access. This could include redundant systems and redundant storage. These redundant systems help to ensure the reliable storage and retrieval data and services. An ECG management system designed to be highly available may help improve the operation of a customer’s healthcare facility, such as a hospital or clinic, doctor’s offices, or other medical office. This is done by reliable storage and retrieval. A reliable ECG management system, for example, allows ECG data to be made available to a cardiologist and other users in diagnosis and treatment. It also helps to avoid system downtime and prevents system failures. Data availability allows a cardiologist to quickly diagnose and treat cardiac problems. A cardiologist can provide high-quality care by having quick access to the data and a diagnosis.

Remote, central access to ECG data could allow multiple users to access ECG data reliably. A centralized ECG storage could allow computing resources and support in a smaller number. Application Service Providers (ASPs), are used in the computer field to facilitate centralized access and storage. ASPs act as hosts for applications and data. ASPs typically manage applications and data from an off-site data centre. Companies in the computer field have hired ASPs to manage their data and applications. An ASP allows companies to access applications and data. Typically, companies can access their data and applications remotely via an ASP central location.

“ASPs can offer a variety of services in the computer field, including data storage and backup, as well as redundant systems. ASPs may offer these services to customers, so they don’t have to charge extra for security, backup, or storage systems. ASPs can host a variety of applications that customers may activate or access remotely. The ASP can provide continuous access and support to the applications by concentrating computing power, maintenance and support at the ASP. This will allow customers to avoid the expense of purchasing and maintaining expensive computers. ASPs can provide support for remote clients and may even manage and support applications. Remote data centers may store client data. Remote data centers may allow clients to retrieve their data via a communication medium, such as the Internet or private network.

There is a need for remote access to ECG data that can be accessed from centralized locations for diagnosis and treatment. ECG data must be available to healthcare professionals for diagnosis and treatment. A reliable ECG management system is also needed to provide ECG data access.

Therefore, the medical industry has a need for a reliable, remote, reliable, and high-availability ECG management system that can be used to provide ECG data access to healthcare professionals to aid in diagnosis and treatment. Remote, central maintenance can reduce healthcare facility resources by reducing the manual transfer of ECG information between facilities. It also helps to decrease the amount of resources required for maintaining ECG data at facilities. High availability, redundant systems can improve the reliability of ECG data access by healthcare professionals for diagnosis and treatment by reducing system failures. A method and system to deploy a high-availability off-site management system of digital cardiac electrocardiograms in an application service provider model is needed.

The preferred embodiment of this invention offers a system and method for remote, high-availability central data management. The preferred embodiment includes a primary remote data storage that stores medical data and a redundant remote data storage that stores a duplicate of the same data. Preferably, the system includes a primary server to store the medical data in primary remote central data storage. Preferably, the primary server stores the medical data in redundant remote central data storage. The system should include a redundant server to store the medical data in both the primary remote central data storage and the redundant remote data storage. In a preferred embodiment, the interface allows access to the system. The interface should be redundant and provide high availability access to remote centralized data management systems. Preferably, the system includes a data source such as an electronic cardiogram unit for generating medical information such as demographic data, waveform data, data on patient’s health, and data interpretations. The system could also include an authentication unit to authenticate access to the remote high-availability central data management system.

“A preferred embodiment of the method involves receiving medical data and storing it in a remote centralized storage. The method also authenticates access to remote centralized storage. Preferably, the method includes the storage of medical data in redundant data storages, preferably using remote data servers. The method may also include retrieving medical data from remote centralized storage. Preferably, this is done using the remote server.

The preferred embodiments provide high availability for retrieving and storing waveform data, demographic information, measurements and interpretations of signals data. The preferred embodiments offer redundant access to high availability systems. The preferred embodiments also provide redundant data storage at high availability.

“FIG. “FIG. 1 shows an ECG management software 100 in accordance with a preferred embodiment. The ECG management software 100 comprises a number of subsystems such as an ECG unit 110 and a database cluster 120. An ECG connection 160 is also included. A user connection 170 is also included. An ECG interface 115 is part of the ECG unit 110. The ECG connection 160 links the ECG unit 110 and the database server cluster 120. The cluster interface 125 is part of the database server cluster 120. It also includes redundant data server 132 and redundant data server 132. Primary data storage 140 and redundant data storage 142. Primary user interface server 150 and redundant user server 152. A user can access the database server cluster 120 via the user connection 170. An authentication unit 180 may be included in the system 100.

“The ECG unit 110 can be used in a preferred embodiment to collect ECG data from patients. The ECG unit 110 can also be used for storing ECG data at the external database server cluster 120. The ECG unit 110 should be portable, such as a handheld device like a cart. Alternately, the ECG 110 could be used as an examination table. A patient should be connected to the ECG 110 to monitor their cardiac activity and ECG data. An operator can then use the ECG 110 to store or analyze the ECG data. Preferably, the ECG unit 110 operator selects the information that will be stored at the 120 database server cluster. Alternately, the ECG 110 can automatically store the patient’s information to the database server 120. Alternately, the ECG 110 could be used as a data source to obtain medical data such as images, stress tests data and electroencephalogram data (BEG), data (EMG) or any other waveform data. This includes demographic data, measurements and interpretations of signals data. ECG data or other waveform data is an example of medical data that will be used in the description.

“Preferably the ECG interface115 facilitates communication between ECG unit 110, the database server cluster 120, via the ECG connector 160. The ECG interface115 permits the ECG unit 110 transmit ECG data and other waveform data to be stored at the database server cluster 120. Alternately, the ECG interface 120 may enable the database server cluster 120 transmit information to either the ECG 110 or 110. Preferably, the ECG interface (115) includes at least one modem that allows access to a number of phone lines in order to call the database server 120 via the ECG connector 160. The ECG interface 115 could include eight modems that allow access to eight different lines in the database server cluster 120. Alternately, the ECG connector 115 could include at least one Ethernet adaptor or Internet adaptor. The ECG interface 115 should be redundant and include multiple access devices for high availability.

“Preferably, the ECG connection 160 must be at least one telephone line. Alternately, the ECG connector 160 could be at least one Ethernet, Internet, wireless, direct cable, Bluetooth or other type of connection. The ECG connection 160, which is preferred, allows data transfer between the ECG interface 110 of the ECG unit 110 or the cluster interface 120 of the database server cluster 120. Data is preferred to be transmitted using a secure client/server protocol.

“In a preferred embodiment the database server cluster 120 stores ECG and other waveform, demographic, measurement, and interpretations signal data and gives access to the ECG and other waveform information. The database server cluster 120 should be a high-availability system with redundant components. The database server cluster 120 should be an application service provider. The system 100’s operation is not affected by the location of the database servers cluster 120 relative to the ECG unit 110. Preferably, the database server 120 contains a primary and redundant data servers 130 and 132. It is preferred that all data servers 130 and 132 in the 120 database server cluster include current applications, databases, operating systems, and/or other software. The redundant data server (132) automatically takes over the operation in the event of failure in the primary server 130.

“In a preferred embodiment the data servers 130 and 132 store ECG data as well as other data (such waveform data or demographic data, measurements and interpretations of signals data. For example, Alternately, data servers 130 and 132 can also store programs or applications, such as scheduling programs or medical diagnostic programs or educational programs. The data servers 130 and 132 should be redundant systems with redundant power supplies, redundant cooling fans and/or RAID drives (Redundant array of independent disks) for protecting data, operating systems and/or applications against failures, system failures, and/or corruption. The ECG unit 110 can access the 130 and 132 data servers at the database server 120 to store ECG data or other waveform data. A user can also access the 130 and 132 data servers at the database server 120 to store, retrieve, or distribute ECG data or any other waveform data.

“Preferably the primary data server 130 includes primary storage 140. The redundant data server 130 should include redundant data storage 140. The data storage 140 and 142 contain data such as ECG data and/or demographic data, measurements and interpretations of signals data. The data storage 140 and 142 should include a redundant hard drive array. The hard drives arrays of the data storage 140 and 142 should be configured in RAID (RedundantArrayofIndependent Disks). RAID allows information to be spread across multiple disks in order to ensure a reliable and fast data storage system. The primary data storage 140 should include a primary disk, redundant disks that are ready to be used in the event that the primary disk fails, and another disk that can be used for data parity. The redundant data storage 140 should be configured in a similar way to the primary storage 140. The primary data server 130 can access the primary storage 140 and redundant storage 142 in a preferred embodiment. The redundant data server 132 can also access the redundant storage 142 or the primary storage 140.

“In a preferred embodiment the cluster interface125 allows the ECG unit 110 and the database server cluster 120 to communicate via the ECG connector 160. The ECG interface 110 allows data exchange between the ECG unit 110, and the database server 120. The cluster interface125 communicates with ECG interface115. The preferred connection to the data servers 130 and 132 is through the cluster interface125. The cluster interface 125 should include a number of redundant communications devices such as modems and other network access cards to receive data from ECG unit 110, or any other data source. Multiple communications devices should operate on one bus. The cluster interface 125 could include eight modems, which can be used to receive data from ECG unit 110.

“Preferably the user interface servers 150 and 152 allow users access to the database server cluster 120. The user can access the database server 120 via the user connection 170 at either the primary user interface servers 150 or redundant user interface servers 152. A preferred method is to access the user interface server 130 and 132 via a web browser. Workstation, a PACS, a PACS and Communications System, a terminal or any other access device. The web servers 150 and 152 can be used to access data stored 140, 142, 130, and 132. The user interface servers 150 and 152 should be redundant. The user interface servers 150 and 152 contain current applications, databases, operating systems, and other software to ensure high availability and reliable access to the database cluster 120. The redundant user interface server (152) takes over access operations in the event of failure in primary user interface server 150. The user interface servers 150 and 152 should include redundant power supplies, redundant cooling fan, redundant network cards, and redundant power supplies (e.g. Fast Ethernet) and/or RAID drive for operating systems, applications and/or data protection against disk failure, system breakdown, and/or corruption.

“Preferably, users can communicate with the database cluster 120 through the user connection 170. Preferably, the user connection 170 can be the Internet, a private network or Ethernet, or any other connection. The preferred embodiment of the user connection 170 includes redundant components, such as redundant network cables and switches, and/or routers that transmit data to networks such as the Internet, private networks, or the Internet. If a component of the user connection 170 fails, the redundant component 170 will handle the network traffic.

“In an alternate embodiment, the cluster interface may be integrated with user interface servers 150,152 to allow access for the ECG unit 110 as well as other users. Alternately, the ECG connector 160 and the user connect 170 can be one connection, allowing bidirectional communication between the database server 120 and external users, such as a doctor, technician, or other user. The above-described embodiments of the invention are only examples. However, the system 100 could include many of the subsystems mentioned above.

“An alternative embodiment of the database server cluster may contain an authentication unit 180 that authenticates access to the database servers cluster via the cluster interface (125) and/or user interface servers (150, 152). The authentication unit 180 should include a predetermined code or set authentication codes (such a table or database of codes). An authentication code is a good example. You can generate the authentication code in a variety of ways. For example, user input, daily, monthly, random, or any other method. An authentication code may be sent to the authentication unit 180 by the ECG unit 110 at cluster interface 125, and/or another user at user interface servers 150,152. The authentication code can be assigned to an individual user or group of users depending on a type of data source, location and/or function. To ensure reliability, the preferred embodiment of the authentication unit 180 contains redundant components.

The ECG connection 160 connects the ECG unit 110 to the 120-member database server cluster. The ECG unit 110, the database server cluster 120 and the ECG interface115 communicate via the ECG connector 160. The user connects to the database servers cluster 120 via the user interface server 150 or 152 using the user connection 170. The cluster interface 125, 150 and 152 are connected to data servers 130 and 132 within the database server cluster 120. Access to data from the data storage 140 and 142 can be made through either the 130 or 132 data servers.

“In operation, an ECG, or other waveform data is obtained from a patient using ECG unit 110, and stored at ECG unit 110. An ECG cart is connected to a patient at a hospital. An ECG can then be electronically charted using the electrical function of the heart. The ECG cart stores the ECG information in its memory.

“Next, connect the ECG unit 110 to the database server 120 via the ECG connector 160 using the ECG interface. 115. One example is that an ECG cart’s on-board modem dials into the database server cluster 120 using a telephone line. The ECG interface interface 115 connects with the cluster interface 125 through the ECG connection 160. One modem on the ECG cart may establish a phone connection to one of the receiving modems at cluster 120. The ECG interface (115) may be manually connected with the ECG connection 160 (for instance, by plugging the modem’s phone line into it). Alternately, the ECG connector 115 can be connected continuously to the ECG connection 160. This is a dedicated connection that connects at the ECG table. The ECG interface 115 might not be physically connected to the ECG connector 160 (for instance, a wireless connection). If one component of the ECG interface115 or cluster interface125 fails, then a redundant component will be available to provide the required functionality. If one of the ECG cart modes fails, the other modem in the ECG bank takes over and dials 120 from the database server cluster 120.

The authentication unit 180 may then authenticate access to the database server 120. The cluster interface 125 may ask the ECG 110 (or, preferably, the user at ECG 110) for an authorization code. This is as described above. The ECG cart prompts the user to enter a password to gain access to the database server 120 after establishing a modem link. The ECG unit 110 then transmits the authentication code via the cluster interface125 to the authentication unit 180. Next, the authentication unit 180 verifies the received authentication code against the predetermined authentication codes, as discussed above. Access to the database server cluster 120 will be denied if the authentication code is not compatible with the predetermined authentication codes. Alternativly, you can try again to enter an authentication code. Access to the database server cluster 120 will be allowed if the authentication code matches the predetermined code. The authentication unit 180, for example, compares the user’s password with the list stored in the authentication 180 and finds a match. The ECG cart user may, for instance, access the 120 database server clusters.

“The ECG unit 110 can then access the database servers cluster 120. The ECG unit 110 can access the 130 data server via the ECG interface115 and the cluster interface125. The ECG cart, for example, accesses 130 of the cluster database server 120 to store the ECG data of the patient.

The ECG unit 110 can store the ECG at primary data storage 140 via primary data server 130. The ECG cart user transfers the ECG to 130 via the primary dataserver 130. In this case, the primary dataserver 130 stores the ECG on a RAID drive. The ECG will be stored in the primary storage 140. After that, the primary server 130 archives it at the redundant storage 142 via redundant data server 132. After the ECG is saved in the RAID drive of the patient, the primary server 130 copies the ECG, and then sends a copy to the redundant server 132. For example, the redundant server 132 then stores the ECG on a backup drive. The database server cluster 120 stores, for example, both a primary and redundant archive copy.

The ECG file is stored on the data servers 130,132, and 140,142. These data servers are then updated to reflect the ECG’s presence. The ECG file may be added to the data servers 130,132 and 140,142 directories so that the ECG can be found on the backup disk and RAID drive. The update can also be reflected on the user interface server 150,152 so that users can access the ECG via user interface server 150,152. The web server 120 of the database server cluster 120 has been updated to include a link to ECG.

“Alternatively, the ECG can be stored at redundant data storage 142, via redundant data server 132, if either the primary storage 130 or 140 has an error/or failure. The ECG cart attempts, for example, to store the ECG at RAID drive 130 via the primary server 130. However, the primary server 130 becomes unavailable because of hardware failure. The ECG cart, for example transfers the ECG from the primary data server 130 to the redundant data service 132 for storage on the RAID drive or backup disk.

“Later, the user can access an ECG at cluster 120. A web browser or a GE Medical Systems MUSECV may be used by the user. Workstation graphical user interface or another information access device. The patient may return to the hospital, and an ECG is taken. For example, a doctor may wish to check the ECG stored on the patient and compare it to the new ECG. The preferred method is to connect via the user connection 170 to the primary user interface server 150. Workstation graphical user interface or another information access device. A doctor might use a web browser to connect to the 120-member database server cluster 120 through the Internet.

“Next, access may be authenticated to the database server cluster 120 using the authentication unit 180. An authentication code may be used to authenticate access, as explained above. The doctor may be asked for a password via the web browser. The doctor’s password is then compared with a list of passwords stored at 180. The doctor can access the database server cluster 120 via web server if the authentication unit 180 matches the doctor?s password.

“The user can then request the ECG, other waveform data or demographic data via the primary user interface 150. The doctor may choose the link from the web server to access the ECG file. The request is then sent to the primary data server 130 by the primary user interface 150. The web server, for example, requests the ECG from primary data server 130. The ECG is then retrieved from the primary storage 140 by the primary server 130. The primary data server 130, for example, locates the ECG files in the directory on the RAID drive and retrieves them from the RAID drive. The ECG is then transmitted by the primary data server 130 to the primary user interface (server 150). The ECG is transferred to the web server’s cache by the primary data server 130. Finally, the user can view the ECG, other waveform data and demographic data via the web browser. Workstation graphical user interface or another information access device. The doctor can view, for example, the ECG stored by the patient on the web server using the web browser from his personal computer.

Alternately, if the primary interface server 150 is down or has an error, the user can access the redundant interface server 152. The user interface servers 150 and 152 can access redundant data server 132, if the primary server 130 is down. If the primary data storage 140 is corrupted or fails, the data servers 130 and 132 can access redundant data storage 142, to retrieve ECG or other waveform data.

A user can also store ECG data or other waveform data at the database server cluster 120 via user interface servers 150 and 152. The primary user interface server 150 may allow the doctor to store the ECG data of the patient in the database server cluster 120. The primary user interface server 150 allows the user to access the database server 120. The doctor may access the database server 120 using a web browser. The authentication unit 180 may then authenticate the user as previously described. The doctor’s password can be verified and access granted.

“Next, the user can transmit the ECG/waveform to the primary user interface (server 150) via the user connection 170. The doctor may initiate an FTP session to the webserver via the browser and then transfer an electronic stored copy to the webserver via the ftp protocol. The primary user interface server 150 then transfers the ECG/waveform to the primary server 130. The web server, for example, transmits the updated ECG to the primary server 130. This will allow the ECG file to be stored with the new ECG. The primary data server 130 then stores the ECG/waveform at the primary storage 140, as explained above. The primary data server 130, for example, stores the ECG or waveform in the RAID drive. As described above, the ECG or any other waveform stored in the primary data server 130 is copied to redundant data storage 142. As described above, the content (for example, directory) of data servers 130,132 and user interface servers 150,152 are updated to reflect any ECG or other waveform. As described above, it is preferable that a problem with the primary user interface servers 150 and/or 140 arises. In this case, the redundant user server 152, redundant server 132, or redundant storage 142 may be used.

“FIG. “FIG. 2” illustrates a flowchart 200 that can be used to store high-availability ECG data in accordance with the preferred embodiment of this invention. At step 210, a patient is asked for an ECG, other waveform data or demographic data. Measurements and interpretations of signals data are also obtained. The ECG and other waveform data can be saved locally. An ECG can be obtained by a patient who is connected to an ECG table in a hospital.

“Next, at step 221, a connection is established to a remote high-availability database server cluster. One bank of modems from the ECG table can dial in to one bank at the database server cluster. For example, if one bank of modems is lost, another bank of modems can complete the connection.

At step 230, authentication may be performed to gain access to the cluster’s database server. A user at the ECG table will be asked for a password or another authentication code when they establish a modem connection. The authentication code is then compared with a predetermined authentication number, as discussed above. Access to the database server cluster will be denied if the authentication code is not compatible with the predetermined authentication codes. Alternativly, you can try again to enter an authentication code. Access to the cluster’s database server cluster will be allowed if the authentication code matches the predetermined code. The password of the user is, for example, compared to a list with preset passwords. For example, if the password of the user matches one in the list, then access to the cluster’s database server cluster will be allowed.

“Next, at step 244, the ECG, or any other waveform, may be stored at a database server cluster. The ECG table user transmits the ECG to a database server cluster. This is done by sending the ECG to a redundant storage device such as a RAID disk. To ensure high availability and reliability, it is preferable that the ECG and other waveform data be stored in redundant storage systems.

“The stored ECG and other waveform data should be duplicated at a secondary redundant storage at step 250. The stored ECG can be copied to a backup hard drive array from the RAID drive. Redundant systems, redundant data and reliable storage ensure that the database cluster is high-availability for ECG management and storage.

“At step 260, the database cluster is updated to reflect the ECG and other waveform data. The name and location of an ECG file or waveform file is added to the interfaces or directory structures of the server to allow retrieval and location of ECG data or other waveform data. This allows for demographic data, measurements, interpretations, and data analysis. After the ECG has been stored, the ECG file’s name and location are added to the cluster directory of the database server. The web server on the cluster of the database servers is then updated to include a link to this file.

“Additionally, an ECG, or other waveform data, may be stored at a remote, high availability server cluster as described above using a Web browser, a GE Medical Systems MSUSE CV? workstation graphical user interface or another information access device. The web browser, GE Medical Systems USE CV? The web browser, GE Medical Systems MUSE CV? As described above, the ECG and other waveform data are then stored redundantly at the database cluster.

“A doctor might obtain an ECG from a patient in a hospital, and then store it on a local MUSE CSV? workstation. The doctor can then access the user interface server 150 from the cluster of database servers using a graphical user-interface on the MUSE CV. workstation. The doctor can transmit the ECG to user interface server 150 after authentication. To do this, drag the icon of an ECG from the local drive to directory of user interface server 15. Next, the user interface server150 transfers the ECG into the redundant storage of database server archive. The user interface server 150 is then updated to include a link to an ECG file in the database server archive.

“FIG. 3. illustrates a flowchart 300 to facilitate high availability ECG access in accordance with the preferred embodiment of this invention. A remote high availability database cluster server cluster may store an ECG or other waveform information, as described in FIG. 2. The database cluster can be accessed later at step 310 to retrieve the ECG and other waveforms. This is a web browser, GE Medical Systems USE CV. The web server, or any other user interface server in the cluster, can be used to view ECG and other waveform data from the workstation. A doctor may want to view the ECG of a patient who is experiencing chest pains and return to hospital to help with diagnosis and treatment. To access the cluster’s web server, the doctor may use a web browser on his personal computer.

“Next, at step 325, the access to the cluster of database servers may be authenticated in accordance with the above. The doctor may be asked for a password via the web browser. The doctor’s password is then compared with a table of passwords. The doctor can access the cluster of database servers via the web server if the doctor’s password matches an entry in the table.

“Next, at step 333, the user can request the ECG file or any other waveform data. The doctor may choose the link from the web server to access the ECG file. The next step is step 340. At this point, the ECG and other waveform data are transferred from the database server cluster to the web server. The doctor can view the ECG by retrieving it from the RAID drive.

“Finally at step 340, you can retrieve the ECG and other waveform data via the web browser, GE Medical Systems USE CV? workstation graphical user interface or another information access device. The doctor can view, for example, the ECG stored by the patient on the web server using the web browser from his personal computer.

The preferred embodiments provide an extremely reliable remote management system for ECGs or other waveform data. The preferred embodiments offer a system that ensures high availability via redundant connections and redundant storage. The preferred embodiments ensure that waveform data is always accessible through redundant storage devices and multiple access interfaces.

The preferred embodiments offer a redundant system that allows for easy access to ECG data and other waveform data. The preferred embodiments also provide redundant components that ensure reliable storage of ECG data and other waveform information. The preferred embodiments provide remote access centralized to enable multiple users to securely store and retrieve data. The preferred embodiments decrease the computing and backup requirements at healthcare facilities and improve healthcare facilities’ workflow in retrieving and storing ECG waveform data.

While the preferred embodiment of the invention was described, those skilled in the arts will understand that many modifications can be made to the invention and equivalents can be used without departing from its scope. Many modifications can be made to adapt particular situations or materials to the teachings without departing from the scope of the invention. The invention is not limited to the disclosed embodiment. However, the appended claims will cover all embodiments within the scope of the invention.

Summary for “High availability deployment in an off-site management software for digital cardiac electrocardiograms operated in an application service provider model.”

“The preferred embodiments are electrocardiogram management systems. In particular, they relate to a method for high availability (HA), deployment of an offsite management system for digital heart electrocardiograms. This system operates in an application service provider model (ASP).

An electrocardiogram (ECG, or EKG), is a graphic record of the electrical activity of a heart. ECGs are typically obtained during routine patient examinations. ECGs can be repeated and updated in order to keep a history of ECGs. A patient’s ECG history can be used to monitor and chart their health and cardiac function.

An electrode or electrocardiographic lead may be used to take an ECG reading. It can be placed in the arms, legs and chest of a patient to get it. An ECG table can be used to take ECG readings. A portable unit can also take ECG readings. A wearable monitor can also be used to record ECG data. ECGS are typically recorded electronically. ECGs can also be charted electronically using a stylus or a paper instrument.

It is essential to ensure that ECG information is available during diagnosis and treatment. ECG information is vital for monitoring a patient’s cardiac function and health during treatment and diagnosis. A healthcare professional (such as a doctor, nurse, assistant, technician or another medical professional) might use ECG trends to diagnose a patient’s cardiac condition. The healthcare provider may also prescribe treatment if the patient is aware of a cardiac condition.

“Quality is key to success in the medical devices market. An ECG management system might serve over thirty customers. Failure in the ECG Management System may lead to dissatisfaction with the ECG system and the company’s services. Dissatisfaction from customers can impact future business opportunities. To provide high quality service, it is important to reduce errors in ECG management systems. A high-availability ECG management system is needed to increase ECG management system availability and up-time. This will allow for better medical diagnosis and treatment.

In the event of an ECG management failure, a service technician will usually be dispatched to the customer’s site. Service calls to customer sites by a technician can be costly and time-consuming because of the location, nature and timing of the problem and the time it takes. To reduce the number of service technicians dispatched to customer sites, redundant high availability systems are necessary. Service calls that are reduced may result in lower service fees, particularly during high-priced periods like weekends, holidays, and nights.

A highly available system or high availability system can be defined as one that offers reliable access. This could include redundant systems and redundant storage. These redundant systems help to ensure the reliable storage and retrieval data and services. An ECG management system designed to be highly available may help improve the operation of a customer’s healthcare facility, such as a hospital or clinic, doctor’s offices, or other medical office. This is done by reliable storage and retrieval. A reliable ECG management system, for example, allows ECG data to be made available to a cardiologist and other users in diagnosis and treatment. It also helps to avoid system downtime and prevents system failures. Data availability allows a cardiologist to quickly diagnose and treat cardiac problems. A cardiologist can provide high-quality care by having quick access to the data and a diagnosis.

Remote, central access to ECG data could allow multiple users to access ECG data reliably. A centralized ECG storage could allow computing resources and support in a smaller number. Application Service Providers (ASPs), are used in the computer field to facilitate centralized access and storage. ASPs act as hosts for applications and data. ASPs typically manage applications and data from an off-site data centre. Companies in the computer field have hired ASPs to manage their data and applications. An ASP allows companies to access applications and data. Typically, companies can access their data and applications remotely via an ASP central location.

“ASPs can offer a variety of services in the computer field, including data storage and backup, as well as redundant systems. ASPs may offer these services to customers, so they don’t have to charge extra for security, backup, or storage systems. ASPs can host a variety of applications that customers may activate or access remotely. The ASP can provide continuous access and support to the applications by concentrating computing power, maintenance and support at the ASP. This will allow customers to avoid the expense of purchasing and maintaining expensive computers. ASPs can provide support for remote clients and may even manage and support applications. Remote data centers may store client data. Remote data centers may allow clients to retrieve their data via a communication medium, such as the Internet or private network.

There is a need for remote access to ECG data that can be accessed from centralized locations for diagnosis and treatment. ECG data must be available to healthcare professionals for diagnosis and treatment. A reliable ECG management system is also needed to provide ECG data access.

Therefore, the medical industry has a need for a reliable, remote, reliable, and high-availability ECG management system that can be used to provide ECG data access to healthcare professionals to aid in diagnosis and treatment. Remote, central maintenance can reduce healthcare facility resources by reducing the manual transfer of ECG information between facilities. It also helps to decrease the amount of resources required for maintaining ECG data at facilities. High availability, redundant systems can improve the reliability of ECG data access by healthcare professionals for diagnosis and treatment by reducing system failures. A method and system to deploy a high-availability off-site management system of digital cardiac electrocardiograms in an application service provider model is needed.

The preferred embodiment of this invention offers a system and method for remote, high-availability central data management. The preferred embodiment includes a primary remote data storage that stores medical data and a redundant remote data storage that stores a duplicate of the same data. Preferably, the system includes a primary server to store the medical data in primary remote central data storage. Preferably, the primary server stores the medical data in redundant remote central data storage. The system should include a redundant server to store the medical data in both the primary remote central data storage and the redundant remote data storage. In a preferred embodiment, the interface allows access to the system. The interface should be redundant and provide high availability access to remote centralized data management systems. Preferably, the system includes a data source such as an electronic cardiogram unit for generating medical information such as demographic data, waveform data, data on patient’s health, and data interpretations. The system could also include an authentication unit to authenticate access to the remote high-availability central data management system.

“A preferred embodiment of the method involves receiving medical data and storing it in a remote centralized storage. The method also authenticates access to remote centralized storage. Preferably, the method includes the storage of medical data in redundant data storages, preferably using remote data servers. The method may also include retrieving medical data from remote centralized storage. Preferably, this is done using the remote server.

The preferred embodiments provide high availability for retrieving and storing waveform data, demographic information, measurements and interpretations of signals data. The preferred embodiments offer redundant access to high availability systems. The preferred embodiments also provide redundant data storage at high availability.

“FIG. “FIG. 1 shows an ECG management software 100 in accordance with a preferred embodiment. The ECG management software 100 comprises a number of subsystems such as an ECG unit 110 and a database cluster 120. An ECG connection 160 is also included. A user connection 170 is also included. An ECG interface 115 is part of the ECG unit 110. The ECG connection 160 links the ECG unit 110 and the database server cluster 120. The cluster interface 125 is part of the database server cluster 120. It also includes redundant data server 132 and redundant data server 132. Primary data storage 140 and redundant data storage 142. Primary user interface server 150 and redundant user server 152. A user can access the database server cluster 120 via the user connection 170. An authentication unit 180 may be included in the system 100.

“The ECG unit 110 can be used in a preferred embodiment to collect ECG data from patients. The ECG unit 110 can also be used for storing ECG data at the external database server cluster 120. The ECG unit 110 should be portable, such as a handheld device like a cart. Alternately, the ECG 110 could be used as an examination table. A patient should be connected to the ECG 110 to monitor their cardiac activity and ECG data. An operator can then use the ECG 110 to store or analyze the ECG data. Preferably, the ECG unit 110 operator selects the information that will be stored at the 120 database server cluster. Alternately, the ECG 110 can automatically store the patient’s information to the database server 120. Alternately, the ECG 110 could be used as a data source to obtain medical data such as images, stress tests data and electroencephalogram data (BEG), data (EMG) or any other waveform data. This includes demographic data, measurements and interpretations of signals data. ECG data or other waveform data is an example of medical data that will be used in the description.

“Preferably the ECG interface115 facilitates communication between ECG unit 110, the database server cluster 120, via the ECG connector 160. The ECG interface115 permits the ECG unit 110 transmit ECG data and other waveform data to be stored at the database server cluster 120. Alternately, the ECG interface 120 may enable the database server cluster 120 transmit information to either the ECG 110 or 110. Preferably, the ECG interface (115) includes at least one modem that allows access to a number of phone lines in order to call the database server 120 via the ECG connector 160. The ECG interface 115 could include eight modems that allow access to eight different lines in the database server cluster 120. Alternately, the ECG connector 115 could include at least one Ethernet adaptor or Internet adaptor. The ECG interface 115 should be redundant and include multiple access devices for high availability.

“Preferably, the ECG connection 160 must be at least one telephone line. Alternately, the ECG connector 160 could be at least one Ethernet, Internet, wireless, direct cable, Bluetooth or other type of connection. The ECG connection 160, which is preferred, allows data transfer between the ECG interface 110 of the ECG unit 110 or the cluster interface 120 of the database server cluster 120. Data is preferred to be transmitted using a secure client/server protocol.

“In a preferred embodiment the database server cluster 120 stores ECG and other waveform, demographic, measurement, and interpretations signal data and gives access to the ECG and other waveform information. The database server cluster 120 should be a high-availability system with redundant components. The database server cluster 120 should be an application service provider. The system 100’s operation is not affected by the location of the database servers cluster 120 relative to the ECG unit 110. Preferably, the database server 120 contains a primary and redundant data servers 130 and 132. It is preferred that all data servers 130 and 132 in the 120 database server cluster include current applications, databases, operating systems, and/or other software. The redundant data server (132) automatically takes over the operation in the event of failure in the primary server 130.

“In a preferred embodiment the data servers 130 and 132 store ECG data as well as other data (such waveform data or demographic data, measurements and interpretations of signals data. For example, Alternately, data servers 130 and 132 can also store programs or applications, such as scheduling programs or medical diagnostic programs or educational programs. The data servers 130 and 132 should be redundant systems with redundant power supplies, redundant cooling fans and/or RAID drives (Redundant array of independent disks) for protecting data, operating systems and/or applications against failures, system failures, and/or corruption. The ECG unit 110 can access the 130 and 132 data servers at the database server 120 to store ECG data or other waveform data. A user can also access the 130 and 132 data servers at the database server 120 to store, retrieve, or distribute ECG data or any other waveform data.

“Preferably the primary data server 130 includes primary storage 140. The redundant data server 130 should include redundant data storage 140. The data storage 140 and 142 contain data such as ECG data and/or demographic data, measurements and interpretations of signals data. The data storage 140 and 142 should include a redundant hard drive array. The hard drives arrays of the data storage 140 and 142 should be configured in RAID (RedundantArrayofIndependent Disks). RAID allows information to be spread across multiple disks in order to ensure a reliable and fast data storage system. The primary data storage 140 should include a primary disk, redundant disks that are ready to be used in the event that the primary disk fails, and another disk that can be used for data parity. The redundant data storage 140 should be configured in a similar way to the primary storage 140. The primary data server 130 can access the primary storage 140 and redundant storage 142 in a preferred embodiment. The redundant data server 132 can also access the redundant storage 142 or the primary storage 140.

“In a preferred embodiment the cluster interface125 allows the ECG unit 110 and the database server cluster 120 to communicate via the ECG connector 160. The ECG interface 110 allows data exchange between the ECG unit 110, and the database server 120. The cluster interface125 communicates with ECG interface115. The preferred connection to the data servers 130 and 132 is through the cluster interface125. The cluster interface 125 should include a number of redundant communications devices such as modems and other network access cards to receive data from ECG unit 110, or any other data source. Multiple communications devices should operate on one bus. The cluster interface 125 could include eight modems, which can be used to receive data from ECG unit 110.

“Preferably the user interface servers 150 and 152 allow users access to the database server cluster 120. The user can access the database server 120 via the user connection 170 at either the primary user interface servers 150 or redundant user interface servers 152. A preferred method is to access the user interface server 130 and 132 via a web browser. Workstation, a PACS, a PACS and Communications System, a terminal or any other access device. The web servers 150 and 152 can be used to access data stored 140, 142, 130, and 132. The user interface servers 150 and 152 should be redundant. The user interface servers 150 and 152 contain current applications, databases, operating systems, and other software to ensure high availability and reliable access to the database cluster 120. The redundant user interface server (152) takes over access operations in the event of failure in primary user interface server 150. The user interface servers 150 and 152 should include redundant power supplies, redundant cooling fan, redundant network cards, and redundant power supplies (e.g. Fast Ethernet) and/or RAID drive for operating systems, applications and/or data protection against disk failure, system breakdown, and/or corruption.

“Preferably, users can communicate with the database cluster 120 through the user connection 170. Preferably, the user connection 170 can be the Internet, a private network or Ethernet, or any other connection. The preferred embodiment of the user connection 170 includes redundant components, such as redundant network cables and switches, and/or routers that transmit data to networks such as the Internet, private networks, or the Internet. If a component of the user connection 170 fails, the redundant component 170 will handle the network traffic.

“In an alternate embodiment, the cluster interface may be integrated with user interface servers 150,152 to allow access for the ECG unit 110 as well as other users. Alternately, the ECG connector 160 and the user connect 170 can be one connection, allowing bidirectional communication between the database server 120 and external users, such as a doctor, technician, or other user. The above-described embodiments of the invention are only examples. However, the system 100 could include many of the subsystems mentioned above.

“An alternative embodiment of the database server cluster may contain an authentication unit 180 that authenticates access to the database servers cluster via the cluster interface (125) and/or user interface servers (150, 152). The authentication unit 180 should include a predetermined code or set authentication codes (such a table or database of codes). An authentication code is a good example. You can generate the authentication code in a variety of ways. For example, user input, daily, monthly, random, or any other method. An authentication code may be sent to the authentication unit 180 by the ECG unit 110 at cluster interface 125, and/or another user at user interface servers 150,152. The authentication code can be assigned to an individual user or group of users depending on a type of data source, location and/or function. To ensure reliability, the preferred embodiment of the authentication unit 180 contains redundant components.

The ECG connection 160 connects the ECG unit 110 to the 120-member database server cluster. The ECG unit 110, the database server cluster 120 and the ECG interface115 communicate via the ECG connector 160. The user connects to the database servers cluster 120 via the user interface server 150 or 152 using the user connection 170. The cluster interface 125, 150 and 152 are connected to data servers 130 and 132 within the database server cluster 120. Access to data from the data storage 140 and 142 can be made through either the 130 or 132 data servers.

“In operation, an ECG, or other waveform data is obtained from a patient using ECG unit 110, and stored at ECG unit 110. An ECG cart is connected to a patient at a hospital. An ECG can then be electronically charted using the electrical function of the heart. The ECG cart stores the ECG information in its memory.

“Next, connect the ECG unit 110 to the database server 120 via the ECG connector 160 using the ECG interface. 115. One example is that an ECG cart’s on-board modem dials into the database server cluster 120 using a telephone line. The ECG interface interface 115 connects with the cluster interface 125 through the ECG connection 160. One modem on the ECG cart may establish a phone connection to one of the receiving modems at cluster 120. The ECG interface (115) may be manually connected with the ECG connection 160 (for instance, by plugging the modem’s phone line into it). Alternately, the ECG connector 115 can be connected continuously to the ECG connection 160. This is a dedicated connection that connects at the ECG table. The ECG interface 115 might not be physically connected to the ECG connector 160 (for instance, a wireless connection). If one component of the ECG interface115 or cluster interface125 fails, then a redundant component will be available to provide the required functionality. If one of the ECG cart modes fails, the other modem in the ECG bank takes over and dials 120 from the database server cluster 120.

The authentication unit 180 may then authenticate access to the database server 120. The cluster interface 125 may ask the ECG 110 (or, preferably, the user at ECG 110) for an authorization code. This is as described above. The ECG cart prompts the user to enter a password to gain access to the database server 120 after establishing a modem link. The ECG unit 110 then transmits the authentication code via the cluster interface125 to the authentication unit 180. Next, the authentication unit 180 verifies the received authentication code against the predetermined authentication codes, as discussed above. Access to the database server cluster 120 will be denied if the authentication code is not compatible with the predetermined authentication codes. Alternativly, you can try again to enter an authentication code. Access to the database server cluster 120 will be allowed if the authentication code matches the predetermined code. The authentication unit 180, for example, compares the user’s password with the list stored in the authentication 180 and finds a match. The ECG cart user may, for instance, access the 120 database server clusters.

“The ECG unit 110 can then access the database servers cluster 120. The ECG unit 110 can access the 130 data server via the ECG interface115 and the cluster interface125. The ECG cart, for example, accesses 130 of the cluster database server 120 to store the ECG data of the patient.

The ECG unit 110 can store the ECG at primary data storage 140 via primary data server 130. The ECG cart user transfers the ECG to 130 via the primary dataserver 130. In this case, the primary dataserver 130 stores the ECG on a RAID drive. The ECG will be stored in the primary storage 140. After that, the primary server 130 archives it at the redundant storage 142 via redundant data server 132. After the ECG is saved in the RAID drive of the patient, the primary server 130 copies the ECG, and then sends a copy to the redundant server 132. For example, the redundant server 132 then stores the ECG on a backup drive. The database server cluster 120 stores, for example, both a primary and redundant archive copy.

The ECG file is stored on the data servers 130,132, and 140,142. These data servers are then updated to reflect the ECG’s presence. The ECG file may be added to the data servers 130,132 and 140,142 directories so that the ECG can be found on the backup disk and RAID drive. The update can also be reflected on the user interface server 150,152 so that users can access the ECG via user interface server 150,152. The web server 120 of the database server cluster 120 has been updated to include a link to ECG.

“Alternatively, the ECG can be stored at redundant data storage 142, via redundant data server 132, if either the primary storage 130 or 140 has an error/or failure. The ECG cart attempts, for example, to store the ECG at RAID drive 130 via the primary server 130. However, the primary server 130 becomes unavailable because of hardware failure. The ECG cart, for example transfers the ECG from the primary data server 130 to the redundant data service 132 for storage on the RAID drive or backup disk.

“Later, the user can access an ECG at cluster 120. A web browser or a GE Medical Systems MUSECV may be used by the user. Workstation graphical user interface or another information access device. The patient may return to the hospital, and an ECG is taken. For example, a doctor may wish to check the ECG stored on the patient and compare it to the new ECG. The preferred method is to connect via the user connection 170 to the primary user interface server 150. Workstation graphical user interface or another information access device. A doctor might use a web browser to connect to the 120-member database server cluster 120 through the Internet.

“Next, access may be authenticated to the database server cluster 120 using the authentication unit 180. An authentication code may be used to authenticate access, as explained above. The doctor may be asked for a password via the web browser. The doctor’s password is then compared with a list of passwords stored at 180. The doctor can access the database server cluster 120 via web server if the authentication unit 180 matches the doctor?s password.

“The user can then request the ECG, other waveform data or demographic data via the primary user interface 150. The doctor may choose the link from the web server to access the ECG file. The request is then sent to the primary data server 130 by the primary user interface 150. The web server, for example, requests the ECG from primary data server 130. The ECG is then retrieved from the primary storage 140 by the primary server 130. The primary data server 130, for example, locates the ECG files in the directory on the RAID drive and retrieves them from the RAID drive. The ECG is then transmitted by the primary data server 130 to the primary user interface (server 150). The ECG is transferred to the web server’s cache by the primary data server 130. Finally, the user can view the ECG, other waveform data and demographic data via the web browser. Workstation graphical user interface or another information access device. The doctor can view, for example, the ECG stored by the patient on the web server using the web browser from his personal computer.

Alternately, if the primary interface server 150 is down or has an error, the user can access the redundant interface server 152. The user interface servers 150 and 152 can access redundant data server 132, if the primary server 130 is down. If the primary data storage 140 is corrupted or fails, the data servers 130 and 132 can access redundant data storage 142, to retrieve ECG or other waveform data.

A user can also store ECG data or other waveform data at the database server cluster 120 via user interface servers 150 and 152. The primary user interface server 150 may allow the doctor to store the ECG data of the patient in the database server cluster 120. The primary user interface server 150 allows the user to access the database server 120. The doctor may access the database server 120 using a web browser. The authentication unit 180 may then authenticate the user as previously described. The doctor’s password can be verified and access granted.

“Next, the user can transmit the ECG/waveform to the primary user interface (server 150) via the user connection 170. The doctor may initiate an FTP session to the webserver via the browser and then transfer an electronic stored copy to the webserver via the ftp protocol. The primary user interface server 150 then transfers the ECG/waveform to the primary server 130. The web server, for example, transmits the updated ECG to the primary server 130. This will allow the ECG file to be stored with the new ECG. The primary data server 130 then stores the ECG/waveform at the primary storage 140, as explained above. The primary data server 130, for example, stores the ECG or waveform in the RAID drive. As described above, the ECG or any other waveform stored in the primary data server 130 is copied to redundant data storage 142. As described above, the content (for example, directory) of data servers 130,132 and user interface servers 150,152 are updated to reflect any ECG or other waveform. As described above, it is preferable that a problem with the primary user interface servers 150 and/or 140 arises. In this case, the redundant user server 152, redundant server 132, or redundant storage 142 may be used.

“FIG. “FIG. 2” illustrates a flowchart 200 that can be used to store high-availability ECG data in accordance with the preferred embodiment of this invention. At step 210, a patient is asked for an ECG, other waveform data or demographic data. Measurements and interpretations of signals data are also obtained. The ECG and other waveform data can be saved locally. An ECG can be obtained by a patient who is connected to an ECG table in a hospital.

“Next, at step 221, a connection is established to a remote high-availability database server cluster. One bank of modems from the ECG table can dial in to one bank at the database server cluster. For example, if one bank of modems is lost, another bank of modems can complete the connection.

At step 230, authentication may be performed to gain access to the cluster’s database server. A user at the ECG table will be asked for a password or another authentication code when they establish a modem connection. The authentication code is then compared with a predetermined authentication number, as discussed above. Access to the database server cluster will be denied if the authentication code is not compatible with the predetermined authentication codes. Alternativly, you can try again to enter an authentication code. Access to the cluster’s database server cluster will be allowed if the authentication code matches the predetermined code. The password of the user is, for example, compared to a list with preset passwords. For example, if the password of the user matches one in the list, then access to the cluster’s database server cluster will be allowed.

“Next, at step 244, the ECG, or any other waveform, may be stored at a database server cluster. The ECG table user transmits the ECG to a database server cluster. This is done by sending the ECG to a redundant storage device such as a RAID disk. To ensure high availability and reliability, it is preferable that the ECG and other waveform data be stored in redundant storage systems.

“The stored ECG and other waveform data should be duplicated at a secondary redundant storage at step 250. The stored ECG can be copied to a backup hard drive array from the RAID drive. Redundant systems, redundant data and reliable storage ensure that the database cluster is high-availability for ECG management and storage.

“At step 260, the database cluster is updated to reflect the ECG and other waveform data. The name and location of an ECG file or waveform file is added to the interfaces or directory structures of the server to allow retrieval and location of ECG data or other waveform data. This allows for demographic data, measurements, interpretations, and data analysis. After the ECG has been stored, the ECG file’s name and location are added to the cluster directory of the database server. The web server on the cluster of the database servers is then updated to include a link to this file.

“Additionally, an ECG, or other waveform data, may be stored at a remote, high availability server cluster as described above using a Web browser, a GE Medical Systems MSUSE CV? workstation graphical user interface or another information access device. The web browser, GE Medical Systems USE CV? The web browser, GE Medical Systems MUSE CV? As described above, the ECG and other waveform data are then stored redundantly at the database cluster.

“A doctor might obtain an ECG from a patient in a hospital, and then store it on a local MUSE CSV? workstation. The doctor can then access the user interface server 150 from the cluster of database servers using a graphical user-interface on the MUSE CV. workstation. The doctor can transmit the ECG to user interface server 150 after authentication. To do this, drag the icon of an ECG from the local drive to directory of user interface server 15. Next, the user interface server150 transfers the ECG into the redundant storage of database server archive. The user interface server 150 is then updated to include a link to an ECG file in the database server archive.

“FIG. 3. illustrates a flowchart 300 to facilitate high availability ECG access in accordance with the preferred embodiment of this invention. A remote high availability database cluster server cluster may store an ECG or other waveform information, as described in FIG. 2. The database cluster can be accessed later at step 310 to retrieve the ECG and other waveforms. This is a web browser, GE Medical Systems USE CV. The web server, or any other user interface server in the cluster, can be used to view ECG and other waveform data from the workstation. A doctor may want to view the ECG of a patient who is experiencing chest pains and return to hospital to help with diagnosis and treatment. To access the cluster’s web server, the doctor may use a web browser on his personal computer.

“Next, at step 325, the access to the cluster of database servers may be authenticated in accordance with the above. The doctor may be asked for a password via the web browser. The doctor’s password is then compared with a table of passwords. The doctor can access the cluster of database servers via the web server if the doctor’s password matches an entry in the table.

“Next, at step 333, the user can request the ECG file or any other waveform data. The doctor may choose the link from the web server to access the ECG file. The next step is step 340. At this point, the ECG and other waveform data are transferred from the database server cluster to the web server. The doctor can view the ECG by retrieving it from the RAID drive.

“Finally at step 340, you can retrieve the ECG and other waveform data via the web browser, GE Medical Systems USE CV? workstation graphical user interface or another information access device. The doctor can view, for example, the ECG stored by the patient on the web server using the web browser from his personal computer.

The preferred embodiments provide an extremely reliable remote management system for ECGs or other waveform data. The preferred embodiments offer a system that ensures high availability via redundant connections and redundant storage. The preferred embodiments ensure that waveform data is always accessible through redundant storage devices and multiple access interfaces.

The preferred embodiments offer a redundant system that allows for easy access to ECG data and other waveform data. The preferred embodiments also provide redundant components that ensure reliable storage of ECG data and other waveform information. The preferred embodiments provide remote access centralized to enable multiple users to securely store and retrieve data. The preferred embodiments decrease the computing and backup requirements at healthcare facilities and improve healthcare facilities’ workflow in retrieving and storing ECG waveform data.

While the preferred embodiment of the invention was described, those skilled in the arts will understand that many modifications can be made to the invention and equivalents can be used without departing from its scope. Many modifications can be made to adapt particular situations or materials to the teachings without departing from the scope of the invention. The invention is not limited to the disclosed embodiment. However, the appended claims will cover all embodiments within the scope of the invention.

Click here to view the patent on Google Patents.