US20210150478A1 - Systems and methods for and displaying patient data - Google Patents

Abstract

Implementations are directed to providing a user of a mobile device access to patient information and patient physiological data. Actions can include receiving user input, the user input indicating a user command to display a task screen, in response to the user input, processing user-specific data to determine one or more patient icons, each patient icon representing a time-sensitive, patient-associated task, and displaying the task screen on the mobile device, the task screen displaying one or more patient icon groups, each patient icon group including a patient icon of the one or more patient icons.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• This application is a continuation of U.S. patent application Ser. No. 16/384,351 filed on Apr. 19, 2019, which is a continuation of U.S. patent application Ser. No. 14/193,246 filed on Feb. 28, 2014, now U.S. Pat. No. 10,262,382, which claims the benefit of and priority to U.S. Provisional Application No. 61/788,233 filed on Mar. 15, 2013, the disclosure of which are expressly incorporated herein by reference in their entirety.
BACKGROUND
• Patient information can be stored across multiple facilities associated with respective health care providers. For example, healthcare continua can include hospitals, clinics, laboratories, and/or other healthcare facilities. In some instances, each healthcare facility had its own data source for storing patient information and data associated with services provided at the respective facility. For example, multiple, different electronic medical records (EMRs) can be provided for a particular patient across a healthcare continuum. In some examples, such EMRs are vendor-specific, storing data and information is disparate formats.
• Physicians and other healthcare providers may be required to access patient data and information from across a healthcare continuum. The disparate nature, in which data and information may be stored, can complicate retrieval and display of relevant patient information to healthcare providers.
SUMMARY
• Implementations of the present disclosure provide methods for providing a user of a mobile device access to patient information and patient physiological data. In some examples, methods include actions of receiving user input, the user input indicating a user command to display a task screen, in response to the user input, processing user-specific data to determine one or more patient icons, each patient icon representing a time-sensitive, patient-associated task, and displaying the task screen on the mobile device, the task screen displaying one or more patient icon groups, each patient icon group including a patient icon of the one or more patient icons. Other implementations of this aspect include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.
• These and other implementations can each optionally include one or more of the following features: the time-sensitive, patient-associated task of each patient icon includes a pending task; actions further include, in response to user selection of a patient icon, displaying a task-specific screen, the task-specific screen including patient data and/or patient information associated with an underlying task; actions further include receiving user input indicating completion of the time-sensitive, patient-associated task of a patient icon, and in response, providing a signal to a back-end system indicating completion of the time-sensitive, patient-associated task; actions further include removing the patient icon from display in the task screen; actions further include each time-sensitive, patient-associated task is determined to be within a threshold time period; and a time-sensitive, patient-associated task is determined to be within the threshold time period when a difference between a current time and a time associated with the task is within the threshold time period.
• Other aspects of the present disclosure provide systems 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 implementations 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.
DESCRIPTION OF DRAWINGS
• The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee.
• FIG. 1 is a schematic illustration of an example system architecture in accordance with implementations of the present disclosure.
• FIG. 2 is a schematic illustration of another example system architecture in accordance with implementations of the present disclosure.
• FIG. 3 is a functional block diagram of an example system in accordance with implementations of the present disclosure.
• FIG. 4 is a more detailed view of the functional block diagram ofFIG. 3.
• FIG. 5 depicts an example platform for providing integrated and unified views of patient data and patient information.
• FIG. 6 depicts example components and sub-components that can be included in core components ofFIG. 5.
• FIGS. 7-10 depict example graphical user interfaces (GUIs) for providing integrated and unified views of patient data and patient information in accordance with implementations of the present disclosure.
• FIG. 11 is a flowchart illustrating an example process that can be executed in accordance with implementations of the present disclosure.
• Like reference symbols in the various drawings indicate like elements.
DETAILED DESCRIPTION
• Implementations of the present disclosure are generally directed to an enterprise scalable, data- and vendor-agnostic mobility architecture to securely deliver patient data and information from medical devices, electronic medical records (EMRs) and patient monitors to healthcare providers anywhere across a healthcare continuum. More particularly, implementations of the present disclosure provide integrated and unified views of patient data and patient information on mobile devices (e.g., smartphones, tablets) from a plurality of data sources across the healthcare continuum. As discussed in further detail herein, implementations of the present disclosure enable timely and collaborative clinical decision-making, and enable healthcare systems to better track quality metrics, empower a mobile workforce, expand networks, and achieve clinical transformation.
• Example systems and methods that can be included in implementations of the present disclosure are provided in U.S. Provisional Application Ser. No. 61/771,591, filed Mar. 1, 2013, the contents of which are expressly incorporated herein by reference in the entirety.
• Referring now toFIG. 1, anexample system architecture100 is illustrated, and includes amobile device102, connectivity interface(s)104, anetwork106, afirst facility system108, and asecond facility system110. As discussed in further detail herein, data is transferred from each of the first andsecond facility systems108,110 through thenetwork106 and connectivity interface(s)104 for presentation, or display on themobile device102. Further, data can be transferred from themobile device102 through the connectivity interface(s)104 and thenetwork106 to each of the first andsecond facility systems108,110. Although a singlemobile device102 is illustrated, it is contemplated that one or moremobile devices102 can communicate with each of the first andsecond facility systems108,110 through thenetwork106 and the connectivity interface(s)104. Similarly, although two facility systems are illustrated, implementations of the present disclosure can include one or more facility systems.
• Themobile device102 can include any number of example devices. Such example devices include, but are not limited to, a mobile phone, a smartphone, a tablet computing device, a personal digital assistant (PDA), a laptop personal computer (PC), a desktop PC, and/or appropriate combinations thereof. In the depicted example, themobile device102 includes adisplay122, aprocessor124,memory126, aninput interface128, and acommunication interface130. Theprocessor124 can process instructions for execution of implementations of the present disclosure. The instructions can include, but are not limited to, instructions stored in thememory126 to display graphical information on thedisplay122. Example displays include, but are not limited to, a thin-film-transistor (TFT) liquid crystal display (LCD), or an organic light emitting diode (OLED) display. Thememory126 stores information within themobile device102. In some implementations, thememory126 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. Example 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.
• In some examples, theinput interface128 can include a keyboard, a touchscreen, a mouse, a trackball, a microphone, a touchpad, and/or appropriate 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 themobile device102. Example sounds can include sound from voice telephone calls, recorded sound (e.g., voice messages, music files, etc.), and/or sound generated by applications operating on themobile device102.
• Themobile device102 may communicate wirelessly through the communication interface(s)104, which can include digital signal processing circuitry. The communication interface(s)104 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 mobile device can be capable of short-range communication using features including, but not limited to, Bluetooth and/or WiFi transceivers (not shown).
• Themobile device102 communicates with thenetwork106 through the connectivity interface(s)104. In some examples, the connectivity interface(s)104 can include a satellite receiver, cellular network, a Bluetooth system, a Wi-Fi system (e.g., 802.x), a cable modem, a DSL/dial-up interface, a private branch exchange (PBX) system, and/or appropriate combinations thereof. Each of these connectivity interfaces104 enables data to be transmitted to/from thenetwork106. In some examples, thenetwork106 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 example systems ofFIGS. 1 and 2, thefirst facility system108 includes a plurality offacilities140, and thesecond facility system110 includes afacility140. It is contemplated that eachfacility system108,110 can include one or more facilities, and is not limited to the example arrangement described herein. In the case of multiple facilities, the facilities can be remotely located from one another, and/or can be located at a common location, or site (e.g., separate departments in a common (the same) building). Eachfacility system108,110 can be provided as a medical care system, for example, which medical care system can include one or more hospitals, hospital systems, clinics, physician offices, and the like.
• In some examples, eachfacility140 includes an associatedinformation system142, computer interface(s)144, and patient monitoring device(s)146. Example information systems can include, but are not limited to, a clinical information system (CIS), an EMR system, an electronic health record (EHR) system, and/or a hospital information system (HIS). Eachinformation system142 can be provided as a server, and supports the acquisition, storage, modification, and distribution of clinical information, such as patient data, throughout thefacility140 and/orfacility system108,110. In some examples, eachinformation system142 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 theexample system architecture100 includes aninformation system142 located at eachfacility140, it is contemplated that thefacilities140 can communicate with acommon information system142 that is remotely located from eitherfacility140, or that is located at one of thefacilities140 within thefacility system108,110.
• In some examples, thecomputer interface144 can communicate with theinformation system142 to enable access to information that is stored within, and managed by theinformation system142. In some examples, thecomputer interface144 can include a personal computer (PC) (e.g., desktop, laptop, or tablet). Although asingle computer interface144 is illustrated in the example architectures described herein, it is contemplated that one ormore computer interfaces144 can communicate with theinformation system142. Communication between eachcomputer interface144 and theinformation system142 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.
• In some examples, eachpatient monitoring device146 monitors physiological characteristics of aparticular patient150, and generates data signals based thereon. As discussed in further detail herein, implementations of the present disclosure provide patient monitoring devices that include a computing device, such as a tablet computing device. The data signals are communicated to theinformation system142, which collects patient data based thereon, and stores the data to a patient record that is associated with the particular patient. An example patient record can include an electronic medical record (EMR). Although a singlepatient monitoring device146 is illustrated per eachpatient150, it is contemplated that multiplepatient monitoring devices146 can monitor aparticular patient150. The patient monitoring device(s)146 can communicate with theinformation system142 via a direct connection, or remotely through a network (not shown) that can include, for example, a LAN, a WAN, a WLAN, and/or the Internet.
• In some examples, the patient data is made available for display on thecomputer device144. A healthcare provider (e.g., a nurse and/or physician) can augment the patient data by inputting patient information that is also stored to theinformation system144. More specifically, the healthcare provider can input patient information corresponding to aparticular patient150, which patient information can be stored to the patient record (e.g., EMR). As one example, a nurse can input nursing notes, which nursing notes can be stored to the patient record in the information system. Example patient information can include any non-physiological information corresponding to a patient (e.g., name, age, date-of-birth (DOB), gender).
• As discussed above, eachinformation system142 stores patient data that can be collected from thepatient monitoring devices146, as well as additional patient information, that can include information that is input by a healthcare provider. Theinformation system144 communicates the patient data and/or the additional patient data to a data management system (DMS)160. TheDMS160 can be provided as a server, or a virtual server, that runs server software components, and can include data storage including, for example, a database and/or flat files. In theexample system architecture100 ofFIG. 1, eachfacility system108,110 includes acorresponding DMS160. In such an arrangement, eachinformation system142 communicates patient data, and/or additional patient data to theDMS160. Furthermore, and as discussed in further detail below, theDMS160 can communicate ancillary information to theinformation system142. Communication between theDMS160 and the information system(s)142 can be achieved via a direct connection, or remotely through a network (not shown) that can include, for example, a LAN, a WAN, a WLAN, and/or the Internet.
• In some examples, aDMS160 corresponding to a particular facility system can be remotely located from any of thefacilities140 of thefacility system108,110, or can be located at aparticular facility140 of thefacility system108,110. In theexample system architecture100 ofFIG. 1, theDMS160 is remotely located from eitherfacility140 within each of thefacility systems108,110. It is contemplated, however, that theDMS160 can be located at one of thefacilities140, and remote from theother facility140.
• In theexample system architecture100′ ofFIG. 2, aDMS160′ is provided that is common to (the same for) thefacility systems108,110. For example, theDMS160′ can be described as being common tovarious facility systems108,110, and is not associated with aparticular facility system108,110. For example, theDMS160′ can be hosted by a third-party vendor (e.g., a cloud service provider). In some examples, each information system42 communicates with theDMS160′ 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. In the example arrangement ofFIG. 2, theDMS160′ communicates with each of theinformation systems142 through thenetwork106. Theinformation systems142 communicate patient data and/or patient information to theDMS160′, and theDMS160′ can communicate ancillary information to theinformation system142, as discussed in further detail below.
• In theexample system architecture100 ofFIG. 1, thefacility140, orfacility system108,110 installs theDMS160 as a local DMS, and theDMS160 sits at the local site with other servers that can include, for example, theinformation system142. In some implementations, theDMS160 can be sectioned off, or separated from a logical network perspective, but still physically exists with the other servers that belong to therespective facility140. In some examples, server components are installed on theDMS160, which components can include, for example, a database component, a database synchronization component, a web services component, and/or a structured query language (SQL) component. An information system interface can also be installed on theDMS160, and functions as the interface to theinformation system142. As one example, the information system interface can include OBLink, provided by GE Healthcare. In some implementations, theDMS160 can be arranged in a multiple server configuration, in which one server only hosts web service related components and is logically segregated, and another server has the remaining necessary server components installed.
• Theexample system architecture100′ ofFIG. 2, provides for the remote location of data collection at theDMS160′. In such implementations, theDMS160′ can be provided at a third-party site, remote from any of thefacilities140, orfacility systems108,110. The third-party functions as a DMS host, and the necessary server components are installed on the remotely hostedDMS160′. In some implementations, a business-to-business (B2B) virtual private network (VPN) can be created between the remotely hostedDMS160′ and the network of thefacility140 orfacility system108,110. In this manner, thefacility140 and/orfacility system108,110 forgoes the purchase and/or maintenance of another physical server, orDMS160. Further, the up-time and the status of availability of theDMS160′ are easier to manage on the part of a dedicated third-party. The DMS' access to the network can be attended to by the third-party, as opposed to burdening thefacility140, or thefacility systems108,110. Further, the third-party can implement virtual server technologies to leverage multiple DMS installations on a single physical server. In such implementations, a plurality of virtual servers are logically partitioned in a single physical server, and each virtual server has the capability of running its own operating system and server components, and can be independently booted.
• In accordance with implementations of the present disclosure, theDMS160,160′ synchronizes and transfers data between themobile device102, or multiplemobile devices102, and theinformation system142, ormultiple information systems142. More specifically, theDMS160,160′ processes and prepares the patient data and/or patient information for transfer to and presentation on themobile device102, or multiplemobile devices102, from theinformation system142, and/or other systems, as discussed in further detail herein. TheDMS160,160′ also processes and prepares ancillary information for transfer to and storage in theinformation system142 from themobile device102, or multiplemobile devices102 for potential presentation at acorresponding computer device144. Example 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 toFIGS. 3 and 4, example module structure, orsystem300 that can be implemented to provide features of the present disclosure will be described in detail. In some examples, theexample system300 enables patient data and patient information to be communicated to/from, and to be exchanged between mobile devices and data sources across healthcare continua. In some examples, each module can be provided as one or more computer-executable programs that are executed using one or more computing devices (e.g., computing devices provided as part of a DMS, computing devices located at one or more facilities of a facility system).
• FIG. 3 illustrates an overview of theexample system300. In the depicted example, the module structure includes modules located at aDMS301, afirst facility system302 and asecond facility system304. In some examples, thefirst facility system302 and thesecond facility304 can be included in at least a portion of a healthcare continuum, discussed in further detail herein. Thefacility system302 includes a patient record module303 (e.g., EMR module) that accesses one or more patient records managed and stored by thefacility system302. Thefacility system304 includes a patient record module305 (e.g., EMR module) that accesses one or more patient records managed and stored by thefacility system304.
• In the depicted example, and as discussed in further detail herein, patient data and/or information can be provided for integrated and unified display on themobile device102 through thenetwork106 and theDMS301 from across healthcare continua (e.g., thefacility systems302,304). In some examples, patient data and/or information can be provided for display on amobile device102′,102″ through thenetwork106 from a facility system (e.g., thefacility system302,304). In some examples, themobile devices102,102′,102″ are the same device. That is, for example, a mobile device can receive patient data and/or information from across a healthcare continuum, and/or from individual facility systems.
• In some implementations, theDMS301 includes aweb module310, ahost module312, adata cache module314 and anadapter module316,web module320, ahost module322, adata cache module324, acollector module326. In general, modules of theDMS301 enable theDMS301 to retrieve and combine data from multiple facility systems (e.g., thefacility systems302,304) across healthcare continua. In some examples, theweb module310 provides a first-level network facing interface to the DMS infrastructure. In some examples, and in response to a request from a mobile device (e.g., the mobile device102), theweb module310 performs request validation and user authentication and routes the request to thehost module312. In some examples, theweb module310 includes one or more sub-modules. Example sub-modules include a request validation sub-module, which validates received requests, a user authentication module, which authenticates an identity of the user and/or mobile device from which a request is received, and a request routing sub-module, which routes requests after validation and authentication.
• In some implementations, thehost module312 orchestrates request processing. In some examples, thehost module312 includes one or more sub-modules. Example sub-modules include a request parsing sub-module that parses received requests, a pipeline assembly sub-module, a pipeline processing sub-module, an operation execution sub-module, a data access sub-module, a results formatting sub-module, an access control sub-module, an encryption sub-module, a data conditioning sub-module, and a logging sub-module. In some examples, thehost module312 parsers a received request (e.g., using the request parsing sub-module) to determine, for example, what type of device issued the request, which application executing on the device issued the request, and/or patient data/information (or other data such as analytical data, discussed below) is needed to fulfill the request. In some examples, and based on the parsed information, thehost module312 builds a pipeline (e.g., using the pipeline assembly sub-module). In some examples, a pipeline can be provided as a list of tasks that need to be executed to fulfill the request. Example tasks can include retrieving particular patient data/information, processing retrieved patient data to generate additional data and/or data visualizations (e.g., analytical data, trend graphs, discussed below), encrypting/decrypting retrieved data, performing access control to retrieve data, generating logs of tasks.
• In some implementations, thehost module312 coordinates data retrieval with the data cache module314 (e.g., using the data access sub-module). The retrieved data is provided back to thehost module312. In some examples, thehost module312 processes the retrieved data (e.g., using the operation execution sub-module, the results formatting sub-module and/or the data conditioning sub-module). In some examples, the retrieved data is processed to generate additional data (e.g., data used for data visualizations). In some examples, the retrieved data and/or the additional data are conditioned to provide efficient transfer back to the requesting mobile device. In some examples, conditioning can include converting data based on transmission protocol, formatting data for optimal display on the particular device, and/or packaging data to send to the requesting device.
• In some implementations, thedata cache module314 enables access to and optional storage of detailed patient data/information used by other components of thesystem300. In some examples, thedata cache module314 includes one or more sub-modules and/or data stores. An example sub-module can include a cache services sub-module. In some examples, thedata cache module314 can operate in a pass-through mode (real-time mode) and a reposed mode. In some examples, patient data/information required to satisfy a given request can be directly accessed from a source system (e.g., thefacility system302,304) in real-time. In such examples, thedata cache module314 operates in a pass-through mode, retrieving the patient data/information from multiple data sources and passing the patient data/information onward for responding to the request. In some examples, an application program interface (API), or other programmatic mechanism can be used to retrieve the patient data/information. In some examples, in the pass-through mode, patient data/information is not stored in a persistent data store accessed by thedata cache module314. In some implementations, it might be desired to improve retrieval performance. Consequently, thedata cache module314 can store data identifiers and/or pointers in a persistent data store. When in the pass-through mode, thedata cache module314 uses theadapter module316 to perform the actual retrieval of patient data/information from one or more facility systems.
• In some examples, the patient data/information that is required to satisfy a request cannot be directly accessed from the facility systems (e.g., thefacility systems302,304). In such examples, thedata cache module314 operates in the reposed mode. In some examples, in the reposed mode, thedata cache module314 stores a detailed copy of the patient data/information in the persistent data store. That is, for example, stored patient data/information is stored at the DMS-level, but had been retrieved from remote data sources (e.g., data sources located at thefacility systems302,304). In some examples, when a request is made for patient data/information in the reposed mode, the patient data/information is retrieved directly from the persistent data store (e.g., by the cache services sub-module).
• In some implementations, theadapter module316 enables the retrieval of patient data/information from across healthcare continua. Consequently, theadapter module316 can be referred to as a federated adapter module. In some examples, in response to receiving a request from themobile device102 for patient data/information from multiple data sources (e.g., thefacility systems302,304), thedata cache module314 utilizes theadapter module316 to retrieve the requested patient data/information from the multiple data sources. In some examples, theadapter module316 communicates with local host modules (discussed in further detail below) of the respective facility systems.
• In some implementations, the request processing operation of theDMS301 is stateless. More particularly, the modules of theDMS301 handle each received request as a distinct unit and, once a request is handled, stores no state information associated with a completed request. In other words, after theDMS301 has processed a request, the DMS301 (e.g., modules within theDMS302 that handled the request) “forget” that the request even occurred. In this manner, subsequently received requests are not influenced by (e.g., handled based on) previously processed requests.
• In some examples, operation of theDMS301 is stateless, but theDMS301 can still provide a log of requests handled (e.g., using the logging sub-module). For example, a request log can be accessed during an audit of thesystem300.
• In some implementations, eachfacility system302,304 includes one or morelocal web modules320,330, one or morelocal host modules322,332, one or more localdata cache modules324,334, and one or morevocabulary service modules328,338. In the depicted example, thefacility system302 includes one ormore collector modules326, and thefacility system304 includes one or more patient record (EMR)adapter modules336.
• In some examples, each of theweb modules320,330 provides functionality as similarly discussed above with respect to theweb module310. More particularly, theweb modules320,330 operate at a local level (e.g., local to therespective facility systems302,304), each performing request validation and user authentication, and routing requests to the respectivelocal host modules322,332. For example, theweb modules320,330 can receive requests from the respectivemobile devices102′,102″, can validate the requests and authenticate the respective users/mobile devices, and route the requests accordingly. In some examples, eachweb module320,330 includes one or more sub-modules. Example sub-modules include a request validation sub-module, which validates received requests, a user authentication module, which authenticates an identity of the user and/or mobile device from which a request is received, and a request routing sub-module, which routes requests after validation and authentication.
• In some examples, each of thelocal host modules322,332 provides functionality as similarly discussed above with respect to thehost module312. More particularly, thelocal host modules322,332 operate at a local level (e.g., local to therespective facility systems302,304), each orchestrating request processing. In some examples, thelocal host modules322,332 orchestrate request processing for requests received from themobile device102 through theDMS301, and/or from the respectivemobile devices102′,102″ through the respectivelocal web modules320,330. In some examples, eachlocal host module322,332 includes one or more sub-modules. Example sub-modules include a request parsing sub-module that parses received requests, a pipeline assembly sub-module, a pipeline processing sub-module, an operation execution sub-module, a data access sub-module, an access control sub-module and an encryption sub-module.
• In some examples, each of the localdata cache modules324,334 provides functionality as similarly discussed above with respect to thedata cache module314. More particularly, the localdata cache modules324,334 operate at a local level (e.g., local to therespective facility systems302,304), each enabling access to and optional storage of detailed patient data/information used by other components of thesystem300. In some examples, the eachdata cache module324,334 can operate in a pass-through mode and a reposed mode, as discussed above with respect to thedata cache module314. In the pass-through mode, the localdata cache modules324,334 retrieve the patient data/information from one or more local data sources and passed the patient data/information onward for responding to the request. In some examples, it might be desired to improve retrieval performance. Consequently, the localdata cache modules324,334 can store data identifiers and/or pointers in a persistent data store. When in the pass-through mode, the localdata cache modules324,334 use thecollector module326 and the patientrecord adapter module336, respectively, to perform the actual retrieval of patient data/information from local data source(s) (e.g., thepatient record module303 and thepatient record module305, respectively). In some examples, when in the pass-through mode, the localdata cache modules324,334 can write data back to the respectivepatient record modules303,305.
• In some examples, the patient data/information that is required to satisfy a request (e.g., from themobile device102′,102″) cannot be directly accessed from the local data sources (e.g., thepatient record modules303,305). In such examples, each localdata cache module324,334 can operate in the reposed mode. In some examples, in the reposed mode, the localdata cache module324,334 stores a detailed copy of the patient data/information in the persistent data store. That is, for example, stored patient data/information is stored at the local level, having been previously received from local data source(s) (e.g., thepatient record modules303,305). In some examples, when a request is made for patient data/information in the reposed mode, the patient data/information is retrieved directly from the persistent data store (e.g., by the cache services sub-module).
• In some implementations, thecollector module326 and theadapter module336 are specific to the type ofpatient record module303,305, respectively. In the example ofFIG. 3, thepatient record module303 can be accessed based on a particular messaging protocol. An example messaging protocol can include the Health Level 7 (HL7) messaging protocol. In some examples, patient data/information provided based on such messaging protocols is reposed by thedata cache module324. Consequently, requests for such data can be fulfilled based on operation of thedata cache module314 and/or the localdata cache module324 in the reposed mode, as discussed above. In some examples, changes to patient records in thepatient record module303 can trigger updating of reposed patient data/information by thedata cache modules314,324. For example, thecollector module326 can automatically receive a message from thepatient record module303 in response to a change/updated, triggering updating/changing of reposed patient data/information.
• In the example ofFIG. 3, thepatient record module305 supports programmatic interface (e.g., API) access. In some examples, patient data/information provided through programmatic interfaces is passed-through thedata cache module314 and/or thedata cache module334. Consequently, requests for such data can be fulfilled based on operation of thedata cache module314 and/or the localdata cache module334 in the pass-through mode, as discussed above. In this manner, such patient data/information is not persisted by thedata cache module314,334.
• Although the example ofFIG. 3 depictsfacility systems302,304 having different types ofpatient record modules303,305, it is appreciated that facility systems can include any appropriate combination of types of patient record modules and any number of patient record modules (e.g.,patient record modules303,305), and respective adapter modules (e.g.,modules326,336). Further, although the example ofFIG. 3 depicts two facility systems, implementations of the present disclosure are applicable in instances include any number of facility systems.
• In some implementations, thevocabulary services modules328,338 perform translation between the vendor-specific vocabularies and a standard vocabulary. In this manner, patient data/information retrieved through themodules303,305 use standard vocabulary to be provided back to themobile device102 in a unified manner. For example, thepatient record modules303,305 can each be provided by a respective third-party (e.g., a vendor) and can record data/information based on a vocabulary that is specific to the particular vendor. Consequently, data sources provided from different third-parties can refer to the same data/information or type of data/information using different terminology. In some examples, eachvocabulary service module328,338 is specific to a respectivepatient record module303,305.
• FIG. 4 is a more detailed view of the functional block diagram ofFIG. 3, depicting additional components of theexample system300. In the depicted example, theDMS301 further includes a patientlist import module400, a patientmembership portal module402, a patientmatching service module404, a provider management (mgmt)module406, a patientinformation data store408, and a directoryinformation data store410. In some examples, the patientinformation data store408 stores patientdemographic information420, adata pointer cache422, a patient-to-provider index424 and a patient-to-facility index426. In some examples, the directoryinformation data store410 stores afacility directory430, aprovider directory432, and provider-to-facility index434.
• In some implementations, the patientlist import module400 enables initial and ongoing import of patient lists and patient demographic information for patients. In some examples, the patientlist import module400 provides an interface to receive a patient list, e.g., provided in a computer-readable document, and processes the patient list to populate the patient information data store408 (e.g., the demographic information420). In some examples, the patientmembership portal module402 provides an interface that enables users (e.g., an administrator) to establish relationships between patient data/information stored across healthcare continua and particular patients. In some examples, healthcare providers, facilities and/or facility systems across healthcare continua can be included in a healthcare organization (e.g., an accountable care organization (ACO)). In some examples, the patientmembership portal module402 enables a user to define relationships between multiple patient records (e.g., based on respective medical record numbers (MRNs)) to the healthcare organization. In some examples, relationship information defined through the patientmembership portal module402 can be stored in the patientinformation data store408.
• In some implementations, the patientmatching service module404 can be accessed by thehost module312 and the patientmembership portal module402. In some examples, the patientmatching service module404 can be accessed by an application executed on a mobile device (e.g., the mobile device102) through thehost module312.
• In some examples, the patientmatching service module404 processes patient data and/or patient information to identify potential patient matches between disparate data sources (e.g., multiple, different EMRs across the healthcare continuum). In some examples, patient information associated with confirmed matches (e.g., confirmed by an administrator through the patientmembership portal module402, confirmed by a healthcare provider using a mobile device through the host module312) can be stored in the patientinformation data store408. In some examples, a patient matching user interface (UI) is provided (e.g., displayed on a mobile device) and can be used by a healthcare provider to search for patients and establish, record and/or confirm relationships between patient records in different systems that are related to a single patient.
• In some examples, thedemographics information420 includes information that can be used to identify any patient that has been established in the system. In some examples, thedemographics information420 can be used to search for patients, discussed in further detail herein. Example demographics information can include name, age and/or gender. In some examples, thedata pointer cache422 stores identifiers associated with detailed patient data. In some examples, the identifiers point to particular data stores, in which to be retrieved patient data/information is stored. In this manner, retrieval performance (e.g., speed) can be improved. In some examples, the patient-to-provider index424 maps particular patients to one or more healthcare providers, and/or particular healthcare providers to one or more patients. For example, a patient can be treated by a plurality of healthcare providers (e.g., members of a patient care team, discussed below). As another example, a healthcare provider can treat a plurality of patients. In some examples, the patient-to-facility index426 maps particular patients to one or more facilities and/or facility systems. In some examples, a patient can be mapped to particular facilities based on respective MRNs of the patient at the respective facilities. For example, a healthcare continuum for a particular patient can include a hospital and a clinic. In this example, the patient-to-facility index can map the patient to the MRN of the hospital and the MRN of the clinic.
• In some implementations, the providermanagement portal module406 provides an interface (e.g., web portal) to enable members of a healthcare organization (e.g., ACO) to update healthcare provider directory information and/or healthcare provider-to-facility relationships. For example, a physician can be associated with one or more facility systems of the healthcare organization and credentials (e.g., for log on and/or authentication) can be provided to enable the physician to access patient data/information provided from the one or more facility systems.
• In some examples, thefacility directory430 provides a directory of the facilities interfaced to by the system (e.g., the DMS301). In some examples, thefacility directory430 also provides configuration parameters to enable communication (messaging) between the system and computing devices associated with the respective facilities. In some examples, theprovider directory432 includes a directory of healthcare providers (e.g., nurses, physicians, specialists, and the like) that are able to access patient data/information through the system (e.g., the DMS301). In some examples, the provider-to-facility index434 maps each healthcare provider (e.g., in the provider directory) to one or more facilities. For example, a healthcare provider can treat patients at multiple facilities. In some examples, the provider-to-facility index434 securely stores credentials of healthcare providers for facilities that the healthcare provider is mapped to. For example, a healthcare provider can have first credentials for accessing patient data/information at a first facility, and can have second credentials for accessing patient data/information at a second facility. In some examples, the provider-to-facility index434 supports single sign-on functionality discussed in further detail herein.
• An example data flow will be discussed to illustrate implementations of the present disclosure. It is appreciated that implementations of the present disclosure are equally applicable to other data flows. The example data flow can be initiated in response to a request received from a mobile device (e.g., the mobile device102). In some examples, the request includes a user identifier, a device identifier, a patient identifier, patient data identifiers, patient information identifiers and additional data identifiers. In some examples, the user identifier can be used to determine the particular user that has issued the request, and the device identifier can be used to determine the particular device that transmitted the request. In some examples, the patient identifier identifies the particular patient that is the subject of the request, the patient data identifiers identify the particular patient data that has been requested, the patient information identifiers identify the particular patient information that has been requested, and the additional data identifiers identify additional data that has been requested. For example, the patient data identifiers can indicate that patient vital data has been requested, and the additional data identifiers can indicate that vitals alarm data and vital data trend visualizations have also been requested.
• In the example data flow, theweb module310 receives the request and processes the request to validate the request and to authenticate the user, who submitted the request (e.g., based on the user identifier and/or the device identifier). Upon validation and authentication, theweb module310 provides the request to thehost module312. Thehost module312 processes the request, as discussed above. In some examples, it can be determined that patient data/information required to fulfill the request can be provided from the data cache module314 (e.g., reposed mode). In such examples, the patient data/information is provided to thehost module312 from thedata cache module314. In some examples, it can be determined that that patient data/information required to fulfill the request is to be retrieved from one or more data sources across a healthcare continuum of the patient (e.g., federated mode).
• In some examples, if patient data/information required to fulfill the request is to be retrieved from one or more data sources across the healthcare continuum (e.g. federated mode), request information (e.g., assembled by thehost module312, as discussed above) is provided to theadapter module316 bydata cache module314. In some examples, theadapter module316 accesses information stored in thedirectory store410 to request data from one or more facility systems (e.g., the facility system304). For example, theadapter module316 can be aware of which facility systems to retrieve patient data/information from (e.g., based on the patient-to-facility index426) and can access the provider-to-facility index434 to retrieve user credentials for the particular provider (e.g., user that issued the request). In this manner, theadapter module316 can provide appropriate user credentials to respective facility systems for patient data/information retrieval.
• In some examples, theadapter module316 sends requests to identified facility systems, each request identifying patient data/information and providing appropriate user credentials. In some examples, respective host modules (e.g., the host module332) of the facility systems receive the requests from theadapter module316, and can process the requests as similarly discussed above with reference to thehost module312. The respective host modules fulfill the requests and provide the requested patient data/information back to theadapter module316. In some examples, theadapter module316 provides the retrieved patient data/information to thehost module312, which completes processing of the request, as discussed above, and provides a response to the mobile device that issued the request.
• As discussed at the outset, the present disclosure provides a healthcare provider, or user of themobile device102, with secure, remote access to patient data and/or patient information. Example patient data can include physiological data. In some examples, physiological data can be obtained from patient monitoring device(s). In some examples, physiological data can be obtained by a local healthcare provider (e.g., a nurse, or physician measuring blood pressure, temperature, heart rate). In some examples, physiological data can be recorded in one or more patient records (e.g., EMRs). In the example case of a maternity patient, patient data can include 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). In some examples, the term patient information refers to information corresponding to a particular patient that is, for example, input into theinformation system142 by the local healthcare provider. Example patient information can include 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 patient data, and/or chart annotations. The term patient information can also refer to patient information provided from one or more patient records (e.g., EMRs).
• The patient data and/or patient information provided to the remotely located user can be provided as real-time data, and/or as historical data and information. The patient data and/or patient information is communicated between themobile device102 and theDMS160,160′ using a secure connection that is established over thenetwork106. 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 themobile device102 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 themobile device102 and theDMS160,160′.
• In some examples, a census, or patient list is provided, which captures a variety of the information and/or data described herein that is associated with each of one or moremonitored patients150. Strip charting is also provided, in which patient data and/or information can be presented to the user in graphical form. In the example case of a maternity patient, a fetal strip and maternal contraction information can be provided for aparticular patient150. More specifically, theparticular patient150 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 themobile device102 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, orplatforms302 associated with the particularmobile device102. Example platforms include, but are not limited to, RIM Blackberry, Apple iOS and/or OS X, MS Pocket PC, Win Mobile (Pocket PC, Smartphone), Win Mobile (standard, professional) and/or any other appropriate platforms (e.g., Google Android, and Hewlett-Packard WebOS, Microsoft Windows, Unix, Linux).
• As discussed in detail herein, implementations of the present disclosure are directed to systems and methods of providing integrated and unified views of patient data and patient information from disparate data sources and/or products. More particularly, implementations of the present disclosure provide integrated and unified views of patient data and patient information retrieved from across a healthcare continuum. In some examples, the healthcare continuum can include a plurality of disparate clinical data sources. In some examples, a clinical data source can correspond to one or more categories of healthcare services. Example categories can include emergency medical services (EMS), outpatient services, inpatient services, ambulatory services, post-acute services, home services and stand-alone services. Example EMS can include emergency departments (e.g., emergency room (ER) of a hospital), urgent care facilities and transport (e.g., ambulance). Example outpatient services and/or inpatient services can include hospitals and/or critical access hospitals (CAHs). Example ambulatory services can include clinics, physicians groups/offices, surgery centers and pre-acute care. Example post-acute services can include skilled nursing facilities, long-term care hospitals, rehabilitation centers and home healthcare. Example stand-alone services can include imaging centers (e.g., MIR), oncology centers, laboratories, virtual call centers and retail clinics.
• FIG. 5 depicts anexample platform500 for providing integrated and unified views of patient data and patient information. Theexample platform500 includes one ormore product applications502 andcore components504. The example platform enables the transfer of patient data/information to/from one ormore data sources506 for display on a mobile device (e.g., the mobile device102). In some examples, theexample platform500 is provided as one or more computer-executable programs that are executed using one or more computing devices (e.g., theDMS160,160′).Example data sources506 can include one or more medical devices (e.g., bedside monitors), one or more EMRs, health information exchange (HIE)data512, image data514 (e.g., x-ray data), andsensor data516.
• In some implementations, theexample platform500 can include amobile application platform520. An examplemobile application platform520 can include the mobile application platform disclosed in U.S. application Ser. No. 13/716,974, filed Dec. 17, 2012, and which claims the benefit of U.S. Prov. App. No. 61/579,954, filed Dec. 23, 2011, the disclosures of which are expressly incorporated herein by reference in their entireties.
• In some examples, themobile application platform520 separates native graphical user interface (GUI) and operating system components from the application logic. In this manner, themobile application platform520 translates and interprets application logic into the native languages of each operating system of mobile devices to/from which patient data/information is to be transferred, and embraces the unique properties, features, function, and usability of each operating system. In some implementations, themobile application platform520 embodies a template-based approach, where one or more templates are provided, each template corresponding to a view of patient data/information that is to be presented on a mobile device. In some examples, and as discussed in further detail herein, default templates can be provided, which provide default views of patient data/information. In some examples, custom templates can be provided, and can include templates customized by a user of a mobile device.
• In some examples, themobile application platform520 processes patient data/information based on a template that defines a view to be displayed on the mobile device. In some examples, themobile application platform520 generates instructions for rendering graphics based on the patient data/information and the template, and provides instructions to the mobile device, the mobile device executing the instructions to provide the template-based view of the patient data/patient (e.g., rendering the patient data/information in a view displayed on the mobile device).
• In some examples, theproduct applications502 can include medical software applications that enable mobility in healthcare. For example, products can enable patient information and patient data (e.g., waveforms and other critical data from EMRs, bedside monitors and devices, pharmacy, lab, and other clinical information systems) to be securely and natively accessed by healthcare provides on mobile devices. Example products can include an obstetrics (OB) product (e.g., AirStrip OB provided by AirStrip Technologies, LLC), a cardiologiy product (e.g., AirStrip CARDIO provided by AirStrip Technologies, LLC), a patient monitoring product (e.g., AirStrip PATIENT MONITORING provided by AirStrip Technologies, LLC), and an EMR extension product (e.g., AirStrip EMR EXTENDER provided by AirStrip Technologies, LLC).
• FIG. 6 depicts example components and sub-components that can be included in thecore components504 ofFIG. 5. In some examples, each component and/or sub-component can be provided as one or more computer-executable programs that can be executed using one or more computing devices (e.g., computing devices of theDMS160,160′ ofFIGS. 1 and 2). In some examples, the core components provide secure data access and data transport, single sign-on and profile/context management, interoperability (data adapters and interfaces), intelligent message routing, master patient indices (e.g., EMPI) and care collaboration.
• In the depicted example, thecore components504 include asecurity component600, a care coordination andcollaboration interfaces component602, a data andworkflow integration component604, a datasource adapters component606 and aservices component608. In the depicted example, thesecurity component600 includes a single sign-onsub-component610 and a user context/profiles sub-component612. In the depicted example, the care coordination andcollaboration interfaces component602 includes avoice sub-component614, avideo sub-component616 and amessaging sub-component618. In the depicted example, the data andworkflow integration component604 includes a patient index (or indices)component620 and anintelligent routing sub-component622. In some examples, the datasource adapters component606 can include adapter services sub-components624 (e.g., theadapter services module324 ofFIG. 3). In the depicted example, theservices component608 includes a reporting and analytics sub-component626, aclinical transformation sub-component628 and an implementation andsupport sub-component630.
• In some examples, the single sign-onsub-component610 supports single sign-on functionality, discussed herein. In some examples, a user can be authenticated once (e.g., by providing log-in credentials to an application executed on a mobile device) and can be provided access to data across a plurality of data sources, without being authenticated for each data source individually. In some examples, the user context/profiles sub-component612 supports user-specific customizations based on a context of the user and/or a profile of the user, as discussed in further detail herein. Example contexts can include the user being an attending physician at one hospital and a part-time physician at another hospital. In some examples, one or more profiles can be associated with the user, each profile reflecting one or more customizations associated with the particular user. For example, the user can customize a default view that can be displayed on a mobile device, to provide a customized view. Consequently, after the user is authenticated, one or more user-defined (user-customized) views can be provided to the mobile device.
• In some examples, the care coordination andcollaboration interfaces component602 supports collaboration between members of a patient care team. For example, a patient care team can include a physician, a consultant, a specialist, an intensivist and a nurse. In some examples, thevoice sub-component614 provides voice-based collaboration between care team members (e.g., teleconferencing). In some examples, thevideo sub-component616 provides video-based collaboration between care team members (e.g., video conferencing). In some examples, themessaging sub-component618 provides messaging-based collaboration between care team members (e.g., SMS/MMS text messaging). In some examples, the care coordination andcollaboration component602 provides security in remote collaboration between care team members (e.g., secure teleconferencing, secure video conferencing and/or secure messaging).
• In some examples, the data andworkflow integration component604 integrates data from a plurality of data sources and routes data for display on mobile devices. In some examples, the patient index (or indices)component620 provides one or more indices for mapping users to facilities and/or patients. In some examples, one or more indices can be provided to associate a user (e.g., a physician) with a facility or multiple facilities (e.g., hospitals), to associate a patient with a facility or multiple facilities, and/or to associate a user with one or more patients. In some examples, an index can be based on an ACO. In some examples, the ACO includes one or more healthcare providers across a healthcare continuum and can provide cross-access to patient data/information. In some examples, theintelligent routing sub-component622 provides intelligent routing functionality, discussed above.
• In some examples, the datasource adapters component606 provides adapter functionality. In the depicted example, theservices component608 includes a reporting and analytics sub-component626, aclinical transformation sub-component628 and an implementation andsupport sub-component630.
• As discussed in further detail herein, patient data and patient information can be provided from one or more disparate patient data sources (e.g., examples depicted inFIG. 5). In some examples, a patient can be associated with one or more healthcare services across the healthcare continuum. Consequently, and for each patient, patient data and patient information can be distributed across the healthcare continuum. For example, a patient can be taken to a hospital by EMS (e.g., ambulance), can be treated in an emergency department of the hospital (e.g., ER), can stay in the hospital on an inpatient basis, can frequent a rehabilitation center (e.g., physical therapy), can be undergoing home healthcare (e.g., home nursing care), and patient samples can be sent to a laboratory for analysis (e.g., blood analysis provided by an external laboratory). In this example, treatment of the particular patient touches multiple facilities across the healthcare continuum, and each facility can generate its own patient data, patient information and patient records (EMRs).
• In general, an EMR can be described as a digital medical record provided as an electronic document that can be processed (e.g., read from/written to) by one or more computer programs executed by one or more computing devices. Further, each entity or organization (e.g., clinic, hospital, physician, rehabilitation center, laboratory) that treats a patient can include its own, stand-alone information system that provides an EMR that is specific to the information system. Consequently, multiple, disparate EMRs can be provided for a single patient across the healthcare continuum. Within the context of the example above, a first EMR can be provided for the patient by an ambulance service that transported the patient to the hospital, a second EMR can be provided for the patient by the hospital, a third EMR can be provided for the patient by the rehabilitation center and a fourth EMR can be provided for the patient by a nursing company that is providing home nursing care to the patient. In some examples, and as noted above, EMRs can be generated from disparate information systems. Consequently, format and syntax of one EMR can be different from the format and syntax of another EMR.
• In some examples, historical patient data and information can be provided for viewing by a healthcare provider, as well as providing real-time patient data for viewing to the healthcare provider. Extending the example above, the patient can be re-admitted to the hospital on an inpatient basis and can be connected to one or more patient monitoring devices that generate patient physiological data based on patient physiological activity. In accordance with implementations of the present disclosure, and as discussed in further detail herein, patient data and information from one or more of the first EMR, the second EMR, the third EMR and the fourth EMR, as well as real-time patient data can be provided for display to a healthcare provider (e.g., a physician attending to the patient) on a mobile device in an integrated and unified manner. For example, real-time and/or historical patient physiological data can be provided for display by multiple products (e.g., a cardiology product and a patient monitoring product). Implementations of the present disclosure enable integration and unification of the patient physiological data across the products.
• In accordance with implementations of the present disclosure, patient data can be displayed to a user of a computing device. In some implementations, the user provides log-in credentials to an application that is executed on the mobile device. For example, the application can open and can provide a log-in screen for the user to provide credentials. In some examples, the credentials can include a personal identification number (PIN). If the PIN is not authenticated (e.g., the user-input PIN is not the same as a pre-stored PIN), an error is displayed. If the PIN is authenticated (e.g., the user-input PIN is the same as a pre-stored PIN), a sites screen or a base screen can be displayed. In some examples, authentication can be provided based on a personal identifier (e.g., the PIN) and another identifier. In some examples, another identifier can include an identifier that is unique to a mobile device that the user is using. For example, the PIN and a unique device identifier can be provided for authentication.
• FIG. 7 depicts an example sites screen700. In some implementations, the sites screen700 provides a GUI including one or more site icons that can be selected (e.g., clicked on) by the user. In some examples, a site can include a specific facility (e.g., hospital clinic), a system of facilities (e.g., a hospital system including one or more hospitals, one or more clinics, and/or one or more laboratories, and the like). In some examples, an index (e.g., a user-facility index) can be accessed based on an identifier associated with the user, to determine the one or more site icons that are to be displayed to the user. In some examples, in response to the PIN being authenticated, an identifier associated with the user can be provided to theDMS160′, for example, by the mobile device102 (seeFIGS. 1 and 2). In some examples, theDMS160′ stores an index (e.g., a user-facility index) that is accessed based on the identifier. In some examples, the index maps the identifier associated with the user to one or more facilities that the user is associated with. In response, theDMS160′ provides instructions to themobile device102 to display the sites screen700 including the one ormore site icons702,704,706,708,710,712,714,716, each site icon being a graphical representation of a facility of facilities that the user is associated with.
• In some implementations, and as noted above, the user can be associated with more than one site (e.g.,702,704,706,708,710,712,714,716). In some implementations, the user is affiliated with a single site, which is included in a network that includes a plurality of inter-communicating sites associated therewith. In some examples, a site can include a medical center, a dispensary, a hospital, an infirmary, a surgery center, an ambulatory setting, a nursing home, a rest home, a sanatorium, a sanitarium, or any other appropriate healthcare facility. In some implementations, thesite screen700 can provide a summary of each site and/or specific sites, with which the user is associated. In some examples, a site summary can include a plurality of selectable icons (e.g. a site access icon, a site information icon, a patient information icon, etc.). In some implementations, each site summary can include attributes (e.g. patient counts).
• User input can be provided to thesite screen700, the user input indicating a selection of a site icon of the one or more site icons. In some examples, user input can include touching of a touchscreen display with a digit (e.g., finger), a stylus, and/or other pointing device, as well as with a digital cursor and/or a keypad.
• In some implementations, a base screen can be displayed. In accordance with implementations of the present disclosure, and as discussed in further detail herein, the base screen can include a menu. In some examples, the menu provides a GUI, through which the user can request display of patient data/information. In some examples, the menu is a user-specific menu. In some examples, the menu is specific to one or more user contexts. In some examples, the menu is specific to a site selected by the user. In some examples, the base screen is displayed in response to the PIN being authenticated. In some examples, the base screen is displayed in response to user input to the sites screen.
• In accordance with implementations of the present disclosure, the menu is provided as a slide-out menu that is animated in response to user selection of an icon. In some examples, the menu can be animated such that the menu appears to slide-out from an edge of the base screen (e.g., left-side edge). In some examples, the menu is animated such that the menu appears to slide-in to the edge of the base screen in response to user selection of an icon from the menu.
• In accordance with implementations of the present disclosure, the menu can include icon groups. In some examples, the icon groups can be provided as default icon groups. For example, a default icon group can be displayed in the menu, the default icon group being agnostic to the particular user (e.g., displayed for any user). In some examples, the icon groups can include user-customized icon groups. For example, the menu can include a user-customized icon group that is specific to (e.g., that was defined by) the user. In some examples, the icon groups can include user-specific and/or site-specific icon groups. For example, an icon group can include a workflow icon group that is specific to the role of the user (e.g., an attending physician) at a specific facility.
• FIG. 8 illustrates an example screen-shot of abase screen800 that includes amenu802. Theexample base screen800 ofFIG. 8 is user-specific and site-specific. For example, thebase screen800 can be displayed in response to user selection of a site icon (e.g., thesite icon704 ofFIG. 7). Consequently, asite identifier816 can be provided to indicate the site, to which themenu802 is specific. In some examples, a request for the base screen is provided to theDMS160′ in response to user selection of an icon from thesites screen700. In some examples, the request indicates the site that was selected. In some examples, a user-facility index can be accessed to determine a configuration of a menu to be displayed in the base screen. For example, and for a given site (facility), the user can have an associated profile, user-defined patient groups, context-specific workflows and/or facility-specific workflows. Consequently, theDMS160′ can provide instructions for displaying a user-specific, site-specific base screen, such as theexample base screen800 ofFIG. 8. More particularly, the instructions can include instructions for displaying a user-specific, site-specific menu802 for thebase screen800.
• In the depicted example, themenu802 provides icons for initiating respective displays of patient data/information. In themenu802, the icons are displayed in icon groups, ormenu groups804a,804b.It is appreciated that more or fewer icon groups can be displayed. In the example ofFIG. 8, theicon group804acan be provided as a default icon group. For example, theicon group804aincludes icons “My Patients”806, “Recently Viewed”808, and “Find Patients”810. In some examples, theicons806,808,810 are default icons. That is, for example, theicons806,808,810 are not specific to the user and/or the facility (e.g., theicons806,808,810 are displayed regardless of the particular user and/or the particular facility). In some examples, theicon group804acan be customized by the user. For example, the user can define a patient group (e.g., “My Cardio Patients,” “My OB Patients”) and can associate one or more patients with the group. Consequently, an icon that is representative of a user-defined group can be displayed in theicon group804a.
• In the example ofFIG. 8, theicon group804bcan be provided as a user-specific and facility-specific icon group. For examples, theicon group804bcan be representative of a workflow (e.g., “Cardio”) associated with the user at the particular facility (e.g., as indicated by the identifier816). Consequently, theicon group804acan include icons that are relevant to the particular workflow. In the depicted example, theicon group804bincludes an “In Basket”icon812 and an “EMS”icon814. In some examples, a workflow can include one or more tasks to be performed by the user as part of the user's role at a particular facility.
• In some implementations, a request can be provided to theDMS160′ in response to user selection of an icon from themenu802. In the example ofFIG. 8, the user can select the “My Patients”icon806. In response, a request can be provided to theDMS160′, the request indicating a request for a list of all patients that the user is associated with. TheDMS160′ can provide a response that includes instructions to display a list of all patients associated with the user and can include patient data/information for display. In some examples, and in response to the user selection of the “My Patients”icon806, themenu802 is animated to slide-in to the edge of the screen.
• Implementations of the present disclosure enable remote execution of patient-associated tasks. In some examples, patient-associated tasks can be time sensitive. For example, review and confirmation of a patient ECG by a cardiologist can be required to be executed within a pre-determined time period. Although review and confirmation of a patient ECG will be used herein as an example patient-associated task, it is contemplated that implementations of the present disclosure are applicable to other appropriate patient-associated tasks. In some examples, if a patient-associated task is not executed within the pre-determined time period associated costs will not be reimbursed (e.g., by a health insurance provider, by government administered programs). Consequently, implementations of the present disclosure provide time-sensitive, patient-associated tasks for display on mobile devices, and enable users to remotely execute such tasks, as discussed in further detail herein.
• In some implementations, information associated with one or more patient-associated tasks can be provided from one or more back-end systems (e.g., ECG management system, perinatal system, patient intake system, any appropriate clinical information system). In the example context, ECG information can be provided from an ECG management system. In some examples, patient-associated tasks that are within the pre-determined time period are displayed to a user of a mobile device. In some examples, an initial timestamp of a patient-associated task can be compared to a current time. In some examples, if a difference between the current time and the initial timestamp is below a threshold time (e.g., the pre-determined time period), a graphical representation of the patient-associated task is displayed to the user. In the example context, it can be provided that an ECG must be reviewed and confirmed within 24 hours of the ECG having been taken. Consequently, if a difference between a current time, and the time at which the ECG was taken exceeds a threshold time (e.g., 24 hours), a graphical representation of the patient-associated task is not displayed to the user.
• In some implementations, graphical representations of time-sensitive, patient-associated tasks can be displayed to the user in a first “Tasks” screen (first screen). In some examples, the first screen displays graphical representations of patient-associated tasks that are still within the pre-determined time period. In some examples, the first screen exclusively displays graphical representations of patient-associated tasks that are still within the pre-determined time period. In some implementations, graphical representations of time-sensitive, patient-associated tasks can be displayed to the user in a second “Tasks” screen (second screen). In some examples, the second screen displays graphical representations of patient-associated tasks that are already outside of the pre-determined time period. For example, although a patient-associated task was not completed within the pre-determined time period, the patient-associated task is still indicated to the user, such that the patient-associated task can still be executed by the user. In some examples, the second screen displays graphical representations of patient-associated tasks that are outside of the pre-determined time period. In some examples, the second screen displays graphical representations of patient-associated tasks that are still within the pre-determined time period, and graphical representations of patient-associated tasks that are outside of the pre-determined time period.
• In some implementations, and as depicted below with reference toFIGS. 9 and 10, the user can perform patient-associated tasks on the mobile device. In some examples, in response to the user performing a patient-associated task, a signal and/or data can be provided to a back-end system. In this manner, the back-end system can record when the patient-associated task was executed and/or determine whether the patient-associated task was completed with the pre-determined time period.
• FIGS. 9 and 10, discussed in further detail below, depict an example context for remote display and execution of time-sensitive, patient-associated tasks. The example context includes reviewing and confirming one or more pending ECGs. In some example, requests and/or ECG information can be provided from an appropriate information source (e.g., an ECG management system).
• FIG. 9 illustrates an example screenshot of a “Time-Sensitive Tasks”screen900 that can be displayed in response to user selection of a “Cardiology” icon in a base screen, and a time-sensitive icon. In this example, thescreen900 is user-specific and site-specific (e.g., specific to General Hospital), and includes amenu902 that provides icons for initiating respective displays of location maps and patient data/information. In theexample menu902, “Recently Viewed”icon904, a “My Patients”icon906, a “Consults”icon908, a “Cardiology”icon910, an “OB”icon912, a “Location”icon914, and a “Find Patients”icon916. Thescreen900 further includes a time-sensitive icon920.
• In the depicted example, theicon910 and theicon920 are selected. Consequently, graphical representations of time-sensitive, patient-associated tasks are displayed. More particularly, thescreen900 providesicon groups922,924, eachicon group922,924 including one or morepatient icons930 that represent a time-sensitive, patient-associated task. For example, thepatient icons930 represent time-sensitive, patient-associated tasks that are still within a pre-determined time period. In the depicted example, the a pre-determined time period includes 23 hours, indicating that each patient-associated task has been initiated within the last 23 hours and still needs to be completed. In some examples, a drop-dead time period can be provided and can be greater than the pre-determined time period. For example, a drop-dead time period can include 24 hours, while the pre-determined time period includes 23 hours. In some examples, the drop-dead time period can be a time period that, if exceeded, provides an adverse results (e.g., non-reimbursement for the cost of the underlying ECG). In some examples, the pre-determined time period provides an indication of how close time-sensitive, patient-associated tasks are to reaching the drop-dead time period.
• In the example ofFIG. 9, thepatient icons930 each include patient information and patient data. The example patient information can include patient name, the patient gender, an identifier associated with the patient, an ECG summary, and/or patient date of birth (DOB). It is appreciated that implementations of the present disclosure can include additional and/or other patient data/information in a patient icon. In some examples, the patient data/information provided in thepatient icons930 can include recorded patient data/information. In some examples, the patient data/information provided in thepatient icons930 can include real-time patient data/information. For example, apatient icon930 can be representative of a patient that is currently being monitored by one or more patient monitoring devices (e.g., as depicted inFIGS. 1 and 2), and the patient data displayed in thepatient icon930 can be updated in real-time based on data provided from the monitoring device(s).
• In the depicted example, the icon groups are associated with locations and/or departments of the particular facility. For example, theicon group922 is associated with the intensive care unit (ICU) of the facility, and theicon group924 is associated with the “East Wing” of the facility. In some examples, icon groups can be associated with times before pre-determined time periods and/or drop-dead time periods are exceeded. For example, a first icon group can be associated with “1 hour” before a pre-determined time period or a drop-dead time period will be exceeded, and a second icon group can be associated with “12 hours” before the pre-determined time period or the drop-dead time period will be exceeded. In this manner, more urgent time-sensitive, patient-associated tasks can be separated from or highlighted relative to less urgent time-sensitive, patient-associated tasks.
• In accordance with implementations of the present disclosure, the user can select apatient icon930 from thescreen900 to initiate execution of a respective time-sensitive, patient associated task. In the example context, in response to user selection of apatient icon930, an ECG screen associated with a respective patient is displayed.
• FIG. 10 depicts anexample ECG screen1000 graphically representing an ECG on the display of a mobile device. In some examples, the ECG screen is displayed in response to user selection of a patient icon (e.g., a patient icon930) from a “Time-Sensitive Tasks” screen (e.g., a “Time-Sensitive Tasks” screen900). The example ECG discussed herein corresponds to a 12-lead ECG Implementations of the present disclosure are applicable to any appropriate type of ECG TheECG screen1000 provides graphical information relating to the data collected from a patient monitoring device. In particular, theECG screen1000 provides cardiology information relating to data collected from an ECG monitoring device coupled to a patient.
• TheECG screen1000 includes adisplay region1002 and adisplay region1004. In the depicted example, thedisplay region1002 provides a grid of ECG trace windows1010a-1010l(e.g., 4 columns by 3 rows, the first column including the leads I, II and III, the second column including the leads aVR, aVL and aVF, and the last two columns including the leads V₁-V₆). Each trace window1010a-1010lincludes a respective voltage trace1005a-1005lcorresponding to the respective lead over a period of time. In some examples, the trace windows1010a-1010lcan be used to zoom in and out of and to scroll along segments of the respective voltage traces1005a-1005l.
• Thedisplay region1004 includes expanded trace windows, each expanded trace window corresponding to a trace window provided in thedisplay region1002. In the example ofFIG. 10, expandedtrace windows1012a,1012bare displayed and correspond to thetrace windows1010a,1010b,respectively, of thedisplay region1002. In some examples, the expanded traced windows can be scrolled upward/downward within thedisplay region1004 to reveal additional expanded trace windows. For example, un-displayed expanded trace windows (e.g., expanded trace windows1012c-1012l), or partially displayed, expanded trace windows (e.g., expandedtrace window1012b) can be scrolled into full view, while displayed trace windows (e.g., expandedtrace windows1012a,1012b) can be scrolled from view.
• Thedisplay region1004 can display expanded trace windows1012a-1012lhaving respective voltage traces1013a-1013l,each voltage trace1013a-1013lcorresponding to voltage traces1005a-1005l.The voltage traces1013a-1013lare each provided as full traces for a particular period of time, graphically representing the ECG data collected over the particular period of time. In some examples, the user defines a desired time period for viewing ECG data by zooming in/out of and/or scrolling along one of the voltage traces1005a-1005lto display a desired segment of the voltage traces1005a-1005lwithin the trace windows1010a-1010l.Accordingly, the trace display windows1010a-1010lrespectively display segments of the voltage traces1005a-1005l,the segments corresponding to respective segments of the voltage traces1013a-1013ldisplayed in the expanded trace windows1012a-1012l.That is, each trace window1010a-1010lcan display a full trace or zoomed-in voltage trace1005a-1005lcorresponding to a voltage trace1013a-1013l.In some examples, the voltage traces1005a-1005lare synchronized with each other, such that scrolling and/or zooming of a voltage trace1005a-1005lin one trace window1010a-1010lresults in an equivalent scrolling and/or zooming in each of the other trace windows1010a-1010l.Consequently, each trace window1010a-1010ldisplays its respective voltage trace1005a-1005lfor the same time period.
• With continued reference toFIG. 10, abeveled scrubber bar1020 can be provided in each of the trace windows1012a-1012l.Thebeveled scrubber bar1020 provides aviewing area1022 having a width w. Theviewing area1022 displays a portion of the voltage trace1013a-1013lcorresponding to the portion of the voltage trace1005a-1005ldisplayed in trace display windows1010a-1010l.Accordingly, the width w generally corresponds to the time period of the voltage traces1005a-1005l.In the example ofFIG. 10, the width w corresponds to the time period between time t₃and t₄. Thebeveled scrubber bars1020 provide a graphical indicator that enables a user to quickly discern which portion of the voltage traces1013a-1013lcorrespond to the voltage traces1005a-1005l.
• Further details of example ECG displays are provided in International App. No. PCT/US2012/021677, which claims the benefit of U.S. Prov. App. No. 61/433,824, the disclosures of which are expressly incorporated herein by reference in their entireties.
• In accordance with implementations of the present disclosure, thescreen1000 includes anedit icon1040. In some examples, user input to the edit icon1040 (e.g., tap on) induces display of one or more option icons. In some examples, a drop-down menu is displayed, the drop-down menu including the one or more option icons. In some examples, the user is able to add a diagnosis, edit a diagnosis, delete a diagnosis and confirm a diagnosis. In some examples, the user can review the ECG in thescreen1000 and can select theedit icon1040 to add, edit and/or delete a diagnosis. In some examples, the user can select the edit icon to confirm a diagnosis. For example, the user can select theedit icon1040 to display the drop-down menu, the drop-down menu including a confirm icon. The user can select the confirm icon to confirm a diagnosis associated with the particular ECG In some examples, a confirmation signal associated with the particular ECG can be transmitted to the back-end system in response to selection of the confirm icon. In some examples, once the ECG has been confirmed, the patient-associated task (e.g., ECG consult) is determined to be completed.
• FIG. 11 depicts anexample process1100 that can be executed in accordance with implementations of the present disclosure. In some examples, theexample process1100 can be provided in one or more computer-executable programs that can be executed using one or more computing devices (e.g., themobile device102 and/or theDMS160,160′).
• User input is received (1102) and a task screen is displayed (1104). In some examples, the task screen is a “Time-Sensitive Tasks” screen that provides one or more patient icons that represent a time-sensitive, patient-associated task (e.g., thescreen900 ofFIG. 9). It is determined whether an icon is selected (1104). For example, it is determined whether a patient icon representative of a time-sensitive, patient-associated task is selected. If an icon is not selected, it is determined whether a new screen is to be displayed (1114). For example, the user can choose to navigate to a different screen from the task-specific screen. If it is determined that a new screen is to be displayed, the new screen is displayed (1116). If it is determined that a new screen is not to be displayed, theexample process1100 loops back.
• If an icon is selected, a task-specific screen is displayed (1108). In some examples, a task-specific screen displays patient data/information associated with the underlying time-sensitive task and enables the user to complete the task (e.g., thescreen1000 ofFIG. 10). It is determined whether completion of the task is confirmed (1110). For example, the user can select a confirm option from the task-specific screen. If completion of the task is confirmed, a signal is transmitted to a back-end system (1112). In this manner, a back-end system managing the underlying task can be informed that the task has been attended to. If completion of the task is not confirmed, it is determined whether a new screen is to be displayed (1114). For example, the user can choose to navigate to a different screen from the task-specific screen. If it is determined that a new screen is to be displayed, the new screen is displayed (1116). If it is determined that a new screen is not to be displayed, theexample process1100 loops back.
• Implementations of the present disclosure can be provided using digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof. In some examples, implementations can be provided one or more computer program products, e.g., a computer program tangibly embodied in a machine-readable storage device, for execution by, or to control the operation of, data processing apparatus, and/or 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.
• Operations in accordance with implementations of the present disclosure can be performed by one or more programmable processors executing a computer program product to perform functions by operating on input data and generating output. By way of 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. Elements of a computer can include a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer can 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 example 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 themobile device102, 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 implementations 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 present disclosure can be performed in a different order and still achieve desirable results. Accordingly, other implementations are within the scope of the following claims.

Claims (11)

1.-9. (canceled)

10. A method for providing a user of a mobile device access to patient information and patient physiological data, the method comprising:

receiving, by one or more processors, user input indicating a user command to display a task screen;

in response to the user input, displaying the task screen on the mobile device, the task screen displaying one or more patient icon groups, each patient icon group comprising one or more patient icons;

receiving, by the one or more processor, a user selection of a patient icon from the one or more patient icon groups; and

in response to the user selection of the patient icon, displaying a plurality of windows on the mobile device, the plurality of windows comprising:

a first window displaying first health information associated with a period of time, the first health information comprising first patient physiological data, wherein the first window comprises a first indicator that indicates a first patient physiological data portion corresponding to a sub-period of time with respect to the period of time, and

a second window synchronized with the first window and displaying second health information associated with the period of time, the second health information comprising second patient physiological data, wherein the second window comprises a second indicator that indicates a second patient physiological data portion corresponding to the sub-period of time.

11. The method ofclaim 10, wherein at least one of the first indicator and the second indicator comprises a beveled scrubber bar comprising a viewing window.

12. The method ofclaim 10, wherein the patient physiological data comprises electrocardiogram (ECG) data.

13. The method ofclaim 10, further comprising processing, by the one or more processors, user-specific data to determine the one or more patient icons, each patient icon representing a time-sensitive, patient-associated task.

