US20140100873A1 - Attaching patient context to a call history associated with voice communication - Google Patents
Attaching patient context to a call history associated with voice communication Download PDFInfo
- Publication number
- US20140100873A1 US20140100873A1 US13/711,206 US201213711206A US2014100873A1 US 20140100873 A1 US20140100873 A1 US 20140100873A1 US 201213711206 A US201213711206 A US 201213711206A US 2014100873 A1 US2014100873 A1 US 2014100873A1
- Authority
- US
- United States
- Prior art keywords
- context
- list
- patient
- call history
- clinician
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- G06F19/322—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04842—Selection of displayed objects or displayed text elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B5/00—Visible signalling systems, e.g. personal calling systems, remote indication of seats occupied
- G08B5/22—Visible signalling systems, e.g. personal calling systems, remote indication of seats occupied using electric transmission; using electromagnetic transmission
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
Definitions
- Patient medical information such as that contained in the EMR, allows health care providers to provide continuity of care to patients.
- these collaborations while important to providing care for patients, often goes undocumented because the ability to track mobile voice communication as well as the content discussed is not currently available. This results in confusion and an inability to reference the details (e.g. patient name, relevant alerts, and the like) of a mobile voice call and leaves the clinician and healthcare entity unable to appropriately track such information that may otherwise be useful in analytics, tracking patient progress, billing, reimbursement, scheduling staff, and patient acuity.
- Embodiments of the present invention relate to declining, attaching, and editing patient context to mobile voice communication. More particularly, patient demographic or alert information is attached to a call history which is stored in the electronic medical record (EMR) and utilized for later analysis (e.g., analytics, patient progress, billing, reimbursement, staff scheduling, patient acuity, and the like).
- EMR electronic medical record
- computer storage media storing computer-executable instructions that, when executed by one or more computing devices, cause the one or more computing devices to perform a method that facilitates attaching patient context to a call history associated with mobile voice communication.
- a selection of one of an alert from an alert list or one or more patients from a patient list is received.
- Context associated with the alert, the one or more patients, or a combination thereof is provided.
- An indication that a first clinician is initiating a voice communication with a second clinician is received.
- a selection of the second clinician from a contact list is received.
- the context is attached to a call history associated with the voice communication.
- a computer system to facilitate attaching patient context to a call history associated with mobile voice communication.
- the computer system comprises a processor coupled to a computer storage medium, the computer storage medium having stored thereon a plurality of computer software components executable by the processor.
- a selection component receives a selection of one of an alert from an alert list or one or more patients from a patient list.
- a context component provides context associated with the alert, the one or more patients, or a combination thereof.
- An indication component receives an indication that a first clinician is initiating a voice communication with a second clinician.
- a contact component receives a selection of the second clinician from a contact list.
- An attachment component attaches the context to a call history associated with the voice communication.
- GUI graphical user interface
- a list display area displays one of an alert list or a patient list.
- a context display area displays context associated with an alert, one or more patients, or a combination thereof.
- a call display area displays an indicator for initiating a voice communication.
- a contact display area displays a contact list.
- An attachment display area displays the context attached to the call history associated with the voice communication.
- FIG. 1 is a block diagram of an exemplary computing environment suitable for use in implementing the present invention
- FIG. 2 is a block diagram of an exemplary system for declining, attaching, or editing patient context to mobile voice communication, in accordance with embodiments of the present invention
- FIGS. 3-19 are illustrative graphical user interface displays of declining, attaching, or editing patient context to mobile voice communication, in accordance with embodiments of the present invention.
- FIG. 20 is a flow diagram showing a method for attaching patient context to mobile voice communication, in accordance with an embodiment of the present invention.
- FIG. 21 is a flow diagram showing a method for declining, attaching, or editing patient context to mobile voice communication, in accordance with an embodiment of the present invention.
- Embodiments of the present invention can positively impact health organizations' key imperatives in a variety of ways.
- Embodiments of the present invention provide context to voice communications that can be utilized in analytics, revealing trends, tracking resources, tracking patient progress, billing, reimbursement, scheduling staff, and patient acuity.
- Embodiments of the present invention provide multi-action buttons on mobile devices that can be utilized by clinicians to improve response time and availability.
- an exemplary computing system environment for instance, a medical information computing system, on which embodiments of the present invention may be implemented is illustrated and designated generally as reference numeral 100 .
- reference numeral 100 It will be understood and appreciated by those of ordinary skill in the art that the illustrated medical information computing system environment 100 is merely an example of one suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the medical information computing system environment 100 be interpreted as having any dependency or requirement relating to any single component or combination of components illustrated therein.
- Embodiments of the present invention may be operational with numerous other general purpose or special purpose computing system environments or configurations.
- Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the present invention include, by way of example only, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above-mentioned systems or devices, and the like.
- Embodiments of the present invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
- program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types.
- Embodiments of the present invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in local and/or remote computer storage media including, by way of example only, memory storage devices.
- the exemplary computing system environment 100 includes a general purpose computing device in the form of a control server 102 .
- Components of the control server 102 may include, without limitation, a processing unit, internal system memory, and a suitable system bus for coupling various system components, including database cluster 104 , with the control server 102 .
- the system bus may be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus, using any of a variety of bus architectures.
- such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronic Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, also known as Mezzanine bus.
- ISA Industry Standard Architecture
- MCA Micro Channel Architecture
- EISA Enhanced ISA
- VESA Video Electronic Standards Association
- PCI Peripheral Component Interconnect
- the control server 102 typically includes, or has access to, a variety of computer readable media, for instance, database cluster 104 .
- Computer readable media can be any available media that may be accessed by server 102 , and includes volatile and nonvolatile media, as well as removable and non-removable media.
- Computer readable media may include computer storage media and communication media.
- Computer storage media may include, without limitation, volatile and nonvolatile media, as well as removable and nonremovable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
- computer storage media may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage device, or any other medium which can be used to store the desired information and which may be accessed by the control server 102 .
- Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media.
- modulated data signal refers to a signal that has one or more of its attributes set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above also may be included within the scope of computer readable media.
- the computer storage media discussed above and illustrated in FIG. 1 provide storage of computer readable instructions, data structures, program modules, and other data for the control server 102 .
- the control server 102 may operate in a computer network 106 using logical connections to one or more remote computers 108 .
- Remote computers 108 may be located at a variety of locations in a medical or research environment, for example, but not limited to, clinical laboratories, hospitals and other inpatient settings, veterinary environments, ambulatory settings, medical billing and financial offices, hospital administration settings, home health care environments, and clinicians' offices.
- Clinicians may include, but are not limited to, a treating physician or physicians, specialists such as surgeons, radiologists, cardiologists, and oncologists, emergency medical technicians, physicians' assistants, nurse practitioners, nurses, nurses' aides, pharmacists, dieticians, microbiologists, laboratory experts, genetic counselors, researchers, veterinarians, students, and the like.
- the remote computers 108 may also be physically located in non-traditional medical care environments so that the entire health care community may be capable of integration on the network.
- the remote computers 108 may be personal computers, mobile devices, servers, routers, network PCs, peer devices, other common network nodes, or the like, and may include some or all of the components described above in relation to the control server 102 .
- the devices can be personal digital assistants or other like devices.
- Exemplary computer networks 106 may include, without limitation, local area networks (LANs) and/or wide area networks (WANs). Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.
- the control server 102 may include a modem or other means for establishing communications over the WAN, such as the Internet.
- program modules or portions thereof may be stored in the control server 102 , in the database cluster 104 , or on any of the remote computers 108 .
- various application programs may reside on the memory associated with any one or more of the remote computers 108 .
- the network connections shown are exemplary and other means of establishing a communications link between the computers (e.g., server 102 and remote computers 108 ) may be utilized.
- a user may enter commands and information into the control server 102 or convey the commands and information to the control server 102 via one or more of the remote computers 108 through input devices, such as a keyboard, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad.
- input devices such as a keyboard, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad.
- Other input devices may include, without limitation, microphones, satellite dishes, scanners, or the like.
- Commands and information may also be sent directly from a remote healthcare device to the control server 102 .
- the control server 102 and/or remote computers 108 may include other peripheral output devices, such as speakers and a printer.
- control server 102 and the remote computers 108 are not shown, those of ordinary skill in the art will appreciate that such components and their interconnections are well known. Accordingly, additional details concerning the internal construction of the control server 102 and the remote computers 108 are not further disclosed herein.
- FIG. 2 a block diagram is illustrated that shows an exemplary computing system architecture for implementing embodiments of the present invention. It will be appreciated that the computing system architecture shown in FIG. 2 is merely an example of one suitable computing system and is not intended as having any dependency or requirement related to any single module/component or combination of modules/components.
- the computing system 200 includes one or more user devices 210 (e.g., a mobile communication device), context engine 220 , network 230 , health information system 240 , and EMR 250 .
- user devices 210 e.g., a mobile communication device
- context engine 220 e.g., a mobile communication device
- network 230 e.g., a network
- health information system 240 e.g., a health information system
- EMR 250 e.g., a mobile communication device
- EMR is not meant to be limiting, and may broadly refer to any or all aspects of the patient's medical record rendered in a digital format.
- the EMR is supported by systems configured to co-ordinate the storage and retrieval of individual records with the aid of computing devices. As such, a variety of types of healthcare-related information may be stored and accessed in this way.
- the EMR may store one or more of the following types of information: patient demographic; medical history (e.g., examination and progress reports of health and illnesses); medicine and allergy lists/immunization status; laboratory test results, radiology images (e.g., X-rays, CTs, MRIs, etc.); evidence-based recommendations for specific medical conditions; a record of appointments and physician's notes; billing records; and data received from an associated medical device (e.g. alerts).
- medical history e.g., examination and progress reports of health and illnesses
- medicine and allergy lists/immunization status e.g., laboratory test results, radiology images (e.g., X-rays, CTs, MRIs, etc.); evidence-based recommendations for specific medical conditions; a record of appointments and physician's notes; billing records; and data received from an associated medical device (e.g. alerts).
- medical device e.g. alerts
- User device 210 receives and displays data from health information system 240 and EMR 250 and communicates or otherwise makes the data available to context engine 220 .
- User device 210 also allows a clinician to make voice communication calls, such as, for example, to other clinicians.
- health information system 240 and EMR 250 are illustrated in FIG. 2 as separate components of computing system 200 , it should be appreciated that one or more of these components may be included in a single computing device.
- Context engine 220 may reside on one or more computing devices, such as, for example, the control server 102 described above with reference to FIG. 1 , user device 210 , as shown in FIG. 2 , or health information system 240 .
- the control server 102 includes a computer processor and may be a server, personal computer, desktop computer, laptop computer, handheld device, mobile device, consumer electronic device, or the like.
- Context engine 220 comprises, in various embodiments, selection component 221 , context component 222 , indication component 223 , contact component 224 , attachment component 225 , item selection component 226 , and edit component 227 .
- selection component 221 receives a selection of one an alert from an alert list or one or more patients from a patient list.
- the alert list and the patient list are communicated from health information system 240 and/or EMR 250 via to the network to the user device 210 where the data is communicated to or otherwise shared with context engine 220 .
- the data is associated with alerts and/or one or more patients. These alerts and/or one or more patients may be organized in an alert list and a patient list, respectively.
- a first clinician may desire to discuss an alert or one or more patients with a second clinician. Accordingly, selection component 221 receives the selection made by the first clinician.
- context component 222 provides context associated with the alert, the one or more patients, or a combination thereof.
- the context may include the alert or patient demographic information.
- the context may further include additional information associated with the alert or patient demographic information, such as information received from health information system 240 or EMR 250 .
- the additional information may include protocols, encounter details, patient demographics, care team information, family contacts, insurance information, pharmacy information, and the like.
- the context provides the clinician with information associated with the selected alert or patient demographic information that can be attached to a call history associated with mobile voice communication for later use.
- indication component 223 receives an indication that the first clinician is initiating voice communication with a second clinician.
- the indication may be made by pressing a button or activating or triggering the phone (e.g., touch-activated screen, voice command, and the like) on the user device 210 .
- the first clinician Upon receiving the indication, the first clinician must select the recipient of the voice communication, or in this case, the second clinician.
- Contact component 224 receives a selection of the second clinician from a contact list.
- the contact list may be a list displayed on the user device 210 or may be contacts maintained by user device 210 or health information system 240 . Or the contact list may merely be a telephone number associated with the second clinician that is selected by the first clinician.
- the selection may be made by the first clinician selecting the second clinician from a contact list or call history displayed on the user device 210 , by voice command, or by manually dialing the telephone number associated with the second clinician.
- attachment component 225 attaches the context to a call history associated with the voice communication.
- the call history may be available on the user device 210 , or a device associated with the second clinician. Further, the call history may be communicated to medical information system 240 and/or stored in the EMR 250 . For clarity, the call history may be an item in the call history log of the user device that is associated with the voice communication between the first clinician and the second clinician.
- item selection component 226 receives a selection of an item from a call history associated with voice communication. For example, an item within the call history on user device 210 may be associated with a voice communication that did not have, or had incomplete or incorrect context attached to it. The clinician may be reviewing items in the call history and determine that context should be added, edited, or declined for a particular item. The clinician makes the appropriate selection and item selection component 226 receives the selection accordingly.
- edit component 227 receives a selection to decline, attach, or edit context associated with the item.
- Edit component 227 may cause a pop-up to appear, allowing the clinician to select an appropriate action.
- the clinician selects the appropriate action. For example, the clinician may just want to indicate that no context is necessary and selects to decline context. Or the clinician may determine that additional or different detail is necessary and selects to edit context. Or the clinician may determine that no context was attached and the item would provide later benefits if context were attached. In this example, the clinician selects to attach context.
- context selection component 221 upon receiving the selection to attach or edit context, receives a selection of the context to add or edit for the item.
- the context comprises an alert, one or more patients, or a combination thereof. This allows the clinician to select an alert, one or more patients (e.g., a first clinician discusses multiple patients with a second clinician), or a combination thereof to attach or edit for the item in the call history.
- attach component 225 attaches or edits the context associated with the item in accordance with the selection of the context.
- an illustrative screen display depicts list display area 400 that displays a patient list, in accordance with embodiments of the present invention.
- List display area includes a search bar 328 to search for a particular patient.
- List display area also includes unit organizers 310 , 314 for organizing the patient list by unit.
- List display are also includes demographic bar 312 , 316 that displays context associated with a particular patient.
- Context includes patient name 336 , date of birth 338 , allergies 340 , and location 342 .
- List display area further includes tabs 330 , 332 , 334 for displaying particular patients of a healthcare facility. For example, assigned tab 430 includes in the patient list patients that are assigned to the clinician using the mobile device.
- Units tab 332 includes in the patient list patients organized by unit (as depicted in FIG. 3 ). All tab 334 includes all patients in the patient list.
- List display area 300 also includes buttons 318 , 320 , 322 , 324 , 326 for displaying additional items.
- patients button 318 displays a patient list in the list display area 300 .
- Staff button 320 displays a staff list in the list display area 300 .
- Alerts button 322 displays an alert list in the list display area 300 .
- Messages button 324 displays a message list in the list display area 300 .
- More button 326 displays other list topics that can be displayed in the list display area 300 .
- other list topics can include any health care related topic that may be useful to a clinician utilizing a mobile device in a healthcare facility.
- Context display area 400 displays context associated with an alert, one or more patients, or a combination thereof.
- Context display area 400 may be utilized to select the desired context to add to a call history associated with voice communication. For example, a first clinician may desire to discuss a particular topic with a second clinician regarding a patient. In order to record the topic of discussion to the EMR, the first clinician selects the appropriate topic from context display area 400 .
- Context display area 400 allows the first clinician to review or select as detailed or general information as desired.
- context display area 400 includes patient information 412 , encounter details 418 , patient demographics 420 , care team 422 , family contacts 424 , insurance information 426 , and preferred pharmacy 428 .
- Call display area 414 displays an indicator for initiating a voice communication. Once the desired information is reviewed and/or selected, the first clinician can select the indicator from call display area 414 or the text message button 416 . The first clinician can return to list display area 300 by selecting the patients button 410 .
- an illustrative screen display depicts a contact display area 510 , in accordance with an embodiment of the present invention.
- the first clinician may desire to view, select, or communicate (e.g., call or text message) a member of the care team for a particular patient.
- call display area 514 By selecting either the care team 522 , call display area 514 , or text message button 516 causes a contact list to be displayed in the contact display area 510 on the first clinician's mobile device.
- call history display area 600 displays a call history or message history associated with a mobile device for a clinician.
- Attachment display area 612 displays the context attached to the call history 614 associated with the voice communication.
- an illustrative screen display depicts list display area 700 that displays an alert list, in accordance with embodiments of the present invention.
- List display area 700 includes tabs for displaying alerts by category. For example, alerts can be displayed according to a timeframe, such as recent 710 , or by severity. Or, all alerts related to a unit, a clinician, or a facility can be displayed.
- Context display area 800 displays context associated with an alert, one or more patients, or a combination thereof.
- Context display area includes patient information 810 .
- Context display area 800 includes alert details 816 , reminders 818 , and communication history 820 .
- Call display area 812 displays an indicator for initiating a voice communication. Once the desired information is reviewed and/or selected, the first clinician can select the indicator from call display area 812 or the group message button 814 . The first clinician can return to list display area 800 by selecting the patients button.
- an illustrative screen display depicts a contact display area 900 , in accordance with an embodiment of the present invention.
- the first clinician may desire to communicate (e.g., call or text message) a member of the care team for a particular patient.
- the call display area 912 or group message button 914 By selecting either the call display area 912 or group message button 914 causes a contact list to be displayed in the contact display area 900 on the first clinician's mobile device.
- Contact display area includes patient information 910 , alert information 920 , and a list of selectable or favorite contacts 930 .
- call history display area 1000 displays a call history or message history associated with a mobile device for a clinician.
- Attachment display area 1012 displays the context 1014 attached to the call history 1016 associated with the voice communication.
- call history display area 1100 includes history associated with voice communication and/or text message communication.
- Item display area 1112 further displays a patient button 1114 and an alert button 1116 for a particular item 1118 in the call history. The clinician may desire to select either the patient button 1114 or the alert button 1116 to add the desired context to the particular item 1118 .
- an illustrative screen display depicts a list display area 1200 , in accordance with embodiments of the present invention.
- List display area includes tabs 1210 , 1212 , 1214 for displaying alerts by category. For example, alerts can be displayed according to a timeframe, such as most recent 1210 , by severity 1212 . Or, all 1214 alerts related to a unit, a clinician, or a facility can be displayed. Lists 1216 , 1218 based on the category are displayed. Once the desired alert is selected, a done button 1220 allows the context to be attached to the particular item in the call history.
- call history display area 1300 displays a call history or message history associated with communication with another clinician 1310 .
- Attachment display area 1312 displays the context 1314 , 1316 attached to the call history 1318 associated with the voice communication.
- call history display area 1400 includes history associated with voice communication and/or text message communication.
- Item display area 1412 further displays a patient button 1414 and an alert button 1416 for a particular item 1418 in the call history.
- the clinician may desire to select either the patient button 1414 or the alert button 1416 to add the desired context to the particular item 1418 .
- an illustrative screen display depicts a list display area 1500 , in accordance with embodiments of the present invention.
- List display area includes tabs 1510 , 1512 , 1514 for displaying patients category. For example, patients can be displayed according to assignment 1510 , by unit 1512 . Or, all 1514 patients for a healthcare facility can be displayed. Lists 1516 , 1518 based on the category are displayed. Once the desired patient is selected, a done button 1520 allows the context to be attached to the particular item in the call history.
- call history display area 1600 displays a call history or message history associated with communication with another clinician 1610 .
- Attachment display area 1612 displays the context 1614 , 1616 attached to the call history 1618 associated with the voice communication.
- an illustrative screen display depicts a call history display area 1700 and a selection display area 1712 , in accordance with embodiments of the present invention.
- Call history display area 1700 displays a call history associated with voice communication.
- Selection display area 1712 displays an indicator for selecting to decline context to an item 1710 associated with the call history. Selecting to decline context to the item 1710 results in the display merely displaying the length of the communication, rather than including buttons for attaching context to the item.
- an illustrative screen display depicts a call history display area 1800 and a selection display area 1812 , in accordance with embodiments of the present invention.
- Call history display area 1800 displays a call history associated with voice communication.
- Selection display area 1812 displays an indicator for selecting to attach context to an item 1810 associated with the call history. Selecting to attach context to the item 1810 results allows the user to attach context to the item, as described herein.
- Upon selecting to attach context to the item 1810 displays a context area that displays context comprising an alert, one or more patients, or a combination thereof to associated with the item (as described herein).
- an illustrative screen display depicts a call history display area 1900 , a selection display area 1912 , and attachment display area in accordance with embodiments of the present invention.
- Call history display area 1900 displays a call history associated with voice communication.
- Selection display area displays an indicator for selecting to edit context to an item 1910 associated with the call history. Selecting to edit context to the item 1910 allows the user to edit context for the item.
- Upon selecting to edit context to the item 1910 displays a context area that displays context comprising an alert, one or more patients, or a combination thereof to associated with the item (as described herein for attaching context).
- Attachment display area displays the context associated with the item in accordance with the selection of content.
- an illustrative flow diagram 2000 is shown of a method for attaching patient context to mobile voice communication, in accordance with embodiments of the present invention.
- a selection of one of an alert from an alert list or one or more patients from a patient list is received.
- Context associated with the alert, the one or more patients, or a combination thereof is provided at step 2020 .
- an indication that a first clinician is initiating a voice communication with a second clinician is received.
- a selection of the second clinician is received, at step 2040 , from a contact list.
- the context is attached to a call history associated with the voice communication. The call history and attached context is stored in the EMR to be used for later purposes.
- a clinician is able to make a phone call while viewing patient details.
- the patient's demographic bar is present on the display. This bar indicates that the information the user is viewing is related to the patient. The bar also indicates that patient context is attached to any action made when it is present.
- the clinician makes a phone call or text message from a display that has a demographic bar (i.e., patient detail or alert detail display)
- the patient context is included in the message log and stored in the EMR for future analytics.
- an illustrative flow diagram 2100 is shown of a method for declining, attaching, or editing patient context to mobile voice communication, in accordance with embodiments of the present invention.
- a selection of an item from a call history associated with voice communication is received.
- a selection to decline, attach, or edit context associated with the item is received at step 2120 .
- a selection of the context to attach or edit is received at step 2130 .
- the context comprises an alert, one or more patients, or a combination thereof.
- the context to be associated with the item is attached or edited in accordance with the selection of the context. When the clinician is not viewing a patient's information while communicating with another clinician, a prompt is provided after the communication is complete.
- the prompt allows the user to attach patients or alerts (i.e., context) to the communication.
- patients or alerts i.e., context
- the clinician is able to include the patient or alert associated with the communication to the message history.
- the message history including the context, is stored in the EMR for future analytics.
Abstract
Systems, methods, and computer-readable media for declining, attaching, and editing patient context to mobile voice communication are provided. Patient demographic or alert information is attached to items within call histories associated with voice communication which are stored in the EMR and utilized for later analysis (e.g., analytics, patient progress, billing, reimbursement, staff scheduling, patient acuity, and the like). In embodiments, the context is declined, attached, or edited to items from the call history. In embodiments, the context is attached to items in the call history when the voice communication is initiated.
Description
- This application claims the benefit of U.S. Provisional Application No. 61/710,409, titled “MULTI-ACTION BUTTON FOR MOBILE DEVICES AND ATTACHING PATIENT CONTEXT TO A CALL HISTORY,” filed Oct. 5, 2012, which is hereby expressly incorporated by reference in its entirety. This application is related by subject matter to U.S. application No. (not yet assigned) (Attorney Docket Number CRNI.175281), entitled “ATTACHING PATIENT CONTEXT TO A CALL HISTORY ASSOCIATED WITH VOICE COMMUNICATION”, which is commonly assigned and filed on even date herewith, and is herein incorporated by reference in its entirety.
- Patient medical information, such as that contained in the EMR, allows health care providers to provide continuity of care to patients. Thus, it is critical for clinicians providing care to patients to review and collaborate with other clinicians for each patient's medical record. However, these collaborations, while important to providing care for patients, often goes undocumented because the ability to track mobile voice communication as well as the content discussed is not currently available. This results in confusion and an inability to reference the details (e.g. patient name, relevant alerts, and the like) of a mobile voice call and leaves the clinician and healthcare entity unable to appropriately track such information that may otherwise be useful in analytics, tracking patient progress, billing, reimbursement, scheduling staff, and patient acuity.
- Further, when receiving alerts regarding a particular patient, it is critical that these alerts are acknowledged in a timely manner. Often, it is necessary for an additional action to be taken in addition to acknowledging the alert. For example, the responding clinician may need to acknowledge (i.e., accept) the alert and call or text another clinician. Unfortunately, displays of current mobile devices are cluttered with option buttons which results in confusion and time lost pondering the correct action.
- This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
- Embodiments of the present invention relate to declining, attaching, and editing patient context to mobile voice communication. More particularly, patient demographic or alert information is attached to a call history which is stored in the electronic medical record (EMR) and utilized for later analysis (e.g., analytics, patient progress, billing, reimbursement, staff scheduling, patient acuity, and the like).
- Accordingly, in one embodiment, computer storage media storing computer-executable instructions that, when executed by one or more computing devices, cause the one or more computing devices to perform a method that facilitates attaching patient context to a call history associated with mobile voice communication is provided. A selection of one of an alert from an alert list or one or more patients from a patient list is received. Context associated with the alert, the one or more patients, or a combination thereof is provided. An indication that a first clinician is initiating a voice communication with a second clinician is received. A selection of the second clinician from a contact list is received. The context is attached to a call history associated with the voice communication.
- In another embodiment, a computer system to facilitate attaching patient context to a call history associated with mobile voice communication is provided. The computer system comprises a processor coupled to a computer storage medium, the computer storage medium having stored thereon a plurality of computer software components executable by the processor. A selection component receives a selection of one of an alert from an alert list or one or more patients from a patient list. A context component provides context associated with the alert, the one or more patients, or a combination thereof. An indication component receives an indication that a first clinician is initiating a voice communication with a second clinician. A contact component receives a selection of the second clinician from a contact list. An attachment component attaches the context to a call history associated with the voice communication.
- In another embodiment, computer storage media having computer-executable instructions embodied thereon that, when executed, produce a graphical user interface (GUI) to facilitate attaching patient context to a call history associated with mobile voice communication is provided. A list display area displays one of an alert list or a patient list. A context display area displays context associated with an alert, one or more patients, or a combination thereof. A call display area displays an indicator for initiating a voice communication. A contact display area displays a contact list. An attachment display area displays the context attached to the call history associated with the voice communication.
- The present invention is described in detail below with reference to the attached drawing figures, wherein:
-
FIG. 1 is a block diagram of an exemplary computing environment suitable for use in implementing the present invention; -
FIG. 2 is a block diagram of an exemplary system for declining, attaching, or editing patient context to mobile voice communication, in accordance with embodiments of the present invention; -
FIGS. 3-19 are illustrative graphical user interface displays of declining, attaching, or editing patient context to mobile voice communication, in accordance with embodiments of the present invention; -
FIG. 20 is a flow diagram showing a method for attaching patient context to mobile voice communication, in accordance with an embodiment of the present invention; and -
FIG. 21 is a flow diagram showing a method for declining, attaching, or editing patient context to mobile voice communication, in accordance with an embodiment of the present invention. - The subject matter of the present invention is described with specificity herein to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or combinations of steps similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the terms “step” and/or “block” may be used herein to connote different components of methods employed, the terms should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described.
- Embodiments of the present invention can positively impact health organizations' key imperatives in a variety of ways. Embodiments of the present invention provide context to voice communications that can be utilized in analytics, revealing trends, tracking resources, tracking patient progress, billing, reimbursement, scheduling staff, and patient acuity. Embodiments of the present invention provide multi-action buttons on mobile devices that can be utilized by clinicians to improve response time and availability.
- Referring now to the drawings in general, and initially to
FIG. 1 in particular, an exemplary computing system environment, for instance, a medical information computing system, on which embodiments of the present invention may be implemented is illustrated and designated generally asreference numeral 100. It will be understood and appreciated by those of ordinary skill in the art that the illustrated medical informationcomputing system environment 100 is merely an example of one suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the medical informationcomputing system environment 100 be interpreted as having any dependency or requirement relating to any single component or combination of components illustrated therein. - Embodiments of the present invention may be operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the present invention include, by way of example only, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above-mentioned systems or devices, and the like.
- Embodiments of the present invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Embodiments of the present invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in local and/or remote computer storage media including, by way of example only, memory storage devices.
- With continued reference to
FIG. 1 , the exemplarycomputing system environment 100 includes a general purpose computing device in the form of acontrol server 102. Components of thecontrol server 102 may include, without limitation, a processing unit, internal system memory, and a suitable system bus for coupling various system components, includingdatabase cluster 104, with thecontrol server 102. The system bus may be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus, using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronic Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, also known as Mezzanine bus. - The
control server 102 typically includes, or has access to, a variety of computer readable media, for instance,database cluster 104. Computer readable media can be any available media that may be accessed byserver 102, and includes volatile and nonvolatile media, as well as removable and non-removable media. By way of example, and not limitation, computer readable media may include computer storage media and communication media. Computer storage media may include, without limitation, volatile and nonvolatile media, as well as removable and nonremovable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. In this regard, computer storage media may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage device, or any other medium which can be used to store the desired information and which may be accessed by thecontrol server 102. Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. As used herein, the term “modulated data signal” refers to a signal that has one or more of its attributes set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above also may be included within the scope of computer readable media. - The computer storage media discussed above and illustrated in
FIG. 1 , includingdatabase cluster 104, provide storage of computer readable instructions, data structures, program modules, and other data for thecontrol server 102. Thecontrol server 102 may operate in acomputer network 106 using logical connections to one or moreremote computers 108.Remote computers 108 may be located at a variety of locations in a medical or research environment, for example, but not limited to, clinical laboratories, hospitals and other inpatient settings, veterinary environments, ambulatory settings, medical billing and financial offices, hospital administration settings, home health care environments, and clinicians' offices. Clinicians may include, but are not limited to, a treating physician or physicians, specialists such as surgeons, radiologists, cardiologists, and oncologists, emergency medical technicians, physicians' assistants, nurse practitioners, nurses, nurses' aides, pharmacists, dieticians, microbiologists, laboratory experts, genetic counselors, researchers, veterinarians, students, and the like. Theremote computers 108 may also be physically located in non-traditional medical care environments so that the entire health care community may be capable of integration on the network. Theremote computers 108 may be personal computers, mobile devices, servers, routers, network PCs, peer devices, other common network nodes, or the like, and may include some or all of the components described above in relation to thecontrol server 102. The devices can be personal digital assistants or other like devices. -
Exemplary computer networks 106 may include, without limitation, local area networks (LANs) and/or wide area networks (WANs). Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. When utilized in a WAN networking environment, thecontrol server 102 may include a modem or other means for establishing communications over the WAN, such as the Internet. In a networked environment, program modules or portions thereof may be stored in thecontrol server 102, in thedatabase cluster 104, or on any of theremote computers 108. For example, and not by way of limitation, various application programs may reside on the memory associated with any one or more of theremote computers 108. It will be appreciated by those of ordinary skill in the art that the network connections shown are exemplary and other means of establishing a communications link between the computers (e.g.,server 102 and remote computers 108) may be utilized. - In operation, a user may enter commands and information into the
control server 102 or convey the commands and information to thecontrol server 102 via one or more of theremote computers 108 through input devices, such as a keyboard, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad. Other input devices may include, without limitation, microphones, satellite dishes, scanners, or the like. Commands and information may also be sent directly from a remote healthcare device to thecontrol server 102. In addition to a monitor, thecontrol server 102 and/orremote computers 108 may include other peripheral output devices, such as speakers and a printer. - Although many other internal components of the
control server 102 and theremote computers 108 are not shown, those of ordinary skill in the art will appreciate that such components and their interconnections are well known. Accordingly, additional details concerning the internal construction of thecontrol server 102 and theremote computers 108 are not further disclosed herein. - With reference to
FIG. 2 , a block diagram is illustrated that shows an exemplary computing system architecture for implementing embodiments of the present invention. It will be appreciated that the computing system architecture shown inFIG. 2 is merely an example of one suitable computing system and is not intended as having any dependency or requirement related to any single module/component or combination of modules/components. - The
computing system 200 includes one or more user devices 210 (e.g., a mobile communication device),context engine 220,network 230,health information system 240, andEMR 250. As utilized herein, the acronym “EMR” is not meant to be limiting, and may broadly refer to any or all aspects of the patient's medical record rendered in a digital format. Generally, the EMR is supported by systems configured to co-ordinate the storage and retrieval of individual records with the aid of computing devices. As such, a variety of types of healthcare-related information may be stored and accessed in this way. By way of example, the EMR may store one or more of the following types of information: patient demographic; medical history (e.g., examination and progress reports of health and illnesses); medicine and allergy lists/immunization status; laboratory test results, radiology images (e.g., X-rays, CTs, MRIs, etc.); evidence-based recommendations for specific medical conditions; a record of appointments and physician's notes; billing records; and data received from an associated medical device (e.g. alerts). -
User device 210 receives and displays data fromhealth information system 240 andEMR 250 and communicates or otherwise makes the data available tocontext engine 220.User device 210 also allows a clinician to make voice communication calls, such as, for example, to other clinicians. Althoughhealth information system 240 andEMR 250 are illustrated inFIG. 2 as separate components ofcomputing system 200, it should be appreciated that one or more of these components may be included in a single computing device. -
Context engine 220 may reside on one or more computing devices, such as, for example, thecontrol server 102 described above with reference toFIG. 1 ,user device 210, as shown inFIG. 2 , orhealth information system 240. By way of example, thecontrol server 102 includes a computer processor and may be a server, personal computer, desktop computer, laptop computer, handheld device, mobile device, consumer electronic device, or the like.Context engine 220 comprises, in various embodiments,selection component 221,context component 222,indication component 223,contact component 224,attachment component 225,item selection component 226, and editcomponent 227. - In one embodiment,
selection component 221 receives a selection of one an alert from an alert list or one or more patients from a patient list. As described above, the alert list and the patient list are communicated fromhealth information system 240 and/orEMR 250 via to the network to theuser device 210 where the data is communicated to or otherwise shared withcontext engine 220. In various embodiments, the data is associated with alerts and/or one or more patients. These alerts and/or one or more patients may be organized in an alert list and a patient list, respectively. A first clinician may desire to discuss an alert or one or more patients with a second clinician. Accordingly,selection component 221 receives the selection made by the first clinician. - In one embodiment,
context component 222 provides context associated with the alert, the one or more patients, or a combination thereof. The context may include the alert or patient demographic information. The context may further include additional information associated with the alert or patient demographic information, such as information received fromhealth information system 240 orEMR 250. The additional information may include protocols, encounter details, patient demographics, care team information, family contacts, insurance information, pharmacy information, and the like. The context provides the clinician with information associated with the selected alert or patient demographic information that can be attached to a call history associated with mobile voice communication for later use. - In one embodiment,
indication component 223 receives an indication that the first clinician is initiating voice communication with a second clinician. The indication may be made by pressing a button or activating or triggering the phone (e.g., touch-activated screen, voice command, and the like) on theuser device 210. Upon receiving the indication, the first clinician must select the recipient of the voice communication, or in this case, the second clinician.Contact component 224 receives a selection of the second clinician from a contact list. The contact list may be a list displayed on theuser device 210 or may be contacts maintained byuser device 210 orhealth information system 240. Or the contact list may merely be a telephone number associated with the second clinician that is selected by the first clinician. The selection may be made by the first clinician selecting the second clinician from a contact list or call history displayed on theuser device 210, by voice command, or by manually dialing the telephone number associated with the second clinician. - Once the contact is selected, in one embodiment,
attachment component 225 attaches the context to a call history associated with the voice communication. The call history may be available on theuser device 210, or a device associated with the second clinician. Further, the call history may be communicated tomedical information system 240 and/or stored in theEMR 250. For clarity, the call history may be an item in the call history log of the user device that is associated with the voice communication between the first clinician and the second clinician. - In one embodiment,
item selection component 226 receives a selection of an item from a call history associated with voice communication. For example, an item within the call history onuser device 210 may be associated with a voice communication that did not have, or had incomplete or incorrect context attached to it. The clinician may be reviewing items in the call history and determine that context should be added, edited, or declined for a particular item. The clinician makes the appropriate selection anditem selection component 226 receives the selection accordingly. - In one embodiment,
edit component 227 receives a selection to decline, attach, or edit context associated with the item.Edit component 227 may cause a pop-up to appear, allowing the clinician to select an appropriate action. After the clinician selects the item from the call history, the clinician selects the appropriate action. For example, the clinician may just want to indicate that no context is necessary and selects to decline context. Or the clinician may determine that additional or different detail is necessary and selects to edit context. Or the clinician may determine that no context was attached and the item would provide later benefits if context were attached. In this example, the clinician selects to attach context. - In one embodiment,
context selection component 221, upon receiving the selection to attach or edit context, receives a selection of the context to add or edit for the item. The context comprises an alert, one or more patients, or a combination thereof. This allows the clinician to select an alert, one or more patients (e.g., a first clinician discusses multiple patients with a second clinician), or a combination thereof to attach or edit for the item in the call history. In one embodiment, attachcomponent 225 attaches or edits the context associated with the item in accordance with the selection of the context. - Referring now to
FIG. 3 , an illustrative screen display depictslist display area 400 that displays a patient list, in accordance with embodiments of the present invention. List display area includes asearch bar 328 to search for a particular patient. List display area also includesunit organizers demographic bar patient name 336, date ofbirth 338,allergies 340, andlocation 342. List display area further includestabs Units tab 332 includes in the patient list patients organized by unit (as depicted inFIG. 3 ). All tab 334 includes all patients in the patient list.List display area 300 also includesbuttons patients button 318 displays a patient list in thelist display area 300.Staff button 320 displays a staff list in thelist display area 300.Alerts button 322 displays an alert list in thelist display area 300.Messages button 324 displays a message list in thelist display area 300.More button 326 displays other list topics that can be displayed in thelist display area 300. As can be appreciated, other list topics can include any health care related topic that may be useful to a clinician utilizing a mobile device in a healthcare facility. - Referring now to
FIG. 4 , illustrative screen display depictscontext display area 400, in accordance with embodiments of the present invention.Context display area 400 displays context associated with an alert, one or more patients, or a combination thereof.Context display area 400 may be utilized to select the desired context to add to a call history associated with voice communication. For example, a first clinician may desire to discuss a particular topic with a second clinician regarding a patient. In order to record the topic of discussion to the EMR, the first clinician selects the appropriate topic fromcontext display area 400.Context display area 400 allows the first clinician to review or select as detailed or general information as desired. For example,context display area 400 includespatient information 412, encounter details 418,patient demographics 420, care team 422, family contacts 424,insurance information 426, andpreferred pharmacy 428. Calldisplay area 414 displays an indicator for initiating a voice communication. Once the desired information is reviewed and/or selected, the first clinician can select the indicator fromcall display area 414 or thetext message button 416. The first clinician can return tolist display area 300 by selecting thepatients button 410. - Referring now to
FIG. 5 , an illustrative screen display depicts acontact display area 510, in accordance with an embodiment of the present invention. As mentioned above, the first clinician may desire to view, select, or communicate (e.g., call or text message) a member of the care team for a particular patient. By selecting either the care team 522, call display area 514, or text message button 516 causes a contact list to be displayed in thecontact display area 510 on the first clinician's mobile device. - Referring now to
FIG. 6 , illustrative screen display depicts callhistory display area 600, in accordance with embodiments of the present invention. Callhistory display area 600 displays a call history or message history associated with a mobile device for a clinician.Attachment display area 612 displays the context attached to thecall history 614 associated with the voice communication. - Referring now to
FIG. 7 , an illustrative screen display depictslist display area 700 that displays an alert list, in accordance with embodiments of the present invention.List display area 700 includes tabs for displaying alerts by category. For example, alerts can be displayed according to a timeframe, such as recent 710, or by severity. Or, all alerts related to a unit, a clinician, or a facility can be displayed. - Referring now to
FIG. 8 , an illustrative screen display depictscontext display area 800, in accordance with embodiments of the present invention.Context display area 800 displays context associated with an alert, one or more patients, or a combination thereof. Context display area includespatient information 810.Context display area 800 includesalert details 816,reminders 818, andcommunication history 820. Calldisplay area 812 displays an indicator for initiating a voice communication. Once the desired information is reviewed and/or selected, the first clinician can select the indicator fromcall display area 812 or thegroup message button 814. The first clinician can return tolist display area 800 by selecting the patients button. - Referring now to
FIG. 9 , an illustrative screen display depicts acontact display area 900, in accordance with an embodiment of the present invention. As mentioned above, the first clinician may desire to communicate (e.g., call or text message) a member of the care team for a particular patient. By selecting either the call display area 912 or group message button 914 causes a contact list to be displayed in thecontact display area 900 on the first clinician's mobile device. Contact display area includespatient information 910,alert information 920, and a list of selectable orfavorite contacts 930. - Referring now to
FIG. 10 , illustrative screen display depicts callhistory display area 1000, in accordance with embodiments of the present invention. Callhistory display area 1000 displays a call history or message history associated with a mobile device for a clinician.Attachment display area 1012 displays thecontext 1014 attached to thecall history 1016 associated with the voice communication. - Referring now to
FIG. 11 , an illustrative screen display depicts a callhistory display area 1100, in accordance with embodiments of the present invention. Callhistory display area 1100 includes history associated with voice communication and/or text message communication.Item display area 1112 further displays apatient button 1114 and analert button 1116 for aparticular item 1118 in the call history. The clinician may desire to select either thepatient button 1114 or thealert button 1116 to add the desired context to theparticular item 1118. - Referring now to
FIG. 12 , an illustrative screen display depicts alist display area 1200, in accordance with embodiments of the present invention. List display area includestabs severity 1212. Or, all 1214 alerts related to a unit, a clinician, or a facility can be displayed.Lists button 1220 allows the context to be attached to the particular item in the call history. - Referring now to
FIG. 13 , an illustrative screen display depicts callhistory display area 1300, in accordance with embodiments of the present invention. Callhistory display area 1300 displays a call history or message history associated with communication with anotherclinician 1310.Attachment display area 1312 displays thecontext call history 1318 associated with the voice communication. - Referring now to
FIG. 14 , an illustrative screen display depicts a callhistory display area 1400, in accordance with embodiments of the present invention. Callhistory display area 1400 includes history associated with voice communication and/or text message communication.Item display area 1412 further displays apatient button 1414 and analert button 1416 for aparticular item 1418 in the call history. The clinician may desire to select either thepatient button 1414 or thealert button 1416 to add the desired context to theparticular item 1418. - Referring now to
FIG. 15 , an illustrative screen display depicts alist display area 1500, in accordance with embodiments of the present invention. List display area includestabs assignment 1510, byunit 1512. Or, all 1514 patients for a healthcare facility can be displayed.Lists button 1520 allows the context to be attached to the particular item in the call history. - Referring now to
FIG. 16 , an illustrative screen display depicts callhistory display area 1600, in accordance with embodiments of the present invention. Callhistory display area 1600 displays a call history or message history associated with communication with anotherclinician 1610.Attachment display area 1612 displays thecontext 1614, 1616 attached to thecall history 1618 associated with the voice communication. - Referring now to
FIG. 17 , an illustrative screen display depicts a callhistory display area 1700 and aselection display area 1712, in accordance with embodiments of the present invention. Callhistory display area 1700 displays a call history associated with voice communication.Selection display area 1712 displays an indicator for selecting to decline context to anitem 1710 associated with the call history. Selecting to decline context to theitem 1710 results in the display merely displaying the length of the communication, rather than including buttons for attaching context to the item. - Referring now to
FIG. 18 , an illustrative screen display depicts a callhistory display area 1800 and a selection display area 1812, in accordance with embodiments of the present invention. Callhistory display area 1800 displays a call history associated with voice communication. Selection display area 1812 displays an indicator for selecting to attach context to anitem 1810 associated with the call history. Selecting to attach context to theitem 1810 results allows the user to attach context to the item, as described herein. Upon selecting to attach context to theitem 1810 displays a context area that displays context comprising an alert, one or more patients, or a combination thereof to associated with the item (as described herein). - Referring now to
FIG. 19 , an illustrative screen display depicts a callhistory display area 1900, aselection display area 1912, and attachment display area in accordance with embodiments of the present invention. Callhistory display area 1900 displays a call history associated with voice communication. Selection display area displays an indicator for selecting to edit context to anitem 1910 associated with the call history. Selecting to edit context to theitem 1910 allows the user to edit context for the item. Upon selecting to edit context to theitem 1910 displays a context area that displays context comprising an alert, one or more patients, or a combination thereof to associated with the item (as described herein for attaching context). Attachment display area displays the context associated with the item in accordance with the selection of content. - Referring now to
FIG. 20 , an illustrative flow diagram 2000 is shown of a method for attaching patient context to mobile voice communication, in accordance with embodiments of the present invention. Atstep 2010, a selection of one of an alert from an alert list or one or more patients from a patient list is received. Context associated with the alert, the one or more patients, or a combination thereof is provided atstep 2020. Atstep 2030, an indication that a first clinician is initiating a voice communication with a second clinician is received. A selection of the second clinician is received, atstep 2040, from a contact list. Atstep 2050, the context is attached to a call history associated with the voice communication. The call history and attached context is stored in the EMR to be used for later purposes. In embodiments, a clinician is able to make a phone call while viewing patient details. When the clinician is viewing a patient's information, the patient's demographic bar is present on the display. This bar indicates that the information the user is viewing is related to the patient. The bar also indicates that patient context is attached to any action made when it is present. Thus, as the clinician makes a phone call or text message from a display that has a demographic bar (i.e., patient detail or alert detail display), the patient context (alert and/or patient information) is included in the message log and stored in the EMR for future analytics. - Referring now to
FIG. 21 , an illustrative flow diagram 2100 is shown of a method for declining, attaching, or editing patient context to mobile voice communication, in accordance with embodiments of the present invention. Atstep 2110, a selection of an item from a call history associated with voice communication is received. A selection to decline, attach, or edit context associated with the item is received atstep 2120. A selection of the context to attach or edit is received atstep 2130. The context comprises an alert, one or more patients, or a combination thereof. Atstep 2140, the context to be associated with the item is attached or edited in accordance with the selection of the context. When the clinician is not viewing a patient's information while communicating with another clinician, a prompt is provided after the communication is complete. The prompt allows the user to attach patients or alerts (i.e., context) to the communication. By attaching the context to the communication, the clinician is able to include the patient or alert associated with the communication to the message history. The message history, including the context, is stored in the EMR for future analytics. - Many different arrangements of the various components depicted, as well as components not shown, are possible without departing from the scope of the claims below. Embodiments of our technology have been described with the intent to be illustrative rather than restrictive. Alternative embodiments will become apparent to readers of this disclosure after and because of reading it. Alternative means of implementing the aforementioned can be completed without departing from the scope of the claims below. Certain features and subcombinations are of utility and may be employed without reference to other features and subcombinations and are contemplated within the scope of the claims.
Claims (20)
1. One or more computer storage media storing computer-executable instructions that, when executed by one or more computing devices, cause the one or more computing devices to perform a method that facilitates attaching patient context to a call history associated with mobile voice communication:
receiving a selection of one of an alert from an alert list or one or more patients from a patient list;
providing context associated with the alert, the one or more patients, or a combination thereof;
receiving an indication that a first clinician is initiating a voice communication with a second clinician;
receiving a selection of the second clinician from a contact list;
attaching the context to a call history associated with the voice communication.
2. The media of claim 1 , wherein the alert list or patient list is communicated from a health information system and/or electronic medical record (EMR).
3. The media of claim 1 , wherein the context includes alert or patient demographic information.
4. The media of claim 1 , wherein the context includes one or more of protocols, encounter details, patient demographics, care team information, family contacts, insurance information, pharmacy information.
5. The media of claim 1 , further comprising communicating the call history to medical information system.
6. The media of claim 1 , further comprising storing the call history in an electronic medical record (EMR).
7. The media of claim 1 , wherein the call history is an item in the call history log of the user device that is associated with the voice communication between the first clinician and the second clinician.
8. The media of claim 6 , further comprising tracking patient progress.
9. The media of claim 6 , further comprising utilizing the call history for billing or reimbursement.
10. The media of claim 6 , further comprising utilizing the call history for scheduling staff.
11. A computer system to facilitate attaching patient context to a call history associated with mobile voice communication, the computer system comprising a processor coupled to a computer storage medium, the computer storage medium having stored thereon a plurality of computer software components executable by the processor, the computer software components comprising:
a selection component for receiving a selection of one of an alert from an alert list or one or more patients from a patient list;
a context component for providing context associated with the alert, the one or more patients, or a combination thereof;
an indication component for receiving an indication that a first clinician is initiating a voice communication with a second clinician;
a contact component for receiving a selection of the second clinician from a contact list;
an attachment component for attaching the context to a call history associated with the voice communication.
12. The system of claim 11 , further comprising an item selection component for receiving a selection of an item from the call history that the first clinician determines needs additional context.
13. The system of claim 12 , further comprising a context selection component for receiving additional context to add to the item.
14. Computer storage media having computer-executable instructions embodied thereon that, when executed, produce a graphical user interface (GUI) to facilitate attaching patient context to a call history associated with mobile voice communication, the GUI comprising:
a list display area that displays one of an alert list or a patient list;
a context display area that displays context associated with an alert, one or more patients, or a combination thereof;
a call display area that displays an indicator for initiating a voice communication;
a contact display area that displays a contact list; and
an attachment display area that displays the context attached to the call history associated with the voice communication.
15. The media of claim 14 , wherein the list display area further displays a search bar to search for a particular patient.
16. The media of claim 14 , wherein the list display area further displays unit organizers for organizing the patient list by unit.
17. The media of claim 14 , wherein the list display area further displays a demographic bar that displays context associated with a particular patient.
18. The media of claim 14 , wherein the list display area further displays buttons for displaying additional items, the additional items including a staff list, an alert list, a message list, and other topics.
19. The media of claim 14 , wherein the list display area further includes tabs for displaying particular patients of a healthcare facility, the particular patients including all patients assigned to the clinician, patients organized by unit, and all patients in the patient list.
20. The media of claim 14 , wherein the context includes one or more of patient name, date of birth, allergies, and location.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/711,206 US20140100873A1 (en) | 2012-10-05 | 2012-12-11 | Attaching patient context to a call history associated with voice communication |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261710409P | 2012-10-05 | 2012-10-05 | |
US13/711,206 US20140100873A1 (en) | 2012-10-05 | 2012-12-11 | Attaching patient context to a call history associated with voice communication |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140100873A1 true US20140100873A1 (en) | 2014-04-10 |
Family
ID=50432263
Family Applications (9)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/711,206 Abandoned US20140100873A1 (en) | 2012-10-05 | 2012-12-11 | Attaching patient context to a call history associated with voice communication |
US13/711,217 Active US8948734B2 (en) | 2012-10-05 | 2012-12-11 | Attaching patient context to a call history associated with voice communication |
US13/711,177 Active 2033-02-07 US9280637B2 (en) | 2012-10-05 | 2012-12-11 | Multi-action button for mobile devices |
US14/551,555 Active 2033-12-26 US11164673B2 (en) | 2012-10-05 | 2014-11-24 | Attaching patient context to a call history associated with voice communication |
US14/983,685 Active 2034-10-29 US10379713B2 (en) | 2012-10-05 | 2015-12-30 | Multi-action button for mobile devices |
US15/395,603 Active 2034-04-08 US10642460B2 (en) | 2012-10-05 | 2016-12-30 | Multi-action button for mobile devices |
US29/602,800 Active USD801373S1 (en) | 2012-10-05 | 2017-05-03 | Display screen or portion thereof with graphical user interface |
US16/439,012 Active US11232864B2 (en) | 2012-10-05 | 2019-06-12 | Multi-action button for mobile devices |
US16/828,361 Active US10978206B2 (en) | 2012-10-05 | 2020-03-24 | Multi-action button for mobile devices |
Family Applications After (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/711,217 Active US8948734B2 (en) | 2012-10-05 | 2012-12-11 | Attaching patient context to a call history associated with voice communication |
US13/711,177 Active 2033-02-07 US9280637B2 (en) | 2012-10-05 | 2012-12-11 | Multi-action button for mobile devices |
US14/551,555 Active 2033-12-26 US11164673B2 (en) | 2012-10-05 | 2014-11-24 | Attaching patient context to a call history associated with voice communication |
US14/983,685 Active 2034-10-29 US10379713B2 (en) | 2012-10-05 | 2015-12-30 | Multi-action button for mobile devices |
US15/395,603 Active 2034-04-08 US10642460B2 (en) | 2012-10-05 | 2016-12-30 | Multi-action button for mobile devices |
US29/602,800 Active USD801373S1 (en) | 2012-10-05 | 2017-05-03 | Display screen or portion thereof with graphical user interface |
US16/439,012 Active US11232864B2 (en) | 2012-10-05 | 2019-06-12 | Multi-action button for mobile devices |
US16/828,361 Active US10978206B2 (en) | 2012-10-05 | 2020-03-24 | Multi-action button for mobile devices |
Country Status (1)
Country | Link |
---|---|
US (9) | US20140100873A1 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160110040A1 (en) * | 2012-10-05 | 2016-04-21 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
WO2018119134A1 (en) * | 2016-12-23 | 2018-06-28 | Bueller Rnds, Inc. | Method and system to facilitate patient care |
US10275570B2 (en) | 2012-12-31 | 2019-04-30 | Cerner Innovation, Inc. | Closed loop alert management |
US10388413B2 (en) | 2015-12-30 | 2019-08-20 | Cerner Innovation, Inc. | Intelligent alert suppression |
US10580279B2 (en) | 2012-12-31 | 2020-03-03 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
US10607728B2 (en) | 2015-10-06 | 2020-03-31 | Cerner Innovation, Inc. | Alert optimizer |
US10957445B2 (en) | 2017-10-05 | 2021-03-23 | Hill-Rom Services, Inc. | Caregiver and staff information system |
Families Citing this family (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9495708B2 (en) | 2012-06-11 | 2016-11-15 | Acorns Grow Incorporated | Systems and methods for managing electronic interactive gaming-based investments |
US9749232B2 (en) | 2012-09-20 | 2017-08-29 | Masimo Corporation | Intelligent medical network edge router |
US8938223B2 (en) | 2012-12-20 | 2015-01-20 | Intel Corporation | Method to tag a phone call to communicate purpose of the call |
USD767605S1 (en) | 2013-03-15 | 2016-09-27 | Dexcom, Inc. | Display screen or portion thereof with a graphical user interface with icons |
USD778929S1 (en) * | 2013-03-15 | 2017-02-14 | Dexcom, Inc. | Display screen or portion thereof with graphical user interface |
US10832818B2 (en) * | 2013-10-11 | 2020-11-10 | Masimo Corporation | Alarm notification system |
WO2016001165A2 (en) | 2014-07-02 | 2016-01-07 | Doro AB | Improved communication |
ES2743429T3 (en) * | 2014-07-02 | 2020-02-19 | Doro AB | Group communication device |
US11507931B1 (en) | 2014-07-31 | 2022-11-22 | Block, Inc. | Payout payment platform |
USD789402S1 (en) * | 2014-09-01 | 2017-06-13 | Apple Inc. | Display screen or portion thereof with graphical user interface |
US9990613B1 (en) | 2014-12-12 | 2018-06-05 | Square, Inc. | Bill payment using direct funds transfer |
USD817965S1 (en) * | 2015-09-09 | 2018-05-15 | General Electric Company | Display screen with graphical user interface of an incubator |
US9860355B2 (en) | 2015-11-23 | 2018-01-02 | International Business Machines Corporation | Call context metadata |
USD817982S1 (en) * | 2016-04-20 | 2018-05-15 | Sorenson Ip Holdings Llc | Display screen or portion thereof with graphical user interface |
US9881296B1 (en) | 2016-09-12 | 2018-01-30 | Square, Inc. | Processing a mobile payload |
USD837227S1 (en) * | 2016-09-12 | 2019-01-01 | Square, Inc. | Display screen with graphical user interface for a mobile device |
US9871911B1 (en) | 2016-09-30 | 2018-01-16 | Microsoft Technology Licensing, Llc | Visualizations for interactions with external computing logic |
USD858545S1 (en) * | 2016-10-17 | 2019-09-03 | Navy Federal Credit Union | Display screen or portion thereof with graphical user interface |
USD837259S1 (en) * | 2016-11-28 | 2019-01-01 | Amazon Technologies, Inc. | Display screen having a graphical user interface or portion thereof |
USD824944S1 (en) * | 2017-02-10 | 2018-08-07 | General Electric Company | Display screen or portion thereof with graphical user interface |
USD845318S1 (en) * | 2017-02-28 | 2019-04-09 | Walmart Apollo, Llc | Display screen with a graphical user interface |
USD838732S1 (en) * | 2017-03-01 | 2019-01-22 | Facebook, Inc. | Display screen with a graphical user interface for an advertisement management application |
USD853408S1 (en) * | 2017-03-31 | 2019-07-09 | Harman International Industries, Incorporated | Display screen or portion thereof with graphical user interface |
USD878402S1 (en) * | 2017-05-22 | 2020-03-17 | Subsplash Ip, Llc | Display screen or portion thereof with transitional graphical user interface |
USD835125S1 (en) * | 2017-05-31 | 2018-12-04 | Airwatch Llc | Display screen or portion thereof with transitional graphical user interface |
US10769594B2 (en) | 2017-06-01 | 2020-09-08 | Airwatch Llc | Dynamically generated configuration profiles based on device operating system |
USD841677S1 (en) * | 2017-06-04 | 2019-02-26 | Apple Inc. | Display screen or portion thereof with graphical user interface |
USD877758S1 (en) * | 2017-06-09 | 2020-03-10 | Microsoft Corporation | Display screen with graphical user interface |
USD875750S1 (en) * | 2017-06-09 | 2020-02-18 | Microsoft Corporation | Display screen with animated graphical user interface |
USD833457S1 (en) * | 2017-07-19 | 2018-11-13 | Lenovo (Beijing) Co., Ltd. | Display screen or a portion thereof with graphical user interface |
USD868808S1 (en) | 2017-09-19 | 2019-12-03 | Robert Bosch Tool Corporation | Display screen or portion thereof with a graphical user interface |
USD869476S1 (en) * | 2017-09-19 | 2019-12-10 | Robert Bosch Tool Corporation | Display screen or portion thereof with graphical user interface |
USD854562S1 (en) * | 2017-10-13 | 2019-07-23 | Facebook, Inc. | Display screen with graphical user interface for games in messaging applications |
USD903708S1 (en) * | 2018-02-21 | 2020-12-01 | Randol Poueriet | Display screen or portion thereof with graphical user interface with icons |
EP3782165A1 (en) | 2018-04-19 | 2021-02-24 | Masimo Corporation | Mobile patient alarm display |
USD931310S1 (en) | 2018-05-18 | 2021-09-21 | Carefusion 303, Inc. | Display screen with graphical user interface for an infusion device |
USD930017S1 (en) * | 2018-05-18 | 2021-09-07 | Carefusion 303, Inc. | Display screen of an infusion device with graphical user interface |
USD897361S1 (en) * | 2018-05-18 | 2020-09-29 | Carefusion 303, Inc. | Display screen of a modular infusion device with transitional graphical user interface |
USD880495S1 (en) | 2018-06-03 | 2020-04-07 | Apple Inc. | Electronic device with graphical user interface |
USD910064S1 (en) * | 2018-10-02 | 2021-02-09 | Facebook, Inc. | Display screen with animated graphical user interface |
USD910694S1 (en) * | 2018-10-30 | 2021-02-16 | Google Llc | Display screen with graphical user interface |
US11095740B2 (en) | 2019-04-18 | 2021-08-17 | Bank Of America Corporation | Two-way push notification of activity events through a wireless device |
USD944292S1 (en) * | 2019-09-02 | 2022-02-22 | Koninklijke Philips N.V. | Display screen or portion thereof with animated graphical user interface |
USD947237S1 (en) * | 2020-03-02 | 2022-03-29 | Koninklijke Philips N.V. | Display screen or portion thereof with animated graphical user interface |
USD942994S1 (en) * | 2020-06-21 | 2022-02-08 | Apple Inc. | Display screen or portion thereof with graphical user interface |
USD1023036S1 (en) | 2022-09-15 | 2024-04-16 | FindSatoshi Lab Limited | Display screen or portion thereof with graphical user interface |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050065817A1 (en) * | 2002-04-30 | 2005-03-24 | Mihai Dan M. | Separation of validated information and functions in a healthcare system |
US7035623B2 (en) * | 2002-02-01 | 2006-04-25 | Microsoft Corporation | System and method for creating a note related to a phone call |
US20110208816A1 (en) * | 2010-02-19 | 2011-08-25 | Avaya Inc. | Contextual summary of recent communications method and apparatus |
US8165893B1 (en) * | 2005-02-16 | 2012-04-24 | Ideal Life Inc. | Medical monitoring and coordinated care system |
US20120101847A1 (en) * | 2010-10-20 | 2012-04-26 | Jacob Johnson | Mobile Medical Information System and Methods of Use |
US20130085798A1 (en) * | 2011-09-30 | 2013-04-04 | Varian Medical Systems, Inc. | Systems and methods for implementing medical workflow |
US20130183923A1 (en) * | 2012-01-16 | 2013-07-18 | Charles Cameron Brackett | Field nurse notification |
US20140051399A1 (en) * | 2012-08-20 | 2014-02-20 | Research In Motion Limited | Methods and devices for storing recognized phrases |
US8886663B2 (en) * | 2008-09-20 | 2014-11-11 | Securus Technologies, Inc. | Multi-party conversation analyzer and logger |
Family Cites Families (209)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US1039713A (en) | 1910-10-29 | 1912-10-01 | William S Eaton | Etching-machine. |
US4237344A (en) | 1979-04-20 | 1980-12-02 | Hospital Communication Systems, Inc. | Rapid response health care communications system |
EP0550517B1 (en) | 1990-08-31 | 1998-12-23 | The General Hospital Corporation | A system for managing multiple devices, for example, portable patient monitoring devices in a network |
US5319355A (en) | 1991-03-06 | 1994-06-07 | Russek Linda G | Alarm for patient monitor and life support equipment system |
US20010011224A1 (en) | 1995-06-07 | 2001-08-02 | Stephen James Brown | Modular microprocessor-based health monitoring system |
US5942986A (en) | 1995-08-09 | 1999-08-24 | Cedars-Sinai Medical Center | System and method for automatic critical event notification |
GB9522872D0 (en) | 1995-11-08 | 1996-01-10 | Oxford Medical Ltd | Improvements relating to physiological monitoring |
US7256708B2 (en) | 1999-06-23 | 2007-08-14 | Visicu, Inc. | Telecommunications network for remote patient monitoring |
US7454359B2 (en) | 1999-06-23 | 2008-11-18 | Visicu, Inc. | System and method for displaying a health status of hospitalized patients |
US8175895B2 (en) | 1999-06-23 | 2012-05-08 | Koninklijke Philips Electronics N.V. | Remote command center for patient monitoring |
US7315825B2 (en) | 1999-06-23 | 2008-01-01 | Visicu, Inc. | Rules-based patient care system for use in healthcare locations |
US7321862B2 (en) | 1999-06-23 | 2008-01-22 | Visicu, Inc. | System and method for patient-worn monitoring of patients in geographically dispersed health care locations |
US7475019B2 (en) | 1999-11-18 | 2009-01-06 | Visicu, Inc. | System and method for physician note creation and management |
US6804656B1 (en) | 1999-06-23 | 2004-10-12 | Visicu, Inc. | System and method for providing continuous, expert network critical care services from a remote location(s) |
US7090053B2 (en) | 1999-07-13 | 2006-08-15 | Bothwell Enterprises, Inc. | Scaffold plank with end connector and method of making the same |
AU6802000A (en) | 1999-09-13 | 2001-04-30 | Healinx | A message and program system supporting communication |
US7933780B2 (en) * | 1999-10-22 | 2011-04-26 | Telaric, Llc | Method and apparatus for controlling an infusion pump or the like |
US20020040282A1 (en) | 2000-03-22 | 2002-04-04 | Bailey Thomas C. | Drug monitoring and alerting system |
GB0016561D0 (en) | 2000-07-05 | 2000-08-23 | Rolls Royce Plc | Health monitoring |
US7249036B2 (en) | 2000-07-06 | 2007-07-24 | Cary Gresham Bayne | Method for clinician house calls utilizing portable computing and communications equipment |
US7225408B2 (en) | 2001-04-27 | 2007-05-29 | Siemens Medical Solutions Health Services Corporation | System and user interface for communicating and processing patient record information |
US6754516B2 (en) | 2001-07-19 | 2004-06-22 | Nellcor Puritan Bennett Incorporated | Nuisance alarm reductions in a physiological monitor |
US7224281B2 (en) | 2001-08-31 | 2007-05-29 | Draeger Medical Systems, Inc. | Patient monitoring and alarm processing system and user interface |
US20110295621A1 (en) | 2001-11-02 | 2011-12-01 | Siemens Medical Solutions Usa, Inc. | Healthcare Information Technology System for Predicting and Preventing Adverse Events |
US20040073453A1 (en) | 2002-01-10 | 2004-04-15 | Nenov Valeriy I. | Method and system for dispensing communication devices to provide access to patient-related information |
US7034691B1 (en) | 2002-01-25 | 2006-04-25 | Solvetech Corporation | Adaptive communication methods and systems for facilitating the gathering, distribution and delivery of information related to medical care |
US8775196B2 (en) | 2002-01-29 | 2014-07-08 | Baxter International Inc. | System and method for notification and escalation of medical data |
US8250483B2 (en) * | 2002-02-28 | 2012-08-21 | Smiths Medical Asd, Inc. | Programmable medical infusion pump displaying a banner |
US20030191730A1 (en) | 2002-04-05 | 2003-10-09 | Compaq Information Technologies Group, L.P. | Unobtrusive rule-based computer usage enhancement system |
US20050146431A1 (en) | 2003-12-31 | 2005-07-07 | Ge Medical Systems Information Technologies, Inc. | Alarm notification system, receiver, and methods for providing live data |
US7301451B2 (en) * | 2003-12-31 | 2007-11-27 | Ge Medical Systems Information Technologies, Inc. | Notification alarm transfer methods, system, and device |
US7319386B2 (en) | 2004-08-02 | 2008-01-15 | Hill-Rom Services, Inc. | Configurable system for alerting caregivers |
US8092380B2 (en) | 2005-02-28 | 2012-01-10 | Rothman Healthcare Corporation | System and method for improving hospital patient care by providing a continual measurement of health |
US8618930B2 (en) * | 2005-03-11 | 2013-12-31 | Aframe Digital, Inc. | Mobile wireless customizable health and condition monitor |
WO2007052285A2 (en) | 2005-07-22 | 2007-05-10 | Yogesh Chunilal Rathod | Universal knowledge management and desktop search system |
USD551239S1 (en) | 2005-11-09 | 2007-09-18 | Microsoft Corporation | User interface for a portion of a display screen |
US7733224B2 (en) * | 2006-06-30 | 2010-06-08 | Bao Tran | Mesh network personal emergency response appliance |
US20100137693A1 (en) * | 2005-11-01 | 2010-06-03 | Fresenius Medical Care Holdings, Inc. | Methods and systems for patient care |
USD577734S1 (en) | 2006-01-04 | 2008-09-30 | Samsung Electronics Co., Ltd. | Display panel with a pop-up window for a user interface |
US20070239488A1 (en) * | 2006-04-05 | 2007-10-11 | Derosso Robert | Computerized dental patient record |
US7430692B2 (en) | 2006-06-16 | 2008-09-30 | Siemens Medical Solutions Usa, Inc. | Processor operational status management system |
US9361769B2 (en) * | 2006-07-17 | 2016-06-07 | Eloquence Communications, Inc. | Method and system for advanced patient communication |
US9779209B2 (en) | 2006-07-24 | 2017-10-03 | Cerner Innovation, Inc. | Application to worker communication interface |
US20080027288A1 (en) * | 2006-07-31 | 2008-01-31 | Jorg Renz | RFID enabled apparatus for monitoring a medical status and a method thereof |
WO2008033970A2 (en) | 2006-09-14 | 2008-03-20 | Sloan Kettering Institute For Cancer Research | Automated association of patient care devices |
US7428189B2 (en) * | 2006-09-21 | 2008-09-23 | Joseph Thomas Hubicki | Electronic assistant and method |
US8160895B2 (en) | 2006-09-29 | 2012-04-17 | Cerner Innovation, Inc. | User interface for clinical decision support |
CA2666379A1 (en) | 2006-10-13 | 2008-04-17 | Michael Rothman & Associates | System and method for providing a health score for a patient |
GB0624081D0 (en) | 2006-12-01 | 2007-01-10 | Oxford Biosignals Ltd | Biomedical signal analysis method |
US8122006B2 (en) | 2007-05-29 | 2012-02-21 | Oracle International Corporation | Event processing query language including retain clause |
USD620020S1 (en) | 2007-06-23 | 2010-07-20 | Apple Inc. | Graphical user interface for a display screen or portion thereof |
US10115171B2 (en) | 2007-07-10 | 2018-10-30 | Cerner Innovation, Inc. | Medication related task notification system |
US20090070765A1 (en) | 2007-09-11 | 2009-03-12 | Bea Systems, Inc. | Xml-based configuration for event processing networks |
USD610159S1 (en) | 2007-12-19 | 2010-02-16 | Joseph Matheny | Computer generated image for a display screen |
USD607004S1 (en) | 2007-12-19 | 2009-12-29 | Yahoo! Inc. | Graphical user interface for a display panel |
USD604740S1 (en) | 2007-12-19 | 2009-11-24 | Joseph Matheny | Computer generated image for a display screen |
US8423076B2 (en) | 2008-02-01 | 2013-04-16 | Lg Electronics Inc. | User interface for a mobile device |
USD596192S1 (en) | 2008-04-24 | 2009-07-14 | Htc Corporation | Graphic user interface for a display screen |
US8451101B2 (en) * | 2008-08-28 | 2013-05-28 | Vocollect, Inc. | Speech-driven patient care system with wearable devices |
USD624556S1 (en) | 2008-09-08 | 2010-09-28 | Apple Inc. | Graphical user interface for a display screen or portion thereof |
CA2739793A1 (en) | 2008-10-21 | 2010-04-29 | Rothman Healthcare Corporation | Methods of assessing risk based on medical data and uses thereof |
USD625317S1 (en) | 2008-11-04 | 2010-10-12 | Xerox Corporation | Ribbed title bar for a touch-based user interface for a display screen |
US8115640B2 (en) * | 2008-11-18 | 2012-02-14 | Pacesetter, Inc. | Implantable medical device alert management |
USD599813S1 (en) | 2008-11-25 | 2009-09-08 | Microsoft Corporation | Animated image for a portion of a display screen |
USD599812S1 (en) | 2008-11-25 | 2009-09-08 | Microsoft Corporation | Animated image for a portion of a display screen |
US20100223071A1 (en) * | 2009-03-02 | 2010-09-02 | Mckesson Financial Holdings Limited | Systems, methods, apparatuses, and computer program products for organizing patient information |
US9218454B2 (en) | 2009-03-04 | 2015-12-22 | Masimo Corporation | Medical monitoring system |
US8615291B2 (en) | 2009-03-13 | 2013-12-24 | National Institutes Of Health (Nih) | Method, system and computer program method for detection of pathological fluctuations of physiological signals to diagnose human illness |
USD631891S1 (en) | 2009-03-27 | 2011-02-01 | T-Mobile Usa, Inc. | Portion of a display screen with a user interface |
USD636401S1 (en) | 2009-03-27 | 2011-04-19 | T-Mobile Usa, Inc. | Portion of a display screen with a user interface |
USD636402S1 (en) | 2009-03-27 | 2011-04-19 | T-Mobile Usa, Inc. | Portion of a display screen with a user interface |
CA2765124C (en) * | 2009-06-08 | 2018-03-06 | Airstrip Ip Holdings, Llc | Systems and methods for viewing patient data |
WO2011026098A2 (en) * | 2009-08-31 | 2011-03-03 | Disruptive Ip, Inc. | System and method of patient flow and treatment management |
USD747343S1 (en) | 2009-09-30 | 2016-01-12 | Htc Corporation | Display screen with an animated graphical user interface |
USD686221S1 (en) | 2009-09-30 | 2013-07-16 | Htc Corporation | Display screen with graphic user interface |
US8886792B2 (en) | 2009-10-13 | 2014-11-11 | Cardiopulmonary Corp. | Method and apparatus for displaying and storing data from medical devices and alarming in response to triggers by a plurality of alarm types |
US8346572B2 (en) | 2009-11-04 | 2013-01-01 | Cerner Innovation, Inc. | Providing clinical information to clinicians |
US8632485B2 (en) | 2009-11-05 | 2014-01-21 | Fresenius Medical Care Holdings, Inc. | Patient treatment and monitoring systems and methods |
US8417662B2 (en) | 2010-02-18 | 2013-04-09 | The University Of Utah Research Foundation | Adjustable alert rules for medical personnel |
US8416085B2 (en) | 2010-02-18 | 2013-04-09 | The University Of Utah Research Foundation | Medical personnel alert rules based on grouping |
US8374988B2 (en) | 2010-02-18 | 2013-02-12 | The University Of Utah Research Foundation | Complex alert rules for a medical personnel alert system |
US9052809B2 (en) | 2010-05-26 | 2015-06-09 | General Electric Company | Systems and methods for situational application development and deployment with patient event monitoring |
USD640276S1 (en) | 2010-06-25 | 2011-06-21 | Microsoft Corporation | Display screen with user interface |
BR112012033288A2 (en) | 2010-06-25 | 2016-11-22 | Innovate Wireless Health Inc | medication administration system and method of compliance |
USD662507S1 (en) | 2010-07-22 | 2012-06-26 | Research In Motion Limited | Display screen with graphical user interface |
USD676858S1 (en) | 2010-09-01 | 2013-02-26 | Apple Inc. | Display screen or portion thereof with graphical user interface |
WO2012068565A2 (en) | 2010-11-19 | 2012-05-24 | Spacelabs Healthcare, Llc | System and method for transfer of primary alarm notification on patient monitoring systems |
USD682294S1 (en) | 2010-12-16 | 2013-05-14 | Cisco Technology, Inc. | Display screen with graphical user interface |
US20120169467A1 (en) * | 2010-12-31 | 2012-07-05 | Condra David L | Patient alert management system |
US8775535B2 (en) | 2011-01-18 | 2014-07-08 | Voxilate, Inc. | System and method for the transmission and management of short voice messages |
US9916420B2 (en) | 2011-02-18 | 2018-03-13 | Nuance Communications, Inc. | Physician and clinical documentation specialist workflow integration |
USD665399S1 (en) | 2011-02-25 | 2012-08-14 | Microsoft Corporation | Display screen with graphical user interface |
AU2012225814A1 (en) | 2011-03-04 | 2013-09-19 | Stryker Corporation | Sensing system for patient supports |
US20120284040A1 (en) * | 2011-04-26 | 2012-11-08 | Kenneth Joe Dupin | Medical Modules and Monitoring Systems |
USD682844S1 (en) | 2011-06-06 | 2013-05-21 | Sony Corporation | Audio video display device with user interface |
US8417233B2 (en) * | 2011-06-13 | 2013-04-09 | Mercury Mobile, Llc | Automated notation techniques implemented via mobile devices and/or computer networks |
USD696682S1 (en) | 2011-06-16 | 2013-12-31 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with a graphical user interface |
US8618927B2 (en) | 2011-08-24 | 2013-12-31 | At&T Intellectual Property I, L.P. | Methods, systems, and products for notifications in security systems |
US9020476B2 (en) * | 2011-09-12 | 2015-04-28 | Leipzig Technology, Llc | System and method for remote care and monitoring using a mobile device |
USD691164S1 (en) | 2011-09-30 | 2013-10-08 | Life Technologies Corporation | Display screen with graphical user interface |
US20130085765A1 (en) | 2011-09-30 | 2013-04-04 | Charles Tuchinda | System and method for providing customized alert settings |
US8856156B1 (en) | 2011-10-07 | 2014-10-07 | Cerner Innovation, Inc. | Ontology mapper |
US8949738B2 (en) | 2011-10-20 | 2015-02-03 | Verizon Patent And Licensing Inc. | Drug calendar and reminder system |
USD700914S1 (en) | 2011-10-20 | 2014-03-11 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US20130103768A1 (en) | 2011-10-24 | 2013-04-25 | Peter Freebeck | Physician mobile communications system and method |
USD695773S1 (en) | 2011-11-03 | 2013-12-17 | Aliphcom | Display screen or portion thereof with graphical user interface |
USD701221S1 (en) | 2011-11-16 | 2014-03-18 | Hewlett-Packard Development Company, L.P. | Computing device display screen with computer-generated layout for a contacts interface |
USD682858S1 (en) | 2011-11-18 | 2013-05-21 | Microsoft Corporation | Display screen with graphical user interface |
US9098604B2 (en) * | 2011-12-22 | 2015-08-04 | General Electric Company | System and method for monitoring clinician responsiveness to alarms |
USD719577S1 (en) | 2011-12-27 | 2014-12-16 | Mitsubishi Electric Corporation | Display panel for an informational display |
USD717808S1 (en) | 2011-12-27 | 2014-11-18 | Mitsubishi Electric Corporation | Display panel with informational display |
USD714817S1 (en) | 2012-01-06 | 2014-10-07 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US9159313B2 (en) | 2012-04-03 | 2015-10-13 | Sony Corporation | Playback control apparatus, playback control method, and medium for playing a program including segments generated using speech synthesis and segments not generated using speech synthesis |
USD715820S1 (en) | 2012-05-04 | 2014-10-21 | Rebstock Consulting S.R.O. | Display screen with graphical user interface |
USD731528S1 (en) | 2012-05-15 | 2015-06-09 | Fujitsu Limited | Display with a graphical user interface |
USD705239S1 (en) | 2012-06-13 | 2014-05-20 | Microsoft Corporation | Display screen with graphical user interface |
USD726202S1 (en) | 2012-07-13 | 2015-04-07 | Thermo Electron Led Gmbh | Display screen of a centrifuge with graphical user interface |
USD720766S1 (en) | 2012-09-10 | 2015-01-06 | Lookout, Inc. | Mobile communication device display with graphical user interface comprising security and privacy advisor screens |
US20140070939A1 (en) * | 2012-09-12 | 2014-03-13 | Michael Halverson | Interactive wireless life safety communications system |
US9585565B2 (en) * | 2012-09-21 | 2017-03-07 | Covidien Lp | System, method, and software for automating physiologic displays and alerts with trending heuristics |
US20140100873A1 (en) * | 2012-10-05 | 2014-04-10 | Cerner Innovation, Inc. | Attaching patient context to a call history associated with voice communication |
USD743978S1 (en) | 2012-11-08 | 2015-11-24 | Uber Technologies, Inc. | Display screen of a computing device with a computer-generated electronic panel for providing confirmation for a service request |
USD734349S1 (en) | 2012-11-08 | 2015-07-14 | Uber Technologies, Inc. | Computing device with computer-generated information panel interface |
US9019099B2 (en) | 2012-11-12 | 2015-04-28 | Covidien Lp | Systems and methods for patient monitoring |
USD733175S1 (en) | 2012-11-28 | 2015-06-30 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US20140156291A1 (en) | 2012-11-30 | 2014-06-05 | Verizon Patent And Licensing Inc. | Methods and Systems for Facilitating Chronic Care of a Patient with a Chronic Medical Condition |
USD743414S1 (en) | 2012-12-03 | 2015-11-17 | Michael Shunock | Display screen with graphical user interface |
USD742909S1 (en) | 2012-12-05 | 2015-11-10 | Lg Electronics Inc. | Television receiver with graphical user interface |
USD743416S1 (en) | 2012-12-05 | 2015-11-17 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US10397162B2 (en) | 2012-12-14 | 2019-08-27 | Facebook, Inc. | Sending notifications to members of social group in a social networking system |
US10275570B2 (en) | 2012-12-31 | 2019-04-30 | Cerner Innovation, Inc. | Closed loop alert management |
US9185202B2 (en) | 2012-12-31 | 2015-11-10 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
AU350076S (en) | 2013-01-09 | 2013-08-02 | Samsung Electronics Co Ltd | Display screen for an electronic device |
US10635263B2 (en) | 2013-03-12 | 2020-04-28 | Gerald Douglas Hosier, JR. | Online systems and methods for advancing information organization sharing and collective action |
USD762676S1 (en) | 2013-03-13 | 2016-08-02 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
USD767605S1 (en) | 2013-03-15 | 2016-09-27 | Dexcom, Inc. | Display screen or portion thereof with a graphical user interface with icons |
USD778929S1 (en) | 2013-03-15 | 2017-02-14 | Dexcom, Inc. | Display screen or portion thereof with graphical user interface |
US9270624B2 (en) | 2013-05-10 | 2016-02-23 | Oracle International Corporation | Cloud messaging services optimization through adaptive message compression |
USD751097S1 (en) | 2013-05-14 | 2016-03-08 | Google Inc. | Display screen with graphical user interface |
USD736789S1 (en) | 2013-05-29 | 2015-08-18 | Microsoft Corporation | Display screen with graphical user interface |
US20140358585A1 (en) | 2013-06-04 | 2014-12-04 | Bruce Reiner | Method and apparatus for data recording, tracking, and analysis in critical results medical communication |
TWD182525S (en) | 2013-06-10 | 2017-04-21 | 蘋果公司 | Graphical user interface for a display screen |
USD752614S1 (en) | 2013-06-20 | 2016-03-29 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US10483003B1 (en) | 2013-08-12 | 2019-11-19 | Cerner Innovation, Inc. | Dynamically determining risk of clinical condition |
USD785003S1 (en) | 2013-09-03 | 2017-04-25 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
USD758400S1 (en) | 2013-09-03 | 2016-06-07 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
USD767587S1 (en) | 2013-09-03 | 2016-09-27 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US9830801B2 (en) | 2013-11-20 | 2017-11-28 | Medical Informatics Corp. | Alarm management system |
USD810115S1 (en) | 2013-11-22 | 2018-02-13 | Apple Inc. | Display screen or portion thereof with graphical user interface |
USD763881S1 (en) | 2013-11-22 | 2016-08-16 | Goldman, Sachs & Co. | Display screen or portion thereof with graphical user interface |
USD753707S1 (en) | 2013-11-26 | 2016-04-12 | Tencent Technology (Shenzhen) Company Limited | Display screen portion with animated graphical user interface |
US20150148617A1 (en) | 2013-11-27 | 2015-05-28 | General Electric Company | Method and system for selecting alarm reduction algorithm |
US9747778B2 (en) | 2013-12-17 | 2017-08-29 | Samsung Electronics Co. Ltd. | Context-aware compliance monitoring |
USD770491S1 (en) | 2014-01-03 | 2016-11-01 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
USD759687S1 (en) | 2014-01-21 | 2016-06-21 | Accompani, Inc. | Display screen with animated graphical user interface |
US9626479B2 (en) | 2014-01-27 | 2017-04-18 | Bernoulli Enterprise, Inc. | Systems, methods, user interfaces and analysis tools for supporting user-definable rules and smart rules and smart alerts notification engine |
USD763863S1 (en) | 2014-01-31 | 2016-08-16 | Genesys Telecommunications Laboratories, Inc. | Display screen with graphical user interface |
US20160360160A1 (en) | 2014-02-23 | 2016-12-08 | Catch Motion Inc. | Person wearable photo experience aggregator apparatuses, methods and systems |
US9355214B2 (en) | 2014-03-07 | 2016-05-31 | Globe Star, Inc. | False clinical alarm rate reduction |
USD757771S1 (en) | 2014-03-19 | 2016-05-31 | Wargaming.Net Limited | Display screen with transitional graphical user interface |
USD752604S1 (en) | 2014-04-25 | 2016-03-29 | Tencent Technology (Shenzhen) Company Limited | Portion of a display screen with graphical user interface |
USD763864S1 (en) | 2014-04-25 | 2016-08-16 | Huawei Device Co., Ltd. | Display screen with graphical user interface |
USD765110S1 (en) | 2014-04-25 | 2016-08-30 | Tencent Technology (Shenzhen) Company Limited | Portion of a display screen with animated graphical user interface |
USD763882S1 (en) | 2014-04-25 | 2016-08-16 | Tencent Technology (Shenzhen) Company Limited | Portion of a display screen with animated graphical user interface |
USD758386S1 (en) | 2014-04-29 | 2016-06-07 | Tencent Technology (Shenzhen) Company Limited | Portion of a display screen with an animated graphical user interface |
USD754679S1 (en) | 2014-05-08 | 2016-04-26 | Express Scripts, Inc. | Display screen with a graphical user interface |
USD777184S1 (en) | 2014-05-09 | 2017-01-24 | Tencent Technology (Shenzhen) Company Limited | Electronic device with graphical user interface |
USD753165S1 (en) | 2014-06-03 | 2016-04-05 | Microsoft Corporation | Display screen with graphical user interface |
WO2015186027A1 (en) | 2014-06-06 | 2015-12-10 | Koninklijke Philips N.V. | Unobtrusive advisors for patient monitor |
USD764511S1 (en) | 2014-06-30 | 2016-08-23 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with animated graphical user interface |
USD754176S1 (en) | 2014-06-30 | 2016-04-19 | Aliphcom | Display screen or portion thereof with graphical user interface |
US9706966B2 (en) | 2014-07-27 | 2017-07-18 | Oridion Medical 1987 Ltd. | Personalized patient alarm management |
USD781315S1 (en) | 2014-08-26 | 2017-03-14 | Tencent Technology (Shenzhen) Company Limited | Display screen portion with graphical user interface |
US9659482B2 (en) | 2014-09-02 | 2017-05-23 | Apple Inc. | Context-based alerts for an electronic device |
USD779517S1 (en) | 2014-09-11 | 2017-02-21 | Shuttersong Incorporated | Display screen or portion thereof with graphical user interface |
USD772259S1 (en) | 2014-09-25 | 2016-11-22 | Adp, Llc | Display screen or portion thereof with graphical user interface |
USD768647S1 (en) | 2014-11-14 | 2016-10-11 | Microsoft Corporation | Display screen with animated graphical user interface |
USD766952S1 (en) | 2014-12-09 | 2016-09-20 | Jpmorgan Chase Bank, N.A. | Display screen or portion thereof with a graphical user interface |
USD763290S1 (en) | 2014-12-17 | 2016-08-09 | Go Daddy Operating Company, LLC | Display screen with graphical user interface |
USD760738S1 (en) | 2015-01-15 | 2016-07-05 | SkyBell Technologies, Inc. | Display screen or a portion thereof with a graphical user interface |
USD771667S1 (en) | 2015-01-20 | 2016-11-15 | Microsoft Corporation | Display screen with graphical user interface |
USD771670S1 (en) | 2015-03-09 | 2016-11-15 | Apple Inc. | Display screen or portion thereof with animated graphical user interface |
USD775167S1 (en) | 2015-03-13 | 2016-12-27 | Adp, Llc | Display screen with graphical user interface |
USD797753S1 (en) | 2015-03-23 | 2017-09-19 | Google Inc. | Display panel portion with a graphical user interface |
USD766294S1 (en) | 2015-04-02 | 2016-09-13 | Kenneth Smith | Display screen with graphical user interface |
USD789956S1 (en) | 2015-04-16 | 2017-06-20 | Honeywell International Inc. | Display screen or portion thereof with graphical user interface |
USD780191S1 (en) | 2015-04-29 | 2017-02-28 | Elijah Kelley | Display screen with graphical user interface |
GB201509809D0 (en) | 2015-06-05 | 2015-07-22 | Isis Innovation | Method and apparatus for vital signs measurement |
USD772921S1 (en) | 2015-06-30 | 2016-11-29 | Xerox Corporation | Office machine screen with segmented control buttons graphical user interface |
US10686738B2 (en) | 2015-07-24 | 2020-06-16 | Facebook, Inc. | Providing personal assistant service via messaging |
USD777758S1 (en) | 2015-07-28 | 2017-01-31 | Microsoft Corporation | Display screen with graphical user interface |
USD784384S1 (en) | 2015-09-02 | 2017-04-18 | Samsung Electronics Co., Ltd. | Display screen or portion thereof with graphical user interface |
US10607728B2 (en) | 2015-10-06 | 2020-03-31 | Cerner Innovation, Inc. | Alert optimizer |
US10037411B2 (en) | 2015-12-30 | 2018-07-31 | Cerner Innovation, Inc. | Intelligent alert suppression |
USD789947S1 (en) | 2016-02-11 | 2017-06-20 | Sears Brands, L.L.C. | Display screen or portion thereof with graphical user interface |
USD789949S1 (en) | 2016-02-11 | 2017-06-20 | Sears Brands, L.L.C. | Display screen or portion thereof with graphical user interface |
USD819067S1 (en) | 2016-06-13 | 2018-05-29 | Apple Inc. | Display screen or portion thereof with graphical user interface |
USD882583S1 (en) | 2016-07-12 | 2020-04-28 | Google Llc | Display screen with graphical user interface |
USD807899S1 (en) | 2016-09-26 | 2018-01-16 | Uber Technologies, Inc. | Display screen with animated graphical user interface |
USD841660S1 (en) | 2016-10-27 | 2019-02-26 | Lifescan Ip Holdings, Llc | Display screen with computer icon for blood glucose monitoring |
USD844635S1 (en) | 2017-03-13 | 2019-04-02 | Episurf Ip Management Ab | Portion of a display screen with a graphical user interface |
US20180315428A1 (en) | 2017-04-27 | 2018-11-01 | 3Play Media, Inc. | Efficient transcription systems and methods |
US10992795B2 (en) | 2017-05-16 | 2021-04-27 | Apple Inc. | Methods and interfaces for home media control |
TWD194943S (en) | 2017-05-08 | 2018-12-21 | 大陸商北京搜狗科技發展有限公司 | Display graphical user interface of the screen |
USD824404S1 (en) | 2017-05-22 | 2018-07-31 | Conio Inc. | Display screen with animated graphical user interface |
USD859442S1 (en) | 2017-12-01 | 2019-09-10 | Beijing Didi Infinity Technology And Development Co., Ltd. | Display screen with animated graphical user interface |
US10573155B2 (en) * | 2017-12-07 | 2020-02-25 | Covidien Lp | Closed loop alarm management |
USD887439S1 (en) | 2018-08-31 | 2020-06-16 | Butterfly Network, Inc. | Display panel or portion thereof with graphical user interface |
USD890795S1 (en) | 2018-12-26 | 2020-07-21 | Yokogawa Electric Corporation | Measurement device display screen with transitional graphical user interface |
-
2012
- 2012-12-11 US US13/711,206 patent/US20140100873A1/en not_active Abandoned
- 2012-12-11 US US13/711,217 patent/US8948734B2/en active Active
- 2012-12-11 US US13/711,177 patent/US9280637B2/en active Active
-
2014
- 2014-11-24 US US14/551,555 patent/US11164673B2/en active Active
-
2015
- 2015-12-30 US US14/983,685 patent/US10379713B2/en active Active
-
2016
- 2016-12-30 US US15/395,603 patent/US10642460B2/en active Active
-
2017
- 2017-05-03 US US29/602,800 patent/USD801373S1/en active Active
-
2019
- 2019-06-12 US US16/439,012 patent/US11232864B2/en active Active
-
2020
- 2020-03-24 US US16/828,361 patent/US10978206B2/en active Active
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7035623B2 (en) * | 2002-02-01 | 2006-04-25 | Microsoft Corporation | System and method for creating a note related to a phone call |
US7035622B2 (en) * | 2002-02-01 | 2006-04-25 | Microsoft Corporation | System and method for creating a note related to a phone call |
US7215945B2 (en) * | 2002-02-01 | 2007-05-08 | Microsoft Corporation | System and method for creating a note related to a phone call |
US20050065817A1 (en) * | 2002-04-30 | 2005-03-24 | Mihai Dan M. | Separation of validated information and functions in a healthcare system |
US8165893B1 (en) * | 2005-02-16 | 2012-04-24 | Ideal Life Inc. | Medical monitoring and coordinated care system |
US8886663B2 (en) * | 2008-09-20 | 2014-11-11 | Securus Technologies, Inc. | Multi-party conversation analyzer and logger |
US20110208816A1 (en) * | 2010-02-19 | 2011-08-25 | Avaya Inc. | Contextual summary of recent communications method and apparatus |
US20120101847A1 (en) * | 2010-10-20 | 2012-04-26 | Jacob Johnson | Mobile Medical Information System and Methods of Use |
US20130085798A1 (en) * | 2011-09-30 | 2013-04-04 | Varian Medical Systems, Inc. | Systems and methods for implementing medical workflow |
US20130183923A1 (en) * | 2012-01-16 | 2013-07-18 | Charles Cameron Brackett | Field nurse notification |
US20140051399A1 (en) * | 2012-08-20 | 2014-02-20 | Research In Motion Limited | Methods and devices for storing recognized phrases |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10642460B2 (en) * | 2012-10-05 | 2020-05-05 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US20190294318A1 (en) * | 2012-10-05 | 2019-09-26 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US10978206B2 (en) * | 2012-10-05 | 2021-04-13 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US11232864B2 (en) * | 2012-10-05 | 2022-01-25 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US10379713B2 (en) * | 2012-10-05 | 2019-08-13 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US20160110040A1 (en) * | 2012-10-05 | 2016-04-21 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US20170109018A1 (en) * | 2012-10-05 | 2017-04-20 | Cerner Innovation, Inc. | Multi-Action Button for Mobile Devices |
US11164673B2 (en) | 2012-10-05 | 2021-11-02 | Cerner Innovation, Inc. | Attaching patient context to a call history associated with voice communication |
US10580279B2 (en) | 2012-12-31 | 2020-03-03 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
US10777059B2 (en) | 2012-12-31 | 2020-09-15 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
US10275570B2 (en) | 2012-12-31 | 2019-04-30 | Cerner Innovation, Inc. | Closed loop alert management |
US11342052B2 (en) | 2015-10-06 | 2022-05-24 | Cerner Innovation, Inc. | Alert optimizer |
US10607728B2 (en) | 2015-10-06 | 2020-03-31 | Cerner Innovation, Inc. | Alert optimizer |
US11749389B2 (en) | 2015-10-06 | 2023-09-05 | Cerner Innovation, Inc. | Alert optimizer |
US10388413B2 (en) | 2015-12-30 | 2019-08-20 | Cerner Innovation, Inc. | Intelligent alert suppression |
US11127498B2 (en) | 2015-12-30 | 2021-09-21 | Cerner Innovation, Inc. | Intelligent alert suppression |
US10699812B2 (en) | 2015-12-30 | 2020-06-30 | Cerner Innovation, Inc. | Intelligent alert suppression |
US11393578B2 (en) | 2016-12-23 | 2022-07-19 | Bueller Rnds, Inc. | Method and system to facilitate patient care |
WO2018119134A1 (en) * | 2016-12-23 | 2018-06-28 | Bueller Rnds, Inc. | Method and system to facilitate patient care |
US11817208B2 (en) | 2016-12-23 | 2023-11-14 | Bueller Rnds, Inc. | Method and system to facilitate patient care |
US10957445B2 (en) | 2017-10-05 | 2021-03-23 | Hill-Rom Services, Inc. | Caregiver and staff information system |
US11257588B2 (en) | 2017-10-05 | 2022-02-22 | Hill-Rom Services, Inc. | Caregiver and staff information system |
US11688511B2 (en) | 2017-10-05 | 2023-06-27 | Hill-Rom Services, Inc. | Caregiver and staff information system |
Also Published As
Publication number | Publication date |
---|---|
US9280637B2 (en) | 2016-03-08 |
US20140097961A1 (en) | 2014-04-10 |
US20200233564A1 (en) | 2020-07-23 |
US10978206B2 (en) | 2021-04-13 |
US10642460B2 (en) | 2020-05-05 |
US10379713B2 (en) | 2019-08-13 |
US20160110040A1 (en) | 2016-04-21 |
USD801373S1 (en) | 2017-10-31 |
US20170109018A1 (en) | 2017-04-20 |
US20140099929A1 (en) | 2014-04-10 |
US11232864B2 (en) | 2022-01-25 |
US20190294318A1 (en) | 2019-09-26 |
US8948734B2 (en) | 2015-02-03 |
US11164673B2 (en) | 2021-11-02 |
US20150081339A1 (en) | 2015-03-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11164673B2 (en) | Attaching patient context to a call history associated with voice communication | |
US10777059B2 (en) | Alert management utilizing mobile devices | |
Singh et al. | Timely follow-up of abnormal diagnostic imaging test results in an outpatient setting: are electronic medical records achieving their potential? | |
US10915222B2 (en) | Multi-disciplinary team workspace | |
US10275570B2 (en) | Closed loop alert management | |
US8560335B2 (en) | Viewing clinical activity details within a selected time period | |
US10402926B2 (en) | Multidevice collaboration | |
US20150100327A1 (en) | Maintaining context between applications utilizing a prioritized patient list | |
US20140278524A1 (en) | Associating patients and medical devices with a mobile device via bluetooth | |
US20140058748A1 (en) | Populating custom patient worklists using demographic and clinical criteria | |
US8751251B2 (en) | Key notifications in a clinical computing environment | |
US20080086684A1 (en) | Clinical activity navigator | |
US9785892B2 (en) | Automating displays based on admissions, discharges, and transfers | |
US10068302B2 (en) | Integrating video into patient workflows | |
US20150066521A1 (en) | Emergency department status display | |
US20080086334A1 (en) | Providing clinical activity details in context | |
US8423384B2 (en) | Providing multidisciplinary activities in context of clinician's role relevant activities | |
US20140278523A1 (en) | Dynamically associating and disassociating patients and medical devices | |
US20200126646A1 (en) | System and Method for Processing Healthcare Information | |
US20130110541A1 (en) | Social health networking | |
US11551791B2 (en) | Key note | |
Wilson | Understanding the technology that supports population health programs |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CERNER INNOVATION, INC., KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VAGLIO, JAY CHRISTOPHER;ANDERSON, MATT RYAN;REEL/FRAME:029448/0117 Effective date: 20121211 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |