Pharmacy workflow management with integrated alerts

Description

RELATED APPLICATIONS

This application relates to and incorporates by reference the co-owned application having Provisional Ser. No. 62/127,580 by Crooks et al. filed on Mar. 3, 2015 entitled PHARMACY WORKFLOW MANAGEMENT WITH INTEGRATED ALERTS.

BACKGROUND

Pharmacies often are relied upon to provide compounded sterile products (CSPs) in connection with the provision of healthcare to patients. Such CSPs may comprise medication doses (sometimes referred to herein simply as doses) that are to be used in connection with the provision of healthcare. In this regard, pharmacies (e.g., including hospital pharmacies, outpatient pharmacies, compounding centers, and the like) often prepare CSPs or doses for delivery to a healthcare provider. Such CSPs may be patient specific doses or be provided for stock or inventory doses in the pharmacy that are compounded in anticipation of use. Accordingly, pharmacy technicians are often tasked with preparation of CSPs under the guidance and supervision of a licensed pharmacist or the like. For instance, a pharmacy technician may, under the supervision of a pharmacist, reconstitute drugs, draw specific drug amounts, gather products, assemble products, and create specific CSPs using reconstituted drugs, products, or the like.

In connection with the preparation of CSPs, pharmacies have begun to introduce an increasing amount of technology to assist in the compounding process. One such example of a technology-assisted compounding system comprises pharmacy workflow management applications that may be executed at pharmacy workstations for use in preparation of CSPs. Such pharmacy workflow management applications may provide assistance to pharmacists and pharmacy technicians in a multitude of areas related to management and preparation of doses. For instance, pharmacy workflow management applications may assist in organizing and managing orders for CSPs or doses (referred to herein as “dose orders”) for efficient and timely preparation of doses. Furthermore, such pharmacy workflow management applications may facilitate documentation of the preparation of a dose. Such documentation may be used to audit preparation steps after the fact for, for example, pharmacist review or in connection with tracking regulatory compliance. Such pharmacy workflow management applications may also assist in tracking doses in relation to movement of the dose within the pharmacy, dispensation from the pharmacy, or even movement through a facility, such as to an administration site.

Pharmacy workflow management applications or other technology-assisted approaches to compounding provide the potential benefit of reduction of errors in the pharmacy. For instance, recognizing an error before it occurs or catching the error prior to dispensation of the pharmacy may lead to reduced patient risk associated with human errors that may occur in the pharmacy. Given the potential to improve patient safety in connection with pharmacy activities, it may be appreciated that the facilities provided by technology-assisted approaches to pharmacy work may advantageously be extended by additional capabilities.

SUMMARY

In view of the foregoing, it has been recognized herein that improvement to technology-assisted compounding tools such as pharmacy workflow management applications or the like may assist in reduction of risk to patients by incorporation of medical information from additional sources (e.g., including potentially sources external to the pharmacy). That is, while pharmacy workflow management applications have been associated with the potential to reduce errors that occur in the pharmacy, prior inability or limited ability to integrate data from additional medical sources (e.g., that may be external to the pharmacy) may in turn limit the ability of such an application to provide meaningful assistance outside the context of pharmacy activities. Given the potential benefits derived from a wider perspective of data integration, it is presently recognized that benefits may be provided in connection with integration of additional data sources beyond data sources with a limited perspective of pharmacy-centric information.

Specifically, it is presently recognized that data aggregated from a plurality of sources may be beneficially accessed and/or utilized at a pharmacy workflow management application to, for example, provide useful information to a user when preparing a dose or to a pharmacist when reviewing a dose. For instance, aggregation of data sources may allow alert data to be generated by one or more alert generation platforms. This alert data may be generated at least in part in view of data sources external to the pharmacy. For example, one such contemplated alert generation platform comprises the ICNet™ Suite of alert products provided by ICNet International Limited. Specifically, such alert platforms may comprise software, firmware, and/or hardware components that may be in operative communication with a number of data sources. In turn, the alert generation platform may extract meaningful and actionable data from the underlying data sources to generate alert data in one or more contexts. That is, the alert generation platform may include logic for processing data from one or more sources to generate alert data. For example, alert data may be provided in the context of infection control, antimicrobial stewardship, or other areas. In any regard, this alert data may provide meaningful and actionable information that may assist a pharmacist or pharmacist technician in relation to pharmacy work (e.g., in relation to management and/or preparation of doses, CSPs, or the like). In other embodiments, an information aggregator may be provided that aggregates information from one or more medical information sources for use by, or presentation at, a pharmacy workflow management application (e.g., in the absence of alert data).

In this regard, the present disclosure contemplates the integration of alert data in technology-assisted compounding techniques. Specifically, an interface is contemplated that may provide operative communication between a pharmacy workstation (e.g., that may execute a pharmacy workflow management application) and an alert generation platform. In turn, the pharmacy workstation may be operative to process alert data of the alert generation platform for use in connection with the pharmacy workflow management application that may be executed at the pharmacy workstation. For instance, the alert data may be used to provide an alert indication to a user of the pharmacy workflow management application. Additionally, the alert indication may provide interactive features that may facilitate functionality that is provided to the user of the pharmacy workflow management application. For example, a user of the pharmacy workflow management application having alert data integration may be capable of accessing an instance of the alert generation platform from the pharmacy workflow management application. In turn, the pharmacist or pharmacy technician's workflow may be simplified such that the access to alert data and/or the alert generation platform may be made more efficient by providing direct access by way of the pharmacy workflow management application.

Additionally, the interface may facilitate bidirectional communication between the pharmacy workstation and the alert generation platform. In turn, information may be exchanged between the pharmacy workstation and the alert generation platform. One such example may include proving a responsive input received from a user of the pharmacy workflow management application to the alert generation platform. Accordingly, the alert generation platform may include resolution information and/or intervention information that may, for example, provide an indication of a response by appropriate personnel to an alert and/or an outcome of the response to the alert. As such, rather than having to separately access the alert generation platform to provide such a responsive input or duplicate the input of such input in multiple platforms, the input may be provided directly to the pharmacy workflow management application executing on a pharmacy workstation such that the responsive input is in turn provided to the alert platform. In turn, responsive inputs such as alert interventions may be communicated in bidirectional fashion between the pharmacy workstation and the alert generation platform.

Additionally, the pharmacy workflow management application may include logic that allows for dose order record manipulation within the pharmacy workflow management application in response to alert data of the alert generation platform. In this regard, dose orders received at a pharmacy may be processed to generate dose order records that may be reflected in the pharmacy workflow management application. For instance, dose order records may be assigned a status by the pharmacy workflow management application and may be presented to a user in a dose order listing. Accordingly, upon receipt of alert data, the pharmacy workflow management application may be capable of processing the alert data in connection with one or more dose order records to take action in relation to a dose order record based on the alert data. For instance, a dose order record may have a status changed, may be displayed in a different manner, may be displayed in a different interface portion of the pharmacy workflow management application, or have some other appropriate action taken in relation to a dose order record in response to the alert data.

Further features may be facilitated by the integration of alert data in a pharmacy workflow management application. For instance, a user of the pharmacy workflow management application may be capable of accessing a local instance of the alert generation platform directly from the interface of the pharmacy workflow management application. As such, the local instance of the alert generation platform may be executed on the pharmacy workstation on which the pharmacy workflow management application is also executed. As may be further appreciated, the local instance of the alert generation platform may be executed in connection with a thin client such as an internet browser such that access to an alert generation platform remote from the pharmacy workstation on which the pharmacy workflow management application is executed may be provided by way of the thin client. Furthermore, access to features of the alert generation platform (e.g., including reporting functionality) may be directly accessed by a user of the pharmacy workflow management application. Further still, additional capabilities provided by certain configurations of a pharmacy workflow management application may facilitate additional functionality in relation to the integration. For instance, a pharmacy workflow management application may be executed in a distributed environment where a plurality of pharmacy workstations may be operative to execute the pharmacy workflow management application. In this case, each of the distributed pharmacy workstations may have access to alert data that is processed once received from an alert generation platform. Furthermore, in at least some embodiments, central server communication used by the pharmacy workflow management application may also be used to provide functionality in connection with the alert data. For instance, alert data, alert indications, alert responses, alert interventions, or other information may be provided to a central server in connection with a backup, a data analytics tool, and/or report generation tool provided in connection with a central server. In this regard, the central server may be in communication with a plurality of local facilities each executing a pharmacy workflow management application. As such, the data received from the plurality of local facilities may be aggregated such that large scale trends in relation to alert data may be identified (e.g., including antimicrobial behaviors at a wide scale such as drug resistances or infection control at a wide scale).

Further still, embodiments are contemplated herein where aggregated medical information may be presented to a user of a pharmacy workflow management application. For example, the aggregated medical information may be collected at an information aggregator (e.g., which may or may not also provide alert generation capability). That is, an alert generation module may aggregate data both for presentation in raw form and for processing to generate alert data therefrom. In any regard, the aggregated medical information may be presented to a user of a pharmacy workflow management application. For instance, aggregated information may be presented to a user of the pharmacy workflow management application prior to preparation of a dose. Further still, aggregated medical information may be presented in connection with preparation of a dose. Additionally or alternatively, aggregated medical information may be presented to a user of the pharmacy workflow management application during approval and/or review of a prepared dose. In this regard, the aggregated medical information may be provided in connection with alert data provide to the pharmacy workflow management application or may be provided in the absence of an alert.

Accordingly, a first aspect comprises a pharmacy workstation for use in connection with execution of a pharmacy workflow management application. The pharmacy workstation includes a memory storing the pharmacy workflow management application and a processor configured to access the pharmacy workflow management application stored in the memory to execute the pharmacy workflow management application. The pharmacy workstation also includes an interface in operative communication with the processor and an alert generation platform. The processor is operative to process alert data of the alert generation platform from the interface and is operable to configure a display to present an alert indication corresponding to at least a portion of the alert data to the user at the pharmacy management workstation in connection with the pharmacy workflow management application.

A number of feature refinements and additional features are applicable to the first aspect. These feature refinements and additional features may be used individually or in any combination. As such, each of the following features that will be discussed may be, but are not required to be, used with any other feature or combination of features of the first aspect.

For example, in an embodiment the alert indication may be displayed at a user interface of the pharmacy workstation presented on the display. Furthermore, the user interface of the pharmacy workstation may further include an input device. As such, the user interface may include an interactive portion corresponding to the alert indication. In an embodiment, the alert indication may include the interactive portion. The alert indication may be provided on a user interface screen of the pharmacy workflow management application corresponding to a pharmacist workspace comprising a listing of dose orders of the pharmacy workflow management application. Additionally or alternatively, the alert indication may be provided on a user interface screen of the pharmacy workflow management application corresponding to an interface for pharmacist verification of a dose order. The alert indication may provide information regarding the nature of the alert and/or action items to be taken in response to the alert indication. The alert may be highlighted in the user interface based upon the nature of the alert (e.g., with important, urgent, or critical alert indications appearing in a different color to highlight the alert relative to lower priority alerts).

The interactive portion may facilitate a number of functionalities within the pharmacy workflow management application. For example, the interactive portion, upon selection by a user by way of an input provided using the input device, may configure the processor at the pharmacy workstation to launch execution of the alert generation platform at the pharmacy workstation. For instance, selection of the interactive portion may launch a local instance of the alert generation platform at the pharmacy workstation executing the pharmacy workflow management application. The local instance may be a local instance of the alert generation platform or may be a thin client operative to present an interface regarding a remotely executed alert generation platform.

The pharmacy workstation may also include a dose processing interface for receipt of dose order data of an order entry system. The order entry system may comprise a portion of a hospital information system, a pharmacy information system, or other appropriate electronic medical record system. The dose order data may include medication data regarding at least one dose order for administration in connection with provision of medical care. For at least some dose orders, the dose order data may include patient data or other EMR data as well. The at least one dose order may be populated into a dose order listing displayed at the display of the user interface of the pharmacy workstation. In turn, the processor may be operative to process the alert data of the alert generation platform from the interface in relation to the dose order listing to associate the alert indication with one or more corresponding respective dose order in the dose order listing.

For instance, in an embodiment, the alert data may include patient specific alert data. For instance, the alert data may relate to a specific lab result for a given patient, a specific treatment undertaken for a specific patient, specific patient allergies, or other patient related information. As such, the alert data may include a first patient identifier corresponding to a patient to whom the alert data applies. The dose order data may include a second patient identifier corresponding to a patient to whom the dose order is to be administered. Correspondence of the first patient identifier and the second patient identifier may result in the alert data being associated to the dose order. In turn, the alert indication may be displayed on the user interface at the pharmacy workstation in connection with a dose order for the patient to whom the alert data is associated. For instance, the first patient identifier and the second patient identifier may be identical or correlated in some fashion (e.g., a look-up table or the like) to associate the alert indication with the patient specific dose order. As such, the alert indication may be provided in corresponding relation to the dose order in the pharmacy workflow management application.

In further regard to alert generation platform functionality provided at the pharmacy workflow management application, the dose order listing may include at least one patient specific order and the user interface comprises a patient link that, upon selection by a user by way of an input provided using the input device, may configure the processor to launch execution of a local instance of the alert generation platform at the pharmacy workstation to display a patient report corresponding to the patient associated with the at least one patient specific dose order from the alert generation platform in connection with the pharmacy workflow management application. The patient report may provide details regarding the patient that may, for example, be presented in a timeline format reflecting major events in relation to the patient's care such as use of medical devices, order or administration of drugs, laboratory results, procedures, vital signs, or other patient related information.

Further still, the input device may be configured to receive a responsive input from a user of the pharmacy workflow management application corresponding to a response to the alert indication. For instance, the responsive input may comprise an intervention and/or outcome related to an alert indication presented at the pharmacy workstation. The interface may be in bidirectional communication with the alert generation platform to provide the responsive input to the alert generation platform. The responsive input may include instructions for modification of a corresponding dose order associated with the alert indication.

In an embodiment, the memory may include alert processing rules accessible by the processor for processing the alert data received at the interface by the processor. For instance, the alert processing rules may define one or more triggering conditions for presentation of the alert indication in the pharmacy workflow management application. Accordingly, upon satisfaction of the one or more triggering conditions (e.g., only upon satisfaction of the one or more triggering conditions), the alert indication may be displayed in corresponding relation to one or more dose orders in a dose order listing of the pharmacy workflow management application.

Additionally or alternatively, the alert processing rules may define one or more actions to be taken with respect to a given dose order in response to the alert indication. Upon satisfaction of the one or more triggering conditions, the processor may be operative to execute the one or more actions with respect to the given dose order in response to the alert indication. The action by the processor may occur automatically upon satisfaction of the triggering condition such that no user input is needed to complete the action for the dose order. The one or more actions to be taken with respect to a given dose order may include modification of a status of the given dose order in the dose order listing of the pharmacy workflow management application. Additionally, the pharmacy workflow management application may include a user interface screen for displaying one or more given dose orders for which one or more actions have been taken in response to one or more corresponding alert indications. For example, a dose order listing filter may be provided that filters a dose order listing to show only those dose orders for which a particular action has been taken in response to satisfaction of a triggering condition by an alert indication.

In an embodiment, the interface may be in bidirectional communication with the alert generation platform. As such, the pharmacy workstation may locally present at the pharmacy workstation information from the alert generation platform. The processor may be operative to configure the display to present report data in connection with the pharmacy workflow management application that is received from the alert generation platform (e.g., in response to a request for the report data from the pharmacy workstation). Additionally, in an embodiment, the pharmacy workstation may be in operative communication with a server remote from the pharmacy workstation. Accordingly, the processor may be in operative communication with the server for communication of the alert data to the server such that the server may store a copy of the alert data in a server memory located at the server. The server remote from the pharmacy workstation may be a pharmacy workflow management server specific to the facility at which the pharmacy workflow management application is executed or may be a central server remote from the facility to which a plurality of pharmacy workflow management applications at different respective facilities communicate information.

While the alert generation platform may be operative to acquire and/or process data from a plurality of medical information sources to provide alert data in a number of contexts, in the specific context of a pharmacy a number of specific alert types may be particularly of interest. For instance, the alert data may include information related to at least one of infection control or antimicrobial stewardship. For instance, alerts associated with given microbial organisms identified in a patient may trigger an alert or may trigger alerts in respect of particular medications ordered for a patient. Furthermore, identification of particular infections may provide alert data in the pharmacy.

Furthermore, the processor of the pharmacy workstation may be operative to process aggregated medical information received from an information aggregator so that the processor may configure a display to present at least a portion of the aggregated medical information to a user at the pharmacy workstation in connection with the pharmacy workflow management application. For instance, the aggregated medical information may correspond to aggregated information regarding a particular patient (e.g., a patient for whom a dose order has been received at the pharmacy workflow management application). Additionally or alternatively, the aggregated medical information may include information regarding a plurality of patients. The aggregated medical information may also relate to a given facility or a collection of facilities. The aggregated medical information may be displayed independently within the pharmacy workflow management application (e.g., in the form of a report or the like), in connection with a dose order record listing, or in connection with a review screen presented during review and/or approval of a dose order.

A second aspect includes a non-transitory computer readable medium comprising computer-readable instructions for configuration of a processor to execute a pharmacy workflow management application and process alert data of an alert generation platform. The computer-readable instructions may further configure the processor to configure a display to present an alert indication corresponding to at least a portion of the alert data to a user of the pharmacy workflow management application in connection with the pharmacy workflow management application.

A number of feature refinements and additional features are applicable to the second aspect. These feature refinements and additional features may be used individually or in any combination. As such, each of the following features that will be discussed may be, but are not required to be, used with any other feature or combination of features of the second aspect. Additionally, any of the features or feature refinements discussed above in relation to the first aspect may be, but are not required to be, used with any other feature or combination of features of the second aspect.

In an embodiment, the computer-readable instructions may configure the processor to display the alert indication at a user interface of the pharmacy workstation on the display. Additionally, the computer-readable instructions may configure the processor to display on the user interface an interactive portion corresponding to the alert indication. In an embodiment, the alert indication may include the interactive portion. As such, the computer-readable instructions may configure the processor to launch execution of the alert generation platform at a pharmacy workstation upon receipt of a selection of the interactive portion by a user (e.g., by way of a user input at the pharmacy workstation).

In an embodiment, the computer-readable instructions may configure the processor to provide the alert indication on a user interface screen of the pharmacy workflow management application corresponding to a pharmacist workspace comprising a listing of dose orders of the pharmacy workflow management application. Additionally or alternatively, the computer-readable instructions configure the processor to provide the alert indication on a user interface screen of the pharmacy workflow management application corresponding to an interface for pharmacist verification of a dose order.

In an embodiment, the non-transitory computer readable medium may further include computer-readable instructions for configuration of the processor to execute a dose processing interface for receipt of dose order data of an order entry system. The dose order data may include medication data regarding at least one dose order for administration in connection with provision of medical care. As such, the computer-readable instructions may configure the processor to populate at least one dose order into a dose order listing displayed at the display of the user interface of the pharmacy workstation. Specifically, the computer-readable instructions may configure the processor to process the alert data of the alert generation platform from the interface in relation to the dose order listing to associate the alert indication with one or more corresponding respective dose orders in the dose order listing.

In an embodiment, the alert data may include patient specific alert data. For instance, the alert data may include a first patient identifier corresponding to a patient to whom the alert data applies, and the dose order data may comprise a second patient identifier corresponding to a patient to whom the dose order is to be administered. The computer-readable instructions may configure the processor to determine correspondence of the first patient identifier and the second patient identifier and associate the alert data to the dose order based on the correspondence. As described above, the first and second patient identifiers may be identical or associated (e.g., in a correlation table or the like). As such, the dose order listing may include at least one patient specific order and the computer-readable instructions may configure the processor to provide a patient link at the user interface that, upon selection by a user by way of an input provided using an input device, further configures the processor to launch execution of the alert generation platform (e.g., a local instance of the alert generation platform) at the pharmacy workstation to display a patient report corresponding to the patient associated with the at least one patient specific dose order from the alert generation platform in connection with the pharmacy workflow management application.

In an embodiment, the computer-readable instructions may configure the processor to provide the alert indication in corresponding relation to a dose order in the pharmacy workflow management application. Additionally, the computer-readable instructions may configure the processor to receive a responsive input from a user of the pharmacy workflow management application corresponding to a response to the alert indication. The computer-readable instructions may configure the processor to communicate with the alert generation platform to provide the responsive input to the alert generation platform. In an embodiment, the responsive input comprises instructions for modification of a corresponding dose order associated with the alert indication.

The computer-readable instructions may include alert processing rules accessible by the processor for processing the alert data received at the interface. The alert processing rules may define one or more triggering conditions for presentation of the alert indication in the pharmacy workflow management application. Upon satisfaction of the one or more triggering conditions, the computer-readable instructions may configure the processor to display the alert indication in corresponding relation to one or more dose orders in a dose order listing of the pharmacy workflow management application. The alert processing rules may define one or more actions to be taken with respect to a given dose order in response to the alert indication. As such, upon satisfaction of the one or more triggering conditions, the computer-readable instructions may configure the processor to execute the one or more actions with respect to the given dose order in response to the alert indication. For instance, the one or more actions to be taken with respect to a given dose order may include modification of a status of the given dose order in the dose order listing of the pharmacy workflow management application. Further still, the computer-readable instructions may configure the processor to display a user interface screen for displaying one or more given dose orders for which one or more actions have been taken in response to one or more corresponding alert indications by the pharmacy workflow management application.

In an embodiment, the computer-readable instructions may configure the processor to communicate with the alert generation platform. As such, the processor may be operative to configure the display to present report data in connection with the pharmacy workflow management application that is received from the alert generation platform in response to a request for the report data from the pharmacy workstation. The report data may be presented locally at a pharmacy workstation executing the computer-readable instructions. The computer-readable instructions may also configure the processor of the pharmacy workstation to communicate with a server remote from the pharmacy workstation. The computer-readable instructions may configure the processor to communicate with the server for communication of the alert data to the server. In turn, the server may store a copy of the alert data in a server memory located at the server.

In an embodiment, the alert data may include information related to at least one of infection control or antimicrobial stewardship. As described above, the alert data may be generated by the alert generation platform based on a number of medical information sources. Specifically, the alert generation platform may apply logic to the medical information received from the various sources to identify trends, patterns, or the like from the data regarding antimicrobial stewardship and/or infection control.

A third aspect includes a method for pharmacy workflow management. The method includes executing a pharmacy workflow management application and processing alert data of an alert generation platform. The method further includes configuring a display to present an alert indication corresponding to at least a portion of the alert data to a user of the pharmacy workflow management application in connection with the pharmacy workflow management application.

A number of feature refinements and additional features are applicable to the third aspect. These feature refinements and additional features may be used individually or in any combination. As such, each of the following features that will be discussed may be, but are not required to be, used with any other feature or combination of features of the third aspect. Additionally, any of the foregoing features described in connection with the first and/or second aspects may be, but are not required to be, used with any other feature or combination of features of the third aspect.

For instance, in an embodiment the method includes displaying the alert indication at a user interface of the pharmacy workstation presented on the display. The user interface may further include an input device. As such, the user interface may also include an interactive portion corresponding to the alert indication. For example, the alert indication may include the interactive portion.

In an embodiment, the method may include providing the alert indication on a user interface screen of the pharmacy workflow management application corresponding to a pharmacist workspace comprising a listing of dose orders of the pharmacy workflow management application. Additionally or alternatively, the method may include providing the alert indication on a user interface screen of the pharmacy workflow management application corresponding to an interface for pharmacist verification of a dose order.

The method may include a number of actions with respect to the interactive portion. For instance, the method may include launching, by the processor, execution of the alert generation platform at the pharmacy workstation upon selection of the interactive portion by a user by way of an input provided using the input device.

In an embodiment, the method may include executing a dose processing interface for receipt of dose order data of an order entry system. The dose order data may include medication data regarding at least one dose order for administration in connection with provision of medical care. The method may further include populating the at least one dose order into a dose order listing displayed at the display of the user interface of the pharmacy workstation. The method may also include processing, using the processor, the alert data of the alert generation platform from the interface in relation to the dose order listing to associate the alert indication with one or more corresponding respective dose order in the dose order listing.

