Patent Grant
11017352
Hospital pharmacies often manage groups of medical items in the form of pharmacy kits. A pharmacy kit can be used, for instance, to provide a group of items for a specific medical procedure, a particular physician, or a designated location of a hospital. As an example, a pharmacy kit can be used to aggregate and transport a collection of medicines for treating a patient with a specific type of stroke, heart condition, or other ailment.
A pharmacy kit (or “kit”) typically comprises a group of items specified by a template. For example, the template may specify that the kit requires three vials of adenosine, two containers of albuterol solution, two vials of amiodarone, and so on. The template may also specify ways in which individual items may be satisfied. For example, it may specify that the vials of adenosine may be satisfied by certain product brands. Pharmacy kits are usually stocked by a hospital pharmacy, but they may be stocked by another entity, such as an outsourced kit stocking company.
A kit is typically created by receiving specified items in a pharmacy, manually recording (e.g., on paper and/or electronic records) their product identifiers (e.g., National Drug Code (NDC) or Universal Product Code (UPC)), lot numbers, and expiration dates, and then loading the items into a container, such as a box, tray, or canister. During the kit's lifetime, it may be updated periodically to replace expired or consumed items. These updates are typically performed by inspecting the kit, comparing it to a corresponding template, modifying kit contents as required, and then manually recording any changes.
One challenge that may complicate the management of pharmacy kits is the rise of medication shortages across the country. From normal saline to propofol, any particular item can go into shortage almost inexplicably. As a result, hospitals are often forced to use different sizes or concentrations than what they normally stock or administer. This, unfortunately, may prevent accurate inventory monitoring and disrupt current processes of kit management.
Due to the above and other shortcomings of conventional approaches, there is a general need for improved techniques and technologies for managing pharmacy kits in the face of inventory shortages.
In one embodiment of the inventive concept, a method of managing a pharmacy kit comprises determining whether a kit stocking contingency has occurred with respect to a segment of the pharmacy kit, as a consequence of determining that the kit stocking contingency has not occurred, determining whether the segment has been satisfactorily stocked according to a first acceptance criterion, and as a consequence of determining that the kit stocking contingency has occurred, determining whether the segment has been satisfactorily stocked according to a second acceptance criterion different from the first acceptance criterion.
In another embodiment of the inventive concept, a method of managing a pharmacy kit using an electronic information processing system comprises defining, in the electronic information processing system, multiple rules for determining whether a segment of a pharmacy kit is satisfactorily stocked, selecting, by the electronic information processing system, at least one rule among the multiple rules according to a kit stocking contingency, and prompting, by the electronic information processing system, a user to stock the segment of the pharmacy kit according to the selected at least one rule.
In one embodiment of the inventive concept, a method of operating an electronic system comprises receiving an input identifying one or more pharmacy items, accessing stored information corresponding to the one or more pharmacy items based on the received input, determining a value of at least one contextual attribute of the one or more pharmacy items based on the accessed information, and selectively executing, blocking, or modifying a workflow to control distribution of the one or more pharmacy items according to the value of the at least one contextual attribute.
In another embodiment of the inventive concept, a system comprises an input capture unit configured to receive an input identifying one or more pharmacy items, a contextual attribute identification unit configured to access stored information corresponding to the one or more pharmacy items based on the received input, and further configured to determine a value of at least one contextual attribute of the one or more pharmacy items based on the accessed information, and a workflow control component configured to selectively execute, block, or modify a workflow to control distribution of the one or more pharmacy items according to the value of the at least one contextual attribute.
The drawings illustrate selected embodiments of the inventive concept. In the drawings, like reference labels denote like features.
Embodiments of the inventive concept are described below with reference to the accompanying drawings. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the inventive concept.
The described embodiments relate generally to the management of pharmacy kits. Certain details of pharmacy kits and related methods of management are described in U.S. patent application Ser. No. 13/554,342 filed Jul. 20, 2012, published as U.S. Patent Application Publication No. 2013/0035950, and U.S. patent application Ser. No. 14/126,419 filed Dec. 14, 2013, the respective disclosures of which are hereby incorporated by reference.
In certain embodiments, a kit management system uses RFID technology to label and track the contents of a kit. The use of RFID technology can allow a pharmacy to accurately and efficiently determine whether items in the kit are consumed, missing, expired, or near expiration. These determinations can be used thereafter to verify and update the kit contents, track item usage patterns, generate patient billing information based on item consumption, and so on.
In certain embodiments, a hospital pharmacy begins by tagging items upon bulk receipt in the hospital, or when a kit is stocked. Alternatively, items may arrive at a hospital pre-tagged. One way to tag the items is by scanning bar codes present on most items used in a kit, printing RFID tags based on the scanned bar codes, and then applying the RFID tags to the items. The scanned bar codes typically provide item information such as product identifiers (e.g., NDC or UPC), lot numbers, and expiration dates. This information can be associated with the RFID tags in a computer database to allow subsequent identification and processing by RFID technology. In some embodiments, the RFID tags can be generated automatically when scanning the bar codes, e.g., through the use of an RFID tag printer operatively connected to a bar code scanning machine. Alternatively, the RFID tags may be non-printed tags.
A kit is typically built by placing tagged items in a container such as a box, tray, or canister, and optionally labeling the kit with an RFID tag having information such as a kit identifier, kit type, intended user, or location, for example. These steps are generally performed by a pharmacist or other competent medical professional.
Once a kit is built, its contents are verified by placing it in an RFID reading station, which reads all RFID tags within its sensing range to identify the kit type and any items present. In some embodiments, the RFID reading station includes an enclosure such as a metal box to allow scanning of the kit exclusive of other RFID devices that may be in the surrounding environment. Alternatively, the RFID reading station may omit such an enclosure, for instance, by performing reading in an open area such as table, or using a handheld RFID reader. If the kit has an RFID tag, the kit type can be determined from the tag. Otherwise, it may be inferred from the items present. Items are typically identified by recognizing their RFID tags and then accessing stored information that maps the RFID tags to specific item information.
The stored information may reside on electronic equipment located at the RFID reader station or a remote location such as a remote server, a personal computer (PC), a mobile device, etc. In addition to basic kit and item information, the electronic equipment may also store metadata related to kit processes, such as who built or rebuilt a kit, what items were replaced if the kit was restocked, when the items were inserted in the kit, when verification and update procedures were last performed or will next be performed, and so on.
After the kit and item information are determined by the kit management system, they are analyzed automatically with reference to one or more templates. For instance, a kit template may be located based on the kit type, and then the identified items may be compared with the kit template to determine whether any items are missing or require replacement based on use or expiration. Additionally, the information processing system may analyze item information to determine whether any items are expired or will soon expire. The kit can then be updated based on these analyses.
Kit templates are typically stored in a database within or associated with the information processing system. However, they can alternatively be stored within a memory associated within the RFID reading station or RFID reader, or they can be stored in a separate system accessible by the information processing system.
In general, expiration of an item may occur based on a fixed or variable timeframe. For example, some items may expire at a fixed date indicated by the manufacturer, while other items may expire after a certain amount of time out of the refrigerator, e.g., time of removal+X days. Whether the timeframe is fixed or variable can be indicated in the template at a master level for a particular item, or at a segment level for a segment including the item.
The automatic processing provided by RFID technology and associated electronic equipment allows kit management to be performed with greater efficiency and accuracy compared with conventional approaches. For instance, in some embodiments, kit contents and expiration dates can be validated in 15 seconds or less. Moreover, kit deficiencies can be reported to a pharmacist automatically, allowing them to be addressed in an efficient manner. This reporting can be accomplished, for instance, by an automatically generated charge sheet showing kit contents and expirations.
Once a kit is built and verified, it is ready to be sealed and deployed for use in the hospital. When a kit is used, the seal is broken and items may be removed or consumed. Accordingly, the kit may be subsequently returned to the RFID reading station for additional verification, monitoring, and updates. These additional procedures can be used, for example, to determine whether any items in the kit are missing (e.g., due to use), and whether any items are erroneously present in the kit. This information can then be used to generate a report indicating the status and any necessary updates for the kit, or for other purposes such as patient billing or supply ordering. Once the relevant information is collected, the kit can be rebuilt using the automatically generated report, and then redeployed for another use.
Stored item and kit information can also be used to perform various forms of monitoring and/or reporting related to inventory management. For instance, stored kit information can be analyzed to identify patterns of item consumption. Moreover, the stored information can be inspected to determine the location of kits containing expired items. These and other forms of monitoring and/or reporting can be performed either automatically or in response to user input. For instance, they can be performed according to a predetermined schedule or in response to certain event triggers. Alternatively, a user may simply request monitoring or a report as needed. For example, a pharmacy manager may log in to view consumption logs, usage logs and current inventory to make more informed decisions on which inventory to keep and which kits may require special attention.
The kit management system typically further comprises a user interface and one or more software applications allowing a user to access information regarding the status of kits. As an example, a software application may be used to generate and print a kit charge sheet or charge sheet with the contents and expiration dates of the items and a kit. As other examples, a software application may be used to generate inventory reports showing where kits are dispatched within a hospital, an expiration report indicating dispatched items that are expired or near expiration, consumption and usage reports with traceability to departments, code types, or patients. The kit management system can also comprise or be integrated with a real-time tracking system to maintain current information regarding kit locations. The real-time tracking system typically comprises electronic components associated with the kits and configured to transmit information from the kits to the information processing system to identify the kits' respective locations. Such tracking systems can also be combined with kit management software in order to update the information used to generate inventory reports.
As indicated by the foregoing, a kit management system according to certain embodiments can provide many potential benefits compared with conventional technologies. For example, the kit management system can provide more efficient verification and recording of kit contents, and more accurate monitoring of kits, items, and expiration dates. In certain embodiments, the kit management system may also provide data analysis capabilities for purposes such as patient billing, inventory tracking, and so on.
In certain embodiments described below, a pharmacy kit is managed using multiple acceptance criteria for at least one pharmacy kit segment. The use of multiple acceptance criteria means that a designated segment may be deemed to be satisfactorily stocked with different types, quantities, or concentrations of pharmacy items under different circumstances. For example, if there is a shortage of a pharmacy item typically used to stock the designated segment, one or more different pharmacy items may be accepted as alternatives during the shortage.
The described embodiments may facilitate the use of multiple acceptance criteria by providing an information processing system that allows users to define different rules for determining automatically whether a segment is successfully stocked under different circumstances. Such a definition may include one or more types of items and be associated with one or more operators to suggest how multiple types of items interact with each other. For example, if a designated segment of a pharmacy kit requires three vials of propofol at 20 ml each (e.g., a “first acceptance criterion”), but there was a shortage for that package size, a user could define a rule allowing two 50 ml packages (e.g., a “second acceptance criterion”) or two 30 ml packages (e.g., a “third acceptance criterion”) as alternative ways of stocking the kit. As another example, an alternate concentration or drug may be used where an alternate size is not available. In that situation, rules may be set to determine which alternate drug or drug combinations would satisfy the requirements of the kit. For instance, if there is no calcium chloride, calcium gluconate may be substituted.
The described embodiments may also allow these rules to be ranked in order of preference to avoid ambiguity of items in a pharmacy kit matching multiple rules at the same time. A pharmacy manager may define preferred rules that cause a system to prompt a user to stock a pharmacy kit in a suggested way. Such rules may be stored in a way that allows a user to query an amount of time that a secondary or tertiary rule is in effect for a particular segment. This information can further be used to suggest optimizations for a pharmacy kit template.
The described embodiments may also be used to generate various types of reports related to the management of pharmacy kits using multiple acceptance criteria. For example, one type of report may identify the most commonly used medications for particular kit segments, enabling a manager greater visibility into medication ordering based on what actually makes it into circulation. Another type of report may provide a history of changes made to kit templates, informing a pharmacy of volatility of certain templates and medication stock. Such a report may be helpful for many management and operational activities such as ordering drug inventory, for instance. Yet another type of report may be an inventory list (or “charge sheet”) with specific billing codes. Such a report may show one of several billing codes for a segment depending on which acceptance criterion or stocking rule was used to stock the segment.
In certain embodiments, a system may also suggest a pharmacy kit configuration based on available inventory. For example, if a pharmacy kit allows for two different sizes of the same medication in a segment, and one size is on shortage, the system could guide a user to increase the medication in the segment based on the size that is not on shortage.
These and other embodiments may provide pharmacy managers with greater flexibly to handle situations related to shortages of pharmacy items, which may in turn increase efficiency in a hospital pharmacy. They may also increase safety by making kit processing more robust in the face of periodic variances in pharmaceutical inventory.
Referring to
RFID reading station 110 comprises an RFID reader configured to read RFID tags located on kit 105. During a typical read operation, the RFD reader interrogates RFID tags associated with respective items in kit 105, and it also interrogates any RFID tag associated with kit 105. As a consequence of the interrogation, the RFID reader receives information identifying each tag, and it conveys the information to information processing system 115. Based on the tag information, information processing system 115 identifies kit 105 and the items present. This can be accomplished, for instance, by relating the tag information to item or kit information stored in a computer database.
Once the kit and items are identified, information processing system 115 may process corresponding information in various ways, for example, by displaying it to a user, generating reports indicating missing or expired items, performing patient billing procedures based on any consumed items, or merely storing it for subsequent analysis. In certain embodiments, the kit and item information is managed as a list. For example, it can be stored and accessed in the form of a list in a computer database or other storage medium.
One of the most common ways of processing information captured from a kit is comparing the captured information with a template of the kit to determine whether the kit is satisfactorily stocked. The template of a kit defines items that are required to be placed in the kit. The template typically defines a plurality of item segments (or “segments”) to be included in the kit, where each item segment corresponds to a class or type of items and/or additional segments to be included in specific quantities. For instance, an item segment may define a specific class of medications, such as ibuprofen, acetaminophen, adenosine, or albuterol. Where a segment includes one or more additional segments, the template is considered to have multiple segment “levels”. In general, a template can have an arbitrary number of segment levels. An example of a template having multiple segment levels would be one containing a segment “analgesic”, with the item “morphine” and a sub-segment “ibuprofen” containing items “Advil” and “Generic”.
A segment of a kit is deemed to be satisfactorily stocked if the kit includes all of the items specified by at least one acceptance criterion associated with that segment. The term “acceptance criterion” here denotes a set of one or more rules that determines items that can be accepted (or required) as fulfilling the requirements for a particular segment under specified circumstances. For instance, one rule may define a “first acceptance criterion” that accepts a first type of medication to stock the segment under normal circumstances, and another rule may define a “second acceptance criterion” that accepts a second type of medication to be stocked in the segment where there is a shortage of the first type of medication. In other words, different rules may govern how a segment can be satisfactorily stocked under normal or shortage conditions. In general, the items that may be used to satisfactorily stock a segment may be, e.g., medications of different types (e.g., brands, formulations, etc.), concentrations, quantities, etc. These items are generally identifiable by distinct NDC or UPC identifiers. Circumstances that trigger the use of a different acceptance criteria are referred to as kit stocking contingencies. A shortage of items is one common example of a kit stocking contingency, but other contingencies are possible.
System 100 may occasionally aggregate last known status information for each kit that has been read, and it may then determine whether any action is required to resolve expiration issues, missing item issues, or extra item issues in all of the kits in a hospital or other facility. These actions can be performed, for example, on a periodic basis, in response to particular events, or in response to a user request.
System 100 may occasionally aggregate last known status information for each kit that has been read, and it may then determine whether any action is required to resolve expiration issues, missing item issues, or extra item issues in all of the kits in a hospital or other facility. These actions can be performed, for example, on a periodic basis, in response to particular events, or in response to a user request.
In addition to storing current or most recent information regarding kits, system 100 may also store a virtual history for each kit. Such a virtual history may include, for example, a record of each transaction involving the kit since the time it was tagged. Such transactions may include, for example, scans, database queries, updates such as restocking or removal of items, the occurrence of kit stocking contingencies and the use of alternative acceptance criteria when stocking segments, and so on. The virtual history may be maintained by information processing system 115, for example, and it may be output in the form of a report in response to a user request. In addition, the virtual history may be used to gather data or statistics that may be useful for planning future tasks such as kit updates, item restocking, and so on.
Kit 105 can be associated to a location or responsible person, such as a physician. This association can then be stored in system 100, and it can be used to quickly determine the location of kit 105 after deployment. The location of kit 105 can also be determined and/or updated by associating its RFID tag with a real time location system. In addition, kit 105 may be associated with a patient identifier or billing identifier and any missing items may be marked as being consumed by that billing or patient identifier. Such billing information may be stored either in system 100, in a separate system or in both system 100 and a separate system. System 100 may retrieve or update some or all of the billing information when a kit is read and items may or may not be consumed.
Where kit 105 contains prescription pharmaceuticals, the facility may be required to comply with requirements set by a state board of pharmacy. The precise regulations may vary from state to state, but can include requirements such as a mandatory visual inspection of kit 105 prior to deployment, or an item-by-item determination of each item type, lot number and expiration date. Other board of pharmacy requirements may include documentation to be included in kit 105 to verify completeness and accuracy of expiration data or a label on the outside of kit 105 to indicate the last check of the kit and the next expiring item in the kit.
In some embodiments, system 100 is configured to store relevant board of pharmacy requirements and verify that each step has been completed. System 100 can also be configured to compute steps automatically where allowed by regulations. Such steps may include, for example, printing documentation or labels, reading tags and verifying items, or requesting confirmation that a manual step has been completed. As these steps are completed, system 100 may record the name of the person who performed the steps. It may also confirm whether the person is authorized to perform the steps. In general, information regarding these and other steps can be recorded in system 100 using a log, database, or other storage format.
Although
In addition, the physical and functional implementation of system 100 can be distributed arbitrarily across multiple devices, systems, or network components. For example, in some embodiments, information processing system 115 may include or be integrated with wireless mobile devices in order to convey information remotely. One potential use of such a configuration would be to transmit kit notifications to remote users via push email or SMS text messaging, or subscription based data feeds. Such notifications could be used, for instance, to alert users that an updated kit is available, that a kit should be returned to the pharmacy, that a checked-out kit requires updates due to item expiration, and so on. Another potential reason to integrate information processing system 115 with remote components is to receive updates of kit templates and item master data. For example, some or all of a kit template or item master data may be received from an external system. The received item master data could indicate, for example, that an item has been recalled or changed in some material respect.
Referring to
The method further comprises, as a consequence of determining that the kit stocking contingency has not occurred (S205=No), determining whether the segment has been satisfactorily stocked according to a first acceptance criterion (S210). This can be accomplished, for instance, by evaluating kit related information captured by a system such as that illustrated in
The method still further comprises, as a consequence of determining that the kit stocking contingency has occurred (S205=Yes), determining whether the segment has been satisfactorily stocked according to a second or third acceptance criterion different from the first acceptance criterion (S215 or S220). In other words, where a kit stocking contingency arises, the method may use a different criterion to determine whether the segment is satisfactorily stocked. As illustrated by a box labeled “Preference?”, the second or third criterion may be selected according to a user preference (or hierarchical ranking), which may be defined within a particular implementation of the method.
The first through third acceptance criteria may specify, for instance, different types, sizes, or concentrations of items (e.g., medications) that can be used to stock the segment. The different types of items may also be associated with different operators (e.g., different authorized professionals), such that where a kit is being stocked by one type of operator, the first through third acceptance criteria may be satisfied by a first type of pharmacy item, and where the kit is being stocked by another type of operator, the first through third acceptance criteria may be satisfied by a second type of pharmacy item different from the first type of pharmacy item.
The method may further comprise determining whether an additional kit stocking contingency has occurred, and as a consequence of determining that the additional kit stocking contingency has occurred, determining whether the segment of the pharmacy kit has been satisfactorily stocked according to one or more additional acceptance criterion different from the first and acceptance criteria. In other words, the method may be extended to use not only secondary acceptance criteria, but also tertiary acceptance criteria, and so on. In general, where multiple acceptance criteria are used under different circumstances, those additional acceptance criterion can be ranked in order of user preference. Moreover, those rankings may differ according to the user who is performing a stocking or kit checking procedure.
The method may still further comprise operations allowing a user to define the rules for determining whether a segment is satisfactory stocked. For instance, the method may comprise receiving a user input to define one or more such rules for the first criterion or the second criterion.
Referring to
The method further comprises selecting, by the electronic information processing system, at least one rule among the multiple rules according to a kit stocking contingency (S310). This selection is typically performed automatically when there is a shortage or other kit stocking contingency. It may be initiated, for instance, in response to reception of an automated shortage notification, in response to user input indicating a shortage, or in response to an inventory level falling below a defined threshold. Additionally, the multiple rules may be ranked in order of user preference and selected according to the ranking.
The method still further comprises prompting, by the electronic information processing system, a user to stock the segment of the pharmacy kit according to the selected at least one rule. (S315). For instance, the system may display an interface instructing the user to stock the segment with a particular type, size, concentration, or quantity of a pharmacy item. The system may then allow the user to rescan the kit to confirm proper stocking of the segment.
The methods of
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Items 210 typically include medicines or other medical supplies that may be stocked by a pharmacy. As shown in
Due to the different types of packaging and materials, items 210 may be tagged with RFID tags having different shapes or types. As one example, RFID tags placed on metal bags may be subject to electromagnetic interference (EMI) from the metal. Accordingly, to prevent EMI, RFID tags connected to metal bags may have a foam backing or other form of insulation to create separation from the bags. Such tags may be referred to as metal-mount tags. As another example, RFID tags attached to small vials or bottles may potentially occlude label information on the vials. Accordingly, to prevent occlusion, RFID tags having a transparent adhesive portion may be attached to vials, bottles, or other types of packages. Such tags may be referred to as transparent tags.
Kit 105 is typically built by manually placing items 210 in container 205. This is typically accomplished by a pharmacist or other competent medical professional after items 210 have been labeled with RFID tags and stocked in the pharmacy. For example, a pharmacist may visit pharmacy shelves to collect items 210 and place them in container 205.
Referring to
For simplicity,
The template further defines a set of permissible items that can be used to satisfy each segment. The permissible items may correspond to different brands or other forms of each item corresponding to the segment. These items are generally identifiable by distinct NDC or UPC identifiers. As an example, a segment defined as a “bottle of ibuprofen” may be satisfied by a either a bottle of Advil or a bottle of generic ibuprofen. For simplicity,
The template still further defines a quantity of items to be included in kit 105 for each segment. For example, based on the template of
In general, the quantity can be zero or more. Where the quantity is greater than one, each item of a particular segment can be satisfied by any combination of the permissible items for that segment. For example, if there are three permissible items and the required quantity is three, the requirement may be satisfied by three of the same permissible item, one of each, etc. For instance, some kits may allow the stock of adenosine vials to be satisfied by different product brands. Alternatively, the template may require that multiple instances of the same item be selected, or that only certain combinations of items are permitted. Moreover, the template may include restrictions on the items that can be included in combination from among different segments.
Although the template determines the contents to be included in the kit under most circumstances, there are occasions where deviation from the template will be permitted. One of these occasions is a national shortage of one or more items to be included in the kit. When there is a national shortage of a particular item, certain substitutions or omissions of the item may be allowed. For example, if sodium bicarbonate is on national shortage, a kit may be permitted to include a suitable substitute for sodium bicarbonate, or it may be permitted to be deployed without sodium bicarbonate or any substitute.
The procedure for managing items under shortage may be defined in a variety of ways. For example, allowable substitutes for national shortage conditions may be embedded in the template itself and then triggered by information processing system 115 when a shortage arises. As an alternative example, information processing system 115 may simply ignore certain restrictions in a template when a shortage arises.
Referring to
The kit record is typically generated by RFID reading station 110 or information processing system 115 upon verifying or re-verifying the kit. It can then be compared to a corresponding template to determine whether the kit has missing or expired items, or it can be stored in information processing system 115 for subsequent comparisons, updates, or analyses.
Referring to
In a typical read operation, RFID reader 305 controls antenna 310 to interrogate any RFID tags within container 315. In response to the interrogation, the RFID tags communicate information to RFID reader 305 via antenna 310. The communicated information is typically associated with corresponding information stored in a database, such as NDC identifiers, lot numbers, and expiration dates for individual items, and a kit identifier for the kit as a whole. RFID reader 305 communicates the received information to information processing system 115 for storage and/or comparison with a template.
Referring to
In some embodiments, RFID reading station 110 is restricted to receiving only one kit at a time. This restriction may be imposed in a variety of ways, for instance, by configuring an enclosure to accommodate only one kit container or interrogating kit tags prior to scanning to ensure that no more than one kit tag is present. In certain alternative embodiments, RFID reading station 110 may be specifically configured to allow concurrent scanning of multiple kits. For example, two kits could be placed in RFID reading station 110, scanned concurrently, and then assigned to a common location or person, such as a particular cart, room, physician, etc. Moreover, such a common assignment may be recorded in information processing system 115 to allow joint analysis or tracking of more than one kit.
Referring to
Computer 405 comprises a browser 410 that receives kit information from the RFID reader via LAN 435 and communicates with server 420 through the internet 415. Server 420 stores templates 425, which typically include kit master templates and item master templates. Server 420 also stores records 430, which include information regarding individual kits and items.
Although server 420 is shown as a single unit in
The RFID printer can be used to print RFID tags automatically when a kit is being built or updated. For example, an RFID tag can be printed for a new item by scanning the item's bar code using a bar code scanner connected to computer 405, accessing server 420 to associate a particular RFID tag with the item, and then printing the RFID tag.
Referring to
Information processing system 115 updates stored records to reflect the scanning (520). In the update, a database in information processing system 115 is updated to reflect the scanned kit contents. For example, the database may be updated to reflect the presence of any new or replaced items, along with their expiration dates. The database may also be updated with other information, such as the name of the person who last modified the kit contents, a location to which the kit is to be deployed, a patient to be billed for consumption of kit items, and so on.
Based on the updated records, information processing system 115 performs a status check to verify the contents of the kit (525). The status check typically involves forming a list of items based on the transmitted information or updated records and comparing the list against a kit template. It may also involve comparing the updated kit information against information obtained in prior scans, or evaluating the kit information in light of certain business rules, such as billing protocols.
If the status check indicates a deficiency in the kit (525=“Deficiency”), such as missing or expired items, the kit contents are updated (530), and the method returns to step 515 where the kit is re-scanned. The update can be performed, for example, by replacing any expired items or inserting missing items. Otherwise, if the status check indicates no deficiency in the kit (525=“No Deficiency”), the kit is deployed for use in the hospital or other facility served by the pharmacy (535).
The updating of records and status check are typically performed any time the kit is scanned, as indicated by the flow of
Deployment of the kit may involve, for example, transporting it to a specific location of the hospital, checking it out to a particular individual, or merely storing it within the pharmacy. Following deployment, steps 515 through 535 may be repeated any number of times as needed. For example, the kit may be re-scanned and updated following each use or it may be periodically updated at specified times, such as daily, weekly, or whenever an expired item is noted in information processing system 115.
Referring to
Based on the item information, system 100 determines whether each item requires a first type of tag (illustrated as type “A”) or a second type of tag (illustrated as item type “B”) (615). This determination is typically performed based on the type of the item or its packaging. For example, items having metal packaging such as metal bag, etc., may require an RFID tag having a thicker insulation layer (e.g., foam) to prevent it from experiencing EMI from the metal. Other types of items, such as glass or plastic packages, may not require such an RFID tag. Although the method of
In creating the tags, system 100 may optionally perform automatic detection of whether it is attached to an RFID printer. If such an attachment is detected, it may control the RFID printer to print an RFID tag having a unique identifier for each item in the kit. Otherwise, a user may manually enter a unique tag identifier for each item into system 100. The manually entered identifiers can be determined, for example, based on the labeling of already printed RFID tags.
Next, system 100 associates the unique identifiers with the stored item information (630), allowing the item information to be retrieved subsequently when the RFID tags are scanned. Finally, the RFID tags are attached to corresponding items (635).
Referring to
Referring to
Referring to
Next, the server returns instructions on how to scan which could take the form of a link allowing control of the RFID reader (830). In the example using a link, the user clicks on the link to start a read operation, and the RFID reader then captures tag information from kit 105 and transmits it to the computer (835). Finally, the computer relays the tag information to the server for validation, storage, and/or other forms of processing (840).
The server typically stores kit-related information such as master templates, item master templates, and information regarding individual kits and items, as in the example of
Referring to
Referring to
Report 1001 also includes a portion 1015 indicating the date of a most recent scan, a portion 1020 showing additional details for the soon-to-expire items, and a portion 1025 showing additional details for missing items.
Report 1100 comprises a portion 1105 indicating the type of the kit and the total number of items in the kit. In this example, the kit comprises 26 total items. Report 1100 further comprises a portion 1010 indicating the number of extra and missing items in the kit, an entity to be billed for used items, and the number of expired or soon to expire items. In this example, there are two extra items, one expired item, and one soon-to-expire item. The entity to be billed is listed as KRE1981. The expired item is a box of Protopic, which is listed as having expired on Sep. 28, 2012.
Report 1100 further comprises a portion 1115 indicating the date of a most recent scan, a portion 1120 showing additional details for the expired items, a portion 1125 showing additional details for the soon-to-expire items, and a portion 1130 showing additional details for the extra items. Report 1100 still further comprises a portion 1135 indicating a current location of the kit and providing a “check out” button for assigning the kit to a specific location or person. In this example, the kit is currently assigned to the location “Central Pharmacy”.
Referring to
Interface 1300A further comprises a second area 1310A for displaying the report. According to the report in area 1310A, system 100 has information on two kits satisfying the specified options. In particular, a demo kit has a shortage of nasal spray, and it has a soon-to-expire container of Gentamicin Sulfate. A bandage kit has shortages of small, medium, and large bandages.
Referring to
Interface 1300B further comprises a second area 1310B for displaying the report. According to the report in area 1310B, a demo kit includes an item with the lot number specified in second area 1310A. Notably, in the example of
In addition to generating reports such as those illustrated in
System 100 may also automatically inventory items in pharmacy kits to determine where anything is missing, extra, expired, or near expired. This can reduce the chance of manual kit stocking errors or related medical errors in a hospital or other facility. System 100 may also automatically find items for recall in the hospital or emergency medical field kits.
As indicated by the foregoing, embodiments of the inventive concept provide various systems and methods for managing pharmacy kits using multiple acceptance criteria for pharmacy kit segments. These and other embodiments may potentially improve the efficiency and accuracy of kit stocking procedures, kit verification procedures, and related reporting procedures, among other things.
The foregoing is illustrative of embodiments and is not to be construed as limiting thereof. Although a few embodiments have been described, those skilled in the art will readily appreciate that many modifications are possible in the embodiments without materially departing from the scope of the inventive concept. Accordingly, all such modifications are intended to be included within the scope of the inventive concept as defined in the claims.
The described embodiments relate generally to management of pharmacy items based on contextual attributes associated with the items. For example, in certain embodiments, one or more pharmacy items are inspected to identify one or more of their contextual attributes, and then a workflow associated with the items is executed, modified, or blocked based on the contextual attributes. As will be apparent from the following description, pharmacy items, workflows, and workflow execution, modification, or blocking can take many alternative forms.
In certain embodiments, pharmacy items are processed in several different stages before being distributed to locations inside a hospital such as smaller satellite pharmacies, dispensing stations, or pre-prepared groups of medications in kits and trays. A system as described below may halt or alter the process of advancing a kit, tray or bulk group of medications in the event that contextual attributes of the item do not meet the requirements of a rules engine evaluating the item's appropriateness for processing. For example, suppose a box of 24 vials of dopamine had been entered into inventory and tagged with radio frequency identification (RFID) tags. Where a user attempts to include one of those vials into a tray destined for use in an operating room, the system may evaluate every item in that tray and, finding that one of the vials had not been verified, stop the process of completing the tray and require an authorized user to verify the item or remove it from the tray before tray completion would be allowed.
To accomplish this, each pharmacy item may have a series of contextual attributes assigned to it, and those contextual attributes may be evaluated by the rules engine, which can be any functional apparatus capable of evaluating conditions related to the contextual attributes. Where an item is received into inventory, the system assigns it a discrete identifier in a database of all labeled items at that facility. This identifier may be programmed into an RFID tag that can be affixed to the container for the item. A database entry for that identifier may include other distinguishing information about the item, including what pharmaceutical product it represents, what lot or batch of that product it came from, a serial number, when it expires, how long it can stay unrefrigerated, what physical location it is stored in, and whether or not it has been verified by a qualified user.
The process of changing an item's status to indicate that an acceptable verification process had been followed could be accomplished in various alternative ways. For example, a batch processing option in which entire boxes or trays of unverified medications could be received into inventory through the use of a RFID scanning station that reads the discrete identifier off of each tag affixed to a medication in the reader and allows for bulk updates of the status to be made is perhaps the easiest. However, other methods of accomplishing this could include using an optical scanner or typing in the unique item identifier in order to update single items requiring status updates. In some embodiments, a first user performs an initial scan to enter an item into inventory, resulting in a verification attribute of the item being set to a status indicating it has not been verified. Thereafter, a second user who is authorized to perform verification changes the verification attribute on the item to indicate that it has been verified.
Where the system is able to distinguish between received items and verified items, a pharmacy could use computerized reporting tools to investigate the amount of received, verified, deployed and used inventory they have recorded, and manage the process of accepting new items into inventory and deploying them out to satellite pharmacy locations, patient care areas, or medications kits and trays.
As used herein, the term “pharmacy item” (or simply “item”) refers to any type of item that is formally dispensed or distributed by way of a pharmacy. In a typical context, such items may include medications, medical instruments, and other materials used by medical professionals to treat patients. The more specific term “regulated pharmacy item” refers to a pharmacy item whose dispensing or distribution is governed by rules of inspection and verification, with such rules being promulgated by, e.g., a state pharmacy board or the hospital itself. In various alternative embodiments, pharmacy items may be processed individually or in groups, referred to as “pharmacy kits”. For instance, inspection and verification procedures may be applied to a kit as a whole, or to individual items independent of a kit. In this context, the term “pharmacy kit” or “kit” denotes a group of items specified by a template. Examples of pharmacy kits, as well as various properties and management techniques for kits, are disclosed in U.S. patent application Ser. No. 13/554,342.
As used herein, the term “contextual attribute” refers to information that has been expressly associated with a pharmacy item or collection of items through a handling process such as labeling, data entry, scanning, tracking, or updating, for example. Contextual attributes may include, for instance, a verification status, current and/or previous item handlers, current and/or previous location(s), associated items, previous workflow steps performed in relation to the item, and so on. The value of a contextual attribute may be determined according to human and/or machine interaction with an item or items. For example, a medical professional may identify and record a contextual attribute by manually entering it into a computer, or the contextual attribute may be identified and recorded by a machine that scans a tag or label on the item. Some ways to associate a contextual attribute with an item include, for instance, linking the attribute and item together in database, or recording the attribute information in a label affixed to the item.
As used herein, the term “workflow” denotes a predetermined sequence of steps that governs the dispensing or distribution of pharmacy items. In general, it may refer to processes performed by humans, electronic systems, and/or various other forms of available equipment. For example, a workflow may comprise a pharmacist scanning a pharmacy item for verification, followed by a computer displaying and/or printing information related to the verification, and subsequent dispatching of the pharmacy item to a destination within a hospital. Typically, the ongoing execution of a workflow is controlled by way of an electronic system, such as a computer network, which may display or record information necessary to perform various processes.
A workflow may be said to be “blocked” where predetermined steps of the workflow are prevented from being performed due to contingencies in the workflow. For instance, where the workflow includes steps for verifying an item and then dispatching the item contingent upon successful verification, the dispatching and any subsequent steps may be prevented or “blocked” upon failed verification. The blocking of a workflow may be accompanied by additional steps, such as displaying a warning screen indicating that a problem has occurred during verification and providing information to fix the problem. Similarly, a workflow may be said to be “modified” where steps are added to or removed from the workflow due to contingencies in the workflow. For instance, where the workflow determines a location of an item, it may add or remove steps depending on the location. A workflow is said to be “executed” where its predetermined or modified steps are performed. In various alternative embodiments, the modification of a workflow may take the form of displaying various screens to a user. For instance, modifying a workflow may involve displaying a first screen to a user if an item is determined to be located in the pharmacy, or displaying a second screen to the user if the item is determined to be located in another location of a hospital.
Certain portions of a workflow, such as verification, may require actions to be performed by an “authorized professional”. Such a professional may include, for instance, a pharmacist, a qualified technician, or some other person indicated by a relevant regulation. The regulation may include, for example, those having the force of law at a federal, state, or local level, or those stipulated by a medical facility's self imposed rules. In general, actions performed by an authorized professional may be accompanied by some form of logging to confirm such a professional's involvement. Such logging may comprise, for instance, signing a printed charge sheet or entering confirmation data for verified items.
Referring to
Input capture component 2305 typically comprises an RFID scanner or bar code scanner capable of capturing information from one or more pharmacy items. Such a device may operate automatically in response to the presence of one or more pharmacy items (e.g., by detecting and interrogating RFID tags), or it may operate in response to some form of user initiation, such as the pressing of a button, the handling of a bar code or RFID scanner, or the operation of a computer user interface. Input capture component 2305 may operate in batch mode to scan multiple items concurrently or in succession, or it may capture information for one item at a time. In addition, input capture component 2305 may comprise more than one device. For instance, it may comprise a collection of different input devices for capturing relevant information used to manage the pharmacy items.
During typical operation, a user presents one or more pharmacy items to input capture component 2305. Upon recognizing the presence of the one or more pharmacy items, input capture component 2305 receives input data identifying the one or more items and transmits the input data to contextual attribute analysis component 2310. Such input data can be, for instance, information encoded in a bar code label or RFID tag affixed to the one or more pharmacy items.
In addition to receiving the input data identifying the one or more pharmacy items, input capture component 2305 may also receive information used to update contextual attributes of the pharmacy items. For example, when a user scans an item, the user may also supply information indicating who performed the scanning, whether the item has been verified, and so on.
Contextual attribute analysis component 2310 accesses stored information corresponding to the one or more pharmacy items based on the received input data, and it determines a value of at least one contextual attribute of the one or more pharmacy items based on the accessed information. The stored information may be located in a database used by an institution to manage a collection of items. For instance, a hospital may use a central database to track pharmacy items throughout the hospital. Among other things, the contextual attribute may indicate whether labeling and contents of the one or more pharmacy items have been verified by one or more authorized pharmacy professionals, it may indicate a current or prior location of the one or more pharmacy items, or it may indicate a current or prior handler of the one or more pharmacy items. Additionally, where the one or more pharmacy items constitute a pharmacy kit, the at least one contextual attribute may correspond to the pharmacy kit as a whole, e.g., whether the kit has been verified, a location of the kit, etc.
Workflow control component 2315 selectively executes, blocks, or modifies a workflow to control distribution of the one or more pharmacy items according to the identified value of the at least one contextual attribute. Various examples of the selective execution, blocking, or modification are described below with reference to
Display component 2320 displays information related to the workflow. For example, it may display various screens indicating the values of contextual attributes, screens confirming or prompting inspection and verification of pharmacy items, screens providing warnings of failed verification, and so on. Display component 2320 may present screens for entering data related to verification or contextual attributes. Various examples of information to be displayed on display component 2320 are illustrated in
Referring to
The method further comprises accessing stored information corresponding to the one or more pharmacy items based on the received input (S2410), and determining a value of at least one contextual attribute of the one or more pharmacy items based on the accessed information (S2415). These steps may be performed, for instance, by accessing a database containing values of contextual attributes for a large collection of items that have been registered with a system or institution. It may also involve analysis of information encoded in a bar code or RFID tag.
Finally, the method comprises selectively executing, blocking, or modifying a workflow to control distribution of the one or more pharmacy items according to the value of the at least one contextual attribute (S2420). As one example of this step, if the at least one contextual attribute indicates that a drug is expired or recalled, the method may block a user from performing a subsequent step of a workflow and/or display a warning. As another example, if the at least one contextual attribute indicates that a drug has already been used on a patient, the method may display information indicating the presence of a new patient and it may therefore prevent a user administering the drug to the new patient. As yet another example, if the at least one contextual attribute indicates that a drug is considered to be a substitute for another drug or has “abnormal strength”, the method may allow a user to continue a workflow but may also display a warning indicating this is a change from normal procedure.
As still another example, if the at least one contextual attribute indicates that an item (e.g., a drug) has undergone secondary preparation within a pharmacy (e.g., mixing of a powder with a liquid or loading of a medication into a syringe), the method may allow a user to perform certain workflow functions that are only available on drugs with secondary preparation, or it may prevent the user from performing certain workflow functions that are available on drugs other than those with secondary preparation. In general, the term “secondary preparation” refers to any process that changes the state of an item as originally provided to a pharmacy into a different state to be used on a patient. In one example, suppose a drug and syringe have undergone secondary preparation by a process of loading the drug into the syringe. Under these circumstances, the method may inspect an item attribute (of the drug and/or the syringe) to determine that the drug is loaded into the syringe, and it may further inspect another item attribute to determine how long ago the drug was loaded into the syringe. If the syringe was prepared too long ago, the method may modify the workflow to prevent the syringe from being used on a patient. Still other examples of workflow variations corresponding to step S2420 are described below with reference to
Referring to
In the illustrated example, the scanning process is used to determine whether the items and/or kit have been verified by an authorized professional. This can be accomplished by comparing the captured information with previously stored information, such as one or more contextual attributes associated with the items and/or kit. Upon successful verification, the items and/or kit may be deployed to a location within a hospital or other facility. Upon failed verification, a warning is displayed on a screen to indicate the failure, and the user is advised that the distribution of the items cannot proceed (S2510). In other words, the workflow is blocked.
Following the warning, a pharmacist may visually review unverified items and labels among those that were previously scanned (S2515). This review process may be used to confirm that the items have the correct contents and labeling. The review process is deemed successful if the pharmacist is able to provide positive confirmation of the items as presented, or to fix any deficiencies that exist. In addition to inspecting the items themselves, the pharmacist may also compare the items with information stored in a computer system. For instance, the pharmacist may inspect a displayed list of recorded items and compare the list to the items actually presented.
Next, assuming a successful review process, the pharmacist provides formal verification that the items and/or kit have correct contents and labeling (S2520). This formal verification may involve, for instance, entering data in a computer system or signing papers. Typically, such verification will indicate the pharmacist's identity, as well as the circumstances of the verification, such as time, date, location, methodology, etc.
Following verification, the technician may re-scan and deploy the kit for use in the hospital or other facility (S2525). Because the kit has been verified at this point, the scanning does not produce an error or warning, and the workflow is not blocked. Finally, following use of the kit, it can be re-stocked by the technician (S2530). The restocking generally introduces unverified items into the kit, so it may result in a return to step S2505.
Referring to
Next, the pharmacist visually reviews the items and corresponding labels to confirm their accuracy (S2615). This step is similar to step S2515 of
When performing the re-scanning in step S2625, the pharmacist may provide input to a computer system to indicate that the re-scanned items have been formally verified for accuracy. Such input may be provided, for instance, through a user interface having a functional relationship with the scanning process. Additional inputs may be similarly provided to the computer system at various steps of the illustrated method to indicate other contextual attributes of the items being handled or otherwise processed. For instance, inputs may be provided to indicate who is handling the items, where the handling is being performed, and so on.
After the items have been verified by the two-step verification process, those items may be added to pharmacy stock or distributed within a hospital or other facility (S2630).
Referring to
The attribute values shown in
Referring to
Referring to
As indicated by the foregoing, pharmacy inventory management often requires multiple individuals reviewing and verifying an item is correctly tagged before it can be safely and accurately incorporated into the supply chain. The described embodiments provide systems and methods to guide users towards the appropriate tools to manage incompletely documented pharmaceutical products and to bar users from including medications that have not been verified as being accurately labeled from being deployed outside of the pharmacy where they could cause harm or waste. By using these and other embodiments, a hospital pharmacy may allow medications to be deployed with relative safety and accuracy throughout the hospital.
The foregoing is illustrative of various embodiments and is not to be construed as limiting the inventive concept. Although a few embodiments have been described, those skilled in the art will readily appreciate that many modifications are possible in the embodiments without materially departing from the novel teachings and advantages of the inventive concept. Accordingly, all such modifications are intended to be included within the scope of the inventive concept as defined in the claims.
This application is a continuation of U.S. patent application Ser. No. 14/472,410, filed Aug. 29, 2014, which is a continuation-in-part of U.S. patent application Ser. No. 13/554,342, filed Jul. 20, 2012, now issued as U.S. Pat. No. 8,990,099, each of which is hereby incorporated by reference. U.S. patent application Ser. No. 13/554,342 claims priority benefit to U.S. Provisional Application No. 61/514,231, filed Aug. 2, 2011. U.S. patent application Ser. No. 14/472,410 also claims priority to U.S. Provisional Application No. 62/021,927, filed on Jul. 8, 2014, the subject matter of which is hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4884827 | Kelley | Dec 1989 | A |
| 4961533 | Teller et al. | Oct 1990 | A |
| 5713485 | Liff et al. | Feb 1998 | A |
| 5930145 | Yuyama et al. | Jul 1999 | A |
| 5963134 | Bowers et al. | Oct 1999 | A |
| 5986662 | Argiro et al. | Nov 1999 | A |
| 6112502 | Frederick et al. | Sep 2000 | A |
| 6249299 | Tainer | Jun 2001 | B1 |
| 6275157 | Mays et al. | Aug 2001 | B1 |
| 6294999 | Yarin et al. | Sep 2001 | B1 |
| 6330351 | Yasunaga | Dec 2001 | B1 |
| 6574166 | Niemiec | Jun 2003 | B2 |
| 6632619 | Harrison et al. | Oct 2003 | B1 |
| 6771369 | Rzasa et al. | Aug 2004 | B2 |
| 6825864 | Botten et al. | Nov 2004 | B2 |
| 6847861 | Lunak et al. | Jan 2005 | B2 |
| 6851615 | Jones | Feb 2005 | B2 |
| 6861954 | Levin | Mar 2005 | B2 |
| 6877658 | Raistrick et al. | Apr 2005 | B2 |
| 6879876 | O'Dougherty et al. | Apr 2005 | B2 |
| 6900021 | Harrison et al. | May 2005 | B1 |
| 6933849 | Sawyer | Aug 2005 | B2 |
| 6935560 | Andreasson et al. | Aug 2005 | B2 |
| 6952681 | McQuade et al. | Oct 2005 | B2 |
| 6985870 | Martucci et al. | Jan 2006 | B2 |
| 6992574 | Aupperle et al. | Jan 2006 | B2 |
| 6994249 | Peterka et al. | Feb 2006 | B2 |
| 7036729 | Chung | May 2006 | B2 |
| 7061831 | De La Huerga | Jun 2006 | B2 |
| 7111780 | Broussard et al. | Sep 2006 | B2 |
| 7116343 | Botten et al. | Oct 2006 | B2 |
| 7118029 | Nycz et al. | Oct 2006 | B2 |
| 7140542 | Andreasson et al. | Nov 2006 | B2 |
| 7146247 | Kirsch et al. | Dec 2006 | B2 |
| 7151456 | Godfrey | Dec 2006 | B2 |
| 7158030 | Chung | Jan 2007 | B2 |
| 7165077 | Kalies | Jan 2007 | B2 |
| 7175081 | Andreasson et al. | Feb 2007 | B2 |
| 7177721 | Kirsch et al. | Feb 2007 | B2 |
| 7178729 | Shaffer et al. | Feb 2007 | B2 |
| 7182256 | Andreasson et al. | Feb 2007 | B2 |
| 7212100 | Terenna | May 2007 | B2 |
| 7212127 | Jacober et al. | May 2007 | B2 |
| 7227469 | Varner et al. | Jun 2007 | B2 |
| 7232066 | Andreasson et al. | Jun 2007 | B2 |
| 7253736 | Tethrake et al. | Aug 2007 | B2 |
| 7256699 | Tethrake et al. | Aug 2007 | B2 |
| 7263501 | Tirinato et al. | Aug 2007 | B2 |
| 7264323 | Tainer et al. | Sep 2007 | B2 |
| 7268684 | Tethrake et al. | Sep 2007 | B2 |
| 7275645 | Mallett et al. | Oct 2007 | B2 |
| 7299981 | Hickle et al. | Nov 2007 | B2 |
| 7316231 | Hickle | Jan 2008 | B2 |
| 7317393 | Maloney | Jan 2008 | B2 |
| 7318529 | Mallett et al. | Jan 2008 | B2 |
| 7339550 | Hayama et al. | Mar 2008 | B2 |
| 7341147 | Mallett et al. | Mar 2008 | B2 |
| 7348884 | Higham | Mar 2008 | B2 |
| 7354884 | Hada et al. | Apr 2008 | B2 |
| 7362228 | Nycz et al. | Apr 2008 | B2 |
| 7375737 | Botten et al. | May 2008 | B2 |
| 7394383 | Hager et al. | Jul 2008 | B2 |
| 7440818 | Handfield et al. | Oct 2008 | B2 |
| 7446747 | Youngblood et al. | Nov 2008 | B2 |
| 7454880 | Austin et al. | Nov 2008 | B1 |
| 7486188 | Van Alstyne | Feb 2009 | B2 |
| 7492257 | Tethrake et al. | Feb 2009 | B2 |
| 7492261 | Cambre et al. | Feb 2009 | B2 |
| 7504954 | Spaeder | Mar 2009 | B2 |
| 7518502 | Austin et al. | Apr 2009 | B2 |
| 7518516 | Azevedo et al. | Apr 2009 | B2 |
| 7551089 | Sawyer | Jun 2009 | B2 |
| 7559483 | Hickle et al. | Jul 2009 | B2 |
| 7564364 | Zweig | Jul 2009 | B2 |
| 7630791 | Nguyen et al. | Dec 2009 | B2 |
| 7639136 | Wass et al. | Dec 2009 | B1 |
| 7644016 | Nycz et al. | Jan 2010 | B2 |
| 7672872 | Shanton | Mar 2010 | B2 |
| 7706915 | Mohapatra et al. | Apr 2010 | B2 |
| 7706916 | Hilton | Apr 2010 | B2 |
| 7712670 | Sauerwein, Jr. et al. | May 2010 | B2 |
| 7715277 | De La Huerga | May 2010 | B2 |
| 7729597 | Wright et al. | Jun 2010 | B2 |
| 7734157 | Wright et al. | Jun 2010 | B2 |
| 7737858 | Matityaho | Jun 2010 | B2 |
| 7747477 | Louie et al. | Jun 2010 | B1 |
| 7752085 | Monroe | Jul 2010 | B2 |
| 7772964 | Tethrake et al. | Aug 2010 | B2 |
| 7775056 | Lowenstein | Aug 2010 | B2 |
| 7783163 | Wright et al. | Aug 2010 | B2 |
| 7783174 | Wright et al. | Aug 2010 | B2 |
| 7801422 | Wright et al. | Sep 2010 | B2 |
| 7815117 | Tuschel et al. | Oct 2010 | B2 |
| 7834765 | Sawyer | Nov 2010 | B2 |
| 7834766 | Sawyer | Nov 2010 | B2 |
| 7837093 | Leu et al. | Nov 2010 | B1 |
| 7837107 | Leu et al. | Nov 2010 | B1 |
| 7858841 | Krautkramer et al. | Dec 2010 | B2 |
| 7860730 | Goodall et al. | Dec 2010 | B1 |
| 7868754 | Salvat, Jr. | Jan 2011 | B2 |
| 7893876 | Brown et al. | Feb 2011 | B2 |
| 7908030 | Handfield et al. | Mar 2011 | B2 |
| 7918830 | Langan et al. | Apr 2011 | B2 |
| 7928844 | Mackenzie et al. | Apr 2011 | B2 |
| 7933033 | Ohishi et al. | Apr 2011 | B2 |
| 7976508 | Hoag | Jul 2011 | B2 |
| 7985711 | Tohmatsu et al. | Jul 2011 | B2 |
| 7990272 | Wass et al. | Aug 2011 | B2 |
| 7996286 | Kreiner et al. | Aug 2011 | B2 |
| 8002174 | Coyne, III et al. | Aug 2011 | B2 |
| 8006903 | Braun et al. | Aug 2011 | B2 |
| 8009913 | Greyshock | Aug 2011 | B2 |
| 8031347 | Edwards et al. | Oct 2011 | B2 |
| 8042738 | Cloix | Oct 2011 | B2 |
| 8049627 | Addante | Nov 2011 | B1 |
| 8063925 | Tainer et al. | Nov 2011 | B2 |
| 8065858 | Leu et al. | Nov 2011 | B2 |
| 8072635 | Roberts et al. | Dec 2011 | B2 |
| 8077041 | Stern et al. | Dec 2011 | B2 |
| 8082192 | Nycz et al. | Dec 2011 | B2 |
| 8099339 | Pinsonneault et al. | Jan 2012 | B1 |
| 8108068 | Boucher et al. | Jan 2012 | B1 |
| 8111159 | Andreasson et al. | Feb 2012 | B2 |
| 8112175 | Handfield et al. | Feb 2012 | B2 |
| 8131397 | Vahlberg et al. | Mar 2012 | B2 |
| 8154390 | Heath et al. | Apr 2012 | B2 |
| 8174392 | Sagbhini et al. | May 2012 | B1 |
| 8186587 | Zmood et al. | May 2012 | B2 |
| 8212677 | Ferguson | Jul 2012 | B2 |
| 8219413 | Martinez et al. | Jul 2012 | B2 |
| 8224483 | Ansari et al. | Jul 2012 | B1 |
| 8231749 | Dent et al. | Jul 2012 | B2 |
| 8258961 | Phillips et al. | Sep 2012 | B2 |
| 8261939 | Knoth | Sep 2012 | B2 |
| 8271128 | Schultz | Sep 2012 | B1 |
| 8279069 | Sawyer | Oct 2012 | B2 |
| 8283287 | Aihara et al. | Oct 2012 | B2 |
| 8284059 | Ross | Oct 2012 | B2 |
| 8285083 | Canessa et al. | Oct 2012 | B2 |
| 8285607 | Danilewitz | Oct 2012 | B2 |
| 8286222 | Silverbrook et al. | Oct 2012 | B2 |
| 8292173 | Yturralde et al. | Oct 2012 | B2 |
| 8292186 | Deloche et al. | Oct 2012 | B2 |
| 8296950 | Colbrunn et al. | Oct 2012 | B2 |
| 8313024 | Marino | Nov 2012 | B2 |
| 8319607 | Grimlund et al. | Nov 2012 | B2 |
| 8328082 | Bochenko et al. | Dec 2012 | B1 |
| 8339649 | Ohishi et al. | Dec 2012 | B2 |
| 8341041 | Hull | Dec 2012 | B2 |
| 8346632 | Saghbini | Jan 2013 | B2 |
| 8355753 | Bochenko et al. | Jan 2013 | B2 |
| 8355962 | Delaney et al. | Jan 2013 | B2 |
| 8359338 | Butterfield et al. | Jan 2013 | B2 |
| 8371448 | Reaux | Feb 2013 | B1 |
| 8376228 | DeVet | Feb 2013 | B2 |
| 8384545 | Hussain et al. | Feb 2013 | B2 |
| 8385972 | Bochenko et al. | Feb 2013 | B2 |
| 8386070 | Eliuk et al. | Feb 2013 | B2 |
| 8394053 | Bochenko et al. | Mar 2013 | B2 |
| 8403212 | van Esch | Mar 2013 | B2 |
| 8403224 | Fedorko et al. | Mar 2013 | B2 |
| 8405508 | Burke | Mar 2013 | B2 |
| 8438067 | Omura et al. | May 2013 | B2 |
| 8461076 | Okada et al. | Jun 2013 | B2 |
| 8483550 | Wright et al. | Jul 2013 | B2 |
| 8509604 | Wright et al. | Aug 2013 | B2 |
| 8515251 | Wright et al. | Aug 2013 | B2 |
| 8519849 | Ross-Messemer | Aug 2013 | B2 |
| 8530379 | Shimizu et al. | Sep 2013 | B2 |
| 8564416 | Steven et al. | Oct 2013 | B2 |
| 8565552 | Sommer et al. | Oct 2013 | B2 |
| 8582171 | Srnka et al. | Nov 2013 | B2 |
| 8589271 | Evans | Nov 2013 | B2 |
| 8593278 | Churbock et al. | Nov 2013 | B2 |
| 8593678 | Ohishi et al. | Nov 2013 | B2 |
| D694817 | Adam et al. | Dec 2013 | S |
| 8606596 | Bochenko et al. | Dec 2013 | B1 |
| 8636202 | Keefe et al. | Jan 2014 | B2 |
| 8639525 | Levine et al. | Jan 2014 | B2 |
| 8686859 | Hussain et al. | Apr 2014 | B2 |
| 8699054 | Edwards et al. | Apr 2014 | B2 |
| 8702674 | Bochenko | Apr 2014 | B2 |
| 8723674 | Conley et al. | May 2014 | B2 |
| 8749356 | Hussain et al. | Jun 2014 | B2 |
| 8755056 | Edwards et al. | Jun 2014 | B2 |
| 8825680 | Burke et al. | Sep 2014 | B2 |
| 8838215 | John et al. | Sep 2014 | B2 |
| 8868616 | Otto et al. | Oct 2014 | B1 |
| 8893970 | Keefe et al. | Nov 2014 | B2 |
| 8922435 | Fontecchio et al. | Dec 2014 | B2 |
| 8935280 | Bauman et al. | Jan 2015 | B2 |
| 8945066 | Bochenko et al. | Feb 2015 | B2 |
| 8948478 | Keefe et al. | Feb 2015 | B2 |
| 8985388 | Ratnakar | Mar 2015 | B2 |
| 8990099 | MacDonald et al. | Mar 2015 | B2 |
| 9037479 | MacDonald et al. | May 2015 | B1 |
| 9058412 | MacDonald et al. | Jun 2015 | B2 |
| 9058413 | MacDonald et al. | Jun 2015 | B2 |
| 9058435 | Keefe et al. | Jun 2015 | B2 |
| 9171280 | Gitchell et al. | Oct 2015 | B2 |
| 9189769 | Caputo et al. | Nov 2015 | B2 |
| 9367665 | MacDonald et al. | Jun 2016 | B2 |
| 9449296 | MacDonald et al. | Sep 2016 | B2 |
| 9539374 | Halpern | Jan 2017 | B2 |
| 9582644 | Gitchell et al. | Feb 2017 | B2 |
| 9734294 | MacDonald et al. | Aug 2017 | B2 |
| 9805169 | MacDonald et al. | Oct 2017 | B2 |
| 10083766 | Gitchell et al. | Sep 2018 | B2 |
| 10210954 | Caputo | Feb 2019 | B2 |
| 10600513 | Gitchell et al. | Mar 2020 | B2 |
| 10609845 | Elizondo, II | Mar 2020 | B2 |
| 9058413 | MacDonald et al. | Apr 2020 | C1 |
| 10621394 | Hussain et al. | Apr 2020 | B2 |
| 10643743 | Caputo et al. | May 2020 | B2 |
| 10658077 | Hussain et al. | May 2020 | B2 |
| 10658078 | Caputo et al. | May 2020 | B2 |
| 10664740 | Elizondo, II | May 2020 | B2 |
| 20020026330 | Klein | Feb 2002 | A1 |
| 20020049650 | Reff | Apr 2002 | A1 |
| 20020087360 | Pettit | Jul 2002 | A1 |
| 20020087362 | Cobb et al. | Jul 2002 | A1 |
| 20020087554 | Seelinger | Jul 2002 | A1 |
| 20030055685 | Cobb et al. | Mar 2003 | A1 |
| 20030074223 | Hickle et al. | Apr 2003 | A1 |
| 20030102970 | Creel et al. | Jun 2003 | A1 |
| 20030160698 | Andreasson et al. | Aug 2003 | A1 |
| 20030216974 | Browne | Nov 2003 | A1 |
| 20040008123 | Carrender et al. | Jan 2004 | A1 |
| 20040032330 | Hoffman | Feb 2004 | A1 |
| 20040051368 | Caputo et al. | Mar 2004 | A1 |
| 20040057609 | Weinberg | Mar 2004 | A1 |
| 20040081669 | Greeven et al. | Apr 2004 | A1 |
| 20040158507 | Meek et al. | Aug 2004 | A1 |
| 20040178071 | Harrison et al. | Sep 2004 | A1 |
| 20040215486 | Braverman | Oct 2004 | A1 |
| 20040225528 | Brock | Nov 2004 | A1 |
| 20050014849 | Pettit et al. | Jan 2005 | A1 |
| 20050060171 | Molnar | Mar 2005 | A1 |
| 20050062603 | Fuerst et al. | Mar 2005 | A1 |
| 20050108044 | Koster | May 2005 | A1 |
| 20050125097 | Chudy et al. | Jun 2005 | A1 |
| 20050127176 | Dickinson | Jun 2005 | A1 |
| 20050149378 | Cyr et al. | Jul 2005 | A1 |
| 20050149414 | Schrodt et al. | Jul 2005 | A1 |
| 20050184151 | DiMaggio et al. | Aug 2005 | A1 |
| 20050283259 | Wolpow | Dec 2005 | A1 |
| 20050285732 | Sengupta et al. | Dec 2005 | A1 |
| 20050285746 | Sengupta et al. | Dec 2005 | A1 |
| 20060006999 | Walczyk et al. | Jan 2006 | A1 |
| 20060043177 | Nycz et al. | Mar 2006 | A1 |
| 20060043179 | Nycz et al. | Mar 2006 | A1 |
| 20060065726 | Andreasson et al. | Mar 2006 | A1 |
| 20060109105 | Varner et al. | May 2006 | A1 |
| 20060132311 | Kruest et al. | Jun 2006 | A1 |
| 20060145871 | Donati et al. | Jul 2006 | A1 |
| 20060152338 | Hsu | Jul 2006 | A1 |
| 20060152364 | Walton | Jul 2006 | A1 |
| 20060152367 | Narayanaswamy | Jul 2006 | A1 |
| 20060208886 | Beamer | Sep 2006 | A1 |
| 20060267731 | Chen | Nov 2006 | A1 |
| 20070001809 | Kodukula et al. | Jan 2007 | A1 |
| 20070008399 | Botten et al. | Jan 2007 | A1 |
| 20070023512 | Miller et al. | Feb 2007 | A1 |
| 20070023513 | Andreasson et al. | Feb 2007 | A1 |
| 20070074722 | Giroux et al. | Apr 2007 | A1 |
| 20070114279 | Lessing et al. | May 2007 | A1 |
| 20070150382 | Danilewitz | Jun 2007 | A1 |
| 20070187475 | MacLeod | Aug 2007 | A1 |
| 20070188306 | Tethrake et al. | Aug 2007 | A1 |
| 20070200702 | Chung | Aug 2007 | A1 |
| 20070213659 | Trovato et al. | Sep 2007 | A1 |
| 20070213684 | Hickle et al. | Sep 2007 | A1 |
| 20070229268 | Swan et al. | Oct 2007 | A1 |
| 20070272746 | Ortiz et al. | Nov 2007 | A1 |
| 20080004908 | Oh | Jan 2008 | A1 |
| 20080012687 | Rubinstein | Jan 2008 | A1 |
| 20080045930 | Makin et al. | Feb 2008 | A1 |
| 20080046295 | Albrecht | Feb 2008 | A1 |
| 20080094214 | Azevedo et al. | Apr 2008 | A1 |
| 20080122878 | Keefe et al. | May 2008 | A1 |
| 20080128482 | Chen et al. | Jun 2008 | A1 |
| 20080129496 | Koblasz | Jun 2008 | A1 |
| 20080150722 | Jackson | Jun 2008 | A1 |
| 20080157967 | Jones et al. | Jul 2008 | A1 |
| 20080172253 | Chung et al. | Jul 2008 | A1 |
| 20080184719 | Lowenstein | Aug 2008 | A1 |
| 20080191013 | Liberatore | Aug 2008 | A1 |
| 20080218307 | Schoettle | Sep 2008 | A1 |
| 20080228160 | Harrison | Sep 2008 | A1 |
| 20080231456 | Matityaho | Sep 2008 | A1 |
| 20080243088 | Evans | Oct 2008 | A1 |
| 20080270178 | McRae et al. | Oct 2008 | A1 |
| 20080296373 | Smood et al. | Dec 2008 | A1 |
| 20080297356 | Oberle | Dec 2008 | A1 |
| 20080306772 | Shahrokh | Dec 2008 | A1 |
| 20080316045 | Sriharto | Dec 2008 | A1 |
| 20090002173 | Bergsten et al. | Jan 2009 | A1 |
| 20090020442 | Dietrich et al. | Jan 2009 | A1 |
| 20090058653 | Geissler et al. | Mar 2009 | A1 |
| 20090144087 | Kelsch et al. | Jun 2009 | A1 |
| 20090153290 | Bierach | Jun 2009 | A1 |
| 20090164042 | Handfield et al. | Jun 2009 | A1 |
| 20090194987 | Christie et al. | Aug 2009 | A1 |
| 20090224891 | Vishik et al. | Sep 2009 | A1 |
| 20090231138 | Cheung et al. | Sep 2009 | A1 |
| 20090267740 | Pizzuto et al. | Oct 2009 | A1 |
| 20090267772 | Dehnadi | Oct 2009 | A1 |
| 20090277815 | Kohl | Nov 2009 | A1 |
| 20090294521 | De La Huerga | Dec 2009 | A1 |
| 20100022953 | Bochenko et al. | Jan 2010 | A1 |
| 20100022987 | Bochenko | Jan 2010 | A1 |
| 20100036310 | Hillman | Feb 2010 | A1 |
| 20100036678 | Bray | Feb 2010 | A1 |
| 20100036755 | Saghbini | Feb 2010 | A1 |
| 20100042439 | Martinez et al. | Feb 2010 | A1 |
| 20100079337 | Hsu et al. | Apr 2010 | A1 |
| 20100098425 | Kewitsch | Apr 2010 | A1 |
| 20100108761 | Nycz et al. | May 2010 | A1 |
| 20100185458 | Calderwood et al. | Jul 2010 | A1 |
| 20100204659 | Bochenko | Aug 2010 | A1 |
| 20100217621 | Schoenberg et al. | Aug 2010 | A1 |
| 20100219097 | Ramasubramanian et al. | Sep 2010 | A1 |
| 20100238039 | Tethrake et al. | Sep 2010 | A1 |
| 20100268548 | Garrett et al. | Oct 2010 | A1 |
| 20100275625 | Lowenstein | Nov 2010 | A1 |
| 20100299158 | Siegel | Nov 2010 | A1 |
| 20100328474 | Hsieh | Dec 2010 | A1 |
| 20100332246 | Fedorko et al. | Dec 2010 | A1 |
| 20110006879 | Bartos | Jan 2011 | A1 |
| 20110063091 | Kang | Mar 2011 | A1 |
| 20110068922 | Ross | Mar 2011 | A1 |
| 20110112682 | Matsukawa et al. | May 2011 | A1 |
| 20110115612 | Kulinets et al. | May 2011 | A1 |
| 20110125315 | Handfield et al. | May 2011 | A1 |
| 20110131056 | Chudy et al. | Jun 2011 | A1 |
| 20110139871 | Yturralde et al. | Jun 2011 | A1 |
| 20110161112 | Keefe et al. | Jun 2011 | A1 |
| 20110163871 | Einav et al. | Jul 2011 | A1 |
| 20110166878 | Louie et al. | Jul 2011 | A1 |
| 20110184751 | Holmes | Jul 2011 | A1 |
| 20110187549 | Balasing | Aug 2011 | A1 |
| 20110225100 | Sangal et al. | Sep 2011 | A1 |
| 20110227722 | Salvat, Jr. | Sep 2011 | A1 |
| 20110240729 | Schuck | Oct 2011 | A1 |
| 20110257991 | Shukla | Oct 2011 | A1 |
| 20110270441 | Handfield et al. | Nov 2011 | A1 |
| 20110291809 | Niemiec et al. | Dec 2011 | A1 |
| 20110301446 | Kamen | Dec 2011 | A1 |
| 20110313395 | Krulevitch et al. | Dec 2011 | A1 |
| 20120037266 | Bochenko | Feb 2012 | A1 |
| 20120041778 | Kraft | Feb 2012 | A1 |
| 20120044054 | Hussain | Feb 2012 | A1 |
| 20120061463 | Burke | Mar 2012 | A1 |
| 20120089411 | Srnka et al. | Apr 2012 | A1 |
| 20120089418 | Kamath et al. | Apr 2012 | A1 |
| 20120116798 | Heath et al. | May 2012 | A1 |
| 20120125994 | Heath et al. | May 2012 | A1 |
| 20120130534 | Wurm | May 2012 | A1 |
| 20120173440 | Becker et al. | Jul 2012 | A1 |
| 20120179132 | Valk et al. | Jul 2012 | A1 |
| 20120185951 | Bauman et al. | Jul 2012 | A1 |
| 20120209619 | Knotts et al. | Aug 2012 | A1 |
| 20120240067 | Bauman et al. | Sep 2012 | A1 |
| 20120273087 | Einy et al. | Nov 2012 | A1 |
| 20120278096 | Holness | Nov 2012 | A1 |
| 20120278228 | Rubinstein | Nov 2012 | A1 |
| 20120323208 | Bochenko et al. | Dec 2012 | A1 |
| 20120325330 | Prince et al. | Dec 2012 | A1 |
| 20130018356 | Prince et al. | Jan 2013 | A1 |
| 20130038452 | Sawyer | Feb 2013 | A1 |
| 20130041784 | Danilewitz | Feb 2013 | A1 |
| 20130092727 | Edwards et al. | Apr 2013 | A1 |
| 20130105568 | Jablonski et al. | May 2013 | A1 |
| 20130151005 | Gerold et al. | Jun 2013 | A1 |
| 20130191149 | Kolberg et al. | Jul 2013 | A1 |
| 20130221082 | Botten | Aug 2013 | A1 |
| 20130225945 | Prince et al. | Aug 2013 | A1 |
| 20140060729 | Srnka et al. | Mar 2014 | A1 |
| 20140066880 | Prince et al. | Mar 2014 | A1 |
| 20140117081 | Jablonski et al. | May 2014 | A1 |
| 20140136229 | Levine et al. | May 2014 | A1 |
| 20140142975 | Keefe et al. | May 2014 | A1 |
| 20140184390 | Elizondo, II | Jul 2014 | A1 |
| 20140184391 | Elizondo, II | Jul 2014 | A1 |
| 20140197954 | Caputo et al. | Jul 2014 | A1 |
| 20140210596 | Hussain et al. | Jul 2014 | A1 |
| 20140262919 | Hussain et al. | Sep 2014 | A1 |
| 20140263614 | Keefe et al. | Sep 2014 | A1 |
| 20140276213 | Bochenko | Sep 2014 | A1 |
| 20140282197 | Keefe et al. | Sep 2014 | A1 |
| 20140291397 | Caputo et al. | Oct 2014 | A1 |
| 20140367080 | Hussain et al. | Dec 2014 | A1 |
| 20150058182 | Kress-Spatz et al. | Feb 2015 | A1 |
| 20150235005 | MacDonald et al. | Aug 2015 | A1 |
| 20150339622 | MacDonald et al. | Nov 2015 | A1 |
| 20160132649 | Gitchell et al. | May 2016 | A1 |
| 20170212993 | Gitchell et al. | Jul 2017 | A1 |
| 20180039758 | MacDonald et al. | Feb 2018 | A1 |
| 20190088354 | Yanowitz et al. | Mar 2019 | A1 |
| 20190272396 | Clouser et al. | Sep 2019 | A1 |
| 20200013494 | Caputo et al. | Jan 2020 | A1 |
| 20200167534 | Elizondo, II | May 2020 | A1 |
| 20200357509 | Gitchell et al. | Nov 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 722 328 | Oct 2009 | CA |
| 2 790 220 | Jun 2013 | CA |
| 102791310 | Dec 2014 | CN |
| 2 496 283 | Sep 2012 | EP |
| 201204914 | Oct 2013 | IN |
| WO 02095675 | Nov 2002 | WO |
| WO 03071943 | Sep 2003 | WO |
| WO 2006026246 | Mar 2006 | WO |
| WO 2006135830 | Dec 2006 | WO |
| WO 2010074781 | Jul 2010 | WO |
| WO 2011056888 | Sep 2011 | WO |
| WO 2011115676 | Sep 2011 | WO |
| WO 2011150013 | Dec 2011 | WO |
| WO 2013082423 | Jun 2013 | WO |
| WO 2013116873 | Aug 2013 | WO |
| WO 2013134256 | Sep 2013 | WO |
| WO 2014159928 | Oct 2014 | WO |
| WO 2014189834 | Nov 2014 | WO |
| WO 2015026387 | Feb 2015 | WO |
| Entry |
|---|
| Baum, “How did RFID help University of MD Medical Center cut medication error rate?” Med City News, https://medcitynews.com/2013/12/rfid-help-university-md-medical-center-cut-medication-error-rate/?rf=1, Dec. 4, 2013, 2 Pages. |
| Brown, Dennis E., “RFID Implementation”, McGraw-Hill Communications, 2007, Ch. 3 & 7 (portions), pp. 62-65, 81, 92-96, 106-113, 188-193 & 429. |
| Garza, Anyssa, “The Future of Pharmacy Medication Kit Storage”, Pharmacy Times, https://www.pharmacytimes.com/contributor/anyssa-garza/2014/12/the-future-of-pharmacy-medication-kit-storage, Dec. 12, 2014, 2 Pages. |
| Glover et al., “RFID Essentials”, O'Reilly Media, 2006, pp. 2, 14, 24, 31, 33, 107-110, 113-114, 117, 137-143, 162-169, 178-179. |
| Hawkins-Simons, “RFID Streamlines Refilling of Drug Trays”, Pharmacy Technology Report, https://www.pharmacypracticenews.com/Pharmacy-Technology-Report/Article/03-14/RFID-Streamlines-Refilling-of-Drug-Trays/26159, Mar. 21, 2014, 9 Pages. |
| Kinsella, Bret, “Premier, Inc. Identifies Kit Check as ‘Technology Breakthrough Product’—Awards exclusive agreement for pharmacy kit medication tracking solution”, Press Release, https://kitcheck.com/2014/04/premier-inc-identifies-kit-check-technology-breakthrough-product-awards-exclusive-agreement-pharmacy-kit-medication-tracking-solution/, Apr. 2, 2014, 5 Pages. |
| KitCheck,“PharMEDium Prefilled Syringes with Kit Check: ASHP Symposium Summary”, Jun. 2016, https://kitcheck.com/wp-content/uploads/2016/06/pharmedium-prefilled-syringes-with-kit-check-download.pdf in 9 pages. |
| KitCheck,“St. Rita's Medical Center: 75% First-year ROI, Less Frustration”, Case Study, 2016, https://kitcheck.com/learn-more/case-study/st-ritas-medical-center/ in 2 pages. |
| “Medication Tray Management” Pharmacy Purchasing & Products, Feb. 2018, pp. 18 & 20. |
| “Medication Tray Management” Pharmacy Purchasing & Products, Presentation, Nov. 2018, pp. 76 & 78. |
| “Medication Tray Management” Pharmacy Purchasing & Products, State of Pharmacy Automation, Aug. 2016, pp. 42 & 45. |
| “Medication Tray Management” Pharmacy Purchasing & Products, State of Pharmacy Automation, Aug. 2019, pp. 34-35. |
| “ODIN Innovation Lab: EasyTunnel RFID”, as posted Jul. 13, 2009, archived via archive.org https://web.archive.org/web/20200316173502/https://www.youtube.com/watch?v=0rQhT4sIQnw, 1 page. |
| “ODIN RFID HQ Tour 2009”, as posted Mar. 19, 2009, archived via archive.org https://web.archive.org/web/20200316180429/https://www.youtube.com/watch?v=4Y4XIlD0B_Y, 1 page. |
| Summerfield, et al. “Evaluation of Medication Kit Processing Time Using Radio Frequency Identification (RFID) Technology”, Innovations in Pharmacy, 2015, vol. 6, No. 2, Article 199, 7 Pages. |
| Swedberg, Claire, “North Carolina Hospital Identifies Recalled Drugs Via RFID”, RFID Journal, http://www.rfidjournal.com/articles/view?10913, Aug. 14, 2013, 4 Pages. |
| Swedberg, Claire, “Zimmer Ohio to Use RFID to Manage Orthopedic Products”, RFID Journal, May 12, 2010, pp. 3. https://www.rfidjournal.com/articles/pdf?7588. |
| “UPM Raflatac UHF EPC Gen2 RFID in ODIN Solution at Johnson-Johnson DePuyIn-Q-Tel”, as posted Jun. 10, 2009, archived via archive.org https://web.archive.org/web/20200316174347/https://www.youtube.com/watch?v=JWGyR8BgfI8 , 1 page. |
| “Vizient, Inc. Awards Kit Check Contract for Pharmacy Kit Medication Inventory Tracking and Replenishment”, Press Release, http://www.prweb.com/releases/2016/09/prweb13691526.htm, Sep. 19, 2016, 3 Pages. |
| Plaintiff Kit Check, Inc.'s Motion to Strike Insufficient Defenses, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 19, 2018, 8 pages. |
| Defendant's Memorandum in Opposition to Plaintiff Kit Check, Inc.'s Mtion to Strike Insufficient Defenses, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 9, 2018, 6 pages. |
| Plaintiff's Answer to Defendant's First Amended Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 21, 2018, 14 pages. |
| Plaintiff Kit Check, Inc.'s Reply in Support of its Motion to Strike Insufficient Defenses, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 21, 2018, 6 pages. |
| Defendant Health Care Logistics, Inc.'s Motion for Judgment on the Pleadings Pursuant to Fed. R. Civ. P. 12(C), Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), May 25, 2018, 31 pages. |
| Exhibit A; U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), May 25, 2018, 12 pages. |
| Opinion & Order, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 13, 2018, 9 pages. |
| Plaintiff Kit Check, Inc.'s Memorandum in Opposition to Defendant Health Care Logistics, Inc.'s Motion for Judgment on the Pleadings, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 35 pages. |
| Exhibit 1; Non-Final Office Action for U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 11 pages. |
| Exhibit 2; Notice of Allowance for U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 15 pages. |
| Exhibit 3; Non-Final Office Action for U.S. Pat. No. 9,367,665, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 12 pages. |
| Exhibit 4; Response to Non-Final Office Action for U.S. Pat. No. 9,367,665, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 18 pages. |
| Defendant Health Care Logistics, Inc.'s Reply in Support of Motion for Judgment on the Pleadings Pursuant to Fed. R. Civ. P. 12(C), Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 20, 2018, 22 pages. |
| Exhibit A, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 20, 2018, 43 pages. |
| Exhibit B; Plaintiff Kit Check, Inc.'s Disclosure of Asserted Claims and Infringement Contentions under Local Patent Rule 103.2, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 20, 2018, 11 pages. |
| Plaintiff Kit Check, Inc.'s Motion to Strike Portions of Defendants' Reply or, in the Alternative, Motion for Leave to File a Sur-Reply, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 10, 2018, 6 pages. |
| Exhibit A; Plaintiff Kit Check, Inc.'s Sur-Reply in Opposition to Defendant's Motion for Judgment on the Pleadings, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 10, 2018, 5 pages. |
| Defendant Health Care Logistics, Inc.'s Memorandum in Opposition to Plaintiff Kit Check, Inc.'s Motion to Strike Portions of Defendant's Reply or, in the Alternative, Motion for Leave to File a Sur-Reply, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 31, 2018, 6 pages. |
| Plaintiff Kit Check, Inc.'s Reply in Support of its Motion to Strike Portions of Defendant's Reply or, in the Alternative, Motion for Leave to File a Sur-Reply, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Sep. 14, 2018, 7 pages. |
| Joint Claim Construction and Prehearing Statement, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Sep. 20, 2018, 21 pages. |
| Plaintiff Kit Check, Inc.'s Opening Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 50 pages. |
| Exhibit 1; Disputed Claim Terms Chart, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 4 pages. |
| Declaration of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 24 pages. |
| Defendant Health Care Logistics, Inc.'s Opening Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 32 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,367,665, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 256 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 9 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 32pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 8,990,099, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 42 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 8,990,099, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 557 pages. |
| Exhibit 1003; Expert Declaration,Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 9 pages. |
| Exhibit 1010; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 32 pages. |
| Exhibit 1011; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,058,412, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 75 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,058,412, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 75 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 9 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 32 pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,058,413, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 73 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,058,413, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 549 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 9 pages. |
| Exhibit 1009; Children's Hospital Boston Joins Others Using RFID to Track Implantables, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 3 pages. |
| Exhibit 1012; The “Orange Book”, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 1103 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 32 pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,805,169, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 76 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,805,169, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 286 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 9 pages. |
| Exhibit 1009; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 32 pages. |
| Exhibit 1010; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,367,665, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 69 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,367,665, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 256 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 9 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 32 pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 50 pages. |
| Plaintiff Kit Check, Inc.'s Notice of Filing Deposition Transcript of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 3 pages. |
| Exhibit A; Deposition of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 86 pages. |
| Plaintiff Kit Check, Inc.'s Responsive Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 23 pages. |
| Exhibit A, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 43 pages. |
| Exhibit B; Deposition of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 22 pages. |
| Defendant Health Care Logistics, Inc.'s Response to Plaintiff Kit Check, Inc.'s Opening Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 22 pages. |
| Plaintiff Kit Check, Inc.'s Memorandum in Opposition to Defendant Health Care Logistics, Inc.'s Motion for Stay, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 11, 2019, 21 pages. |
| Exhibit 1; Defendant Health Care Logistics, Inc.'s Invalidity Contentions Pursuant to Local Patent Rule 103.4, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 11, 2019, 26 pages. |
| Defendant Health Care Logistics, Inc.'s Reply in Support of Motion for Stay, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 25, 2019, 10 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, U.S. Pat. No. 8,990,099, Mar. 8, 2019, 26 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, U.S. Pat. No. 9,058,412 B2, Mar. 8, 2019, 28 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, U.S. Pat. No. 9,058,413 B2, Mar. 13, 2019, 28 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, U.S. Pat. No. 9,805,169 B2, Mar. 13, 2019, 25 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, U.S. Pat. No. 9,367,668 B2, Mar. 13, 2019, 28 pages. |
| Opinion & Order, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Mar. 14, 2019, 17 pages. |
| Joint Stipulation of Partial Dismissal Without Prejudice, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Apr. 16, 2019, 2 pages. |
| Transcript of Markman Hearing Proceedings, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), May 6, 2019, 74 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. §314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, U.S. Pat. No. 9,058,412 B2, Jun. 3, 2019, 28 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. §314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, U.S. Pat. No. 9,805,169 B2, Jun. 3, 2019, 20 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. §314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, U.S. Pat. No. 8,990,099 B2, Jun. 4, 2019, 18 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. §314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, U.S. Pat. No. 9,058,413 B2, Jun. 7, 2019, 26 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. §314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, U.S. Pat. No. 9,367,665 B2, Jun. 11, 2019, 25 pages. |
| Stipulation and [Proposed] Order Granting Leave to Amend Plaintiff's Infringement Contentions and Defendant's Invalidity Contentions, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 3, 2019, 3 pages. |
| Defendant Health Care Logistics, Inc.'s Motion for Leave to File Second Amended Answer, Affirmative Defenses, and Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 17, 2019, 5 pages. |
| Exhibit A; Defendant's Second Amended Answer, Affirmative Defenses, and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 17, 2019, 49 pages. |
| Request for ExParteReexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 8,990,099 B2, U.S. Appl. No. 13/554,342, filed Jul. 25, 2019 in 80 pages. |
| Request for ExParteReexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,058,412 B2, U.S. Appl. No. 14/603,730, filed Jul. 26, 2019 in 118 pages. |
| Request for ExParteReexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,058,413 B2, U.S. Appl. No. 14/603,828, filed Jul. 25, 2019 in 151 pages. |
| Request for ExParteReexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,805,169 B2, U.S. Appl. No. 14/701,958, filed Jul. 26, 2019 in 220 pages. |
| Request for ExParteReexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,367,665 B2, U.S. Appl. No. 14/818,113, filed Jul. 26, 2019 in 164 pages. |
| Opinion & Order, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 30, 2019, 26 pages. |
| Bryant, Blake, “Hacking SIEMs to Catch Hackers: Decreasing the Mean Time to Respond to Network Security Events with a Novel Threat Ontology in SIEM Software”, Master's Thesis, University of Kansas, 2016, pp. 257. |
| Pace et al., “Distributed Ambulatory Research in Therapeutics Network (DARTNet): Summary Report”, Effective Health Care Research Reports, No. 14, Agency for Healthcare Research and Quality, Jul. 2009, pp. 41. |
| “AmerisourceBergen Specialty Group Reconfigures Cubixx Medical Cabinet”, Jan. 9, 2011, pp. 2, https://web.archive.org/web/20180620192642/http://pharmaceuticalcommerce.com/supply-chain-logistics/amerisourcebergen-specialty-group-reconfigures-cubixx-medical-cabinet/. |
| Bacheldor, Beth, “ASD Healthcare Deploys RFID Refrigerated Drug Cabinets”, RFID Journal, Sep. 24, 2007, p. 1. http://www.rfidjournal.com/articles/view?3632. |
| Bacheldor, Beth, “Cardinal Health Readies Item-Level Pilot”, RFID Journal, May 31, 2006, p. 1. http://www.rfidjournal.com/articles/view?2380. |
| Bacheldor, Beth, “UCSD Medical Center Expands Its RFID Deployment”, RFID Journal, Oct. 29, 2008, pp. 2. http://www.rfidjournal.com/articles/view?4423. |
| Bacheldor, Beth, “UMass Med Center Finds Big Savings Through Tagging”, RFID Journal, Nov. 21, 2007, pp. 2. http://www.rfidjournal.com/articles/view?3763/2. |
| Becker et al., “SmartDrawer: RFID-Based Smart Medicine Drawer for Assistive Environments”, Conference: Proceedings of the 2nd International Conference on Pervasive Technologies Related to Assistive Environments, PETRA 2009, Corfu, Greece, Jun. 9-13, 2009, pp. 8. |
| Bendavid et al., “Using RFID to Improve Hospital Supply Chain Management for High Value and Consignment Items”, Procedia Computer Science, vol. 5, 2011, pp. 849-856. |
| Bendavid et al., “Redesigning the Replenishment Process of Medical Supplies in Hospitals with RFID”, Business Process Management Journal, 2010, vol. 16, No. 6, pp. 991-1013. |
| Cangialosi et al., “Leveraging RFID in Hospitals: Patient Life Cycle and Mobility Perspectives”, IEEE Applications & Practice, Sep. 2007, pp. 18-23. |
| Chao et al., “Determining Technology Trends and Forecasts of RFID by a Historical Review and Bibliometric Analysis from 1991 to 2005”, Technovation, vol. 27, 2007, pp. 268-279. |
| Collins, “RFID Cabinet Manages Medicine”, RFID Journal, Aug. 12, 2004, p. 1. http://www.rfidjournal.com/articles/view?1081. |
| “Data Gathering Developments”, Manufacturing Chemist, Feb. 1, 2005, p. 24. https://www.manufacturingchemist.com/news/article_page/Data_gathering_developments/35805. |
| Dutta et al., “RFID and Operations Management: Technology, Value, and Incentives”, Production and Operations Management (POMS), vol. 16, No. 5, Sep.-Oct. 2007, pp. 646-655. |
| Edwards, John, “RFID Smart Shelves and Cabinets”, RFID Journal, Aug. 24, 2009, pp. 4. http://www.rfidjournal.com/articles/view?5140/4. |
| Erdem et al., “Investigation of RFID Tag Readability for Pharmaceutical Products at Item Level”, Drug Development and Industrial Pharmacy, 2009, vol. 35, No. 11, pp. 1312-1324. |
| Fahrni, Jerry, “More RFID Refrigerator Stuff—Cubixx and myCubixx”, Sep. 3, 2012, pp. 4. http://jerryfahmi.com/2012/09/more-rfid-refrigerator-stuff-cubixx-and-mycubixx/. |
| “Faraday Cage”, Wikipedia, last edited Apr. 12, 2018, pp. 5. https://en.wikipedia.org/wiki/Faraday_cage. |
| Floerkemeier et al., “The Smart Box Concept for Ubiquitous Computing Environments”, The Smart Box Concept for Ubiquitous Computing Environments, 2004, pp. 4. |
| Green, Kathryn, “Doing the Wave: Inventory Management with RFID”, Diagnostic & Interventional Services, UMass Memorial Medical Center, Worcester, MA, vol. 15, No. 9, Sep. 2007, pp. 7. https://www.cathlabdigest.com/articles/Doing-Wave-Inventory-Management-RFID. |
| Ho et al., “A Prototype on RFID and Sensor Networkds for Elder Healthcare: Progress Report”, SIGCOMM '05 Workshops, Aug. 22-26, 2005, Philadelphia, PA, pp. 70-75. |
| Howard, JD, “Implementation of RFID in the Pharmaceutical Industry”, Advisor: Dr. Jay Singh, California Polytechnic State University, San Luis Obispo, CA, Feb. 2009, pp. 11. |
| Humble, RN, Carol, “How RFID Freed Nurses From the Pain of Inventory Duties”, Cath Lab Digest, Dec. 2009, vol. 17, No. 12. https://www.cathlabdigest.com/articles/How-RFID-Freed-Nurses-From-Pain-Inventory-Duties. |
| “Intel & Siemens Launch RFID Blood Bank in Malaysia”, RFID Journal, Aug. 16, 2007, p. 1. https://www.rfidjournal.com/articles/view?6801. |
| Jones et al., “The Benefits, Challenges and Impacts of Radio Frequency Identification Technology (RFID) for Retailers in the UK”, Marketing Intelligence & Planning, Mar. 2005, vol. 23, No. 4, pp. 395-402. |
| Juels, Ari, “RFID Security and Privacy: A Research Survey”, IEEE Journal on Selected Areas in Communications, vol. 24, No. 2, Feb. 2006, pp. 381-394. |
| Lahtela et al., “RFID and NFC in Healthcare: Safety of Hospitals Medication Care”, 2008 Second International Conference on Pervasive Computing Technologies for Healthcare, Tampere, Finland, Jan. 30-Feb. 1, 2008, pp. 4. |
| Lewis, Mark O., “RFID-Enabled Capabilities and their Impact on Healthcare Process Performance”, 31st International Conference on Information Systems, St. Louis, 2010, pp. 1-20. |
| Liu et al., “Point-of-Care Support for Error-Free Medication Process” (Jun. 25, 2007), retrieved Aug. 21, 2017, 12 pages, available at http://ieeexplore.ieee.org/document/4438162/. |
| McCall et al., “RMAIS: RFID-based Medication Adherence Intelligence System” (Aug. 31, 2010), retrieved Aug. 21, 2017, 4 pages, available at http://ieeexplore.ieee.org/document/5627529/. |
| Mehrjerdi, Yahia Zare, “RFID-Enabled Healthcare Systems: Risk-Benefit Analysis”, International Journal of Pharmaceutical and Healthcare Marketing, 2010, vol. 4, No. 3, pp. 282-300. |
| Meiller et al., “Adaptive Knowledge-Based System for Health Care Applications with RFID-Generated Information”, Decision Support Systems, vol. 51, 2011, pp. 198-207. |
| Mowry, Mike, “A Survey of RFID in the Medical Industry: With Emphasis on Applications to Surgery and Surgical Devices”, MAE188, Introduction to RFID, Dr. Rajit Gadh, UCLA, Jun. 9, 2008, pp. 22. |
| “New RFID Medical Cabinets Deployed at 50 Hospitals”, RFID Journal, Sep. 17, 2007, pp. 2. https://www.rfidjournal.com/articles/view?6823. |
| O'Connor, Mary Catherine, “Drug Distributor Uses RFID to Vend Meds”, RFID Journal, May 23, 2006, pp. 2. https://www.rfidjournal.com/articles/view?2363/2. |
| O'Connor, Mary Catherine, “GlaxoSmithKline Tests RFID on HIV Drug”, RFID Journal, Mar. 24, 2006, pp. 2. https://www.rfidjournal.com/articles/view?2219/. |
| O'Connor, Mary Catherine, “Interrogators Start to Evolve”, RFID Journal, Jun. 1, 2006, pp. 3. https://www.rfidjournal.com/purchase-access?type=Article&id=2398&r=%2Farticles%2Fview%3F2398. |
| O'Connor, Mary Catherine, “Johnson & Johnson Finds Value in Multiple RFID Apps”, RFID Journal, Apr. 23, 2008, pp. 2. https://www.rfidjournal.com/articles/pdf?4046. |
| O'Connor, Mary Catherine, “McKesson Starts RFID Pilot for Viagra”, RFID Journal, Feb. 17, 2005, pp. 2. https://www.rfidjournal.com/articles/view?2157. |
| O'Connor, Mary Catherine, “Pfizer Using RFID to Fight Fake Viagra”, RFID Journal, Jun. 6, 2006, pp. 2. https://www.rfidjournal.com/articles/pdf?2075. |
| Parida et al., “Application of RFID Technology for In-House Drug Management System”, 15th International Conference on Network-Based Information Systems, 2012, pp. 577-581. |
| “RFID Medical Cabinets Evaluated in New Benchmark”, RFID Journal, Sep. 12, 2007, pp. 2. https://www.rfidjournal.com/articles/view?6819. |
| Roberti, Mark, “RFID Basics for Health Care, RFID in Health Care”, Produced by RFID Journal, Sep. 17, 2009, The Westin Waltham-Boston, Waltham, MA, pp. 33. |
| Saygin, C., “Adaptive Inventory Management Using RFID Data”, The International Journal of Advanced Manufacturing Technology, 2007, vol. 32, pp. 1045-1051. |
| Singh et al., “Versatility of Radio Frequency Identification (RFID) Tags in the Pharmaceutical Industry”, Instrumentation Science and Technology, vol. 36, pp. 656-663, 2008. |
| Swedberg, Claire, “Tennessee Hospital Tracks High-Value Items”, RFID Journal, Aug. 5, 2009, pp. 2. http://www.rfidjournal.com/articles/view?5106. |
| Tsai et al., “iMAT: Intelligent Medication Administration Tools” (Jul. 1, 2010), retrieved Aug. 21, 2017, 8 pages, available at http://ieeexplore.ieee.org/document/5556551/. |
| Tsai et al., “Smart Medication Dispenser: Design, Architecture and Implementation” (Sep. 27, 2010), retrieved Aug. 21, 2017, 12 pages, available at http://ieeexplore.ieee.org/document/5585838/. |
| Wang et al., “RFID Applications in Hospitals: A Case Study on a Demonstration RFID Project in a Taiwan Hospital”, Proceedings of the 39th Hawaii International Conference on System Sciences, 2006, pp. 1-10. |
| Wasserman, Elizabeth, “Purdue Pharma to Run Pedigree Pilot”, RFID Journal, May 31, 2005, pp. 2. http://www.rfidjournal.com/articles/view?1626. |
| Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Dec. 1, 2017, 45 pages. |
| Defendant's Answer, Affirmative Defenses and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 2, 2018, 43 pages. |
| Defendant's First Amended Answer, Affirmative Defenses and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 9, 2018, 43 pages. |
| Defendant Health Care Logistics, Inc's Invalidity Contentions Pursuant to Local Patent Rule 103.4, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 25 pages. |
| Exhibit 1; Initial Invalidity Claim Chart for U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 51 pages. |
| Exhibit 2; Initial Invalidity Claim Chart for U.S. Pat. No. 9,058,413, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 94 pages. |
| Exhibit 3; Initial Invalidity Claim Chart for U.S. Pat. No. 9,058,412, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 83 pages. |
| Exhibit 4; Initial Invalidity Claim Chart for U.S. Pat. No. 9,734,294, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 58 pages. |
| Exhibit 5; Initial Invalidity Claim Chart for U.S. Pat. No. 9,805,169, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 251 pages. |
| Exhibit 6; Initial Invalidity Claim Chart for U.S. Pat. No. 9,037,479, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 43 pages. |
| Exhibit 7; Initial Invalidity Claim Chart for U.S. Pat. No. 9,367,665, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 109 pages. |
| Exhibit L; Fagron Academy, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Dec. 1, 2017, 2 pages. |
| Plaintiff's Answer to Defendant's Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 19, 2018, 14 pages. |
| Barlas, Stephen, “Pharmacy Product Tracing Likely to Go National—Costs to Pharmacies Worrisome,” Pharmacy & Therapeutics, Jan. 2009, vol. 34 No. 1, p. 14. |
| Belson, D., “Storage, Distribution, and Dispensing of Medical Supplies,” CREATE Interim Report Under FEMA Grant EMW-2004-GR-0112, Apr. 21, 2005, pp. 1-36. |
| Çakici et al., “Using RFID for the management of pharmaceutical inventory-system optimization and shrinkage control,” Decision Support Systems, 2011, pp. 842-852. |
| CPG Sec. 400.210, Radiofrequency Identification Feasibility Studies and Pilot Programs for Drugs Nov. 2004 Compliance Policy Guide available at: http://www.fda.goy/ICECI/ComplianceManuals/CompliancePolicyGuidanceManual/ucm074357.htm. |
| Crash Cart Inventory Checklist, Outpatient Surgery Magazine, Oct. 2004, “Outpatient Surgery”, available at: http://www.outpatientsurgery.net/resources/forms/2004/pdf/OutpatientSurgeryMagazine_0410_crashCart.pdf, in 1 page. |
| Curtin et al., “Making the ‘MOST’ out of RFID: a research agenda for the study of the adoption, usage and impact of RFID,” Information Technology Management, Apr. 2007, pp. 87-110. |
| Gonzalez, Stephanie, “Health Maintenance System (HMS) Hardware Research, Design, and Collaboration,” NASA USRP—Internship Final Report, 2010, pp. 1-20. |
| Harrop et al., “RFID for Healthcare and Pharmaceuticals, 2008-2018,” Securing Pharma, May 2008, pp. 1-12. |
| Houliston, Bryan, “Integrating RFID Technology into a Drug Administration System,” Bulletin of Applied Computing and Information Technology, vol. 3, No. 1, May 2005, pp. 8. Retrieved Sep. 26, 2013 from http://citrenz.ac.nz/bacit/0301/2005Houliston_RFID.htm. |
| Jorgensen et al., “Executable Use Cases: Requirements for a Pervasive Health Care System,” IEEE Software, Mar./Apr. 2004, pp. 34-41. |
| Lai et al., “Enhancing Medication Safety and Reduce Adverse Drug Events on Inpatient Medication Administration using RFID,” WSEAS Transactions on Communications, Oct. 2008, vol. 7, No. 10, pp. 1045-1054. |
| Lampe et al., “The Smart Box Application Model,” Advances in Pervasive Computing, 2004, pp. 1-6. |
| “McKesson's Announces New Touch-Screen Driven Medication Dispensing Solution”, Business Wire, Jun. 15, 2009, pp. 2, Available at: http://www.businesswire.com/news/home/20090615005349/en/McKesson-Announces-Touch-Screen-Driven-Medication-Dispensing-Solution#.VR7quPnF_10. |
| “Medical Packaging Inc. Announces Clear Stem Flag Label System for Ampoules, Vials, and Syringes” Feb. 1, 2006 available at: http://www.medpak.com/v1/news/20060201_CSFLAG.pdf, in 1 page. |
| O'Connor, Mary Catherine, “To Keep Drugs from Expiring, Hospital Tests Intelliguard System”, RFID Journal, Jan. 12, 2011, pp. 3. http://www.rfidjournal.com/articles/view?8123. |
| O'Driscoll et al, “RFID: An Ideal Technology for Ubiquitous Computing?” Dublin Institute of Technology School of Electronic and Communications Conference Papers, Jan. 1, 2008, pp. 1-17. |
| Pappu, Ph.D. et al., “RFiD in Hospitals: Issues and Solutions” Consortium for the Accelerated Deployment of RFID in Distribution, Sep. 2004, pp. 1-12. |
| Tzeng et al., “Evaluating the Business Value of RFID: Evidence from Five Case Studies,” International Journal of Production Economics, 2008, vol. 112, pp. 601-613. |
| Wang et al., “Applying RFID Technology to Develop a Distant Medical Care Service Platform,” International Journal of Electronic Business Management, 2010, vol. 8, No. 2, pp. 161-170. |
| International Search Report and Written Opinion in PCT Application No. PCT/US2014/053837 dated Nov. 24, 2014. |
| International Preliminary Report on Patentability and Written Opinion in PCT Application No. PCT/US2014/053837 dated Jan. 19, 2017. |
| Number | Date | Country | |
|---|---|---|---|
| 20170132734 A1 | May 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62021927 | Jul 2014 | US | |
| 61514231 | Aug 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14472410 | Aug 2014 | US |
| Child | 15269371 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13554342 | Jul 2012 | US |
| Child | 14472410 | US |
