Public health surveillance

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Public health surveillance (also epidemiological surveillance, clinical surveillance or syndromic surveillance) is, according to the World Health Organization (WHO), "the continuous, systematic collection, analysis and interpretation of health-related data needed for the planning, implementation, and evaluation of public health practice."[1] Public health surveillance may be used to "serve as an early warning system for impending public health emergencies; document the impact of an intervention, or track progress towards specified goals; and monitor and clarify the epidemiology of health problems, to allow priorities to be set and to inform public health policy and strategies."[1]

The term applies to surveillance of populations and is distinct from active surveillance, which applies to individuals.

Techniques of public health surveillance have been used in particular to study infectious diseases. Many large institutions, such as the WHO and the CDC, have created databases and modern computer systems (public health informatics) that can track and monitor emerging outbreaks of illnesses such as influenza, SARS, HIV, and even bioterrorism, such as the 2001 anthrax attacks in the United States.

Many regions and countries have their own cancer registry, one function of which is to monitor the incidence of cancers to determine the prevalence and possible causes of these illnesses.

Other illnesses such as one-time events like stroke and chronic conditions such as diabetes, as well as social problems such as domestic violence, are increasingly being integrated into epidemiologic databases called disease registries that are being used in cost-benefit analysis in determining governmental funding for research and prevention.

Systems that can automate the process of identifying adverse drug events, are currently being used, and are being compared to traditional written reports of such events.[2] These systems intersect with the field of medical informatics, and are rapidly becoming adapted by hospitals and endorsed by institutions that oversee healthcare providers (such as JCAHO in the United States). Issues in regards to healthcare improvement are evolving around the surveillance of medication errors within institutions.[3]

Syndromic surveillance

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Syndromic surveillance is the analysis of medical data to detect or anticipate disease outbreaks. According to a CDC definition, "the term 'syndromic surveillance' applies to surveillance using health-related data that precede diagnosis and signal a sufficient probability of a case or an outbreak to warrant further public health response. Though historically syndromic surveillance has been utilized to target investigation of potential cases, its utility for detecting outbreaks associated with bioterrorism is increasingly being explored by public health officials."[4]

The first indications of disease outbreak or bioterrorist attack may not be the definitive diagnosis of a physician or a lab.

Using a normal influenza outbreak as an example, once the outbreak begins to affect the population, some people may call in sick for work/school, others may visit their drug store and purchase medicine over the counter, others will visit their doctor's office and other's may have symptoms severe enough that they call the emergency telephone number or go to an emergency room.

Syndromic surveillance systems monitor data from school absenteeism logs, emergency call systems, hospitals' over-the-counter drug sale records, Internet searches, and other data sources to detect unusual patterns. When a spike in activity is seen in any of the monitored systems disease epidemiologists and public health professionals are alerted that may be an issue.

An early awareness and response to a bioterrorist attack could save many lives and potentially stop or slow the spread of the outbreak. The most effective syndromic surveillance systems automatically monitor these systems in real-time, do not require individuals to enter separate information (secondary data entry), include advanced analytical tools, aggregate data from multiple systems, across geo-political boundaries and include an automated alerting process.[5]

A syndromic surveillance system based on search queries was first proposed by Gunther Eysenbach, who began work on such a system in 2004.[6] Inspired by these early, encouraging experiences, Google launched Google Flu Trends[7] in 2008. More flu-related searches are taken to indicate higher flu activity. The results closely match CDC data, and lead it by - 1–2 weeks. The results appeared in Nature.[8] More recently, a series of more advanced linear and nonlinear approaches to influenza modelling from Google search queries have been proposed.[9] Extending Google's work researchers from the Intelligent Systems Laboratory (University of Bristol, UK) created Flu Detector;[10] an online tool which based on Information Retrieval and Statistical Analysis methods uses the content of Twitter to nowcast flu rates in the UK.[11]

Influenzanet

Influenzanet is a syndromic surveillance system based on voluntary reports of symptoms via the internet. Residents of the participant countries are invited to provide regular reports on the presence or absence of flu related symptoms. The system has been in place and running since 2003 in the Netherlands and Belgium. The success of this first initiative led to the implementation of Gripenet in Portugal in 2005 followed by Italy in 2008 and Brasil, Mexico, and the United Kingdom in 2009.

Laboratory-based surveillance

Some conditions, especially chronic diseases such as diabetes mellitus, are supposed to be routinely managed with frequent laboratory measurements. Since many laboratory results, at least in Europe and the US, are automatically processed by computerized laboratory information systems, the results are relatively easy to inexpensively collate in special purpose databases or disease registries. Unlike most syndromic surveillance systems, in which each record is assumed to be independent of the others, laboratory data in chronic conditions can be theoretically linked together at the individual patient level. If patient identifiers can be matched, a chronological record of each patient's laboratory results can be analyzed as well as aggregated to the population level.

Laboratory registries allow for the analysis of the incidence and prevalence of the target condition as well as trends in the level of control. For instance, an NIH-funded program called the Vermedx Diabetes Information System[12] maintained a registry of laboratory values of diabetic adults in Vermont and northern New York State in the US with several years of laboratory results on thousands of patients.[13] The data included measures of blood sugar control (glycosolated hemoglobin A1C), cholesterol, and kidney function (serum creatinine and urine protein), and were used to monitor the quality of care at the patient, practice, and population levels. Since the data contained each patient's name and address, the system was also used to communicate directly with patients when the laboratory data indicated the need for attention. Out of control test results generated a letter to the patient suggesting they take action with their medical provider. Tests that were overdue generated reminders to have testing performed. The system also generated reminders and alerts with guideline-based advice for the practice as well as a periodic roster of each provider's patients and a report card summarizing the health status of the population. Clinical and economic evaluations of the system, including a large randomized clinical trial, demonstrated improvements in adherence to practice guidelines and reductions in the need for emergency room and hospital services as well as total costs per patient.[14][15][16] The system has been commercialized and distributed to physicians, insurers, employers and others responsible for the care of chronically ill patients. It is now being expanded to other conditions such as chronic kidney disease.

A similar system, The New York City A1C Registry,[17] is in used to monitor the estimated 600,000 diabetic patients in New York City, although unlike the Vermont Diabetes Information System, there are no provisions for patients to have their data excluded from the NYC database. The NYC Department of Health and Mental Hygiene has linked additional patient services to the registry such as health information and improved access to health care services. As of early 2012, the registry contains over 10 million test results on 3.6 million individuals. Although intended to improve health outcomes and reduce the incidence of the complications of diabetes,[18] a formal evaluation has not yet been done.

In May 2008, the City Council of San Antonio, Texas approved the deployment of an A1C registry for Bexar County. Authorized by the Texas Legislature and the state Health Department, the San Antonio Metropolitan Health District[19] implemented the registry which drew results from all the major clinical laboratories in San Antonio. The program was discontinued in 2010 for lack of funds.

Laboratory surveillance differs from population-wide surveillance in that it can only monitor patients who are already receiving medical treatment and therefore having lab tests done. For this reason, it does not identify patients who have never been tested. Therefore, it is more suitable for quality management and care improvement than for epidemiological monitoring of an entire population or catchment area.

See also

References

  1. 1.0 1.1 Public health surveillance, World Health Organization (accessed January 14, 2016).
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. disa.mil PDF
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. United States Centers for Disease Control and Prevention (WebCited/cached version)
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. [1] Archived June 9, 2007 at the Wayback Machine
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.