For example, in an embodiment, the alert data may include patient specific alert data. As such, the alert data may include a first patient identifier corresponding to a patient to whom the alert data applies and the dose order data may include a second patient identifier corresponding to a patient to whom the dose order is to be administered. In turn, correspondence of the first patient identifier and the second patient identifier may result in the alert data being associated to the dose order. The correspondence may be identical patient identifiers or otherwise associable patient identifiers to identify a given patient.

In this regard, the dose order listing may include at least one patient specific order and the user interface may include a patient link. The method may further include launching alert generation platform at the pharmacy workstation upon selection by a user by way of an input provided using the input device to display a patient report corresponding to the patient associated with the at least one patient specific dose order from the alert generation platform in connection with the pharmacy workflow management application.

In an embodiment, the method may include providing the alert indication in corresponding relation to the dose order in the pharmacy workflow management application. The method may further include receiving a responsive input from a user of the pharmacy workflow management application corresponding to a response to the alert indication. For instance, the responsive input may comprise an intervention or outcome relative to an alert. The method may further include communicating with the alert generation platform to provide the responsive input to the alert generation platform. In an embodiment, the responsive input comprises instructions for modification of a corresponding dose order associated with the alert indication.

In an embodiment the method may include applying alert processing rules accessible by the processor for processing the alert data received at the interface. The alert processing rules may define one or more triggering conditions for presentation of the alert indication in the pharmacy workflow management application. As such, upon satisfaction of the one or more triggering conditions, the method may further include displaying the alert indication in corresponding relation to one or more dose orders in a dose order listing of the pharmacy workflow management application. The alert processing rules may define one or more actions to be taken with respect to a given dose order in response to the alert indication. As such, upon satisfaction of the one or more triggering conditions, the method may further include executing the one or more actions with respect to the given dose order in response to the alert indication. As such, the method may include status of the given dose order in the dose order listing of the pharmacy workflow management application based on the alert indication. The method may also additionally include displaying one or more given dose orders for which one or more actions have been taken in response to one or more corresponding alert indications at a user interface screen of the pharmacy workflow management application.

In an embodiment, the method may include configuring the display to present report data in connection with the pharmacy workflow management application that is received from the alert generation platform in response to a request for the report data from the pharmacy workstation. Further still, the method may include communicating the alert data to a server remote from the pharmacy workstation, wherein the server stores a copy of the alert data in a server memory located at the server. Also, as described above, the alert data may include information related to at least one of infection control or antimicrobial stewardship.

A fourth aspect includes a pharmacy workstation for use in connection with execution of a pharmacy workflow management application. The pharmacy workstation includes a memory storing the pharmacy workflow management application and a processor configured to access the pharmacy workflow management application stored in the memory to execute the pharmacy workflow management application. The pharmacy workstation may further include an alert generation module executable by the processor to configure the processor to communicate with one or more healthcare information sources and to generate alert data based at least in part on healthcare data of the one or more healthcare information sources. The alert generation module may be operative to process the alert data and configure a display to present an alert indication corresponding to at least a portion of the alert data to the user at the pharmacy management workstation in connection with the pharmacy workflow management application.

A number of feature refinements and additional features are applicable to the fourth aspect. These feature refinements and additional features may be used individually or in any combination. As such, each of the features discussed above in connection with any of the foregoing aspects, but in particular the first aspect, may be, but are not required to be, used with any other feature or combination of features of the fourth aspect.

A fifth aspect includes a medical information processing system for exchange of medical information. The medical information processing system may include a medical information processing platform comprising at least one processor configured for receipt and distribution of medical information. The medial information processing system may further include one or more exchange interfaces executed by the medical information processing platform that are in operative communication with a plurality of medical information sources each configured to store digital medical information and operable to communicate the digital medical information with the medical information processing platform by way of the one or more exchange interfaces. The medical information processing system may further include a memory at the medical information processing platform configured for storage of the digital medical information received from the plurality of medical information sources. The memory may include a formulary for use in the provision of medical care, and wherein the formulary reflects information regarding the digital medical information received from the plurality of medication information sources.

A number of feature refinements and additional features are applicable to the fifth aspect. These feature refinements and additional features may be used individually or in any combination. As such, the following features may be, but are not required to be, used with any other feature or combination of features of the first aspect. For instance, in an embodiment of the medical information processing system a first of the plurality of medical information sources may include an alert generation platform and a second of the plurality of medical information sources may include a pharmacy workstation. In this embodiment of the system, any of the foregoing features described in connection with the above aspects may be, but are not required to be, used with any other feature or combination of features with the fifth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a schematic view of an approach for medical information exchange.

FIG. 2 depicts a schematic view of an approach for medical information exchange using a medical information processing platform.

FIG. 3 depicts an embodiment of an approach for medical information exchange using a medical information processing platform with specific examples of medical information sources.

FIG. 4 depicts an embodiment of a medical information processing system to facilitate exchange of information between an alert generation platform and a pharmacy workflow management application.

FIG. 5 depicts an embodiment of an interface for accessing a pharmacy workflow management application.

FIG. 6 depicts an embodiment of a navigation interface screen of a pharmacy workflow management application.

FIG. 7 depicts an embodiment of an alert interface screen of a pharmacy workflow management application.

FIG. 8 depicts a dose verification interface having an alert indication presented.

FIG. 9 depicts an embodiment of an interface of a pharmacy workstation having a pharmacy workflow management application and a local instance of an alert generation platform displayed.

FIGS. 10-12 depict embodiments of a pharmacy workflow management application interface shown in connection with an alert generation platform interface that are in bidirectional communication for information exchange.

FIG. 13 depicts an interface of a pharmacy workflow management application for configuration of alert data processing at the pharmacy workflow management application.

FIG. 14 depicts embodiments of interfaces for display of filtered alert indication listings.

FIG. 15 depicts a dose order detail screen depicting action history in respect to the dose order.

FIGS. 16 and 17 depict embodiments of pharmacy workflow management application interfaces that are capable of presenting report information from an alert generation platform.

DETAILED DESCRIPTION

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and are herein described in detail. It should be understood, however, that it is not intended to limit the invention to the particular form disclosed, but rather, the invention is to cover all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the claims.

As described above, the use of technology-assisted preparation of doses has been used as a mechanism by which to help reduce the risk of committing errors during the compounding of doses in a pharmacy or the like. In this regard, such technology-assisted approaches such as the use of a pharmacy workflow management application or the like may leverage information to assist in identifying errors and risks to patients. For instance, formulary information in combination with dose order information and information related to scanned products and drugs during preparation may provide a pharmacist or pharmacy technician insight that is useful when preparing doses. However, to date the information that may be utilized has generally been primarily limited to information that is maintained within the pharmacy (e.g., wholly stored by a pharmacy workflow management application or the like) with limited or no ability to integrate data from other sources.

In turn, it is herein recognized that the exchange of medical information between sources of medical information may advantageously be leveraged to reduce patient risk, thereby potentially improving patient outcomes. However, with the desire to exchange medical information comes complications associated with the exchange. One such issue is illustrated in FIG. 1. FIG. 1 depicts a first medical information source 10, a second medical information source 20, a third medical information source 30, and a fourth medical information source 40. In approaching exchange of data between medial information sources 10-40, one potential paradigm would be to provide individual exchange paths (represented in FIG. 1 as arrowed lines connecting the sources) between each respective one of the medical information sources 10-40. However, such an approach provides additional complexity in that each individual data exchange between every given medical source must be individually managed. For instance, if an exchange protocol for a given source (e.g., medical information source 40) is altered, each other source (e.g., source 10, source 20, and source 40) must each account for the change in protocol. That is, each individual exchange path must be modified, thus leading to additional complexity and cost in connection with the information exchange. For example, the medical information sources 10-40 may each be provided by different respective entities such that collaboration in relation to changes may be difficult.

In contrast, FIG. 2 shows depicts a number of medical information sources (i.e., a first medical information source 10, a second medical information source 20, a third medical information source 30, and a fourth medical information source 40) that are each in communication with a medical information processing platform 100. The medical information processing platform 100 may in turn manage the exchange of information between various ones of the medical information sources 10-40. Accordingly, the medical information processing platform 100 may facilitate cross-source data exchange such that the exchange of data between any or all of the various sources 10-40 may be made more efficiently. For instance, in the event the exchange protocol for a source (e.g., medical information source 40) is altered, only the exchange between the medical information processing platform 100 may be modified to accommodate for the change, while the remainder of the sources are unchanged. In turn, the medial information processing platform 100 may provide a robust, efficient, and scalable exchange platform for exchange of data between sources even when the data formats and exchange protocols differ between the various sources.

Accordingly, given the architecture facilitated by way of the medical information processing platform 100, a variety of medical information sources have the potential to be operatively engaged for exchange of information. In this regard, with improved data exchange, additional patient safeguards, production efficiencies, product optimizations, or other benefits may be realized as will be appreciated from the continued discussion below. FIG. 3 depicts one environment of a medication information processing system 105 that demonstrates the potential benefit of employing a medical information processing platform 100 to facilitate data exchange.

For instance, FIG. 3 provides a few examples of potential medical information sources that may be in communication with a medical information processing platform 100 to facilitate exchange of medical information. In this regard, FIG. 3 depicts one or more point of care devices 102 that may be in operative communication with the medical information processing platform 100. The point of care device 102 may, for example, include an administration device such as an infusion pump or the like that may provide information about a patient and/or administration parameters to the medical information processing platform 100. The point of care device 102 may further include workstations at the point of care (e.g., bedside terminals or the like) that may provide information to the medical information processing platform 102.

The medical information processing platform 100 may also be in operative communication with one or more product or drug providers 104. For instance, the product or drug providers 104 may provide information regarding available drugs and products including, for example, information regarding national drug codes (NDCs), recall information, new product information, or the like.

One or more electronic medical record (EMR) systems 106 may also be in operative communication with the medical information processing platform 100. The EMR system 106 may comprise a hospital information system (HIS) or a pharmacy information system (PhIS). For instance, the EMR system 106 may provide patient admission/discharge information, patient identifier information, information regarding facility resources, order information from a physician order entry system (OES), inventory information, claims processing information, billing information, or any other information managed or stored by the EMR system 106.

The medical information processing platform 100 may also be in operative communication with an analytics tool 108. The analytics tool 108 may provide information regarding data analytics regarding any one or more of the other medical information sources in operative communication with the medical information processing platform 100. The analytics tool 108 may also provide information regarding metrics, parameters, data dimensions, pivot tables, values, measures, or any other appropriate data analytics tool to the medical information processing platform 100.

Further still, the medical information processing platform 100 may be in operative communication with a clinical surveillance tool 110. The clinical surveillance tool 110 may comprise an alert generation platform that may provide alert data regarding, for example, antimicrobial stewardship within a facility, infection control, or other appropriate data. As will be appreciated in the discussion presented below, the clinical surveillance tool 110 may leverage information obtained from other medical information sources (e.g., either through the medical information processing platform or by direct communication outside the platform 100) to generate alert data based on logic provided in relation to the information processed. Specific examples of potential alert data is addressed in greater detail below.

The medical information processing platform 100 may also be in operative communication with one or more medical dispensing apparatuses 112. The medical dispensing apparatus 112 may include a drug dispending cabinet, a nurse accessible medication cabinet, or any other appropriate locale where medication and/or medical products may be made available for dispensation. The medical dispensing apparatus 112 may provide information regarding inventory, access requests, dispensation events, or other appropriate information.

One or more pharmacy automation devices 114 may also be in operative communication with the medical information processing platform 100. Such pharmacy automation devices 114 may include, for example, automated syringe processing devices, automated pill dispenser/counter devices, automated compounding devices, dose preparation robots, or other appropriate automated devices utilized in the pharmacy.

Additionally, the medical information processing platform 100 may be in operative communication with a pharmacy workflow management application 116. The pharmacy workflow management application 116 may provide information regarding dose orders, documented preparation steps for doses, dose verification information, product usage, drug usage, drug lot/expiration information, technician workflow information, formulary information, or other information related to pharmacy workflow management.

In the exchanges of information between the medical information processing platform 100 and the medical information sources 102-116 described above, it may be appreciated that different respective exchange protocols and/or data formats may be used to exchange information. For example, the exchange of data between any of the sources 102-116 and the medical information processing platform 100 may be by way of an Health Level 7 (HL7) interface, a print-feed interface, an XML interface, an http format, an html format, a text format, a comma separated value (CSV) format, an SQL format, or any other appropriate format or protocol for exchange of data. Given the potential ability of the medical information processing platform 100 to process such diverse protocols and formats, the medical information processing platform 100 may be scalable to communicate with any number of different sources. For example, the medical information processing platform 100 may receive data in a first format or exchange protocol associated with a first medical information source (e.g., HL7) and in turn provide the data to a second source using a second format or exchange protocol (e.g., XML format).

Turning to FIG. 4, one particular embodiment of a medical information processing system 105 is shown. As a brief overview, a medical information processing platform 100 may be provided that is in operative communication with an EMR system 106, a clinical surveillance tool 110 (e.g., in the particular embodiment also referred to as an alert generation platform 110), and a pharmacy workflow management application 116. As may be appreciated, the medical information processing platform 100 may also be in operative communication with an order entry system 118 (e.g., such as an order entry system 118 that is provided separately from the EMR system 106 which may also include order generation/entry functionality).

The medical information processing platform 100 may include an alert processing interface 200 that is in operative communication with the alert generation platform 110 to receive alert data from the alert generation platform 100. The alert generation platform 110 may be in further communication with an EMR system 106, a laboratory system 120 and/or an operating room information system 122. The EMR system 106, laboratory system 120, and operating room information system 122 are shown in phantom in FIG. 4 to represent a possible embodiment where the alert generation platform 110 may be in direct communication with each of the EMR system 106, laboratory system 120, and operating room information system 122. However, the alert generation platform 110 may alternatively be in operative communication with the EMR system 106, laboratory system 120, and/or operating room information system 122 by way of the medial information processing platform 100. That is, the EMR system 106, laboratory system 120, and/or operating room information system 122 may comprise medical information sources as described in FIG. 3 that may be in operative communication with the medical information processing platform 100 to facilitate exchange of information from any one or more of the EMR system 106, laboratory system 120, and/or operating room information system 122 to the alert generation platform 110.

The alert generation platform 110 may be operative to, based on information received from any one or more of the laboratory system 120, EMR system 106, operating room information system 122, and/or any other appropriate medical information source, generate alert data. The alert data, in certain embodiments, may comprises alerts related to infection control or antimicrobial stewardship.

In an alternative embodiment, the medical information processing platform 100 may be in operative communication with and/or comprise an information aggregator. The information aggregator may be in operative communication with a plurality of medical information sources as described above. In this regard, the medical information processing platform 100 may itself be considered an information aggregator. Additionally or alternatively, the alert generation platform 110 may comprise an information aggregator. In this regard, the medical information processing platform 100 may maintain aggregated medical information and/or be in operative communication with an information aggregator (e.g., the alert generation platform 110) to access aggregated medical information for access and/or display in connection with the pharmacy workflow management application. The aggregated medical information may be used in conjunction with generation of alert data. In this regard, at least a portion of aggregated medical information may be provided in conjunction with alert data generated by the alert generation platform 110. In another embodiment, aggregated medical information may be accessed and/or displayed independent of any alert data. For instance, the pharmacy workflow management application may display the aggregated information to a user of the pharmacy workflow management application in a number of different potential screens or contexts of the pharmacy workflow management application. As will be described below, such aggregated information may be provided in connection with a dose order record listing, a dose order review screen, or a report selection screen, among others.

In any regard, the alert generation platform 110 may be in operative communication with an alert processing interface 200 of the medical information processing platform 100. As may be appreciated, the medial information processing platform 100 may include a memory 202 and processor 204. In this regard, the medical information processing platform 100 may comprise a specifically configured component configured to operate in a predetermined manner as will be described in greater detail below. As such, the specifically configured medial information processing platform may comprise specifically designed software, firmware, and/or hardware for performing certain tasks associated with the medical information exchange described herein. For instance, the memory 202 may store specific instructions that are accessible by the processor 204 to configure the processor 204 to perform functionality associated with the medical information processing platform 100. The memory 202 may comprise a non-transitory computer readable medium such as, for example, an optical disc, non-volatile storage such as a hard drive disc or the like, flash memory, EEPROM memory, or other appropriate computer memory. The memory 202 may in turn store one or more portions, components, or modules of computer-readable instructions that are predefined to specifically configure the processor 204 to execute functionality associated with the medical information processing platform 100. The processor 204, while referred to herein singularly, may comprise a plurality of processor cores or devices that may collectively execute to perform processing in a specifically configured manner. Furthermore, while the memory 202 is referred to singularly, the memory 202 may also comprises a plurality of discrete memory devices.

The medical information processing platform 100 may also comprise a plurality of data stores. The data stores may comprise databases of information stored in a format that facilitates efficient access and storage of information. For instance, the databases may comprise SQL databases or the like. For example, the medical information processing platform 100 may comprise a facility data database 206 and a formulary database 208. The facility database 206 may store information regarding pharmacy operations related to a pharmacy workflow management application 116 as will be discussed in greater detail below. However, the facility database 206 may also store information from any other medical information source with which the medical information processing platform 100 is in communication, such as any of the sources shown in FIG. 3. The formulary database 208 may maintain formulary information for a pharmacy associated with the pharmacy workflow management application 116. In this regard, the formulary database 208 may contain information related to drugs and products that may be utilized in the pharmacy in connection with the preparation of doses or other CSPs.

In any regard, the processor 204 may be configured to process alert data received from the alert generation platform 110 by way of the alert processing interface 200. For instance, the processor 204 may be configured to apply logic to the alert data of the alert generation platform 110. In some embodiments, the logic applied by the processor 204 to the alert data may at least in part be based on information contained in the facility data database 206 and/or the formulary database 208 as will be described in greater detail below.

The medical information processing platform 100 may be in further operative communication with a pharmacy workflow management application 116. In this regard, alert data may be processed by the processor 204 of the medical information processing platform 100 to provide information to the pharmacy workflow management application 116. The pharmacy workflow management application 116 is intended to encompass a plurality of potential system configurations within a pharmacy for execution of the pharmacy workflow management application 116. For example, in an embodiment a single pharmacy workstation comprising a memory and processor may be provided to execute the pharmacy workflow management application 116. In this regard, the memory may store computer-readable instructions in a non-transitory computer readable storage medium that, when accessed by the processor, may specifically configure the processor to execute the pharmacy workflow management application 116.

In another embodiment depicted in FIG. 4, the pharmacy workflow management application 116 may be executed in a distributed pharmacy environment that may include a plurality of pharmacy workstations. For instance, a pharmacy workflow management server 210 may be provided in association with a pharmacy. The pharmacy workflow management server 210 may comprise a memory 212 and a processor 214. In this regard, the memory 212 may store computer-readable instructions in a non-transitory computer readable storage medium that, when accessed by the processor 214, may specifically configure the processor to execute the pharmacy workflow management server 210. Specifically, the pharmacy workflow management server 210 may be in operative communication with one or more other pharmacy workstations. For instance, one or more medication preparation workstations 216 may be in operative communication with the pharmacy workflow management server 210. Again, each of the mediation preparation workstations 216 may comprise a memory 218 and processor 220 for execution of functionality associated with the medication preparation workstation in that the memory 218 may store computer-readable instructions in a non-transitory computer readable storage medium that, when accessed by the processor 220, may specifically configure the processor 220 to execute functionality associated with the medication preparation workstation 216. The medication preparation workstation 216 may comprise a workstation with a user interface comprising a display and an input for interaction by a user with the medication preparation workstation 216. The medication preparation workstation 216 may further include input devices for use in preparation of doses such as, for example, scanners for reading machine readable indicia (e.g., including NDC codes in machine readable barcode format), cameras for acquisition of images related to preparation of doses, foot pedals for interaction with the workstation 216 or other devices. The medication preparation workstation 216 may also include a printer for printing labels or the like in connection with preparation of doses at the workstation.

In any regard, a pharmacy workflow management server 210, a medication preparation workstation 210, or any other appropriate workstation may individually or collectively define a pharmacy workstation that may individually or collectively execute the pharmacy workflow management application 116. Furthermore, while the medical information processing platform 100 is shown as separate from the pharmacy workflow management application 116, it may be appreciated that the medical information processing platform 100 and the pharmacy workflow management application 116 may execute on a single computing device having collective memory and processor capabilities.

As such, one or more pharmacy workstations executing the pharmacy workflow management application 116 may be operative to receive from the medical information processing platform 100 information relating to the alert data processed at the medical information processing platform 100. For instance, the alert data may be processed by the medical information processing platform 100 to generate an alert indication that is provided to the pharmacy workflow management application 116. In turn, the alert indication may be displayed at one or more workstations associated with the pharmacy workflow management application 116. As described above, the pharmacy workstation (e.g., a workstation in operative communication with the pharmacy workflow management server 210 such as the medication preparation workstation 216) may provide a user interface having a display. As such, the alert indication may be provided on the display in connection with the pharmacy workflow management application 116. As will be appreciated in greater detail in the discussion to follow, the user interface of the pharmacy workstation may also present to a user an interactive portion that may allow for a user to access and/or manipulate various features in association with the alert generation platform 110. For instance, the user may interact with the user interface of the pharmacy workstation to select the interactive portion corresponding to the alert indication to launch execution of the alert generation platform 110 on the pharmacy workstation from which the user is interacting with the alert indication. That is, a local instance of the alert generation platform 110 may be executed at the pharmacy workflow management application 116. Accordingly, the alert generation platform 110 may be accessed by way of the pharmacy workstation (e.g., directly or by way of the medical information processing platform 100). For instance, the local instance of the alert generation platform 110 may be a thin client such as a web browser or the like such that the alert generation platform 110 may be accessed to display information provided from the alert generation platform 110 on the pharmacy workstation. As will be discussed in greater detail below, a user may further interact with the alert generation platform 110 by way of the pharmacy workstation to, for example, provide a responsive input to the alert generation platform 110, access reporting functionality of the letter generation platform 110, or otherwise engage with the alert generation platform 110.

FIG. 4 also illustrates the medical information processing platform 100 being in operative communication with an EMR system 106 by way of a dose order processing interface 222. Additionally or alternatively, the medical information processing platform 100 may be in operative communication with an order entry system 118 by way of the dose processing interface 222. In any regard, the medical information processing platform 100 may receive, by way of the dose processing interface 222, information regarding dose orders corresponding to dose is to be administered in connection with the provision of medical care. For instance, the dose order may contain medication data regarding at least one dose order that may be processed by the medical information processing platform 100. Specifically, the medical information processing platform 100 may process the dose order information to generate dose order records that may, for example, be stored in the facility data database 206. In turn, the pharmacy workflow management application 116 may be operative to also process the dose order records and present to a user of the pharmacy workflow management application 116 a dose order listing corresponding to the dose orders managed by the pharmacy workflow management application 116.

The alert indication may be presented at the pharmacy workflow management application 116 in connection with the dose order listing. Additionally or alternatively, the alert indication may be presented at the pharmacy workflow management application 116 connection with a user interface screen of the pharmacy workflow management application 116 corresponding to an interface for pharmacist verification of the dose order. For instance, in either of the foregoing regards, a processor in connection with the pharmacy workflow management application 116 may be operative to process the alert data of the alert generation platform 110 in relation to the dose order listing maintained by the pharmacy workflow management application 116 to associate an alert indication with one or more corresponding respective dose orders in the dose order listing.

In one particular example, the alert data of the alert generation platform 110 may be patient specific alert data. That is, the alert data may regard a specific patient. In this regard, the alert data may comprise a patient identifier corresponding to the patient to whom the alert data applies. In a similar regard, at least one dose order received at the dose processing interface 222 may be a patient specific dose order for administration to a specific patient. In this regard, the patient specific dose order may also comprise a patient identifier. In this regard, upon correlation of the patient identifier for the alert data and the patient identifier for the dose order, the patient specific alert data may be associated with the dose orders for the given patient to which the alert data applies. The correlation of the patient identifiers of the alert data and the dose order may include use of identical patient identifiers by the EMR system 106 and the alert generation platform 110. Alternatively, different patient identifiers may be used by the respective medical information sources that may be associated (e.g., in a look-up table or the like).

In addition, the pharmacy workflow management application 116 and/or the medical information processing platform 100 may be configured to apply logic in relation to the alert data in connection with the processing of the alert data received at the alert processing interface 200. For instance, alert processing rules may define one or more triggering conditions that relate to the presentation and/or actions related to dose orders in relation to an alert indication at the pharmacy workflow management application 116. As such, upon satisfaction of the one or more triggering conditions, the alert indication may be displayed in connection with the pharmacy workflow management application 116. In this regard, alert data may be received the medical information processing platform 100 and/or the pharmacy workflow management application 116 that is not displayed in connection with the pharmacy workflow management application 116 if a triggering condition is not satisfied by the alert data. The alert processing rules that may include the triggering condition may allow for tailoring of the presentation of alert data to a user of the pharmacy workflow management application 116. This may be used to limit the number of alert indications provided to a user of the pharmacy workflow management application 116, thus reducing the potential for alert fatigue whereby a user tends to ignore all alerts if the alert frequency for low severity alert is too high.

In addition, the alert processing rules may define one or more actions to be taken with respect to a given dose order in connection with the alert indication. For example, upon association of a dose order with an alert indication, the corresponding dose order record may be processed by the pharmacy workflow management application 116 according to the alert processing rules. For instance, the status the dose order record for which alert indication is provided may be modified such that the dose order is, for example, put on hold or elevated to a STAT (or otherwise elevated) priority in the event that an alert indication of a given type is received in corresponding relation to the dose order record.

The pharmacy workflow management application 116 may be in further operative communication with a central server 224. The pharmacy workflow management application 116 may communicate data to the central server 224. For example, at least a portion of the data stored in the facility data database 206 may be communicated to the central server 224. The communication of such data may be direct from the medical information processing platform 100 or by way of the pharmacy workflow management application 116. In this regard, the central server 224 may provide backup services in relation to the data processed by the medical information processing platform 100 and/or the pharmacy workflow management application 116. In this regard, alert data generated by the alert generation platform 110 may also be communicated to the central server 224 and provided for purposes of backing up the alert data received from the alert generation platform 110. Further still, the central server 224 may provide the data aggregation point whereby data may be aggregated for purposes of subjecting the data to data analytics the like. In this regard, in the event alert data is provided to the central server 224, the alert data may also be subjected to aggregation for purposes of potential data analytics in relation to the alert data.

The central server 224 may be in operative communication with a plurality of pharmacy workflow management applications 116 and/or a plurality of medical information processing platforms 100. For instance, different respective entities may operate to respective ones of the medical information processing platform 100 and/or pharmacy workflow management application 116. The different respective entities operating the medical information processing platform 100 and/or the pharmacy workflow management application 116 may each be unrelated or unaffiliated parties. However, the central server 224 may be in operative communication with a plurality of the unaffiliated instances of the pharmacy workflow management application 116 and/or medical information processing platform 100 to provide backup data services with respect to the unaffiliated instances. For instance, the central server 224 may be operated by a provider of the pharmacy workflow management application 116 for purposes of backing up data processed by a given facility using the pharmacy workflow management application 116.

Without limiting any of the foregoing discussion, specific embodiments of an interface connection with a pharmacy workflow management application 116 according to the present disclosure is presented in FIGS. 5-13. In this regard, it may be appreciated that the interface screens depicted in connection with FIGS. 5-13 may be presented at and/or generated by one or more pharmacy workstations associated with the pharmacy workflow management application 116. As such, functionality described in connection with the interface screens presented in FIGS. 5-13 may alternatively be provided using different specific configurations of interface screen. That is, the functionality described below can be provided in addition to or as an alternative to the foregoing description of the operation of the pharmacy workflow management application 116 and medical information processing platform 100 described above in connection with the foregoing. As may be appreciated, the processor (e.g., processor 214 or processor 220 discussed above in connection with the pharmacy workflow management application 116) may be configured in a manner as described above to display the various interface screens presented in FIGS. 5-13. Additionally, processing of user inputs received in connection with the interface screens described below may also be accomplished by the processor associated with the pharmacy workflow management application 116. In this regard, the functionality and processing described below in connection with the interface screens may be provided by the processor pharmacy workflow management application 116.

Turning to FIG. 5, a login screen 230 is depicted corresponding to the embodiment of a user interface of a pharmacy workflow management application 116. The log in screen 230 may include a user name field 232 and a password field 234. A user of the pharmacy workflow management application 116 may provide a username and the user name field 232 and a password in the password field 234 in order to gain access to the pharmacy workflow management application 116. In this regard, and authenticated username and password match may be required to access the pharmacy workflow management application 116.

Upon successful authentication of a user by the pharmacy workflow management application 116 (e.g., in response to provision of the username and password combination by a user), a user may be redirected to a navigation interface screen 236. The navigation interface screen 236 may provide a number of links or other interactive elements to allow for a user to navigate to different interface screens corresponding to different functionality associated with the pharmacy workflow management application 116. Of particular interest to the present discussion, the navigation interface screen 236 may include a link 238 to an alert interface screen 240 (an embodiment of which is depicted in FIG. 7). In addition to the link 238 to the alert interface screen 240, the navigation interface screen 236 may further provide interactive links to allow user to access various functionality of the pharmacy workflow management application 116 such as a dose order listing, a pharmacy verification workspace, formulary management workspaces, or other interfaces for providing functionality in connection with the pharmacy workflow management application 116.

Turning now to FIG. 7 depicting an embodiment of an alert interface screen 240, the alert interface screen 240 may display one or more alert indications corresponding to at least a portion of alert data received by the pharmacy workflow management application 116 and/or the medical information processing platform 100 from the alert generation platform 110. The alert interface screen 240 may include a listing 242 of alert indications 246. The alert indications 246 may be provided in the listing 242 such that the alert indications 246 are organized in any fashion appropriate for display to a user. For example, the alert indications 246 could be listed according to one or more of time of receipt, priority, alphabetical order, severity, or any other appropriate metric. Furthermore, as described above, aggregated medical information may be presented in the absence of any alert indication.

As depicted in FIG. 7, the listing 242 is provided such that alert indications 246 are displayed in corresponding relation to a patient specific dose order record 244 to which the alert indication corresponds. In this regard, the listing 242 may include a dose order record 244 that may provide an indication with respect to the dose order and/or patient associated with the dose order. Accordingly, the alert indications 246 corresponding to the dose order record 244 may be displayed in corresponding relation to the dose order record 244 in the listing 242. In this regard, while only a single alert indication 246 is shown for any single one of the dose order records 244 depicted in FIG. 7, it may be appreciated that a plurality of alert indications 246 could be displayed in corresponding relation to a given dose order record 244. In this case, the additional alert indications 246 may be displayed as a nested list of alert indications 246 relative to a given dose order record 244. The user may interact with a given dose order record 244 to expand or collapse the nested list of alert indications 246 corresponding to the dose order record 244.

In the embodiment depicted in FIG. 7, the alert indications 246 shown in the listing 242 may comprise patient specific alert indications. In this regard, it may be appreciated that the dose order record 244 may include one or more portions of patient information. For example, patient name and patient identifier are provided in connection with the dose order record 244. It may be appreciated that the alert indication 246 may also include a patient identifier corresponding to the patient identified in connection with the dose order record 244. In this regard, the patient identifier may be identical for the dose order record 244 and the alert indication 246. Alternatively, a patient identifier receiving connection with an alert indication may correspondingly associated with a patient identifier for dose order record 244 such that the different respective patient identifiers for the alert indication 246 in the dose order record 244 may be correlated (e.g., in a correlation table or the like). In any regard, the alert indications 246 may be associated with the dose order record 244 in a manner shown in FIG. 7.

The alert interface screen 240 may provide a user certain information regarding the alert indication 246 such as, for example, the alert name, an intervention associated with the alert indication 246, an outcome for the alert indication 246, an indication of when the alert was reviewed, and an indication of the user who review the alert indication 246, etc. In addition, each alert indication 246 may be presented in corresponding relation to an interactive portion 248. As will be described in greater detail below, the interactive portion 248 may be selected by a user of the pharmacy workflow management application 116 to access various functionality associated with the alert generation platform 110.

The alert interface screen 240 may also include a pharmacy workflow management application navigation bar 250. The navigation bar 250 may provide a shortcut to allow for a user to navigate to different respective interface screens of the pharmacy workflow management application 116. For example, the navigation bar 250 may have selectable portions corresponding to a global dose order record listing, a dose order record listing filtered by dose order records awaiting verification by pharmacist, a dose order record listing filtered by dose order records having errors associated therewith, or a dose order record listing filtered by dose order records having alert indications associated therewith. It may be appreciated that the error tab and alert tab may be consolidated into a single listing such that the errors that may be presented in connection with the pharmacy workflow management application 1116 may be processed in a similar manner as the alert indications 246.

A user may select the appropriate portion of the navigation bar 250 to navigate to the alert interface screen 240 that may provide the listing 242 of dose order records 244 filtered by those having alert indications 246 such that the dose order records 244 are shown in corresponding relation to the alert indications 246. The alert interface screen 240 may further include a plurality of navigation tabs 252 that may allow a user to further filter the dose order record listing 242 displayed in the alert interface screen 240. For example, an alert tab may be provided that displays all dose order record listings 244 for which an alert indication is provided 246. Additionally, a hold tab and/or a STAT tab may be provided that, when selected, filters the listing 242 to display only dose order records 244 having an alert indication 246 that caused the corresponding dose order record 244 to have a status change to on hold or STAT depending upon the respective tab selected. In this regard, not all alert indications 246 may result in a dose order record 244 having a status changed. Further still, a tab may be provided to access a report listing corresponding to reports available at the alert generation platform 110 for display in connection with the pharmacy workflow management application 116 as will be described in greater detail below.

In addition to the alert interface screen 240, an alert indication 246 may be provided in other appropriate interface screens of the pharmacy workflow management application 116. One such example is provided in FIG. 8 where a dose verification screen 254 shown. The dose verification screen 254 may show information corresponding to a specific dose order record 244 for purposes of verification by a pharmacist of the dose prepared by a pharmacy technician. In this regard, dose information may be provided for review by the pharmacist including, for example, images of the dose prepared by the pharmacy technician in connection with the dose order. Additionally, the dose verification screen 254 may include an alert indication 246 that corresponds to the given dose order for the dose verification screen 254. That is, in the event an alert indication 246 is present for a given dose order record 244, the pharmacist may be presented the alert indication 246 on the dose verification screen 254 associated with the dose order record 244 at the time the pharmacist is reviewing the dose order information for verification of the dose. While not shown in FIG. 8, the dose verification screen 254 could further include an interactive portion 248 to allow the pharmacist reviewing the dose to access the various functionality associated with the interactive portion 248 described below.

Also, while not depicted in FIG. 8, the dose verification screen 254 may be operative to display aggregated medical information for review by a pharmacist even in the absence of an alert indication. In this regard, the pharmacist may be provided useful aggregated medical information from a plurality of medial information sources for review during the review of the dose order. For instance, the aggregated medical information may be specific to the dose order being verified in the dose verification screen 254. Aggregated medical information regarding a particular drug or product used in the dose may be displayed (e.g., including the number of orders containing the particular drug or product in a given time frame, potential alternatives, possible risks associated with the particular drug or product, etc.). The aggregated medical information may also relate to a given patient associated with the dose order being verified. For instance, information regarding procedures, allergies, medical devices, other ordered drugs/products, or other information particular to the patient may be presented to the pharmacist in connection with the dose verification screen 254.

FIG. 9 further illustrates functionality associated with an interactive portion 248. For example, with returned reference to FIG. 7, the alert interface screen 240 may provide a listing 242 of alert indications 246 that may each include an interactive portion 248. In this regard, the user may, by way of the user interface of the pharmacy workflow management application 116, select the interactive portion 248 to, for example, launch execution of the alert generation platform 110 (e.g., a local instance of the alert generation platform 110) at the pharmacy work station executing the pharmacy workflow management application 116. This is illustrated in FIG. 9. In FIG. 9, the interactive portion 248 has been selected for a given alert indication 246 in the listing 242. In turn, a local instance 256 of the alert generation platform 110 may be launched at the pharmacy workstation executing the pharmacy workflow management application 116.

As described above, the alert generation platform 110 may be executed remotely from the pharmacy workstation executing the pharmacy workflow management application 116. In this regard, the local instance 256 of the alert generation platform 110 may comprise a thin client application executing on the pharmacy workstation that is in operative communication with the alert generation platform 110 (e.g., by way of the medical information processing platform 100) to display information to the user of the pharmacy workstation in relation to the alert generation platform 110. In this regard, the thin client may be used to present the local instance 256 of the alert generation platform 110 to the user of the pharmacy workstation. The thin client may be, for example, an internet browser or the like that may communicate with the alert generation platform 110 (e.g., using html, http, or other appropriate internet protocol). Alternatively, the alert generation platform 110 may, in at least some embodiments, be executed on the same pharmacy workstation executing the pharmacy workflow management application 116. In such an embodiment where the alert generation platform 110 is executed on the same pharmacy workstation as the pharmacy workflow management application 116, selection of the interactive portion 248 may launch a local native instance of the alert generation platform 110 at the pharmacy workstation to allow for interaction with the alert generation platform 110 by the user of the pharmacy workstation.

In any regard, as depicted in FIG. 9, a local instance 256 of the alert generation platform 110 may be presented to the user of the pharmacy workflow management application 116 on the pharmacy workstation utilized by the user. In this regard, the user may interact with the alert generation platform 110 to, for example, obtain additional information regarding the alert indication 246 presented in the listing 242. Furthermore, in the event that the alert indication 246 is a patient specific alert indication, corresponding patient information may be accessed in the local instance 256 of the alert generation platform 110 at the pharmacy workflow management application 116.

While a number of different types of alert data may be generated by the alert generation platform 110 and received at the medical information processing platform 100, a number of specific examples of alert data and corresponding alert indications are provided below, these examples are intended as demonstrative and not limiting. The alert data may include alerts as follows:

Alert Indication
Alert Description

Adverse Drug Event: High Gentamicin trough level:
Alerting when a lab test for a patient has exceeded the

Risk of nephrotoxicity/ototoxicity
safe threshold for Gentamicin. May be triggered if dose

order for Gentamicin for patient in connection with lab

results. May result in dose order being put on hold

status

Adverse Drug Event: Patient on Phenytoin and
These drugs are contraindicated. Given together the

Warfarin
effects of either can be elevated. May be triggered if

patient has dose orders for both drugs in the dose

order listing or in patient history information.

Adverse Drug Event: Possible Nonsteroidal Anti-
Patient may have elevated potassium level following

inflammatory Hyperkalemia
prescription of an NSAID. May be triggered with dose

order for potassium containing ingredient and if lab

results indicate elevated potassium level.

Adverse Drug Event: Patient on Warfarin or IV
Dangerous INR level following prescription of

anticoagulant with high INR
anticoagulant. May be triggered with specific lab

results and dose order for Warfarin or IV

anticoagulant.

CRE from any source
Alerts pharmacist to Multi-drug resistant organism

result. May be triggered upon receipt of lab results

showing CRE

Double Beta-lactam Coverage
Shows when the patient is receiving two antibiotics

from the same class. This may be wasteful in terms of

cost, but also with the potential to further encourage

development of antimicrobial resistance. May be

triggered upon dose order with two Beta-lactam

antibiotics.

Gram Negative Resistant to Therapy
Drug resistant bug alert. Indicates that the patient has

a positive culture for a gram negative organisms which

is resistant to the therapy they are currently receiving.

May be triggered upon history of dose order for

antibiotic and subsequent lab results showing

organism.

Gram Positive Resistant to Therapy
Drug resistant bug alert. Indicates that the patient has

a positive culture for a gram positive organisms which

is resistant to the therapy they are currently receiving.

May be triggered upon history of dose order for

antibiotic and subsequent lab results showing

organism.

MRSA Bacteraemia with no Vancomycin/Linezolid
Bug, no drug alert. Alert may trigger if no dose order

therapy
for Vancomycin or Linezolid is provided after 1 hour of

the positive blood infection result being authorized.

Narrow spectrum antibiotic used with no isolate
Drug, no bug alert. May be triggered upon a narrow

spectrum antibiotic dose order without a specimen

result being received for an organism for which the

antibiotic is appropriate.

New ESBL Infections
Alerts pharmacist to multi-drug resistant organism

result.

Patient on Glycopeptide or Aminoglycoside with Low
Possible indicator of nephrotoxicity following use of

CrCl
certain antibiotics. May require specific lab result and

dose order for certain antibiotics

Patient on Nitrofurantoin
Alerts Pharmacist when a restricted antibiotic

prescription has been issued. May trigger upon

receipt of dose order.

Patient prescribed penicillin class antibiotic and
Alerts to patient who is allergic to penicillin and has a

allergic
dose order for a penicillin-like antibiotic.

Possible Antibiotic or PPI Related C difficile
Alerts that a new C. difficile infection may have been

related to a previous prescription.

Possible antibiotic-related hypokalemia
Potassium levels are low and this could be related to

the use of Nafcillin, penicillin or gentamicin. May

trigger on dose order for suspect drugs in view of

specific lab results.

Patient allergic to Latex
Alerts to patient who is allergic to Latex.

MSSA Bacteraemia with no Cefazolin therapy
Bug, no drug alert. As above, but for Cefazolin.

Risk of Nephrotoxicity: High Vancomycin Trough
High level of Vancomycin still in blood, may need to

Level
consider adjusting dose or timing for next

administration. May trigger upon receipt of dose

order. May result in dose order being put on hold

status.

Antibiotic dose order for longer than 4 days.
Alert to encourage review of the prescription to see if

Consider IV to PO switch
an oral formulation is available, reducing costs and

potentially narrowing spectrum. May trigger on

receipt of antibiotic dose order for treatment to last

longer than 4 days. May result in dose order being

moved to hold status.

Ceftazadime Usage and Incidence of ESBL
Helps identify correlation between antibiotic usage

and incidence of MDRs.

Ceftriaxone Days of Therapy
Shows usage of Ceftriaxone in the facility.

Epileptic prescribed Clarithromycin
Clarithromycin is one of a group of antibiotics than can

trigger a fit in epileptic patients. May trigger upon

dose order for patient with epilepsy in patient history.

Fluoroquinolone prescribed for longer than 6 days
An example of an alert where the pharmacist might

want to review the continued use of the class of

antibiotics. May trigger on receipt of dose order for

treatment to last longer than 6 days. May result in

dose order being moved to hold status.

Patient on Carbapenem
Alerts Pharmacist when a restricted antibiotic

prescription has been issued.

Linezolid/Vancomycin Coverage
Used to alert the pharmacist when a patient has been

moved from one therapy to another, giving them

opportunity to question the decision. May trigger on

receipt of specific dose order sequence.

Vancomycin: Consider switch from IV to oral
Patient has received Vancomycin for longer than 3

days, review and consider a switch to an oral

medication. May trigger upon dose order for longer

than 3 days. May result in subsequent dose order

being moved to hold.

In this regard, the alert generation platform 110 may include additional information received by way of the data connections provided with the alert generation platform 110. For example, the user may be able to review laboratory results, device utilization, medication information, procedure information, treatment information, or other relevant information regarding the patient, the alert indication, a dose order, or other parameter. Furthermore, the user may be operative to review alert data or reporting regarding alerts presented directly in the alert generation platform 110. For instance, the alert data may relate to a microbial organism where no drug has been ordered (e.g., bug, no drug), order of a drug where no microbial organism is present (e.g., drug, no bug), order of an inappropriate drug (e.g., bug, wrong drug), an adverse drug event, abnormal lab results, or any other appropriate alert context.

Additionally, the alert generation platform 110 may maintain responsive inputs in relation to an alert indication provided by the alert generation platform 110. For example, the responsive inputs may correspond to information regarding interventions and/or outcomes associated with an alert. An intervention for an alert indication may include any action, modification of action, or change in action taken in relation to receipt of the alert. Examples of interventions may include monitoring, modification of dose orders, modification of treatment plans, modifications of device utilization, or any other change in connection with the treatment provided to a patient. In this regard, the alert generation platform 110 may provide the intervention information in relation to an alert indication 246. Furthermore, an outcome may be provided that is maintained by the alert generation platform 110 in relation to an outcome associated with the alert indication 244 and/or intervention provided in relation to the alert indication 244. The outcome information may include resolution of diagnoses, further laboratory results, a pharmacy action, or other information.

Accordingly, as depicted in FIG. 10, the alert generation platform 110 may include an intervention detail portion 258. The alert generation platform 110 may be a local instance 256 executed locally relative to the pharmacy workflow management application 116. Alternatively, the alert generation platform 110 may be executed remotely from the pharmacy workflow management application 116. In any regard, the alert generation platform 110 may allow a user of the alert generation platform 110 to provide intervention details 260. To this end, a user interface element may be provided at the alert generation platform 110 to allow the intervention details 260 to be provided. For example, a list of intervention details may be provided for selection for an intervention detail 260 by a user, a text portion for freeform entry of text corresponding to the intervention detail 260 may be provided, radar buttons may be provided for input of intervention detail 260, or other selection or input modalities may be provided to allow user to provide intervention detail 260 to the alert generation platform 110. Furthermore, outcome details may also be provided in a corresponding manner such that the provision of outcome details at the alert generation platform 110 may be reflected at the pharmacy workflow management application 116.

FIG. 10 also depicts an alert interface screen 240. As may be appreciated, the alert interface screen 240 may provide intervention details 260 provided at the local instance 256 or remotely executed alert generation platform 110. That is, the intervention details 260 provided that the alert generation platform 110 may in turn be provided to the pharmacy workflow management application 116 (e.g., by way of the medication information processing platform 100) and be provided in corresponding relation to an alert indication 246 to which the intervention detail 260 corresponds. Outcome details may also be provided in corresponding relation to an alert indication 246 in the alert listing 242 provided on the alert interface screen 240.

With further reference to FIG. 11, the pharmacy workflow management application 116 may also allow a user to provide information regarding intervention details 260 and/or outcome details 266 in relation to an alert indication 246 presented by the pharmacy workflow management application 116. The alert interface screen 240 may allow user to select an alert indication 246. Upon selection of the alert indication 246, a button 262 may become active that, upon selection, provides the user and intervention/outcome dialog box 264. Using inputs provided in the dialog box 264, the user may be allowed to, at the pharmacy workflow management application 116, provide an intervention details 260 and/or outcome details 266 regarding the selected alert indication 246.

As such, the pharmacy workflow management application 116 may be in bidirectional communication with the medical information processing platform 100 to provide to the alert generation platform 110 the intervention detail 260 or outcome detail 266 provided by the user the pharmacy workflow management application 116. That is, intervention detail 260 and/or outcome detail 266 may be provided to either the pharmacy workflow management application 116 or alert generation platform 110 such that the corresponding other one of the pharmacy workflow management application 116 or alert generation platform 110 may reflect the intervention detail 260 or outcome detail 266.

For example, FIG. 12 depicts an alert interface screen 240 and a corresponding instance 256 of the alert generation platform 110. As may be appreciated, outcome details 266 may have been provided by the user of the pharmacy workflow management application 116 utilizing the dialog box 264 for selection of the outcome details 266 at the pharmacy workflow management application 116 for a given one of the alert indications 246. The instance 256 the alert generation platform may receive the outcome details 266 such that the outcome details 266 may be displayed in a intervention detail portion 258 of the instance 256. That is, information provided in relation to the alert indication 246 at the pharmacy workflow management application 116 may be reflected at the alert generation platform 110.

The pharmacy workflow management application 116 may further include functionality in relation to actions to be taken upon receipt of alert indication 246 at the pharmacy workflow management application 116. For instance, the alert generation platform 110 may be operative to provide alert data to the pharmacy workflow management application 116. The pharmacy workflow management application 116 may further have alert processing rules stored in the memory associated with the pharmacy workflow management application 116 that is accessible by a processor associated with the pharmacy workflow management application 116 to configure the processor to process the alert data upon receipt. Specifically, the alert processing rules may define one or more triggering conditions for presentation of the alert indication 246 in the pharmacy workflow management application 116. That is, if the alert data received at the pharmacy workflow management application 116 meets certain predefined criteria defined by the one or more triggering conditions of the alert processing rules, a corresponding alert indication 246 may be provided to the user of the pharmacy workflow management application 116. However, if the alert data does not meet the predefined criteria defined by the one or more triggering conditions of the alert processing rules, the pharmacy workflow management application 116 may not generate any alert indication corresponding to the alert data. The one or more triggering conditions may be selectable or configurable by a user of the pharmacy workflow management application 116 to specifically tailor the alert indications presented to a user of the pharmacy workflow management application 116. Parameters used for the triggering conditions may include patient information of the alert, drug information of the alert, details for the dose order record associated with the alert, or other parameters.

The alert processing rules may also define one or more actions to be taken with respect to a given dose order record 244 in response to receipt of the alert data at the pharmacy workflow management application 116. For example, if the alert data satisfies appropriate alert processing rules, an alert indication 246 may be generated that corresponds to a given dose order record 244 maintained at the pharmacy workflow management application 116. Upon generation of the alert indication 246, further rules may be provided to determine whether the alert indication 246 should result in further action being taken with respect to a given one of the dose order record 244 to which the alert indication corresponds. For example, upon satisfaction one or more triggering conditions, the processor of the pharmacy workflow management application 116 may be operative to execute the one or more actions defined by the alert processing rules with respect to the given dose order record 244 in response to the alert indication 246. For example, a status of the dose order may be modified (e.g., to an on hold status or a stat status). Furthermore, the dose order record may be provided in a specific user interface screen of the pharmacy workflow management application 116. That is, the pharmacy workflow management application 116 may be operative to segregate or separately display dose order records 244 having a given alert indication 246 present for the dose order associated with the alert indication 246.

With respect to FIG. 13, a configuration interface 268 shown. The configuration interface 268 may include a plurality of selections that allow for configuration of actions taken in respect to dose order records 246 for which given alert indications 244, interventions 260, and/or outcomes 266 are received from the alert generation platform 110. For example, a first field 270 may allow for configuration of which alert indications 246, interventions 260, or outcomes 266 that, when received, result in the corresponding dose order record 244 to which the alert data corresponds to be promoted to a STAT (or otherwise elevated or prioritized) status. A second field 272 may allow for configuration of which alert indications 246, interventions 260, or outcomes 266 that, when received, result in the corresponding dose order record 244 to which the alert data corresponds to be placed on hold (e.g., delaying or suspending preparation of the dose order).

Furthermore, FIG. 14 depicts utilization of the navigation tabs 252 to allow for selective display of dose order records 244 for which actions have been taken in response to alert data. In this regard, use of the navigation tabs 252 may allow for presentation of a filtered alert listing 242. In this regard, in the left portion of FIG. 14, the STAT doses navigation tab 252 has been selected. In turn, the alert listing 242 may be filtered such that only dose order records 244 that have been promoted to STAT status in response to receipt of an alert indication 246, intervention 260, or outcome 266, are displayed in the listing 242. In the right portion of FIG. 14, the hold doses navigation tab 252 has been selected. In turn, the alert listing 242 may be filtered such that only dose order records 244 that have been modified to hold status in response to receipt of an alert indication 244, intervention 260, or outcome 266, are displayed in the listing 242. Furthermore, FIG. 15 depicts a dose detail screen 274 that may provide information regarding actions taken with respect to a dose order record 244 based on receipt of alert data, an alert indication 244, intervention 260, or an outcome 266 associated with the dose order record 244.

With further reference to FIG. 16, the navigation tabs 252 may be utilized to navigate to an alert generation platform report listing 276. That is, upon selection of the appropriate navigation tab 252, a report listing 276 may be provided in the pharmacy workflow management application 166 interface that allows a user to select a report corresponding to reports provided by way of the alert generation platform 110. That is, the alert generation platform 110 may provide information corresponding to the reports listed in the report listing 276. In this regard, user the pharmacy workflow management application 116 may select a given one of the reports in the report listing 276 and select a run report button 278.

Upon selection of the run report button 278, a local instance 256 of the alert generation platform 110 may be executed at the pharmacy workflow management application 116. Within the local instance 256, a report 280 may be provided by the alert generation platform 110 and may be displayed to the user the pharmacy workflow management application 116. As may be appreciated, plurality of different types of reports may be provided in the listing 276 for access by a user for display in the local instance 256. For example, reports corresponding to the number of prescriptions for a given drug, the way in which drugs are utilized, the frequency of alerts, cumulative antimicrobial susceptibility information, the number of active medications in a given facility, timelines for interventions, or other information may be provided in various ones of the reports provided in the listing 276. As such, the reports provided in the listing 276 may comprise data related to alert data or may be related to aggregated medical information independent of any alert data.

Furthermore, a user may be capable of accessing a specific patient report 284 provided by the alert generation platform 110 from the alert interface screen 240. In this regard, selection of a given alert indication 246 from the alert listing 242 may enable the print patient report button 282 on the alert interface screen 240. Upon selection of the print patient report button 282, a local instance 256 of the alert generation platform 110 may be launched on the pharmacy workstation executing the pharmacy workflow management application 116. The local instance 256 may display a patient report 284 that may provide details regarding the patient to which the selected alert indication 246 corresponds. A number of different types of information may be provided in the patient report to 84. Examples of which may include, microbiology results, patient observations, patient vitals, patient chart notes, medications prescribed to the patient, devices being utilized by the patient, and/or monitoring trends that may present on a timeline various events, resources, or other parameters related to the patient's care.

While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description is to be considered as exemplary and not restrictive in character. For example, certain embodiments described hereinabove may be combinable with other described embodiments and/or arranged in other ways (e.g., process elements may be performed in other sequences). Accordingly, it should be understood that only the preferred embodiment and variants thereof have been shown and described and that all changes and modifications that come within the spirit of the invention are desired to be protected.

Claims

1. A pharmacy workstation for use in connection with execution of a pharmacy workflow management application, the pharmacy workstation comprising: a memory storing the pharmacy workflow management application;a processor configured to access the pharmacy workflow management application stored in the memory to execute the pharmacy workflow management application; anda dose processing interface in operative communication with the processor, an alert generation platform, and a data source including at least one of a laboratory system, an electronic medical record (“EMR”) system, or an operating room information system, the dose processing interface configured to receive dose order data of an order entry system from the data source, the dose order data comprising medication data regarding a patient specific dose order that has been prescribed for a patient,wherein the processor in cooperation with the alert generation platform are operative to receive, from the data source, infection information indicative of microbial organisms identified in a patient,receive, from the data source via the dose processing interface, the medication data indicative of the patient specific dose order that has been prescribed for the patient,populate the patient specific dose order into a dose order listing displayed by a user interface of the pharmacy workstation,determine, after the patient specific dose order has been prescribed, alert data is to be generated based on the received infection information and the medication data, the alert data indicative that the patient specific dose order conflicts with the infection information indication of the microbial organisms,process the alert data in relation to the dose order listing to associate the alert data with the patient specific dose order in the dose order listing,determine intervention options based on the received infection information and the medication data when the alert data is generated, at least one of the intervention options including a modification of the patient specific dose order, andconfigure the user interface to present an alert indication corresponding to at least a portion of the alert data and the intervention options to a user at the pharmacy workstation in connection with the pharmacy workflow management application,wherein the alert indication and the intervention options are displayed at the user interface of the pharmacy workstation,wherein the user interface further comprises an input device and a patient link that, upon selection by the user by way of an input provided using the input device, instructs the processor to display a patient report corresponding to the patient specific dose order and the related alert data in connection with the pharmacy workflow management application,wherein the input device is configured to receive a responsive input from the user of the pharmacy workflow management application corresponding to a response to the alert indication, wherein the response to the alert indication is entered, by the user, into the pharmacy workflow management application and includes a selection of at least one intervention option,wherein the selection of the intervention option for modifying the patient specific dose order causes the processor to transmit a request to the data source to modify the patient specific dose order,wherein the user interface is in bidirectional communication with the alert generation platform to provide the responsive input to the alert generation platform, andwherein the responsive input comprises instructions for modification of the patient specific dose order associated with the alert indication.
2. The pharmacy workstation of claim 1, wherein the user interface comprises an interactive portion corresponding to the alert indication.
3. The pharmacy workstation of claim 2, wherein the alert indication comprises the interactive portion.
4. The pharmacy workstation of claim 2, wherein the interactive portion, upon selection by the user by way of an input provided using the input device, configures the processor to launch the alert generation platform at the pharmacy workstation.
5. The pharmacy workstation of claim 4, wherein the alert indication is provided on a second user interface of the pharmacy workflow management application corresponding to a pharmacist workspace comprising a listing of dose orders of the pharmacy workflow management application.
6. The pharmacy workstation of claim 4, wherein the alert indication is provided on a second user interface of the pharmacy workflow management application corresponding to an interface for pharmacist verification of the patient specific dose order.
7. The pharmacy workstation of claim 1, wherein the alert data comprises patient specific alert data.
8. The pharmacy workstation of claim 7, wherein the alert data comprises a first patient identifier corresponding to the patient to whom the alert data applies and the patient specific dose order comprises a second patient identifier corresponding to the patient to whom the patient specific dose order is to be administered, and wherein correspondence of the first patient identifier and the second patient identifier results in the alert data being associated with the patient specific dose order.
9. The pharmacy workstation of claim 1, wherein the alert indication is provided in corresponding relation to the patient specific dose order in the pharmacy workflow management application.
10. The pharmacy workstation of claim 1, wherein the memory comprises alert processing rules accessible by the processor for determining the alert data.
11. The pharmacy workstation of claim 10, wherein the alert processing rules define one or more triggering conditions for presentation of the alert indication in the pharmacy workflow management application.
12. The pharmacy workstation of claim 11, wherein upon satisfaction of the one or more triggering conditions, the alert indication is displayed in corresponding relation to one or more dose orders in the dose order listing of the pharmacy workflow management application.
13. The pharmacy workstation of claim 11, wherein the alert processing rules define one or more actions to be taken with respect to the patient specific dose order in response to the alert indication.
14. The pharmacy workstation of claim 13, wherein upon satisfaction of the one or more triggering conditions, the processor is operative to execute the one or more actions with respect to the patient specific dose order in response to the alert indication.
15. The pharmacy workstation of claim 14, wherein the one or more actions to be taken with respect to the patient specific dose order comprises modification of a status of the patient specific dose order in the dose order listing of the pharmacy workflow management application.
16. The pharmacy workstation of claim 15, wherein the pharmacy workflow management application comprises a second user interface for displaying one or more given dose orders for which one or more actions have been taken in response to one or more corresponding alert indications.
17. The pharmacy workstation of claim 1, wherein the user interface is in bidirectional communication with the alert generation platform, and wherein the processor is operative to configure the user interface to present report data in connection with the pharmacy workflow management application that is received from the alert generation platform in response to a request for the report data from the pharmacy workstation.
18. The pharmacy workstation of claim 1, wherein the pharmacy workstation is in operative communication with a server remote from the pharmacy workstation, wherein the processor is in operative communication with the server for communication of the alert data to the server, and wherein the server stores a copy of the alert data in a server memory located at the server.
19. The pharmacy workstation of claim 1, wherein the alert data comprises information related to at least one of infection control or antimicrobial stewardship.

US Referenced Citations (1348)

