A system for management of a medical equipment and a method thereof

Abstract

A system (100) for management of a medical equipment is disclosed A ticketing module (120) receives a ticket via a user interface raised by a first user in response to a failure of the medical equipment. Further, the verification module (130) allows a second user to scan a quick response code embedded on the medical equipment and renders an image of the medical equipment in response to retrieving data of the medical equipment from a database (135). Further, a mapping module (140) maps a workflow with the verified medical equipment using an artificial intelligence model. Furthermore, a processing module (150) guides the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment. Moreover, the processing module enables the third user to guide the second user in real-time if the medical equipment is not listed in the database thereby resolving the ticket.

Description

[0001]A SYSTEM FOR MANAGEMENT OF A MEDICAL EQUIPMENT AND A METHOD THEREOF EARLIEST PRIORITY DATE This Application claims priority from a Complete patent application filed in India having Patent Application No.202441044306 filed on 07th day of June 2024 and A SYSTEM FOR MANAGEMENT OF A MEDICAL EQUIPMENT AND A METHOD THEREOF FIELD OF INVENTION Embodiments of the present disclosure relate to the field of medical equipment management, and more particularly, a system for management of a medical equipment and a method thereof. BACKGROUND Medical equipment management (MEM) is a systematic management of a medical equipment’s life cycle in a healthcare center to maximize performance and minimize risk of the medical equipment. Further, the medical equipment management involves selecting and acquiring the medical equipment. installation and calibration, and maintaining accurate inventory records, conducting regular preventive maintenance and repair. Currently, medical staff reports faulty medical equipment to a management department responsible for maintenance, typically through phone calls, leading to potential delays and miscommunication. Subsequently, when a maintenance engineer arrives, handling the medical equipment is time-consuming and error prone. The maintenance engineer then determines if the medical equipment is within a manufacturer's warranty period; if so, the manufacturer engineer handles repairs, but after the warranty expires, the medical staff must rely on external maintenance companies, causing further delays and inconsistencies in the repair quality, impacting patient care and operational efficiency. Further, the maintenance information is recorded on a paper, resulting in inefficient record-keeping and difficulties in tracking the medical equipment maintenance data. Additionally, the medical staff often lack knowledge and training to perform repairs on the medical equipment, leading to significant drawbacks. Without proper expertise, the medical staff cannot accurately diagnose or fix issues, resulting in prolonged the medical equipment downtime. Hence, there is a need for an improved system for management of a medical equipment which addresses the aforementioned issue(s). OBJECTIVE OF THE INVENTION An objective of the invention is to enable a second user (engineer) to resolve a ticket raised by a first user (operator) in occurrence of failure of a medical equipment though voice-enabled video assistance. Another objective of the invention is to resolve the ticket by enabling a third user (technical team) to guide the second user in real-time via a sequence of instructions if the medical equipment is not listed in the database. BRIEF DESCRIPTION In accordance with an embodiment of the present disclosure, a system for management of a medical equipment is provided. The system includes a processing subsystem hosted on a server. The processing subsystem is configured to execute on a network to control bidirectional communications among a plurality of modules. The processing subsystem includes a ticketing module configured to receive a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment. Further, the processing subsystem includes a verification module operatively coupled to the ticketing module wherein the verification module is configured to allow a second user to scan a quick response code embedded on the medical equipment. Further, the verification module is configured to render an image of the medical equipment in response to retrieving data of the medical equipment from a database. Furthermore, the verification module is also configured to enable the second user to verify the image of the medical equipment thereby indicating successful verification. Moreover, the verification module is configured to allow the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database. Further, the processing subsystem includes a mapping module operatively coupled to the verification module wherein the mapping module is configured to map a workflow with the verified medical equipment using an artificial intelligence model, wherein the workflow includes a sequence of instructions designed specifically to resolve the ticket. Furthermore, the processing subsystem includes a processing module operatively coupled to the mapping module wherein the processing module is configured to guide the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment. Furthermore, the processing module is also configured to enable the third user to guide the second user in real-time if the medical equipment is not listed in the database thereby resolving the ticket. In accordance with another embodiment of the present disclosure, a method for management of a medical equipment is provided. The method includes receiving, by a ticketing module, a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment. The method also includes allowing, by a verification module, a second user to scan a quick response code embedded on the medical equipment. Further, the method incudes rendering, by the verification module, an image of the medical equipment in response to retrieving data of the medical equipment from a database. Furthermore, the method includes enabling, by the verification module, the second user to verify the image of the medical equipment thereby indicating successful verification. Moreover, the method includes allowing, by the verification module, the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database. Additionally, the method includes mapping, by a mapping module, a workflow with the verified medical equipment using an artificial intelligence model, wherein the workflow includes a sequence of instructions designed specifically to resolve the ticket. In addition, the method includes guiding, by a processing module, the second user via the sequence of instructions through a voice- enabled video assistance with respect to the medical equipment. Besides, the processing subsystem also includes enabling, by the processing module, the third user to guide the second user in real-time if the medical equipment is not listed in the database thereby resolving the ticket. To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures. BRIEF DESCRIPTION OF THE DRAWINGS The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which: FIG. 1 is a block diagram representation of a system for management of a medical equipment in accordance with an embodiment of the present disclosure; FIG.2 is a block diagram representation of an exemplary embodiment of the system for management of a medical equipment of FIG.1 in accordance with an embodiment of the present disclosure; FIG.3 illustrates a flowchart representing an exemplary process of resolving a ticket of a medical equipment in accordance with an embodiment of the present disclosure; FIG.4 is a block diagram of a computer or a server in accordance with an embodiment of the present disclosure; FIG. 5(a) illustrates a flow chart representing the steps involved in a method for management of a medical equipment in accordance with an embodiment of the present disclosure; and FIG.5(b) illustrates continued steps of the method of FIG.5(a) in accordance with an embodiment of the present disclosure. Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein. DETAILED DESCRIPTION For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure. The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting. In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise. Embodiments of the present disclosure relates to system for management of a medical equipment. The processing subsystem is configured to execute on a network to control bidirectional communications among a plurality of modules. The processing subsystem includes a ticketing module configured to receive a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment. Further, the processing subsystem includes a verification module operatively coupled to the ticketing module wherein the verification module is configured to allow a second user to scan a quick response code embedded on the medical equipment. Further, the verification module is configured to render an image of the medical equipment in response to retrieving data of the medical equipment from a database. Furthermore, the verification module is also configured to enable the second user to verify the image of the medical equipment thereby indicating successful verification. Moreover, the verification module is configured to allow the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database. Further, the processing subsystem includes a mapping module operatively coupled to the verification module wherein the mapping module is configured to map a workflow with the verified medical equipment using an artificial intelligence model, wherein the workflow includes a sequence of instructions designed specifically to resolve the ticket. Furthermore, the processing subsystem includes a processing module operatively coupled to the mapping module wherein the processing module is configured to guide the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment. Furthermore, the processing module is also configured to enable the third user to guide the second user in real-time if the medical equipment is not listed in the database thereby resolving the ticket. In the following discussion, references are made to a ‘first user’, ‘second user’ and ‘third user’ to differentiate the role of the said individuals. Specifically, the ‘first user’ refers to an operator of a medical instrument, the ‘second user’ refers to a technical engineer / maintenance engineer and the ‘third user’ refers to a technical team. FIG. 1 is a block diagram representation of a system for management of a medical equipment in accordance with an embodiment of the present disclosure. The system (100) includes a processing subsystem (105) hosted on a server (108). In one embodiment, the server (108) may include a cloud-based server. In another embodiment, parts of the server (108) may be a local server coupled to a user device (not shown in FIG.1). The processing subsystem (105) is configured to execute on a network (115) to control bidirectional communications among a plurality of modules. In one example, the network (115) may be a private or public local area network (LAN) or Wide Area Network (WAN), such as the Internet. In another embodiment, the network (115) may include both wired and wireless communications according to one or more standards and / or via one or more transport mediums. In one example, the network (115) may include wireless communications according to one of the 802.11 or Bluetooth specification sets, or another standard or proprietary wireless communication protocol. In yet another embodiment, the network (115) may also include communications over a terrestrial cellular network, including, a global system for mobile communications (GSM), code division multiple access (CDMA), and / or enhanced data for global evolution (EDGE) network. The processing subsystem (105) includes a ticketing module (120), a verification module (130), a mapping module (140), and a processing module (150). The ticketing module (120) is configured to receive a ticket via a user interface raised by a first user in response to a failure of the medical equipment. The first user is an operator of the medical equipment. Typically, in a medical Center, a wide range of the medical equipment is necessary for a patient care, diagnosis, and treatment of the patient. The medical equipment includes, but is not limited to, Magnetic Resonance Imaging (MRI) scanners, ultrasound machines, electrocardiogram (ECG) monitors and blood pressure cuffs, all of which are essential for a medical staff for assessing the patient health. Further, when the medical equipment fails, a ticket is initiated by the first user. For instance, consider a nurse in an intensive care unit notice that a patient monitor is not displaying vital signs correctly. The nurse accesses the ticketing module (120) through a computer or mobile device, enters the necessary details about the malfunction, and submits the ticket. The maintenance team receives a notification and can quickly address the issue to restore the monitor's functionality. In one embodiment, the first user access servicing the medical equipment on a subscription basis. The medical staff pays a fee annually or monthly basis for the medical equipment maintenance. For example, the medical staff may subscribe to an annual package. The annual package includes but is not limited to regular maintenance of the medical equipment, sudden failure of the medical equipment. Further, a verification module (130) is operatively coupled to the ticketing module. The verification module (130) is configured to allow a second user to scan a quick response code embedded on the medical equipment. Typically, the second user is a maintenance engineer. Further, the QR code is a two-dimensional barcode that stores information about the medical equipment. In one embodiment, the QR code stores maintenance history of the medical equipment, service contract, and user manuals. Further, the verification module (130) is also configured to render an image of the medical equipment in response to retrieving data of the medical equipment from a database (135). Typically, the database (135) stores the data of the medical equipment and a corresponding identification number of the medical equipment. Furthermore, the verification module (130) is configured to enable the second user to verify the image of the medical equipment thereby indicating successful verification. Moreover, the verification module (130) is configured to allow the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database (135). Typically, the second user uploads the image of the medical equipment if the database (135) fails to display the medical equipment and simultaneously the second user contacts the third user, thereby resolving the ticket with guidance of the third user through sequence of instructions. Further, the second user records a video when examining the medical equipment for future reference and training by utilizing a suitable artificial intelligence model. Typically, the artificial intelligence model is utilized to analyze the video and extract information from the video. Further, the artificial intelligence model identifies patterns within the video providing valuable features for the reference and training purposes. In one embodiment, natural language processing (NLP) techniques may be employed to transcribe and annotate the video content, making it more accessible and searchable for the future reference. Furthermore, the mapping module (140) is operatively coupled to the verification module (130). The mapping module (140) is configured to map a workflow with verified medical equipment using the artificial intelligence model. The workflow includes a sequence of instructions designed specifically to resolve the ticket. For example, the sequence of instructions includes, but is not limited to check the power connection and monitor connection, fuse connection, and replace components in the medical equipment if necessary. Moreover, the processing module (150) is operatively coupled to the mapping module (140). The processing module (150) is configured to guide the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment. Typically, the voice-enabled video assistance combines the capabilities of voice recognition technology with live or recorded video streams to provide interactive guidance to the second user or support in real-time when the medical equipment fails. Further, the processing module (150) is configured to enable the third user to guide the second user in real-time if the medical equipment is not listed in the database (135) thereby resolving the ticket. Typically, the third user is a technician or a subject matter expert who possesses extensive knowledge about various medical equipment and troubleshooting procedures. The third user guides the second user via communication tools. The communication tools include, but is not limited to voice call, video call, text, and direct communication. FIG. 2 is a block diagram of an exemplary embodiment of the system for building a brand and managing a corresponding supply chain of FIG. 1 in accordance with an embodiment of the present disclosure. The processing subsystem (105) includes a workflow document module (160) operatively coupled to the processing module (150). The workflow document module (160) is configured to provide an outline of the sequence of instructions from powering the medical equipment to handover the medical equipment in working condition, ensuring a comprehensive and efficient process. Typically, the workflow document module (160) provides end-to-end troubleshooting procedure for the medical equipment through the sequence of instructions. The troubleshooting procedure includes, but is not limited to initial setup, calibration procedures, system checks, and safety protocols. In an example, consider a scenario, where first user ‘X’ is the medical staff responsible for operating the medical equipment, such as an ECG. If the medical equipment (245) malfunctions, the first user ‘X’ raises the ticket through a mobile device (235). Further, the second user ‘Y’ is a biomedical engineer or a maintenance technician or a maintenance engineer tasked with verifying and resolving the medical equipment (235) issues. Furthermore, the second user ‘Y’ scans the QR code on the ECG, which triggers the system (100) to retrieve data about the medical equipment (235) from the database (135). If the data is found, the verification module (130) renders an image of the medical equipment (235), and the second user ‘Y’ verifies its accuracy. However, if the medical equipment (235) isn't listed, the second user escalates the issue to a third user ‘Z’, perhaps a manufacturer's representative or an experienced technician. Through real-time communication, the third user ’Z’ guides the second user ‘Y’ in resolving the ticket, utilizing their expertise and the aid of voice-enabled video assistance. Together, they navigate through troubleshooting steps tailored to the situation, ensuring the medical equipment is back in working order efficiently. FIG.3 illustrates a flowchart representing an exemplary process of resolving a ticket of a medical equipment in accordance with an embodiment of the present disclosure. The ticket regarding failure of the medical equipment is raised by the operator or first user within a medical center. The flowchart begins by scanning the QR code on the medical equipment in step 400. Further, the medical equipment is verified with a provided image in step 405. If the medical equipment is not found, then the image of the medical equipment is uploaded, and a technical team is contacted for corrections. Subsequently, the QR code is scanned again in step 410 and the process ends in step 415. Referring back to step 405, the medical equipment is checked for any physical damage in step 420. Further, an incident / damage and missing report of the medical equipment is prepared in step 425 and the process ends in step 430. Referring back to 410, the medical equipment is connected to a mains and ON status of the medical equipment is checked in step 435. Further, it is verified if the medical equipment is powered ON while display of the medical equipment is OFF in step 440. Furthermore, display board of the medical equipment is verified for necessary voltage in step 445. Moreover, the display of the medical equipment is replaced in step 450. Referring back to 440, the technical team is contacted through a video call for further assistance in step 455. Referring back to step 445, the technical team is contacted through video call for further assistance in step 455 and the process ends in step 480. Referring back to step 435, it is confirmed whether the voltage of wall outlet is 230 volts in step 460. Further, it is verified if the fuse was blown in step 465. The technical team is contacted through a video call for further assistance in step 455 and the process end in 480. Referring back to 460, the medical equipment is shifted to a place which has 230-volt wall supply in step 470. Further, the medical equipment is connected to the mains and ON status of the medical equipment is checked in step 435. Referring back to 465, the fuse is replaced with new fuse in step 475. Further, the medical equipment is connected to the mains and ON status of the medical equipment is checked in step 435. In this way, the ticket is resolved by a second user or the maintenance engineer. FIG.4 is a block diagram of a computer or a server in accordance with an embodiment of the present disclosure. The server (200) includes processor(s) (230), and memory (210) operatively coupled to the bus (220). The processor(s) (230), as used herein, means any type of computational circuit, such as, but not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a very long instruction word microprocessor, an explicitly parallel instruction computing microprocessor, a digital signal processor, or any other type of processing circuit, or a combination thereof. The memory (210) includes several subsystems stored in the form of executable program which instructs the processor (230) to perform the method steps illustrated in FIG. 1. The memory (210) includes a processing subsystem (105) of FIG.1. The processing subsystem (105) further has following modules a ticketing module (120), a verification module (130), a mapping module (140), and a processing module (150). The processing subsystem (105) includes a ticketing module (120) configured to receive a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment. Further, the processing subsystem (105) includes a verification module (130) operatively coupled to the ticketing module (120) wherein the verification module (130) is configured to allow a second user to scan a quick response code embedded on the medical equipment. Further, the verification module (130) is configured to render an image of the medical equipment in response to retrieving data of the medical equipment from a database (135). Furthermore, the verification module (130) is also configured to enable the second user to verify the image of the medical equipment thereby indicating successful verification. Moreover, the verification module (130) is configured to allow the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database (135). Further, the processing subsystem (105) includes a mapping module (140) operatively coupled to the verification module (130) wherein the mapping module (140) is configured to map a workflow with the verified medical equipment using an artificial intelligence model, wherein the workflow includes a sequence of instructions designed specifically to resolve the ticket. Furthermore, the processing subsystem (105) includes a processing module (150) operatively coupled to the mapping module (140) wherein the processing module (150) is configured to guide the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment. Furthermore, the processing module (150) is also configured to enable the third user to guide the second user in real-time if the medical equipment is not listed in the database (135) thereby resolving the ticket. The bus (220) as used herein refers to internal memory channels or computer network that is used to connect computer components and transfer data between them. The bus (220) includes a serial bus or a parallel bus, wherein the serial bus transmits data in bit- serial format and the parallel bus transmits data across multiple wires. The bus (220) as used herein, may include but not limited to, a system bus, an internal bus, an external bus, an expansion bus, a frontside bus, a backside bus, and the like. FIG.5 (a) illustrates a flow chart representing the steps involved in a method (300) for management of a medical equipment with an embodiment of the present disclosure. FIG.5 (b) illustrates continued steps of the method of FIG.5 (a) in accordance with an embodiment of the present disclosure. The method (300) includes receiving, by a ticketing module, a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment in step 310. The method (300) also includes allowing, by a verification module, a second user to scan a quick response code embedded on the medical equipment in step 320. Further, the method (300) includes rendering, by the verification module, an image of the medical equipment in response to retrieving data of the medical equipment from a database in step 330. In one embodiment, the database (135) stores the data of the medical equipment and a corresponding identification number of the medical equipment. Further, the method (300) also includes enabling, by the verification module, the second user to verify the image of the medical equipment thereby indicating successful verification in step 340. Furthermore, the method (300) includes allowing, by the verification module, the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database in step 350. In one embodiment, the verification module (130) is configured to allow the second user to upload the image of the medical equipment if the database (135) fails to display the medical equipment and simultaneously the second user contacts the third user to resolve the ticket. In another embodiment, the verification module (130) is configured to allow the second user to record a video when examining the medical equipment for future reference and training by utilizing an artificial intelligence technique. Moreover, the method (300) includes mapping, by a mapping module, a workflow with the verified medical equipment using an artificial intelligence model, wherein the workflow includes a sequence of instructions designed specifically to resolve the ticket in step 360. Additionally, the method (300) includes guiding, by a processing module, the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment in step 370. Moreover, the method (300) includes enabling, by the processing module, the third user to guide the second user in real-time if the medical equipment is not listed in the database thereby resolving the ticket in step 380. Various embodiments of system (100) for management of the medical equipment as described above provides various benefits in streamlining resolution process for the medical equipment failures and malfunctions. By allowing seamless communication and collaboration between the first user, second user and the third user, it facilitates swift identification and verification of the medical equipment issues. Further, the system (100) allows the second user to scan the QR code on the medical equipment and upload images expedites the verification process, thereby reducing manual data entry and minimizing delays. Additionally, integration of artificial intelligence into the mapping module (140) ensures that users receive sequence of instructions for resolving each unique issue, thereby optimizing efficiency and accuracy. Furthermore, utilization of the voice-enabled video assistance enhances communication and guidance, enabling the second user and the third user to troubleshoot effectively even in complex situations. The techniques described in this disclosure may be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the described techniques may be implemented within one or more processors, including one or more microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. The term “processor” or “processing subsystem” may generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry, or any other equivalent circuitry. A control unit including hardware may also perform one or more of the techniques of this disclosure. Such hardware, software, and firmware may be implemented within the same device or within separate devices to support the various techniques described in this disclosure. In addition, any of the described units, modules, or components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features as modules or units is intended to highlight different functional aspects and does not necessarily imply that such modules or units must be realized by separate hardware, firmware, or software components. Rather, functionality associated with one or more modules or units may be performed by separate hardware, firmware, or software components, or integrated within common or separate hardware, firmware, or software components. It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof. While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.

Claims

CLAIM:

1. A system (100) for management of a medical equipment comprising: a processing subsystem (105) hosted on a server (108) wherein the processing subsystem (105) is configured to execute on a network (115) to control bidirectional communications among a plurality of modules comprising: a ticketing module (120) configured to receive a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment; characterized in that, a verification module (130) operatively coupled to the ticketing module (120) wherein the verification module (130) is configured to: allow a second user to scan a quick response code embedded on the medical equipment; render an image of the medical equipment in response to retrieving data of the medical equipment from a database (135); enable the second user to verify the image of the medical equipment thereby indicating successful verification; and allow the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database (135); a mapping module (140) operatively coupled to the verification module (130) wherein the mapping module (140) is configured to map a workflow with the verified medical equipment using an artificial intelligence model, whereinthe workflow comprises a sequence of instructions designed specifically to resolve the ticket; a processing module (150) operatively coupled to the mapping module (140) wherein the processing module (150) is configured to: guide the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment; and enable the third user to guide the second user in real-time if the medical equipment is not listed in the database (135) thereby resolving the ticket.

2. The system (100) as claimed in claim 1, wherein the verification module (130) is configured to allow the second user to upload the image of the medical equipment if the database (135) fails to display the medical equipment and simultaneously the second user contacts the third user to resolve the ticket.

