The present invention relates to the tracking of inventory (i.e., implants, tools, and other objects that may be used in a surgical procedure) in the medical device field. More particularly, the present invention relates to the tracking of inventory after the inventory has left the manufacturer (e.g., as part of a bulk package in a tray) and has been put into use at a medical facility. Currently, tracking surgical or medical device inventory is difficult. Further, there is a need to comply with government regulations regarding unique device identifying codes for devices that are bulk packaged in trays intended for repetitive steam sterilization prior to implantation or use.
In current systems for providing implants and tools during an operation, a large choice of devices may be provided to the operating area for the surgeon (or other personnel), allowing for the individualization of choice by the surgeon for the patient. In other words, the surgeon is provided with many options during an operation in order to make the best decision for the patient and operation. However, after the devices (and other medical items) has left the manufacturer and before the devices reaches the operating area, middlemen such as distributors, sales representatives, and hospital central sterilization departments may be involved. The system may not foster reliable tracking and product control policies for these middlemen, often leading to shrinkage, wastage, loss, and increased expense for the manufacturer and/or medical facility.
Current FDA/EU regulations require more specific identification of implants to allow better tracking for patient safety and for outcome evaluation. In a tray with hundreds of implants intended for steam sterilization repetitively, this may become obtrusive and unworkable in current systems.
One embodiment of the present disclosure relates to a virtual tray system. The virtual tray system includes a tray inventory system configured to track a current inventory of a tray, the inventory including a plurality of items, and further configured to associate one or more details specified for each item in the tray. The virtual tray system further includes a database configured to store the current inventory of the tray. The virtual tray system further includes a user interface system configured to generate a visual representation of the inventory of the tray for display on a user interface of a user device. The virtual tray system further includes a communications system configured to receive an input relating to a change in status of at least one of the plurality of items in the tray. Based on the input, the tray inventory system is configured to update the current inventory of the tray in the database, and the user interface system is configured to update the visual representation of the tray based on the input.
Another embodiment of the present disclosure relates to a method. The method includes receiving from a manufacturer, by a virtual tray system, tray inventory information for a tray, wherein the inventory information includes one or more details for a plurality of items in the tray. The method further includes storing, by the virtual tray system, the tray inventory information in a database. The method further includes receiving, by the virtual tray system, updated tray inventory information from a distributor that received the tray from the manufacturer and updating, by the virtual tray system, the tray inventory information in the database. The method further includes receiving, by the virtual tray system, updated tray inventory information from a medical facility that received the tray from the distributor and updating, by the virtual tray system, the tray inventory information in the database. The method further includes receiving an input relating to a change in status of at least one of the plurality of items in the tray during a medical procedure and updating, by the virtual tray system, the tray inventory information in the database.
Another embodiment of the present disclosure relates to a method. The method includes receiving, at a virtual tray system from a monitoring system, an indication of the use of an item in a tray. The method further includes updating, by the virtual tray system, an inventory of the tray based on the use of the item. The method further includes updating, by the virtual tray system, a database configured to store the current inventory of the tray. The method further includes updating, by the virtual tray system, a visual representation of the tray for display on a user device.
The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:
Referring generally to the figures, systems and methods for providing a user friendly interface for tracking devices and instruments are shown. The interface provides a way for tracking devices and instruments in a tray from the time the tray leaves the manufacturer to the time the devices and instruments are used. The interface allows for reliable tracking of unique device identifier information (UDI) and for simplification of every transaction involving the devices and instruments.
In the present disclosure, the interface is described with reference to bulk packaged steam sterilized devices. Such devices may be packed into a tray at the manufacturer and shipped out. In other embodiments, the systems and methods herein may be adapted to be implemented with medical implants, or devices and instruments packaged or sterilized in any other way. Further, while the present disclosure describes the implementation of the interface in a medical setting, it should be understood that the systems and methods described herein may be implementable for any type of devices in any type of setting.
Referring to
The virtual tray 100 design shown is an example design that may be presented on a user interface to a user (e.g., a surgeon, manufacturer, distributor, etc.). In one embodiment, virtual tray 100 may look similar to the actual tray. Virtual tray 100 may be any two-dimensional or three-dimensional view illustrating the actual tray and the contents of the tray, and may be of any other design or type without departing from the scope of the present disclosure. Virtual tray 100, in various embodiments, may be shown from any angle, may be configured to rotate or provide different views, etc. As shown in
Virtual tray 100 may include visual representations for any number of items 102 in the actual tray. In the example of
Unique device identifier (UDI) information may be associated with each item in virtual tray 100 and may be presented in various ways on the actual items. For example, items may be color coded, or have individual patterns or illustrations recognizable by optical character recognition (OCR), a barcode, or other methods. The UDI information may include an item or lot number specific to the item.
Referring to
In the embodiment of
Virtual tray 100 may be displayed on one or more displays 206 and/or devices 208. This allows virtual tray 100 to be available to one or more personnel 202 in operating room 200 during an operation. Each individual may have a unique ID associated with him or her, allowing specific interactions with virtual tray 100 as described below.
In some embodiments, when personnel interacts with an actual tray 104 of items in operating room 200 (or elsewhere between the manufacturer and the operating room in other embodiments), an interaction involving virtual tray 100 and displays 206/device 208 may be initiated. For example, when a user touches or removes an item in tray 104, or selects an item via display 206/device 208, specific information relating to the item may be accessed on the virtual tray (i.e., displayed on the display/device of the surgeon). As another example, touching or removing an item from tray 104 may cause the item to be added to a bill of materials or invoice that charges the medical facility for use of the item. As another example, upon use of an item in tray 104, the tray inventory may be updated. Tray 104 may generally include a monitoring system and/or one or more monitoring devices for detecting the use of an item, may include an interface for allowing personnel 202 to identify an item being used, or may detect the usage of an item in any other way. The management of the various interactions with tray 104 is described in greater detail below.
Operating room 200 may include a monitoring system 210 which may be implemented either in a computing device located in operating room 200 or remotely from operating room 200. Monitoring system 210 may monitor the activity in operating room 200. For example, monitoring system 210 may monitor the use of one or more medical devices, such as items from tray 104, during an operation. Monitoring system 210 may be used in conjunction with or instead of a monitoring system of tray 104 for detecting the use of one or more items in the tray. Monitoring system 210 may be connected to a plurality of devices, such as cameras 212, RFID readers 214, or other devices, configured to detect the usage of items in tray 104. For example, one or more items may have a RFID tag attached to it that is detectable by RFID reader 214. Monitoring system 210, cameras 212, RFID reader 214, and other monitoring devices and methods may further be used in operating room 200 for other functionality not related to the use of items in tray 104.
Referring now to
Referring generally to the disclosure, activities described as being executed by virtual tray system 300 may generally include activities executed by the individual modules and databases as described below. The term “virtual tray system” is used to describe the collective activities of the modules and databases, and it should be understood that such activities may be executed by any number of individual modules and databases.
In some embodiments, virtual tray system 300, and more particularly the modules and databases shown, may be implemented at a single server, at one or more servers, or at any number of other devices within “the cloud”. Virtual tray system 300 is shown to generally include an API/communication layer 320 configured to facilitate communications between the modules and databases and the various users and devices attempting to access a virtual tray. Virtual tray system 300 is further shown to include a security/firewall layer 322 configured to secure the communications between the modules and databases and the users and devices. Layers 320, 322 may be configured to receive communications directly from the users and devices, or the users may communicate with the modules and databases via a web interface 324 that allows a user to enter information about a tray.
It should be understood that the architecture described herein is provided by way of example only, and that virtual tray system 300 may be implemented in various ways. In the cloud-based embodiment of
Each module of virtual tray system 300 may be implemented by any number of servers, virtual machines, devices, etc. Different modules may be implemented at the same server or machine or different servers or machines. Each server or machine may generally include a processing circuit including a processor and memory to execute the activities of the module. The processor may be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components. The memory is one or more devices (e.g., RAM, ROM, flash memory, hard disk storage, etc.) for storing data and/or computer code for completing and/or facilitating the various user or client processes, layers, and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory. The memory may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures of the present disclosure. The memory is communicably connected to the processor and includes computer code or instruction modules for executing one or more processes described herein.
An inventory module 310 is configured to track the inventory of an actual tray, for the virtual tray generated by virtual tray system 300. An individual tray may include a unique identifier for the tray along with a unique identifier of each item in the tray. Inventory module 310 may be configured to maintain an inventory of each tray (using the tray unique identifier), and more particularly a quantity of each item available in the tray. Inventory module 310 may receive an input from any of manufacturer 340, distributor 342, sales representative 344, or a user in medical facility 346 regarding a change in status of the tray (e.g., the addition or removal of an item), and may update the inventory of the virtual tray in real-time or near real-time. In various embodiments, virtual tray system 300 and inventory module 310 may track any number of trays from any number of manufacturers. In some embodiments, inventory module 310 may maintain an inventory database 330 for storing tray inventory information for the plurality of trays.
In some embodiments, tray inventory module 310 updates an inventory of a tray based on an input from a manufacturer 340. At manufacturer 340, a tray may be prepared and sent out to a distributor. The tray may be prepared based on an order from a medical facility or personnel, prepared for a specific operation with a patient or a specific type of operation, or may be a tray generally prepared by manufacturer 340 for general use. Manufacturer 340 may place a plurality of items in the tray, such as one or more implants to be inserted into a patient during an operation, one or more tools for use during the operation, and other devices. Each item placed in the tray may be recorded by manufacturer 340 to allow the item to be identified by tray inventory module 310. For example, each item may be associated with a unique device identifier that can be detected by another user or device. The unique device identifier may be a numerical value, a name, a visual indicia (e.g., color coding or an image), etc. Therefore, when the item is used, it can be decremented from the inventory of the tray. Further, each item may be assigned a particular location or storage method within the tray.
In some embodiments, manufacturer 340 may attach specific content to each item. For example, the content may be instructions for using the item, warnings or contraindications associated with the item, an expiration date of the item, a date of manufacture of the item, a fatigue life of the item, or any other useful information. The information is associated with each item via the item identifier. Further, each item is associated with the tray in which it is housed.
Tray inventory module 310 may receive input from manufacturer 340 regarding the contents of a tray, as the manufacturer is setting up the tray or after. In some embodiments, manufacturer 340 may scan identifiers for each individual item to be placed in the tray, and the device scanning the items may relay the information to tray inventory module 310. In some embodiments, the tray may include one or more sensors or devices for tracking the items placed within the tray, and such information may be provided via the sensors or devices to tray inventory module 310.
In some embodiments, tray inventory module 310 updates an inventory of a tray based on an input from a distributor 342. Distributor 342 may receive a tray from manufacturer 340, and be generally responsible for distributing (e.g., selling) trays to a plurality of medical facilities 346, restocking trays, and the like. At distributor 342, for example, implants in the tray may be repopulated with devices shipped from manufacturer 340. In some embodiments, the unique information associated with the items may already be associated with a specific tray location by manufacturer 340 and may be confirmed by distributor 342. In other embodiments, the unique information associated with the items may be assigned a specific tray location at distributor 342. In such embodiments, distributor 342 may provide tray location data for each item to tray inventory module 310 in order to keep the virtual tray up to date.
In some embodiments, tray inventory module 310 updates an inventory of a tray based on an input from a user at medical facility 346 (or other central receiving or supply department that receives a tray for use in an operating room at the medical facility). At medical facility 346, the actual tray may be received and compared to the virtual tray (which is accessible through an online user interface as described below) in order to confirm the inventory in the tray and record deficiencies (i.e., identify broken or missing items). Personnel at medical facility 346 may further verify product usage after an operation, as described below.
In some embodiments, at medical facility 346, it is a large facility with many consigned products. Therefore, the tray at medical facility 346 may be accessed by users such as sales representatives 344 (selling items and other devices to the institution) and facility employees. In some embodiments, tray inventory module 310 may be configured to receive an input when a sales representative 344 repopulates the tray in concert with the manufacturer and distributor. For example, the medical facility may order additional items through sales representative 344 from a manufacturer and distributor to be placed in the tray. Tray inventory module 310 receives an indication of the transaction and updates the inventory of the tray in response.
In some embodiments, tray inventory module 310 updates an inventory of a tray based on an input from a device 208 in an operating room 200. Virtual tray system 300 provides a virtual tray for display on a screen in operating room 200 (as described by display module 316 below). The virtual tray may be accessible to any personnel in the operating room (e.g., a scrub tech, circulating nurse, sales representative, etc.) via a device 208. The personnel can use device 208 to access information related to the tray and the items in the tray. Tray inventory module 310 may receive input from the devices in operating room 200 relating to an interaction with the tray. This input may be from personnel or detected by a camera 212 or sensor 214. For example, a sensor on the tray may detect the removal of an implant from the tray and relay the information (through device 208) to tray inventory module 310, which may then update the inventory of the tray accordingly.
In one embodiment, the input received by tray inventory module 310 may be from a RFID reader 214. RFID reader 214 may generally be configured to detect the use of an item in the tray by reading a RFID tag that is coupled to the item. RFID reader 214 may detect when the item is being moved, and to associate the movement with usage of the item. Tray inventory module 310 may receive the detection by RFID reader 214 and update the virtual tray accordingly.
Each person accessing the virtual tray via virtual tray system 300 may have a unique ID associated with him or her. A user ID module 312 may be configured to manage user interactions with the virtual tray system based on the user ID. Each person may generally have a unique ID (or other more general identifier) that identifies the user to user ID module 312. User ID module 312 may allow different levels of interactions, or specific interactions, with the virtual tray depending on the user ID. For example, some users (e.g., surgeons) may be able to access information relating to the use of an implant or tool during a surgical procedure. The surgeon may be able to touch a touchscreen displaying the virtual tool in order to view specific information or diagrams. As another example, some users (e.g., sales representatives) may be able to access information relating to the available inventory or stock of an item that the user wants to sell to the hospital, via the virtual tray. As yet another example, a surgeon may be able to access patient data via patient database 334 during an operation or before the operation, preparing for the operation.
In some embodiments, user ID module 312 may track access of the virtual tray by the various users. For example, user ID module 312 may be configured to store a history of who interacted with the virtual tray, who removed or added items to the virtual tray, and so forth. This information may be stored in inventory database 330 (allowing tray history data to be stored with other tray information), assets database 332, or may be stored in another local or remote database or data store.
In some embodiments, a user may touch or remove an item from the tray in operating room 200. The interaction with the item may be detected by a camera, sensor, or the tray, and sent to tray inventory module 310. In other embodiments, a user can indicate use of an item through the user interface (described below). In response, a bill of materials may be generated for the use of the item in a surgical procedure. For example, if an implant was removed, an invoice charging the medical facility for the use of the implant in a procedure may be generated. A billing module 314 is shown for facilitating such a transaction relating to the use of the item. In some embodiments, billing module 314 may automatically generate a purchase order and sales invoice in response to the use of an item with a particular UDI. Billing module 314 may generate the bill of materials in conjunction with user ID module 312 (e.g., user ID module 312 may identify the personnel using the item in question and may determine whom to charge for use of the item and which manufacturer to provide the revenue). Billing module 314 may be configured to generate an invoice in real time (e.g., creating the invoice as tray inventory module 310 receives indication of the use of the item, and as the virtual tray is updated), or may generate an invoice on a schedule or when requested (e.g., by a user, the medical facility, etc.).
A transaction initiated by billing module 314 may require more than one person or entity to confirm. For example, the use of the item in a procedure may be confirmed by personnel in operating room 200 after detection of the use of the item. Billing module 314 may work in conjunction with the other modules of virtual tray system 300 to verify the use of the item and whom to charge for the usage.
A display module 316 may generally be configured to generate the visual tray for display on a device. Display module 316 may generate an image (e.g., an avatar) used to represent each item of a tray. For example, referring again to
Virtual tray system 300 is shown to include a reporting module 318. During an operation at medical facility 346, one or more items of a tray may be used. Reporting module 318 may be configured to generate a report detailing the usage of the one or more items, and to associate the items with a particular patient, case, or operation as a result. This may allow virtual tray system 300 to generally track and provide information relating to the usage of a particular item. Such information may be stored in a database 330, 332, or 334.
Virtual tray system 300 is shown to include an inventory database 330, assets database 332, and patient database 334. In various embodiments, virtual tray system 300 may include any number of databases storing information relevant to the virtual trays. Inventory database 330 may generally store inventory information for each tray. Assets database 332 may generally store information regarding assets available to the personnel in the trays at the medical facility. Patient database 334 may generally store information for each patient, such as a procedure to be performed on the patient and the trays and items necessary for the procedure. For example, using patient database 334, a surgeon (or other personnel) may access all information needed for a procedure, including the one or more trays and items therein that are needed for the procedure.
In some embodiments, virtual tray system 300 may facilitate communications between personnel, distributors, and manufacturers based on the tray. For example, comments relating to the tray or the items therein may be provided by surgical personnel to be provided to the manufacturer, distributor, a central supply station, or a regulatory agency. The comments may generally relate to problems or questions related to the items in the tray. This may allow the surgical personnel to access and/or provide information that results in a corrective or preventative action.
In some embodiments, virtual tray system 300 may portray multiple virtual trays from different manufacturers on one or more screens, or may display virtual trays specific to a facility. The various virtual trays may be used to gather information from surgical personnel, the health care institution, or another end user that may be used by the manufacturer to set up the tray. The various virtual trays may further be presented when the medical facility or other end user is ordering a tray. Further, virtual tray system 300 may facilitate communications between the medical facility and manufacturer (or other users) during a transaction, allowing the manufacturer to customize the tray (i.e., provide appropriate items in the tray, provide items for a specific procedure or patient, etc.) for the facility. The display of one or more virtual trays by virtual tray system 300 may facilitate such a process, allowing the end user to access any information from the manufacturer regarding the tray or from virtual tray system 300 (e.g., information stored in inventory database 330).
In some embodiments, virtual tray system 300 may allow a virtual tray to be accessible to an online specialist. For example, during a surgical procedure, a surgeon or other personnel may select an item and ask for assistance related to the item. The personal may then be put in contact with an online specialist remotely located from the operating room, who is identified as being able to assist based on the item. The virtual tray may be accessible to the online specialist, allowing the specialist to assist in the surgical procedure.
In some embodiments, virtual tray system 300 may provide a training virtual tray for training for personnel at a medical facility. The training tray may be used to familiarize personnel with the devices, implants, and other items in the virtual tray, and to provide information relating to a procedure associated with the devices and implants. Virtual tray system 300 may include a database or other data store (or be connected to the database or other data store) storing such information, or may retrieve the information from inventory database 330.
Referring now to
The actual tray is provided by distributor 342 to a medical facility 346 (e.g., a hospital). Upon receiving the tray, medical facility 346 may compare the actual tray to the virtual tray (provided by virtual tray system 300) to confirm the inventory. The actual tray may be moved to an operating room 200 in which the items of the tray will be used. Upon detection of usage of an item in the tray, an indication may be sent to virtual tray system 300, and the virtual tray may be updated accordingly. Further, virtual tray system 300 may provide notification (via changing the virtual tray) of the change to manufacturer 340, distributor 342, and medical facility 346.
Process 500 further includes updating a virtual tray associated with the tray in the operating room (block 506). For example, block 506 may include removing an icon associated with the item in the virtual tray display. Process 500 further includes updating an tray database configured to store the current inventory of the tray (block 508).
In some embodiments, process 500 includes generating a purchase order for use of the item (block 510). In other words, the personnel or the health care institution in which the operating room is located may be charged for use of the item. Process 500 further includes notifying a manufacturer of the tray and/or the item of the use of the item (block 512). This may cause the manufacturer to receive payment for use of the item, alert the manufacturer or other user to provide a replacement item, or otherwise.
Referring now generally to
Referring to
User interface 600 may generally include a first portion 610 or section in which the multiple trays available to a user are shown. The user may select a tray to cause a second portion 612 of the display to show the selected tray 604. User interface 600 also includes a third portion 614 in which, in the example of
Referring to user interface 700 of
Referring to user interface 800 of
Referring now to user interface 900 of
Referring to user interface 1000 of
As shown in user interface 1000, two additional items 1012, 1014 are selected and highlighted in list 1004 and in the virtual tray. In the example of
Referring now to user interface 1100 of
The user interfaces of
Referring generally to
Referring to user interface 1200 of
Referring to user interface 1300 of
Referring generally to
Referring to user interface 1500 of
Further, fields 1506, 1508 may be updated based on the instructions displayed. For example, for a set of instructions, fields 1506 are updated to show the total number of devices needed to follow the particular step, and the number of devices used or damaged among such devices. Further, in fields 1508, the user can mark other items as used or damaged as they are used while following the instructions.
Referring to user interface 1600 of
Referring now to user interface 1800 of
User interface 1800 is shown to further include fields 1816, 1818 for listing the step and listing the related devices for the step (e.g., the items to be used during the step). User interface 1800 may be configured to present such information upon selection of the step by a user, or may automatically present the information when the user indicates to the virtual tray system that he/she has reached the step.
Referring generally to
Referring to user interface 1900 of
The virtual tray system in some embodiments provides an administrative console through which a user, can log into the system or can access information related to another user of the system. In one embodiment, the user may cause a user interface such as user interface 2100 of
The user may further use the virtual tray system user interface to access other information. For example, the user may be able to browse a list of cases (described below in
Referring now to user interface 2200 of
User interface 2200 may include an option 2202 to go to the virtual tray to be used, and an option 2204 to view a bill of materials for items used so far. The user may further select an option 2206 to view the case history (e.g., items and trays used in the past) or an option 2208 to close the case. In some embodiments, closing the case may generate an invoice for the personnel or medical facility.
The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, networked systems or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can include RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions. The machine-executable instructions may be executed on any type of computing device (e.g., computer, laptop, etc.) or may be embedded on any type of electronic device (e.g., a portable storage device such as a flash drive, etc.).
Although the figures may show a specific order of method steps, the order of the steps may differ from what is depicted. Also, two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.
This application claims the benefit of and priority to U.S. Provisional Application No. 62/236,724, filed Oct. 2, 2015, which is incorporated herein by reference in its entirety.
Number | Date | Country | |
---|---|---|---|
62236724 | Oct 2015 | US |