Number	Name	Date	Kind
641748	Smith	Jan 1900	A
819339	Cleland	May 1906	A
3426150	Tygart	Feb 1969	A
3739943	Williamsen et al.	Jun 1973	A
3742938	Stern	Jul 1973	A
3756752	Stenner	Sep 1973	A
3774762	Lichtenstein	Nov 1973	A
3786190	Pori	Jan 1974	A
3809871	Howard et al.	May 1974	A
3810102	Parks, III et al.	May 1974	A
3848112	Weichselbaum et al.	Nov 1974	A
3858574	Page	Jan 1975	A
3878967	Joslin et al.	Apr 1975	A
3910257	Fletcher et al.	Oct 1975	A
3910260	Sarnoff et al.	Nov 1975	A
3921196	Patterson	Nov 1975	A
3971000	Cromwell	Jul 1976	A
3995630	Verrdonk	Dec 1976	A
3998103	Bjorklund et al.	Dec 1976	A
4032908	Rice et al.	Jun 1977	A
4078562	Friedman	Mar 1978	A
4144496	Cunningham et al.	Mar 1979	A
4151407	McBride et al.	Apr 1979	A
4156867	Bench et al.	May 1979	A
4164320	Irazoqui et al.	Aug 1979	A
4173971	Karz	Nov 1979	A
4199307	Jassawalla	Apr 1980	A
4270532	Franetzki et al.	Jun 1981	A
4273121	Jassawalla	Jun 1981	A
4282872	Franetzki et al.	Aug 1981	A
4308866	Jelliffe et al.	Jan 1982	A
4319338	Grudowski et al.	Mar 1982	A
4320757	Whitney et al.	Mar 1982	A
4354252	Lamb et al.	Oct 1982	A
4369780	Sakai	Jan 1983	A
4370983	Lichtenstein	Feb 1983	A
4373527	Fischell	Feb 1983	A
4381776	Latham, Jr.	May 1983	A
4385630	Gilcher et al.	May 1983	A
4398289	Schoate	Aug 1983	A
4398908	Siposs	Aug 1983	A
4414566	Peyton et al.	Nov 1983	A
4416654	Schoendorfer et al.	Nov 1983	A
4425114	Schoendorfer et al.	Jan 1984	A
4428381	Hepp	Jan 1984	A
4443216	Chappell	Apr 1984	A
4447224	DeCant, Jr. et al.	May 1984	A
4449538	Corbitt et al.	May 1984	A
4451255	Bujan et al.	May 1984	A
4457750	Hill	Jul 1984	A
4458693	Badzinski et al.	Jul 1984	A
4460358	Somerville et al.	Jul 1984	A
4464172	Lichtenstein	Aug 1984	A
4469481	Kobayashi	Sep 1984	A
4475901	Kraegen et al.	Oct 1984	A
4476381	Rubin	Oct 1984	A
4480751	Lueptow	Nov 1984	A
4481670	Freeburg	Nov 1984	A
4487604	Iwatschenko et al.	Dec 1984	A
4490798	Franks et al.	Dec 1984	A
4496351	Hillel et al.	Jan 1985	A
4511352	Theeuwes et al.	Apr 1985	A
4525861	Freeburg	Jun 1985	A
4526574	Pekkarinen	Jul 1985	A
4529401	Leslie et al.	Jul 1985	A
4531527	Reinhold, Jr. et al.	Jul 1985	A
4538138	Harvey et al.	Aug 1985	A
4545071	Freeburg	Oct 1985	A
4551133	Zegers de Beyl et al.	Nov 1985	A
4559038	Berg et al.	Dec 1985	A
4560979	Rosskopf	Dec 1985	A
4561443	Hogrefe et al.	Dec 1985	A
4562751	Nason	Jan 1986	A
4564054	Gustavsson	Jan 1986	A
4590473	Burke et al.	May 1986	A
4602249	Abbott	Jul 1986	A
4619653	Fischell	Oct 1986	A
4622979	Katchis et al.	Nov 1986	A
4624661	Arimond	Nov 1986	A
4636950	Caswell et al.	Jan 1987	A
4637817	Archibald et al.	Jan 1987	A
4650469	Berg et al.	Mar 1987	A
4652262	Veracchi	Mar 1987	A
4653010	Figler et al.	Mar 1987	A
4676776	Howson	Jun 1987	A
4681563	Deckert et al.	Jul 1987	A
4688167	Agarwal	Aug 1987	A
4691580	Fosslien	Sep 1987	A
4695954	Rose et al.	Sep 1987	A
4696671	Epstein et al.	Sep 1987	A
4697928	Csongor	Oct 1987	A
4702595	Mutschler et al.	Oct 1987	A
4705506	Archibald	Nov 1987	A
D293135	Medema et al.	Dec 1987	S
4714462	DiComenico	Dec 1987	A
4717042	McLaughlin	Jan 1988	A
4718576	Tamura et al.	Jan 1988	A
4722224	Scheller et al.	Feb 1988	A
4722349	Baumberg	Feb 1988	A
4722734	Kolln	Feb 1988	A
4730849	Siegel	Mar 1988	A
4731058	Doan	Mar 1988	A
4732411	Siegel	Mar 1988	A
4741732	Crankshaw et al.	May 1988	A
4741736	Brown	May 1988	A
4756706	Kerns et al.	Jul 1988	A
4759756	Forman	Jul 1988	A
4770184	Greene et al.	Sep 1988	A
4778449	Weber et al.	Oct 1988	A
4779626	Peel et al.	Oct 1988	A
4784645	Fischell	Nov 1988	A
4785799	Schoon et al.	Nov 1988	A
4785969	McLaughlin	Nov 1988	A
4796644	Polaschegg	Jan 1989	A
4797840	Fraden	Jan 1989	A
4803625	Fu et al.	Feb 1989	A
4810090	Boucher	Mar 1989	A
4810243	Howson	Mar 1989	A
4811844	Moulding, Jr. et al.	Mar 1989	A
4816208	Woods et al.	Mar 1989	A
4817044	Ogren	Mar 1989	A
4828545	Epstein et al.	May 1989	A
4829524	Yoshida	May 1989	A
4830018	Treach	May 1989	A
4831562	Mcintosh et al.	May 1989	A
4832033	Maher et al.	May 1989	A
4835372	Gombrich et al.	May 1989	A
4835521	Andrejasich et al.	May 1989	A
4838275	Lee	Jun 1989	A
4839806	Goldfischer et al.	Jun 1989	A
4845644	Anthias et al.	Jul 1989	A
4847764	Halvorson	Jul 1989	A
4850009	Zook et al.	Jul 1989	A
4850972	Schulman et al.	Jul 1989	A
4853521	Claeys et al.	Aug 1989	A
4854324	Hirschman et al.	Aug 1989	A
4857713	Brown	Aug 1989	A
4857716	Gombrich et al.	Aug 1989	A
4865584	Epstein et al.	Sep 1989	A
4871351	Feingold	Oct 1989	A
4878175	Norden-Paul et al.	Oct 1989	A
4880013	Chio	Nov 1989	A
4889132	Hutcheson et al.	Dec 1989	A
4889134	Greenwold et al.	Dec 1989	A
4893270	Beck et al.	Jan 1990	A
4897777	Janke et al.	Jan 1990	A
4898209	Zbed	Feb 1990	A
4898576	Philip	Feb 1990	A
4898578	Rubalcaba, Jr.	Feb 1990	A
4901728	Hutchison	Feb 1990	A
4905163	Garber et al.	Feb 1990	A
4908017	Howson et al.	Mar 1990	A
4912623	Rantala et al.	Mar 1990	A
4916441	Gombrich et al.	Apr 1990	A
4922922	Pollock et al.	May 1990	A
4925444	Orkin et al.	May 1990	A
4933843	Scheller et al.	Jun 1990	A
4937777	Flood et al.	Jun 1990	A
4941808	Qureshi et al.	Jul 1990	A
4943279	Samiotes et al.	Jul 1990	A
4943987	Asahina et al.	Jul 1990	A
4946445	Lynn	Aug 1990	A
4949274	Hollander et al.	Aug 1990	A
4952928	Carroll et al.	Aug 1990	A
4953074	Kametani et al.	Aug 1990	A
4960230	Marelli	Oct 1990	A
4964847	Prince	Oct 1990	A
4966579	Polaschegg	Oct 1990	A
4967928	Carter	Nov 1990	A
4968295	Neumann	Nov 1990	A
4975647	Downer et al.	Dec 1990	A
4977590	Milovancevic	Dec 1990	A
4978335	Arthur, III	Dec 1990	A
4991091	Allen	Feb 1991	A
4992926	Janke et al.	Feb 1991	A
4993068	Piosenka et al.	Feb 1991	A
4993506	Angel	Feb 1991	A
4998249	Bennett et al.	Mar 1991	A
5002055	Merki et al.	Mar 1991	A
5003296	Lee	Mar 1991	A
5006699	Felkner et al.	Apr 1991	A
5007429	Treatch et al.	Apr 1991	A
5012402	Akiyama	Apr 1991	A
5012411	Policastro et al.	Apr 1991	A
5014875	McLaughlin et al.	May 1991	A
5016172	Dessertine	May 1991	A
5023770	Siverling	Jun 1991	A
5025374	Roizen et al.	Jun 1991	A
5036852	Leishman	Aug 1991	A
5038800	Oba	Aug 1991	A
5041086	Koenig et al.	Aug 1991	A
5045048	Kaleskas et al.	Sep 1991	A
5047959	Phillips et al.	Sep 1991	A
5053031	Borsanyi	Oct 1991	A
5053990	Kreifels et al.	Oct 1991	A
5055001	Natwick et al.	Oct 1991	A
5057076	Polaschegg	Oct 1991	A
5061243	Winchell et al.	Oct 1991	A
5072356	Watt et al.	Dec 1991	A
5072383	Brimm et al.	Dec 1991	A
5072412	Henderson, Jr. et al.	Dec 1991	A
5078683	Sancoff et al.	Jan 1992	A
5084828	Kaufman et al.	Jan 1992	A
5087245	Doan	Feb 1992	A
5088904	Okada	Feb 1992	A
5088981	Howson et al.	Feb 1992	A
5088990	Hivale et al.	Feb 1992	A
5096385	Georgi et al.	Mar 1992	A
5098377	Borsanyi et al.	Mar 1992	A
5100380	Epstein et al.	Mar 1992	A
5100394	Dudar et al.	Mar 1992	A
5103211	Daoud et al.	Apr 1992	A
5104374	Bishko et al.	Apr 1992	A
5108131	Nassim	Apr 1992	A
5108363	Tuttle et al.	Apr 1992	A
5108367	Epstein et al.	Apr 1992	A
5108372	Swenson	Apr 1992	A
5109487	Ohgomori et al.	Apr 1992	A
5109849	Goodman et al.	May 1992	A
5112319	Lai	May 1992	A
5116203	Natwick et al.	May 1992	A
5116312	Blankenship et al.	May 1992	A
5131092	Sackmann et al.	Jul 1992	A
5134574	Beaverstock et al.	Jul 1992	A
5135500	Zdeb	Aug 1992	A
5137023	Mendelson et al.	Aug 1992	A
5151978	Bronikowski et al.	Sep 1992	A
5152296	Simons	Oct 1992	A
5153416	Neeley	Oct 1992	A
5153827	Coutre et al.	Oct 1992	A
5155693	Altmayer et al.	Oct 1992	A
5157595	Lovrenich	Oct 1992	A
5158091	Butterfield et al.	Oct 1992	A
5159673	Sackmann et al.	Oct 1992	A
5160320	Yum et al.	Nov 1992	A
5161211	Taguchi et al.	Nov 1992	A
5167235	Seacord et al.	Dec 1992	A
5169642	Brinker et al.	Dec 1992	A
5172698	Stanko	Dec 1992	A
5176004	Gaudet	Jan 1993	A
5179569	Sawyer	Jan 1993	A
5179700	Aihara et al.	Jan 1993	A
5181910	Scanlon	Jan 1993	A
5190185	Blechl	Mar 1993	A
5190522	Wojcicki et al.	Mar 1993	A
5191891	Righter	Mar 1993	A
5208762	Charhut et al.	May 1993	A
5208907	Shelton et al.	May 1993	A
5211849	Kitaevich et al.	May 1993	A
5213099	Tripp, Jr.	May 1993	A
5213232	Kraft et al.	May 1993	A
5213568	Lattin et al.	May 1993	A
5219330	Bollish et al.	Jun 1993	A
5219331	Vanderveen	Jun 1993	A
5225974	Mathews et al.	Jul 1993	A
5226425	Righter	Jul 1993	A
5228450	Sellers	Jul 1993	A
5231990	Gauglitz	Aug 1993	A
5234404	Tuttle et al.	Aug 1993	A
5235510	Yamada et al.	Aug 1993	A
5236416	McDaniel et al.	Aug 1993	A
5238001	Gallant et al.	Aug 1993	A
5240007	Pytel et al.	Aug 1993	A
5244463	Cordner, Jr. et al.	Sep 1993	A
5245704	Weber et al.	Sep 1993	A
5254096	Rondelet et al.	Oct 1993	A
5256156	Kern et al.	Oct 1993	A
5256157	Samiotes et al.	Oct 1993	A
5261884	Stern et al.	Nov 1993	A
5262943	Thibado et al.	Nov 1993	A
5265010	Evans-Paganelli et al.	Nov 1993	A
5265431	Gaudet et al.	Nov 1993	A
5267174	Kaufman et al.	Nov 1993	A
5271405	Boyer et al.	Dec 1993	A
5272318	Gorman	Dec 1993	A
5272321	Otsuka et al.	Dec 1993	A
5273517	Barone et al.	Dec 1993	A
5277188	Selker	Jan 1994	A
5283861	Dangler et al.	Feb 1994	A
5284150	Butterfield et al.	Feb 1994	A
5286252	Tuttle et al.	Feb 1994	A
5292029	Pearson	Mar 1994	A
5297257	Struger et al.	Mar 1994	A
5298021	Sherer	Mar 1994	A
5304126	Epstein et al.	Apr 1994	A
5307263	Brown	Apr 1994	A
5307372	Sawyer et al.	Apr 1994	A
5307463	Hyatt et al.	Apr 1994	A
5311908	Barone et al.	May 1994	A
5314243	McDonald et al.	May 1994	A
5315505	Pratt et al.	May 1994	A
5317506	Coutre et al.	May 1994	A
5319363	Welch et al.	Jun 1994	A
5319543	Wilhelm	Jun 1994	A
5321618	Gessman	Jun 1994	A
5321829	Zifferer	Jun 1994	A
5324422	Colleran et al.	Jun 1994	A
5325478	Shelton et al.	Jun 1994	A
5327341	Whalen et al.	Jul 1994	A
5331549	Crawford, Jr.	Jul 1994	A
5336245	Adams et al.	Aug 1994	A
5337230	Baumgartner et al.	Aug 1994	A
5337747	Neftel	Aug 1994	A
5337919	Spaulding et al.	Aug 1994	A
5338157	Blomquist	Aug 1994	A
5339421	Housel, III	Aug 1994	A
5339821	Fujimoto	Aug 1994	A
5341291	Roizen et al.	Aug 1994	A
5341412	Ramot et al.	Aug 1994	A
5348008	Bornn et al.	Sep 1994	A
5348539	Herskowitz	Sep 1994	A
5349675	Fitzgerald et al.	Sep 1994	A
5356378	Doan	Oct 1994	A
5360410	Wacks	Nov 1994	A
5361202	Doue	Nov 1994	A
5361758	Hall et al.	Nov 1994	A
5366896	Margrey et al.	Nov 1994	A
5366904	Qureshi et al.	Nov 1994	A
5367555	Isoyama	Nov 1994	A
5368562	Blomquist et al.	Nov 1994	A
5370612	Maeda et al.	Dec 1994	A
5371687	Holmes, II et al.	Dec 1994	A
5374251	Smith	Dec 1994	A
5374813	Shipp	Dec 1994	A
5374965	Kanno	Dec 1994	A
5375604	Kelly et al.	Dec 1994	A
5376070	Purvis et al.	Dec 1994	A
5377864	Blechl et al.	Jan 1995	A
5378231	Johnson et al.	Jan 1995	A
5379214	Arbuckle et al.	Jan 1995	A
5389078	Zalesky et al.	Feb 1995	A
5390238	Kirk et al.	Feb 1995	A
5392951	Gardner et al.	Feb 1995	A
5395320	Padda et al.	Mar 1995	A
5395321	Kawahara et al.	Mar 1995	A
5398336	Tantry et al.	Mar 1995	A
5401059	Ferrario	Mar 1995	A
5404292	Hendrickson	Apr 1995	A
5404384	Colburn et al.	Apr 1995	A
5406473	Yoshikura et al.	Apr 1995	A
5412715	Volpe	May 1995	A
5415167	Wilk	May 1995	A
5416695	Stutman et al.	May 1995	A
5417222	Dempsey et al.	May 1995	A
5420977	Sztipanovits et al.	May 1995	A
5421343	Feng	Jun 1995	A
5423746	Burkett et al.	Jun 1995	A
5429602	Hauser	Jul 1995	A
5431201	Torchia et al.	Jul 1995	A
5431299	Brewer et al.	Jul 1995	A
5431627	Pastrone et al.	Jul 1995	A
5433736	Nilsson	Jul 1995	A
5438607	Przygoda, Jr. et al.	Aug 1995	A
5440699	Farrand et al.	Aug 1995	A
5441047	David et al.	Aug 1995	A
5445294	Gardner et al.	Aug 1995	A
5445621	Poli et al.	Aug 1995	A
5446868	Gardea, II et al.	Aug 1995	A
5453098	Botts et al.	Sep 1995	A
5455851	Chaco et al.	Oct 1995	A
5458123	Unger	Oct 1995	A
5460294	Williams	Oct 1995	A
5460605	Tuttle et al.	Oct 1995	A
5461665	Shur et al.	Oct 1995	A
5462051	Oka et al.	Oct 1995	A
5464392	Epstein et al.	Nov 1995	A
5465286	Clare et al.	Nov 1995	A
5467773	Bergelson et al.	Nov 1995	A
5468110	McDonald et al.	Nov 1995	A
5469855	Pompei et al.	Nov 1995	A
5471382	Tallman et al.	Nov 1995	A
5474552	Palti	Dec 1995	A
5482043	Zulauf	Jan 1996	A
5482446	Williamson et al.	Jan 1996	A
5485408	Blomquist	Jan 1996	A
5490610	Pearson	Feb 1996	A
5494592	Latham, Jr. et al.	Feb 1996	A
5496265	Langley et al.	Mar 1996	A
5496273	Pastrone et al.	Mar 1996	A
5502944	Kraft et al.	Apr 1996	A
5507412	Ebert et al.	Apr 1996	A
5508912	Schneiderman	Apr 1996	A
5509318	Gomes	Apr 1996	A
5509422	Fukami	Apr 1996	A
5513957	O'Leary	May 1996	A
5514088	Zakko	May 1996	A
5514095	Brightbill et al.	May 1996	A
5515426	Yacenda et al.	May 1996	A
5520450	Colson, Jr. et al.	May 1996	A
5520637	Pager et al.	May 1996	A
5522396	Langer et al.	Jun 1996	A
5522798	Johnson et al.	Jun 1996	A
5526428	Arnold	Jun 1996	A
5528503	Moore et al.	Jun 1996	A
5529063	Hill	Jun 1996	A
5531680	Dumas et al.	Jul 1996	A
5531697	Olsen et al.	Jul 1996	A
5531698	Olsen	Jul 1996	A
5533079	Colburn et al.	Jul 1996	A
5533981	Mandro et al.	Jul 1996	A
5534691	Holdaway et al.	Jul 1996	A
5536084	Curtis et al.	Jul 1996	A
5537313	Pirelli	Jul 1996	A
5537853	Finburgh et al.	Jul 1996	A
5542420	Goldman et al.	Aug 1996	A
5544649	David et al.	Aug 1996	A
5544651	Wilk	Aug 1996	A
5544661	Davis et al.	Aug 1996	A
5545140	Conero et al.	Aug 1996	A
5546580	Seliger et al.	Aug 1996	A
5547470	Johnson et al.	Aug 1996	A
5549117	Tacklind et al.	Aug 1996	A
5549460	O'Leary	Aug 1996	A
5553609	Chen et al.	Sep 1996	A
5558638	Evers et al.	Sep 1996	A
5558640	Pfeiler et al.	Sep 1996	A
5560352	Heim et al.	Oct 1996	A
5562232	Pearson	Oct 1996	A
5562621	Claude et al.	Oct 1996	A
5563347	Martin et al.	Oct 1996	A
5564434	Halperin et al.	Oct 1996	A
5564803	McDonald et al.	Oct 1996	A
5568912	Minami et al.	Oct 1996	A
5569186	Lord et al.	Oct 1996	A
5569187	Kaiser	Oct 1996	A
5571258	Pearson	Nov 1996	A
5573502	LeCocq et al.	Nov 1996	A
5573506	Vasko	Nov 1996	A
5575632	Morris et al.	Nov 1996	A
5576952	Stutman et al.	Nov 1996	A
5579001	Dempsey et al.	Nov 1996	A
5579378	Arlinghaus, Jr.	Nov 1996	A
5581369	Righter et al.	Dec 1996	A
5581687	Lyle et al.	Dec 1996	A
5582593	Hultman	Dec 1996	A
5583758	Mcilroy et al.	Dec 1996	A
5588815	Zaleski, II	Dec 1996	A
5589932	Garcia-Rubio et al.	Dec 1996	A
5590648	Mitchell et al.	Jan 1997	A
5591344	Kenley et al.	Jan 1997	A
5593267	McDonald et al.	Jan 1997	A
5594637	Eisenberg et al.	Jan 1997	A
5594786	Chaco et al.	Jan 1997	A
5597995	Williams et al.	Jan 1997	A
5598536	Slaughter, III et al.	Jan 1997	A
5601445	Schipper et al.	Feb 1997	A
5609575	Larson et al.	Mar 1997	A
5609576	Voss et al.	Mar 1997	A
5613115	Gihl et al.	Mar 1997	A
5619428	Lee et al.	Apr 1997	A
5619991	Sloane	Apr 1997	A
5623652	Vora et al.	Apr 1997	A
5623925	Swenson et al.	Apr 1997	A
5626144	Tacklind et al.	May 1997	A
5628619	Wilson	May 1997	A
5630710	Tune et al.	May 1997	A
5631844	Margrey et al.	May 1997	A
5633910	Cohen	May 1997	A
D380260	Hyman	Jun 1997	S
5634893	Rishton	Jun 1997	A
5637082	Pages et al.	Jun 1997	A
5637093	Hyman et al.	Jun 1997	A
5640301	Roecher et al.	Jun 1997	A
5640953	Bishop et al.	Jun 1997	A
5641628	Bianchi	Jun 1997	A
5643193	Papillon et al.	Jul 1997	A
5643212	Coutre et al.	Jul 1997	A
5647853	Feldmann et al.	Jul 1997	A
5647854	Olsen et al.	Jul 1997	A
5651775	Walker et al.	Jul 1997	A
5652566	Lambert	Jul 1997	A
5658240	Urdahl et al.	Aug 1997	A
5658250	Blomquist et al.	Aug 1997	A
5661978	Holmes et al.	Sep 1997	A
5664270	Bell et al.	Sep 1997	A
5666404	Ciccotelli et al.	Sep 1997	A
D385646	Chan	Oct 1997	S
5678562	Sellers	Oct 1997	A
5678568	Uchikubo et al.	Oct 1997	A
5681285	Ford et al.	Oct 1997	A
5682526	Smokoff et al.	Oct 1997	A
5683367	Jordan et al.	Nov 1997	A
5685844	Marttila	Nov 1997	A
5687717	Halpern	Nov 1997	A
5687734	Dempsey et al.	Nov 1997	A
5695473	Olsen	Dec 1997	A
5697951	Harpstead	Dec 1997	A
5700998	Palti	Dec 1997	A
5701894	Cherry et al.	Dec 1997	A
5704351	Mortara et al.	Jan 1998	A
5704364	Saltzstein et al.	Jan 1998	A
5704366	Tacklind et al.	Jan 1998	A
5712798	Langley et al.	Jan 1998	A
5712912	Tomko et al.	Jan 1998	A
5713485	Liff et al.	Feb 1998	A
5713856	Eggers et al.	Feb 1998	A
5715823	Wood et al.	Feb 1998	A
5716114	Holmes et al.	Feb 1998	A
5716194	Butterfield et al.	Feb 1998	A
5718562	Lawless et al.	Feb 1998	A
5719761	Gatti et al.	Feb 1998	A
RE35743	Pearson	Mar 1998	E
5724025	Tavori	Mar 1998	A
5724580	Levin et al.	Mar 1998	A
5732709	Tacklind et al.	Mar 1998	A
5733259	Valcke et al.	Mar 1998	A
5735887	Barreras, Sr. et al.	Apr 1998	A
5737539	Edelson et al.	Apr 1998	A
5740185	Bosse	Apr 1998	A
5740800	Hendrickson et al.	Apr 1998	A
5745366	Higham et al.	Apr 1998	A
5745378	Barker et al.	Apr 1998	A
5752917	Fuchs	May 1998	A
5752976	Duffin et al.	May 1998	A
5755563	Clegg et al.	May 1998	A
5758095	Albaum et al.	May 1998	A
5764923	Tallman et al.	Jun 1998	A
5766155	Hyman et al.	Jun 1998	A
5769811	Stacey et al.	Jun 1998	A
5771657	Lasher et al.	Jun 1998	A
5772585	Lavin et al.	Jun 1998	A
5772586	Heinonen et al.	Jun 1998	A
5772635	Dastur et al.	Jun 1998	A
5772637	Heinzmann et al.	Jun 1998	A
5776057	Swenson et al.	Jul 1998	A
5778345	McCartney	Jul 1998	A
5778882	Raymond et al.	Jul 1998	A
5781442	Engleson et al.	Jul 1998	A
5782805	Meinzer et al.	Jul 1998	A
5782878	Morgan et al.	Jul 1998	A
5785650	Akasaka et al.	Jul 1998	A
5788669	Peterson	Aug 1998	A
5788851	Kenley et al.	Aug 1998	A
5790409	Fedor et al.	Aug 1998	A
5791342	Woodard	Aug 1998	A
5791880	Wilson	Aug 1998	A
5793861	Haigh	Aug 1998	A
5793969	Kamentsky et al.	Aug 1998	A
5795317	Brierton et al.	Aug 1998	A
5795327	Wilson et al.	Aug 1998	A
5797515	Liff et al.	Aug 1998	A
5800387	Duffy et al.	Sep 1998	A
5801755	Echerer	Sep 1998	A
5803906	Pratt et al.	Sep 1998	A
5805442	Crater et al.	Sep 1998	A
5805454	Valerino et al.	Sep 1998	A
5805456	Higham et al.	Sep 1998	A
5805505	Zheng et al.	Sep 1998	A
5807321	Stoker et al.	Sep 1998	A
5807322	Lindsey et al.	Sep 1998	A
5807336	Russo et al.	Sep 1998	A
5810747	Brudny et al.	Sep 1998	A
5812410	Lion et al.	Sep 1998	A
5814015	Gargano et al.	Sep 1998	A
5815566	Ramot et al.	Sep 1998	A
5818528	Roth et al.	Oct 1998	A
5822418	Yacenda et al.	Oct 1998	A
5822544	Chaco et al.	Oct 1998	A
5823949	Goltra	Oct 1998	A
5826237	Macrae et al.	Oct 1998	A
5829438	Gibbs et al.	Nov 1998	A
5832447	Rieker et al.	Nov 1998	A
5832448	Brown	Nov 1998	A
5832450	Myers et al.	Nov 1998	A
5833599	Schrier et al.	Nov 1998	A
5835897	Dang	Nov 1998	A
5836910	Duffy et al.	Nov 1998	A
5841975	Layne et al.	Nov 1998	A
5842841	Danby et al.	Dec 1998	A
5842976	Williamson	Dec 1998	A
5845253	Rensimer et al.	Dec 1998	A
5848593	McGrady et al.	Dec 1998	A
5851186	Wood et al.	Dec 1998	A
5852590	De La Huerga	Dec 1998	A
5853387	Clegg et al.	Dec 1998	A
5855550	Lai et al.	Jan 1999	A
5857967	Frid et al.	Jan 1999	A
5859972	Subramaniam et al.	Jan 1999	A
5865745	Schmitt et al.	Feb 1999	A
5865786	Sibalis et al.	Feb 1999	A
5867821	Ballantyne et al.	Feb 1999	A
5871465	Vasko	Feb 1999	A
5876926	Beecham	Mar 1999	A
5880443	McDonald et al.	Mar 1999	A
5882338	Gray	Mar 1999	A
5883370	Walker et al.	Mar 1999	A
5883576	De La Huerga	Mar 1999	A
5884273	Sattizahn et al.	Mar 1999	A
5884457	Ortiz et al.	Mar 1999	A
5885245	Lynch et al.	Mar 1999	A
5891035	Wood et al.	Apr 1999	A
5891734	Gill et al.	Apr 1999	A
5893697	Zimi et al.	Apr 1999	A
5894273	Meador et al.	Apr 1999	A
5895371	Levitas et al.	Apr 1999	A
5897493	Brown	Apr 1999	A
5897530	Jackson	Apr 1999	A
5897989	Beecham	Apr 1999	A
5899665	Makino et al.	May 1999	A
5899855	Brown	May 1999	A
5901150	Jhuboo et al.	May 1999	A
5904668	Hyman et al.	May 1999	A
5905653	Higham et al.	May 1999	A
5907291	Chen et al.	May 1999	A
5907493	Boyer et al.	May 1999	A
5908027	Butterfield et al.	Jun 1999	A
5910107	Iliff	Jun 1999	A
5910252	Truitt et al.	Jun 1999	A
5911132	Sloane	Jun 1999	A
5911687	Sato et al.	Jun 1999	A
5912818	McGrady et al.	Jun 1999	A
5913197	Kameda	Jun 1999	A
5913310	Brown	Jun 1999	A
5915089	Stevens et al.	Jun 1999	A
5915240	Karpf	Jun 1999	A
5919154	Toavs et al.	Jul 1999	A
5921938	Aoyama et al.	Jul 1999	A
5923018	Kameda et al.	Jul 1999	A
5924074	Evans	Jul 1999	A
5924103	Ahmed et al.	Jul 1999	A
5927540	Godlewski	Jul 1999	A
5931791	Saltzstein et al.	Aug 1999	A
5935060	Iliff	Aug 1999	A
5935099	Peterson et al.	Aug 1999	A
5935106	Olsen	Aug 1999	A
5938413	Makino et al.	Aug 1999	A
5939326	Chupp et al.	Aug 1999	A
5939699	Perttunen et al.	Aug 1999	A
5940306	Gardner et al.	Aug 1999	A
5940802	Hildebrand et al.	Aug 1999	A
5941829	Saltzstein et al.	Aug 1999	A
5941846	Duffy et al.	Aug 1999	A
5942986	Shabot et al.	Aug 1999	A
5943423	Muftic	Aug 1999	A
5943633	Wilson et al.	Aug 1999	A
5944659	Flach et al.	Aug 1999	A
5945651	Chorosinski et al.	Aug 1999	A
5946083	Melendez et al.	Aug 1999	A
5946659	Lancelot et al.	Aug 1999	A
D414578	Chen et al.	Sep 1999	S
5950006	Crater et al.	Sep 1999	A
5951300	Brown	Sep 1999	A
5951510	Barak	Sep 1999	A
5954640	Szabo	Sep 1999	A
5954885	Bollish et al.	Sep 1999	A
5954971	Pages et al.	Sep 1999	A
5956023	Lyle et al.	Sep 1999	A
5957885	Bollish et al.	Sep 1999	A
5959529	Kail, IV	Sep 1999	A
5960085	de la Huerga	Sep 1999	A
5960403	Brown	Sep 1999	A
5960991	Ophardt	Oct 1999	A
5961446	Beller et al.	Oct 1999	A
5961448	Swenson et al.	Oct 1999	A
5961487	Davis	Oct 1999	A
5961923	Nova et al.	Oct 1999	A
5963641	Crandall et al.	Oct 1999	A
5964700	Tallman et al.	Oct 1999	A
5966304	Cook et al.	Oct 1999	A
5967975	Ridgeway	Oct 1999	A
5970423	Langley et al.	Oct 1999	A
5971593	McGrady	Oct 1999	A
5971921	Timbel	Oct 1999	A
5971948	Pages et al.	Oct 1999	A
5974124	Schlueter, Jr. et al.	Oct 1999	A
5975737	Crater et al.	Nov 1999	A
5980490	Tsoukalis	Nov 1999	A
5983193	Heinonen et al.	Nov 1999	A
5987519	Peifer et al.	Nov 1999	A
5991731	Colon et al.	Nov 1999	A
5993046	McGrady et al.	Nov 1999	A
5993420	Hyman et al.	Nov 1999	A
5995077	Wilcox et al.	Nov 1999	A
5995939	Berman et al.	Nov 1999	A
5995965	Experton	Nov 1999	A
5997167	Crater et al.	Dec 1999	A
5997476	Brown	Dec 1999	A
6003006	Colella et al.	Dec 1999	A
6004020	Bartur	Dec 1999	A
6004276	Wright et al.	Dec 1999	A
6006191	DeRienzo	Dec 1999	A
6006946	Williams et al.	Dec 1999	A
6009333	Chaco	Dec 1999	A
6010454	Arieff et al.	Jan 2000	A
6011858	Stock et al.	Jan 2000	A
6011999	Holmes	Jan 2000	A
6012034	Hamparian et al.	Jan 2000	A
6013057	Danby et al.	Jan 2000	A
6014631	Teagarden et al.	Jan 2000	A
6016444	John	Jan 2000	A
6017318	Gauthier et al.	Jan 2000	A
6018713	Coli et al.	Jan 2000	A
6019745	Gray	Feb 2000	A
6021392	Lester et al.	Feb 2000	A
6022315	Iliff	Feb 2000	A
6023522	Draganoff et al.	Feb 2000	A
6024539	Blomquist	Feb 2000	A
6024699	Surwit et al.	Feb 2000	A
6027217	McClure et al.	Feb 2000	A
6029138	Khorasani et al.	Feb 2000	A
6032119	Brown et al.	Feb 2000	A
6032155	de la Huerga	Feb 2000	A
6033076	Braeuning et al.	Mar 2000	A
6039251	Holowko et al.	Mar 2000	A
6039467	Holmes	Mar 2000	A
6047259	Campbell et al.	Apr 2000	A
6048086	Valerino	Apr 2000	A
6050940	Braun et al.	Apr 2000	A
6055487	Margery et al.	Apr 2000	A
6057758	Dempsey et al.	May 2000	A
6059736	Tapper	May 2000	A
6061603	Papadopoulos et al.	May 2000	A
6065819	Holmes et al.	May 2000	A
6068153	Young et al.	May 2000	A
6068156	Liff et al.	May 2000	A
6073046	Patel et al.	Jun 2000	A
6074345	van Oostrom et al.	Jun 2000	A
6079621	Vardanyan et al.	Jun 2000	A
6080106	Lloyd et al.	Jun 2000	A
6081048	Bergmann et al.	Jun 2000	A
6081786	Barry et al.	Jun 2000	A
6082776	Feinberg	Jul 2000	A
6083206	Molko	Jul 2000	A
6093146	Filangeri	Jul 2000	A
6095985	Raymond et al.	Aug 2000	A
6096561	Tayi	Aug 2000	A
6098892	Peoples, Jr.	Aug 2000	A
6101407	Groezinger	Aug 2000	A
6101478	Brown	Aug 2000	A
6102856	Groff et al.	Aug 2000	A
6108399	Hernandez-Guerra et al.	Aug 2000	A
6108588	McGrady	Aug 2000	A
6109774	Holmes et al.	Aug 2000	A
6112224	Peifer et al.	Aug 2000	A
RE36871	Epstein et al.	Sep 2000	E
6113554	Gilcher et al.	Sep 2000	A
6116461	Broadfield et al.	Sep 2000	A
6117940	Mjalli	Sep 2000	A
6123524	Danby et al.	Sep 2000	A
6125350	Dirbas	Sep 2000	A
6129517	Danby et al.	Oct 2000	A
6132371	Dempsey et al.	Oct 2000	A
6134504	Douglas et al.	Oct 2000	A
6135949	Russo et al.	Oct 2000	A
6139177	Venkatraman et al.	Oct 2000	A
6139495	De La Huerga	Oct 2000	A
6141412	Smith et al.	Oct 2000	A
6144922	Douglas et al.	Nov 2000	A
6145695	Garrigues	Nov 2000	A
6146523	Kenley et al.	Nov 2000	A
6148297	Swor et al.	Nov 2000	A
6149063	Reynolds et al.	Nov 2000	A
6151536	Arnold et al.	Nov 2000	A
6152364	Schoonen et al.	Nov 2000	A
6154668	Pedersen et al.	Nov 2000	A
6154726	Rensimer et al.	Nov 2000	A
6157914	Seto et al.	Dec 2000	A
6158965	Butterfield et al.	Dec 2000	A
6160478	Jacobsen et al.	Dec 2000	A
6161095	Brown	Dec 2000	A
6161141	Dillon	Dec 2000	A
6163737	Fedor et al.	Dec 2000	A
6165154	Gray et al.	Dec 2000	A
6168563	Brown	Jan 2001	B1
6170007	Venkatraman et al.	Jan 2001	B1
6170746	Brook et al.	Jan 2001	B1
6171112	Clark et al.	Jan 2001	B1
6171237	Avitall et al.	Jan 2001	B1
6171264	Bader	Jan 2001	B1
6173198	Schulze et al.	Jan 2001	B1
6175779	Barrett	Jan 2001	B1
6175977	Schumacher et al.	Jan 2001	B1
6176392	William et al.	Jan 2001	B1
6182047	Dirbas	Jan 2001	B1
6183417	Geheb et al.	Feb 2001	B1
6186145	Brown	Feb 2001	B1
6192320	Margrey et al.	Feb 2001	B1
6193480	Butterfield	Feb 2001	B1
6195887	Danby et al.	Mar 2001	B1
6198394	Jacobsen et al.	Mar 2001	B1
6200264	Satherley et al.	Mar 2001	B1
6200289	Hochman et al.	Mar 2001	B1
6202923	Boyer et al.	Mar 2001	B1
6203495	Bardy	Mar 2001	B1
6203528	Deckert et al.	Mar 2001	B1
6206238	Ophardt	Mar 2001	B1
6206829	Iliff	Mar 2001	B1
6210361	Kamen et al.	Apr 2001	B1
6213391	Lewis	Apr 2001	B1
6213738	Danby et al.	Apr 2001	B1
6213972	Butterfield et al.	Apr 2001	B1
6219439	Burger	Apr 2001	B1
6219587	Ahlin et al.	Apr 2001	B1
6221009	Doi et al.	Apr 2001	B1
6221011	Bardy	Apr 2001	B1
6221012	Maschke et al.	Apr 2001	B1
6222619	Herron et al.	Apr 2001	B1
6224549	Drongelen	May 2001	B1
6225901	Kail, IV	May 2001	B1
6226564	Stuart	May 2001	B1
6226745	Wiederhold	May 2001	B1
6230142	Benigno et al.	May 2001	B1
6230927	Schoonen et al.	May 2001	B1
6234997	Kamen et al.	May 2001	B1
6245013	Minoz et al.	Jun 2001	B1
6246473	Smith, Jr. et al.	Jun 2001	B1
6248063	Barnhill et al.	Jun 2001	B1
6248065	Brown	Jun 2001	B1
6255951	De La Huerga	Jul 2001	B1
6256643	Cork et al.	Jul 2001	B1
6256967	Hebron et al.	Jul 2001	B1
6259355	Chaco et al.	Jul 2001	B1
6259654	De La Huerga	Jul 2001	B1
6260021	Wong et al.	Jul 2001	B1
6266645	Simpson	Jul 2001	B1
6269340	Ford et al.	Jul 2001	B1
D446854	Cheney, II et al.	Aug 2001	S
6270455	Brown	Aug 2001	B1
6270457	Bardy	Aug 2001	B1
6272394	Lipps	Aug 2001	B1
6272505	De La Huerga	Aug 2001	B1
6277072	Bardy	Aug 2001	B1
6278999	Knapp	Aug 2001	B1
6283322	Liff et al.	Sep 2001	B1
6283944	McMullen et al.	Sep 2001	B1
6290646	Cosentino et al.	Sep 2001	B1
6290650	Butterfield et al.	Sep 2001	B1
6294999	Yarin et al.	Sep 2001	B1
6295506	Heinonen	Sep 2001	B1
6304788	Eady et al.	Oct 2001	B1
6306088	Krausman et al.	Oct 2001	B1
6307956	Black	Oct 2001	B1
6308171	De La Huerga	Oct 2001	B1
6311163	Sheehan et al.	Oct 2001	B1
6312227	Davis	Nov 2001	B1
6312378	Bardy	Nov 2001	B1
6314384	Goetz	Nov 2001	B1
6317719	Schrier et al.	Nov 2001	B1
6319200	Lai et al.	Nov 2001	B1
6321203	Kameda	Nov 2001	B1
6322502	Schoenberg et al.	Nov 2001	B1
6322504	Kirshner	Nov 2001	B1
6322515	Goor et al.	Nov 2001	B1
6330491	Lion	Dec 2001	B1
6332090	DeFrank et al.	Dec 2001	B1
RE37531	Chaco et al.	Jan 2002	E
6337631	Pai et al.	Jan 2002	B1
6338007	Broadfield et al.	Jan 2002	B1
6339732	Phoon et al.	Jan 2002	B1
6345260	Cummings, Jr. et al.	Feb 2002	B1
6346886	De La Huerga	Feb 2002	B1
6347553	Morris et al.	Feb 2002	B1
6352200	Schoonen et al.	Mar 2002	B1
6353817	Jacobs et al.	Mar 2002	B1
6358225	Butterfield	Mar 2002	B1
6358237	Paukovits et al.	Mar 2002	B1
6361263	Dewey et al.	Mar 2002	B1
6362591	Moberg	Mar 2002	B1
6363282	Nichols et al.	Mar 2002	B1
6363290	Lyle et al.	Mar 2002	B1
6364834	Reuss et al.	Apr 2002	B1
6368273	Brown	Apr 2002	B1
6370841	Chudy et al.	Apr 2002	B1
6381577	Brown	Apr 2002	B1
6385505	Lipps	May 2002	B1
6393369	Carr	May 2002	B1
6397190	Goetz	May 2002	B1
6401072	Haudenschild et al.	Jun 2002	B1
6402702	Gilcher et al.	Jun 2002	B1
6406426	Reuss et al.	Jun 2002	B1
6407335	Franklin-Lees et al.	Jun 2002	B1
6408330	DeLaHuerga	Jun 2002	B1
6416471	Kumar et al.	Jul 2002	B1
6421650	Goetz et al.	Jul 2002	B1
6424996	Killcommons et al.	Jul 2002	B1
6427088	Bowman, IV et al.	Jul 2002	B1
6434531	Lancelot et al.	Aug 2002	B1
6434569	Tomlinson et al.	Aug 2002	B1
6438451	Lion	Aug 2002	B1
RE37829	Charhut et al.	Sep 2002	E
6449927	Hebron et al.	Sep 2002	B2
6450956	Rappaport et al.	Sep 2002	B1
6458102	Mann et al.	Oct 2002	B1
6461037	O'Leary	Oct 2002	B1
6463310	Swedlow et al.	Oct 2002	B1
6468242	Wilson et al.	Oct 2002	B1
6470234	McGrady	Oct 2002	B1
6471089	Liff et al.	Oct 2002	B2
6471645	Warkentin et al.	Oct 2002	B1
6471646	Thede	Oct 2002	B1
6475146	Frelburger et al.	Nov 2002	B1
6475148	Jackson et al.	Nov 2002	B1
6475180	Peterson et al.	Nov 2002	B2
6478737	Bardy	Nov 2002	B2
6485465	Moberg et al.	Nov 2002	B2
6494831	Koritzinsky	Dec 2002	B1
6511138	Gardner et al.	Jan 2003	B1
6519569	White et al.	Feb 2003	B1
6537244	Paukovits	Mar 2003	B2
6542902	Dulong et al.	Apr 2003	B2
6542910	Cork et al.	Apr 2003	B2
6544174	West et al.	Apr 2003	B2
6544228	Heitmeier	Apr 2003	B1
6551243	Bocionek et al.	Apr 2003	B2
6551276	Mann et al.	Apr 2003	B1
6554791	Cartledge et al.	Apr 2003	B1
6554798	Mann et al.	Apr 2003	B1
6555986	Moberg	Apr 2003	B2
6558321	Burd et al.	May 2003	B1
6561975	Pool et al.	May 2003	B1
6562001	Lebel et al.	May 2003	B2
6564104	Nelson et al.	May 2003	B2
6564105	Starkweather et al.	May 2003	B2
6564121	Wallace et al.	May 2003	B1
6571128	Lebel et al.	May 2003	B2
6575900	Zweig et al.	Jun 2003	B1
6577899	Lebel et al.	Jun 2003	B2
6579232	Sakamaki et al.	Jun 2003	B2
6581069	Robinson et al.	Jun 2003	B1
6581798	Liff et al.	Jun 2003	B2
6584336	Ali et al.	Jun 2003	B1
6585157	Brandt et al.	Jul 2003	B2
6585644	Lebel et al.	Jul 2003	B2
6585675	O'Mahony et al.	Jul 2003	B1
6592551	Cobb	Jul 2003	B1
6593528	Franklin-Lees et al.	Jul 2003	B2
6602469	Maus et al.	Aug 2003	B1
6607485	Bardy	Aug 2003	B2
6610973	Davis, III	Aug 2003	B1
6613009	Bainbridge et al.	Sep 2003	B1
6616633	Butterfield et al.	Sep 2003	B1
6635014	Starkweather et al.	Oct 2003	B2
6648821	Lebel et al.	Nov 2003	B2
6659948	Lebel et al.	Dec 2003	B2
6664893	Eveland et al.	Dec 2003	B1
6668196	Villegas et al.	Dec 2003	B1
6669663	Thompson	Dec 2003	B1
6673314	Burbank et al.	Jan 2004	B1
6687546	Lebel et al.	Jan 2004	B2
6689091	Bui et al.	Feb 2004	B2
6694191	Starkweather et al.	Feb 2004	B2
6694334	DuLong et al.	Feb 2004	B2
6711460	Reese	Mar 2004	B1
6731324	Levy	May 2004	B2
6733447	Lai et al.	May 2004	B2
6735497	Wallace et al.	May 2004	B2
6740075	Lebel et al.	May 2004	B2
6746398	Hervy et al.	Jun 2004	B2
6758810	Lebel et al.	Jul 2004	B2
6768425	Flaherty et al.	Jul 2004	B2
6771369	Rzasa et al.	Aug 2004	B2
6775602	Gordon, Jr. et al.	Aug 2004	B2
6776304	Liff et al.	Aug 2004	B2
6790198	White et al.	Sep 2004	B1
6804656	Rosenfeld et al.	Oct 2004	B1
6810290	Lebel et al.	Oct 2004	B2
6811533	Lebel et al.	Nov 2004	B2
6811534	Bowman, IV et al.	Nov 2004	B2
6811707	Rovatti et al.	Nov 2004	B2
6813473	Bruker	Nov 2004	B1
6813519	Lebel et al.	Nov 2004	B2
6814255	Liff et al.	Nov 2004	B2
6820093	De La Huerga	Nov 2004	B2
6842736	Brzozowski	Jan 2005	B1
6847861	Lunak et al.	Jan 2005	B2
6854088	Massengale et al.	Feb 2005	B2
6871211	Labounty et al.	Mar 2005	B2
6873268	Lebel et al.	Mar 2005	B2
6877530	Osborne et al.	Apr 2005	B2
6880034	Manke et al.	Apr 2005	B2
6885288	Pincus	Apr 2005	B2
6887201	Bardy	May 2005	B2
6892941	Rosenblum	May 2005	B2
6912549	Rotter et al.	Jun 2005	B2
6913590	Sorenson et al.	Jul 2005	B2
6915265	Johnson	Jul 2005	B1
6915823	Osborne et al.	Jul 2005	B2
6928452	De La Huerga	Aug 2005	B2
6950708	Bowman, IV et al.	Sep 2005	B2
6958705	Lebel et al.	Oct 2005	B2
6974437	Lebel et al.	Dec 2005	B2
6975924	Kircher et al.	Dec 2005	B2
6976628	Krupa	Dec 2005	B2
6979306	Moll	Dec 2005	B2
6980958	Surwit et al.	Dec 2005	B1
6981644	Cheong et al.	Jan 2006	B2
6985870	Martucci et al.	Jan 2006	B2
6991002	Osborne et al.	Jan 2006	B2
6995664	Darling	Feb 2006	B1
7006893	Hart et al.	Feb 2006	B2
7015806	Naidoo et al.	Mar 2006	B2
7017622	Osborne et al.	Mar 2006	B2
7017623	Tribble et al.	Mar 2006	B2
7028723	Alouani et al.	Apr 2006	B1
7096212	Tribble et al.	Aug 2006	B2
7117902	Osborne	Oct 2006	B2
7151982	Liff et al.	Dec 2006	B2
7194336	DiGianfilippo et al.	Mar 2007	B2
7209891	Addy et al.	Apr 2007	B1
7213009	Pestotnik	May 2007	B2
7240699	Osborne et al.	Jul 2007	B2
7255680	Gharib	Aug 2007	B1
7277579	Huang	Oct 2007	B2
7277757	Casavant et al.	Oct 2007	B2
7317967	DiGianfilippo et al.	Jan 2008	B2
7321861	Oon	Jan 2008	B1
7343224	DiGianfilippo et al.	Mar 2008	B2
7403901	Carley et al.	Jul 2008	B1
7427002	Liff et al.	Sep 2008	B2
7493263	Helmus et al.	Feb 2009	B2
7499581	Tribble et al.	Mar 2009	B2
7509280	Haudenschild	Mar 2009	B1
7555557	Bradley et al.	Jun 2009	B2
7561312	Proudfoot et al.	Jul 2009	B1
7581953	Lehmann et al.	Sep 2009	B2
7599516	Limer et al.	Oct 2009	B2
7610115	Rob et al.	Oct 2009	B2
7630908	Amrien et al.	Dec 2009	B1
7636718	Steen et al.	Dec 2009	B1
7672859	Louie et al.	Mar 2010	B1
7698019	Moncrief et al.	Apr 2010	B2
7698154	Marchosky	Apr 2010	B2
7734478	Goodall et al.	Jun 2010	B2
7753085	Tribble et al.	Jul 2010	B2
7769601	Bleser et al.	Aug 2010	B1
7783383	Eliuk et al.	Aug 2010	B2
D624225	Federico et al.	Sep 2010	S
7801642	Ansari et al.	Sep 2010	B2
7847970	McGrady	Dec 2010	B1
7853621	Guo	Dec 2010	B2
7904822	Monteleone et al.	Mar 2011	B2
7931859	Mlodzinski et al.	Apr 2011	B2
7937290	Bahir	May 2011	B2
7986369	Burns	Jul 2011	B1
7991507	Liff et al.	Aug 2011	B2
8165893	Goldberg	Apr 2012	B1
8170271	Chen	May 2012	B2
8191339	Tribble et al.	Jun 2012	B2
8215557	Reno et al.	Jul 2012	B1
8220503	Tribble et al.	Jul 2012	B2
8225824	Eliuk et al.	Jul 2012	B2
D667961	Marmier	Sep 2012	S
8267129	Doherty et al.	Sep 2012	B2
8271128	Schultz	Sep 2012	B1
8271138	Eliuk et al.	Sep 2012	B2
8280549	Liff et al.	Oct 2012	B2
8284305	Newcomb et al.	Oct 2012	B2
8374887	Alexander	Feb 2013	B1
8386070	Eliuk et al.	Feb 2013	B2
8548824	daCosta	Oct 2013	B1
8554579	Tribble et al.	Oct 2013	B2
D693480	Spiess et al.	Nov 2013	S
8595206	Ansari	Nov 2013	B1
8666541	Ansari et al.	Mar 2014	B1
8678047	Tribble et al.	Mar 2014	B2
8810408	Hanson	Aug 2014	B2
D715958	Bossart et al.	Oct 2014	S
9053218	Osborne et al.	Jun 2015	B2
D733480	Shao	Jul 2015	S
D738152	Grasselli et al.	Sep 2015	S
D753428	Shao	Apr 2016	S
9362969	Burgess et al.	Jun 2016	B1
9382021	Tribble et al.	Jul 2016	B2
9662273	Ranalletta et al.	May 2017	B2
9930297	Alexander et al.	Mar 2018	B2
9956145	Thompson et al.	May 2018	B2
20010001237	Stroda et al.	May 2001	A1
20010003177	Schena et al.	Jun 2001	A1
20010007053	Bardy	Jul 2001	A1
20010007932	Kamen et al.	Jul 2001	A1
20010011153	Bardy	Aug 2001	A1
20010016699	Burbank et al.	Aug 2001	A1
20010017817	De La Huerga	Aug 2001	A1
20010021801	Bardy	Sep 2001	A1
20010025138	Bardy	Sep 2001	A1
20010025156	Bui et al.	Sep 2001	A1
20010027634	Hebron et al.	Oct 2001	A1
20010028308	De La Huerga	Oct 2001	A1
20010030234	Wiklof	Oct 2001	A1
20010031944	Peterson et al.	Oct 2001	A1
20010032101	Statius Muller	Oct 2001	A1
20010034502	Moberg et al.	Oct 2001	A1
20010034614	Fletcher-Haynes et al.	Oct 2001	A1
20010034616	Giannini	Oct 2001	A1
20010037057	Bardy	Nov 2001	A1
20010037083	Hartlaub et al.	Nov 2001	A1
20010037217	Abensour et al.	Nov 2001	A1
20010037220	Merry et al.	Nov 2001	A1
20010041920	Starkweather et al.	Nov 2001	A1
20010044588	Mault	Nov 2001	A1
20010044731	Coffman et al.	Nov 2001	A1
20010047125	Quy	Nov 2001	A1
20010051764	Bardy	Dec 2001	A1
20010053885	Gielen et al.	Dec 2001	A1
20020002326	Causey, III et al.	Jan 2002	A1
20020002473	Schrier et al.	Jan 2002	A1
20020004645	Carlisle et al.	Jan 2002	A1
20020007285	Rappaport	Jan 2002	A1
20020010568	Rubbert et al.	Jan 2002	A1
20020010679	Felsher	Jan 2002	A1
20020013612	Whitehurst	Jan 2002	A1
20020016567	Hochman et al.	Feb 2002	A1
20020016568	Lebel et al.	Feb 2002	A1
20020016719	Nemeth et al.	Feb 2002	A1
20020016722	Kameda	Feb 2002	A1
20020019606	Lebel et al.	Feb 2002	A1
20020019748	Brown	Feb 2002	A1
20020022776	Bardy	Feb 2002	A1
20020025796	Taylor et al.	Feb 2002	A1
20020026104	Bardy	Feb 2002	A1
20020029157	Marchosky	Mar 2002	A1
20020029776	Blomquist	Mar 2002	A1
20020032582	Feeney et al.	Mar 2002	A1
20020032602	Lanzillo, Jr. et al.	Mar 2002	A1
20020038392	De La Huerga	Mar 2002	A1
20020040208	Flaherty et al.	Apr 2002	A1
20020044043	Chaco et al.	Apr 2002	A1
20020046062	Kameda	Apr 2002	A1
20020046185	Villart et al.	Apr 2002	A1
20020046346	Evans	Apr 2002	A1
20020052539	Haller et al.	May 2002	A1
20020052542	Bardy	May 2002	A1
20020052574	Hochman et al.	May 2002	A1
20020062227	Yuyama	May 2002	A1
20020062229	Alban et al.	May 2002	A1
20020065540	Lebel et al.	May 2002	A1
20020065686	Monteleone et al.	May 2002	A1
20020067273	Jaques et al.	Jun 2002	A1
20020072733	Flaherty	Jun 2002	A1
20020073250	Ommering	Jun 2002	A1
20020077852	Ford et al.	Jun 2002	A1
20020077865	Sullivan	Jun 2002	A1
20020082480	Riff et al.	Jun 2002	A1
20020082865	Bianco et al.	Jun 2002	A1
20020082868	Pories et al.	Jun 2002	A1
20020084904	De La Huerga	Jul 2002	A1
20020087120	Rogers et al.	Jul 2002	A1
20020091309	Auer	Jul 2002	A1
20020099283	Christ et al.	Jul 2002	A1
20020099301	Bardy	Jul 2002	A1
20020100762	Liff et al.	Aug 2002	A1
20020107476	Mann et al.	Aug 2002	A1
20020107707	Naparstek et al.	Aug 2002	A1
20020116226	Auer et al.	Aug 2002	A1
20020116509	De La Huerga	Aug 2002	A1
20020128606	Cowan et al.	Sep 2002	A1
20020128871	Adamson et al.	Sep 2002	A1
20020128880	Kunikiyo	Sep 2002	A1
20020133377	Brown	Sep 2002	A1
20020140675	Ali et al.	Oct 2002	A1
20020143254	Maruyama	Oct 2002	A1
20020156462	Stultz	Oct 2002	A1
20020158128	Ashiuro	Oct 2002	A1
20020165491	Reilly	Nov 2002	A1
20020169636	Eggers et al.	Nov 2002	A1
20020173875	Wallace et al.	Nov 2002	A1
20020188467	Eke	Dec 2002	A1
20020198473	Kumar et al.	Dec 2002	A1
20020198513	Lebel et al.	Dec 2002	A1
20020198624	Greenwald	Dec 2002	A1
20030006878	Chung	Jan 2003	A1
20030023177	Bardy	Jan 2003	A1
20030033532	Marks	Feb 2003	A1
20030036783	Bauhahn et al.	Feb 2003	A1
20030046114	Davies et al.	Mar 2003	A1
20030046280	Rotter et al.	Mar 2003	A1
20030046439	Manke et al.	Mar 2003	A1
20030050621	Lebel et al.	Mar 2003	A1
20030050731	Rosenblum	Mar 2003	A1
20030052787	Zerhusen	Mar 2003	A1
20030060753	Starkweather et al.	Mar 2003	A1
20030060754	Reilly	Mar 2003	A1
20030060765	Campbell et al.	Mar 2003	A1
20030060768	Kiyatake	Mar 2003	A1
20030060926	Yuyama et al.	Mar 2003	A1
20030065287	Spohn et al.	Apr 2003	A1
20030076736	Buker et al.	Apr 2003	A1
20030078534	Hochman et al.	Apr 2003	A1
20030079746	Hickle	May 2003	A1
20030083901	Bosch et al.	May 2003	A1
20030088238	Poulsen et al.	May 2003	A1
20030097092	Flaherty	May 2003	A1
20030114836	Estes et al.	Jun 2003	A1
20030117580	Franz et al.	Jun 2003	A1
20030125609	Becker	Jul 2003	A1
20030125611	Bardy	Jul 2003	A1
20030139701	White et al.	Jul 2003	A1
20030144878	Wilkes et al.	Jul 2003	A1
20030149599	Goodall et al.	Aug 2003	A1
20030154108	Fletcher-Haynes et al.	Aug 2003	A1
20030158508	DiGianfilippo	Aug 2003	A1
20030158755	Neuman	Aug 2003	A1
20030160683	Blomquist	Aug 2003	A1
20030163088	Blomquist	Aug 2003	A1
20030163223	Blomquist	Aug 2003	A1
20030163789	Blomquist	Aug 2003	A1
20030167035	Flaherty et al.	Sep 2003	A1
20030176933	Lebel et al.	Sep 2003	A1
20030179287	Kozic et al.	Sep 2003	A1
20030181851	Mann et al.	Sep 2003	A1
20030182164	Blomquist	Sep 2003	A1
20030195397	Bardy	Oct 2003	A1
20030200117	Manetta et al.	Oct 2003	A1
20030201697	Richardson	Oct 2003	A1
20030212379	Bylund et al.	Nov 2003	A1
20030225596	Richardson et al.	Dec 2003	A1
20030225728	Moura	Dec 2003	A1
20030231803	Huang	Dec 2003	A1
20040002874	Shaffer et al.	Jan 2004	A1
20040017475	Akers et al.	Jan 2004	A1
20040019607	Moubayed et al.	Jan 2004	A1
20040115132	Brown	Jan 2004	A1
20040039260	Bardy	Feb 2004	A1
20040039264	Bardy	Feb 2004	A1
20040051368	Caputo et al.	Mar 2004	A1
20040055611	Penny et al.	Mar 2004	A1
20040064343	Korpman et al.	Apr 2004	A1
20040073329	Engleson	Apr 2004	A1
20040088187	Chudy et al.	May 2004	A1
20040088374	Webb et al.	May 2004	A1
20040111293	Firanek et al.	Jun 2004	A1
20040116862	Ray	Jun 2004	A1
20040117215	Marchosky	Jun 2004	A1
20040128162	Schlotterbeck et al.	Jul 2004	A1
20040129616	Mori et al.	Jul 2004	A1
20040148195	Kalies	Jul 2004	A1
20040158193	Bui et al.	Aug 2004	A1
20040172283	Vanderveen et al.	Sep 2004	A1
20040172289	Kozic et al.	Sep 2004	A1
20040172300	Mihai et al.	Sep 2004	A1
20040193328	Zaitsu et al.	Sep 2004	A1
20040193453	Butterfield et al.	Sep 2004	A1
20040204673	Flaherty	Oct 2004	A1
20040204954	Lacko	Oct 2004	A1
20040215490	Duchon et al.	Oct 2004	A1
20040220829	Baharav et al.	Nov 2004	A1
20040225528	Brock	Nov 2004	A1
20040235446	Flaherty et al.	Nov 2004	A1
20040236630	Kost et al.	Nov 2004	A1
20040248295	Katsuhiko et al.	Dec 2004	A1
20040260233	Garibotto et al.	Dec 2004	A1
20040260577	Dahlin et al.	Dec 2004	A1
20050001033	Cheong et al.	Jan 2005	A1
20050017864	Tsoukalis	Jan 2005	A1
20050033124	Kelly et al.	Feb 2005	A1
20050033773	Roberge et al.	Feb 2005	A1
20050038680	McMahon	Feb 2005	A1
20050039742	Hickle	Feb 2005	A1
20050043665	Vinci et al.	Feb 2005	A1
20050045548	Brugger et al.	Mar 2005	A1
20050054923	Pan	Mar 2005	A1
20050060372	DeBettencourt et al.	Mar 2005	A1
20050080651	Morrison et al.	Apr 2005	A1
20050187794	Kimak	Aug 2005	A1
20050209737	Kircher	Sep 2005	A1
20050228238	Monitzer	Oct 2005	A1
20050279419	Tribble et al.	Dec 2005	A1
20060084042	Weaver et al.	Apr 2006	A1
20060124656	Popovic, Jr.	Jun 2006	A1
20060136095	Rob et al.	Jun 2006	A1
20060149416	Mohapatra et al.	Jul 2006	A1
20060161294	DiMaggio	Jul 2006	A1
20060173714	Grotzinger, Jr.	Aug 2006	A1
20060178578	Tribble et al.	Aug 2006	A1
20060181391	McNeill et al.	Aug 2006	A1
20060235881	Masarie et al.	Oct 2006	A1
20070043767	Osborne et al.	Feb 2007	A1
20070047980	Limer et al.	Mar 2007	A1
20070088568	Goodall et al.	Apr 2007	A1
20070110305	Corcoran et al.	May 2007	A1
20070125442	Tribble et al.	Jun 2007	A1
20070168228	Lawless	Jul 2007	A1
20070179806	Knowlton et al.	Aug 2007	A1
20070189597	Limer et al.	Aug 2007	A1
20070192139	Cookson et al.	Aug 2007	A1
20070216998	Sander	Sep 2007	A1
20070239482	Finn et al.	Oct 2007	A1
20070239997	Qu et al.	Oct 2007	A1
20080046292	Myers et al.	Feb 2008	A1
20080056556	Eller et al.	Mar 2008	A1
20080059228	Bossi et al.	Mar 2008	A1
20080091467	Moncrief et al.	Apr 2008	A1
20080119958	Bear et al.	May 2008	A1
20080125897	DiGianfilippo et al.	May 2008	A1
20080147554	Stevens et al.	Jun 2008	A1
20080195246	Tribble et al.	Aug 2008	A1
20080306926	Friedlander et al.	Dec 2008	A1
20090024414	Mansour et al.	Jan 2009	A1
20090080408	Natoli et al.	Mar 2009	A1
20090097368	Vlutters et al.	Apr 2009	A1
20090138340	Borr et al.	May 2009	A1
20090188937	Kim	Jul 2009	A1
20090205877	Claypool	Aug 2009	A1
20090210252	Silver	Aug 2009	A1
20090235194	Arndt et al.	Sep 2009	A1
20090258331	Do et al.	Oct 2009	A1
20090285762	Flower	Nov 2009	A1
20090313044	Haque et al.	Dec 2009	A1
20090318561	Davis	Dec 2009	A1
20090323170	Lin	Dec 2009	A1
20090324032	Chen	Dec 2009	A1
20100017031	Rob et al.	Jan 2010	A1
20100091281	Suzuki	Apr 2010	A1
20100094653	Tribble et al.	Apr 2010	A1
20100128165	Newcomb et al.	May 2010	A1
20100157293	Rzasa et al.	Jun 2010	A9
20100179169	Davis	Jul 2010	A1
20100185456	Kansal	Jul 2010	A1
20100241270	Eliuk et al.	Sep 2010	A1
20110119088	Gunn	May 2011	A1
20110191121	Fioravanti	Aug 2011	A1
20110202366	Akers et al.	Aug 2011	A1
20110208350	Eliuk et al.	Aug 2011	A1
20110257991	Shukla	Oct 2011	A1
20110267465	Alexander et al.	Nov 2011	A1
20120097290	Mikhaeil	Apr 2012	A1
20120200596	Gotou et al.	Aug 2012	A1
20120211565	Colavito et al.	Aug 2012	A1
20120303388	Vishnubhalta et al.	Nov 2012	A1
20120323602	Ryan et al.	Dec 2012	A1
20130079581	Agamaite et al.	Mar 2013	A1
20130090947	Nockley	Apr 2013	A1
20130197445	Schabbach et al.	Aug 2013	A1
20130262138	Jaskela et al.	Oct 2013	A1
20130279774	Helgason et al.	Oct 2013	A1
20130304510	Chan et al.	Nov 2013	A1
20130314535	Yuyama et al.	Nov 2013	A1
20130342676	Amano	Dec 2013	A1
20140022569	Matsui et al.	Jan 2014	A1
20140114687	Frank	Apr 2014	A1
20140156064	Crawford et al.	Jun 2014	A1
20140156294	Tribble et al.	Jun 2014	A1
20140214199	Utech et al.	Jul 2014	A1
20140214436	Utech et al.	Jul 2014	A1
20140278448	Sadeghi	Sep 2014	A1
20140350950	Jaskela et al.	Nov 2014	A1
20150205932	Tribble	Jul 2015	A1
20150227719	Ranalletta	Aug 2015	A1
20150272320	Ranalletta et al.	Oct 2015	A1
20150278477	Tribble	Oct 2015	A1
20150286799	Padmani	Oct 2015	A1
20160072985	Sandmann et al.	Mar 2016	A1
20160092638	Padmani	Mar 2016	A1
20160092639	Padmani	Mar 2016	A1
20160140315	Diaz et al.	May 2016	A1
20160210437	Padmani	Jul 2016	A1
20160371462	Wallen	Dec 2016	A1
20170372034	Tribble	Dec 2017	A1

Foreign Referenced Citations (113)

Number	Date	Country
1516257	May 1999	CN
2440518	Aug 2001	CN
1131076	Dec 2003	CN
0237588	Sep 1987	EP
0462466	Dec 1991	EP
0505627	Sep 1992	EP
0522527	Jan 1993	EP
0439355	Sep 1994	EP
0844581	May 1998	EP
0960627	Dec 1999	EP
0970655	Jan 2000	EP
1072994	Feb 2001	EP
1107158	Jun 2001	EP
1097671	Feb 2003	EP
1501037	Jan 2005	EP
994977	Jun 1965	GB
2210713	Feb 1987	GB
2279784	Jan 1995	GB
2285135	Jun 1995	GB
2379037	Feb 2003	GB
53137644	Dec 1978	JP
61066950	Apr 1986	JP
63068133	Mar 1988	JP
2111375	Apr 1990	JP
3423055	Jan 1994	JP
6086813	Mar 1994	JP
06327636	Nov 1994	JP
07204253	Aug 1995	JP
08315040	Nov 1996	JP
8315040	Nov 1996	JP
104585	Jan 1998	JP
10014890	Jan 1998	JP
10079770	Mar 1998	JP
2000036032	Feb 2000	JP
03055131	Apr 2000	JP
20000270376	Sep 2000	JP
2002011095	Jan 2002	JP
2002092181	Mar 2002	JP
2002099619	Apr 2002	JP
2002520718	Jul 2002	JP
2003022322	Jan 2003	JP
2003062043	Mar 2003	JP
2004078970	Mar 2004	JP
2004280327	Oct 2004	JP
2004326436	Nov 2004	JP
2004340770	Dec 2004	JP
2005252710	Sep 2005	JP
2006033291	Feb 2006	JP
2006195526	Jul 2006	JP
2006195526	Jul 2006	JP
2006334062	Dec 2006	JP
2007115089	May 2007	JP
2007190395	Aug 2007	JP
2007198934	Aug 2007	JP
2008139201	Jun 2008	JP
4276654	Jun 2009	JP
2009265827	Nov 2009	JP
2010056619	Mar 2010	JP
2010170504	Aug 2010	JP
2010533927	Oct 2010	JP
2011151430	Aug 2011	JP
2012078265	Apr 2012	JP
5342197	Nov 2013	JP
5747150	Jul 2015	JP
6086813	Mar 2017	JP
20000036642	Jul 2000	KR
1020000036642	Jul 2000	KR
20010094703	Nov 2001	KR
1020010094703	Nov 2001	KR
20050054379	Dec 2003	KR
20110115927	Oct 2011	KR
1020110115927	Oct 2011	KR
20130001500	Jan 2013	KR
WO8400493	Feb 1984	WO
WO9524010	Sep 1995	WO
WO9634291	Oct 1996	WO
WO9741525	Nov 1997	WO
WO9814275	Apr 1998	WO
WO9815092	Apr 1998	WO
WO9824358	Jun 1998	WO
WO9833433	Aug 1998	WO
WO9859487	Dec 1998	WO
WO9904043	Jan 1999	WO
WO9910029	Mar 1999	WO
WO9942933	Aug 1999	WO
WO9944162	Sep 1999	WO
WO9959472	Nov 1999	WO
WO0013588	Mar 2000	WO
WO0029983	May 2000	WO
WO0043941	Jul 2000	WO
WO0052437	Sep 2000	WO
WO0052626	Sep 2000	WO
WO0057339	Sep 2000	WO
WO0060449	Oct 2000	WO
WO0069331	Nov 2000	WO
WO0072181	Nov 2000	WO
WO0078374	Dec 2000	WO
WO0101305	Jan 2001	WO
WO0102979	Jan 2001	WO
WO0106468	Jan 2001	WO
WO0145774	Jun 2001	WO
WO0217777	Jul 2002	WO
WO02091276	Nov 2002	WO
WO03025826	Mar 2003	WO
WO03094073	Nov 2003	WO
WO2004070557	Aug 2004	WO
WO2004070994	Aug 2004	WO
2006060572	Jun 2006	WO
2014164875	Sep 2014	WO
2014164875	Sep 2014	WO
2014164875	Oct 2014	WO
2014164875	Oct 2014	WO
20140164875	Oct 2014	WO

Non-Patent Literature Citations (198)

Entry
Paxton, Anne. “Finally, microbiology labs getting a lift from IT.” Cap Today. May 2012. http://www.captodayonline.com/Archives/0512/0512f_finally.html (Year: 2012).
Japanese Office Action and English translation for related Japanese Application No. 2017-546118; action dated Sep. 18, 2018; (14 pages).
Written Opinion issued by the Singapore Patent Office for related Singapore Patent Application No. 11201707114X; opinion dated Mar. 26, 2018; (8 pages).
Texas Administrative Code, Title 22, Part 15, Ch 291, Rules 20, 36, and 71-74. Feb. 10, 2004.
Peterson, Charles D. and Anderson, Jr., Howard C.; “The North Dakota Telepharmacy Project: Restoring and Retaining Pharmacy Services in Rural Communities” Feb. 1, 2004.
Phillips, Jon, Associate Director of Telemedicine; “Telepharmacy at Texas Tech,” presented Apr. 30, 2003, published at http://www.ttuhsc.edu/telemedicine/publication.htm at least by Jun. 22, 2003 Jun. 22, 2003.
European Search Report for related European Application No. 16759518.0; action dated Sep. 25, 2018; (7 pages).
AHRQ Health Information Technology Program—Update Jun. 2005 Fact Sheet,, http://www.ahrq.gov/research/findings/factsheets/it/hitfact/index.html—3 pages.
Albert A. Cook, “An integrated nursing-pharmacy approach to a computerized medication dispensing/administration system,” Hospital Pharmacy, May 1985, pp. 321-325, vol. 20, JB Lippincott Company, Philadelphia, PA.
Allan T. Pryor, “Current State of Computer-based Patient Record Systems,” Aspects of the Computer-based Patient Record, 1992, pp. 67-82, Springer-Verlag, New York, NY.
Anderson, Howard “A Narrative on the History of the Development of Telepharmacy in North Dakota from the Board of Pharmacy's Perspective Recorded by Excerpts from Board Minutes”, Feb. 2006.
Angaran, “Telemedicine and telepharmacy: Current status and future implications”, Am J Health-Syst Pharm, vol. 56, Jul. 15, 1999, pp. 1404-1405.
Ann Slone Endo, “Using Computers in Newborn Intensive Care Settings,” American Journal of Nursing, Jul. 1981, pp. 1336-1337.
Anonymous, “Chains covet customized pharmacy integration” Drug Store New, Aug. 18, 2003, vol. 25, No. 10—p. 73.
Automated Dispensing Technologies: Directory of Vendors, http://pharmacyautomation.com/vendors.html, Jun. 5, 2003—3 pages.
Auto Syringe® AS40A Infusion Pump Technical Manual, 1995, 89 pages, Baxter Healthcare Corporation, Deerfield, IL.
Auto Syringe® AS40A: Model AS40A Infusion Pump Operation Manual, undated, 78 pages, Baxter Healthcare Corporation, Deerfield, IL.
Baxa Corporation, DoseEdge The Leading Edge in Dose Management, Brochure, published copyright date 2010—5 pages.
Baxa Corporation, Product Catalog 2010-2011, published at least by Sep. 15, 2012, https://web.archive.org/web/20120915210739http://www.baxa.com/resources/docs/BaxaCatalog.pdf (52 pages).
Bell Atlantic Healthcare Systems, Inc., court exhibit, StatLan Functions and Features, Specification, release 3.5, dated Nov. 12, 1992, 49 pages.
Ben Schneiderman, “Designing the User Interface: Strategies for Effective Human-Computer Interaction,” 2d Ed., 1992, Chapter 5: Direct Manipulation (56 pages), Addison-Wesley Publishing Company.
“Block Medical: Growing with Home Infusion Therapy,” taken from Invivo, the Business and Medicine Report, Apr. 1991, pp. 7-9.
Bynum et al., “The Effect of Telepharmacy Counseling on Metered-Dose Inhaler Technique among Adolescents with Asthma in Rural Arkansas”, Telemedicine Journal and e-health, vol. 7, No. 3, 2001, Mary AnnLiebert, Inc., pp. 207-218.
Cabral, Jr. et al., “Multmedia Systems for Telemedicine Systems for Telemedicine and Their Communications Requirements,” IEEE Communications Magazine Jul. 1996, pp. 20-27.
Cardinal Health Introduces Rxe-source(SM) to Address Pharmacist Labor Shortage and Medication Safety Challenges at Hospitals. PR Newswire, Feb. 25, 2003—5 pages.
Casey, Michelle M. et al., “Pharmacist Staffing and the Use of Technology in Small Rural Hospitals: Implications for Medication Safety” Upper Midwest Rural Health Research Center, Dec. 2005—51 pages.
Cato Reference Manual, Support for Trial Version (Abridged), Vienna, May 2004 Jun. 1, 2004.
Cato Reference Manual, Vienna, May 2005 May 1, 2005.
Charles Safran, M.D et al., “Computer-Based Support for Clinical Decision Making,” Clinical Computin, vol. 7, No. 5 (1990), pp. 319-322.
Clayton M. Curtis, “A Computer-based Patient Record Emerging from the Public Sector: The Decentralized Hospital Computer Program,” First Annual Nicholas E. Davies Award Proceedings of the CPR Recognition Symposium, 1995, pp. 75-132, Computer-based Patient Record Institute, Inc., Bethesda, MD.
Clement J. McDonald, M.D. et al., “The Three-Legged Stool: Regenstrief Institute for Health Care,” Third Annual Nicholas E. Davies Award Proceedings of the CPR Recognition Symposium, 1997, pp. 131-158, Computer-based Patient Record Institute, Inc., Bethesda, MD.
Clement J. McDonald, M.D. et al., The Regenstrief Medical Record System: 20 Years of Experience in Hospitals, Clinics, and Neighborhood Health Centers,: M.D. Computing, 1992 pp. 206-217, vol. 9, No. 4, Springer-Verlag, New York, NY.
Clifton, G. Dennis et al., “Provision of pharmacy services to underserved populations via remote dispensing and two-way videoconferencing” Am J Health-Syst Pharm, vol. 60, Dec. 15, 2003 oe pp. 2577-2582.
Dan Murphy, “Nuclear Pharmacy Primer”, Radiation Protection Management, vol. 20, No. 5 (2003), pp. 1-10.
Dan Scheraga; “Tech firms answer chain pharmacy's call for productivity,” Drug Store News; Dec. 15, 2003; 25, 17; ProQuest Research Library, p. 31-32.
Daniel Andresen et al., “Scalability Issues for High Performance Digital Libraries on the World Wide Web,” Proceedings of ADL '96, 1996, pp. 139-148, IEEE.
Daniel J. Nigrin et al., “Glucoweb: A Case Study of Secure, Remote Biomonitoring and Communication,” Proceedings of the 2000, 5 pages, American Medical Informatics Association, Bethesda, MD.
Darryl V. Wareham et al., “Combination Medication Cart and Computer Terminal in Decentralized Drug Distribution,” American Journal of Hospital Pharmacy, Jun. 1983, pp. 976-978, vol. 40, American Society of Hospital Pharmacists.
Dart, Luann, “Digital Doses” Rural Electric, Jan. 2005—pp. 28-31.
Deborah J. Mayhew, “Principles and Guidelines in Software user Interface Designs,” 1992, selected portions of Chapter 9, 17 pages, Prentice-Hall, Inc.
Defendants Initial Invalidity Contentions with Exhibits A and B dated Sep. 8, 2014; Civil Action No. 1:14-cv-00222.
Dennis D. Cote et al., “Robotic system for i.v. antineoplastic drug preparation: Description and preliminary evaluation under simulated conditions,” American Journal of Hospital Pharmacy, Nov. 1989, pp. 2286-2293, vol. 46, American Society of Hospital Pharmacists.
Donna Young; “Loan repayments help pharmacists provide care in medically underserved areas,” American Journal of Health—System Pharmacy; Nov. 1, 2003, pp. 2186-2188, vol. 60.
Environmental Scan of Pharmacy Technicians; M. MacInnis; Canadian Pharmacists Association; Sep. 2001.
Exhibit 1, Publications Manually Reviewed for the Search to U.S. Pat. No. 8,347,887 titled “System and Method for Remotely Supervising and Verifying Pharmacy Functions” As of Jun. 25, 2014.
Exhibit 1001 U.S. Pat. No. 8,374,887, Alexander issued Feb. 12, 2013.
Exhibit 1002 Patent File History U.S. Pat. No. 8,374,887.
Exhibit 1003, Declaration of Mr. Brian T. Hart from U.S. Pat. No. 8,374,887.
Exhibit 1004, Declaration of Wayne H. Grant from U.S. Pat. No. 8,374,887.
Exhibit 1005, 22 TAC §§291.20, 291.36, and 291.71-291.74 date issued Mar. 5, 2015 from U.S. Pat. No. 8,374,887.
Exhibit 1006 U.S. Pat. No. 6,711,460 Reese issued Mar. 23, 2004 from U.S. Pat. No. 8,374,887.
Exhibit 1009, Peterson et al., The North Dakota Telepharmacy Project: Restoring and Retaining Pharmacy Services in Rural Communities; the journal of Pharmacy Technology, vol. 20, No. 1, Jan./Feb. 2004—pp. 1-39 from U.S. Pat. No. 8,374,887.
Exhibit 1010, Declaration of Benjamin E. Weed from U.S. Pat. No. 8,374,887.
Exhibit 1011, Complaint—Alexander v. Baxter, (W.D.Texas 2014) filed Mar. 13, 2014 from U.S. Pat. No. 8,374,887.
Exhibit 1012, Charles F. Seifert et al., “The Training of a Telepharmacist: Addressing the Needs of Rural West Texas,” American Journal of Pharmaceutical Education, 2004; 68 (3) Article 60—pp. 1-9 from U.S. Pat. No. 8,374,887.
Exhibit 1013, Assignment Emily H. Alexander to Becton, Dickinson and Company; U.S. Appl. No. 13/747,231; Reel 034110/Frame 0789 from U.S. Pat. No. 8,374,887.
Exhibit 1014, Exhibit A—Corrected Parties' Claims Construction Terms, Proposed Construction and cites Civil, 1:14cv-00222-LY—pp. 1-7 from U.S. Pat. No. 8,374,887.
Exhibit 1015, Information about Telepharmacy presentation 42503 and Presentation Telepharmacy at Texas Tech; Jon Phillips—1-27 from U.S. Pat. No. 8,374,887.
Exhibit 1017, Declaration of Dr. Roger W. Anderson in Support of Becton, Dickinson & Company's Response to Baxter's Motion for Summary Judgment of Invalidity Based Upon 35 U.S.C. § 101 filed Jan. 15, 2015 from U.S. Pat. No. 8,374,887.
Exhibit 1018, Plaintiff's Claim Construction Brief, 1:14-cv-222-LY filed Oct. 17, 2014 from U.S. Pat. No. 8,374,887.
Exhibit 1019, Plaintiff's Reply Claim Construction Brief, 1:14-cv-222-LY filed Nov. 7, 2014 from U.S. Pat. No. 8,374,887.
Exhibit 1020, The United States Pharmacopeia—the Official Compendia of Standards; 2004 from U.S. Pat. No. 8,374,887.
Exhibit 1021, Curriculum Vitae of Brian T Hart from U.S. Pat. No. 8,374,887.
Exhibit 1022, Curriculum Vitae of Wayne H Grant—Expert oversight—Expert Witness-Litigation Support from U.S. Pat. No. 8,374,887.
Exhibit 1023, Charles D Peterson et al., “The North Dakota Telepharmacy Project: Restoring and Retaining Pharmacy Services in Rural Communities,” J Pharm Technol, 2004; vol. 20—pp. 028-039 from U.S. Pat. No. 8,374,887.
Exhibit 1025, Affidavit of Christopher Butler with attached Telemedicine Report Archive dated Mar. 4, 2015—6 pages from U.S. Pat. No. 8,374,887.
Exhibit 1026, Affidavit of Christopher Butler with attached presentation Telepharmacy at Text Tech—Jon Phillips dated Mar. 4, 2015—31 pages from U.S. Pat. No. 8,374,887.
Exhibit 1027, Order on Motion for Summary Judgment filed Aug. 3, 2015 from U.S. Pat. No. 8,374,887.
Exhibit 1028, Final Judgment filed Aug. 3, 2015 from U.S. Pat. No. 8,374,887.
Exhibit 1029 Charles Seifert from U.S. Pat. No. 8,374,887.
Exhibit 1030 Deposition of Charles Seifert Dec. 4, 2015 from U.S. Pat. No. 8,374,887.
Exhibit 1031 Deposition of Diane B. Ginsburg, PhD. Dec. 16, 2015 from U.S. Pat. No. 8,374,887.
Exhibit 1032 Texas Administrative Code, Title 22, Chapter 291, Subchapter A, Section 291.23 as in effect on Feb. 1, 2004 from U.S. Pat. No. 8,374,887.
Felkey, Bill G., “Integrating Technology at the Point of Care”, Insight, Jan. 2004—pp. 8-10.
Formula for Patient Safety; ScriptPro; Aug. 17, 2003.
Fred Puckett, “Medication-management component of a point-of-care information system,” Am. J. Health-Syst.Pharm., Jun. 15, 1995, pp. 1305-1309, vol. 52, American Society of Health-System Pharmacists, Inc.
“GE ImageQuant TL 7.0 Image Analysis Software” User Manual , May 2007, http://nba.uth.tmc.edu/Assets/pdf/other/typhoon-supporting-files/IQTL-UserManual.pdf, Uppsala, Sweden.
Gerald E. Meyer et al., “Use of bar codes in inpatient drug distribution,” Am. J. Hosp. Pharm., May 1991, pp. 953-966, vol. 48, American Society of Hospital Pharmacists, Inc.
Ghent, Natale, “Pharmacists go digital to fight shortage”, Pharmacy Practice 20.11 (Nov. 2004): 47—2 pages.
Gilad J. Kuperman, M.D. et al., “Innovations and research review: The impact of the HELP computer system on the LDS Hospital paper medical record,” Topics in Health Record Management, 1991, pp. 76-85, vol. 12, Issue 2, Aspen Publishers, Inc.
“Global Med Announces First Safetrace TX™ Sale,” Apr. 1, 1999, 2 pages.
Global Med Technologies, Inc. Introduces PeopleMed™.com, inc., A Chronic Disease Management Application Service Provider (ASP) Subsidiary, Jan. 11, 2000, 2 pages, Global med Technologies, Inc., Denver, CO.
Gretchen A. Barry et al., “Bar-code technology for documenting administration of large-volume intravenous solutions,” American Journal of Hospital Pharmacy, Feb. 1989, pp. 282-287, vol. 46, American Society of Hospital Pharmacists.
H. Paul Hammann et al., “A World Wide Web Accessible Multi-Species ECG Database,” 1997, pp. 7-12, ISA.
Halverson, Daniel R. IsoRx: TelePharmacy Software presentation—23 pages.
Henry J. Lowe et al., “WebReport: A World Wide Web Based Clinical Multimedia Reporting System,” 1996, pp. 314-318, AMIA, Inc.
“Hospitals battle errors with bar codes,” Mar. 24, 2004, 3 pages, MSNBC.
Howard L. Bleich et al., “Clinical Computing in a Teaching Hospital,” Use and Impact of Computers in Clinical Medicine, 1987, pp. 205-223 and selected pages, Springer-Verlag, New York, NY.
http://isorx.com/ Jan. 29, 2004.
http://www.scriptpro.com/products//sp-200/main.htm, Feb. 13, 2004, Product listing for SP 200® Robotic Prescription Dispensing System.
http://www.scriptpro.com/products/space/space200.htm, Feb. 10, 2004, Product listing for SP Automation Center 200TM (Space 200TM) Prescription Dispensing Automation Center.
Hughes, Shirley, “Bedside Terminals: Clinicom,” Clinical Computing, Jan./Feb. 1988, pp. 22-28, vol. 5, No. 1.
IPR Decision Paper No. 8 Entered Aug. 13, 2015 from U.S. Pat. No. 8,374,887.
IPR Final Written Decision Paper No. 29 Entered Jul. 11, 2016 from U.S. Pat. No. 8,374,887.
James Kazmer et al., “The Creation of Virtual Electronic Medical Record,” 1996, 17 pages.
Jennifer Langham; “Taking Automation to New Levels,” Insight, the QS/1 Magazine, Oct. 2002; pp. 2-5.
John Frady; “What's New in RxCare Plus 17.2,” Insight, the QS/1 Magazine, Apr. 2002; pp. 2-3, 14.
Jones, et al., “Use of a remote computerized system for study documentation in clinical trials” Drug Information Journal, Oct.-Dec. 1998, vol. 32, No. 4 oe pp. 1153-1163.
Karen E. Bradshaw et al., “Physician decision-making—Evaluation of data used in a computerized ICU,” International Journal of Clinical Monitoring and Computing, 1984, pp. 81-91, vol. 1, Martinus Nijhoff Publishers, Netherlands.
Kastango, Eric S. and Bradshaw, Brian D., “USP chapter 797: Establishing a practice standard for compounding sterile preparations in pharmacy” Am J Health-Syst Pharm., Sep. 15, 2004, vol. 61—pp. 1928-1938.
Kenneth N. Barker et al., “Effect of an automated bedside dispensing machine on medication errors,” American Journal of Hospital Pharmacy, Jul. 1984, pp. 1352-1358, vol. 41, No. 7, American Society of Hospital Pharmacists.
Keeys, Christopher A. et al., “Providing nighttime pharmaceutical services through telepharmacy” Am J Health-Syst Pharm, Apr. 15, 2002, vol. 59—pp. 716-721.
Khan, Shamima et al., “Is There a Successful Business Case for Telepharmacy?” Telemedicine and e-Health, vol. 14, No. 3, Apr. 2008, pp. 235-245.
Kimber, Michael B. et al., “Telepharmacy-Enabling Technology to Provide Quality Pharmacy Services in Rural and Remote Communities” Journal of Pharmacy Practice and Research, vol. 36, No. 2, 2006—128-133.
Kodak DirectView PACS—Rural Hospital Joins the Big Leagues PACS/Enterprise Information management (EIM) Solution—www.kodak.com/go/medical—4 pages.
Kosub, David, “Device allows pharmacy care in remote areas” Pharmacy Practice, vol. 20, No. 10, Oct. 2004—pp. 12-13.
Koutnik, Eileen, Assistnat Editor, Pharmacy Times, “The Pharmacy of Tomorrow” Pharmacy Times, Aug. 1, 2003—3 pages.
Larry B. Grandia, B.S.E. et al., “Building a computer-based Patient Record System in an Evolving Integrated Health System,” First Annual Nicholas E. Davies Award Proceedings of the CPR Recognition Symposium, 1995, pp. 19-55, Computer-based Patient Record Institute, Inc., Bethesda, MD.
Lefkowitz, Sheldon et al., “A Trial of the Use of Bar Code Technology to Restructure a Drug Distribution and Administration System,” 1991, pp. 239-242, Hospital Pharmacy, vol. 26.
LP, “ATM-STyle Drug Dispensers Taking Hold In Areas With Limited Pharmacist Services” Pharmacy Practice News, Jan. 2004, vol. 31, No. 1—4 pages.
“The Longitudinal Clinical Record: A View of the Patient,” taken from Proceedings of the 1994 Annual HIMSS Conference, Feb. 14, 1994, pp. 239-250, Healthcare Information and Management Systems Society, Chicago, Illinois, USA.
Lustig, Ahuva, “Medication error prevention by pharmacists—An Israeli solution” Pharmacy World & Science, 2000, vol. 22, No. 1—pp. 21-25.
Medicaid Memo—Department of Medical Assistance Services (Converting NDCs from 10-digits to 11-digits) May 31, 2007.
Medcin® Technical Overview, undated, 111 pages, Medicomp Systems.
Michael H. Mackin, “Impact of Technology on Environmental Therapeutic Device Design,” Medical Instrumentation, Feb. 1987, pp. 33-35, vol. 21, No. 1, Association for the Advancement of Medical Instrumentation.
Michelle M. Casey, M.S., Jill Klingner, R.N., M.S., and Ira Moscovice, Ph.D.; “Access to Rural Pharmacy Services In Minnesota, North Dakota, and South Dakota, ” Working Paper Series, Jul. 2001, #36.
Monane et al., “Improving Prescribing Patterson for the Elderly Through an Online Drug Utilization Review Intervention”, JAMA, Oct. 14, 1998, vol. 280, No. 14—pp. 1249-1252.
Morris, Aisha M., Schneider, Philip J., Pedersen, Craig A. and Mirtallo, Jay M. “National survey of quality assurance activities for pharmacy-compounded sterile preparations” Am J Health-Syst Pharm, Dec. 15, 2003, vol. 60—pp. 2567-2576.
Murray, Michael D. et al. “Effects of Computer-based Prescribing on Pharmacist Work Patterns” Journal of the American Medical Informatics Association, Nov./Dec. 1998, vol. 5, No. 6—pp. 546-553.
Napoli, M. et al., “Picture archiving and communication in radiology”, Rays. Jan.-Mar. 2003—PubMed-NCBI http://www.ncbi.nlm.m=nih.gov/pubmed/14509181—Abstract.
Nissen et al., Can telepharmacy provide pharmacy services in the bush, School of Pharmacy, University of Queensland, Brisbane, Australia, Journal of Telemedicine and Telecare 2003, vol. 9 (Suppl. 2): S2:39-41.
North Dakota Century Code Statute Law—State Board of Pharmacy—219 pages.
Parks, Liz, “Annual report of retail pharmacy: Using central-fill to maximize dispensing” Drug Store News, Aug. 20, 2001 vol. 24, No. 11—pp. 51, 75.
Parsons, et al., “Digital Media—Can I Change a Graphic's File Size?”, New Perspectives on Computer Concepts-Course Technology, 2011, Cengage Learning, Boston, MA.
Paul H. Perlstein et al., “Computer-Assisted Newborn Intensive Care,” Pediatrics, Apr. 1976, pp. 494-501, vol. 57, No. 4, American Academy of Pediatrics, Inc., Evanston, Illinois.
Paul H. Perlstein et al., “Future Directions for Device Design and Infant Management,” Medical Instrumentation, Feb. 1987, pp. 36-41, vol. 21, No. 1, Association for the Advancement of Medical Instrumentation.
PCA II Multi-Mode Cartridge Operator's Manual, Sep. 1995, approx. 40 pages, Baxter Healthcare Corporation, Deerfield, IL.
Pesce, James, “Bedside Terminals: Medtake,” Clinical Computing, Jan. /Feb. 1988, pp. 16-21, vol. 5, No. 1.
Peter Lord et al., MiniMed Technologies Programmable Implantable Infusion System, Annals New York Academy of Science, pp. 66-71, describing clinical trials from Nov. 1986.
Peterson et al., The North Dakota Telepharmacy Project Restoring and Retaining Pharmacy Services in Rural Communities—Presentation North Dakota State University, Fargo, North Dakota.
Petition for Inter Partes Review Baxter International Inc. v. Becton, Dickinson and Company for U.S. Pat. No. 8,374,887, pp. 1-69.
Pharmacy Automation Online Vendors Page; Internet Archive Wayback Machine; http://pharmacyautomation.com/vendors.html—3 pages.
Pharmacy Data Management (PDM) Technical Manual/Security Guide Version 1.0, Sep. 1997—55 pages.
Pharmacy education and practice out of sync? (Roundtable) Chain Drug Review, vol. 25, No. 6, Mar. 17, 2003, RX2 (6).
Prem S. Chopra, Virgil A. Thomason, and Dell M. Stinett; “Voice-Activated Networked Workstation for a Physically Disabled Physician,” 10-7803-2050-6/94 1994 IEEE, pp. 478-479.
Product literature, Baxter Healthcare Corporation, “Flo-Gard® 6201 Volumetric Infusion Pump,” 1992, 2 pages.
Product literature, Baxter Healthcare Corporation, “MultiPlex™ Series 100 Fluid Management System,” 1988, 2 pages.
Product literature, Baxter Healthcare Corporation, “MultiPlex™ Series 100 Fluid Management System,” undated, 2 pages.
Remote Dispensing Regulations, NABPLAW Sep. 2003.
Woodall, Sandra C., Remote Order Entry and Video Verification; Reducing After-Hours Medication Errors in a Rural Hospital; S. Woodall; Joint Commission on Accreditation of Healthcare Organizations; vol. 30; No. 8; Aug. 2004.
Rich Muller; “NRx QS/1's Premium Pharmacy Software,” Insight, the QS/1 Magazine, Jul. 2003; pp. 2-3, 12-15.
Rouse, et al., Academy of Managed Care Pharmacy et al., “White paper on pharmacy technicians 2002: Needed changes can no longer wait” Am J Health-Syst Pharm, Jan. 1, 2003, vol. 60—pp. 37-51.
Rule Section 291.36—Class A Pharmacies Compounding Sterile Pharmaceuticals—1 page.
Schrenker, Richard and Cooper, Todd, “Building the Foundation for Medical Device Plug-and-Play Interoperability”.
Seifert et al.; “The Training of a Telepharmacist: Addressing the Needs of Rural West Texas,” American Journal of Pharmaceutical Education 2004; 68 (3) Article 60. Jul. 16, 2004.
Standard Specification for Transferring Clinical Laboratory Data Messages Between Independent computer Systems, Annual Book of ASTM Standards, Mar. 25, 1988, pp. 1-16, E 1238-88, Global Engineering Documents, Philadelphia, PA.
Standard Specification for Transferring Clinical Observations Between Independent Computer Systems, Annual Book of ASTM Standards, June Mar. 1994, pp. 132-210, E 1238-94, Philadelphia, PA.
Standard Specification for Transferring Clinical Observations Between Independent Computer Systems, Aug. 10, 1997, 79 pages, ASTM E 1238-97, West Conshohocken, PA, United States.
Standard Specification for Transferring Information Between Clinical Instruments and Computer Systems, Annual Book of ASTM Standards, Jun. 1991, 15 pages, E 1394-91, Philadelphia, PA.
Suzanne Carter, RN, Ed.D. et al., “The Computer-based Patient Record: The Jacobi Medical Center Experience,” Second Annual Nicholas E. Davies Award Proceedings of the CPR Recognition Symposium, 1996, pp. 71-95, Computer-based Patient Record Institute, Inc., Bethesda, MD.
T. Allan Pryor et al., “help—A Total Hospital Information System,” Proceedings of the Fourth Annual Symposium on Computer Applications in Medical Care, Nov. 2-5, 1980, pp. 3-7, vol. 1, Institute for Electrical and Electronics Engineers, New York, NY.
T.E. Bozeman et al., “The Development and Implementation of a Computer-Based Patient Record in a Rural Integrated Health System,” Third Annual Nicholas E. David Award Proceedings of the CPR Recognition Symposium, 1997, pp. 101-130, Computer-based Patient Record Institute, Inc., Bethesda, MD.
“Telepharmacy project expands students' practice experience” Telemedicine Report, vol. 6, No. 1, Jan. 2004 oe 4 pages.
The World's First Fully Integrated Workflow Manager for I.V. Rooms, IntelliFlowRx Brochure, For Health Technologies Inc,. United States, May 2008.
Title 22. Examining Boards, 22 TAC Section 1.161; texinfo.library.unt.edu/Texasregister/html/2001/sep-14/PROPOSED/22.EXAMING BOARDS.html—Sep. 20, 2014, pp. 1-70.
Ukens, Carol, “Pharmacist shortage boosts telepharmacy” Drug Topoics, Jun. 3, 2002; 146, 11—p. 53.
Valeriy Nenov et al., “Remote Analysis of Physiological Data from Neurosurgical ICU Patients,” Journal of the American Medical Informatics Association, Sep./Oct. 1996, pp. 318-327, vol. 3, No. 5.
“Victor J. Perini et al., Comparison of automated medication-management systems,: Am. J. Hosp. Pharm., Aug. 1, 1994, pp. 1883-1891, vol. 51, American Society of Hospital Pharmacists, Inc.”.
Vincenzo Della Mae et al., “HTML generation and semantic markup for telepathology,” Computer Networks and ISDN Systems, 1996, pp. 1085-1094, vol. 28, Elsevier Science B.V.
Website information for Cartharsis Medical Technology Products, Dec. 9, 2001, 15 pages.
Website information for MedPoint™, Mar. 13, 2003, 20 pages, Bridge Medical, Solana Beach, CA.
William R. Dito et al., “Bar codes and the clinical laboratory: adaptation perspectives,” Clinical Laboratory Management Review, Jan./Feb. 1992, pp. 72-85, Clinical Laboratory Management Association, Inc.
Wills, Robert D., “Drug Images and Drug Imprints” Insight, Apr. 2001—p. 7.
Yvonne Mari Abdoo, “Designing a Patient Care Medication and Recording System that Uses Bar Code Technology,” Computers in Nursing, May/Jun. 1992, pp. 116-120, vol. 10, No. 3.
Jon Phillips, Telepharmacy at Texas Tech, PowerPoint, Jan. 26, 1997, https://web.archive.org/web/20040509162423/http:/www.ttuhsc.edu/telemedicine/Powerpoint/Telepharmacy%20presentation%2042503.ppt.
A.H. McMorris et al. “Are Process Control Rooms Obsolete?”, Control Engineering, pp. 42-47, Jul. 1971.
Standard Specification for Transferring Clinical Observations between Independent Computer Systems, Annual Book of ASTM Standards, Nov. 14, 1991, pp. 1-64, ASTM E 1238-91, Philadelphia, PA.
Standard Specification for Transferring Information Between Clinical Instruments and Computer Systems, Dec. 10, 1997; 15 pages, ASTM E 1394-97, West Conshohocken, PA, United States.
Web site information, Information Data Management, Inc.'s PCMS: Plasma Center Management System, Dec. 14, 2001, 11 pages.
Web site Information, Wyndgate Technologies' SafeTrace Tx™, undated, 15 pages.
Specification for Low-Level Protocol to Transfer Messages Between Clinical Laboratory Instruments and Computer Systems, Mar. 11, 1991; 7 pages, ASTM E 1381-91, Philadelphia, PA, United States.
Atherton, H.D., Dollberg, S., Donnelly, M.M., Perlstein, P. H. Roath, S.B., “Computerized Temperature Control of the Low-Birth-Weight Infant: A 20-Year Retrospective and Future Prospects,” Biomedical Instrumentation and Technology, Jul./Aug. 1994, pp. 302-309, vol. 28 No. 4.
Friesdorf, W., Grob-Alltag, F., Konichezky, S., Schwilk, B., Fattroth, A., Fett, P., “Lessons learned while building an integrated ICU workstation,” International Journal of Clinical Monitoring and Computing, 1994, pp. 89-97, vol. 11.
Gammon, K., Robinson, K., “Bedside Data System Aids Pharmacy,” Computers in Healthcare, Dec. 1988, pp. 35-37, vol. 9 No. 12.
Graseby 3100 Syringe Pump, Graseby Medical Ltd., A Cambridge Electronic Industries Company, England, 2 pages.
Kampmann, J., Lau, G., Kropp, St., Schwarzer, E., Hernandez Sande, C., “Connection of electronic medical devices in ICU according to the standard ‘MIB’,” International Journal of Clinical Monitoring and Computing, 1991, pp. 163-166, vol. 8.
Angaran, “Telemedicine and telepharmacy: Current status and future implications”, Am J Health-Syst Pharm, vol. 56, Jul. 15, 1999 (32 pages).
Carson, Ewart et al., “A Systems Methodology for the Development and Evaluation of a Telematic Home Haemodialysis Service,” Proceedings—19th International Conference—IEEE/EMBS Oct. 30-Nov. 2, 1997, Chicago, Illinois, pp. 907-910.
Singapore Written Opinion for related Singapore Application No. 11201707114X; action dated Mar. 5, 2019; (7 pages).
Japanese Office Action for related Japanese Application No. 2017-546118; action dated May 15, 2019; (4 pages).
European Office Action for related European Application No. 16759518.0; action dated Jan. 13, 2020; (7 pages).
Singapore Written Opinion for related Singapore Application No. 11201707114X; report dated May 5, 2020; (7 pages).
Extended European Search Report for related European Application No. 20210407.1; action dated Mar. 5, 2021; (11 pages).
Office Action in JP Application No. 2019-165983, dated Nov. 2, 2020 (4 pages).
Third Australian Examination report for related Australian application No. 2016226164; action dated Jul. 14, 2021; (5 pages).
Japanese Office Action and Denial of Entry of Amendment for related Japanese Application No. 2017-546118; actions dated Aug. 20, 2021; (6 pages).
Singapore Examination Report for related Singapore Application No. 11201707114X; report dated May 14, 2021; (9 pages).
Canadian Office Action for related Canadian Application No. 2,978,455; action dated Feb. 23, 2022; (5 pages).
Notice of Reasons for Refusal for Japanese Patent Application No. 2021204870 dated Feb. 28, 2023.
Becton, Dickinson and Company, Appellant v. Baxter Corporation Englewood, Appelle, Case No. 2020-1937 Appeal from the United States Patent and Trademark Office, Patent Trial and Appeal Board in No. IPR2019-00119—Decided: May 28, 2021—Document 30 filed May 28, 2021—21 pages.
Becton, Dickinson and Company, Petitioner, v. Baxter Corporation Englewood, Patent Owner, IPR2019-00212, U.S. Pat. No. 9,474,693 B2 Judgment Final Written Decision Determining All Challenged Claims Unpatentable 35 U.S.C. Section 318(a)—Denying Patent Owner's Revised Motion to Amend to Substitute Claims 20-38 35 U.S.C. Section 318(a)—Denying Petitioner's Motion to Exclude Evidence 37 C.F.R. Section 42.64—Paper No. 63 dated Apr. 29, 2020—102 pages.
Becton, Dickinson and Company, Petitioner, v. Baxter Corporation Englewood, Patent Owner, IPR2019-00119, U.S. Pat. No. 8,554,579 B2 Judgment Final Written Decision Determining No. Challenged Claims Unpatentable 35 U.S.C. Section 318(a)—Denying Petitioner's Motion to Exclude Evidence 37 C.F.R. Section 42.64, Paper 51 entered Apr. 29, 2020—63 pages.
Baxter Corporation Englewood, Appellant v. Becton, Dickinson and Company, Appellee, Case Nos. 2020-1806, 2020, 1808, Judgment Document 40 filed/entered Mar. 8, 2021 IPR2019-00120, IPR2019-00212 Baxter Corporation Englewood, Appellant v. Becton, Dickinson and Company, Appellee, Case Nod. 2020-1806, 2020, 1808, Mandate entered Mar. 8, 2021 Document 43, filed May 17, 2021 IPR2019-00120, IPR2019-00212.
Becton, Dickinson and Company, Petitioner, v. Baxter Corporation Englewood, Patent Owner, IPR2019-00120 U.S. Pat. No. 9,662,273 B2 Judgement Final Written Decision Determining Challenged Claims Unpatentable 35 U.S.C. Section 318 (a)—Denying Patent Owner's Revised Motion to Amend to Substitute Claims 22-42 35 U.S.C. Section 318(a) Denying Petitioner's Motion to Exclude Evidence 37 C.F.R. Section 42.64—Paper 63 dated Apr. 29, 2020, 90 pages.
Baxter Corporation Englewood, Appellant v. Becton, Dickinson and Company, Appellee, Case Nos. 2020-1806, 2020-1808 IPR2019-00120-IPR2019-0012, On Petition for Rehearing En Banc, Order—Document 42, filed May 10, 2021—2 pages.
Baxter Corporation Englewood, Appellant, v. Becton, Dickinson and Company, Appellee, Case Nos. 20-1806, 20-1808 Inter Partes Review Nos. IPR2019-00120, IPR2019-00121—Petition for Rehearing En Banc By Appellant Baxter Corporation Englewood—Document 41, filed Apr. 7, 2021—18 pages.
Inter Partes Review Certificate, Ranalletta et al. U.S. Pat. No. 9,662,273 K1 Certificate issued Dec. 30, 2021—2 pages.
Inter Partes Review Certificate, Tribble et al. U.S. Pat. No. 8,554,579 K1 Certificate issued May 12, 2022—2 pages.

Related Publications (1)

	Number	Date	Country
	20160260035 A1	Sep 2016	US

Provisional Applications (1)

	Number	Date	Country
	62127580	Mar 2015	US

Pharmacy workflow management with integrated alerts

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension