CN1759413A - System for accessing patient information - Google Patents

Abstract

Certain exemplary embodiments provide a system for accessing patient medical information in a network. The network includes multiple servers. Certain exemplary embodiments of the network also include a repository including a patient identifier and an associated server identifier identifying one or more servers storing medical information associated with a particular patient. In response to a received command or request to display medical information for a particular patient, certain exemplary embodiments of the network include a search processor for initiating a search of the repository to locate the Specific server identifier. In response to user commands, certain exemplary embodiments of the network include an interface processor for generating a Uniform Resource Locator (URL) address incorporating the located specific server identifier in the data field, and for initiating access at A request for stored patient-specific medical information at the generated URL address hosted by the server.

Description

Systems to Access Patient Information

Cross References to Related Applications

This application claims priority to co-pending Provisional Application Serial No. 60/454.278 (Applicant Docket No. 03P03690US) filed March 13, 2003.

Background technique

Known products provide a web viewer for patient vital data. In order to display a particular patient's vital data via the web viewer, a user is typically required to provide a series of identifiers including user ID, user password, patient name, patient identification code, server and/or patient vital data residency location etc. Often times, however, users are unaware of one or more required identifiers for accessing such vital data, since such information is typically maintained at least in part within the clinical environment at the time of medical visit. Furthermore, the temporary circulation of such data is also problematic. In some known products, the data and/or medical records obtained by users cannot accurately reflect real-time patient information.

Contents of the invention

Certain exemplary embodiments provide a system for accessing patient medical information in a network. The network includes multiple servers. Certain exemplary embodiments of the network also include a repository including a patient identifier and an associated server identifier identifying one or more servers storing medical information associated with a particular patient. In response to a received command or request to display medical information for a particular patient, certain exemplary embodiments of the network include a search processor for initiating a search of the repository to locate the Specific server identifier. In response to user commands, certain exemplary embodiments of the network include an interface processor for generating a Uniform Resource Locator (URL) address incorporating the located specific server identifier into the data field, and for initiating access by The server hosts the request for the stored patient-specific medical information at the generated URL address.

Description of drawings

The wide range of possible embodiments can be better understood with the following detailed description and accompanying drawings, in which:

Figure 1 is an exemplary embodiment of a system for accessing patient information;

Figure 2 is a block diagram of an exemplary embodiment of a telematics device for accessing patient information;

3 is an exemplary embodiment of a user interface supporting operations associated with a system for accessing patient information;

4 is an exemplary embodiment of a user interface supporting operations associated with a system for accessing patient information;

5 is an exemplary embodiment of a user interface supporting operations associated with a system for accessing patient information;

6 is an exemplary embodiment of a user interface supporting operations associated with a system for accessing patient information;

Figure 7 is a flowchart for an exemplary embodiment of a method of a system for accessing patient information; and

8 is a flowchart of an exemplary embodiment of a method for a system for accessing patient information.

definition

When the following terms are used herein, the attached definitions apply:

Database - One or more collections of structured persistent data, usually associated with software that updates and queries the data. A simple database can be a single file containing many records, each structured using the same set of fields. A database may contain maps where various identifiers are organized according to various factors such as identity, physical location, location on a network, function, and so on.

Function link - a link on the page that allows the user to access a specific function by activating the function link through actions such as keystrokes or mouse clicks. Activation of a function link may occur via a "single action," as used herein, refers to any single action that can activate a function, such as a mouse click, a mouse click to activate a link, a keyboard tap, a pen tap, a finger tap, or a signal, ( start at a predetermined screen position and last for a predetermined time), and/or any equivalent thereof.

Identifier - A set of symbols unique to a particular entity, activity, and/or file. For example, an identifier could be a medical record number. Identifiers may be human and/or machine readable, such as numbers, strings of letters, barcodes, RFID, and the like.

Patient Identifier - An identifier for a specific patient of a healthcare facility. A patient identifier may be a social security number, taxpayer ID number, state ID number, medical number, Medicaid number, Medicare ID number, medical record number, and the like.

Server Identifier - the identifier of the specific server to which the one or more patient monitoring devices are linked.

User Identifier - an identifier for a particular user of the devices and/or systems described herein.

Information device - a device capable of processing information, such as any general purpose and/or special purpose computer, such as a personal computer, workstation, server, minicomputer, mainframe, supercomputer, computer terminal, laptop, telephone, and/or any equivalents and so on.

Interface - A boundary across which two independent systems meet and interact or communicate. For connection or interaction by means of an interface.

Machine-readable medium - memory that can be read by an information device.

memory - a device capable of storing analog or digital information, such as nonvolatile memory, volatile memory, random access memory (RAM), read only memory (ROM), flash memory, magnetic media, hard disk, floppy disk, magnetic tape, optical media, compact disks, compact disks, CDs, digital versatile disks, DVDs, and/or redundant arrays of independent disks, etc. The memory may be coupled to the processor and may store instructions adapted to be executed by the processor according to embodiments disclosed herein.

network - a wired and/or wireless communication network.

network interface - telephone, cellular telephone, cellular modem, telephone data modem, fax modem, wireless transceiver, Ethernet card, cable modem, digital subscriber line interface, bridge, hub, router, or other similar device.

Patient - A human or other type of animal regulated for health care purposes.

Patient Information - information relating to the medical and/or treatment of a patient, including real-time vital, biological and/or physiological data, near real-time data relating to vital, biological and/or physiological data and /or past history data, blood pressure parameters, ventilation parameters, vital sign parameters, parameters representing blood oxygen concentration, infusion pump parameters related to infusion, drip drug related parameters, blood gas parameters, insurance information, health care personnel information, health care Institutional information, billing information, household information, financial information, treatment information, medication information, and/or any equivalent, etc.

Patient Monitoring Device - A device capable of collecting, displaying and/or relaying patient information.

Processor - a device and/or set of machine-readable instructions for performing a task. A processor includes any one or combination of hardware, firmware, and/or software. A processor acts upon information by manipulating, analyzing, modifying, transforming, transmitting the information for use by an executable program and/or an information device, and/or routing the information to an output device. The processor can use the capabilities of the controller.

Server - an information device that provides some service to other information devices connected to it via a network. A common example is a file server that has a local disk and services requests from remote clients to read and write files on that disk. The server may also provide access to resources such as programs, shared devices, and the like.

Client - An information device and/or process running on it that requests services from another information device or process running on it ("server") using some protocol and accepts the server's responses. A client is part of a client-server software architecture. For example, a computer that requests the content of a file from a file server is a client of the file server.

Thin Client - a relatively simple client program and/or hardware device that relies primarily on a server for most of its capabilities. Web pages displayed using a standard web browser that also contain either plain text, HTML, scripts, or simple objects such as ActiveX components or Java applets represent exemplary embodiments of this category.

Uniform Resource Locator (URL) - a standard way of specifying the location of an object, such as a web page, on the Internet, a network, and/or servers connected thereto. URLs can contain data fields containing one or more identifiers.

user interface - a device and/or program for presenting information to and/or requesting information from a user. A user interface may include textual, graphical, audio, video, animated and/or tactile elements.

User - An individual who can utilize the system for accessing patient information.

Vital Sign - The measurement of any biological and/or physiological process in a living organism. Exemplary embodiments of vital, biological, and/or physiological data may include data associated with the patient's heart rate, body temperature, blood gases, red blood cell count, white blood cell status, respiratory volume, respiratory rate, and/or any equivalent thereof patient information.

Detailed ways

Certain exemplary embodiments provide a system for accessing patient information in a network. Certain embodiments of the system for accessing patient information in a network include a user interface coupled to a processing method that enables launching of a thin-client vital viewer from a clinical access application via a web-based URL link . Certain exemplary embodiments of the system accept input of a patient identifier and/or user authentication information such as a user name and password. Entry of the patient identifier triggers the system to automatically launch the correct vital monitor containing information pertaining to the patient associated with the accepted patient identifier from the host server located within the hospital clinical information system. Certain exemplary embodiments of a system for accessing patient information automatically check a plurality of servers to provide patient information to a user. By polling the servers, a common database of identifiers of patients and servers on which the patient's information resides is created and maintained. Via the user interface, the patient information is extracted by launching a browser-based application, such as a vital viewer, with the identifier.

FIG. 1 is an exemplary embodiment of a system 100 for accessing patient information. Certain exemplary embodiments of system 100 include a plurality of patient monitoring devices 110 . A patient is coupled to one or more patient monitoring devices. Patient monitoring device 110 is coupled to one or more servers 120 . Server 120 includes one or more processors 125 . Processor 125 performs any function, such as collecting information from associated patient monitoring devices 110, organizing the collected information by patient and/or patient monitoring device identifiers, receiving requests for identifiers stored in server 120, sending requesting information, performing system maintenance, authorizing user access to system 100 and/or any equivalent thereof, and the like.

In some exemplary embodiments of system 100 , server 120 is coupled to repository server 130 . Certain exemplary embodiments of repository server 130 include repository 140 . Repository 140 contains functionality to maintain a database of all patient lists associated with their respective monitoring devices. An example of system 100 for accessing patient information utilizes patient identifiers and server identifiers stored in repository 140 . Repository server 130 includes one or more processors 135 . Processor 135 includes a search processor, an interface processor, an acquisition processor, a display processor, an authorization processor, and/or any equivalent thereof, and the like.

A user accesses patient information via repository server 130 , repository 140 and/or server 120 using any suitable access device 150 . Access device 150 is any general and/or special purpose information device. The network connections of system 100 are wired and/or wireless connections and/or communication networks. Certain exemplary embodiments of the system 100 are password protected and/or use standard network security measures such as password and data encryption, firewalls, virus protection, and/or any equivalent thereof, and the like.

2 is a block diagram of an exemplary embodiment of a telematics device 200, which in some operational embodiments represents, for example, patient monitoring device 110, server 120, repository server 130, repository 140, and/or access to FIG. device 150. Information device 200 includes any number of known components, such as one or more network interfaces 210, one or more processors 220, one or more memories 230 containing instructions 240, one or more input/output (I/O ) device 250, and/or one or more user interfaces 260 coupled to the I/O device 250, and the like.

Certain exemplary embodiments of the telematics device 200 include a user interface 260 . User interface 260 displays patient information. The user interface 260 also presents instructions for interacting with the telematics device 200 . In certain exemplary embodiments, user interface 260 cooperates with one or more input/output (I/O) devices 250 . Interaction between user interface 260 and I/O device 250 allows a user to request, collect, organize, view, and/or relay patient information, among other things. Certain exemplary embodiments of I/O device 250 automatically collect, request, relay, display, and/or organize patient information, among other things. In certain exemplary embodiments, via one or more user interfaces 260 , such as a graphical user interface, a user provides a URL and/or receives current location information related to a patient monitoring device of interest.

Certain exemplary embodiments of the telematics device 200 include patient information comprising real-time, near real-time, or historical patient data collected from other telematics devices, such as patient monitoring devices and their associated servers . In certain exemplary embodiments, patient information is stored in memory 230 . Certain exemplary embodiments of memory 230 contain a list of patient identifiers and their associated server identifiers. The instructions 240 of the telematics device 200 govern the proper collection and organization of data and information within the memory 230 . Instructions 240 are stored in one or more different types of memory.

Certain exemplary embodiments of the telematics device 200 include one or more processors 220 . An exemplary embodiment of processor 220 is a search processor. In response to the command received, processor 220 initiates a search of memory 230 . The received command may be user initiated, or a timed event scheduled by the user or by software. Processor 220 searches for the patient identifier and server identifier. Certain exemplary embodiments of processor 220 poll the various servers to identify patients connected to patient monitoring devices linked to the one or more servers. The polling process is an automatic event and/or a scheduled event. Alternatively, the user instructs processor 220 to initiate a search. In some embodiments, processor 220 provides notification as to whether a particular patient is currently being monitored prior to a user attempting to access the patient's medical information. In order to access patient information, a user does not need to know the exact location of a particular patient.

An exemplary embodiment of processor 220 is an interface processor. Accordingly, certain exemplary embodiments of processor 220 coordinate responses to user commands for patient information. Processor 220 generates a URL address for accessing the requested information. Certain exemplary embodiments of processor 220 generate the URL using the appropriate patient identifier and server identifier. When a URL is activated, processor 220 initiates collection of the requested information. Additionally, processor 220 communicates the collected information via user interface 260 and/or I/O device 250 . In certain exemplary embodiments, processor 220 determines whether the requested patient identifier and/or an associated server identifier exists within the network and initiates generation of a message communicating whether the requested identifier is available. Certain exemplary embodiments of processor 220 refrain from initiating a request to access patient medical information if the requested patient identifier and/or server identifier is not present in the associated network.

An exemplary embodiment of processor 220 is an acquisition processor. Accordingly, certain exemplary embodiments of processor 220 collect and/or compile a list of patient identifiers and server identifiers for storage in memory 230 . Certain exemplary embodiments of processor 220 collect other forms of data, such as patient vital sign data, patient medical history, billing information, and/or any suitable patient information. In some exemplary embodiments, the acquisition functions of processor 220 are automatic and/or scheduled. Alternatively, a user manually instructs processor 220 to perform various tasks. Certain exemplary embodiments of processor 220 periodically and/or aperiodically query a number of different servers to compile data indicative of patient identifiers and associated server identifiers for storage in the repository. Certain exemplary embodiments of processor 220 periodically and/or aperiodically query the plurality of different servers in response to an input identifying the plurality of different servers. An exemplary embodiment of an input is any data form or record that identifies multiple identifiers.

An exemplary embodiment of processor 220 is a display processor. Accordingly, certain exemplary embodiments of processor 220 initiate and/or maintain various forms of displayed data, such as textual and/or graphical data displays of patient information, such as EKG waveforms, on user interface 260 .

An exemplary embodiment of processor 220 is an authorization processor. Accordingly, certain exemplary embodiments of the processor 220 verify that the user is authorized to access patient information stored within one or more telematics devices 200 and/or a network of multiple telematics devices 200 . If the user is not authorized to access patient information, processor 220 blocks access to information device 200 and, in certain exemplary embodiments, processor 220 initiates a message indicating that access is prohibited. Alternatively, if the user is authorized to access the information appliance 200, the processor 220 initiates a communication to the user indicating successful access.

Certain exemplary embodiments of the telematics device 200 include a network interface 210 . The network interface 210 allows interaction with other information appliances 200 via a wired and/or wireless network.

FIG. 3 is an exemplary embodiment of a user interface 300 that supports operations associated with a system for accessing patient information. Certain exemplary embodiments of user interface 300 are non-browser-based executable applications configured to collect information over a network. Certain exemplary embodiments of executable applications support access to patient information via a clinical access application that includes an Internet-compatible user interface 300 and processing methods enabling thin Client life watcher. Certain exemplary embodiments of user interface 300 are viewed and/or presented via the browser page identified by URL address 330 . URL address 330 contains data fields containing various identifiers.

Certain exemplary embodiments of user interface 300 include a login screen 310 . Login screen 310 includes login functionality 320 . Some exemplary embodiments of the login function 320 include a standard username and password system. Thus, the login function 320 accepts a user's name and password to allow access to the system for accessing patient information. Alternatively, the login function 320 accepts input of a patient identifier. In certain exemplary embodiments, entry of the patient identifier results in presentation of the correct vital monitor from a host server located within the hospital clinical information system.

Certain exemplary embodiments of login screen 310 include one or more user interface elements, such as buttons 330 , function links 340 , and/or icon links 350 . Activation of user interface elements 330, 350 and/or function link 340 causes any action such as launching a separate window, redirecting the user to another window, and/or launching a new application.

FIG. 4 is an exemplary embodiment of a user interface 400 that supports operations associated with a system for accessing patient information. The user interface 400 presents a patient information view 410 . Certain exemplary embodiments of the patient information view 410 include a patient list 450 , one or more functional links 440 , and/or one or more scrolling menus 460 . Select a different screen to view by clicking on the page tab 430 . Certain exemplary embodiments of overview view 410 comprise sub-screens within user interface 400 . Certain features of the user interface 400 thus remain static, such as the user identifier 420 and/or various function links 470 such as a print function link icon or a logout hyperlink.

Certain exemplary embodiments of patient list 450 include a list of patient names and associated patient information. Patient information includes name, age, gender, address and/or vital sign data, among others. Certain exemplary embodiments of the patient name contain functional links to additional patient information. In certain exemplary embodiments, a patient name is associated with a chart icon 455 . In certain exemplary embodiments, user selection of the chart icon 455 allows access to any patient information found within traditional patient records.

FIG. 5 is an exemplary embodiment of a user interface 500 that supports operations associated with a system for accessing patient information. User interface 500 includes patient information view 510 . In certain exemplary embodiments, selection of a patient name initiates detailed patient viewing 520 . Detailed patient observation 520 includes additional patient information, such as ID number, vital signs, physiological data, patient monitoring devices currently added to the patient, past patient information, and/or any equivalent thereof, among others. Certain exemplary embodiments of detailed patient viewing 520 also include functional links to applications for managing patient monitoring devices. For example, a user selects the IV drip icon to access a user interface that enables adjustment of IV drip parameters. Certain exemplary embodiments of detailed patient viewing 520 include various scrolling functions 530 to enable viewing of more data.

FIG. 6 is an exemplary embodiment of a user interface 600 that supports operations associated with a system for accessing patient information. Certain exemplary embodiments of the user interface 600 include a patient vitals viewer 610 . The patient vitals monitor 610 contains any vital signs and/or physiological information 620, 650 of the patient. The patient vitals viewer 610 includes one or more sub-screens 630, 640 that include scroll bars. Such a structure allows a user to access more information within a single patient vitals viewer 610 .

Certain exemplary embodiments of information 620 include real-time and/or near real-time physiological information. The information 620, 650 presented within the patient vitals viewer 610 is the result of data collected from the patient monitoring device and/or entered by the healthcare provider at the point of care. Information 620 is presented to the user in text. Some exemplary embodiments of information 650 include graphical information, such as traces indicative of electrical activity of the brain. Information 620 , 650 also contains previous textual and/or graphical patient data and/or information.

FIG. 7 is a flowchart of an exemplary embodiment of a method 700 for a system for accessing patient information. In act 710, a command is received. Certain exemplary embodiments of a command include instructions for collecting patient identifiers and/or server identifiers associated with a particular patient. Commands are automatically generated or manually initiated by a user.

At act 720, identifiers are collected for storage in a repository. In certain exemplary embodiments, the patient identifier designates a patient with patient information stored within the patient information management system. The associated server identifier is used to designate one or more servers on which the patient's information is stored. In act 730, the identifier is stored. Collect and organize identifiers according to any institution's system. In certain exemplary embodiments, the repository server uses a processor, such as a collection, search, web, display, authorization, and/or interface processor, to collect and/or organize patient identifiers and their associated server identifiers . The identifiers are stored in one or more servers and or repositories. In certain exemplary embodiments, the repository includes a map linking patient identifiers with their associated server identifiers to identify servers hosting medical information for a particular patient. Thus, various polling processes retrieve lists of valid patients attached to patient monitoring devices linked to the server, and create a master list and/or map from this collection. The map is constantly and automatically updated so that changes in any monitored patient parameters can be incorporated, thereby eliminating outdated patient information.

In act 740, a URL is generated. The URL incorporates the patient identifier and/or server identifier into the URL data field. At act 750, a request to access information is processed. In certain exemplary embodiments, the URL address in conjunction with the patient identifier and one or more associated server identifiers allows retrieval of patient information within the network via a browser.

FIG. 8 shows a flowchart of an exemplary embodiment of a method 800 for a system for accessing patient information. At act 810, a search of at least one data source is performed to locate the patient identifier and any associated server identifiers. In some exemplary embodiments, the search is the result of an automated command. Alternatively, the user initiates the search via a command entered through the user interface. In act 820, a URL address is generated from the search and incorporates the server identifier and/or patient identifier into its data fields.

At act 830, a request to access patient information at a URL address is received. In some exemplary embodiments, the request is generated by the user clicking on a function link. Alternatively, a user enters a user identifier to generate a list of patients associated with that user. In certain exemplary embodiments, the user also enters a patient identifier in order to generate a request to access information associated with that particular patient.

At act 840, the patient information is communicated for display on the user interface. The transfer of patient information allows users to request real-time and/or near real-time patient information. At act 850, patient information is displayed to the user via the user interface. In certain exemplary embodiments, if the patient identifier is found using the repository and/or the server, the Vital Viewer is activated and presented to the user in a web page where the user views the patient information. If the patient identifier is replicated on multiple servers, the user interface displays this information to the user. If no equivalent patient identifier is found, an appropriate message is displayed to the user. In order to access patient information, a user does not have to enter a patient location, such as a physical location or a location within a network.

Certain exemplary embodiments of the system for accessing patient information include a URL call within the clinical client application: http://<host_server_name_or_IP_Address>/WinViewFrontEnd/WVBootAgent.asp. The URL call is physically mapped to the file WVBootAgent.asp in the directory C:\Inetpub\wwwRoot\WinViewFrontEnd on the gateway server.

Certain exemplary embodiments of a system for accessing patient information include WVBootAgent.asp. This page is called with the following parameters: http://<host_server_name_or_1P_Address>/WinViewFrontEnd/WVBootAgent.asp? Login=guest&PID=xxxxxxxxwvyz&Pwd=winview. The code for this contains:

<%@Language=VBScript%>

<HTML>

<HEAD>

<META NAME="GENERATOR"Content="Microsoft Visual Studio 6.0">

</HEAD>

<BODY bgcolor="black" text="white" close ()">

<%

dim urlParameterl

dim urlParameter2

dim urlParameter3

dim urlParameter4

urlParameter1=trim(request("PID"))

urlParameter2=trim(request("Login"))

urlParameter3=trim(request("Pwd"))

URLValue="checkPID.asp? PID="

URLValue = URLValue & urlParameter1

URLValue=URLValue & ″&Login=″& urlParameter2 &″&Pwd=″& urlParameter3

Response.Write("<SCRIPT language='JavaScript'>")

Response.Write(″top.open(″′&URLValue&″′)″)

Response. Write(″<SCRIPT>″)

%>

<CENTER><h3>WinView Boot Agent</h3></CENTER>

</BODY>

</HTML>

Certain exemplary embodiments of a system for accessing patient information may include checkPID.asp. Extract PID, Login and Pwd from the calling page: WVBootAgent.asp. The code for checkPID.asp contains:

<HTML>

<%@Language=VBScript%>

<BODY>

<%

dim gatewayAmount

dim gatewayArray(10)

dim URLValue

dim temp

dim temp2

dim pidString

dim urlPID

dim urlUser

dim urlLogin

dim urlPwd

urlPID=trim(request("PID"))

urlLogin=trim(request("Login"))

urlPwd=trim(request("Pwd"))

Rem******************************

Rem* creates filesystem objects for reading and writing.

Rem******************************

et fs＝CreateObject("Scripting.FileSystemObject")

Rem******************************

Rem* defines constants for reading, writing, and adding data.

Rem******************************

Const ForReading=1, ForWriting=2, ForAppending=8

Rem******************************

Rem* compares the current PID with the list of Pids

Rem******************************

Within checkPID.asp, pid_info.inf is a manually created file containing a list of PatientIds and their associated Gateway Servers. This file is typically maintained (ie updated) for each gateway. The code for checkPID.asp also contains:

           
    Response. Write("<BR>")

    set f=fs.OpenTextFile
    ("C:\SecureFiles\WinViewFE\pid_info.inf", ForReading,
    false)

    IF f.ReadLine="PID_INFO FILE==D0 NOT MODIFY" THEN

         gateWayAmount=0

          WHILE NOT f.AtEndOfStream

             temp=f.ReadLine

             pos1 = Instr(1, TEMP, "=", 0)

             IF pos1 > 0 THEN

                 temp2 = Mid(temp, pos1+1, len(temp))

                 temp=Mid(temp,1,pos1)

                 pos2 = Instr(1, temp, "\\", 0)

                 IF pos2 > 0 THEN

                     temp=Mid(temp, pos2+2, len(temp))

                     pos3 = Instr(1, temp, "\", 0)

                     IF pos3 > 0 THEN

                         temp=Mid(temp, 1, pos3-1)

                     END IF

                 END IF
				
<dp n="d13"/>
                 IF temp2 = urlPID THEN

                     gatewayArray(gatewayAmount)=temp

                     gatewayAmount=gatewayAmount+1

                 END IF

             END IF

        WEND

    END IF

        

In some exemplary embodiments of checkPID.asp, if only one gateway server is found with the patient ID (PID), then all is well and the next step is to call the actual ActiveX page that launches the winwebviewer. The code for checkPID.asp also contains:

           
    Rem****************************************

    Rem* gives choice if more than one PID is matched,

    Rem *otherwise, start with new PID and server

    Rem*

    Rem****************************************

    IF gatewayAmount=1 THEN

        URLValue = "http://" & gatewayArray(0) &
"/zeus4panel/index1.htm?Serv="

        URLValue = URLValue & gatewayArray(0) &"&Login="&
urlLogin

        URLValue = URLValue &"&Pwd="&urlPwd&"&PatID="&
urlPID

        Response. Redirect URLValue

        Response.end

    ELSEIF gatewayAmount＞1 THEN

        Response.Write("<B><FONT FACE=COURIER SIZE=2>PID
found on more than one gateway server<BR>")

        Response.Write("Please Choose the gateway Server to
use＜/FONT＞＜/B＞＜BR＞＜BR＞")

    For 1＝0 to gatewayAmonunt-1

        Response.Write("<A href='http://"&amp; gatewayArray(0)
&amp;"/zeus4panel/index1.htm?Serv="&amp;gatewayArray(1)&amp;
				
<dp n="d14"/>
              "&amp;Login="&amp;urlLogin&amp;"&amp;Pwd="&amp;urlPwd&amp;"&amp;PatID="&amp; urlPID &amp;"'>Server:"&amp; gatewayArray(1) &amp;
"＜/A＞＜BR＞")

    Next

    ELSE

             Response.Write("<B><FONT FACE=COURIER
SIZE＝2＞PID NOT found on any gateway server

             Server＜/FONT＞＜BR＞＜/B＞")

    END IF

    %>

    ＜/BODY＞

    </HTML>

        

Certain exemplary embodiments of a system for accessing medical information include a GatewayPIDListener ReadMe file containing:

WinView Boot Agent

         WinViewBootReadMe.txt

================================================= =====================

====

introduction

================================================= =====================

====

ask:

One or more gateway servers create ptlist.txt

Shared directory containing ptlist.txt accessible by GatewayPidListener java application, web server (IIS recommended), WinView observer

recommend:

java sdk (re-edit if necessary, java version 1.4.1 is recommended)

Purpose: To allow access to the WinWeb Vital Viewer from a clinical information access application if patient vitals are available.

================================================= ======================

====

decompress

================================================= ======================

====

Create a directory called SecureFiles on your C drive.

Unzip WinViewBoot.zip to this directory.

Two directories will be created (WinViewFE and WebRoot)

You will need to make the WebRoot available from the web server either by making it a virtual directory (IIS) or copying it to a network accessible directory.

NOTE: If you unpacked WinViewBoot.zip to any other directory, you will usually modify the following lines of code in the following .ASP pages:

Line 35 in C:\SecureFiles\WinViewFE\pid_info.inf->checkPID.asp

C:\SecureFiles\WinViewFE\wvpassword.txt->line 29 in ProcessPassword.asp

Edit these to include the appropriate paths to these two files.

================================================= =====================

====

Install

================================================= ======================

====

GateWayList.txt

-------------------

This file is located in the WinViewFE directory. You modify this file with the correct location of the ptlist.txt file on each gateway server you want to poll. For the java application we have access to, ptlist.txt is accessible from a network drive.

Please don't edit the first line:

Use the following format for the ptlist.txt location:

\\[ip address/server name]\[directory name containing ptlist.txt]\ptlist.txt

For example:

\\Gateway1\vs files\ptlist.txt

wvpassword.txt

----------------------

This file is located in the WinViewFE directory. You modify this file with the correct username and password you want to use with the WVLogin.asp page.

This file contains usernames and passwords in the following format:

[Username Password]

For example:

MyName MyPassword

(Note: the name does not contain any spaces at this time)

================================================= ========

====

Using WinViewBoot Agent

================================================= ========

====

From the Clinical Information Access app

---------------------------------

WVBootAgent.asp can be accessed from the web server.

The link to WVBootAgent.asp from the Clinical Information Access application contains the following parameters when invoked: PID, USER

ALSO NOTE: Other clinical information will also be utilized to access application operations.

PID will contain the PID of the patient trying to be observed.

USER will contain the username that will be used to access the watcher.

from the server containing the GatewayPidListener java application

-------------------------------------------------- ---------

To run GatewayPidListener, make sure GateWayList.txt is in the same directory as the GatewayListener.bat file and GatewayListener.class file. (Note: These files should be located in the WinViewFE directory)

Execute the GatewayListener.bat file, which will start the java application and the application will poll the specific gateway server.

Certain exemplary embodiments of a system for accessing medical information include GatewayPIDListener.java. The code contains:

           
    import java.io.*;

    import java.awt.*;

    import java.net.*;

    import java.lang.*;

    import java.util.*;

    import java.lang.Math;

    import java.util.Random;

    import java.text.*;

    import java.util.Vector;

    public class GatewayPidListener extends Thread implements
Runnable

    {

        private String ListFileName =
"GateWayList.txt"; // Location and file name of GateWayList.txt

        private String outputFileName = "pid_info.inf"; // input
The location and filename of the output file

        private int PollDelay = 30; // delay for polling in seconds

        boolean keepRunning=true;//Really run continuously in seconds

        boolean debug=false; //debug output

    Vector serverArray=new Vector();//Reserve all gateway servers

    private int serverAmount = 0;

    File ListFile = new File(ListFileName);

    File outputFile = new File(output FileName);

    public GatewayPidLis tener()
				
<dp n="d18"/>
    {

        this. start();

    }//end constructor

    public void run()

    {

        System.out.printIn("Polling gateway servers...");

        do

        {

            ListGrabber();

            CreateOutput();

    //reset all data

            serverArray. removeAllElements();

            serverAmount=0

            System.out.print(">");

            try//sleep metering

            {

               sleep(PollDelay * 1000);

            }catch(InterruptedException ie){

               System.err.printIn("Problem with the sleep
thread:"+ie);

        }//end catch program

        }while(keepRunning);//loop during keepRunning

    }

    public static void main(String argv[])

    {

        GatewayPidListener MV = new GatewayPidListener();

    }//End the main program

    public boolean ListGrabber()
				
<dp n="d19"/>
    {

    try

    {

    BufferedReader listInput = new BufferedReader(new
FileReader(ListFile));

    String dummy =
listInput.readLine(); //System.out.printIn(dummy);

    if(dummy.equals(“***GateWay List Path***”))

    {

    int counter = 0;

    while((dummy=listInput. readLine())!=null)

       {

        if (debug)

         System.out.printIn("ADDED to
serverARRAY["+serverAmount+"]: "+dummy);

        serverArray. addElement(dummy);

        serVerAmount++;

    }//End while

    }//End if dummy

      } catch (Exception e) {

      System.err.printIn("Error in loadList(): "+e);

      return false;

    }

    return true;

    }//end ListGrabber

    public void CreateOutput()

    {

       try

       {

       PrintWriter FOut＝new PrintWriter(new FileWriter
(outputFile));

       FOut.printIn("PID_INFO FILE==DO NOT MODIFY");
				
<dp n="d20"/>
         // Open each ptlist.txt to determine PIDS

         for(int i=0; i<serverAmount; i++)

         {

try

{

File temp = new File((String) serverArray. elementAt(i));

BufferedReader Fin = new
BufferedReader(new FileReader(temp));

String dummy;

for(int j=0; j<9; j++)//jump to pids

dummy = Fin. readLine();

while((dummy=Fin.readLine())!=null)

{

if(!dummy.equals("[End List]"))

{

if(debug)

System.out.printIn(dummy);

//Parse out the pid

int pos1=0; int pos2=0;

String thepid="";

pos1 = dummy. indexOf("1");

if(pos1>=0)

thepid

dummy. substring(pos1+1, dummy. length());

pos2 = thepid.indexOf("|");

if(pos2>=0)

thepid =
thepid.substring(0, pos2);

if(debug)

System.out.printIn("PID: "+thepid
				
<dp n="d21"/>
);

                         // output to file

               FOut.printIn((String)serverArray.elementAt
(i)+"="+thepid);

               }//End if Idummy

             }//End while

            }catch(Exception e){

            System.err.printIn("Error in read ptlist: "+e);

        }

    }//End for i

    FOut. close();

    }catch(Exception e){

    System.err.printIn(“Could not open the output file for
writing: "+e);

    }//end catch

    }//end ExamineList

    }//end GatewayPidListener

        

Certain exemplary embodiments of a system for accessing patient information include the following instructions for locating a server:

C:

Inetpub

wwwRoot

WinViewFrontEnd

WVBootAgent.asp

checkPID.asp

C:

SecureFiles

WinViewFE

GatewayList.txt

pid_info.inf

GatewayPidListener.bat

GatewayPidLiStener.java

GatewayPidListener.class

Certain exemplary embodiments of a system for accessing patient information include automatically launching a GatewayPidListener on a gateway server. Locate GatewayPidListener_auto.bat on a gateway's C: drive. Contents of this file:

cd c:\securefiles\winviewfe

GatewayPidListener.bat

Then enter the following information into the Autoexec.bat file on the server (accessed using the Sysedit command from the Start->Run command line):

c:\GatewayPidListener_auto.bat

If for some reason a process is not running as verified by checking the process in the task management operation, then the user can access either the GatewayPidListener_auto.bat file in the c: drive or the GatewayPidListener.bat file in securefiles\winviewfe. This can also be done by placing the GatewayPidListener_auto.bat file in the Startup folder. This causes the process to start automatically when the server starts.

Certain exemplary embodiments of a system for accessing patient information include a user interface and process that enable a thin-client vital viewer to be launched from a clinical access application via a web-based URL link. The system accepts the patient ID and automatically launches the correct vital monitor from the host gateway server located within the hospital's clinical information system and presents the patient's results (if on the monitor) via the web via its own web window out. Although the Vital Viewer itself does not assist in doing this on its own, the system has the ability to automatically (without being specified by the clinical access application) check against multiple existing servers to provide the correct patient's vital waveform to the user . A system of methods of accomplishing this task involves a polling process that retrieves a list of active patients on each existing server vital monitor and creates a master list that is retrieved by a network-based viewer for Determine in near real-time whether a patient is on a vital monitor. If the patient is found in the server's associated database, the patient's vitals viewer is activated and presented to the user as a web page where the user observes near real-time vital information results. This method is shown to the user if the patient ID is replicated on multiple servers. If no equivalent patient identifier is found, the message is displayed to the user.

The current server product group provides thin client web viewers for patient vital data. In order to display a particular patient's vital parameters via the thin client network viewer, a user ID, user password, name of the particular server on which the patient resides, and a patient identifier must be specified. However, knowledge of a specific server is typically not available to health information system users because this information is generally maintained in the clinical environment at the point of care. The system for accessing patient information removes user knowledge and Specify the need for a specific gateway server.

A system for accessing patient information can advantageously provide for enabling a thin client web-based vital viewer provided by a gateway server set of products without having to specify in advance the patient's location on a particular gateway server. In an alternative exemplary embodiment, a specific server identifier is encoded into a URL call to the thin client web viewer. The system can be used by other applications that require specific knowledge of the location of an entity within the enterprise (that is, to locate a particular patient within the clinical area of a particular hospital).

Other embodiments will be apparent to those of ordinary skill in the art from reading the foregoing detailed description and the accompanying drawings of certain exemplary embodiments.

Claims (12)

1, a kind of for the system in the network accessing patient medical information that comprises a plurality of servers, it comprises:

Storage vault, described storage vault comprise patient's identifier and are used for identifying the identifier server that is associated of the particular server of the medical information of storing specific patient;

Search processor is used for starting in response to the order that receives the search of described storage vault, to locate the particular server identifier that is associated with described specific patient's identifier; With

Interface processor, for generation of the URL address that described oriented particular server identifier is combined in the data field, and be used in response to the request of user command initiated access in the specific patient's of the described storage at the place, URL address of the described generation of being managed on behalf of another by described particular server medical information.

2, system according to claim 1, wherein

Described storage vault comprises the described patient's identifier of link and is used for identifying the mapping of the described identifier server that is associated of the server of the medical information of managing on behalf of another specific patient.

3, system according to claim 1, wherein

Described interface processor produces described URL address by described specific patient's identifier is combined in the data field.

4, system according to claim 1, wherein

Described search processor is judged at least one in the following situation: (a) described storage vault whether contain a plurality of described specific patient's identifiers and (b) described storage vault whether do not contain the identifier that is complementary with described particular server identifier,

In response to described judgement, described interface processor start sign (a) and (b) at least one message generation and

The described specific patient's of described storage the request of medical information is accessed in the judgement of at least one in response to (a) and (b), described interface processor No starting.

5, system according to claim 1 also comprises

Acquisition Processor is used for inquiring about a plurality of different servers, with the data of editor's indication patient's identifier and the identifier server that is associated be stored in the described storage vault and

Described Acquisition Processor is inquired about described a plurality of different server periodically in response to the record that identifies described a plurality of different servers.

6, system according to claim 1 also comprises

Video-stream processor, be used for to start the described access of representative the described specific patient who stores medical information data generation and

The described specific patient's who stores of described access medical information comprises with lower at least one: (a) blood pressure parameter, (b) ventilation parameter, (c) vital signs parameter, (d) represent infusion pump parameter, (f) drop medicine that parameter, (e) and the feeding of blood oxygen concentration be associated relevant parameter, (g) parameter of vim and vigour and (h) relate to the interactive financial information of described specific patient and health institution.

7, system according to claim 1 also comprises

Licenses Processor, be used for being authorized to access the described specific patient's of described storage medical information in response to described user command authentication of users, and be used for forbidding that in response to unsuccessful checking described user accesses the described specific patient's of described storage medical information.

8. system that is used in the network accessing patient medical information of the Internet Protocol compatibility that comprises a plurality of servers, it comprises:

Support is through the executable application program of the user interface accessing patient medical information of internet compatibility;

Search processor is used for starting in response to the user command with described user interface input the search of at least one data source, to find out the particular server identifier that is associated with specific patient's identifier; With

Interface processor is used for:

Generation will be combined in by the described particular server identifier that described search processor finds the URL address in the data field,

The request of the described specific patient's of the described storage that the URL address start access by described generation is managed on behalf of another by described particular server medical information; And

Transmit the medical information of storing of described access, be shown to the user with the user interface that uses described internet compatibility.

9, system according to claim 8, wherein

Described at least one data source comprises with lower at least one: the storage vault and (b) a plurality of different servers that (a) comprise patient's identifier and the identifier server that is associated of the particular server of the medical information that is used for identifying the specific patient of storage.

10. system that is used in the network accessing patient medical information of the Internet Protocol compatibility that comprises a plurality of servers, it comprises:

Support is through the executable application program of the user interface accessing patient medical information of internet compatibility;

Comprise patient's identifier and be used for identifying the storage vault of the identifier server that is associated of particular server of the specific patient's of storage medical information;

Search processor is used for starting in response to the order that receives the search of described storage vault, to locate the particular server identifier that is associated with described specific patient's identifier; With

Interface processor is used for coming initiated access in the request of the specific patient's of the described storage at the place, URL address that obtains in response to described oriented particular server identifier and described specific patient's identifier medical information in response to user command.

11, system according to claim 10 also comprises

Acquisition Processor is used for inquiring about a plurality of different servers with the data of editor's indication patient identifier and the identifier server that is associated, to be stored in the described storage vault.

12. a method that is used in the network accessing patient medical information of the Internet Protocol compatibility that comprises a plurality of servers, described method comprises following action:

User command in response to the input of user's interface starts the search of at least one data source, to find the particular server identifier that is associated with specific patient's identifier;

Generation will be attached to by the described particular server identifier that described search is found the URL address in the URL data field;

Initiated access is in the request of the specific patient's who stores at the place, URL address of the described generation of being managed on behalf of another by described particular server medical information; With

Network by described Internet Protocol compatibility transmits the medical information of storing of described access to be shown on the described user interface.

Images