Description:TECHNICAL FIELD
[0001] The present disclosure relates to the field of remote monitoring of performance of medical equipment, in particular, relates to remote tracking of oxygen concentrator and remote firmware up gradation for doctors and device manufactures to track and service.

BACKGROUND
[0002] The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[0003] In situation like severe pandemic, the demand for oxygen supplies has increased in the country. While a large population of people gasping for breath and queuing up outside hospital premises, there are also a significant number of infected individuals who are getting themselves treated at home, breathing with the help of oxygen concentrators.
[0004] Giving individual attention to the huge number of patients is impossible. But it is very necessary to monitor each and every patient with safe working of oxygen concentrators spread across a large city. Remotely monitoring and tracking of the critical parameters of oxygen concentrator which are connected to patients is very much necessary. Also, monitoring is necessary when oxygen concentrators fail to produce therapeutic levels of oxygen because of common problems involving the air-intake system, malfunctioning sieve-control valves, and contaminated sieve materials.
[0005] Hence, there is a need for an apparatus that enables collection of parameter data of oxygen concentrators in real time and thereby monitor the performance and other related functioning data of the oxygen concentrator to ensure smooth functioning, provide alerts in case of any performance issues or technical snags in the oxygen concentrator and fetches the GPS location and collects the operational data from oxygen concentrators.

OBJECTS OF THE PRESENT DISCLOSURE
[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0007] It is the principal object of the present disclosure to enable real-time monitoring of performance of Oxygen concentrators.
[0008] It is an object of the present disclosure to allow tracking of geographical location, performance information and critical data of the oxygen concentrators.
[0009] It is a further object of the present disclosure is to establish a continuous communicative coupling between the oxygen concentrators and a centralized server.
[0010] It is yet another object of the present disclosure to collect and store critical information and performance information of the oxygen concentrators in a database.
[0011] It is yet another object of the present disclosure to enable control of Oxygen concentrators from a remote location.
[0012] It is an object of the present disclosure to enable triggering of alerts on critical parameters going below pre-defined threshold values.
[0013] It is yet another object of the present disclosure to enable monitoring of health parameters of a patient in real-time from a remote location.
[0014] It is yet another object of the present disclosure enables provisioning of Over the Air firmware updating to the monitoring apparatus.
[0015] These and other objects of the present invention will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings.