3. The system (100) as claimed in claim 1, wherein the verification module (130) is configured to allow the second user to record a video when examining the medical equipment for future reference and training by utilizing an artificial intelligence technique.

4. The system (100) as claimed in claim 1, wherein the database (135) stores the data of the medical equipment and a corresponding identification number of the medical equipment.

5. The system (100) as claimed in claim 1, comprising a workflow document module (160) operatively coupled to the processing module (150) wherein the workflow document module (160) is configured to provide an outline of the sequenceof instructions from powering the medical equipment to handover the medical equipment in working condition, ensuring a comprehensive and efficient process.

6. The system (100) as claimed in claim 1, wherein the first user access servicing the medical equipment on a subscription basis.

7. A method (300) for management of a medical equipment comprising: receiving, by a ticketing module, a ticket via a user interface raised by a first user in response to a failure of the medical equipment, wherein the first user is an operator of the medical equipment; (310) characterized in that, allowing, by a verification module, a second user to scan a quick response code embedded on the medical equipment; (320) rendering, by the verification module, an image of the medical equipment in response to retrieving data of the medical equipment from a database; (330) enabling, by the verification module, the second user to verify the image of the medical equipment thereby indicating successful verification; (340) allowing, by the verification module, the second user to contact a third user upon uploading the image of the medical equipment if data of the medical equipment is not found in the database; (350) mapping, by a mapping module, a workflow with the verified medical equipment using an artificial intelligence model, wherein the workflow comprises a sequence of instructions designed specifically to resolve the ticket; (360)guiding, by a processing module, the second user via the sequence of instructions through a voice-enabled video assistance with respect to the medical equipment; (370) and enabling, by the processing module, the third user to guide the second user in real-time if the medical equipment is not listed in the database thereby resolving the ticket. (380)

Images