FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
TITLE OF THE INVENTION:
“SYSTEM AND METHOD FOR MONITORING AND MANAGING
INFECTIONS”
APPLICANT –
(a) Name: METROPOLIS HEALTHCARE LIMITED
(b) Nationality: Indian
(c) Address: No 250D, Worli Udyog Bhavan, Hind Cycle Road, Worli, behind Glaxo, Mumbai,
Maharashtra – 400030, India
PREAMBLE TO THE DESCRIPTION
The following specification particularly describes the invention and the manner in which it is
to be performed:
2
FIELD OF INVENTION
[001] The present invention broadly relates to a system and method for monitoring and
managing infections. More particularly, the invention relates to tuberculosis (TB)
monitoring and management by clinical data acquisition complemented with laboratory
results. The invention also relates to decision support systems for management of
infections caused by Mycobacterium species.
BACKGROUND ART
[002] The following 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.
[003] Amongst various challenging diseases affecting human population worldwide,
Tuberculosis (TB) has been one of the most infectious disease with a high mortality
rate if not treated and commonly prevalent in many countries in South-East Asian
Region, African Region, and Western Pacific Region. As per the WHO report, in 2020,
87% of new TB cases occurred in 30 high TB burden countries. Eight countries
accounted for more than two-thirds of the global total: India, Indonesia, China, the
Philippines, Pakistan, Nigeria, Bangladesh and the Democratic Republic of the Congo.
[004] Tuberculosis is usually diagnosed by chest x-ray, acid fast staining on samples and
culture nucleic acid detection and culture. At present, diagnostics in tuberculosis has
many tests which can be divided into different categories such as tests for detection of
M. tuberculosis, tests for identification and tests for drug susceptibility testing. There
exists no single test that deliver all three results with 100% sensitivity and specificity.
The sensitivity and specificity depend upon the site of the sample, time of collection of
the sample, quality of the sample and paucibacillary nature of bacterium at
extrapulmonary sites. Currently, there are gaps in awareness of all available
technologies for accurate diagnosis and patient management leading to delays in the
management of tuberculosis. This coupled with high numbers of cases of multidrug
resistant disease is a serious threat to the National TB elimination program of India.
Another gap is the traceability of patients, although government has advised
3
laboratories to notify tuberculosis so that patients can be traced but this being
unidirectional does not inform the treating doctor/clinician and the patient on the next
best action or line of treatment. Also, this complete information and navigation is not
promptly or readily accessible to the patient and treating doctors.
[005] Further, the use of incorrect/inadequate testing protocol leading to incorrect treatment
regimens is a major problem. To address this the Government of India, under National
Tuberculosis Elimination Program (NTEP) has released new guidelines for
‘programmatic management of drug resistant tuberculosis’ through Nikshay portal.
However, the same is not easily translating to actual patient care scenarios when it
comes to the selection of a test for detection and antibiotic sensitivity testing. In
addition, registration of TB-positive patients on the Nikshay portal is not immediately
actionable due to the manual process involved and doctors are not exposed to the latest
technology. Due to this, the patients have to wait for the next best action.
[006] Another issue is the lack of standardization in the approach to the diagnosis and
evaluation of diagnosed TB patients. Besides this, doctors do not have access to an
algorithmic approach to NTEP recommended treatment-based laboratory panels for
treatment and replacement antibiotics.
[007] Therefore, there is a need for a solution which overcomes the aforesaid limitations and
drawbacks in the available approaches. There is a need for techniques which are user
friendly, enable timely monitoring, and management of TB or other infections that
cause serious prejudice to human life.
SUMMARY
[008] The present disclosure overcomes one or more shortcomings of the prior art and
provides additional advantages. Embodiments and aspects of the disclosure described
in detail herein are considered a part of the claimed disclosure.
[009] In one non-limiting embodiment of the present disclosure, a system to monitor and
manage infections is disclosed. The system comprises a database unit comprising a
plurality of records corresponding to a plurality of entities, wherein each record of the
plurality of records comprises information associated with a plurality of parameters.
The system further comprises a processing unit communicatively coupled to the
4
database unit and comprising an input interface, an output interface, a memory and at
least one processor operatively coupled to one another. In one aspect, the processing
unit is configured to receive via the input interface, identification information of an
entity. The processing unit is further configured to identify the entity as one of: a new
entity and a pre-existing entity by comparing the received identification information of
the entity with the plurality of records. The processing unit is further configured to
receive information corresponding to current symptoms experienced by the entity. The
processing unit is further configured to determine, from the plurality of records, one or
more records corresponding to one or more entities with a stored symptom list having
a highest degree of similarity with the current symptoms experienced by the entity.
Further, the processing unit is configured to selectively analyze the one or more records
to recommend, via the output interface, an infection management plan to the entity
identified as the new entity and selectively analyze the one or more records and a record
present in the database unit corresponding to the entity identified as the pre-existing
entity to recommend, via the output interface, an infection management plan.
[0010] In another non-limiting embodiment of the present disclosure, the plurality of
parameters in each record at least comprises entity name, age, race, gender, location,
genetic factors, single nucleotide polymorphism (SNP), initial symptoms, family
history, medical history, treatment history, contact history, laboratory investigations
and imaging studies.
[0011] In yet another non-limiting embodiment of the present disclosure, to analyze the one or
more records, the processing unit is configured to analyze the medical history, the
treatment history, the laboratory investigations and the imaging studies of each of the
one or more medical records.
[0012] In yet another non-limiting embodiment of the present disclosure, the recommended
infection management plan at least comprises: one or more laboratory investigations to
measure at least one of: biomarkers, physiological markers of the entity and drug
susceptibility and a recommended drug regimen to be initiated for the entity based on
results of the laboratory investigations.
5
[0013] In yet another non-limiting embodiment of the present disclosure, wherein the
laboratory investigations are recommended based on a type of sample being tested and
sensitivity of each laboratory investigation.
[0014] In yet another non-limiting embodiment of the present disclosure, a method for
monitoring and managing infections is disclosed. The method comprises receiving
identification information of an entity. The method further comprises identifying the
entity as one of: a new entity and a pre-existing entity by comparing the received
identification information of the entity with a plurality of records pre-stored in a
database unit. Further, the method comprises receiving information corresponding to
current symptoms experienced by the entity. Further, the method comprises
determining from the plurality of records, one or more records corresponding to one or
more entities with a stored symptom list having a highest degree of similarity with the
current symptoms experienced by the entity. The method further comprises selectively
analyzing the one or more records to recommend an infection management plan to the
entity identified as the new entity and selectively analyzing the one or more records and
a record present in the database unit corresponding to the entity identified as the preexisting entity to recommend an infection management plan.
[0015] In yet another non-limiting embodiment of the present disclosure, analyzing the one or
more records further comprises analyzing the medical history, the treatment history, the
laboratory investigations and the imaging studies of each of the one or more medical
records.
BRIEF DESCRIPTION OF DRAWINGS
[0016] The features, nature, and advantages of the present disclosure will become more
apparent from the detailed description set forth below when taken in conjunction with
the drawings in which like reference characters identify correspondingly throughout.
Some embodiments of system and/or methods in accordance with embodiments of the
present subject matter are now described, by way of example only, and with reference
to the accompanying Figs., in which:
6
[0017] Figures 1A and 1B depict exemplary environments 100A and 100B respectively for
monitoring and managing infections in accordance with an embodiment of the present
disclosure,
[0018] Figure 2 depicts, by way of a block diagram 200, a system to monitor and manage
infections in accordance with an embodiment of the present disclosure,
[0019] Figure 3 depicts, by way of a logic flow diagram 300, a decision-making process
implemented by the system to recommend an infection management plan in accordance
with an embodiment of the present disclosure, and
[0020] Figure 4 depicts, by way of a flowchart, an exemplary method 400 for monitoring and
managing infections in accordance with an embodiment of the present disclosure.
[0021] It should be appreciated by those skilled in the art that any block diagrams herein
represent conceptual views of illustrative systems embodying the principles of the
present subject matter. Similarly, it will be appreciated that any flow charts, flow
diagrams, state transition diagrams, pseudo code, and the like represent various
processes which may be substantially represented in a computer readable medium and
executed by a computer or processor, whether or not such computer or processor is
explicitly shown.
DETAILED DESCRIPTION
[0022] The foregoing has broadly outlined the features and technical advantages of the present
disclosure in order that the detailed description of the disclosure that follows may be
better understood. It should be appreciated by those skilled in the art that the conception
and specific embodiment disclosed may be readily utilized as a basis for modifying or
designing other structures for carrying out the same purposes of the present disclosure.
[0023] The novel features which are believed to be characteristic of the disclosure, both as to
its organization and method of operation, together with further objects and advantages
will be better understood from the following description when considered in connection
with the accompanying figures. It is to be expressly understood, however, that each of
the figures is provided for the purpose of illustration and description only and is not
intended as a definition of the limits of the present disclosure.
7
[0024] Amongst various infectious diseases, tuberculosis (TB) is one that is highly widespread
and requires extensive techniques to diagnose it and further requires long and targeted
treatment to manage the disease. However, gaps in awareness of all available
technologies for accurate diagnosis and patient management lead to delays in the
management of tuberculosis. Another gap is the traceability of patients, leading to the
treating doctor/clinician not being able to guide the patients on the next best action or
line of treatment. Further, the use of incorrect/inadequate testing protocol leading to
incorrect treatment regimens is a major problem. Another issue is the lack of
standardization in the approach to the diagnosis and evaluation of diagnosed TB
patients.
[0025] In order to overcome the above-mentioned challenges, the present disclosure provides
a system and a method to monitor and manage infections. In particular, the present
disclosure provides a system that uses historical data of a plurality of patients
(hereinafter referred to as entities) to assess current symptoms of an entity in order to
recommend an infection management plan. A detailed description of the proposed
solution is explained in the forthcoming paragraphs in conjunction with Figures 1-3.
[0026] Figures 1A and 1B depict exemplary environments 100A and 100B respectively for
monitoring and managing infections in accordance with an embodiment of the present
disclosure. In particular, Figures 1A and 1B depict two different scenarios for
recommending an infection management plan based on the type of entity. For instance,
figure 1A depicts a scenario where entity 102 is a new entity, i.e., there does not exist
any historical data for him/her. On the other hand, figure 1B depicts a scenario where
entity 104 is a pre-existing entity, i.e., the entity 104 was previously diagnosed with TB
and thus has historical data associated with him/her. A detailed explanation of the
exemplary environments 100A and 100B is provided in the forthcoming paragraphs in
conjunction with Figures 2 and 3.
[0027] Figure 2 depicts by way of a block diagram 200 an exemplary system to monitor and
manage infections. A system 202 may include various elements such as a database unit
204 and a processing unit 206. The database unit 204 and the processing unit 206 may
communicate with each other over wired or wireless link.
8
[0028] According to an exemplary embodiment of the present disclosure, the database unit 204
may comprise a plurality of records corresponding to a plurality of entities diagnosed
with TB, in such a manner that each entity has a record associated with him/her. Further,
each record may comprise information associated with a plurality of parameters. In an
exemplary embodiment, the plurality of records stored in the database unit 204 may
represent historical data of the past several years and may include information
corresponding to a plurality of parameters, including but not limited to patient
information, symptoms, types of tests that may be carried out to identify the diseases,
diseases, test results, treatment provided to the patients, location, etc. but not limited
thereto. In an embodiment, the patient information may comprises one or more of
following, but not limited to, age, race, gender, location, genetic factors, single
nucleotide polymorphism (SNP), family history, medical history, treatment history,
contact history, other laboratory investigation and imaging studies. Further, each record
pertaining to an individual entity may be assigned a unique ID.
[0029] In another exemplary embodiment, the database unit 204 may also include information
about the infection/disease. The information about the disease may include
one of pathogenicity, mode of infection, therapeutic efficacy, mortality, recovery
period, cost of treatment, infectivity, infection rate, and past outbreaks. In yet another
embodiment, the data in the database unit 204 may be updated periodically.
[0030] Further, the processing unit 206 may include an input interface 208, a memory 210, at
least one processor 212 and an output interface 214 communicatively coupled to one
another. The at least one processor 212 may be configured to receive one or more inputs
via the input interface 208, process the same and provide one or more outputs via the
output interface 214.
[0031] In one exemplary embodiment, the processing unit 206, via the input interface 208, may
receive identification information of an entity and may identify the entity as a new
entity 102 or a pre-existing entity 104. In one exemplary aspect, if the entity is a preexisting entity 104, the processing unit 206 may receive his/her entity ID. Alternatively,
if the entity 104 does not remember his/her entity ID or if the entity ID is not provided,
the processing unit 206 may receive other identification information such as name, age,
address, Aadhar card number etc. Upon establishing that the entity is a pre-existing
9
entity 104, the processing unit 206 may fetch his/her record from the database unit 202
and store them in the memory 210 for future use. However, if the processing unit 206
identifies the entity as a new entity 102, it may create a new entity ID for him/her and
store it in the memory 210 for future use.
[0032] Further, as depicted in exemplary environments 100A and 100B, irrespective of
whether the entity is a new entity 102 or a pre-existing entity 104, the processing unit
206 may receive information corresponding to current symptoms being experienced by
the entity 102, 104.
[0033] Now, if the entity is the new entity 102, the processing unit 206 may determine, from
the plurality of records stored in the database unit 202, one or more records
corresponding to one or more entities with initial symptom list similar to those
experienced by the entity 102. For instance, as depicted in exemplary environment
100A, out of the plurality of records corresponding to entities X, Y, Z, A, B and C, the
processing unit 206 may determine that entities X and A had the most similar symptoms
to the symptoms being experienced by the entity 102. The processing unit 206 may then
analyze the records corresponding to the entities X and A to recommend an infection
management plan for the entity 102. For instance, the processing unit 206 may analyze
the medical history, the treatment history, the laboratory investigations and the imaging
studies of the entities X and A to recommend the infection management plan. In one
exemplary embodiment, the processing unit 206 may recommend the infection
management plan in stages. For instance, at first stage, the processing unit 206 may
recommend a series of laboratory investigations to get an indication of entity’s
condition. In one aspect, the series of laboratory investigations may comprise
measuring biomarkers. Further, considering the infection to be TB, the biomarker(s)
comprises but not limited to detection of bacterium by culture, detection of bacterium
by genes IS6110, IS1081 and genetic markers for drugs resistance by mutation in rpo
B, hA, KatG, eth A/B/C, rpsA, pncA, rrs, tlyA, eis, gyrA/B, rrl, thyA, Rv0678, atpE,
Rv1979c, pepQ, fgd1, fbiC, fbiA, ddn, Adenosine deaminase level, but not limited
thereto. Furthermore, the biomarkers are measured in a body fluid sample from the
entity. Non-limiting exemplary body fluids include blood, plasma, serum, sputum,
urine, feces, semen, mucus, lymph, saliva, or nasal washes. Biomarkers may be
measured in culture isolates of mycobacterium. In another aspect, the series of
10
laboratory investigations may comprise weight, body temperature, respiratory rate,
hemoglobin, liver function, kidney function, eyes, heart rate, blood pressure, ECG, etc.
[0034] In the next stage, based on the results of the series of laboratory investigations, the
processing unit 206 may provide appropriate information for the next best test be it
detection or drug susceptibility testing based on the analysis of the one or more records
(for instance those corresponding to entities X and A) and the current test results. The
processing unit 206 may provide information about the right sample type and
technology to be used that helps with optimum quality and avoids misdiagnosis. The
processing unit 206 may further provide a standardized test selection thus reducing cost
by avoiding incorrect/excessive testing. The processing unit 206 may output, via the
output interface 214, the various tests as per decreasing order of sensitivity considering
the sample being tested. The processing unit 206 may also provide, via the output
interface 214, the antitubercular drug testing panels with details of drugs tested.
[0035] In an embodiment, the system 202 may thus provide a complete infection management
plan including tests and appropriate drug regimen for the entity 102 to assist the entity
as well as the treating physician. In an embodiment, the system 202 may determine and
share the output to various user devices such as a mobile device, a laptop, a desktop, a
personal assistance device, etc., but not limited thereto. It may be noted by a skilled
person that the infection management plan may be updated periodically based on
entity’s current condition, reaction to drugs and new advances in drug regimen.
[0036] In another embodiment, if the entity is a pre-existing entity 104, the processing unit 206
may determine, from the plurality of records stored in the database unit 202, one or
more records corresponding to one or more entities with initial symptom list similar to
those experienced by the entity 102. For instance, as depicted in exemplary
environment 100B, out of the plurality of records corresponding to entities X, Y, Z, A,
B and C, the processing unit 206 may determine that entities Y and B had the most
similar symptoms to entity 104. The processing unit 206 may then analyze the records
corresponding to entities Y and B and may also analyze the record corresponding to
entity 104 that was fetched from the database unit 204 and stored in the memory 210 to
recommend an infection management plan to entity 104.
11
[0037] In particular, to recommend an infection management plan to entity 104, the processing
unit 206 may follow an extensive decision-making process 300 as illustrated by way of
a logic flow diagram in Figure 3. For instance, at block 302, the process 300 may
comprise determining whether the entity 104 had a previous case of exposure/treatment
to MDR (Multi-drug resistant) TB. If the result of the determination is YES, the process
300 shall proceed to step 304 and if the result of the determination is NO, the process
shall proceed to step 306.
[0038] At block 304, the process 300 may determine whether the type of MDR-TB was
pulmonary or extrapulmonary and based on the determination may recommend either
tests 350 or tests 352.
[0039] At block 306, the process 300 upon determining that the entity 104 does not have a
history of exposure to MDR-TB, may recommend different tests. In one embodiment,
the tests may differ based on sample type. Further, based on the results of the tests, the
process 300 may either recommend drug susceptibility test (block 308) or may
recommend a drug regimen (block 310).
[0040] Further, in another embodiment, the processing unit 206 may adopt the above-described
decision-making process 300 in conjunction with the analysis of the records
corresponding to entities Y and B (with the most similar symptoms to entity 104) to
recommend the infection management plan. It may be noted by a skilled person that the
infection management plan may be updated periodically based on entity’s current
condition, reaction to drugs and new advances in drug regimen.
[0041] Hence, the system 202 may provide a standardized approach for managing an infection
including but not limited to TB.
[0042] Figure 4 illustrates a flowchart of an exemplary method 400 for monitoring and
managing infections in accordance with an embodiment of the present disclosure. The
method 400 may also be described in the general context of computer executable
instructions. Generally, computer executable instructions may include routines,
programs, objects, components, data structures, procedures, modules, and functions,
which perform specific functions or implement specific abstract data types.
12
[0043] The order in which the method 400 is described is not intended to be construed as a
limitation, and any number of the described method blocks may be combined in any
order to implement the method. Additionally, individual blocks may be deleted from
the methods without departing from the spirit and scope of the subject matter described.
[0044] At step 402, the method 400 may include receiving identification information of an
entity. In one embodiment, for receiving identification information, the input interface
208 of the processing unit 206 may be used. Further, in one exemplary aspect, the
identification information may comprise name, age, address, Aadhar card number,
entity ID etc.
[0045] At step 404, the method 400 may include identifying the entity as one of: a new entity
102 and a pre-existing entity 104 by comparing the received identification information
of the entity with a plurality of records pre-stored in the database unit 202. In one
exemplary aspect, upon establishing that the entity is a pre-existing entity 104, the
processing unit 206 may fetch his/her record from the database unit 202 and store them
in the memory 210 for future use. However, if the processing unit 206 identifies the
entity as a new entity 102, it may create a new entity ID for him/her and store it in the
memory 210 for future use.
[0046] At step 406, the method 400 may include receiving information corresponding to
current symptoms experienced by the entity. In one embodiment, for receiving said
information, the input interface 208 of the processing unit 206 may be used.
[0047] At step 408, the method 400 may include determining from the plurality of records, one
or more records corresponding to one or more entities with a stored symptom list having
a highest degree of similarity with the current symptoms experienced by the entity. In
one embodiment, for said determining, the processing unit 206 may be used.
[0048] At step 410, the method 400 may include selectively analyzing the one or more records
to recommend, via the output interface, an infection management plan to the entity
identified as the new entity 102. In one embodiment, for said analyzing the processing
unit 206 may be used.
13
[0049] At step 412, the method 400 may include selectively analyzing the one or more records
and a record present in the database unit corresponding to the entity identified as the
pre-existing entity 104 to recommend, via the output interface 214, an infection
management plan. In one embodiment, for said analyzing the processing unit 206 may
be used.
[0050] The illustrated steps are set out to explain the exemplary embodiments shown, and it
should be anticipated that ongoing technological development will change the manner
in which particular functions are performed. These examples are presented herein for
purposes of illustration, and not limitation. Further, the boundaries of the functional
building blocks have been arbitrarily defined herein for the convenience of the
description. Alternative boundaries can be defined so long as the specified functions
and relationships thereof are appropriately performed.
[0051] Furthermore, one or more computer-readable storage media may be utilized in
implementing embodiments consistent with the present disclosure. A computerreadable storage medium refers to any type of physical memory on which information
or data readable by a processor may be stored. Thus, a computer-readable storage
medium may store instructions for execution by one or more processors, including
instructions for causing the processor(s) to perform steps or stages consistent with the
embodiments described herein. The term “computer- readable medium” should be
understood to include tangible items and exclude carrier waves and transient signals,
i.e., are non-transitory. Examples include random access memory (RAM), read-only
memory (ROM), volatile memory, non-volatile memory, hard drives, CD ROMs,
DVDs, flash drives, disks, and any other known physical storage media.
[0052] Suitable processors include, by way of example, a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor (DSP), a graphic
processing unit (GPU), a plurality of microprocessors, one or more microprocessors in
association with a DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any
other type of integrated circuit (IC), and/or a state machine.
14
We Claim:
1. A system (202) to monitor and manage infections, the system comprising:
a database unit (204) comprising a plurality of records corresponding to a
plurality of entities, wherein each record of the plurality of records comprises
information associated with a plurality of parameters; and
a processing unit (206) communicatively coupled to the database unit (204) and
comprising an input interface (208), an output interface (214), a memory (210) and at
least one processor (212) operatively coupled to one another, wherein the processing
unit (206) is configured to:
receive via the input interface (208), identification information of an
entity;
identify the entity as one of: a new entity (102) and a pre-existing entity
(104) by comparing the received identification information of the entity with the
plurality of records;
receive information corresponding to current symptoms experienced by
the entity;
determine, from the plurality of records, one or more records
corresponding to one or more entities with a stored symptom list having a highest
degree of similarity with the current symptoms experienced by the entity; and
selectively:
analyze the one or more records to recommend, via the output
interface (214), an infection management plan to the entity identified as the new
entity (102); and
analyze the one or more records and a record present in the
database unit corresponding to the entity identified as the pre-existing entity (104)
to recommend, via the output interface (214), an infection management plan.
2. The system as claimed in claim 1, wherein the plurality of parameters in each record at
least comprises entity name, age, race, gender, location, genetic factors, single
nucleotide polymorphism (SNP), initial symptoms, family history, medical history,
treatment history, contact history, laboratory investigations and imaging studies.
3. The system as claimed in claim 1, wherein to analyze the one or more records, the
processing unit (206) is configured to:
analyze the medical history, the treatment history, the laboratory investigations
and the imaging studies of each of the one or more medical records.
4. The system as claimed in claim 1, wherein the recommended infection management
plan at least comprises:
laboratory investigations to measure at least one of: biomarkers, physiological
markers of the entity and drug susceptibility; and
recommended drug regimen to be initiated for the entity based on results of the
laboratory investigations.
15
5. The system as claimed in claim 1, wherein the laboratory investigations may be
recommended based on: a type of sample being tested and sensitivity of each laboratory
investigation.
6. A method (400) for monitoring and managing infections, the method comprising:
receiving (402) identification information of an entity;
identifying (404) the entity as one of: a new entity (102) and a pre-existing entity
(104) by comparing the received identification information of the entity with a plurality
of records pre-stored in a database unit (202);
receiving (406) information corresponding to current symptoms experienced by
the entity;
determining (408) from the plurality of records, one or more records
corresponding to one or more entities with a stored symptom list having a highest
degree of similarity with the current symptoms experienced by the entity; and
selectively:
analyzing (410) the one or more records to recommend an infection
management plan to the entity identified as the new entity (102); and
analyzing the one or more records and a record present in the database unit
(202) corresponding to the entity identified as the pre-existing entity (104) to
recommend an infection management plan.
7. The method as claimed in claim 6, wherein the plurality of parameters in each record
at least comprises entity name, age, race, gender, location, genetic factors, single
nucleotide polymorphism (SNP), initial symptoms, family history, medical history,
treatment history, contact history, laboratory investigations and imaging studies.
8. The method as claimed in claim 6, wherein analyzing the one or more records further
comprises:
analyzing the medical history, the treatment history, the laboratory investigations
and the imaging studies of each of the one or more medical records.
9. The method as claimed in claim 6, wherein the recommended infection management
plan at least comprises:
laboratory investigations to measure at least one of: biomarkers, physiological
markers of the entity and drug susceptibility; and
recommended drug regimen to be initiated for the entity based on results of the
laboratory investigations.
10. The method as claimed in claim 6, wherein the laboratory investigations may be
recommended based on a type of sample being tested and sensitivity of each laboratory
investigation.