Demonstrating Collect once, Use Many Assimilating Public Health Secondary Data Use Requirements into an Existing Domain Analysis Model
|
|
- Ashley Golden
- 5 years ago
- Views:
Transcription
1 Demonstrating Collect once, Use Many Assimilating Public Health Secondary Data Use Requirements into an Existing Domain Analysis Model Cynthia Barton, RN 1, Crystal Kallem, RHIA 2, Patricia Van Dyke, RN 3, Donald Mon, PhD 2, Rachel Richesson, PhD 4 1 Duke University School of Nursing, Durham, NC; 2 American Health Information Management Association, Chicago, IL; 3 Delta Dental Plans Association, Portland, OR; 4 Division of Bioinformatics and Biostatistics, University of South Florida, College of Medicine, Department of Pediatrics, Tampa, FL Abstract The healthcare industry has an increasing need for clinical data content standards to support patient care and data re-use in areas such as research, quality and public health. The Diabetes Data Strategy (Diabe-DS) project was formed in 2009 by the HL7 EHR Working Group to demonstrate a repeatable process that identifies disease-specific Common Data Elements (CDEs) for clinical care and secondary use. The Diabe-DS project previously developed a set of important CDEs and supporting data models for clinical care, quality and research uses of diabetes data. This paper will describe the process for identifying the data elements and activities required for public health use of clinical data, and mapping them to Diabe-DS CDEs, use case and data models. The result is a model for consideration which provides data needed in the immediate clinical environment of care, and supports the use of data for multiple uses. Introduction The healthcare industry has an increasing need for clinical data to support both patient care and data re-use. The areas of disease surveillance, population health, quality measurement and clinical research have a need to define and harmonize clinical data content standards (e.g., Common Data Elements, Domain Analysis Models) which can support both patient care and secondary data uses. The notion of meaningful secondary use as a means to improve the quality, safety, and efficiency of healthcare is an important theme in current national information infrastructure discussions. 1 Central to any discussion of meaningful secondary use are the topics of interoperability and data standards. The Diabetes Data Strategy (Diabe-DS) proof-of-concept project was formed in 2009 by the Health Level Seven International (HL7) EHR Working Group with the objective to demonstrate a repeatable process that identifies disease-specific Common Data Elements (CDEs) for clinical care and secondary use. This project provides a framework for the collect once, use many times paradigm for a national health information strategy. The process will inform other domain specific groups wanting to develop content standards for clinical documentation that can support multiple uses, such as research, quality measurement, public health, reimbursement and others. The Diabe-DS (Diabetes Data Strategy) project focuses on Type 1 Diabetes (T1D) assessment in an ambulatory setting. This project is a pilot demonstration to show how data re-use might work and to develop a method to inform subsequent content standards efforts. The Diabe-DS project team has created a set of common data elements, a comprehensive suite of use cases, and UML models that can be used by application developers to support applications for T1D data collection that address multiple data uses. In addition, the team has identified relationships between these models and other standard models, such as the Healthcare Information Technology Standards Panel (HITSP) medication model 2 (used in developing data interoperability use cases for the US Office of the National Coordinator). Diabe-DS began by examining clinical data elements that could be used to support the secondary uses of research and quality measurement. The purpose of this work is to present the process used to incorporate the public health requirements (as another secondary use) into the Diabe-DS project. This paper will first discuss public health data requirements and uses for the data in relation to diabetes. Subsequently, the following processes will be described: the process of writing a public health use case and incorporating the use case into the already created suite of use cases, identifying the data elements needed, and mapping the data elements to the use case and the existing Diabe-DS domain analysis model. 98
2 Background Diabetes Data Standards and Diabe-DS Diabetes is a prevalent disease with high morbidity and growing incidence worldwide. A lack of domain standards for diabetes data collection exists in clinical, research, and public health settings. 3,4 This same lack of standards prevents the collect once, use many approach to diabetes data collection on both a personal and a national scale. Data standards for the uniform collection of diabetes data will support the various secondary uses that can improve our understanding of the disease, and identify new treatments and best practices that will improve the health and quality of life for millions. The early work of the Diabe-DS team explored locally developed EHR entry interfaces for diabetes clinics and saw little commonality. Similarly, the review of research data collection forms used in a spectrum of multi-site diabetes investigations showed little standardization of diabetes specific data elements. The National Quality Forum 5 (NQF), in collaboration with quality measure stewards, has expressed multiple diabetes quality measures for use in the electronic environment. 6 The NQF has done significant work to express the data requirements for these quality measures in a way that enables the extraction of clinical data from EHRs. Specifically, the quality measures are translated into multiple data elements that represent the units of clinical data collection. The Diabe-DS project leveraged this work, and selected two measures (Diabetes Care HbA1c Control and Diabetic Foot Exam) to demonstrate the harmonization of clinical and quality data elements to a single standard that would support both functions. Rather than risk creating different diabetes-specific data elements for each secondary purpose (e.g., quality, research, public health), the Diabe-DS group is attempting to harmonize data capture requirements across various secondary uses. The Diabe-DS project was designed to be a proof-of-concept focused on creating a narrow set of artifacts, processes and methodologies applied to a similarly narrow context: the collection of pediatric T1D assessment data in an outpatient clinic setting (patient care) that can support related clinical research, quality measurement and population health activities (all secondary uses). 7 Within the domain of T1D, the project strives to harmonize the data elements that support these three secondary uses. This includes a set of data elements that are required for various secondary uses and mappings or relationships to the data as would be captured in electronic medical records. Additionally, the team developed a comprehensive suite of use cases that address the primary data collection as well as each of the secondary uses. These use cases illustrate the uniform collection of a set of data elements, and their subsequent re-use in multiple (secondary use) scenarios. An intentional and continuous theme throughout the Diabe-DS work is the requisite to leverage any previous work, including existing UML models for patient care, such as the medication model from HITSP. 2 Common data elements A Common Data Element, or CDE, is a question or unit of data collection that is represented uniformly across one or more applications and which has value across multiple settings or contexts. A common ISO definition of a data element is used which includes the name of the data element, the values and the definition. In HL7, a primary developer of EHR data standards, CDEs are related to a specific Domain Analysis Model (DAM), which is required to support the development of HL7-based messages in a particular disease or application area. The premise of HL7 is that CDEs should inform the development of a model constructed from the information units, communication requirements and clinical workflows of a domain. HL7 considers Domain Analysis Models to be conceptual representations of these tasks and information units against which software can be defined and evaluated. Both CDEs and DAMs are considered part of clinical data content standards in HL7. DAM development is a component of the HL7 Healthcare Development Framework. 8 Typically common data elements refer to a disease domain or therapeutic area, such as Tuberculosis or Cardiovascular care. The Diabe-DS project constrains the notion of common in CDEs even further, and collects data elements that are common to both primary (clinical documentation) and one or more secondary uses within the Type 1 Diabetes domain. The specification of common data capture requirements to support T1D care and data re-use includes narrative use cases that describe the primary data capture at the clinical encounters and the secondary uses, in addition to clearly defined data elements and the data models that relate them. Although there are many domain-specific CDE projects (both in and outside of HL7 organization) there are few published methods to guide these efforts. The Pre-op Anesthesia core dataset project 9 and the National Cancer Institute s Early Detection Research Network 10 have presented their experience identifying and vetting data 99
3 elements within a medical domain. The Tuberculosis and Cardiovascular HL7 DAM 11,12 projects were both intended to be informative demonstrations of developing domain-specific content standards and supporting artifacts (activity diagram, UML models) required by HL7 to support various messaging applications. They provide guidance for the number of communications, type of correspondence and other means to engage a clinical community in the process of identifying CDEs. However, the authors are not aware of other projects or methods that focus on harmonizing data elements across primary and secondary uses, or that focus on the development (and harmonization) of supporting data models and narrative use cases. The Diabe-DS project has presented its approach, 7,13 and this paper focuses on the specific problem of adding a new secondary use to existing multi-use models. Public health represents an important secondary use for clinical data and the incorporation of public health uses in the Diabe-DS collect once, use many times scenario was critical to the success of the project. Public Health In order to identify the data needs of public health for Type 1 Diabetes it was necessary to gain a better understanding of the public health domain, including objectives, activities and data requirements for public health - e.g., how it uses the data it receives from clinicians, and the problems related to data usage within the domain of public health itself. The public health community has been actively pursuing standards that further its mission and that recognize public health as part of a bigger system of interoperable data. As such, the public health data standards community has previously articulated its mission, specific objectives, and activities as they relate to primary data collection. 4 This widely vetted, clearly articulated, and carefully documented work of public health data requirements collectively facilitated the Diabe-DS project team s work described here. The documents cited in this section informed the expansion of Diabe-DS artifacts to address public health as a secondary use. Public Health has a mission to assure conditions in which people may be healthy. 14 The scope of public health is both population-based and patient-centric, and in order to fulfill its mission health care providers and public health agencies must be able to exchange pertinent health data about both individuals and communities. 4 Many information systems used by public health agencies have been in place since before standards for information exchange existed and are not capable of exchanging data electronically within agency programs, much less with healthcare providers. 3,4 Although limited resources are a persistent challenge, public health agencies are continuously improving capabilities to send, receive and exchange data with clinical practices. Public health information needs must be taken into account during development of data standards in order for them to be able to send, receive and exchange relevant data with EHR systems as the public health systems are upgraded. In order to fulfill the functions of public health, agencies need to receive and analyze data gathered at the patient s point-of-care. Until now, agencies have primarily relied on health care providers to actively submit data to public health departments using specific forms populated by healthcare providers, either with data from their EHR or free text from paper charts. Whether the data is parsed from free text or populated from the EHR it may not be standardized. 3,4 Further, healthcare providers normally do not receive data back from public health agencies that impacts individual patient care. In other words, there generally are not productive information exchanges between healthcare providers and public health, although there is potential for bi-directional data exchanges. Populationbased data aggregated by public health agencies and sent back to providers can assist them in decision making to improve patient care and outcomes. Similarly, the clinical data can be used by public health to identify community resources that are needed to give patients more options for healthy living and disease prevention. 15 Public health s involvement in chronic disease care management, surveillance and prevention is supported with disease-specific registries. These registries contain information about prevalence, trends, and risk factors among a population. The registries are populated with the data sent from clinical settings, mostly via the forms described above. Some may be submitted through web-based portals or collected through surveys. 16 Standardization of the CDEs in disease-specific domains such as T1D will allow multiple healthcare providers and EHR systems to submit standardized data to public health, and enable the development of standardized chronic disease registries. Public health could then use these standardized registries for diabetes care management and surveillance as well as to inform health promotion interventions and guidelines to support clinical practice. 4,17 Additionally, the receipt of current and standardized data from various EHR systems using Diabe-DS data elements could enable public health to develop standard and population-based approaches to monitor the health and services of this population, and to develop interventions that support effective management of the disease. 100
4 Adding public health requirements to existing data capture specifications The Public Health Data Standards Consortium (PHDSC) has focused for many years on identifying needs and opportunities for interoperability with EHRs and public health. 4,17 This group has been a consensus organization, working to engage many and distributed public health experts to develop a collective sense of purpose and needs and has documented their work very clearly. The PHDSC used a Functional Requirements Analysis Document (FRAD) methodology to identify common data sets and use cases for exchange of diabetes care management and surveillance data between Wisconsin clinical care and public health information systems. 18,19 The same methodology was used for common data sets for interoperability between New York City schools and syndrome surveillance with clinical care records. 20 These were closely examined as was the public health interoperability specification document prepared by the Health Information Technology Standards Panel (HITSP). 21 Earlier disease specific data standardization efforts conducted within the HL7 organization also provide important background for the Diabe-DS project and any domain-specific CDE. These projects were done by disease experts in the domains of Tuberculosis and Cardiovascular Disease and a set of data elements and HL7 domain analysis models were described for each disease area. 11,12 While the methods of these CDE projects were carefully documented and did serve as a good starting point for the Diabe-DS project, these projects represented first run CDE projects and were not concerned with re-using or harmonizing existing data elements (that might overlap with other domains) nor do they have any coverage on harmonizing use cases and data models across multiple secondary uses. This is an important challenge that all CDE projects will face, and one very germane to the Diabe-DS project. From the onset, the Diabe-DS team documented detailed processes, strategic decisions, and examples of specific data elements that were selected, excluded, revised, or harmonized. These examples should inform future disease specific data standards efforts, as well as inform solutions that encourage future re-use and harmonization across disease domains. METHODS The literature was reviewed to identify public health s data needs for T1D which needed to be included in the Diabe- DS CDEs. In order to understand best practice and public health boundaries, the Diabe-DS team reviewed current clinical practice guidelines for T1D, including the ADA Clinical Practice Guidelines for Diabetes Care 22 and the Wisconsin Diabetes Mellitus Care Guidelines. 23 The public health community s defined data requirements and public health secondary use case 17 served as the foundation and starting point for this project. The primary task was to assess and integrate the public health community s consensus data requirements and activities within the framework of the Diabe-DS project. The original PHDSC work was comprehensive, addressed many public health activities, and only addressed clinical data capture for public health needs. For purposes of the Diabe-DS demonstration, a more limited view of a single public health activity was needed, and one that was heavily inspired by previous PHDSC work. A separate use case was developed by the Diabe-DS team to identify the actors and the workflow of Public Health. This allowed the team to conceptualize which of the public health data elements would have overlap with both the clinical care scenario (describing primary data capture) or the previously-defined secondary uses (research and quality). This use case, plus existing Diabe-DS use cases, provided a lens to identify CDEs that were important to public health and the Diabe-DS demonstration project. The public health use case was incorporated into the suite of use cases already written by the Diabe-DS project team. The Diabe-DS project team informed the remainder of the steps for incorporating public health s data needs based upon their current approach to the project. Specifically, the tasks for the project included: 1. Develop a public health use case, using existing PHDSC materials 2. Examine the existing (n=250) T1D CDEs identified by the Diabe-DS project to determine which fit with public health secondary data needs 3. Compile the list of Type 1 Diabetes specific CDEs still needed by public health 4. Develop the definitions and value sets of the CDEs 5. Incorporate the use case into the suite of use cases previously developed by the Diabe-DS Project team 6. Map the CDEs to the use case 7. Work with the data modelers to add the public health data elements to the data models (data models assert relationships between all of the data elements and are informed by other HL7 data models such as the CV and TB DAMs) 101
5 8. Document the process Diabetes care management is one of the activities addressed by the PHDSC work previously done, so the first order of business was to look at the T1D-specific activities and CDEs that these public health stakeholders had previously identified. (The PHDSC work had previously been explored in depth and vetted through the public health data standards community.) This gave the Diabe-DS project an excellent starting point to harmonize these needs into the existing Diabe-DS suite of use cases. The Wisconsin Functional Requirements Standard for diabetes care management and surveillance prepared by the PHDSC informed this harmonization. A Functional Requirements Analysis Document (FRAD) as used by the PHDSC is a shortened version of the requirements analysis document produced by users and software developers. This document uses the standard functional requirements elicitation methodology and includes the goals of the system, the actors, use cases, functional requirements, data elements and workflow. The Wisconsin FRAD documents the functional requirements for EHR-S information exchange with public health. Since the Wisconsin FRAD focuses on chronic disease care management and surveillance in the disease specific domain of diabetes, this was a good starting point for the process of identifying the CDEs needed for secondary use by Public Health. 18 Identifying the CDEs needed for T1D for public health was an iterative process. The CDEs already identified by the Diabe-DS team were reviewed to see if any of the CDEs identified to date fit with the use cases and data elements identified in the Wisconsin FRAD. The existing Diabe-DS CDEs are maintained on an excel spreadsheet located at: Originally the team felt that some CDEs were too specific (e.g., too atomic) for the Diabe-DS project but found the specificity to be necessary in order to meet the requirements for public health re-use. These data elements e.g. ethnicity and diabetes education were included in the data elements which were eventually presented to the team as necessary for public health. As with other data standards projects (HL7, HITSP), the idea of a use case to guide the work was an important aspect of the Diabetes-DS project. 24 A suite of use cases had already been developed to help refine the scope of the project and describe how the same core data could be used throughout various purposes (e.g., delivery of patient care, research, quality reporting, etc.). The scenarios represented in the use cases include: 1. Patient presents in ambulatory clinic and is diagnosed with T1D 2. Patient is followed by endocrinologist through several visits 3. Patient is seen by diabetic educator 4. Patient is enrolled in a research study 5. Patient data is aggregated and reported for quality measurement A use case was written to describe the flow of data between the clinical care setting and public health. The use case was loosely based on the Wisconsin glycemic control use case developed as part of the Functional Requirements Standard for Diabetes Care Management. 18 The use case was written to cover the following goals of Public Health for diabetes care and management: 1. Monitor prevalence of diabetes in the community and HbA1c testing trends 2. Inform clinical decisions for diabetes care management by providers with community health information and community resources 3. Improve communication between patients and providers and provide patients with educational materials and information on community resources The use case follows the flow of data from the provider s EHR to a public health agency where it is aggregated and sent back to the provider for his use in diabetes care management. The public health use case was initially written independently as a separate document and then incorporated into the suite of use cases previously developed by the Diabetes-DS team. It was through this exercise that documenting care management information such as immunization status and obtaining demographic information which had been omitted from the original provider visit use cases were identified as being necessary to support this additional re-use scenario. These were discussed with the Diabe-DS team during a biweekly conference call and the team agreed they should be part of the use case. The use case was then used to re-examine the data elements in the Diabe-DS master spreadsheet to determine if any additional public health data elements were in the spreadsheet or needed to be added. Additional data elements such as age, county of residence, and race were identified as important to public health for disease surveillance and trends. A total of fifteen additional data elements were added to the spreadsheet. 102
6 After the data elements were identified, the process of developing definitions and determining permissible value sets for each one of them began. Some of the data elements, such as ethnicity, are widely used but the names and permissible values (value set) are not standardized. A value set is the list of permissible values for a data element. The process for developing or determining the definitions and the value sets included searching for the data elements in several places. The CaBIG website has a CDE browser 24 which aided in writing definitions and in determining the value sets for each CDE. Different permissible values were found depending on which organization had defined the data element and its values. For instance, the value set for the data element smoking might be: Current smoker, smoked but quit within last year, and never smoked. After researching the possible value sets, definitions and data element names, and determining which combination suited the needs for the Diabe-DS project, the data elements for public health - as they relate to the existing set of Diabe-DS elements - were discussed by the Diabe-DS team. When consensus was obtained the data elements were added to the master spreadsheet as new data elements, or mapped to existing or closely related data elements. Next, the data elements were mapped to the use case. Mapping data elements to the use case involved going through the use case and matching all the data elements in the use case with those in the spreadsheet. Any elements identified as missing in the spreadsheet were investigated and vice versa. This was a tedious but necessary step and as part of this harmonization of data elements definitions and value sets were further clarified. Finally, the public health data elements were harmonized with the existing UML models. The modeling process helps to define data relationships at their most granular level and deconstructs data requirements into finite elements which can be understood by more than the patient care community. Results Bringing public health into the Diabe-DS project was challenging. Developing the use case and identifying data elements for public health use of data from a T1D office encounter expanded the total number of data elements in the Diabe-DS project by only fifteen. The focus of the Diabe-DS project is on the intersection of data elements for T1D in public health, research, quality and clinical care. An example of the data elements, the definitions and permissible value sets is found in the table on the left side of Figure 1 which shows several steps of the use case. The arrows illustrate the mapping of a common data element to the use case. To address the functional and data requirements for secondary use of clinical T1D data, a total of 15 new data elements were defined and added to the 250+ existing Diabe-DS data elements. Of the data elements already present, approximately thirty were relevant to public health. Thirteen of the public health data elements which were added to the list had not been previously identified. Two data elements (ethnicity and diabetes education) had been identified previously, but it was felt they were too specific to be included in this early demonstration. Because of their importance to public health surveillance and diabetes care management the consensus of the Diabe-DS team was to add them to the list of CDEs. 103
7 Figure 1. Relationship between Common Data Elements and the Public Health Secondary Data Use Case. The Diabe-DS team had worked on harmonization of the data elements with clinical, quality and research needs, but not with public health needs. To harmonize the existing data elements with the public health use case required reviewing the existing definitions and the value sets and the public health literature. 3,18 Ensuring that the definitions and permissible values of the existing elements fit with public health s data needs was time consuming. For instance, a data element name might not be a lexical match, but a search of the definitions might produce the needed element with a different name which would satisfy public health s data needs. This required comparing the definitions in the spreadsheet to public health s data needs. In the master spreadsheet there are many CDEs with similar names and similar definitions. A decision had to be made as to whether an existing data element fit public health s needs or if an additional data element was needed. Another difficulty with incorporating public health into the Diabe-DS project was that many of public health s data needs are related to Type 2 Diabetes and the Diabe-DS project is specific to T1D. It was necessary to carefully go through public health s data needs and research which needs also apply to T1D. There is disparity among organizations about data element names, definitions and value sets. For instance, when researching ethnicity, which is important for public health, several names and value sets were found. The data element names included ethnicity, ethnicity group, and ethnicity participant group. The value sets included: (a) White/African American/Asian/Native American/Other; (b) White/Non White; or (c) African American, White, Asian/Pacific Islander, Native American, Biracial/ Multiracial, NR/Unknown, Other. 16 Each time the value set of a data element had multiple names, definitions, and/or value sets research was done to clarify which of these were appropriate for public health s data needs. 104
8 The public health use case was originally written separately and when incorporating it into the suite of use cases it was necessary to add a step at the beginning. The need for providers to know the criteria for reporting data to public health had not been recognized in any of the existing use cases and this is key to public health s mission. Care management information such as immunization status had also been omitted from the use cases, as had demographic information. Discussion As the use of EHRs becomes more widespread and consistent, the ideal scenario is to have structured, computable, semantically interoperable data collected by the clinicians interacting with the patient. Developing CDEs for disease domains which are standardized across secondary uses will allow clinicians to input only one set of data. Theoretically this lowers the documentation burden on clinicians and allows the discrete data collected in an EHR to be re-used for multiple secondary uses, including public health. Since public health is an important secondary use for healthcare data, it should be a primary consideration for any national health information strategy and data standards activity. Through happenstance the founding Diabe-DS members were interested in research and quality secondary uses. Ideally, public health would have been involved as a major stakeholder at the start of Diabe-DS, but their absence allowed the Diabe-DS effort to address and articulate the incremental addition of additional important secondary uses to a previously defined domain CDEs standard. Theoretically, this approach should address public health data requirements the same as if they were part of the process from the start. So this was a good opportunity to document and reflect on our methods as they might generalize to future CDE and collect once, use many efforts. The purpose of this paper is not to fully describe a process of eliciting public health requirements for data elements in a domain. The purpose was to describe our experience adding a secondary use case to an existing collect once, use many model. This was not a trivial task, but will be necessary for domain-specific data element projects to think about. The most difficult part was reviewing the CDEs which had already been identified as necessary for the disease domain. This included reviewing the definition, values and data element names to ensure the CDE represented the information accurately. For diabetes care management and surveillance, much of public health s focus is on Type 2 diabetes which meant that it was necessary to determine the specific data public health needs for T1D focused surveillance and care management. One objective of this paper is to illustrate that there is a lot of work involved in achieving Collect once, Use many data use. The notion that the same data construct (e.g., diagnosis) could be collected in slightly different ways for different secondary uses obviously seems absurd to many. But to harmonize data elements means harmonizing communities and leveraging relevant work. The Public Health Community had done a thorough analysis of the space, including tasks and data requirements. The work for the Diabe-DS project was greatly enabled by their previous work. For other disease areas, this requirements gathering and use case development will have to be done. We recommend that the secondary use communities develop their requirements and supporting documentation (activities, use cases, etc.) and these then become harmonized in multi-disciplinary groups like Diabe-DS. Even with that work, the need to harmonize multiple disease-specific domains will require much hard work from disease experts and technical experts alike. Disease experts will be needed for their knowledge of the disease domain and technical experts to deal with technical components, data models, and integration of multiple secondary uses. Conclusion: Data standards are a critical component of interoperability and meaningful secondary use. Domain specific data standards efforts such as CDEs - will proliferate as these are sensible approaches to identify standards requirements from various stakeholders. Future domain specific CDE efforts will need to harmonize data elements across secondary uses in their disease area, and with data elements from other disease domains. These efforts can be informed by existing CDEs and use cases, as well as best practice recommendations and lessons learned from our work. Acknowledgements: The authors wish to thank the supporters and members of the Diabe-DS project listed at In particular, we thank Maryanne Quinn, Donna DuLong, Luigi Sisson, Wendy Huang, and Scott Bolte for their significant contributions to the Diabe-DS project. 105
9 REFERENCES 1. ONC. HIT Standards Committee Draft Transcript; February 24, 2010: Office of the National Coordinator for Health Information Technology [Cited 2011 Jun 28]. Available at: 24_standards_transcript_draft.pdf. 2. Health Information Technology Standards Panel. Medication management. [Internet] [Cited 2011 Mar 15]. Available at: fix=is&prefixnumeric=07 3. Public Health Data Standards Consortium. Pediatric electronic health record: public health perspectives. [Internet] [Cited 2011 Mar 15]. Available at: 4. Public Health Data Standards Consortium. Building a roadmap for health information systems interoperability for public health (Public health uses of electronic health record data). [White Paper]. [Internet] [Cited 2011 Mar 3]. Available at: 5. National Quality Forum. [Internet] [Cited 2011 Mar 15]. Available at: 6. National Quality Forum. Electronic quality measures. [Internet] [Cited 2011 Mar 15]. Available at: 7. Kallem, C., Richesson, R, DuLong, D., Sison, L, Van Dyke, P., and Mon, D. Advancing secondary data uses through data Standards. J AHIMA. April 2011;82(4): Health Level 7. HL7 healthcare development framework version 1.5[Internet] [Cited 2011 Jul 5]. Available at: 9. Ahmadian L, Cornet R, Kalkman C, de Keizer NF. Development of a national core dataset for preoperative assessment. Methods Inf Med. 2009;48(2): Winget, M, Baron, JA, Spitz, MR, et al. Development of common data elements: the experience of and recommendations from the early detection research network. Int J of Med Inform. 2003;70(1): Health Level 7. Cardiology DAM. [Internet] 2008 [Cited 2011 Mar 3]. Available at: Health Level 7. Tuberculosis DAM. [Internet] [Cited 2011 Mar 3]. Available at: Richesson, R., et al., A strategy for defining common data elements to support clinical care and secondary use in clinical research, in 2010 AMIA Clinical Research Informatics Summit. 2010; San Francisco. Available at: Institute of Medicine. The future of the public s health in the 21 st century. [Internet] [Cited 2011 Mar 3]. Available at: Public Health Data Standards Consortium. Towards a functional standard on electronic data exchange between clinical care and public health. [Internet] [Cited 2011 Mar 3]. Available at: Office of the National Coordinator. Public health case reporting detailed use case. [Internet] [Cited 2011 Mar 3]. Available at: cached=true 17. Orlova, A., Dunnagan, M., Finitzo, T., et al. An electronic health record-public health (EHR-PH) system prototype for interoperability in 21 st century healthcare systems. AMIA Annu Symp Proc. 2005; 2005: Public Health Data Standards Consortium. Standards for public health data exchange: functional requirements standard for diabetes care management and surveillance. [Internet] [Cited 2011 Mar 3]. Available at: Orlova, A., Reed-Forquet, L. Knowledge representation in chronic care management: example of diabetes care management. [White paper] Public Health Data Standards Consortium. Developing a vision for functional requirements specification for electronic data exchange between clinical and public health settings: Examples of school health and syndromic surveillance in New York City. [Internet] [Cited 2011 Mar 15]. Available at: HITSP. Public health case reporting interoperability specification. [Internet] [Cited 2011 Mar 15]. Available at: 106
10 efix=is&prefixnumeric= American Diabetes Association. Standards of medical care in diabetes [Position paper]. Diabetes Care, 2010; (34) Supplement 1, pp S11-S61. doi: /dc11-s Wisconsin Department of Health Services. Wisconsin diabetes mellitus care guidelines. [Internet] [Cited 2011 Mar 11]. Available at: HITSP Harmonization Framework [Internet]. Health Information Technology Standards Panel [Cited 2011 Jul 5]. Available at: CDE Browser [Internet]. Cancer Data Standards Registry and Repository [Cited 2011 Mar 17]. Available at: 107
Common Data Elements for Clinical Documentation and Secondary Use: Diabe-DS Proof-of-Concept for Collect Once, Use Many Times
Common Data Elements for Clinical Documentation and Secondary Use: Diabe-DS Proof-of-Concept for Collect Once, Use Many Times Project White Paper White Paper Authors: Rachel L. Richesson, PhD, MPH; Crystal
More informationQuality Improvement through HIT
Quality Improvement through HIT What is quality in healthcare? Safe Effective Patientcentered Timely Efficient Equitable Overview Reinforce a vision for using HIT to improve quality Share our approach
More informationThe North American Association of Central Cancer Registries, Inc. (NAACCR) Interoperability Activities
The North American Association of Central Cancer Registries, Inc. (NAACCR) Interoperability Activities Lori A. Havener, CTR Program Manager of Standards Public Health Data Standards Consortium 2008 Annual
More informationNational Vaccine Plan Goal 4 Immunization Information Systems. Mike Garcia Scientific Technologies Corporation 24 July 2008
National Vaccine Plan Goal 4 Immunization Information Systems Mike Garcia Scientific Technologies Corporation 24 July 2008 Immunization Information Systems (IIS) role in the Goal: Achieve better use of
More informationSemantic Alignment between ICD-11 and SNOMED-CT. By Marcie Wright RHIA, CHDA, CCS
Semantic Alignment between ICD-11 and SNOMED-CT By Marcie Wright RHIA, CHDA, CCS World Health Organization (WHO) owns and publishes the International Classification of Diseases (ICD) WHO was entrusted
More informationThe openehr approach. Background. Approach. Heather Leslie, July 17, 2014
Heather Leslie, July 17, 2014 The openehr approach Background The open source openehr 1 architecture specifications 2 have evolved as the result of over 20 years of research and international implementations,
More informationSAGE. Nick Beard Vice President, IDX Systems Corp.
SAGE Nick Beard Vice President, IDX Systems Corp. Sharable Active Guideline Environment An R&D consortium to develop the technology infrastructure to enable computable clinical guidelines, that will be
More informationEHR Developer Code of Conduct Frequently Asked Questions
EHR Developer Code of Conduct Frequently Asked Questions General What is the purpose of the EHR Developer Code of Conduct? EHR Association (the Association) members have a long tradition of working with
More informationElectronic Support for Public Health Vaccine Adverse Event Reporting System (ESP:VAERS)
Grant Final Report Grant ID: R18 HS 017045 Electronic Support for Public Health Vaccine Adverse Event Reporting System (ESP:VAERS) Inclusive dates: 12/01/07-09/30/10 Principal Investigator: Lazarus, Ross,
More informationNPCR-AERRO S PARTNERSHIP WITH IHE: ENSURING CANCER S CONNECTIVITY WITH THE EMR/EHR
NPCR-AERRO S PARTNERSHIP WITH IHE: ENSURING CANCER S CONNECTIVITY WITH THE EMR/EHR Wendy Blumenthal, MPH Epidemiologist NAACCR Annual Conference June 24, 2010 National Center for Chronic Disease Prevention
More informationNational Program of Cancer Registries Advancing E-cancer Reporting and Registry Operations (NPCR-AERRO): Activities Overview
National Program of Cancer Registries Advancing E-cancer Reporting and Registry Operations (NPCR-AERRO): Activities Overview Sandy Jones Public Health Advisor NAACCR 2011 Conference June 22, 2011 National
More informationCombining Archetypes with Fast Health Interoperability Resources in Future-proof Health Information Systems
180 Digital Healthcare Empowering Europeans R. Cornet et al. (Eds.) 2015 European Federation for Medical Informatics (EFMI). This article is published online with Open Access by IOS Press and distributed
More informationMedicare & Medicaid EHR Incentive Programs
Medicare & Medicaid EHR Incentive Programs Stage 2 NPRM Overview Robert Anthony March 6, 2012 Proposed Rule Everything discussed in this presentation is part of a notice of proposed rulemaking (NPRM).
More informationThe Oral Health Workforce & Access to Dental Care
The Oral Health Workforce & Access to Dental Care Beth Mertz, PhD, MA National Health Policy Forum April 10, 2015 Objectives 1. Provide an overview of the current dental access and workforce landscape
More informationAbout the Highmark Foundation
About the Highmark Foundation The Highmark Foundation, created in 2000 as an affiliate of Highmark Inc., is a charitable organization and a private foundation that supports initiatives and programs aimed
More informationMoving Family Health History & Genetic Test Result Data into the Electronic Health Record for Clinical Decision Support
Moving Family Health History & Genetic Test Result Data into the Electronic Health Record for Clinical Decision Support HL7 30 Years of Standards Development HIMSS February 21, 2017 Grant M. Wood Intermountain
More informationNATIONAL QUALITY FORUM
National Voluntary Consensus Standards for Patient Outcomes Summary of the Eye Care Technical Advisory Panel Conference Call March 25, 2010: 10:00-11:00PM Eastern Standard Time TAP members participating:
More informationTexas ereferral Project with Lonestar Circle of Care, NextGen, Alere Wellbeing and University of Texas at Austin Update Date: October 2014
ereferral Project Summary Please describe the purpose / goals for your ereferral project. Give a description of the health care provider/system, why/how they were selected, and other relevant information.
More informationAgenda. Immunization Registry Reporting in Community Health Centers. Presented by: Ben Pierson Program Manager Health Information Exchange
Immunization Registry Reporting in Community Health Centers Presented by: Ben Pierson Program Manager Health Information Exchange Agenda Introduction About OCHIN Vaccination support in EHR Immunization
More informationProgress in Standardization of Reporting and Analysis of Data from Early Hearing Detection and Intervention (EHDI) Programs
2016; 1(2): 2-7 Progress in Standardization of Reporting and Analysis of Data from Early Hearing Detection and Intervention (EHDI) Programs Suhana Alam,MPH., 1 Ashley Satterfield, MPH., 2 Craig A. Mason,
More informationNew York State Immunization Information System (NYSIIS) New York State Department of Health. Digital Government: Government to Business (G to B)
New York State Immunization Information System (NYSIIS) New York State Department of Health Digital Government: Government to Business (G to B) 1 Executive Summary The New York State Immunization Information
More informationOral Health: An Essential Component of Primary Care. Executive Summary
Oral Health: An Essential Component of Primary Care Executive Summary June 2015 Executive Summary The Problem Oral health is essential for healthy development and healthy aging, yet nationwide there is
More informationWELSH INFORMATION STANDARDS BOARD
WELSH INFORMATION STANDARDS BOARD DSC Notice: DSCN 2018 / 06 Date of Issue: 8 th August 2018 Welsh Health Circular / Official Letter: (2015) 053 Subject: CT Maturity Matrix Sponsor: Chris Newbrook, Head
More informationScenario Vendor Products Standards
Use Case Title: Cancer, Registry, Discovery, & Research Overview: Shira discovers she has colon cancer that has moved into her lungs. She seeks treatment with her oncologist and enrolls in a clinical trial
More informationEdward Jones, MD KCP Chairman Gail Wick, MHSA, BSN, RN, CNN Allen Nissenson, MD
Re-launching KCQA Edward Jones, MD KCP Chairman Gail Wick, MHSA, BSN, RN, CNN Allen Nissenson, MD ABOUT KCP Re-launching KCQA Founded in May 2003 Voice of the entire kidney care community Patients and
More informationPROPOSED WORK PROGRAMME FOR THE CLEARING-HOUSE MECHANISM IN SUPPORT OF THE STRATEGIC PLAN FOR BIODIVERSITY Note by the Executive Secretary
CBD Distr. GENERAL UNEP/CBD/COP/11/31 30 July 2012 ORIGINAL: ENGLISH CONFERENCE OF THE PARTIES TO THE CONVENTION ON BIOLOGICAL DIVERSITY Eleventh meeting Hyderabad, India, 8 19 October 2012 Item 3.2 of
More informationPublic Health Meaningful Use: Views from the Field. HIMSS HIE Roundtable May 19, 2011
Public Health Meaningful Use: Views from the Field HIMSS HIE Roundtable May 19, 2011 Public Health and Meaningful Use: Views from the Field HIMSS HIE Roundtable May 19, 2011 Noam H. Arzt President, HLN
More informationAugust 29, Dear Dr. Berwick:
August 29, 2011 Donald Berwick, MD Administrator Centers for Medicare & Medicaid Services U.S. Department of Health and Human Services 200 Independence Avenue, SW Room 445-G Washington, DC 20201 Re: Proposed
More informationBritish Columbia Data Standards
British Columbia Data Standards Minimum Immunization Data Set Interoperability Guide Version: 1.0 October 23, 2017 Sponsors PHSA: Jill Reedijk Canada Health Infoway DOCUMENT CONTROL DOCUMENT HISTORY Version
More informationWhat is a Special Interest Group (SIG)?
PATIENT REPORTED OUTCOMES RESEARCH SPECIAL INTEREST GROUP Open Meeting 20 th Annual European Congress November 6, 2017 Glasgow, Scotland What is a Special Interest Group (SIG)? Member-driven group interested
More informationIntroduction and Purpose
Proceedings Illinois Oral Health Summit September 11, 2001 Illinois Response to the Surgeon General s Report on Introduction and Purpose The landmark Illinois Oral Health Summit convened on September 11,
More informationFrom EHR Immunization Requirements to a Validation and Recognition Program
From EHR Immunization Requirements to a Validation and Recognition Program National Adult and Influenza Immunization Summit May 9 11, 2017 Atlanta, GA 1 Today s Speaker: Joyce Sensmeier MS, RN-BC, CPHIMS,
More informationSession #206, March 8, 2018 Susan J. Kressly, MD, FAAP, Kressly Pediatrics Dr. Jacques Orces, D.O., Nicklaus Children s Hospital
Improving Preventative Care in Pediatrics through Health and Technology: A Davies Story Session #206, March 8, 2018 Susan J. Kressly, MD, FAAP, Kressly Pediatrics Dr. Jacques Orces, D.O., Nicklaus Children
More informationAn Ontology for Healthcare Quality Indicators: Challenges for Semantic Interoperability
414 Digital Healthcare Empowering Europeans R. Cornet et al. (Eds.) 2015 European Federation for Medical Informatics (EFMI). This article is published online with Open Access by IOS Press and distributed
More informationGreatest challenges and opportunities in oncology
Greatest challenges and opportunities in oncology Clifford Hudis, MD Chief, Breast Medicine Service, MSKCC Professor of Medicine, WCMC Immediate Past-President, ASCO 1. Understanding pathways to novel
More informationRebooting Cancer Data Through Structured Data Capture GEMMA LEE NAACCR CONFERENCE JUNE, 2017
Rebooting Cancer Data Through Structured Data Capture GEMMA LEE NAACCR CONFERENCE JUNE, 2017 Acknowledgement Richard Moldwin, MD, PhD, CAP Sandy Jones, CDC Wendy Blumenthal, CDC David Kwan, Cancer Care
More informationHL7 EHR Interoperability WG. Project Planning. Facilitators: Gora Datta, Gary Dickinson 14 October 2009
HL7 EHR Interoperability WG Project Planning Facilitators: Gora Datta, Gary Dickinson 14 October 2009 US HIT Policy Committee Notable Recommendations Certification and Adoption Implement a New Certification
More informationMeaningful Use Overview
Eligibility Providers may be eligible for incentives from either Medicare or Medicaid, but not both. In addition, providers may not be hospital based. Medicare: A Medicare Eligible Professional (EP) is
More informationPharmacotherapy selection system supports shared clinician-patient decision-making in diabetes treatment
FOR IMMEDIATE RELEASE Pharmacotherapy selection system supports shared clinician-patient decision-making in diabetes treatment Electronic health record-based comparative display of pharmaceutical options
More informationDENTAL QUALITY ALLIANCE: 2018 ANNUAL MEASURES REVIEW
DENTAL QUALITY ALLIANCE: 2018 ANNUAL MEASURES REVIEW REPORT FROM THE DQA MEASURES DEVELOPMENT AND MAINTENANCE COMMITTEE JUNE 2018 2018 American Dental Association on behalf of the Dental Quality Alliance
More informationThe findings and conclusions in this presentation
The findings and conclusions in this presentation formall disseminated by b the have not been formally Centers for Disease Control and Prevention and should not be construed to represent any agency p y
More informationNursing Home Outreach MEETING THE DENTAL HEALTH N E E DS F OR B I SMARCK/MANDAN E L DERLY
Nursing Home Outreach MEETING THE DENTAL HEALTH N E E DS F OR B I SMARCK/MANDAN E L DERLY What Do.. Four Nursing Facilities Newest Long Term Care Centers And And All Have in Common?? An Out Reach Program
More informationSemantic Interoperable Electronic Patient Records: The Unfolding of Consensus based Archetypes
170 Digital Healthcare Empowering Europeans R. Cornet et al. (Eds.) 2015 European Federation for Medical Informatics (EFMI). This article is published online with Open Access by IOS Press and distributed
More informationIntegrating the Patient Perspective Into Value Frameworks
Integrating the Patient Perspective Into Value Frameworks Avalere Health An Inovalon Company August, 2017 Speakers and Agenda Josh Seidman, PhD Senior Vice President jjseidman@avalere.com @jjseidman 1.
More informationCalifornia Environmental Protection Agency
California Environmental Protection Agency OCTOBER 2004 ENVIRONMENTAL JUSTICE ACTION PLAN TABLE OF CONTENTS 1. INTRODUCTION...2 1.1 Purpose... 2 1.2 Development and Update...3 2. OBJECTIVES...4 2.1 Develop
More informationthe rural primary care practice guide to Creating Interprofessional Oral Health Networks
the rural primary care practice guide to Creating Interprofessional Oral Health Networks November 2017 2 purpose and background 3 getting started: developing a plan 4 activities and ideas for consideration
More informationDonald L. Patrick PhD, MSPH, Laurie B. Burke RPh, MPH, Chad J. Gwaltney PhD, Nancy Kline Leidy PhD, Mona L. Martin RN, MPA, Lena Ring PhD
Content Validity: Establishing and Reporting the Evidence in Newly-Developed Patient-Reported Outcome (PRO) Instruments for Medical Product Evaluation - Good Research Practices Donald L. Patrick PhD, MSPH,
More information= AUDIO. Managing Diabetes for Improved Cardiovascular Health. An Important Reminder. Mission of OFMQ 8/18/2015. Jimmi Norris MS, RN, CDE
Managing Diabetes for Improved Cardiovascular Health Jimmi Norris MS, RN, CDE An Important Reminder For audio, you must use your phone: Step 1: Call (866) 906 0123. Step 2: Enter code 2071585#. Step 3:
More informationCommon Data Elements: Making the Mass of NIH Measures More Useful
Common Data Elements WG Common Data Elements: Making the Mass of NIH Measures More Useful Jerry Sheehan Assistant Director for Policy Development Na?onal Library of Medicine Gene/c Alliance Webinar Series
More informationAbstract. Introduction. Providers stand to lose $1.15 billion in CMS reimbursements under MU
Abstract As of November 1, 2014, only 2% of eligible professionals had attested to Meaningful Use 2 1. This is not good news for the thousands of independent physician practices that rely on Medicare payments:
More informationVolunteering in NHSScotland Developing and Sustaining Volunteering in NHSScotland
NG11-07 ing in NHSScotland Developing and Sustaining ing in NHSScotland Outcomes The National Group for ing in NHS Scotland agreed the outcomes below which formed the basis of the programme to develop
More informationTask Force Background Donald Patrick. Appreciation to Reviewers. ISPOR PRO GRP Task Force Reports
Content Validity: Establishing and Reporting the Evidence in Newly-Developed Patient-Reported Outcome (PRO) Instruments for Medical Product Evaluation - Good Research Practices Donald L. Patrick PhD, MSPH,
More informationRiding the Current: Upstream and Downstream Approaches to Implement Adult Immunization Strategies
Riding the Current: Upstream and Downstream Approaches to Implement Adult Immunization Strategies Paul Nguyen Community Health Partnership Connie Chung-Bohling California Department of Public Health Session
More informationHL7 s Version 2 standards and submission to immunization registries
HL7 s Version 2 standards and submission to immunization registries Alean Kirnak Cochair HL7 Public Health and Emergency Response Workgroup American Immunization Registry Association Software Partners
More informationIHE Quality, Research and Public Health Technical Framework Supplement. Early Hearing Care Plan (EHCP) Trial Implementation
Integrating the Healthcare Enterprise 5 IHE Quality, Research and Public Health Technical Framework Supplement 10 Early Hearing Care Plan (EHCP) Trial Implementation 15 20 Date: September 2, 2011 Author:
More informationREPORT TO CONGRESS Multi-Disciplinary Brain Research and Data Sharing Efforts September 2013 The estimated cost of report or study for the Department of Defense is approximately $2,540 for the 2013 Fiscal
More informationProgress from the Patient-Centered Outcomes Research Institute (PCORI)
Progress from the Patient-Centered Outcomes Research Institute (PCORI) Anne Beal, Chief Operating Officer of the Patient-Centered Outcomes Research Institute Sharon-Lise Normand, Vice Chair, Methodology
More informationImmunization Reporting and Clinical Decision Support via SOA. Mike Suralik Project Manager HLN Consulting, LLC. June 4, 2009
Immunization Reporting and Clinical Decision Support via SOA Mike Suralik Project Manager June 4, 2009 1 Introduction Public health agencies have unique assets (e.g. data and algorithms) that can and should
More informationAppendix B: Planning Process
HILLSBOROUGH COUNTY POST-DISASTER REDEVELOPMENT PLAN B-1 Appendix B: Planning Process The Hillsborough County Post Disaster Redevelopment Plan (PDRP) is a community plan that was developed over the course
More informationThe Academy Capitol Forum: Meet the Experts. Diagnosing Which Health Treatments Improve Outcomes: A PCORI Overview and How to Get Involved
The Academy Capitol Forum: Meet the Experts Diagnosing Which Health Treatments Improve Outcomes: A PCORI Overview and How to Get Involved Presenter: Gregory Martin, Deputy Directory of Stakeholder Engagement
More informationSafe States Alliance 2018 Innovative Initiatives Finalist Summaries for Review
Safe States Alliance 2018 Innovative Initiatives Finalist Summaries for Review 1 Initiative #1: Aiming for Equity in Sexual Violence Prevention - Mapping Risks, Policies, Outcomes and Resources Statement
More informationWednesday, July 13, 2016 National Press Club Washington, DC
Wednesday, July 13, 2016 National Press Club Washington, DC National Vision & Eye Health Surveillance System Jinan Saaddine MD, MPH, CDC Vision Health Initiative David Rein PhD, NORC at the University
More informationQUALITY IMPROVEMENT TOOLS
QUALITY IMPROVEMENT TOOLS QUALITY IMPROVEMENT TOOLS The goal of this section is to build the capacity of quality improvement staff to implement proven strategies and techniques within their health care
More informationHL7 EHR Interoperability WG. Projects in Progress. Co-Facilitators: Gora Datta, Gary Dickinson 4 October 2010
HL7 EHR Interoperability WG Projects in Progress Co-Facilitators: Gora Datta, Gary Dickinson 4 October 2010 Standards Convergence ISO 16223 Standards Convergence to Promote EHR Interoperability Prior Simplification
More informationPatricia Bax, RN, MS August 17, Reaching New York State Tobacco Users through Opt-to-Quit
Patricia Bax, RN, MS August 17, 2015 Reaching New York State Tobacco Users through Opt-to-Quit Good Afternoon! Welcome Roswell Park Cessation Services and Opt-to-Quit Overview Featured Site: Stony Brook
More informationPriority Area: 1 Access to Oral Health Care
If you are unable to attend one of the CHARTING THE COURSE: Developing the Roadmap to Advance Oral Health in New Hampshire meetings but would like to inform the Coalition of activities and services provided
More informationTeam-Based Decision Support in Diabetes Outcomes and Costs
Team-Based Decision Support in Diabetes Outcomes and Costs Session 89, 8:30 a.m. February 13, 2019 Gary Ozanich, Ph.D. - College of Informatics, Northern Kentucky University 1 Conflict of Interest Gary
More information**Please read the DQA Measures User Guide prior to implementing this measure.**
**Please read the DQA Measures User Guide prior to implementing this measure.** DQA Measure Technical Specifications: Administrative Claims-Based Measures Prevention: Topical Fluoride for Children at Elevated
More informationAMERICAN PROFESSIONAL SOCIETY FOR ADHD & RELATED DISORDERS Setting Direction for the Society
AMERICAN PROFESSIONAL SOCIETY FOR ADHD & RELATED DISORDERS Setting Direction for the Society August 2015 TABLE OF CONTENTS Core Ideology Core Purpose and Core Values Page 2 Envisioned Future Page 3 Goals
More information2015 NAIIS Summit Quality Measures May 12, 2015
2015 NAIIS Summit Quality Measures May 12, 2015 Sharon L. Sprenger Co-Lead Quality Measures Workgroup Director, Measurement Coordination and Outreach Division Healthcare Quality Evaluation The Joint Commission
More informationLinking Public Interests to Ensure Sustainable Statewide Quitlines
Linking Public Interests to Ensure Sustainable Statewide Quitlines Public health tobacco prevention and control programs (TCPs) find themselves working within evershifting financial and political landscapes,
More informationHow Doctors Feel About Electronic Health Records. National Physician Poll by The Harris Poll
How Doctors Feel About Electronic Health Records National Physician Poll by The Harris Poll 1 Background, Objectives, and Methodology New research from Stanford Medicine, conducted with The Harris Poll
More informationGLOBAL ANTIMICROBIAL RESISTANCE SURVEILLANCE
GLOBAL ANTIMICROBIAL RESISTANCE SURVEILLANCE Sonja Löfmark Public Health Agency of Sweden 6 th BARN Workshop May 12, 2016 Uppsala What is GLASS? A global programme for AMR surveillance The data it collects
More informationSuccesses in Regional Collaboration to Achieve the Triple Aim Oregon. Pay for Performance Summit San Francisco March 24, 2014
Successes in Regional Collaboration to Achieve the Triple Aim Oregon Pay for Performance Summit San Francisco March 24, 2014 Agenda Oregon Health Care Quality Corporation (Q Corp) Background Priority Projects
More informationThe impact of electronic health record (EHR) interoperability on immunization information system (IIS) data quality
The impact of electronic health record (EHR) interoperability on immunization information Mary Woinarowicz 1, MA, Molly Howell 1, MPH 1. North Dakota Department of Health, Division of Disease Control Abstract
More informationUses of the NIH Collaboratory Distributed Research Network
Uses of the NIH Collaboratory Distributed Research Network Jeffrey Brown, PhD for the DRN Team Harvard Pilgrim Care Institute and Harvard Medical School March 11, 2016 The Goal The NIH Collaboratory DRN
More informationA Framework for Optimal Cancer Care Pathways in Practice
A to Guide Care Cancer Care A for Care in Practice SUPPORTING CONTINUOUS IMPROVEMENT IN CANCER CARE Developed by the National Cancer Expert Reference Group to support the early adoption of the A to Guide
More informationLeveraging Data for Targeted Patient Population Health Improvements
Leveraging Data for Targeted Patient Population Health Improvements Diabetes Impact on Health in America Diabetes is a major health concern in the United States today. The Centers for Disease Control
More informationPalliative Care and IPOST Hospital Engagement Network June 5, Palliative Care
Palliative Care and IPOST Hospital Engagement Network June 5, 2012 Jim Bell, MD Medical Director St. Luke s Palliative Care and Hospice Palliative Care The interdisciplinary specialty that focuses on improving
More informationFlorida Asthma Coalition 2013 Operational Plan Page 1 of 11
Building the Infrastructure for Asthma Control Page 1 of 11 Contents Introduction 2 About the 2 About the Annual Operational Plan 2 2013 Meeting s 3 Glossary of Terms and Acronyms 3 Part 1: Coalition System
More informationLessons Learned from Meaningful Use Implementation. Cynthia L. Bero, MPH Partners HealthCare May 19, 2011
Lessons Learned from Meaningful Use Implementation Cynthia L. Bero, MPH Partners HealthCare May 9, 20 Meaningful Use Plan of Action Learn the HITECH program Certified EHR Technology. Analyze gap between
More informationEHR Incentive Programs for Eligible Professionals: What You Need to Know for 2015 Tipsheet
EHR Incentive Programs for Eligible Professionals: What You Need to Know for 2015 Tipsheet CMS recently published a final rule that specifies criteria that eligible professionals (EPs), eligible hospitals,
More informationEli Schwarz - School of Dentistry. Do quality metrics derive from dental. practice activities and flow back into the dental school?
Acknowledgments Dr. Denice Stewart Senior Associate Dean Clinical Affairs, School of Dentistry, Oregon Health & Science University, Portland OR, and Past Chair, Consortium for Oral Health, Research, and
More informationCall for Proposals: Demonstration Projects and Champion Development for Providers to address Type 2 Diabetes Prevention
Call for Proposals: Demonstration Projects and Champion Development for Providers to address Type 2 Diabetes Prevention Introduction The American College of Preventive Medicine (ACPM) recently began our
More informationEFSA cross-cutting guidance lifecycle. European Food Safety Authority (EFSA), Daniela Maurici, Raquel Garcia Matas, Andrea Gervelmeyer
TECHNICAL REPORT APPROVED: 29 June 2018 doi:10.2903/sp.efsa.2018.en-1446 Abstract EFSA cross-cutting guidance lifecycle European Food Safety Authority (EFSA), Daniela Maurici, Raquel Garcia Matas, Andrea
More informationOrganizational HIV Treatment Cascade Guidance for Construction. Introduction. Background
Organizational HIV Treatment Cascade Guidance for Construction Introduction This guidance document provides organizations with the necessary tools and resources to construct their Organizational HIV Treatment
More informationIncreasing Adult Immunization Rates in the US Through Data and Quality: A Roadmap
Increasing Adult Immunization Rates in the US Through Data and Quality: A Roadmap Avalere Health An Inovalon Company November 16, 2017 In Partnership with GSK Agenda 1 2 3 4 5 Welcome & Introductions Overview:
More informationMonthly Campaign Webinar. May 19, 2016
Monthly Campaign Webinar May 19, 2016 WEBINAR REMINDERS Webinar will be recorded today and available the week of May 23 rd Together2Goal.org Website (Improve Patient Outcomes Webinars) Email distribution
More informationJanine E. Janosky, Ph.D. Vice President and Head, Center for Community Health Improvement. June 2013
Janine E. Janosky, Ph.D. Vice President and Head, Center for Community Health Improvement June 2013 ABIA: Unique Convergence Accountable Care Community (ACC) Vision To improve the health of the community.
More informationPediatrics Milestones and Meaningful Assessment Translating the Pediatrics Milestones into Assessment Items for use in the Clinical Setting
Pediatrics Milestones and Meaningful Assessment Translating the Pediatrics Milestones into Assessment Items for use in the Clinical Setting Ann Burke Susan Guralnick Patty Hicks Jeanine Ronan Dan Schumacher
More informationResearch for Development Impact Network
Research for Development Impact Network Mid-term Review of Research for Development Impact (RDI) Network Program Executive Summary and Management Response Submitted: 11 July 2017 This report has been prepared
More informationPediatric Oral Healthcare Exploring the Feasibility for E-Measures December 2012
Pediatric Oral Healthcare Exploring the Feasibility for E-Measures December 2012 Copyright 2012 American Dental Association on behalf of the Dental Quality Alliance (DQA). All rights reserved. Use by individuals
More informationIntroduction. Legislation & Policy Context
Consumer Participation Plan 2017-2018 1 Introduction Barwon South Western Regional Integrated Cancer Service (BSWRICS) is committed to improving the experiences and outcomes of those affected by cancer
More informationRural Health Initiative
Rural Health Initiative 1 Our Vision For Rural Health To facilitate best in class health care in rural areas and reduce rural health care in Idaho as a disparity. To facilitate equity in health in rural
More informationClinical Quality Management Policy Clarification Notice
Clinical Quality Management Policy Clarification Notice Policy Clarification Notice (PCN) #15-02 Related legislation: Title XXVI of the Public Health Service (PHS) Act 2604(h)(5), 2618(b)(3)(E), 2664(g)(5),
More informationLow Tolerance Long Duration (LTLD) Stroke Demonstration Project
Low Tolerance Long Duration (LTLD) Stroke Demonstration Project Interim Summary Report October 25 Table of Contents 1. INTRODUCTION 3 1.1 Background.. 3 2. APPROACH 4 2.1 LTLD Stroke Demonstration Project
More informationInputs Activities Outputs Outcomes Impact
LOGIC MODEL OVERVIEW A logic model is a tool which visually describes the linkages between goals, activities, and expected outcomes for a program. Logic models are frequently characterized as a roadmap
More informationElectronic Health Records (EHR) HP Provider Relations October 2012
Electronic Health Records (EHR) HP Provider Relations October 2012 Agenda Session Objectives Electronic Health Record (EHR) EHR Incentive Program Certified Technology EHR Meaningful Use EHR Incentive Program
More information10.2 Summary of the Votes and Considerations for Policy
CEPAC Voting and Policy Implications Summary Supplemental Screening for Women with Dense Breast Tissue December 13, 2013 The last CEPAC meeting addressed the comparative clinical effectiveness and value
More informationCONGENITAL HEART PUBLIC HEALTH CONSORTIUM
CONGENITAL HEART PUBLIC HEALTH CONSORTIUM Impact and opportunity of a public health approach to congenital heart defects WHO WE ARE In 2009, various organizations across federal, state and local communities
More information