Patent Application
20100235782
This invention generally relates to systems and methods for transmitting, receiving and displaying data and/or information over wireless communication and data processing devices, and more specifically to a system and method for collecting, uploading, transmitting, receiving, downloading, manipulating, and displaying medical patient data and/or information to a remote device operable by a health care provider.
While physicians and other health care providers currently utilize a large number of products and systems that benefit from advances in wireless communication technology, there are still significant limitations to the information that can be transmitted, received, and displayed over these devices in a practical and efficient manner. There are many limitations that are intrinsic to mobile devices, especially those constraints related to speed, performance, memory, and display size. In addition, because of the critical nature of medical data, it is important that the technology work reliably and efficiently over potentially low speed, low bandwidth, and sometimes intermittent wireless connections.
Efforts have been made in the past to transmit medical information through various telecommunication means to health care professionals for review and analysis.
Some such efforts are outlined in commonly assigned U.S. patent application Ser. No. 11/301,348, filed on Dec. 12, 2005, the disclosure of which is expressly incorporated herein by reference in its entirety for all purposes. Such examples utilize wireless data communication technologies to transmit medical information to health care providers, or to condition data such that it may be useful for remote monitoring purposes.
In one aspect, the present invention provides a method of providing and managing patient data. In some aspects, the method includes providing patient data to a data management system that is in communication with an information system located at a facility, providing the patient data to a remote device that is in communication with the data management system, receiving, in the remote device, ancillary information that is input based on the patient data, providing the ancillary information to the data management system, and providing the ancillary information to the information system from the data management system.
In some aspects, the method further includes providing an interface that is associated with the information system, and displaying the ancillary information on the interface.
In some aspects, the method further includes displaying patient data on the remote device, and associating the ancillary information with particular patient data that is displayed on the remote device.
In some aspects, the method further includes displaying an annotation on the remote device, which annotation having been generated at the facility.
In some aspects, the annotation is generated based on user input into the information system. In some aspects, the annotation is automatically generated by a patient monitoring device that is in communication with the information system.
In some aspects, the method further includes generating a dialog box on a display of the remote device, and inputting the ancillary information into the remote device using the dialog box.
In some aspects, the ancillary information includes at least one of an annotation, a digital image, digital video, audio and an electronic document.
In some aspects, the method further includes processing and formatting the ancillary information using the data management system for subsequent display at the facility.
In other aspects, the invention also provides computer-readable medium encoded with a computer program comprising instructions that, when executed, operate to cause one or more processors to perform one or more of the methods provided herein.
Other aspects of the invention provide system including one or more processors, and a computer-readable medium coupled to the one or more processors having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform one or more of the methods provided herein.
It is appreciated that methods in accordance with the present disclosure can include any combination of the aspects and features described herein. That is to say that methods in accordance with the present disclosure are not limited to the combinations of aspects and features specifically described herein, but also include any combination of the aspects and features provided.
The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
The present disclosure provides a healthcare provider with secure, remote access to patient data. The present disclosure builds on that of commonly assigned U.S. patent application Ser. No. 11/301,348, filed on Dec. 12, 2005, the disclosure of which is expressly incorporated herein by reference in its entirety for all purposes. U.S. patent application Ser. No. 11/301,348 claims the benefit of U.S. Prov. App. No. 60/641,057, filed on Jan. 3, 2005, the disclosure of which is also expressly incorporated herein by reference in its entirety for all purposes. For purposes of the instant description, and by way of non-limiting example, implementations of the present disclosure will be described in the context of patient data corresponding to maternity patients (e.g., obstetric (OB) patient). Implementations of the present disclosure are applicable to any variety of patients and corresponding patient data.
Referring now to
The remote device 12 can include any number of exemplar devices. Such exemplar devices include, but are not limited to, a mobile phone, a smartphone, a personal digital assistant (PDA), a laptop, a tablet personal computer (PC), a desktop PC, and/or combinations thereof. The remote device 12 includes a display 22, a processor 24, memory 26, an input interface 28, and a communication interface 30. The processor 24 can process instructions for execution of implementations of the present disclosure. The instructions can include, but are not limited to, instructions stored in the memory 26 to display graphical information on the display 22. Exemplar displays include, but are not limited to, a thin-film-transistor (TFT) liquid crystal display (LCD), or an organic light emitting diode (OLED) display.
The memory 26 stores information within the remote device 12. In some implementations, the memory 26 can include a volatile memory unit or units, and/or a non-volatile memory unit or units. In other implementations, removable memory can be provided, and can include, but is not limited to, a memory card. Exemplar memory cards can include, but are not limited to, a secure digital (SD) memory card, a mini-SD memory card, a USB stick, and the like.
The input interface 28 can include, but is not limited to, a keyboard, a touchscreen, a mouse, a trackball, a microphone, a touchpad, and/or combinations thereof. In some implementations, an audio codec (not shown) can be provided, which receives audible input from a user or other source through a microphone, and converts the audible input to usable digital information. The audio codec can generate audible sound, such as through a speaker that is provided with the remote device 12. Such sound may include, but is not limited to, sound from voice telephone calls, recorded sound (e.g., voice messages, music files, etc.), and sound generated by applications operating on the remote device 12.
The remote device 12 may communicate wirelessly through the communication interface(s) 14, which can include digital signal processing circuitry. The communication interface(s) 14 may provide communications under various modes or protocols including, but not limited to, GSM voice calls, SMS, EMS or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, and/or GPRS. Such communication may occur, for example, through a radio-frequency transceiver (not shown). Further, the remote device can be capable of short-range communication using features including, but not limited to, Bluetooth and/or WiFi transceivers (not shown).
The remote device 12 communicates with the network 16 through the connectivity interface(s) 14. The connectivity interface(s) 14 can include, but is not limited to, a satellite receiver, cellular network, a Bluetooth system, a Wi-Fi system (e.g., 802.x), a cable modem, a DSL/dial-up interface, and/or a private branch exchange (PBX) system. Each of these connectivity interfaces 14 enables data to be transmitted to/from the network 16. The network 16 can be provided as a local area network (LAN), a wide area network (WAN), a wireless LAN (WLAN), a metropolitan area network (MAN), a personal area network (PAN), the Internet, and/or combinations thereof.
In the exemplar systems of
Each facility 40 includes an associated information system 42, computer interface(s) 44, and patient monitoring device(s) 46. Exemplar information systems can include, but are not limited to, a clinical information system (CIS), and/or a hospital information system (HIS). Each information system 42 can be provided as a server, and supports the acquisition, storage, modification, and distribution of clinical information, such as patient data, throughout the facility 40 and/or facility system 18, 20. Exemplar information systems include, but are not limited to, the Integriti Enterprise Wide CIS, the QS Perinatal CIS, and/or the QS Critical Care CIS, each provided by General Electric (GE), the OBiX Perinatal Data System provided by Clinical Computer Systems, Inc., the IntelliVue Clinical Information Portfolio (ICIP), Critical Care and/or OB TraceVue Perinatal Data System provided by Royal Philips Electronics, the Essentris Perinatal, Acute Care and/or Critical Care systems provided by CliniComp International, Inc., the CALM Perinatal Data System provided by LMS Medical Systems, the Horizon Lab, Medical Imaging, Cardiology, Emergency Care and/or Perinatal Care provided by McKesson Corporation, and/or the NaviCare WatchChild System provided by Hill-Rom. Each information system 42 can communicate with one or more ancillary information systems (not shown) that can include, but are not limited to, a pharmacy management system, a laboratory management system, and/or a radiology management system. Although the exemplar system architecture 10 includes an information system 42 located at each facility 40, it is contemplated that the facilities 40 can communicate with a common information system 42 that is remotely located from either facility 40, or that is located at one of the facilities 40 within the facility system 18, 20.
The computer interface 44 can communicate with the information system 42 to enable access to information that is stored within, and managed by the information system 42. The computer interface 44 can include, but is not limited to, a personal computer (PC) (e.g., desktop, laptop, or tablet). Although a single computer interface 44 is illustrated in the exemplar architectures described herein, it is contemplated that one or more computer interfaces 44 can communicate with the information system 42. Communication between each computer interface 44 and the information system 42 can be achieved via a direct connection, or remotely through a network (not shown) that can include, but is not limited to, a LAN, a WAN, a WLAN, and/or the Internet.
Each patient monitoring device 46 monitors physiological characteristics of a particular patient 50, and generates data signals based thereon. Exemplar patient monitoring devices include, but are not limited to, maternal/fetal heart rate monitors, blood pressure monitors, respiratory monitors, vital signs monitors, electrocardiogram monitors, oximetry and/or anesthesia monitors. Exemplar patient monitoring devices can include, but are not limited to the Corometric Series Monitors, DINAMAP Series Monitors, DASH Series Monitors, and/or Solar Series monitors provided by GE Healthcare, IntelliVue and/or SureSigns Series patient monitors, and/or Avalon Series Fetal Monitors provided by Royal Philips Electronics, and/or Infinity Series patient monitors provided by Draeger Medical. The data signals are communicated to the information system 42, which collects patient data based thereon, and stores the data to a patient profile that is associated with the particular patient. Although a single patient monitoring device 46 is illustrated per each patient 50, it is contemplated that multiple patient monitoring devices 46 can monitor a particular patient 50. The patient monitoring device(s) 46 can communicate with the information system 42 via a direct connection, or remotely through a network (not shown) that can include, but is not limited to, a LAN, a WAN, a WLAN, and/or the Internet.
The patient data is made available for display on the computer device 44. A healthcare provider (e.g., a nurse and/or physician) can augment the patient data by inputting patient information that is also stored to the information system 44. More specifically, the healthcare provider can input patient information corresponding to a particular patient 50, which patient information can be stored to the patient profile. By way of one non-limiting example, a nurse can input nursing notes, which nursing notes can be stored to the patient profile in the information system. As used herein, the term patient information includes any information corresponding to a patient that is input and stored to the information system 42 through the computer interface 44. Patient information is discussed in further detail below.
As discussed above, each information system 42 stores patient data that can be collected from the patient monitoring devices 46, as well as additional patient information, that can include information that is input by a healthcare provider. The information system 46 communicates the patient data and/or the additional patient data to a data management system (DMS) 60. The DMS 60 can be provided as a server, or a virtual server, that runs server software components, and can include data storage including, but not limited to, a database and/or flat files. In the exemplar system architecture of
A DMS 60 corresponding to a particular facility system can be remotely located from any of the facilities 40 of the facility system 18, 20, or can be located at a particular facility 40 of the facility system 18, 20. In the exemplar system architecture of
In the exemplar system architecture of
In the exemplar system architecture of
The exemplar system architecture of
The DMS 60, 60′ synchronizes and transfers data between the remote device 12, or multiple remote devices 12, and the information system 42, or multiple information systems 42. More specifically, the DMS 60, 60′ processes and prepares the patient data and/or patient information for transfer to and presentation on the remote device 12, or multiple remote devices 12, from the information system 42. The DMS 60, 60′ also processes and prepares ancillary information for transfer to and storage in the information system 42 from the remote device 12, or multiple remote devices 12 for potential presentation at a corresponding computer device 44. Exemplar DMSs can include, but are not limited to, the AirStrip Server provided by AirStrip Technologies, LLC, which AirStrip Server includes AirStrip Server Components installed therein.
Referring now to
In the exemplar structure illustrated in
The alert and notification services module 90 sends alerts and/or notifications to the remote device 12, as discussed in further detail below. The observer client services module 92 facilitates communication between client applications, running on the remote device 12, and backend server components that provide access to application data. The observer client services module 92 transmits data through a formatted request, and receives data in a proprietary data format. An exemplar data format includes, but is not limited to, JavaScript Object Notation (JSON), which is a lightweight computer data interchange format that provides a text-based, human-readable format for representing simple data structures and associative arrays, called objects). The global services module 94 communicates with the client running on the remote device 12 and performs registration and client application configuration settings. Client application settings can be customized by the user of the remote device 12, and the facility 40 and/or facility systems 18, 20, for which the remote device 12 is configured to receive data.
The integration services module 82 is responsible for routing requests that are received from the observer client services module 92 to retrieve and package requested data, and to send a corresponding response. More specifically, the integration services module 82 requests data from the adapter services module 84, or from the synchronization database 100 depending on how the particular DMS 60, 60′ is configured. If the DMS 60, 60′ is configured to use a vendor adapter, the request goes directly to the adapter services module 84 to retrieve the data. If the DMS 60, 60′ is configured for synchronization, then the data is retrieved from the synchronization database 100. The synchronization services module 96 communicates with the adapter services module 84 to maintain the synchronization database 100 current using intelligent synchronization.
Intelligent synchronization is synchronization executed based on variable configuration parameters, which enable the possibility of only some of the patient data and/or patient information to be synchronized as opposed to all of the available data being continuously synchronized. By using custom business rule logic to intelligently determine which patient data and/or information should be synchronized, and which patient data and/or information should be synchronized, the DMS 60, 60′ functions more efficiently and can service an increased number of clients and configurations. By way of non-limiting example, prior to a user logging on to the DMS 60, 60′ via the remote device 12, no specific patient data and/or information is synchronized. Instead, only a patient census list and specific data elements corresponding to particular patients 50 are synchronized between the DMS 60, 60′ and the information system(s) 42. Once the user logs on, and selects a particular patient 50 to review, the synchronization services begin synching all of the available patient data and/or information for that particular patient 50. Consequently, subsequent reviews of the particular patient 50 are much faster, because the patient data and/or information has been synchronized.
The adapter services module 84 is the mechanism that retrieves data from the information system 42, through the connectivity mechanism module 76, and that structures the data for the DMS 60, 60′. The data is formatted and rules are applied for the specific DMS 60, 60′, for which the adapter has been written, regardless of whether the data is directly requested for a client through the integration services module 82, or is retrieved through the synchronization services module 96. The configuration module 102 captures configuration settings used by the information system(s) 42. The configuration module 102 can use already existing configuration information so that it does not have to be replicated in the DMS 60, 60′. By way of non-limiting example, all of the patient beds of a particular facility 40, and to which unit(s) they belong are typically stored in the information system(s) 42. The configuration module 102 reduces, or obviates manual effort in entering the configuration information. The configuration module 102 can also prevent problems from occurring when a configuration change is made in the information system(s) 42, but a system administrator forgets to make the change in the DMS 60, 60′.
The authentication module 104 handles the authentication needs of the DMS 60, 60′, which can include, but are not limited to active directory authentication, vendor authentication, device ID restrictions, device phone number restrictions, and any combination thereof. Each facility system 18, 20 and/or facility 40 is configured to authenticate using any combination of such authentication mechanisms. Device ID restriction is the ability for an authentication service to look at a pre-configured list of device ID's, associated with respective remote devices 12, that are authorized to connect to the facility system 18, 20 and/or facility 40, and only authorizes call from software client that originate with that device ID (i.e., from the particular remote device 12). The device phone number restriction restricts access to remote devices 12 that have a phone number that has been pre-configured in the authentication system.
The ADT module 106 enables the use of existing ADT interfaces within the facility system 18, 20 and/or facility 40 to obtain patient admission, discharge and transfer information in order to always know which patient is associated to which bed and/or unit. The patient data module 108 provides all waveform and non-waveform patient data and/or information from the information system(s) 42 to the DMS 60, 60′. The patient data module 108 can also provide all waveform and non-waveform acquired from a data acquisition system such as the AirStrip data collector or an independent data collecting system including but not limited to Capsule Technologies' Data Captor system. This includes, but is not limited to, all nursing charting information as well as any automated means of data collection used by the information system(s) 42.
In the exemplar structure illustrated in
As discussed at the outset, the present disclosure provides a healthcare provider, or user of the remote device 12, with secure, remote access to patient data and/or patient information. As used herein, the term patient data refers to physiological data that can be obtained from the patient monitoring device(s), and/or physiological patient data that is input into the information system 42 by a local healthcare provider (e.g., a nurse, or physician). The term patient information refers to information corresponding to a particular patient that is input into the information system 42 by the local healthcare provider. Exemplar patient information can include, but is not limited to, the patient's name, the name of the doctor(s) assigned to the patient, the nurse(s) assigned to the patient, a facility identification, a patient bed identification, a summary of key patient data, and/or chart annotations. In the exemplar case of a maternity patient, the key patient data can include, but is not limited to, delivery progress information such as cervical exam status, membrane status, gravida, para, epidural status, and/or whether the patient is attempting a vaginal birth after cesarean (VBAC).
The patient data and/or patient information provided to the remotely located user can be provided in real-time data, and/or as historical data and information. The patient data and/or patient information is communicated between the remote device 12 and the DMS 60, 60′ using a secure connection that is established over the network 16. A secure log-in, or sign-on process is provided, which is preferably compliant with the provisions of the Health Insurance Portability and Accountability Act (HIPAA). The secure sign-on authenticates the identity of the user of the remote device 12 based on a unique user ID and password combination. Both the user ID and the password must be correct in order to establish the secure communication between the remote device 12 and the DMS 60, 60′. Implementations of sign-on and authentication processes are described in further detail below.
A census, or patient list is provided to the remote device 12, which captures a variety of the information and/or data described herein that is associated with each of one or more monitored patients 50. Strip charting is also provided, in which patient data and/or information can be presented to the user in graphical form. In the exemplar case of a maternity patient, a fetal strip and maternal contraction information can be provided for a particular patient 50. More specifically, the particular patient 50 is selected from the patient list, and the patient information and/or data is subsequently presented. The presented information and/or data can include a fetal strip and maternal contraction waveform, the patient name, the hospital name, the patient room and/or bed number, and the date and time. The strip charting can provide a real-time view of the patient data, as well as a historical view of the patient data. More specifically, the waveform display can be updated in real-time, such that the user of the remote device 12 observes the patient data as it occurs and/or is recorded. The user can scroll through the waveform display, to view historical patient data, as described in further detail below.
Several navigation features can be provided that enable the user to manipulate a view of the waveform display. In some implementations, the user can zoom in/out of the displayed image. In this manner, the user can view very specific waveform information, and/or other waveform micro-characteristics by zooming in, for example, and/or can view patterns or other waveform macro-characteristics by zooming out, for example. In some implementations, the user can scroll forward or backward through the waveform display. In this manner, the user can view historical patient data.
A patient data display can also be provided. In some implementations, the patient data display can overlay the strip charting described herein. In other implementation, the patient data display can be provided as an overlay, and/or as a separate display. The patient data display can include, but is not limited to, the patient's name, age, fetal gestation, gravida, parity, cervical exam information, and physician name.
Implementations of the present disclosure can be realized on any one of a number of operating systems, or platforms 72 associated with the particular remote device 12. As discussed above with reference to
With particular reference to the facility system icons 126, 128, attributes can be provided. Exemplar attributes can include, but are not limited to, patient counts. A first patient count 130 provides the total number of patients at the facility, for which the particular user is responsible. For example, if the user is a physician, the first patient count 130 illustrates the total number of patients that are under the care of that particular physician. In the exemplar illustration of
The exemplar facility summary display of
The user can navigate from the facility summary display 122 by selecting any one of the icons. An icon can be selected in any one of a number of manners that is supported by the particular platform. By way of non-limiting examples, an icon can be selected by touching the screen with a digit (i.e., finger), a stylus, and/or other pointing device, as well as with a digital cursor, and/or a keypad.
By selecting a particular patient from the patient summary display 136, a specific patient summary display 142 is provided.
Referring now to
The exemplar implementations of
Upon selecting the particular strip for display, a request is made from the remote device 12 to the corresponding information system 42 to transmit the patient data and/or information for the particular patient. The patient data and/or information is provided to the remote device 12, with the remote device 12 buffering the patient data and/or information to provide real-time viewing thereof. Basic real-time viewing of the patient data is provided on a background grid with a timing mark shown and patient information being provided. In implementations of the present disclosure, the patient data trace moves from right to left across the display.
In implementations of the present disclosure, provide zoom in and out functionality. In each case, the user can take advantage of viewing a trend (e.g., zoom out), or a specific data segment (e.g., zoom in) to facilitate a judgment with regard to the condition of the patient. Implementations of the present disclosure also provide variable speed scroll functionality of the data strip. More specifically, the user of the remote device 12 can be presented with a bi-directional, multilevel selection bar, and/or virtual controls that regulate the direction and the scrolling speed of the data strip. In this manner, the user can customize viewing of the patient data to personal preferences, or to the specific situations that dictate review of the patient data. For example, the user may quickly scroll through the data strip to a point, at which a particular anomaly occurred, and can more slowly scroll the data strip around that point to study the patient data in further detail.
With particular reference to
As discussed immediately above, the user can view annotations on the waveform (e.g., fetal strip) that are input at the facility 40. Such annotations can include, but are not limited to, nursing notes, for example. In such cases, the annotations can be manual annotations that originate from an attending nurse, who enters the annotation through the information system 42, typically through the computer device 44 (e.g., a PC client). It is also contemplated, that some annotations can be automatically entered by the information system 42. Such annotations can include, but are not limited to, blood pressure and/or heart rate, that are automatically generated by a corresponding patient monitoring device 46.
Implementations of the present disclosure enable the user to annotate the waveform, or strip using the remote device 12. More specifically, the user can input ancillary information that is subsequently transferred from the remote device 12 to the information system 42 through the DMS 60, 60′. Such ancillary information can include, but is not limited to, annotations (e.g., user notes), digital images (e.g., x-rays, photographs, drawings, sketches), digital video, audio and/or electronic documents. The ancillary information is processed and formatted through the DMS 60, 60′ for subsequent display at the facility 40. More specifically, the ancillary information generated on the remote device 12 can be stored to the information system 42 for subsequent display on the computer interface 44. In this manner, the remotely located user can provide feedback, and/or any other necessary information to local healthcare provider.
By way of one non-limiting example, the user can record a voice note using a microphone of the remote device 12, which voice note is stored in memory of the remote device 12. The voice note can be communicated from the remote device 12 to the information system 42 for subsequent access to the voice note at a particular facility 40 or facilities 40. By way of another non-limiting example, the user can record a video that can include an associated audio component, using a video camera and microphone of the remote device 12, which video is stored in memory of the remote device 12. The video can be communicated from the remote device 12 to the information system 42 for subsequent access to the video at a particular facility 40 or facilities 40. By way of still another non-limiting example, the user can generate an image, such as a photograph, using a camera of the remote device 12, which image is stored in memory of the remote device 12. The image can be communicated from the remote device 12 to the information system 42 for subsequent access to the image at a particular facility 40 or facilities 40.
In some implementations, the user can initiate the opening of a dialog box within the display of the remote device 12. The dialog box can provide the user with options for inputting ancillary information, and to associate, or link such ancillary information to a particular patient data point, or segment on the waveform. For example, the dialog box can enable the user to type in notes, choose from a list of pre configured commonly used annotation choices, and/or upload digital images (e.g., x-rays, photographs, drawings, sketches), digital video, audio and/or electronic documents.
With particular reference to
The alert can be indicated to the user of the local device 12 in any number of available manners. For example, a visual indication can be presented on the display, an audible indication can issue from the remote device 12, and/or the remote device 12 can be induced to vibrate. The relative importance of the alert can be set by the user, and can be reflected by the type of indication. By way of non-limiting example, a very important alert can be visually, audibly, and physically (e.g., vibration) indicated. An alert of less importance may only include a visual indication, for example.
In some implementations, the alert(s) can be configured by the user at the remote device 12, and can be registered with the DMS 60, 60′ through the alert rules engine module 98 in the integration services module 82 (see
The alert functionality also enables the user to configure and customize constraints around available alerts such that they are tailored to that user's needs. Some of such alerts can originate from the information system 42, and others can originate from the DMS 60, 60′, which is collecting and monitoring the patient data from the information system 42.
Exemplar patient alerts can include, but are not limited to, a new patient alert, a patient status alert, a patient discharge alert, and/or a request alert. The new patient alert can include an alert that notifies the user of a new patient that they have been assigned to his/her care. In some implementations, a user name can be input as part of the patient information that is input at the facility 40, when the new patient is admitted to the facility. For example, the user could be a physician that has been assigned to the patient. If input user name matches, or is similar to the name of the user of a particular remote device 12, an alert is generated on that remote device 12 notifying the user the he/she may have been assigned a new patient. Other constraints could be applied in such cases. By way of one non-limiting example, the alert may only be generated at the remote device 12, if the new patient is a VBAC patient. In another example, the patient's name could be compared to a list of “VIP” patients that has been pre-defined by a particular user. In such cases, the new patient alert will be generated, and the user will be notified if the new patient is on that user's list of “VIP” patients. In this manner, the user will still be notified that the particular patient has been admitted, even though that particular user may not have been assigned as the primary caretaker for that particular patient. For example, even if an attending nurse at the facility 40 entered another user as the primary physician, the user would still be notified that there is a potential VIP patient that has been admitted to a particular facility. In this manner, the user, as a non-primary physician, could still track that particular patient's progress. Such functionality could enable the administrator of the DMS 60, 60′ to coordinate electronic medical records to programmatically feed a particular physician's or physician group's patient names and/or identifiers.
A patient status alert can be generated to notify the user of the remote device to a particular patient condition. By way of non-limiting example, an alert can be generated to notify the user to a change in dilatation, or any parameters associated with a vaginal exam, such as in the exemplar context of a maternity patient. Such alerts could be constrained to only alert the user if the particular patient is listed on the user's “VIP” list, and/or if the particular patient is listed in the user's “My Patients” list (e.g., a list of patients to which the particular user has been assigned as the primary physician. Such alerts could be alternatively constrained, or be further constrained by a particular value. For example, if the particular patient's dilation exceeds a threshold (e.g., 8 centimeters).
Other exemplar patient status alerts can include, but are not limited to, a change in the particular patient's membrane condition (e.g., ruptured), a notification that a particular patient has been administered an epidural, and/or a notification that a particular patient had delivered, or was scheduled for C-section, in the exemplar context of a maternity patient. Such alerts could be constrained to only alert the user if the particular patient is listed on the user's “VIP” list, and/or if the particular patient is listed in the user's “My Patients” list.
By way of another non-limiting example, the user may want to be alerted when a particular patient's dilation progresses past a particular threshold (e.g., 7 centimeters). The user may also configure additional constraints such that, if the particular alert is triggered, the user is made aware of it's relative importance. In this example, the user can configure a rule using the remote device 12, which rule will generate an alert notification if particular patient is included on the user's patient list, if the patient's dilation is greater than or equal to the threshold, if the patient has had an epidural, and if the “My Alerts” option is turned on. In the event that each of these conditions is true, the user is presented with an alert at the remote device 12, such as the alert illustrated in
Still other exemplar patient status alerts can include, but are not limited to, a periodic status alerts for each patient that is listed in the particular user's “VIP” list, and/or “My Patients” list. Such periodic status alerts can be constrained to a definable time interval (e.g., every minute, every X minutes, where X is greater than one, every hour, every Y hours, where Y is greater than one, every day, every week, every month, and so on). Such a periodic status alert could notify the user to pertinent patient data and/or information without requiring data and/or information to be retrieved, or without requiring the user to drill down. In order to ensure privacy of the patient data, the user would be required to enter a password and/or PIN, before the pertinent patient data and/or information was presented on the display of the remote device 12.
A patient discharge alert could notify the user that a particular patient is to be discharged from the facility 40. Such an alert could further notify the user of action required by the user to complete such a patient discharge. For example, the patient discharge alert could notify the user is required to sign patient discharge papers. A request alert could notify the user of a request from a caretaker that is on-site (e.g., is at the facility 40), such as a nurse or physician. Such requests could include, but are not limited to, a request that the user review specified patient data and/or information for a particular patient, and could include a message from the on-site caretaker. Such alerts could be clickable to link the user directly to the relevant patient data and/or information (e.g., automatically display the relevant portion of a strip). Again, such alerts could be constrained to only alert the user if the particular patient is listed on the user's “VIP” list, and/or if the particular patient is listed in the user's “My Patients” list.
A system alert could notify the user to certain system conditions. For example, the system alert could notify the user that a particular information system 42, and/or a particular DMS 60, 60′ will be unable, or inaccessible, for a specified reason (e.g., routine maintenance). This may be particularly relevant to the user, if the particular user is on call. Such system alerts could also notify the user of other system disruptions, such as with a particular DMS 60, 60′, a particular information system 42, a particular facility 40, and/or a particular facility system 18, 20.
As discussed above, the user is initially authenticated based on a user ID and password. In some implementations, the user may be required to input a user ID and password for each DMS they are seeking to communicate with. In the exemplar system of
Referring now to
When the user subsequently initiates communication with the information system(s) 42 through the DMS 60, 60′, the user is prompted to input their universal user ID and password combination. The DMS 60, 60′ authenticates the universal user ID and password combination 600 and enables the user to access the DMS 60, 60′. In turn, each information system 42 authenticates the user based on corresponding local user ID and password combinations 602 provided by the DMS 60, 60′. More specifically, the DMS 60, 60′ retrieves multiple local user ID and password combinations 602 based on the universal user ID and password combination 600. In the exemplar illustration of
Referring now to
In implementations of the method of
Referring now to
In implementations of the method of
Referring now to
In implementations of the method of
Referring now to
In implementations of the method of
In some implementation of the method of
The present disclosure can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof. The invention can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network. Such a computer program can include modules and/or code segments for executing one or more of the features, aspects and/or implementations provided herein.
Method steps of the present disclosure can be performed by one or more programmable processors executing a computer program product to perform functions of the present disclosure by operating on input data and generating output. By way of one non-limiting example, a computer program product can include modules and/or code segments corresponding to each of the method steps, aspects and/or features provided herein. Method steps can also be performed by, and apparatus of the present disclosure can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
The present disclosure can be implemented in a system including, but not limited to the exemplar systems described herein, which include a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client device, such as the remote device 12, having a graphical user interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network.
A number of embodiments have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. For example, steps of the invention can be performed in a different order and still achieve desirable results. Accordingly, other embodiments are within the scope of the following claims.
This application claims priority to U.S. Provisional Application No. 61/159,138, filed on Mar. 11, 2009, the disclosure of which is expressly incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61159138 | Mar 2009 | US |