SUMMARY
[0016] The present disclosure relates to the field of remote monitoring of performance of medical equipment and in particular, to remote tracking of performance and oxygen levels of oxygen concentrators in use by patients.
[0017] The present invention generally relates to electronic medical equipment that monitor the critical data/information of oxygen concentrator sensors and share its location to a remote server. The apparatus i.e., monitoring device/Succour-GeoTag device sits with oxygen concentrator to collect the critical data and share with the remote server using data network.
[0018] An aspect of the present disclosure pertains to a system for remotely tracking and monitoring operational status of one or more oxygen concentrators deployed across the geographical location, the system comprising a Succour-GeoTag operatively coupled with each of the one or more oxygen concentrators, one or more processors operatively coupled with a memory storing instructions which when executed enable the processor to: receive, at a server, a first set of data packets from the one or more oxygen concentrators, establish a communicative coupling between the one or more oxygen concentrators and the server such that responsive to receipt of the first set of data packets. The server is configured to receive, at regular pre-defined intervals, a second set of data packets from the oxygen concentrators and store the second set of data packets received at regular intervals within a database. The server then compares, by the processor, the received second set of data packets with a pre-defined threshold stored within the database. Based on the comparison, the server is configured to identify an operational status of the oxygen concentrator based on the received first set of data packets.
[0019] In an embodiment, the first set of data packets pertain to a geographical location information of the oxygen concentrator, an authentication information of the oxygen concentrator, a registration information to register an IP address through an LTE network.
[0020] In an embodiment, the second set of data packets received at regular intervals contains an operational performance metadata of the oxygen concentrator and the health metadata of the oxygen concentrator.
[0021] In an embodiment, the Succour-GeoTag can be operatively configured with the oxygen concentrators by a Universal Asynchronous Receiver Transmitter (UART) and said Succour-GeoTag is adapted to receive power from a battery.
[0022] In an embodiment, the operational performance metadata of the oxygen concentrator within the second set of data packets comprises any or a combination of oxygen concentrator ID, temperature, oxygen pressure, compressor current, compressor voltage, oxygen level, oxygen flow rate and total up time of oxygen concentrator.
[0023] In an embodiment, the authentication information of the oxygen concentrator is an oxygen concentrator id that can be pre-stored within the database at the server and fetched to compare the received authentication information from the oxygen concentrator and the oxygen concentrator id pre-stored at the database to obtain a positive verification of the oxygen concentrator.
[0024] In yet another embodiment, the server can be configured to analyze the received second set of data packets and generate a third set of data packets to be transmitted based on the received second set of data packets being deviant from the pre-defined threshold within the database.
[0025] In an embodiment, the one or more error codes are defined and stored within the oxygen concentrator, each of said error codes being specified for a particular deviance from the pre-defined threshold such that the server, responsive to receipt of specific error code generates the third set of data packets specific to the received error code.
[0026] In an embodiment, the server is configured to display on a map of the geographical location, through an interface, the co-ordinates of the oxygen concentrators based on the received location information from each of the Succour-GeoTag device.
[0027] In an embodiment, the battery of Succour-GeoTag device can be in low power mode. The oxygen concentrator can be operating in its configured state and provide operational parameters to the Succour-GeoTag attached to it via UART. The Succour-GeoTag in turn combines the data from oxygen concentrator, its own location coordinates and sends to the centralized server.
[0028] In an embodiment, the Succour-GeoTag device can be in low power mode at regular pre-defined intervals and on receipt of an alert signal, the Succour-GeoTag device configured to transmit the second set of data packets from the oxygen concentrators to the server.
[0029] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing FIG.s in which like numerals represent like components.

BRIEF DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that invention of such drawings includes the invention of electrical components, electronic components or circuitry commonly used to implement such components.
[0031] The nature and scope of the present invention will be better understood from the accompanying drawings, which are by way of illustration of a preferred embodiment and not by way of any sort of limitation. In the accompanying drawings: -
[0032] FIG. 1 is a network diagram illustrating the communication of oxygen concentrator with the server via Succour-GeoTag device in accordance with an embodiment of the present disclosure.
[0033] FIG. 2 illustrates architecture of the processing engine configured within the server in accordance with an embodiment of the present disclosure.
[0034] FIG. 3Aillustratesthearchitecture of a Succour-GeoTag installed at each oxygen concentrator in accordance with an embodiment of the present disclosure.
[0035] FIG.3B is a block diagram illustrating the signal flow and the communication protocol between the Succour-GeoTag and the oxygen concentrator and communication between Succour-GeoTag and server in accordance with an embodiment of the present disclosure.
[0036] FIG. 3C illustrates the overall system of fetching the data from the Oxygen concentrator by an authentic admin access of the critical information in accordance with an embodiment of the present disclosure.
[0037] FIG.4 illustrates the mapping of Succour-GeoTag medical equipment/oxygen concentrators on a display dash board associated with the server for easy monitoring of oxygen concentrators located in a large area in accordance with an embodiment of the present disclosure.
[0038] FIG. 5 illustrates an exemplary architecture of the computer system to implement the proposed system in accordance with embodiments of the present disclosure.
[0039] The foregoing shall be more apparent from the following more detailed description of the invention.

DETAILED DESCRIPTION
[0040] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0041] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth.
[0042] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0043] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0044] Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, steps may be performed by a combination of hardware, software, firmware and/or by human operators.
[0045] Embodiments of the present invention may be provided as a computer program product or mobile application, which may include a machine-readable storage medium tangibly embodying thereon instructions, which may be used to program a computer (or other electronic medical equipment) or mobile medical equipment, to perform a process. The machine-readable medium may include, but is not limited to, fixed (hard) drives, magnetic tape, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, PROMs, random access memories (RAMs), programmable read-only memories (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions (e.g., computer programming code, such as software or firmware).
[0046] Various methods described herein may be practiced by combining one or more machine-readable storage media containing the code according to the present invention with appropriate standard computer or mobile hardware, along with a computer application or Android or IOs application, to execute the code contained therein. An apparatus for practicing various embodiments of the present invention may involve one or more computers (or one or more processors within a single computer) and storage systems containing or having network access to computer program(s) coded in accordance with various methods described herein, and the method steps of the invention could be accomplished by modules, routines, subroutines, or subparts of a computer program product.
[0047] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0048] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0049] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0050] In all the figures, like reference numerals represent like features. Further, when in the following it is referred to “top portion”, “left inside”, “right inside”, “upward”, “downward”, “above” or “below”, “front”, “rear” and similar terms, this is strictly referring to an orientation with reference to the apparatus, where the base of the apparatus is horizontal and is at the bottom portion of the figures and the portion facing the reader in the diagrams is the front of the apparatus. Further, the number of components shown is exemplary and not restrictive and it is within the scope of the invention to vary the shape and size of the apparatus as well as the number of its components, without departing from the principle of the present invention.
[0051] While describing a particular figure, certain features have been also referred which are shown in some other figure. For the sake of convenience, the figure. Number is given for such features for understanding. Further, at the beginning only the structure of the apparatus is explained with reference to each figure. Thereafter, the functioning is explained separately and for that purpose the figures are again referred to highlighting on the functional part.
[0052] Referring now to FIG.1 that illustrates an exemplary architecture of the system 102is disclosed. According to a network implementation, the proposed system 102 (referred to as system 102, hereinafter) can facilitate a patient to connect with the system through the oxygen concentrator or other medical equipment in use by the patient. It may be understood that system 102 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a server, a network server, a cloud-based environment and the like. It may be appreciated that the system 102 may be accessed by multiple patients 104-1, 104-2…104-N (collectively referred to as patients 104, and individually referred to as the patient 104 hereinafter), through one or more medical equipment 106-1, 106-2…106-N (collectively referred to as patient medical equipment 106, or first medical equipment 106 and individually referred to as patient oxygen concentrator 106, or first oxygen concentrator 106 hereinafter), or applications residing on the patient medical equipment 106. The communication of oxygen concentrator 106and the server can be performed via Succour-GeoTag device (110-1 to 110-N (which are collectively referred to as Succour-GeoTag device 110, herein))
[0053] In an embodiment, the system 102 can be operatively coupled to a website and so be operable for monitoring from any Internet-enabled remote server. Examples of patient medical equipment 106, may include, but are not limited to, oxygen concentrator, health parameter monitoring equipment, blood pressure monitoring equipment, heart condition monitoring equipment, Breathing monitoring equipment and the like. The patient medical equipment106 can be communicatively coupled with system 102 and with each other through a network 108.
[0054] In one implementation, network 108 can be a wireless network, a wired network or a combination thereof. Network 108 can be implemented as one of the different types of networks, such as an intranet, local area network (LAN), wide area network (WAN), the internet, and the like. Further, network 108 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further, network 108 can include a variety of network medical equipment, including routers, bridges, servers, computing medical equipment, storage medical equipment, and the like. In another implementation the network 108 can be a cellular network or mobile communication network based on various technologies, including but not limited to, Global System for Mobile (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Long Term Evolution (LTE), WiMAX, and the like.
[0055] An aspect of the present disclosure pertains to the system for remotely tracking and monitoring operational status of one or more oxygen concentrators deployed in a geographical location, the system comprising a Succour-GeoTag operatively coupled with each of the one or more oxygen concentrators. In an embodiment, the Succour-GeoTag can be operatively configured with the Oxygen concentrators by a Universal Asynchronous Receiver Transmitter (UART) and said Succour-GeoTag is adapted to receive power from a battery.
[0056] The system may further include one or more processors operatively coupled with a memory storing instructions which when executed enable the processor to receive, at a server, a first set of data packets from the one or more oxygen concentrators, establish a communicative coupling between the one or more oxygen concentrators and the server such that responsive to receipt of the first set of data packets.
[0057] In an embodiment, the first set of data packets pertain to a location information of the oxygen concentrator, an authentication information of the oxygen concentrator, a registration information to register an IP address through an LTE network.
[0058] The server is configured to receive, at regular pre-defined intervals, a second set of data packets and store the second set of data packets received at regular intervals within a database. In an embodiment, the second set of data packets received at regular intervals contains an operational performance metadata of the Oxygen concentrator and the health metadata of the oxygen concentrator.
[0059] The server then compares, by the processor, the received second set of data packets with a pre-defined threshold stored within the database. Based on the comparison, the server is configured to identify an operational status of the oxygen concentrator based on the received first set of data packets.
[0060] In an embodiment, the operational performance metadata of the oxygen concentrator within the second set of data packets comprises any or a combination of oxygen concentrator ID, temperature, oxygen pressure, compressor current, compressor voltage, oxygen level, oxygen flow rate and total up time of oxygen concentrator.
[0061] In an embodiment, the authentication information of the oxygen concentrator is an oxygen concentrator ID that can be pre-stored within the database at the server and fetched to compare the received authentication information from the oxygen concentrator and the oxygen concentrator ID pre-stored at the database to obtain a positive verification of the oxygen concentrator.
[0062] In yet another embodiment, the server may be configured to analyze the received second set of data packets and generate a third set of data packets to be transmitted based on the received second set of data packets being deviant from the pre-defined threshold within the database.
[0063] In an embodiment, the one or more error codes are defined and stored within the oxygen concentrator, each of said error codes being specified for a particular deviance from the pre-defined threshold such that the server, responsive to receipt of specific error code generates the third set of data packets specific to the received error code.
[0064] In an embodiment, the server is configured to display on a map of the geographical location, through an interface, the co-ordinates of the oxygen concentrators based on the received location information from each of the oxygen concentrators.
[0065] In an embodiment, the battery of Succour-GeoTag device 110to be in low power mode. The oxygen concentrator 106 can be operating in its configured state and provide operational parameters to the Succour-GeoTag110 attached to it via UART. The Succour-GeoTag in turn combines the data from oxygen concentrator, its own location coordinates and sends to the centralized server. Succour-GeoTag that goes to sleep mode and active mode.
[0066] The Succour-GeoTag 110 that goes to sleep mode and active mode, oxygen concentrator 106 is fully active all the time it has separate power supply. Whereas Succour-GeoTag has battery that must be managed.
[0067] The Succour-GeoTag device 110 can be in low power mode at regular pre-defined intervals and on receipt of an alert signal, the Succour-GeoTag device configured to transmit the second set of data packets from the oxygen concentrators 106 to the server.
[0068] FIG. 2 illustrates various functional units of the system at the server, in accordance with aspects of the present disclosure.
[0069] In an aspect, system 102 may comprise one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any medical equipment that manipulate data based on operational instructions. Among other capabilities, one or more processor(s) 202 are configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 102. The memory 204 may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory 204 may comprise any non-transitory storage Oxygen concentrator including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0070] System 102 may also comprise an interface(s) 206. The interface(s) 206 may comprise a variety of interfaces, for example, interfaces for data input and output medical equipment, referred to as I/O medical equipment, storage medical equipment, and the like. The interface(s) 206 may facilitate communication of system 102. The interface(s) 206 may also provide a communication pathway for one or more components of the system 102. Examples of such components include, but are not limited to, processing engine(s) 208 and database 210.
[0071] The processing engine(s) 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 208 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 208. In such examples, system 102 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to system 102 and the processing resource. In other examples, the processing engine(s) 208 may be implemented by electronic circuitry.
[0072] The database 210 may comprise data that is either stored or generated as a result of functionalities implemented by any of the components of the processing engine(s) 208 or system 102.
[0073] In an exemplary embodiment, the processing engine(s) 208 may include an input engine 212 that receives the first set of data packets from the Oxygen concentrators. Further, a logical engine 214 may be configured to process the Oxygen concentrator health and Oxygen performance status based on the received first set of data packets. The processing engine may then, based on the received pre-stored data from the database 210, make a comparison by the logical engine 214. Based on the comparison with the threshold values pre-stored within the database 210, by an alert generation engine, an alert may be generated and transmitted to authorized personnel.
[0074] Referring now to FIGs. 3A-3C that illustrate the functioning of an exemplary remote tracking and monitoring oxygen concentrator by Succour-GeoTag in accordance with the disclosed system. In an embodiment, an Succour-GeoTag tracks the exact location of the oxygen concentrator, as well as gets the physical parameters such as oxygen concentrators’ ID, temperature, oxygen pressure, compressor current, compressor voltage, oxygen level, oxygen flow rate & total up time of oxygen concentrator etc. regularly in pre-defined time intervals. Any sudden alert message or warning from oxygen concentrator in case of emergency is also captured in the event. The alert may be raised on a mismatch between the pre-defined threshold values within the database and the real-time sensed values from the oxygen concentrator, such as pressure, high temp, low voltage, compressor failure, co-processor overload, FAN failure, oxygen concentration output error, low pressure, low oxygen level, compressor overheating and the like.
[0075] In an embodiment, the Succour-GeoTag may be operated by a battery 304. The oxygen concentrator 106 may connect with the network 108 by network hardware 302. The network hardware 302 may include a Global Positioning System Antenna and Global Navigation Satellite System. Further, the Succour-GeoTag can include an indicator 306.
[0076] In an embodiment, the well-defined, mapped error codes to each of these errors are stored in oxygen concentrator 106 and on receipt of such errors/issues oxygen concentrator 106maysendcorrespondingerrorcodetoSuccour-GeoTag, in turn Succour-GeoTag gives the priority to this warning message received from oxygen concentrator 106 and immediately sends this to the server.
[0077] In an embodiment, the server is a cloud server.
[0078] In an embodiment, the cloud server re-maps the error code received with the error and displays on the display dash board operatively coupled with the server.
[0079] As shown in FIG.3B, the Succour-GeoTag110 fitted to oxygen concentrator106may be designed based on an Application Processor with LTE/Wi-Fi/GPS and running with headless Android/Embedded Linux. This may hosts the Open embedded Linux as its OS. Succour-GeoTag Application is developed for the medical equipment using Software Development Kit(SDK) which is installed on Android/Embedded Linux.
[0080] In an embodiment, the Succour-GeoTag maybe powered by a separate battery and some critical data indicating LEDs.
[0081] In an embodiment, the oxygen concentrator106 and the Succour-GeoTag may enable monitoring of basic critical health parameters of the patient and transmit the health parameters along with the Succour-GeoTag information. The medical applications monitoring basic critical parameters of a patient such as Oxygen level, Blood Pressure, SPO2, etc., are very important. The Succour-GeoTag 110 may be designed for medical purpose to receive this critical information and transmit the critical information along with the geo location and performance data of the oxygen concentrator 106.
[0082] Oxygen concentrator 106and Succour-GeoTag can be connected through UART/I2C/SPI or any compatible communication protocol as shown in FIG. 3B.Succour-GeoTagwhichcaninclude any communication protocol such as LTE module with GNSS, SIM slot, LTE antenna, GPS antenna, Battery connection, and any serial connectivity provision to connect with the oxygen concentrator 106.
[0083] As shown in FIG.3C, in an embodiment, the Succour-GeoTag may host an embedded Linux. On boot Linux auto starts the Succour-GeoTag app stored on the hardware. This app on execution registers with the 4G Network and gets the IP address for data connectivity. After this, Application may be configured to fetch GPS location Latitude and Longitude co-ordinates. The oxygen concentrator 106may connect to the server 308 through network hardware 302. The server 308, through the network 106 may authenticate user access 310 by comparing the oxygen concentrator ID with the pre-stored information within the database.
[0084] In an embodiment, if GPS antenna is exposed outdoors, then the oxygen concentrator106 may receive GPS coordinates immediately. If the GPS antenna is not exposed outside, then it may take a few minutes to fetch the GPS co-ordinates. Meanwhile, the Succour-GeoTag Oxygen concentrator communicates with Oxygen Concentrator, sends one byte of data (‘a’at present) after getting one byte of data from Geo-Tag, Oxygen Concentrator forms a packet (sensor data) of 7 fields separated by ‘;’ description of each field. After receiving a packet of sensor data at Geo-Tag, it parses the packet frames the message suitable for a URL to send it to the server and enable to display the data on the display dashboard. This uploading sensor data and GPS data may be scheduled as per the patient requirements (viz. once in every 15 minutes or once in every half an hour).
[0085] FIG. 4 shows a cloud server 308 displaying the coordinates of the deployed Succour-GeoTag/medical equipment in accordance with an embodiment of the present disclosure. In an embodiment, this dashboard 400 can only be accessed with authentication or by authorized personnel.
[0086] In an embodiment, the Succour-GeoTagmay be operatively configured with other medical equipment.
[0087] In an embodiment, any alarms, exceptions, failures generated on the oxygen concentrator 106 may be proactively sent to Succour-GeoTag immediately. Succour-GeoTag in turn collects all these alarms codes and sends them to Dash board for the manual service. Alarm codes and its descriptions are explained below. These codes may be parsed at a web server.
[0088] In an embodiment, the oxygen concentrator 106 may also be configured with fetching location latitude and longitude from cell-phone ID by enabling a communicative coupling between the cell-phone and the Succour-GeoTag to get the approximate location info in the absence of GPS Connectivity for the Succour-GeoTag. In an embodiment, the accuracy may vary from 100m to 1km in case of Cell-ID based co-ordinates.
[0089] In an embodiment, the Succour-GeoTag Oxygen concentrator hardware, OS and applications are designed and implemented including hosting of Web server with a static IP, by designing a web-page, database maintenance, parsing of Geo-Tag data at server side and displaying in human readable format.
[0090] In an embodiment, the functionality of Succour-GeoTag has been extended such that it will communicate with the medical equipment for collecting sensor information and push this information on to the Dash board. Later the same oxygen concentrator 106can be used in many such fields where monitoring the position as well as some critical data need to be collected and send to a remote defined location.
[0091] FIG. 5 illustrates an exemplary architecture of the computer system to implement the proposed system in accordance with embodiments of the present disclosure.
[0092] As shown in FIG. 5, computer system 500 includes an external storage device 510, a bus 520, a main memory 530, a read only memory 540, a mass storage device 550, communication port 560, and a processor 570. A person skilled in the art will appreciate that computer system may include more than one processor and communication ports. Examples of processor 570 include, but are not limited to, an Intel® Itanium® or Itanium 2 processor(s), or AMD® Opteron® or Athlon MP® processor(s), Motorola® lines of processors, FortiSOC™ system on a chip processors or other future processors. Processor 470 may include various units associated with embodiments of the present invention. Communication port 560 can be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. Communication port 560 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which computer system connects.
[0093] Memory 530 can be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read only memory 540 can be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or BIOS instructions for processor 570. Mass storage 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), e.g. those available from Seagate (e.g., the Seagate Barracuda 7200 family) or Hitachi (e.g., the Hitachi Deskstar 7K1000), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks (e.g., SATA arrays), available from various vendors including Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc. and Enhance Technology, Inc.
[0094] Bus 520 communicatively couples processor(s) 570 with the other memory, storage, and communication blocks. Bus 520 can be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects processor 570 to software system.
[0095] Optionally, operator and administrative interfaces, e.g. a display, keyboard, and a cursor control device, may also be coupled to bus 520 to support direct operator interaction with computer system. Other operator and administrative interfaces can be provided through network connections connected through communication port 560. External storage device 510 can be any kind of external hard-drives, floppy drives, IOMEGA® Zip Drives, Compact Disc - Read Only Memory (CD-ROM), Compact Disc - Re-Writable (CD-RW), Digital Video Disk - Read Only Memory (DVD-ROM). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0096] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C … N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.
[0097] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

ADVANTAGES OF THE INVENTION
[0098] The centralized health and critical parameter collected at the database and displayed on the dashboard data can be accessed by any authentic doctors and device manufactures for further data processing and decision making.
[0099] The Succour-GeoTag helps in remotely monitoring huge number of patients spread across a geographical area from one place.
[00100] The Succour-GeoTag monitors the location of all the oxygen concentrators and checks for its healthy state.
, Claims:1. A system(100) for remotely tracking and monitoring operational status of one or more oxygen concentrators deployed in a geographical location, the system comprising:
a Succour-GeoTag device (110) operatively coupled with each of the one or more oxygen concentrators (106), one or more processors operatively coupled to Succour-GeoTag device, the processor coupled with a memory storing instructions which when executed enable the processor to:
receive, at a server, a first set of data packets from the one or more oxygen concentrators;
establish a communicative coupling between the one or more oxygen concentrators and the server, responsive to receipt of the first set of data packets;
receive, at regular pre-defined intervals, a second set of data packets from the one or more oxygen concentrators and store the second set of data packets received at regular intervals within a database;
compare, by the processor, the received second set of data packets with a pre-defined threshold stored within the database;
identify, an operational status of the one or more oxygen concentrators based on the received first set of data packets.
2. The system as claimed in claim 1, wherein the first set of data packets pertain to a location information of the one or more oxygen concentrators, an authentication information of the one or more oxygen concentrators, a registration information to register an IP address through an LTE network, wherein the second set of data packets received at regular intervals contain an operational performance metadata of the one or more oxygen concentrators and the health metadata of the one or more oxygen concentrators.
3. The system as claimed in claim 2, wherein the operational performance metadata of the one or more oxygen concentrators within the second set of data packets comprises any or a combination of oxygen concentrator ID, temperature, oxygen pressure, compressor current, compressor voltage, oxygen level, oxygen flow rate and total up time of oxygen concentrator.
4. The system as claimed in claim 2, wherein the authentication information of the one or more oxygen concentrators is an oxygen concentrator ID that is pre-stored within the database at the server and fetched to compare the received authentication information from the one or more oxygen concentrators and the oxygen concentrator ID pre-stored at the database to obtain a positive verification of the oxygen concentrator.
5. The system as claimed in claim 1, wherein the Succour-GeoTag device (110) is operatively configured with the one or more oxygen concentrators by a Universal Asynchronous Receiver Transmitter (UART) and the Succour-GeoTag device (110) is adapted to receive power from a battery.
6. The system as claimed in claim1, wherein the server is configured to analyze the received second set of data packets and generate a third set of data packets to be transmitted on the received second set of data packets being deviant from the pre-defined threshold within the database.
7. The system as claimed in claims 1 and 6, wherein one or more error codes are defined and stored within the one or more oxygen concentrator, each of said error codes being specified for a particular deviance from the pre-defined threshold such that the server, responsive to receipt of specific error code generates the third set of data packets specific to the received error code.
8. The system as claimed in claim 1, wherein the server is configured to display on a map of the geographical location, through an interface, the co-ordinates of the one or more oxygen concentrators based on the received location information from each of the oxygen concentrator.
9. The system as claimed in claim 4, wherein the Succour-GeoTag device (110) comprises a battery that is configured to enable a low power mode at regular pre-defined intervals and on receipt of an alert signal, the Succour-GeoTag device transmits the second set of data packets from the oxygen concentrators to the server.
10. The system as claimed in claim 1, wherein the Succour-GeoTag device (110) having a facility to update the firmware remotely over the air though the server, the process is secured by challenge-response authentic mechanism.