14. The method ofclaim 13, further comprising receiving user input indicating completion of the time-sensitive, patient-associated task of the patient icon, and in response, providing a signal to a back-end system indicating completion of the time-sensitive, patient-associated task.

15. The method ofclaim 14, further comprising removing the patient icon from display in the task screen.

16. The method ofclaim 13, wherein each time-sensitive, patient-associated task is determined to be within a threshold time period.

17. The method ofclaim 16, wherein the time-sensitive, patient-associated task is determined to be within the threshold time period when a difference between a current time and a time associated with the time-sensitive, patient-associated task is within the threshold time period.

18. A computer-readable storage device coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for providing a user of a mobile device access to patient information and patient physiological data, the operations comprising:

receiving user input indicating a user command to display a task screen;

in response to the user input, displaying the task screen on the mobile device, the task screen displaying one or more patient icon groups, each patient icon group comprising one or more patient icons;

receiving a user selection of a patient icon from the one or more patient icon groups; and

in response to the user selection of the patient icon, displaying a plurality of windows on the mobile device, the plurality of windows comprising:

a first window displaying first health information associated with a period of time, the first health information comprising first patient physiological data, wherein the first window comprises a first indicator that indicates a first patient physiological data portion corresponding to a sub-period of time with respect to the period of time, and

a second window synchronized with the first window and displaying second health information associated with the period of time, the second health information comprising second patient physiological data, wherein the second window comprises a second indicator that indicates a second patient physiological data portion corresponding to the sub-period of time.

19. A system, comprising:

one or more processors; and

a computer-readable storage medium in communication with the one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for providing a user of a mobile device access to patient information and patient physiological data, the operations comprising:

receiving user input indicating a user command to display a task screen,

in response to the user input, displaying the task screen on the mobile device, the task screen displaying one or more patient icon groups, each patient icon group comprising one or more patient icons,

receiving a user selection of a patient icon from the one or more patient icon groups, and

in response to the user selection of the patient icon, displaying a plurality of windows on the mobile device, the plurality of windows comprising:

a first window displaying first health information associated with a period of time, the first health information comprising first patient physiological data, wherein the first window comprises a first indicator that indicates a first patient physiological data portion corresponding to a sub-period of time with respect to the period of time, and

a second window synchronized with the first window and displaying second health information associated with the period of time, the second health information comprising second patient physiological data, wherein the second window comprises a second indicator that indicates a second patient physiological data portion corresponding to the sub-period of time.

Images