US20220262529A9 - Clinical Notifications - Google Patents
Clinical Notifications Download PDFInfo
- Publication number
- US20220262529A9 US20220262529A9 US16/236,881 US201816236881A US2022262529A9 US 20220262529 A9 US20220262529 A9 US 20220262529A9 US 201816236881 A US201816236881 A US 201816236881A US 2022262529 A9 US2022262529 A9 US 2022262529A9
- Authority
- US
- United States
- Prior art keywords
- clinician
- notification
- control server
- clinical
- user
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 26
- 230000008569 process Effects 0.000 claims description 10
- 230000007170 pathology Effects 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 5
- 238000003745 diagnosis Methods 0.000 claims description 3
- 238000005259 measurement Methods 0.000 claims description 3
- 208000024891 symptom Diseases 0.000 claims description 3
- 238000001914 filtration Methods 0.000 claims 2
- 238000012360 testing method Methods 0.000 abstract description 9
- 230000009471 action Effects 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 25
- 230000002452 interceptive effect Effects 0.000 description 17
- 238000004891 communication Methods 0.000 description 14
- CVSVTCORWBXHQV-UHFFFAOYSA-N creatine Chemical compound NC(=[NH2+])N(C)CC([O-])=O CVSVTCORWBXHQV-UHFFFAOYSA-N 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 8
- 229960003624 creatine Drugs 0.000 description 4
- 239000006046 creatine Substances 0.000 description 4
- 230000001934 delay Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000007423 decrease Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 206010072970 Meniscus injury Diseases 0.000 description 1
- 230000001154 acute effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000002068 genetic effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 210000003127 knee Anatomy 0.000 description 1
- 238000009533 lab test Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/001—Apparatus specially adapted for cleaning or sterilising syringes or needles
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/142—Pressure infusion, e.g. using pumps
- A61M5/14244—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/142—Pressure infusion, e.g. using pumps
- A61M5/14244—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body
- A61M5/14248—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body of the skin patch type
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/158—Needles for infusions; Accessories therefor, e.g. for inserting infusion needles, or for holding them on the body
-
- 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
- G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
-
- H04L67/26—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M2005/1401—Functional features
- A61M2005/1402—Priming
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/142—Pressure infusion, e.g. using pumps
- A61M5/14244—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body
- A61M5/14248—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body of the skin patch type
- A61M2005/14252—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body of the skin patch type with needle insertion means
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/58—Means for facilitating use, e.g. by people with impaired vision
- A61M2205/582—Means for facilitating use, e.g. by people with impaired vision by tactile feedback
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/58—Means for facilitating use, e.g. by people with impaired vision
- A61M2205/583—Means for facilitating use, e.g. by people with impaired vision by visual feedback
-
- 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
Definitions
- test results are faxed to a physician.
- test results are entered into an individual's electronic medical chart, such as an EMR, and the clinician logs into the electronic medical chart to view the results.
- test results are delivered to the ordering physician or nurse by a telephone call.
- an MRI of the knee reveals a meniscus tear.
- the radiologist calls the ordering physician to provide results, and then dictates the report.
- the process is duplicate effort for the radiologist and requires phone availability from the ordering physician.
- Embodiments of the present invention provide methods and systems for performing providing clinical information for a person, such as a test result, immediately and the information automatically and immediately pushed to the ordering physician's Cerner-provisioned device(s) or personal device. It removes the manual processes that create bottlenecks in care today. Patients may begin treatment earlier, providing the greatest opportunity for positive outcomes.
- Input by the control server is received for a sign on for a user clinician and identification of a person being treated by the user clinician.
- the control server automatically generates one or more graphical user interfaces for displaying a medical order screen for the person being treated or list of persons being treated by the clinician and at least a graphical representation of one or more user selectable clinical notification options.
- Input is received by the control server representing a user selection of one or more of the user selectable clinical notification options.
- the user selection is compared to a subsequent medical data received for the one or more persons being treated via the control server.
- the subsequent medical data is analyzed to determine if it satisfies the user selection of the clinical notification option.
- the control server automatically generates in real time one or more graphical user interfaces for displaying the event notification of the subsequent medical data on a one or more clinician devices.
- input is received by the control server representing a user selection of a multiple medical devices selected to receive the clinical notification option.
- the control server in response to determining if the subsequent medical data satisfies the user selection of the clinical notification option, displays an event notification on the multiple medical devices selected to receive the clinical notification option.
- the event notification is filtered by the control server to remove the subsequent medical data about the one or more persons being treated by the user clinician.
- the medical order screen comprises a medical summary for the individual being treated by the clinician.
- the medical summary comprises patient vitas and measurements, reported symptoms, and prior diagnosis.
- the event notification in some aspects comprises critical alerts, vitals, and pathology results for the one or more persons being treated by the user clinician.
- the event notification may include subsequent medical data about the one or more persons being treated by the user clinician.
- control server receives input representing a user selection of the clinical notification option and a multiple medical devices selected to receive the notification.
- the control server automatically generates, in real time, one or more graphical user interfaces for displaying notification of data received for the person being treated on the multiple medical devices selected to receive the notification.
- only one medical device may be selected to receive the notification.
- a clinician may only want to be notified of critical results for an individual who they are treating but do not want non-critical results for the individual.
- This technology allows a medical worker to specify notification own to a patient, order and individual test result level so as not to over alert a medical worker. Additionally, the medical professional can specify devices for alerting. Each of these alerts occurring in real time, overcoming the slow process of traditional clinical notifications.
- the clinical notification management application provides a system for clinicians and ancillary users to subscribe to, push, and receive notifications related to their role in medical treatment in real time. Notifications can be sent and received for clinical results for individuals being treated. Notifications can also be pushed to a clinician based on a change in status of patient encounters, appointments, or rooms. A user clinician can provide preferences to receive notifications based on individual encounters, patients, locations, lists, and date ranges.
- the clinical notification management application in some embodiments, provides real time notifications of clinical information to clinicians and decreases delays in patient care.
- the clinical notification management application provides notifications outside of authenticated sessions (push notifications) without exposing protected health information (PHI) of individuals. This technology eliminates or reduces dependency of manual processes to communicate clinical results or status changes.
- the one or more graphical user interfaces with the subsequent medical data are displayed only when the user clinician authenticates on at least one of the multiple medical devices.
- the clinician does not have to log into an individual's EMR or wait for a fax or telephone call to determine clinical information for the individual, such as test results.
- the clinical notification management application provides real time notifications of clinical information to clinicians and decreases delays in patient care.
- the clinical notification management application provides notifications outside of authenticated sessions (push notifications) without exposing protected health information (PHI) of individuals.
- the notification is sent to a selection of the multiple medical devices selected by the user.
- the selection of multiple medical devices is determined by the control server based on device preference of the user. This can include information about the device including location.
- a notification route is generated to deliver an event notification of the one or more clinician devices. The notification route may be generated by the control server in real time based on device data such as location of the device, date range, and notification type.
- the claimed solution is necessarily rooted in computerized electronic medical relational database technology in order to overcome a problem specifically arising in the realm of computer medical clinical notification and communication.
- the claims address the problem of quickly and efficiently notifying a clinician of clinical information even when a user is not logged into an individual's electronic medical record.
- the claimed system and method of the present application represents a new paradigm notifying clinicians in a real time manner. Not only does the claimed invention provide a way for a user to receive real time notifications of clinical results, the user can specify what user device to push notification. The user can also choose to receive notification when entering an order into an individual's electronic medical record.
- the method and system for providing the user with the capability decide what notifications he/she wants to receive about what individuals and what devices to push the notifications.
- the clinical notification management application according to the new technology saves time and costs as clinical information is communicated to a user clinician in a manner defined by the user clinician.
- FIG. 1 is a block diagram of an exemplary computing environment suitable to implement embodiments of the present invention
- FIG. 2 is an exemplary system architecture suitable to implement embodiments of the present invention
- FIG. 3 is an exemplary system architecture suitable to implement embodiments of the present invention.
- FIG. 4 is a flow diagram depicting a process to provide clinical notifications to a clinician
- FIG. 5 is an exemplary block diagram depicting where clinical notifications are to be provided to a clinician
- FIG. 6 is an interactive graphical user interface depicting a medical summary of an individual to a clinician
- FIG. 7 is an interactive graphical user interface displaying user selectable notification options for an individual to a clinician
- FIG. 8 is an interactive graphical user interface displaying user selectable options for a list of individuals being treated
- FIG. 9 is an interactive graphical user interface displaying user selectable options of individuals being treated.
- FIG. 10 is an interactive graphical user interface displaying user selectable notification options for individuals being treated
- FIG. 11 is an interactive graphical user interface with an order summary for an individual
- FIG. 12 is an interactive graphical user interface for a clinician to create an order for an individual
- FIG. 13 is an interactive graphical user interface for a clinician to select notifications of results from an order being created
- FIG. 14 is an interactive graphical user interface for a clinician to sign an order created for an individual.
- FIG. 15 is an interactive graphical user interface for displaying notifications to a clinician.
- the present invention overcomes the delay in clinical notifications of previous clinical notification options.
- Previous clinical notification options rely on human interaction, sending alerts via phone calls and pagers by nurses or assistants. These notification options are slow because they require human oversight and input to contact clinicians and caregivers. Further, old notification options can be indiscrete—without verification the clinician is the one viewing what can be sensitive patient material.
- Embodiments of the present invention allow users to select the notification to receive that is instantaneous and in real time. These notifications can be sent only to devices the user selects, or notifications can be sent to a selection of devices based on various data available to the control server.
- notifications can be filtered from all sensitive medical data about a patient, only allowing a clinician to be notified of basic information such as results are in for a particular test. All of these features provide a faster, more reliable, and secure means to provide clinician notifications that overcome many of the failings of older notification solutions.
- the computing environment 100 comprises a computing device in the form of a control server 102 .
- Exemplary components of the control server 102 comprise a processing unit, internal system memory, and a suitable system bus for coupling various system components, including data store 104 , with the control server 102 .
- the system bus might 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.
- Exemplary architectures comprise 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 therein, or has access to, a variety of non-transitory computer-readable media.
- Computer-readable media can be any available media that might be accessed by control server 102 , and includes volatile and nonvolatile media, as well as, removable and nonremovable media.
- Computer-readable media may comprise computer storage media and communication media.
- Computer storage media includes both volatile and nonvolatile, removable and non-removable 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 includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by 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 includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics 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 should also be included within the scope of computer-readable media.
- the control server 102 might operate in a computer network 106 using logical connections to one or more remote computers 108 .
- Remote computers 108 might be located at a variety of locations in a medical or research environment, including clinical laboratories (e.g., molecular diagnostic laboratories), hospitals and other inpatient settings, veterinary environments, ambulatory settings, medical billing and financial offices, hospital administration settings, home healthcare environments, and clinicians' offices.
- Clinicians may comprise 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; laboratory technologists; genetic counselors; researchers; veterinarians; students; and the like.
- the remote computers 108 might also be physically located in nontraditional medical care environments so that the entire healthcare community might be capable of integration on the network.
- the remote computers 108 might be personal computers, servers, routers, network PCs, peer devices, other common network nodes, or the like and might comprise some or all of the elements described above in relation to the control server 102 .
- the devices can be personal digital assistants or other like devices.
- Computer networks 106 comprise 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 When utilized in a WAN networking environment, the control server 102 might comprise a modem or other means for establishing communications over the WAN, such as the Internet.
- program modules or portions thereof might be stored in association with the control server 102 , the data store 104 , or 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 . 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., control server 102 and remote computers 108 ) might be utilized.
- an organization might 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 microphone (e.g., voice inputs), a touch screen, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad.
- input devices such as a keyboard, a microphone (e.g., voice inputs), a touch screen, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad.
- Other input devices comprise satellite dishes, scanners, or the like. Commands and information might also be sent directly from a remote healthcare device to the control server 102 .
- the control server 102 and/or remote computers 108 might comprise other peripheral output devices, such as speakers and a printer.
- control server 102 and the remote computers 108 are not shown, such components and their interconnection 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.
- Embodiments of the present invention may be implemented in a cloud-computing environment as shown in FIG. 2 .
- the cloud-computing network may comprise single or multiple servers running single or multiple virtual machines.
- a computer environment is depicted for managing and providing clinical notifications to a clinician for individuals being medically treated.
- Control server 102 hosts clinical notification management application in a cloud computing environment. Tasks performed by the processor utilize a variety of computer technology.
- the control server are three tiers: a web server, application server and database server. Each tier is comprised of a number of system layers as described below.
- a clinical notification system 300 includes a client server 310 , such as Cerner Millennium, with active relational database files is located in a location such as a pharmacy, hospital system servers in a cloud-computing environment.
- Clinical notification management application 305 resides on a control server and is in communication with multiple clinician devices 315 , 320 and 325 to provide notifications to the clinician according to the clinician's subscription preferences via a network (not shown).
- a network such as the internet or other public or private network, serves as a communications link from clinical notification management application 305 , a relational database EMR 310 , such as Millennium and clinician devices 315 , 320 and 325 .
- Clinical notification management application 305 manages notification subscriptions, pushes notifications, and processes read receipts.
- Clinical notification management application 305 includes user login 330 , order module 335 , notification module 340 and communication module 345 .
- User login 330 allows the user to log into the clinical notification management application 305 .
- a user may login directory to the clinical notification management application 305 or may be indirectly logged into the clinical notification management application 305 by logging into the client server hosting the EMR.
- medical data collected are displayed only when the user clinician authenticates on at least one of the multiple medical devices.
- the order module manages clinical result for individuals, changes in status for individuals being treated and errors relating the individual medical chart modifications.
- Notification module 340 manages clinician notification subscription by providing user selectable notification options to the clinician via communication module 345 .
- the subscription notification preferences can include the relationship between the clinician and individual being medically treated (e.g., doctor patient relationship).
- the subscriptions can also be based on location of the individual (e.g., the ward of the medical facility) or location of the clinician (e.g., in the medical facility or outside the medical facility).
- the subscriptions can be made by the clinician at the time of encounter. For example, while the clinician is placing an order for the individual in the EMR, the clinician can select user selectable options to be notified of all or part of the results from the order being placed.
- the clinician can also choose notifications based for a particular date range for an individual or group of individuals.
- the clinician can further subscribe to notification based on result type such a radiology, lab, pathology and/or results that are critical versus non-critical results.
- result type such as a radiology, lab, pathology and/or results that are critical versus non-critical results.
- the type of result can be designated for an individual, multiple individuals or an individual being treated by the clinician.
- the clinical notification management application allow a clinician to “ad hoc” subscribe for notifications not specifically provided for.
- the local database of the notification module stores the clinician notification preferences.
- the notification module monitors clinical data for the individual being communicated to the individual's EMR.
- the notification module compares the clinician notification preferences to clinical data for the individual, and if one or more of the clinician notification preferences is satisfied, the communication module 345 communicate the notification to the preferred clinician device(s) 315 - 325 .
- the communication module determines a notification route to deliver the notifications to a selection of medical devices.
- the communication module may take into account several factors when making this determination, including the location of the clinician devices, date range, priority, and notification type. This determination is advantageous to provide sufficient notification to the clinician without over alerting the clinician. Sending too many notifications can cause a clinician not to check the clinical device for updates.
- the clinician and clinician devices are registered with the clinician notification management application by querying a database of clinician or direct registration by the clinician.
- a user with authority can access the authorized individual medical treatment electronic records and can register with the clinical notification management application to receive notification regarding the individual and/or electronic record.
- the clinical notifications management application provides graphical user interfaces via communication module to one or more clinician devices. User clinicians choose from user selectable options to select notifications they want to receive and on what devices.
- a method 400 for providing coordinated clinical messages to a clinician is provided.
- a user clinician logs into the clinical notification management application directly or indirectly through an EMR system.
- a medical summary for an individual being treated by the clinician or order entry screen for the individual are provided to a clinician.
- These interactive graphical user interfaces are displayed on a variety of user devices included a smart phone, laptop, smart watch and personally.
- user selectable notification options are provided to the clinician to select notifications.
- the user selectable options can be provided generally to a clinician or while a clinician is viewing an individual's medical summary or in conjunction with a medical order entry interactive graphical user interface as shown in FIGS. 6-14 .
- the clinical notification management application receives selection of the clinician of criteria to notify the clinician.
- Other information that may be selected by the user clinician includes what user device to notify.
- the user selectable options can include the relationship between the clinician and individual being medically treated (e.g., doctor patient relationship).
- the subscriptions can also be based on location of the individual (e.g., the ward of the medical facility) or location of the clinician (e.g., in the medical facility or outside the medical facility).
- the subscriptions can be made by the clinician at the time of encounter. For example, while the clinician is placing an order for the individual in the EMR, the clinician can select user selectable options to be notified of all or part of the results from the order being placed.
- the clinician can also choose notifications based for a particular date range for an individual or group of individuals.
- the clinician can further subscribe to notification based on result type such a radiology, lab, pathology and/or results that are critical versus non-critical results.
- result type such as a radiology, lab, pathology and/or results that are critical versus non-critical results.
- the type of result can be designated for an individual, multiple individuals or an individuals being treated by the clinician.
- a physician or nurse selects to be notified on all personal user devices regarding all information a person in his/her treatment so that the clinician can treat the patient as quickly as possible.
- an ambulatory physician or nurse selects user options to be notified with status updates on the clinician laptop, phone or watch so the clinician knows when a patient is ready to be seen.
- a clinician is electronically charting for a patient and needs to be aware of error notifications in the patient's chart that have not successfully been saved so the clinician can take corrective action.
- a clinician wants to set results alerts to be provided notifications related to a particular encounter, patient, or list so that clinician can treat or consult on a patient faster. Additional notifications include providing notifications to an acute care bed management user, receiving notifications on his or her laptop, phone, or watch when a bed is available for use.
- the clinician user preferences are stored in a local database of the clinical notification management application.
- the user preferences can be specific to the user and to the individual(s) the user clinician is treating.
- clinical data such as test results for an individual are received and evaluated to see if they satisfy user notification preference. This clinical data may be subsequent medical data received after the clinician user preferences are received. The clinical data could be information specific to an individual patient, a department or information related to charting patient information.
- the control server determines a notification route to provide the alert to the clinician selected medical devices.
- the notification route may be to send an alert to a selection of devices based on a number of factors about the device, such as the location, date range, priority, and type of notification.
- the notification is provided to the device.
- FIG. 5 if the user clinician is logged in at a medical facility the user clinician may select to only be notified at the medical facility and not on his or her personal device. And therefore the notification route will only send the messages to the medical facility and not the his or her personal device. However, if the clinician is not located at the medical facility, the clinician may want to receive notifications on his or her personal smart phone, tablet or laptop. In another example, in embodiments where the notification route selects one device from the user selected medical devices and the medical devices include personal devices, the notification route may determine not to provide notifications to the users personal device. The control server based on time of day and location of devices will determine that notifications should be provided to the medical devices at the medical facility to alert the clinician.
- an interactive graphical user interface on a user clinician's personal device is shown.
- the graphical user interface includes a medical summary for an individual being treated by the clinician.
- the user can select the “alert” icon in the top right corner to select notification options for this individual.
- FIG. 7 is an interactive graphical user interface that includes user selectable notification options. From this interface, the user clinician can select the types of notifications such as critical alerts, vitals and pathology results for this individual. Once selected, these user notifications preferences are stored and screened by the clinical notification management application.
- FIG. 8 is an interactive graphical user interface that includes user selectable options to view a list of the user clinician's patients in a particular location, ward 2 East as shown in FIG. 9 . From FIG. 9 , the user can select the “alert” icon in the top right corner to select notifications for this group of individuals.
- FIG. 10 is an interactive graphical user interface that includes user selectable notification options. From this interface, the user clinician can select the types of notifications for this group of patients. The user clinician selects to receive notifications for critical alerts, vitals and pathology result for the individuals in this group.
- FIG. 11 is an interactive graphical user interface that displays to a clinician an order summary for a patient being treated.
- the user can select the option to create a new order for the patient and sign and place orders from this graphical user interface. From the graphical user interface, the user selects to create a new creatine order as shown in the pop up screen of FIG. 12 .
- the user can choose from the order details whether to be notified of the results.
- the user signs the order for a creatine lab tests in the upper right hand corner.
- the selection of the notification preference is stored and monitored by the clinical notification management application as described above.
- the application determines that the results for the creatine order have been received, a notification of creatine results is sent to the user clinician's device as shown in FIG. 15 (previously specified by user).
- FIG. 15 the clinician is notified that results are available but no HIPAA private information is displayed.
- the user clinician can access a secure and private application to view the actual result information for the patient while maintaining privacy for the individual.
Abstract
Description
- This application claims priority to U.S. Provisional Application 62/612,482, entitled “CLINICAL NOTIFICATIONS” and filed on 31 Dec. 2017, wherein the entirety of the application has been incorporated by reference herein.
- Today, the speed at which individuals receive medical care is dependent upon manual processes. For instance, a patient's treatment is dependent upon the ordering physician's receipt of test results. This is typically accomplished one of three manual ways. First, the results are faxed to a physician. Second, test results are entered into an individual's electronic medical chart, such as an EMR, and the clinician logs into the electronic medical chart to view the results. Third, test results are delivered to the ordering physician or nurse by a telephone call.
- For example, an MRI of the knee reveals a meniscus tear. The radiologist calls the ordering physician to provide results, and then dictates the report. The process is duplicate effort for the radiologist and requires phone availability from the ordering physician.
- Each scenario delays care because it requires users to purposefully (and manually) retrieve or deliver results. Each manual process is time consuming, costly, and significantly delays treatment of the individual.
- Embodiments of the present invention provide methods and systems for performing providing clinical information for a person, such as a test result, immediately and the information automatically and immediately pushed to the ordering physician's Cerner-provisioned device(s) or personal device. It removes the manual processes that create bottlenecks in care today. Patients may begin treatment earlier, providing the greatest opportunity for positive outcomes.
- Systems, methods and computer readable media for providing clinical notifications in a cloud-computing environment are described. Input by the control server is received for a sign on for a user clinician and identification of a person being treated by the user clinician. The control server automatically generates one or more graphical user interfaces for displaying a medical order screen for the person being treated or list of persons being treated by the clinician and at least a graphical representation of one or more user selectable clinical notification options. Input is received by the control server representing a user selection of one or more of the user selectable clinical notification options. The user selection is compared to a subsequent medical data received for the one or more persons being treated via the control server. The subsequent medical data is analyzed to determine if it satisfies the user selection of the clinical notification option. In response to determining if the subsequent medical data satisfies the user selection of the clinical notification option, the control server automatically generates in real time one or more graphical user interfaces for displaying the event notification of the subsequent medical data on a one or more clinician devices.
- In one embodiment, input is received by the control server representing a user selection of a multiple medical devices selected to receive the clinical notification option. In this described embodiment in response to determining if the subsequent medical data satisfies the user selection of the clinical notification option, the control server displays an event notification on the multiple medical devices selected to receive the clinical notification option.
- In some embodiments the event notification is filtered by the control server to remove the subsequent medical data about the one or more persons being treated by the user clinician. In some aspects, the medical order screen comprises a medical summary for the individual being treated by the clinician. In other aspects, the medical summary comprises patient vitas and measurements, reported symptoms, and prior diagnosis. The event notification in some aspects comprises critical alerts, vitals, and pathology results for the one or more persons being treated by the user clinician. The event notification may include subsequent medical data about the one or more persons being treated by the user clinician.
- In one embodiment, the control server receives input representing a user selection of the clinical notification option and a multiple medical devices selected to receive the notification. When a clinical notification is generated, the control server automatically generates, in real time, one or more graphical user interfaces for displaying notification of data received for the person being treated on the multiple medical devices selected to receive the notification. In some embodiments, only one medical device may be selected to receive the notification.
- A clinician may only want to be notified of critical results for an individual who they are treating but do not want non-critical results for the individual. This technology allows a medical worker to specify notification own to a patient, order and individual test result level so as not to over alert a medical worker. Additionally, the medical professional can specify devices for alerting. Each of these alerts occurring in real time, overcoming the slow process of traditional clinical notifications.
- The clinical notification management application provides a system for clinicians and ancillary users to subscribe to, push, and receive notifications related to their role in medical treatment in real time. Notifications can be sent and received for clinical results for individuals being treated. Notifications can also be pushed to a clinician based on a change in status of patient encounters, appointments, or rooms. A user clinician can provide preferences to receive notifications based on individual encounters, patients, locations, lists, and date ranges.
- The clinical notification management application in some embodiments, provides real time notifications of clinical information to clinicians and decreases delays in patient care. The clinical notification management application provides notifications outside of authenticated sessions (push notifications) without exposing protected health information (PHI) of individuals. This technology eliminates or reduces dependency of manual processes to communicate clinical results or status changes. In some embodiments the one or more graphical user interfaces with the subsequent medical data are displayed only when the user clinician authenticates on at least one of the multiple medical devices.
- Unlike prior solutions, the clinician does not have to log into an individual's EMR or wait for a fax or telephone call to determine clinical information for the individual, such as test results. The clinical notification management application provides real time notifications of clinical information to clinicians and decreases delays in patient care. The clinical notification management application provides notifications outside of authenticated sessions (push notifications) without exposing protected health information (PHI) of individuals.
- In some embodiments, when a user selects more than one medical devices to receive the clinical notification option the notification is sent to a selection of the multiple medical devices selected by the user. In some embodiments, the selection of multiple medical devices is determined by the control server based on device preference of the user. This can include information about the device including location. In other embodiments, a notification route is generated to deliver an event notification of the one or more clinician devices. The notification route may be generated by the control server in real time based on device data such as location of the device, date range, and notification type.
- The claimed solution is necessarily rooted in computerized electronic medical relational database technology in order to overcome a problem specifically arising in the realm of computer medical clinical notification and communication. The claims address the problem of quickly and efficiently notifying a clinician of clinical information even when a user is not logged into an individual's electronic medical record.
- The claimed system and method of the present application represents a new paradigm notifying clinicians in a real time manner. Not only does the claimed invention provide a way for a user to receive real time notifications of clinical results, the user can specify what user device to push notification. The user can also choose to receive notification when entering an order into an individual's electronic medical record.
- The method and system for providing the user with the capability decide what notifications he/she wants to receive about what individuals and what devices to push the notifications. The clinical notification management application according to the new technology saves time and costs as clinical information is communicated to a user clinician in a manner defined by the user clinician.
- 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. The present invention is defined by the claims.
- Embodiments are described in detail below with reference to the attached drawing figures, wherein:
-
FIG. 1 is a block diagram of an exemplary computing environment suitable to implement embodiments of the present invention; -
FIG. 2 is an exemplary system architecture suitable to implement embodiments of the present invention; -
FIG. 3 is an exemplary system architecture suitable to implement embodiments of the present invention; -
FIG. 4 is a flow diagram depicting a process to provide clinical notifications to a clinician; -
FIG. 5 is an exemplary block diagram depicting where clinical notifications are to be provided to a clinician; -
FIG. 6 is an interactive graphical user interface depicting a medical summary of an individual to a clinician; -
FIG. 7 is an interactive graphical user interface displaying user selectable notification options for an individual to a clinician; -
FIG. 8 is an interactive graphical user interface displaying user selectable options for a list of individuals being treated; -
FIG. 9 is an interactive graphical user interface displaying user selectable options of individuals being treated; -
FIG. 10 is an interactive graphical user interface displaying user selectable notification options for individuals being treated; -
FIG. 11 is an interactive graphical user interface with an order summary for an individual; -
FIG. 12 is an interactive graphical user interface for a clinician to create an order for an individual; -
FIG. 13 is an interactive graphical user interface for a clinician to select notifications of results from an order being created; -
FIG. 14 is an interactive graphical user interface for a clinician to sign an order created for an individual; and -
FIG. 15 is an interactive graphical user interface for displaying notifications to a clinician. - 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 elements 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.
- The present invention overcomes the delay in clinical notifications of previous clinical notification options. Previous clinical notification options rely on human interaction, sending alerts via phone calls and pagers by nurses or assistants. These notification options are slow because they require human oversight and input to contact clinicians and caregivers. Further, old notification options can be indiscrete—without verification the clinician is the one viewing what can be sensitive patient material. Embodiments of the present invention, however, allow users to select the notification to receive that is instantaneous and in real time. These notifications can be sent only to devices the user selects, or notifications can be sent to a selection of devices based on various data available to the control server. Further, notifications can be filtered from all sensitive medical data about a patient, only allowing a clinician to be notified of basic information such as results are in for a particular test. All of these features provide a faster, more reliable, and secure means to provide clinician notifications that overcome many of the failings of older notification solutions.
- With continued reference to
FIG. 1 , thecomputing environment 100 comprises a computing device in the form of acontrol server 102. Exemplary components of thecontrol server 102 comprise a processing unit, internal system memory, and a suitable system bus for coupling various system components, includingdata store 104, with thecontrol server 102. The system bus might 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. Exemplary architectures comprise 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 therein, or has access to, a variety of non-transitory computer-readable media. Computer-readable media can be any available media that might be accessed bycontrol server 102, and includes volatile and nonvolatile media, as well as, removable and nonremovable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable 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 includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed bycontrol 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 includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics 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 should also be included within the scope of computer-readable media. - The
control server 102 might operate in acomputer network 106 using logical connections to one or moreremote computers 108.Remote computers 108 might be located at a variety of locations in a medical or research environment, including clinical laboratories (e.g., molecular diagnostic laboratories), hospitals and other inpatient settings, veterinary environments, ambulatory settings, medical billing and financial offices, hospital administration settings, home healthcare environments, and clinicians' offices. Clinicians may comprise 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; laboratory technologists; genetic counselors; researchers; veterinarians; students; and the like. Theremote computers 108 might also be physically located in nontraditional medical care environments so that the entire healthcare community might be capable of integration on the network. Theremote computers 108 might be personal computers, servers, routers, network PCs, peer devices, other common network nodes, or the like and might comprise some or all of the elements described above in relation to thecontrol server 102. The devices can be personal digital assistants or other like devices. -
Computer networks 106 comprise 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 might comprise a modem or other means for establishing communications over the WAN, such as the Internet. In a networking environment, program modules or portions thereof might be stored in association with thecontrol server 102, thedata store 104, or any of theremote computers 108. For example, 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.,control server 102 and remote computers 108) might be utilized. - In operation, an organization might 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 microphone (e.g., voice inputs), a touch screen, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad. Other input devices comprise satellite dishes, scanners, or the like. Commands and information might 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 might comprise 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, such components and their interconnection are well known. Accordingly, additional details concerning the internal construction of thecontrol server 102 and theremote computers 108 are not further disclosed herein. - Embodiments of the present invention may be implemented in a cloud-computing environment as shown in
FIG. 2 . The cloud-computing network may comprise single or multiple servers running single or multiple virtual machines. In an embodiment exhibited byFIG. 2 , a computer environment is depicted for managing and providing clinical notifications to a clinician for individuals being medically treated.Control server 102 hosts clinical notification management application in a cloud computing environment. Tasks performed by the processor utilize a variety of computer technology. In one embodiment, the control server are three tiers: a web server, application server and database server. Each tier is comprised of a number of system layers as described below. - As shown in
FIG. 3 , aclinical notification system 300 includes aclient server 310, such as Cerner Millennium, with active relational database files is located in a location such as a pharmacy, hospital system servers in a cloud-computing environment. Clinicalnotification management application 305 resides on a control server and is in communication withmultiple clinician devices notification management application 305, arelational database EMR 310, such as Millennium andclinician devices - Clinician notifications are managed and transmitted by clinical
notifications management application 305 on a control server in a cloud-computing environment in a timely, efficient and secure manner using embodiments of the present invention. Clinicalnotification management application 305 manages notification subscriptions, pushes notifications, and processes read receipts. Clinicalnotification management application 305 includesuser login 330,order module 335,notification module 340 andcommunication module 345. -
User login 330 allows the user to log into the clinicalnotification management application 305. A user may login directory to the clinicalnotification management application 305 or may be indirectly logged into the clinicalnotification management application 305 by logging into the client server hosting the EMR. In some embodiments, medical data collected are displayed only when the user clinician authenticates on at least one of the multiple medical devices. - The order module manages clinical result for individuals, changes in status for individuals being treated and errors relating the individual medical chart modifications.
Notification module 340 manages clinician notification subscription by providing user selectable notification options to the clinician viacommunication module 345. The subscription notification preferences can include the relationship between the clinician and individual being medically treated (e.g., doctor patient relationship). The subscriptions can also be based on location of the individual (e.g., the ward of the medical facility) or location of the clinician (e.g., in the medical facility or outside the medical facility). The subscriptions can be made by the clinician at the time of encounter. For example, while the clinician is placing an order for the individual in the EMR, the clinician can select user selectable options to be notified of all or part of the results from the order being placed. - The clinician can also choose notifications based for a particular date range for an individual or group of individuals. The clinician can further subscribe to notification based on result type such a radiology, lab, pathology and/or results that are critical versus non-critical results. The type of result can be designated for an individual, multiple individuals or an individual being treated by the clinician. For things not specified, the clinical notification management application allow a clinician to “ad hoc” subscribe for notifications not specifically provided for.
- In some embodiments, the local database of the notification module stores the clinician notification preferences. The notification module monitors clinical data for the individual being communicated to the individual's EMR. The notification module compares the clinician notification preferences to clinical data for the individual, and if one or more of the clinician notification preferences is satisfied, the
communication module 345 communicate the notification to the preferred clinician device(s) 315-325. In other embodiments, the communication module determines a notification route to deliver the notifications to a selection of medical devices. The communication module may take into account several factors when making this determination, including the location of the clinician devices, date range, priority, and notification type. This determination is advantageous to provide sufficient notification to the clinician without over alerting the clinician. Sending too many notifications can cause a clinician not to check the clinical device for updates. - The clinician and clinician devices are registered with the clinician notification management application by querying a database of clinician or direct registration by the clinician. A user with authority can access the authorized individual medical treatment electronic records and can register with the clinical notification management application to receive notification regarding the individual and/or electronic record. The clinical notifications management application provides graphical user interfaces via communication module to one or more clinician devices. User clinicians choose from user selectable options to select notifications they want to receive and on what devices.
- Referring next to
FIG. 4 , amethod 400 for providing coordinated clinical messages to a clinician is provided. Atstep 405, a user clinician logs into the clinical notification management application directly or indirectly through an EMR system. - At
step 410, in some embodiments a medical summary for an individual being treated by the clinician or order entry screen for the individual are provided to a clinician. These interactive graphical user interfaces are displayed on a variety of user devices included a smart phone, laptop, smart watch and personally. Atstep 415, user selectable notification options are provided to the clinician to select notifications. The user selectable options can be provided generally to a clinician or while a clinician is viewing an individual's medical summary or in conjunction with a medical order entry interactive graphical user interface as shown inFIGS. 6-14 . - Continuing with
FIG. 4 , atstep 420, the clinical notification management application receives selection of the clinician of criteria to notify the clinician. Other information that may be selected by the user clinician includes what user device to notify. The user selectable options can include the relationship between the clinician and individual being medically treated (e.g., doctor patient relationship). The subscriptions can also be based on location of the individual (e.g., the ward of the medical facility) or location of the clinician (e.g., in the medical facility or outside the medical facility). The subscriptions can be made by the clinician at the time of encounter. For example, while the clinician is placing an order for the individual in the EMR, the clinician can select user selectable options to be notified of all or part of the results from the order being placed. - The clinician can also choose notifications based for a particular date range for an individual or group of individuals. The clinician can further subscribe to notification based on result type such a radiology, lab, pathology and/or results that are critical versus non-critical results. The type of result can be designated for an individual, multiple individuals or an individuals being treated by the clinician.
- In one use case, a physician or nurse selects to be notified on all personal user devices regarding all information a person in his/her treatment so that the clinician can treat the patient as quickly as possible. In another use case, an ambulatory physician or nurse selects user options to be notified with status updates on the clinician laptop, phone or watch so the clinician knows when a patient is ready to be seen.
- In another example, a clinician is electronically charting for a patient and needs to be aware of error notifications in the patient's chart that have not successfully been saved so the clinician can take corrective action. In another case, a clinician wants to set results alerts to be provided notifications related to a particular encounter, patient, or list so that clinician can treat or consult on a patient faster. Additional notifications include providing notifications to an acute care bed management user, receiving notifications on his or her laptop, phone, or watch when a bed is available for use.
- At
step 425, the clinician user preferences are stored in a local database of the clinical notification management application. The user preferences can be specific to the user and to the individual(s) the user clinician is treating. Atstep 430, clinical data, such as test results for an individual are received and evaluated to see if they satisfy user notification preference. This clinical data may be subsequent medical data received after the clinician user preferences are received. The clinical data could be information specific to an individual patient, a department or information related to charting patient information. Atstep 435, it is determined whether the result satisfies the notification preference. If the personal result fromstep 430 does not satisfy the notification preference atstep 435, then the process repeats for a subsequent personal result. Ifstep 435 is satisfied, then the control server may proceed to step 440. Atstep 440, the control server determines a notification route to provide the alert to the clinician selected medical devices. In some embodiments, the notification route may be to send an alert to a selection of devices based on a number of factors about the device, such as the location, date range, priority, and type of notification. Atstep 445 the notification is provided to the device. - For example,
FIG. 5 , if the user clinician is logged in at a medical facility the user clinician may select to only be notified at the medical facility and not on his or her personal device. And therefore the notification route will only send the messages to the medical facility and not the his or her personal device. However, if the clinician is not located at the medical facility, the clinician may want to receive notifications on his or her personal smart phone, tablet or laptop. In another example, in embodiments where the notification route selects one device from the user selected medical devices and the medical devices include personal devices, the notification route may determine not to provide notifications to the users personal device. The control server based on time of day and location of devices will determine that notifications should be provided to the medical devices at the medical facility to alert the clinician. - With reference to
FIG. 6 , an interactive graphical user interface on a user clinician's personal device is shown. The graphical user interface includes a medical summary for an individual being treated by the clinician. The user can select the “alert” icon in the top right corner to select notification options for this individual. -
FIG. 7 is an interactive graphical user interface that includes user selectable notification options. From this interface, the user clinician can select the types of notifications such as critical alerts, vitals and pathology results for this individual. Once selected, these user notifications preferences are stored and screened by the clinical notification management application. -
FIG. 8 is an interactive graphical user interface that includes user selectable options to view a list of the user clinician's patients in a particular location,ward 2 East as shown inFIG. 9 . FromFIG. 9 , the user can select the “alert” icon in the top right corner to select notifications for this group of individuals. -
FIG. 10 is an interactive graphical user interface that includes user selectable notification options. From this interface, the user clinician can select the types of notifications for this group of patients. The user clinician selects to receive notifications for critical alerts, vitals and pathology result for the individuals in this group. -
FIG. 11 is an interactive graphical user interface that displays to a clinician an order summary for a patient being treated. The user can select the option to create a new order for the patient and sign and place orders from this graphical user interface. From the graphical user interface, the user selects to create a new creatine order as shown in the pop up screen ofFIG. 12 . In the graphical user interface ofFIG. 13 , the user can choose from the order details whether to be notified of the results. - In
FIG. 14 , the user signs the order for a creatine lab tests in the upper right hand corner. The selection of the notification preference is stored and monitored by the clinical notification management application as described above. When the application determines that the results for the creatine order have been received, a notification of creatine results is sent to the user clinician's device as shown inFIG. 15 (previously specified by user). As can be seen inFIG. 15 , the clinician is notified that results are available but no HIPAA private information is displayed. After receiving the notification, the user clinician can access a secure and private application to view the actual result information for the patient while maintaining privacy for the individual. - The present invention has been described in relation to particular embodiments, which are intended in all respects to be illustrative rather than restrictive. Further, the present invention is not limited to these embodiments, but variations and modifications may be made without departing from the scope of the present invention.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/236,881 US20220262529A9 (en) | 2018-01-02 | 2018-12-31 | Clinical Notifications |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862612842P | 2018-01-02 | 2018-01-02 | |
US16/236,881 US20220262529A9 (en) | 2018-01-02 | 2018-12-31 | Clinical Notifications |
Publications (2)
Publication Number | Publication Date |
---|---|
US20190206577A1 US20190206577A1 (en) | 2019-07-04 |
US20220262529A9 true US20220262529A9 (en) | 2022-08-18 |
Family
ID=65199601
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/236,881 Pending US20220262529A9 (en) | 2018-01-02 | 2018-12-31 | Clinical Notifications |
US16/238,055 Active 2039-11-08 US11241527B2 (en) | 2018-01-02 | 2019-01-02 | Priming system for drug delivery device |
US17/496,708 Active 2039-08-10 US11925783B2 (en) | 2018-01-02 | 2021-10-07 | Priming system for drug delivery device |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/238,055 Active 2039-11-08 US11241527B2 (en) | 2018-01-02 | 2019-01-02 | Priming system for drug delivery device |
US17/496,708 Active 2039-08-10 US11925783B2 (en) | 2018-01-02 | 2021-10-07 | Priming system for drug delivery device |
Country Status (10)
Country | Link |
---|---|
US (3) | US20220262529A9 (en) |
EP (1) | EP3735282A1 (en) |
JP (2) | JP7025553B2 (en) |
CN (2) | CN115252955A (en) |
AU (2) | AU2019205210B2 (en) |
BR (1) | BR112020009244A2 (en) |
CA (1) | CA3081577C (en) |
MX (1) | MX2020006249A (en) |
SG (1) | SG11202005291WA (en) |
WO (1) | WO2019136071A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USD1007676S1 (en) | 2021-11-16 | 2023-12-12 | Regeneron Pharmaceuticals, Inc. | Wearable autoinjector |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110001605A1 (en) * | 2009-03-04 | 2011-01-06 | Masimo Corporation | Medical monitoring system |
US20150066525A1 (en) * | 2013-08-30 | 2015-03-05 | William Baxter Webb, III | System for exchanging medical information |
Family Cites Families (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5232454A (en) * | 1990-08-01 | 1993-08-03 | Smiths Industries Medical Systems, Inc. | Safety needle container |
US7544189B2 (en) * | 2000-10-10 | 2009-06-09 | Meridian Medical Technologies, Inc. | Needle and hub assembly for automatic injector |
GB2453069B (en) * | 2004-11-22 | 2009-12-09 | Intelliject Llc | Devices,systems and methods for medicament delivery |
WO2007062182A2 (en) * | 2005-11-23 | 2007-05-31 | Eksigent Technologies, Llp | Electrokinetic pump designs and drug delivery systems |
GB2480407B (en) * | 2006-11-21 | 2011-12-28 | Intelliject Inc | Injection device for medicament delivery |
US8313467B2 (en) * | 2007-12-27 | 2012-11-20 | Medtronic Minimed, Inc. | Reservoir pressure equalization systems and methods |
GB0821492D0 (en) | 2008-11-25 | 2008-12-31 | Team Holdings Uk Ltd | Integrated auto-injector cartridge system |
TW201103590A (en) * | 2009-06-02 | 2011-02-01 | Sanofi Aventis Deutschland | Medicated module with integral flow distribution system |
US8328757B2 (en) | 2010-01-08 | 2012-12-11 | Wisconsin Alumni Research Foundation | Bladder arrangement for microneedle-based drug delivery device |
WO2011118410A1 (en) | 2010-03-26 | 2011-09-29 | テルモ株式会社 | Liquid dispensing circuit |
JP5804675B2 (en) | 2010-05-27 | 2015-11-04 | 日本コヴィディエン株式会社 | Connector cap and infusion line connection device provided with the same |
EP2457602A1 (en) | 2010-11-25 | 2012-05-30 | F. Hoffmann-La Roche AG | Infusion pump having dosing unit with safety valve |
WO2012072563A1 (en) * | 2010-11-29 | 2012-06-07 | Sanofi-Aventis Deutschland Gmbh | Medicated module with automatic reservoir engagement |
US9844629B2 (en) | 2011-05-18 | 2017-12-19 | Becton, Dickinson And Company | Injection device |
AU2013245990B2 (en) | 2012-04-13 | 2017-06-15 | Becton, Dickinson And Company | Microinfuser with automatic needle retraction |
RU2684037C2 (en) * | 2013-03-15 | 2019-04-03 | Гипротек, Инк. | Multi-chamber injection device |
JP6491195B2 (en) | 2013-05-03 | 2019-03-27 | ベクトン・ディキンソン・アンド・カンパニーBecton, Dickinson And Company | Fluid path subassembly |
US10037410B2 (en) * | 2013-11-27 | 2018-07-31 | General Electric Company | Cloud-based clinical information systems and methods of use |
EP3074073B1 (en) | 2013-12-01 | 2019-02-06 | Becton, Dickinson and Company | Medicament device |
JP6321431B2 (en) | 2014-03-31 | 2018-05-09 | 国立大学法人大阪大学 | Medical line connector |
CN107278158A (en) * | 2014-09-29 | 2017-10-20 | 尤尼特拉克特注射器控股有限公司 | Rigid needle interposer for medicine transportation pump |
CN105839152A (en) | 2015-10-21 | 2016-08-10 | 北京中科三环高技术股份有限公司 | Electrodeposition method, electrodeposition solution and method for preparation of rare earth permanent magnetic material by electrodeposition |
US10792432B2 (en) | 2016-06-09 | 2020-10-06 | Becton, Dickinson And Company | Drive assembly and spacer for drug delivery system |
US10603445B2 (en) * | 2016-06-09 | 2020-03-31 | Becton, Dickinson And Company | Needle actuator assembly for drug delivery system |
-
2018
- 2018-12-31 US US16/236,881 patent/US20220262529A9/en active Pending
-
2019
- 2019-01-02 SG SG11202005291WA patent/SG11202005291WA/en unknown
- 2019-01-02 JP JP2020536844A patent/JP7025553B2/en active Active
- 2019-01-02 CN CN202210881142.8A patent/CN115252955A/en active Pending
- 2019-01-02 AU AU2019205210A patent/AU2019205210B2/en active Active
- 2019-01-02 US US16/238,055 patent/US11241527B2/en active Active
- 2019-01-02 MX MX2020006249A patent/MX2020006249A/en unknown
- 2019-01-02 EP EP19701402.0A patent/EP3735282A1/en active Pending
- 2019-01-02 BR BR112020009244-4A patent/BR112020009244A2/en unknown
- 2019-01-02 CN CN201980006420.1A patent/CN111479599B/en active Active
- 2019-01-02 CA CA3081577A patent/CA3081577C/en active Active
- 2019-01-02 WO PCT/US2019/012057 patent/WO2019136071A1/en unknown
-
2021
- 2021-05-20 AU AU2021203247A patent/AU2021203247B2/en active Active
- 2021-10-07 US US17/496,708 patent/US11925783B2/en active Active
-
2022
- 2022-02-10 JP JP2022019696A patent/JP7401577B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110001605A1 (en) * | 2009-03-04 | 2011-01-06 | Masimo Corporation | Medical monitoring system |
US20150066525A1 (en) * | 2013-08-30 | 2015-03-05 | William Baxter Webb, III | System for exchanging medical information |
Also Published As
Publication number | Publication date |
---|---|
US20220023530A1 (en) | 2022-01-27 |
CN115252955A (en) | 2022-11-01 |
AU2019205210A1 (en) | 2020-05-21 |
CN111479599A (en) | 2020-07-31 |
US11925783B2 (en) | 2024-03-12 |
JP7401577B2 (en) | 2023-12-19 |
CA3081577C (en) | 2022-11-29 |
US20190201626A1 (en) | 2019-07-04 |
AU2021203247A1 (en) | 2021-06-10 |
WO2019136071A1 (en) | 2019-07-11 |
CN111479599B (en) | 2022-08-12 |
CA3081577A1 (en) | 2019-07-11 |
AU2021203247B2 (en) | 2022-07-21 |
JP7025553B2 (en) | 2022-02-24 |
US11241527B2 (en) | 2022-02-08 |
EP3735282A1 (en) | 2020-11-11 |
BR112020009244A2 (en) | 2020-10-20 |
JP2022051941A (en) | 2022-04-01 |
JP2021509610A (en) | 2021-04-01 |
MX2020006249A (en) | 2020-09-03 |
US20190206577A1 (en) | 2019-07-04 |
AU2019205210B2 (en) | 2021-03-04 |
SG11202005291WA (en) | 2020-07-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10777059B2 (en) | Alert management utilizing mobile devices | |
US11062263B2 (en) | Clinical collaboration using an online networking system | |
US11482321B2 (en) | Patient portal management of referral orders | |
US8112294B2 (en) | System and method for orchestrating clinical collaboration sessions | |
US20150310176A1 (en) | Healthcare event response and communication center | |
US10275570B2 (en) | Closed loop alert management | |
US20060184524A1 (en) | Method and system for automated data analysis, performance estimation and data model creation | |
US20160125168A1 (en) | Care management assignment and alignment | |
US20140129255A1 (en) | Medical Information and Scheduling Communication | |
US20100205005A1 (en) | Patient oriented electronic medical record system | |
US20100179825A1 (en) | Copying patient-customized healthcare plans/orders/phases | |
US20180374388A1 (en) | System and method for displaying discharge instructions for a patient | |
US20130282391A1 (en) | Patient management of referral orders | |
US11521718B2 (en) | Mobile application for medication reminders | |
US8065167B1 (en) | Computer systems for managing patient discharge | |
US20160335400A1 (en) | Systems and methods for managing patient-centric data | |
US10339617B2 (en) | Order profile safeguarding mechanism | |
US20210202081A1 (en) | Customization of population management | |
US20190206577A1 (en) | Clinical Notifications | |
US10741273B1 (en) | User friendly medical records systems, apparatuses and methods | |
US20050149357A1 (en) | Computerized system and method for generating and satisfying health maintenance item expectations in a healthcare environment | |
US20130110541A1 (en) | Social health networking | |
Gawade et al. | Trusty Medicare: An Online Virtual Care System | |
Kaiser | Assessing Referral Appropriateness in the Intake Department: System Changes Under PPS |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CERNER INNOVATION, INC., KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MCCURDY, MICHAEL;ANDERSON, MATT R.;HENKES, MATTHEW JOSEPH;REEL/FRAME:049132/0921 Effective date: 20190104 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PRE-INTERVIEW COMMUNICATION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION COUNTED, NOT YET MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |