DESC:TECHNICAL FIELD
[0001] The proposed invention relates to health monitoring, and more particularly to, a system and method for monitoring health parameters of one or more subjects.

BACKGROUND
[0002] Monitoring certain health/vital parameters of subjects in a hospital ward, ambulance, home and for patients with non-favourable conditions (for example, elderly, sick, and injured) has become increasingly important and critical in recent times. In hospitals the patients must be regularly monitored for vitals as that is the only way to check if the patient is recovering well. Monitoring of the health parameters not only provides diagnostic clues as to the current condition of the illness of the subject but also provides an advance warning if health condition of the subject is worsening.

[0003] Various health-monitoring devices are currently in use for monitoring health parameters of the subjects. However, such health-monitoring devices are bulky, expensive, and difficult to wear while the subject is performing normal routine functions. Thus, bulk, cost, and wearability of the health-monitoring devices make them inappropriate to use.

[0004] Further, hospitals/healthcare delivery centres collect health data captured from the health-monitoring devices for interpretation and monitoring of the health parameters of the subjects. However, conventional approaches for data collection are largely manual and error prone also as a specialist/expert needs to be involved for in interpreting the health data of the subjects.

[0005] Thus, it may be difficult to interpret data of the subjects, when a ratio of the specialist to the patients is low, especially in times of high-patient occupancy/enrolment for monitoring. Further, the specialist may not always be available locally to interpret the data of the patients and to take appropriate decisions. Thus, causing patients to go unmonitored and assessment of criticality of the condition of the patients gets jeopardized. Many a times the manual interpretation of data is prone to unavoidable human errors as well which may lead to wrong decisions of treatments at the end. Therefore, the current health monitoring devices lack huge data monitoring in real-time.

SUMMARY
[0006] Consequently, the proposed disclosure provides a system and method for monitoring health parameters of one or more subjects automatically. The disclosure also provides an efficient wearable apparatus for collecting health data of a subject, which obviates the foregoing and other limitations and disadvantages of the prior art.

[0007] According to a first aspect of the present disclosure, there is provided a system for monitoring health parameters of one or more subjects in a communication network, The system comprises at least one wearable apparatus, comprising: a rechargeable patch arranged to be in contact with a subject and capture health data of the one or more subjects; and a device configured to capture, store and communicate the input data of the subject to one or more servers in real time. The system further comprises a monitoring server of the one or more servers configured to communicate with the at least one wearable apparatus through at least one wireless device. The monitoring server is configured to receive and monitor the health data of the one or more subjects in real-time. The monitored health data, by the monitoring server are accessed by one or more servers comprising a meta server and a routing server over the communication network The system further comprises a local entity of one or more local entities communicatively coupled with the monitoring server configured to receive the health data of the one or more subjects in real time, and displaying the received health data on a dashboard. The system further comprises an external entity of one or more external entities configured to receive the health data of one or more subjects from the one or more monitoring servers, through the routing server, based on user login information and permissions stored in the meta server.

[0008] According to a second aspect of the present disclosure, there is provided a wearable apparatus for monitoring health parameters of one or more subjects, the wearable apparatus, comprising: a rechargeable patch arranged to be in contact with a subject and capture and monitor health data of the subject; and a device configured to capture, store and communicate the health data of the subject to one or more servers in real time.
[0009] According to a third aspect of the present disclosure, there is provided a method for monitoring health parameters of one or more subjects in a communication network. The method comprises capturing and monitoring, through a wearable apparatus, health data of the one or more subjects. The health data of the subject is communicated to one or more servers in the communication network through an associated wireless device. The method further comprises receiving and monitoring, through a monitoring server of the one or more servers configured in communication with the wearable apparatus, the health data of the one or more subjects in real-time. The at least one wearable apparatus is communicatively coupled through the at least one wireless device. The monitored health data by the monitoring server are accessed by one or more servers comprising a routing server and a meta server over the communication network. The method further comprises receiving, by a local entity of one or more local entities communicatively coupled with a monitoring server, the health data of the one or more subjects in real time. The method further comprises displaying the received health data of one or more subjects from the one or more monitoring servers on a dashboard. The method further comprises receiving, by an external entity of one or more external entities, the health data of one or more subjects from the one or more monitoring servers, through the routing server, based on user login information and permissions stored in the meta server.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] For a more complete understanding of the present invention and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0011] FIG. 1A shows network implementation of a system for monitoring health parameters according to an embodiment disclosed herein;

[0012] FIG. 1B, and 1C disclose an example system for monitoring the health parameters, according to an embodiment disclosed herein;

[0013] FIG. 2A and 2B discloses components of a wearable apparatus configured in the system, according to an embodiment disclosed herein;

[0014] FIG. 2C illustrates an exploded view of different components of the wearable apparatus comprising reusable patch, according to an embodiment disclosed herein;

[0015] FIG. 2D discloses components though an exploded view of different components of the wearable apparatus, according to an embodiment disclosed herein;

[0016] FIG. 2E discloses wearability of a rechargeable patch of the wearable apparatus on the body, according to an embodiment disclosed herein;

[0017] FIG. 3 discloses an example illustration of the system for monitoring the health parameters of subjects, according to an embodiment disclosed herein;

[0018] FIG. 4 discloses an example architecture of the system for remote monitoring of the health parameters of subjects, according to an embodiment disclosed herein;

[0019] FIG. 5A-5G disclose an example dashboard generated based on monitoring of the health parameters of subjects through the system, according to an embodiment disclosed herein; and

[0020] FIG. 6 illustrates a flowchart showing steps of a method performed for monitoring health parameters of one or more subjects, according to an embodiment disclosed herein.

DETAILED DESCRIPTION
[0021] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0022] Embodiments herein disclose a system and a method for monitoring health parameters of one or more subjects. The health parameters may include, but are not limited to, Electrocardiogram (ECG), Heart Rate, Body Temperature Respiration Rate (RR), Oxygen Saturation (SpO2), Blood Pressure Trend (BP), and so on. Embodiments herein also disclose a wearable device for capturing health data of a subject.

[0023] Referring to FIG. 1A, 1B and 1C in combination, in an example embodiment, FIG. 1A shows a network implementation of the system 1000 for monitoring heath parameters of one or more subjects.
[0024] In another exemplary embodiment, FIG.s 1B, and 1C disclose an example system 1000 for monitoring health parameters of the one or more subjects. The system 1000 referred herein is configured for continuous analysis and monitoring of the health parameters of the one or more subjects at a time. The subject referred herein may include, but is not limited to, a sick person, an elder person, a disabled person, or the like.

[0025] In accordance with the first aspect of this disclosure as shown in FIG. 1C, the system 1000 comprises at least one wearable apparatus 900, a monitoring server 300 of the one or more servers, at least one wireless device 400, a meta server 800 and a routing server 600, a local entity 700 of one or more local entities and an external entity 750 of one or more external entities.

[0026] Again, referring to FIG. 1A to 1C, the monitoring server 300 of the one or more servers configured to communicate with the at least one wearable apparatus 900 through at least one wireless device 400. The monitoring server 300 is configured to receive and monitor the health data of the one or more subjects in real-time. The monitored health data, by the monitoring server 300 are accessed by one or more servers comprising the meta server 800 and the routing server 600 over the communication network 500.

[0027] The local entity 700 of one or more local entities is communicatively coupled with the monitoring server 300 and configured to receive the health data of the one or more subjects in real time, and displaying the received health data on a dashboard 200. The external entity 750 of one or more external entities is configured to receive the health data of one or more subjects from the one or more monitoring servers 300, through the routing server 600, based on user login information and permissions stored in the meta server 800.

[0028] In an embodiment, the meta server 800 is main management server and is arranged for storing data regarding the patients, wearable apparatus, location information,health parameters and episodes. The monitoring server 300 is arranged to provide active central monitoring of the health parameters.

[0029] The monitoring server 300 may communicate with one or more wearable apparatus 900 configured in the system 1000. The wearable apparatus 900 may be worn by the plurality of subjects at multiple wards of a hospital, day care centres, Intensive Care Units (ICUs), remote camps, and so on. Alternatively, the wearable apparatus 900 may be worn by the subject at home, in ambulance, or the like.

[0030] In an example implementation, again referring to FIG. 1A, the meta server 800, may communicate with the plurality of monitoring server 300 and the Monitoring server 300 may communicate with the plurality of wearable apparatus 900 through the wireless devices 400 associated with the wearable apparatus 900. In an example, the wireless devices 400 may correspond to computing devices being used by the subjects. Examples of the computing devices may include, but is not limited to, a smart phone, a tablet, a phablet, a wireless gateway or, the like.

[0031] The monitoring server 300 may communicate with the wearable apparatus 900 through at least one wireless device 400 in the communication network 500. In an example, the communication network 500 comprises a wireless network, a wired network, or a combination thereof. More specifically, the communication network 500 may be implemented as one of the different types of networks, such as intranet, Local Area Network, LAN, Wireless Personal Area Network, WPAN, Wireless Local Area Network, WLAN, wide area network, WAN, the Internet, and the like. The communication network 500 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, MQ Telemetry Transport, MQTT, Extensible Messaging and Presence Protocol, XMPP, Hypertext Transfer Protocol, HTTP, Transmission Control Protocol/Internet Protocol, TCP/IP, Wireless Application Protocol, WAP, and the like, to communicate with one another. Further, the communication network 500 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.

[0032] The monitoring server 300 may also communicate with the local entities 700 or the external entities 750 through the communication network 500, as depicted in Figure 1C. In some examples, the local entities 700 or the external entities 750 (also may referred as nodes) referred herein may be devices being used by hospitals, healthcare delivery centres, support centres, reporting centres, consultants/doctors, healthcare personnel, or the like. The external entities 750 referred herein if operate as remote stations then they may communicate through routing server 600 . The routing server 600 may receive the health data of the one or more subjects from the plurality of wearable apparatus 900 through the plurality of monitoring servers 300 and metadata from the server 800 and provide the received health data to the remote dashboards 200 for monitoring of the health parameters, wherein the wireless device 400 may be associated with the wearable apparatus 900 being worn by the subjects.

[0033] In an example implementation, proprietary communication protocols may be adapted for communication between the meta server 800, monitoring servers 300 and the devices 400, the wireless apparatus 900, the local entities 700 and the external entities 750. The proprietary communication protocols may ensure low latency, low bandwidth utilization (raw data only) and may help coordinating between the monitoring servers 300 and the devices 900, 700, 750 and 400 to fetch information about real-time and remote monitoring of the health parameters.

[0034] Thus, the meta server 800 referred herein may act as the metadata server 800 positioned over a cloud for access to the external entities 750, local entities 700, monitoring servers 300 and the dashboards 200.

[0035] Further, the meta server 800, routing server 600, and the monitoring server 300 may correspond to computing devices. It may be understood that the meta server 800, routing server 600 and monitoring server 300 may also be implemented in a variety of computing systems such as a laptop computer, a desktop computer, a workstation, a mainframe computer, a network server, a cloud-based computing environment, and the like. It may be understood that the Meta server 800, routing server 600,and monitoring server 300 may correspond to a variety of portable computing devices such as, a laptop computer, a desktop computer, and the like.

[0036] The monitoring server 300, routing server 600 and meta server 800 is configured for real-time and remote monitoring of health parameters of the subjects, thereby monitoring health condition of the subjects. The monitoring server 300 and meta server 800 comprises at least one processor, a memory, a user interface, and a communication unit (not shown in Figures).

[0037] The meta server 800 may also comprise database that may include a repository for storing the meta data of the subjects, information about (for example, identities (IDs), location, or the like) the wearable apparatus 900, the health parameters of the subjects, or the like.

[0038] The meta server 800 may also comprise a communication unit for enabling communication of the meta server 800 with other monitoring servers 300, routing server 600, local entities 700, external entities 750 and wireless devices 400 through the communication network 500.

[0039] The one or more local entities 700 is communicatively coupled to the monitoring server 300 and configured to receive the health data of one or more subjects monitored by the monitoring server 300 and display the received health data on the dashboard 200 in real time.

[0040] The monitoring server 300 may also comprise a communication unit for enabling communication of the monitoring server 300 with wearable apparatus 900 and wireless devices 400 through the communication network 500.

[0041] The meta server 800 is configured to receive the health data of the one or more subjects from the associated one or more wearable apparatus 900. The meta server 800 is also configured to receive meta data from the one or more monitoring servers 300. The meta server 800 may access health parameters of the one or more subjects monitored by the monitoring server 300 in real-time. The health parameters may include first variant parameters or second variant parameters. Examples of the first variant parameters may include ECG, respiration rate (RR), and body temperature. Examples of the second variant parameters may include ECG, respiration rate, body temperature, Oxygen Saturation (SpO2), blood pressure trend. In an example, the metadata comprising at least one of: patient information, information of at least one wearable apparatus 900, location information of the at least one wearable apparatus 900, user information and episodes for the at least one wearable apparatus 900, user login information, access permissions for the one or more local entities 700 or external entities 750 to access the one or more monitoring servers 300 or the one or more wearable apparatus 900. In an example, the episodes comprise of specific snapshots of significance captured from a continuous health parameter reading indicating deviation from normal parameters. In an example, the health data of the subject comprises cardiac data comprising electrocardiogram (ECG) signals indicating one or more of: P wave, QRS complex and T wave; Respiration Rate (RR), Heart Rate (HR), Temperature, SpO2 and Blood Pressure Trend (BP).

[0042] In some embodiments, the monitoring server 300 identifies the heartbeats of the subjects from the received health data, analyses all the heartbeats for beat level fiducial points and performs beat-to-beat rhythm analysis for all possible anomalies within a beat and beat-to-beat rhythms problem for example, for every 16 seconds. All the beat-to-beat rhythm analysis may be performed for critical alarms/use cases.

[0043] In some embodiments, the monitoring server 300 calculates SpO2 after critical analysis of waves for noise conditions of waves and skin conditions to ensure reliable blood oxygenation. The monitoring server 300 also crosschecks the calculated pulse rate from SpO2 with a HR from ECG data and identifies the deviation.

[0044] In some embodiments, the monitoring server 300 uses Artificial Intelligence (AI) and Machine Learning (ML) models for identifying the BP from a PPG wave, which extrapolates the BP from pulse volume, and pulse pressure and is achieved by 1-level calibration (that is performed by a nurse or a healthcare personnel member for the subject using an external BP apparatus).

[0045] The monitoring server 300 is also configured to generate and display early warning and notifications on the local entities 700 or the external entities 750 using the dashboards 200 about the health parameters of the subjects. Also, the monitoring server 300 is configured to generate and display early warning and notifications on a consumption device (terminal or tablet) being used by nurse/doctor/expert user/specialist. For example, when remote monitoring of the subjects is required by an expert user outside an Intranet, the external entities 750 may collaborate with the routing server 600 on-demand to fetch the appropriate health parameters of the subjects and to display the fetched health parameters on a consumption device (terminal or tablet) being used by the expert user.

[0046] The monitoring server 300 is also configured to generate an early warning scoring system that may be configurable on the local entities 700 or on the external entities 750, which indicates the hospitals, healthcare delivery centres, support centres, reporting centres, consultants/doctors, healthcare personnel, or the like, to dynamically change preferences on how the subjects need to be monitored.

[0047] The monitoring server 300 is also configured to generate live dashboards 200 (later depicted in FIG.s 5A-5G) for all the subjects. The live dashboards 200 may provide information about the subjects, details associated with the subjects (for example, a contact number, a location, or the like), waveforms and health parameters associated with the subjects. The information provided by the live dashboards 200 may be associated with timestamps in case of any communication delays.

[0048] In some embodiments, the live dashboards 200 may be generated with critical level indicators, alarms, automated trend chart reporting, reporting with checks for false positives, and color-coded callout analysis for analysis of the health parameters of the subjects. For example, the monitoring server 300/ live dashboards 200 may automatically allocate priorities and color codes on the live dashboards 200 to notify doctors or consultants or nurses about the health parameters of the subjects on need-basis. The doctors or consultants may select an individual subject and view waveform and other health parameters related to that subject from the live dashboards 200 for remote consumption.

[0049] In some examples, multiple users (for example, doctors, nurses, consultants, healthcare personnel, or the like) may login to an application provided by the meta server 800 for accessing the dashboards and notifications related to the health parameters of the subjects. Thus, the entire system may be secured by login control and designed for role-based access, ensuring data privacy and security.

[0050] Thus, the monitoring server 300 may act as single compact device for comprehensive, non-intrusive monitoring of the health parameters of the multiple subjects.

[0051] In some embodiments, the routing server 600 is arranged to fetch the health data from the one or more monitoring servers 300 on demand by one or more external entities 750. The one or more external entities 750 are configured to receive health data through the routing server 600 and display the health data remotely on a dashboard 200 in real time. The routing server 600 is further configured to fetch health data from the one or more monitoring server 300 on demand by one or more external entities 750, receive the health data from the monitoring server 300 associated with the at least one wearable apparatus 900. The routing server 600 may determine a type of data from the received health data, upon selection of the subject associated with wearable apparatus 900 by the local entity 700 or external entity 750. In an example, the type of data comprises at least one of ECG wave, P wave, QRS complex and T wave; Respiration Rate (RR), Heart Rate (HR), Temperature, SpO2 and Blood Pressure Trend (BP). The routing server 600 may communicate, through one or more communication channels via the communication network 500, the health data from the one or more monitoring servers 300 to the one or more external entities 750 or local entities 700.
[0052] In some embodiments, the monitoring server 300 is configured to receive, analyse and locally store the health data and the meta data from the one or more wearable apparatus 900 and provide health data of the one or more wearable apparatus 900 to one or more communicatively coupled local entities 700 for displaying on a dashboard 200 without any connection to additional servers comprising routing server 600 or meta server 800.
[0053] In some embodiments, the dashboard 200 is arranged to display health data and alerts to one or more local entities 700 or external entities 750. The alerts are sent to the one or more local entities 700 or external entities 750 upon one or more conditions. The one or more conditions may include and not limited to abnormal readings, saving critical minutes in times of emergencies, non-reception of health data from the subject, detection of detachment of the rechargeable patch from the subject, reception of noisy signal, low battery status.
[0054] Referring to FIG. 2A to 2D, in accordance with embodiments disclosed herein, the wearable apparatus 900 comprises the device 902 and the rechargeable patch 904. The rechargeable patch 904 (also may referred to as patch 904) is arranged to be in contact with a subject and capture health data of the one or more subjects. The rechargeable patch 904 comprises a reusable silicon or a thermoplastic patch. The rechargeable patch 904 comprises a sleeve component with a rechargeable battery 920, one or more electronics layers 915, one or more sensors and electrodes. The patch 904 houses a battery 920 and electrodes, where the patch 904 may be charged/recharged for every test. Since battery is not arranged on the device 902, the monitoring of the subject may be proceeded with a different patch 904, which may cause subject monitoring workflow to be efficient and real-time while preventing downtime during replacements of the patch 904 of the wearable apparatus 900 for longer durations. The patch/battery may be recharged and replaced for uninterrupted data capture.

[0055] The patches 904 may be decoupled/detached from the device 902, as depicted in FIG. 2A. Decoupling of the device 902 and the patch 904 may ensure continuous reuse of the wearable apparatus 900, which may further ensure lower costs per test and enable smooth operations. The operations may include changing of the patch 904 once in a predefined number of days, for example, three days and automatically triggering replacement of the patch 904 based on battery low indication or wear and tear or periodically.

[0056] Referring to FIG. 2E is example illustration disclosing wearable options for wearing the wearable apparatus 900. Embodiments provide the wearable apparatus 900 with multiple wearable options. In an example, as disclosed in FIG. 2E, the wearable apparatus 900 may be worn by the subject with electrodes and has limited reusability.

[0057] FIG. 2B illustrates a top view 908 and bottom view 910 of the assembled rechargeable patch 904 of the wearable apparatus 900.

[0058] FIG. 2C shows an exploded patch 904. In FIG. 2C the patch 904 comprises a stud button top 918, a silicon top part 914, and a Printed Circuit Board (PCB) 915. The patch 904 further comprises an eyelet crimp 918 and a battery 920. The battery 920 comprises a rechargeable battery may be configured to provide power supply to the wearable apparatus 900. The patch 904 further comprises silicon bottom part 922 and a stud bottom part 924. The electrodes in the patch 904 may be configured to capture health data of the one or more subjects. The patch may include one or more sensors to capture health data of the subject. In an example, a single channel electrode arranged to be on a chest of the subject may be used to capture data related to the ECG. In another example, the sensor may comprise an Infrared (IR) sensor to capture data related to body temperature. In yet another example, the sensor may comprise Red and IR Light Emitting Diodes (LEDs) to capture data related to SpO2, thereby, SpO2 data may be captured using photoplethysmography.

[0059] FIG. 2D shows an exploded view of the device 902 in the wearable device 900. The device 902 comprises the SPO2 sensor 906, a device top plastic 926, a device bottom plastic 928 and PCB layer 916. The device 902 also comprises a temperature sensor 930.

[0060] In an example, the PCB layer 916 may also comprise a local/device storage to store the capture health data of the subject for a pre-defined number of days, for example, upto 3 days.

[0061] The PCB layer 916 may also comprise a communication unit to transfer the captured health data of the subject to the monitoring server 300. In an example, the health data may be transferred to the monitoring server 300 or meta server 800 in small packets instead of sharing in large chunks to enable a faster generation of report. In an example, the communication unit transfers the health data of the subject to the server 300 or meta server 800 continuously. In another example, the communication unit transfers the health data of the subject to the monitoring server 300 or meta server 800 at periodic intervals, for example, for every few seconds.

[0062] In an example, FIG. 2E shows the device 902, the patch 904 fixed on a human body of the wearable apparatus 900.

[0063] In some examples, the wearable apparatus 900 may be provided for the subjects in different variants based on their location. In an example, the wearable apparatus 900 with the same patch may be provided for all the subjects present at a hospital word. In another example, the wearable apparatus 900 with a small hospital step down ICU variant may be provided for the subjects at an ICU. In yet another example, the wearable apparatus 900 may be provided for the subject at home.

[0064] FIG. 3 discloses an example illustration of the system 1000 for monitoring the health parameters of the subjects. The system 1000 provides a multi-vital remote monitoring platform that is a complete suite with ECG and all health parameters including blood pressure without cuff called blood pressure trend.

[0065] The system 1000 comprises the meta server 800 for centralized monitoring of the health parameters of the subjects.

[0066] The meta server 800 receives the health data of the plurality of subjects present at various locations. For example, the meta server 800 may receive the health data of the subjects admitted in hospital wards. In such a scenario, the meta server 800 may receive the health data of the subjects from the monitoring server 300, wherein the monitoring server 300 herein correspond to local servers deployed in the hospital wards. The monitoring server 300 receive the health data of each subject from the wearable apparatus 900 worn by that subject. For another example, the monitoring server 300 may receive the health data of the subjects located at remote camps, at home, or in ambulance. In such a scenario, the monitoring server 300 is installed in the cloud and may receive the health data of the subjects from the wireless devices 400 (correspond to the computing devices associated with the subjects). The wireless devices 400 receive the health data of each subject from the wearable apparatus 900 worn by that subject. Thus, the monitoring server 300 may receive the health data of the plurality of subjects without any delay (for example, within seconds).

[0067] Upon collecting the health data of the subjects, the monitoring server 300 may analyze the health data using AI or ML models for monitoring the health parameters of the subjects. The monitoring server 300, provides live dashboards locally through the dashboards 200 on the local entities 700 or external entities 750. The monitoring server 300 remotely provides the monitored health parameters of the subjects to a central monitoring facility at a central hospital or to doctors/consultants through the routing server 600 by generation of live dashboards through dashboards 200 on the local entities 700 or external entities 750. Thus, providing remote consultant live viewing of the health parameters without any delay, which enables the doctors/consultants to remotely view the health parameters or the live dashboards through an application.

[0068] The monitoring server 300 also generates automatic alarms for the central monitoring facility or for the doctors/consultants to analyse the health condition of the subjects, when the monitored health parameters indicate worsening of the health condition of the subjects.

[0069] FIG. 4 discloses an example architecture of the system 1000 for remote monitoring of the health parameters of the subject. As depicted in FIG. 4, the system 1000, one method where the wearable apparatus connects directly to the Wi-Fi network or comprises the wireless device 400, which is connected to the wearable apparatus 900 being worn by the subject. The wearable device 400 is provided with a gateway that connects to the wearable apparatus 900 through a wireless network and to a standard Wi-Fi router.

[0070] Still referring to FIG. 4, the system 1000 comprises the meta server 800 and the routing server 600 (also may referred to as remote server). The meta server 800 and the routing server 600 may be connected on the same network. In some examples, the meta server 800 and the routing server 600 may be the same machine. The remote server 600 may receive and store the health data of the subjects received from the plurality of monitoring server 300 through the network. The remote server 600 provides the health data of the subjects to the one or more external entities 750.

[0071] The monitoring server 300 analyses the health data of the subjects using AI or ML models to monitor the health parameters of the subjects. The meta server 800 also generates dashboard or reports providing information about the monitored health parameters of the subjects. The monitoring server 300 may provide the generated live dashboards or reports to the local entity 700 or the one or more external entities 750 collaborated with the Meta server 800. The remote server/routing server 600 further sends live data (that is the health parameters) of waveform in real-time to remote devices being used by doctors/consultants, so that the doctors/consultants may remotely view the live data for further analysis.

[0072] FIG.s 5A-5G disclose an example dashboard 200 generated based on monitoring of the health parameters of the one or more subjects by the system 1000.

[0073] The dashboard 200 generated by the monitoring server 300 while monitoring the health parameters of the subjects is depicted in FIG. 5A. The monitoring server 300 may remotely display the generated dashboard on a user interface of the local entity 700 or external entity 750 in real-time for further analysis, as depicted in FIG. 5B.

[0074] In an example, the dashboard 200 may provide information about trends of health parameters of the subject, as depicted in FIG. 5C. The health parameters may include heart rate, body temperature, respiration rate, SpO2, or the like.

[0075] In another example, the dashboard application 200 may provide information about ECG snapshot, as depicted in FIG. 5D.

[0076] In another example, the dashboard application 200 may provide periodic record of the health parameters of the subject, as depicted in FIG. 5E. The record indicates the health parameters of the subject monitored at different time intervals.

[0077] In yet another example, the dashboard application 200 may provide information about the health parameters of the different subjects on a single web page, as depicted in FIG. 5F.

[0078] In yet another example, the dashboard application 200 may provide information about the health parameter of each subject on a single web page, as depicted in FIG. 5G. The display of the information presented over the dashboard may be controlling by enabling display restrictions to selected users. For example, the doctor may be able to see information about patients consulting the doctor. With this, the system 1000 would provide data privacy while displaying the information.

[0079] Thus, by providing the dashboard application 200, the doctors/consultants/nurses may:
? access trend charts of the subjects at a remote or central location;
? review all episode snapshots of the subjects (depicting specific snapshots of significance, indicating deviation from normal health parameters) that were generated during a course of monitoring;
? generate additional snapshots at any point in time during the course of monitoring;
? choose different snapshots to be added into the reports and generate consolidated reports;
? review selected snapshots remotely; and
? connect to any patient remotely to monitor and give consultation.

[0080] Figure 6 is a flowchart illustrating method steps of a method 6000 performed for real-time and remote monitoring of the health parameters (health parameters) of the subject. The method 6000 may be executed by the monitoring server 300.

[0081] At step 602, the method 6000 comprises capturing and monitoring, through the wearable apparatus 900, health data of the one or more subjects. The health data of the subject is communicated to one or more servers in the communication network 500 through an associated wireless device 400.

[0082] At step 604, the method 6000 comprises receiving and monitoring, through the monitoring server 300 of the one or more servers configured in communication with the wearable apparatus 900, the health data of the one or more subjects in real-time. The at least one wearable apparatus 900 is communicatively coupled through the at least one wireless device 400. The monitored health data by the monitoring server 300 are accessed by one or more servers comprising the routing server 600 and the meta server 800 over the communication network 500.

[0083] At step 606, the method 6000 comprises receiving, by the local entity 700 of one or more local entities communicatively coupled with a monitoring server 300, the health data of the one or more subjects in real time and displaying the received health data on the dashboard 200.

[0084] At step 608, the method 6000 comprises receiving, by the external entity 750 of one or more external entities, the health data of one or more subjects from the one or more monitoring servers 300, through the routing server 600, based on user login information and permissions stored in the meta server 800.

[0085] In an example, the method 6000 comprises monitoring, by the monitoring server 300, the health parameters of the subjects by analysing the received health data using AI or ML models.

[0086] In some embodiments, the method 6000 comprises reporting, by the one or more server, the health parameters of the one or more subjects to the one or more external entities 750 for further assessment. In some embodiments, the method 6000 comprises providing, by the server, the live dashboards 200 indicating the health parameters of the one or more subjects, so that the health parameters may be remotely viewed by the one or more external entities 750 for further assessment.

[0087] The proposed system 1000 enables:
? real-time and remote monitoring of the health parameters: With such a feature, efficiency of monitoring may be increased with better resource usage. For example, from better resource usage, hospitals may save cost in terms of nurses that are used for monitoring and the nurses may be moved from a task noting down the health parameters to attend the subjects/patients;
? better patient/subject outcomes: With an advent of monitoring the patient from a remote location, the nurse may raise alert when the health condition of the patient worsens. In such a scenario, the doctor may connect to the patient remotely, analyse the health parameters and trend, and appropriately take a decision. Thus, causing an improvement in the patient’s outcomes; and
? lower cost in digitizing patient monitoring due to reusable electronics, and reduced nursing cost: The wearable apparatus is designed in such a way that the device of the apparatus may be reused, and the patch of the apparatus may be reused based on the patch used. The reuse of the device comprising electronics may save cost and reduce overall cost in monitoring. With the reduced cost, better patient care may be provided.

[0088] Further, with the proposed system 1000,
? patients need not be disturbed for routine collection of the health data;
? minimum chances of contamination due to contactless collection of the health data;
? complete digital records may be available for further reference;
? alerts may be raised in case of abnormal readings saving critical minutes in times of emergencies; and
? reports may be assessed by a doctor remotely.

[0089] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure.
,CLAIMS:We Claim:

1. A system (1000) for monitoring health parameters of one or more subjects in a communication network (500), the system (1000) comprising:
at least one wearable apparatus (900), comprising:
a rechargeable patch (904) arranged to be in contact with a subject and capture health data of the one or more subjects; and
a device (902) configured to capture, store and communicate the input data of the subject to one or more servers in real time; and
a monitoring server (300) of the one or more servers configured to communicate with the at least one wearable apparatus (900) through at least one wireless device (400), and wherein the monitoring server (300) is configured to receive and monitor the health data of the one or more subjects in real-time, wherein the monitored health data, by the monitoring server (300) are accessed by one or more servers comprising a meta server (800) and a routing server (600) over the communication network (500);
a local entity (700) of one or more local entities communicatively coupled with the monitoring server (300) configured to receive the health data of the one or more subjects in real time, and displaying the received health data on a dashboard (200); and
an external entity (750) of one or more external entities configured to receive the health data of one or more subjects from the one or more monitoring servers (300), through the routing server (600), based on user login information and permissions stored in the meta server (800).
2. The system (1000) as claimed in claim 1, wherein the rechargeable patch (904) comprises a reusable silicon or a thermoplastic patch, and wherein the rechargeable patch (904) comprises a sleeve component with a rechargeable battery, one or more electronics layers (916), one or more sensors and electrodes, and
wherein the rechargeable battery is configured to provide power supply to the wearable apparatus (900), and wherein the one or more sensors and electrodes in the rechargeable patch (904) capture the health data from the subject.
3. The system (1000) as claimed in claim 1, wherein the health data comprise at least one of: Electrocardiogram (ECG), Heart Rate, Body Temperature Respiration Rate (RR), Oxygen Saturation (SpO2), Blood Pressure Trend (BP).
4. The system (1000) as claimed in claim 1, wherein a wireless device (400) is communicatively coupled with the wearable apparatus (900), wherein the wireless device (400) is configured to receive and communicate the health data of each subject from the wearable apparatus (900) worn by that subject.
5. The system (1000) as claimed in claim 1, comprising:
one or more local entities (700) communicatively coupled to the monitoring server (300) and configured to receive the health data of one or more subjects monitored by the monitoring server (300) and display the received health data on a dashboard (200).
6. The system (1000) as claimed in claim 1, wherein the one or more servers comprising a meta server (800) configured to:
receive the health data and meta data from the one or more monitoring servers (300),
store the meta data,
wherein the metadata comprising at least one of: patient information, information of at least one wearable apparatus (900), location information of the at least one wearable apparatus (900), user information and episodes for the at least one wearable apparatus (900), user login information, access permissions for the one or more local entities (700) or external entities (750) to access the one or more monitoring servers (300) or the one or more wearable apparatus (900).

7. The system (1000) as claimed in claim 6,
wherein the health data of the subject comprises cardiac data comprising electrocardiogram (ECG) signals indicating one or more of: P wave, QRS complex and T wave; Respiration Rate (RR), Heart Rate (HR), Temperature, SpO2 and Blood Pressure Trend (BP), and
wherein the metadata comprises at least one of: data related to the wearable apparatus (900), data related location information, episodes and data related to access information, information about the wearable apparatus (900) comprises an identity (ID) of the wearable apparatus (900), name of the subject associated with each wearable apparatus (900), contact number of the subject, date and time about wearability of each wearable apparatus (900) by the subject, a status of each wearable apparatus (900), information about each wireless device (400) to which the wearable apparatus (900) is connected, and a location information associated with the wearable apparatus (900).
8. The system (1000) as claimed in claim 1, wherein the one or more servers comprising a routing server (600), arranged to:
fetch the health data from the one or more monitoring servers (300) on demand by one or more external entities (750);
wherein the one or more external entities (750) are configured to:
receive health data through the routing server (600); and
display the health data remotely on a dashboard (200) in real time.
9. The system (1000) as claimed in claim 8, wherein the routing server (600) further configured to:
fetch health data from the one or more monitoring server (300) on demand by one or more external entities (750);
receive, the health data from the monitoring server (300) associated with the at least one wearable apparatus (900);
determine, a type of data from the received health data, wherein the type of data comprises at least one of: ECG wave, P wave, QRS complex and T wave; Respiration Rate (RR), Heart Rate (HR), Temperature, SpO2 and Blood Pressure Trend (BP) upon selection of the subject associated with wearable apparatus (900); and
communicate, through one or more communication channels via the communication network (500), the health data from the one or more monitoring servers (300) to the one or more external entities (750) or local entities (700).
10. The system (1000) as claimed in claim 1, wherein the monitoring server (300) configured to:
receive, analyse and locally store the health data and the meta data from the one or more wearable apparatus (900);
provide health data of the one or more wearable apparatus (900) to one or more communicatively coupled local entities (700) for displaying on a dashboard (200) without any connection to additional servers comprising routing server (600) or meta server (800)

11. The system (1000) as claimed in claim 1, comprising:
the dashboard (200), arranged to:
display health data and alerts to one or more external entities (700, 750), wherein the alerts are sent to the one or more external entities (700, 750) upon one or more conditions, wherein the one or more conditions comprise at least one of: abnormal readings, saving critical minutes in times of emergencies, non-reception of health data from the subject, detection of detachment of the rechargeable patch from the subject, reception of noisy signal, low battery status.
12. A wearable apparatus (900) for monitoring health parameters of one or more subjects, the wearable apparatus (900), comprising:
a rechargeable patch (904) arranged to be in contact with a subject and capture and monitor health data of the subject; and
a device (902) configured to capture, store and communicate the health data of the subject to one or more servers in real time.
13. The wearable apparatus (900) as claimed in claim 12, wherein the rechargeable patch (904) comprises a reusable silicon or a thermoplastic patch, and wherein the rechargeable patch (904) comprises a sleeve component with a rechargeable battery, one or more electronics layers (916), one or more sensors and electrodes, and
wherein the rechargeable battery is configured to provide power supply to the wearable apparatus (900), and wherein the one or more sensors and electrodes in the rechargeable patch (904) capture the health data from the subject.

14. A method (6000) for monitoring health parameters of one or more subjects in a communication network (500), the method (6000) comprising:
capturing and monitoring, through a wearable apparatus (900), health data of the one or more subjects, wherein the health data of the subject is communicated to one or more servers in the communication network (500) through an associated wireless device (400); and
receiving and monitoring, through a monitoring server (300) of the one or more servers configured in communication with the wearable apparatus (900), the health data of the one or more subjects in real-time, wherein the at least one wearable apparatus (900) is communicatively coupled through the at least one wireless device (400), and wherein the monitored health data by the monitoring server (300) are accessed by one or more servers comprising a routing server (600) and a meta server (800) over the communication network (500).
receiving, by a local entity (700) of one or more local entities communicatively coupled with a monitoring server (300), the health data of the one or more subjects in real time, and displaying the received health data on a dashboard (200);
receiving, by an external entity (750) of one or more external entities, the health data of one or more subjects from the one or more monitoring servers (300), through the routing server (600), based on user login information and permissions stored in the meta server (800).
15. The method (6000) as claimed in claim 14, wherein the rechargeable patch (904) comprises a reusable silicon or a thermoplastic patch, and wherein the rechargeable patch (904) comprises a sleeve component with a rechargeable battery, one or more electronics layers (916), one or more sensors and electrodes, and
wherein the rechargeable battery is configured to provide power supply to the wearable apparatus (900), and wherein the one or more sensors and electrodes in the rechargeable patch (904) capture the health data from the subject.
16. The method (6000) as claimed in claim 14, wherein the health data comprise at least one of: Electrocardiogram (ECG), Heart Rate, Body Temperature Respiration Rate (RR), Oxygen Saturation (SpO2), Blood Pressure Trend (BP).
17. The method (6000) as claimed in claim 14, wherein the method (6000) comprising:
receiving and communicating, through a wireless device (400), the health data of each subject from the wearable apparatus (900) worn by that subject, wherein the wireless device (400) is communicatively coupled with the wearable apparatus (900).
18. The method (6000) as claimed in claim 14, wherein the method (6000) comprising:
receiving, by one or more local entities (700) communicatively coupled to the monitoring server (300), the health data of one or more subjects monitored by the monitoring server (300), and
displaying the received health data on a dashboard (200).
19. The method (6000) as claimed in claim 14, wherein the method comprising:
receiving, by the meta server (800) the health data and the meta data from the one or more monitoring servers (300);
storing the meta data,
wherein the metadata comprising at least one of: patient information, information of at least one wearable apparatus (900), location information of the at least one wearable apparatus (900), user information and episodes for the at least one wearable apparatus (900), user login information, access permissions for the one or more local entities (700) or external entities (750) to access the one or more monitoring servers (300) or the one or more wearable apparatus (900).
20. The method (6000) as claimed in claim 14, wherein the health data of the subject comprises cardiac data comprising electrocardiogram (ECG) signals indicating one or more of: P wave, QRS complex and T wave; Respiration Rate (RR), Heart Rate (HR), Temperature, SpO2 and Blood Pressure Trend (BP), and
wherein the metadata comprises at least one of: data related to the wearable apparatus (900), data related location information, episodes and data related to access information, information about the wearable apparatus (900) comprises an identity (ID) of the wearable apparatus (900), name of the subject associated with each wearable apparatus (900), contact number of the subject, date and time about wearability of each wearable apparatus (900) by the subject, a status of each wearable apparatus (900), information about each wireless device (400) to which the wearable apparatus (900) is connected, and a location information associated with the wearable apparatus (900).
21. The method (6000) as claimed in claim 14, wherein the method (6000) comprising:
fetching, by the routing server (600), the health data from the one or more monitoring servers (300) on demand by one or more external entities (750),
wherein the one or more external entities (750) are configured to:
receive health data through the routing server (600); and
display the health data remotely on a dashboard (200) in real time.
22. The method (6000) as claimed in claim 14, wherein the method (6000) comprising:
fetching health data from the one or more monitoring server (300) on demand by one or more external entities (750);
receiving, the health data from the monitoring server (300) associated with the at least one wearable apparatus (900);
determining, a type of data from the received health data, wherein the type of data comprises at least one of: ECG wave, P wave, QRS complex and T wave; Respiration Rate (RR), Heart Rate (HR), Temperature, SpO2 and Blood Pressure Trend (BP) upon selection of the subject associated with wearable apparatus (900); and
communicating, through one or more communication channels via the communication network (500), the health data from the one or more monitoring servers (300) to the one or more external entities (750) or local entities (700).
23. The method (6000) as claimed in claim 14, wherein the method (6000) comprising:
receiving, analyzing and locally storing the health data and the meta data from the one or more wearable apparatus (900);
providing health data of the one or more wearable apparatus (900) to one or more communicatively coupled local entities (700) for displaying on a dashboard (200) without any connection to additional servers comprising routing server (600) or meta server (800).
24. The method (6000) as claimed in claim 14, wherein the method (6000) comprising:
displaying through a dashboard application (200), health data and alerts to one or more external entities (750) or local entities (700) , wherein the alerts are sent to the one or more external entities (750) or local entities (750) upon one or more conditions, wherein the one or more conditions comprise at least one of: abnormal readings, saving critical minutes in times of emergencies, non-reception of health data from the subject, detection of detachment of the rechargeable patch from the subject, reception of noisy signal, low battery status.