- primary health care
- community health services
- health information technology
- outcome and process assessment (health care)
- electronic health records
- medical informatics
- classification
- population health
- health data standards
The purpose of this commentary is to inspire a coordinated effort by primary care leaders, communities, and health information technology (IT) experts to establish a conceptual primary care data model. A shared data model is necessary to guide the development of health IT standards that will enable primary care clinicians to make essential, foundational contributions within redesigned systems of care, education, and research. This work requires that we understand the core functions of primary care in a transformed US health care system.
Primary care provides integrated, accessible health care by clinicians who are accountable for addressing most personal health care needs, developing a sustained partnership with patients, and practicing in the context of family and community.1 The role of primary care is complex, with well-defined attributes that can serve as the foundation of health care delivery systems. As a service, primary care can be expected to improve individual and population health, the quality of health care, and the efficiency and affordability of health care, as well as relieve inequities in health and health care.2–4 A jurisdiction with weak primary care would be expected to have comparatively worse health and health care, be unnecessarily expensive, and result in substantial disparities in health and health care within its population—as is the case for the United States.5,6
All problems concerning health and health care may exist in primary care and are accepted and managed in partnerships with individuals, families, communities, and other health and health care enterprises. Thus, primary care probably represents health care’s most complex information challenge. There is not yet a shared understanding of what particular data, from which diverse sources, should be collected, organized, linked, and used to enable excellent primary care.
Developing a data model for primary care requires examining both its historical and contemporary contexts. Throughout the 20th century, the elaboration of disciplines, specialties, and sectors concerned with health and health care7 has yielded well-intentioned efforts to advance health care and improve health that are important but fragmented and not well-integrated, characterized as “silos of understanding that misrepresent the world in ways that block advancement.”8 Yet, even as dramatic changes in the science base, organization, delivery, and financing of health care occurred during the last century, frontline primary care practices have persisted and remained stable as the largest platform of formal health care delivery in the United States.9,10 Much that is known about what is necessary to achieve high-performing primary care1,8,11 has exposed the need for modernized robust care capable of providing safe, comprehensive, prioritized, and personalized care to resolve most of the health concerns most people have most of the time.
Primary care clinicians—filled at once with high hopes and considerable fear and frustration—continue to struggle to establish their place, integrative role, knowledge base, and ways of working with patients, families, and communities12 in an environment shaking with concern, complexity, and change. The financial unsustainability13 and persistent quality and performance gaps of the US health care enterprise5,6 have inspired recent efforts to reimagine and reconstruct our approach to health and health care delivery. Nations have rediscovered that health is a community affair,14,15 that physical and mental health are inseparable, and that prevention of mental, emotional, and behavioral problems has been neglected.16,17 There are renewed calls for exploring how to integrate primary care and public health.18 The idea of a learning health care system, capable of closing the research-practice gap by deriving and applying evidence from everyday clinical practice, has matured.19 The importance and methods of community engagement in the discovery and application of knowledge for health and health care improvement has been established.20 The information revolution’s transformative power has penetrated health care,21,22 and there is progress toward counting what counts, measuring what matters, and generating a parsimonious set of core measures to guide improvements in care and relieve the processes that burden health care without sufficient return on investment.23 These developments provide a tremendous opportunity to re-engineer primary care.
There are good reasons to think that establishing a conceptual data model for primary care is important and achievable now. In 2002 the United States National Committee on Vital and Health Statistics (NCVHS) published a vision for population health statistics in the 21st century.24 Figure 1 displays its proposed reference set of community attributes and contextual cultural, political, and natural environmental factors that influence population health.
Proposed NCVHS community-population health data model.
Reprinted with permission from National Committee on Vital and Health Statistics.24
Communities across the country want data about health and health care that is actionable at local levels, but they lack the needed infrastructure to enable stewardship of relevant, personalized, and protected data for health and health care improvement. Authoritative recommendations for moving forward using data for continuous learning in health and health care have been formulated regarding data sources and mapping, public and patient engagement, building a clinical data learning utility, and governance.25 The hopes, fears, enablers, and impediments that accompany transforming communities to learning systems for health in the information age are being exposed.25,26 The Office of the National Coordinator for Health Information Technology (ONC), at the forefront of federal health IT efforts, is promoting nationwide health information and exchange to improve health and care. Its 10-year vision27 identifies 5 essential building blocks, including core technical standards and functions, and envisions:
By 2024, individuals, care providers, communities, and researchers should have an array of interoperable health IT products and services that allow the health care system to continuously learn and advance the goal of improved health care. This “learning health system” should also enable lower health care costs, improved population health, truly empower consumers, and drive innovation.
Circle Square, Inc, closely observing trends in health IT, reported in June of 2014 that “40% of health systems are indifferent or dissatisfied with their electronic health records (EHRs) with health IT being a top driver of costs in health systems…. Patient-centered medical home model gets results …EHRs are not enough.” Health IT is attracting billions of dollars of venture capital.28 The member boards of the American Board of Medical Specialties have adopted standards for physician certification that move beyond taking tests to using data to improve practice.29 Yet there is great frustration with health IT at the clinical practice level. Major investment in adopting EHR systems has not led to gains in clinical productivity or personal or community health benefits.30
Clearly, a journey is underway toward health IT and use that catapults clinicians, scientists, people, health care systems, and communities into fruitful partnerships to discover the origins of disease and illness, promote well-being, and relieve suffering. It is difficult to imagine a sufficient data infrastructure that does not enable primary care, and it seems sensible that leaders in family medicine and primary care should provide guidance about the data requirements of modernized primary care. The first critical step in this process would be to develop, sanction, and share with health IT developers and other decision makers a proper data model to support robust primary care. Fortunately, there are reasons to think that new technologies may be able to overcome the massive primary care data challenges, and there is prior work from which to build.31
A CONCEPTUAL DATA MODEL FOR PRIMARY CARE
What is a Data Model?
A data model is a set of objects, relationships, and rules that describes essential data elements and standardizes how they relate to each other in ways that foster understanding and enable helpful action.32,33 A relevant data model can provide a concise representation of reality in a way that ensures communication between people or actors in a system.
Why Do We Need a Primary Care Data Model?
To guide the parsimonious collection of data that can accurately describe the essential core content of the primary care domain
To specify the data relationships necessary to capture the clinical processes of primary care
To improve the design of clinical information systems that support the everyday clinical practice of person-centered primary care
To enable and accurately assess primary care for individuals, families, and communities within the larger health care enterprise
Our current health IT infrastructure best serves the few individuals who receive care for known diseases in hospitals within integrated health systems. EHR systems are primarily designed to provide standardized clinical documentation to support disease-based care and meet complex billing requirements. Many systems can now provide embedded clinical decision support and standardized clinical pathways for chronic diseases.
But for most individuals in our communities who experience symptoms and decide to seek care, there is no common machine language to describe those symptoms, their impact, the reasons for seeking care, or the personal and social context in which care is provided. There is no common machine language to describe and capture individuals’ goals or their priorities for health or healing. And there is no common machine language to capture the larger community context envisioned by the NCVHS. It is not surprising that health IT systems are poorly designed to support primary care34,35; developers have been given very little to work with.
We need to provide health IT developers with a sufficient primary care data model—linked to the NCVHS community model—that describes, structures, and standardizes this content to support the higher-order primary care functions of integrating, personalizing, and prioritizing care to foster healing and health.35
What Has Been Done?
Much work has been done recently to revise existing classification and terminology tools to support primary care. The World Health Organization (WHO) is nearing completion of the International Classification of Diseases, Eleventh Revision (ICD-11). The International Health Terminology Standards Development Organization (IHTSDO) is preparing to release the Systematized Nomenclature of Medicine-Clinical Terms (SNOMED CT) Primary Care Reference Set. The World Family Medicine Organization (Wonca) International Classification Committee has revised the International Classification of Primary Care-2 (ICPC-2), mapped it to ICD and SNOMED-CT, and is beginning work on ICPC-3. These efforts have all been limited by the absence of a guiding data model. The Comité Européen de Normalisation Technical Committee 251 published a detailed primary care information model,36 and an expert group chartered by the Robert Graham Center in the United States developed a draft data model in 2007,37 but neither model gained wide acceptance, likely lost in the wake of the large-scale events described above.
A New Starting Point?
Figure 2 displays an updated version of the 2007 Robert Graham Center’s primary care data model, along with its key operational components (inputs and outputs).
Draft primary care data model.
CCD =Continuity of Care Document; HEDIS = Healthcare Effectiveness Data and Information Set; HL7 = Health Level Seven International; XML = Extensible Markup Language; TBD = to be determined.
This high-level model is built around 5 core objects: Persons, Problems, Goals, Clinical Modifiers, and Actions. Each object is composed of several data elements.
Persons includes essential demographic and biopsychosocial data elements related to the person experiencing care, capturing trait data expected to be stable with time. Biologic data could include a genetic profile identifying disease risks in addition to current data, such as medication allergies; psychological data could identify internal emotional structures related to self-concept, identity, and autonomy that shape a person’s response to illness; and social and demographic data would identify and capture important social determinants of health.
Problems includes the health and social problems currently known to and addressed by the clinical team providing care, linked where possible to the actions taken over time to address the problem. This concept is similar to the problem list in current practice, with 2 important distinctions: it includes active social problems, and it does not include previously experienced but now inactive clinical events or problems (included in this model as Clinical Modifiers) or risk factors (captured in this model in a genetic profile or as Clinical Modifiers).
Goals includes reason(s) for seeking care (reasons for encounter), expressed goals, priorities and preferences for care, illness burden, and functional status, representing the point of view of the person experiencing care. These elements capture a person’s state data that can and will change with time and that should guide clinicians in providing person-centered care.
Clinical Modifiers includes previous clinical, behavioral, or social events that are no longer active problems but that could or should affect care for current or new problems. Examples might include major medical events (hysterectomy, myocardial infarction, history of cerebrovascular accident); emotional trauma, such as an assault; and secondary or tertiary prevention issues, such as local environmental problems. Clinical Modifiers enables the systematic capture of unstructured but important clinical information clinicians sometimes enter in sticky note fields in current EHRs.
Actions includes the range of actions taken or decisions made during the course of care: engagement of family members in care, engaged health care team members, linkages or referrals to community resources, laboratory or ancillary service use, referral decisions, procedures performed, pharmacy orders, exception or error reporting, and disposition (follow-up plans). The Actions object captures the process of care for problems over time.
The model contains 2 core structural components. An episode structure addresses the linkage of actions to problems, enabling clinical data to be placed in the context of time and earlier actions. In a model that adheres to the episode structure, each problem has a history that traces encounters and actions taken to address the problem. Without this structure, clinical data lose much of their meaning and its validity. One important advantage of this feature is that it enables the calculation of specific disease probabilities for presenting symptoms, as well as the proportion of symptoms that resolve without diagnosis. Data exchange protocols are necessary to standardize inputs and outputs of interoperable clinical data by patients, clinicians, and automated data feeds. The clinical, social, family, and community data required to provide high-quality patient-centered care will increasingly come from patients and their personal devices, from community sources, and from automated data feeds from multiple sources. Examples include direct patient entry of requests for services, import of data obtained outside the practice (ranging from cardiac catheterization results to glucose-monitoring data posted by mobile devices, to automated posts of data from sensors embedded in smartphones, to soil contaminant levels in a census tract), and structured export of data to support clinical care transitions.
This model includes all data elements from the Common Clinical Data Set described by the ONC,38 and it complements the NCVHS community-population health data model shown in Figure 1. The 5 core objects were conceived to capture and codify key social determinants of health (in Persons and Clinical Modifiers) and the family and community context in which personal doctoring occurs (in Persons, Goals, and Clinical Modifiers). Several of these data elements are already specified in the NCVHS model, most clearly seen under the category headings of social attributes, economic resources, collective lifestyles, and cultural context.
Linked together, the 2 models can provide a comprehensive, community-oriented, primary care data model that integrates social, environmental, and clinical information at the personal, community, and population level: Figure 3 illustrates its potential utility in everyday clinical practice. This linkage can provide a roadmap to guide the integration of population health and primary care data necessary to assess the value of primary care to the overall health care enterprise.
Example of potential utility of primary care data model in clinical care coordination.
ACSC = ambulatory care sensitive conditions; CCD = Continuity of Care Document; ER = emergency department; HUD = Housing and Urban Development; PCMH = primary care medical home; Rx = prescription; TBD = to be determined.
Some Distinguishing Primary Care Model Features That Need Immediate Attention
Much work remains to be done to identify the standard content that can bring this model to life; some content is already available but deeply buried in enterprise EHR software. Work is also needed to reduce and realign the technology overhead; current EHR platforms require clinicians to expend considerable effort to collect and enter highly granular clinical and billing data that are minimally useful in supporting patient-centered primary care.36,39 It seems clear that disruptive innovation will be required to re-engineer the primary care health IT infrastructure.
The first challenge is developing the new core content specified in the data model. Prior work to apply the biopsychosocial model in clinical care, current applied theories of heath behavior, and advances in genomics research can collectively guide efforts to identify the core data elements to include in Persons. Further research is needed to identify and operationalize core social determinant standards from the NCVHS model, then partner with patients and community stakeholders to find acceptable ways to collect and integrate these data. The core content for Goals can build upon current efforts to collect and codify patient goals and preferences and reasons for encounter, using existing instruments to measure functional status and illness burden. Although the concept of Clinical Modifiers as structured and codified sticky notes is appealing, work to determine what events to include and where to fit in primary prevention and preventive actions remains to be done. The Wonca International Classification Committee is active in this area of work,40 but no consensus has yet emerged.
The second challenge is to optimize the data model content found in the current generation of EHRs. EHR problem lists are generally unstructured and uncontrolled; they include acute and chronic symptoms and diagnoses, duplicated or overlapping problem and disease labels, risk factors, and some clinical modifiers. Most problem list entries are not referenced to a structured terminology or classification that can facilitate data extraction, display, and analysis at the point of care. Active social, family, or community problems that affect care are rarely recorded. Actions are recorded in detail—particularly immunizations, procedures, prescriptions, laboratory tests, and other items (supplies) that can be billed for—but are not uniformly linked to problems or to standard terminologies. Restructuring this content and structure will require considerable effort.
The third and most difficult challenge will come with re-engineering health IT infrastructure to enable routine collection of core content that aligns with the thought-flow and workflow of primary care while at the same time reducing the technology overhead of the primary care practice. This can be achieved through an interactive record that accepts input directly from persons (patients), clinicians, and automated data exchange (Figure 2). It will require a major human-factors engineering effort to learn how to assemble data from direct person entry, ubiquitous personal devices and sensors, and automated feeds from medical databases, then to sort and filter those data in ways that support the patient-focused, family- and community-contextualized clinical work of primary care. Technical standards for coding and transmission of novel data elements must be created. Although decisions must be made about standards for episode-based data entry and retrieval to operationalize the element of time in the EHR data structure, several current examples of how this might be approached can be found from clinical information systems implemented in other countries.41–44
A Way Forward
The 2007 Harmonizing Primary Care Clinical Classification and Data Standards conference, convened by The Robert Graham Center and Agency for Healthcare Research and Quality, brought together multiple stakeholders to create a strategy map to support primary care health IT transformation.31 The action items from that map provide a good starting point for a renewed effort, including the following steps.
Create a collaborative primary care data standards working group to complete development of the data model and coordinate its testing and dissemination. This expert group would be commissioned to review and revise the current draft data model while being attentive to new ways of collecting and novel ways of synthesizing data, and then work with content area experts to decide upon and/or develop core data elements and measurement options.
Vet the data model with stakeholders, including primary care organizations, federal agencies (eg, NCVHS and ONC), national organizations (eg, National Committee for Quality Assurance (NCQA), National Quality Forum (NQF), and Patient-Centered Primary Care Collaborative (PCPCC), as well as EHR vendors.
Create the business case for the data model across the full range of stakeholders, including primary care practices, vendors, health care systems, and a general public increasingly engaged in developing a high-value health care system and a healthier population.
Develop partnerships with one or a few health IT vendors willing to create and evaluate IT products that integrate the content and structural features of the data model.
Test the data model with demonstration projects in a variety of clinical settings, followed by broader community-based trials. Large-scale trials could occur through alliances with payers, purchasers, and other organizations to incorporate some or all data model components into clinical demonstrations or ongoing initiatives (eg, state innovation model demonstration projects). The model will need testing in several settings to see whether it supports multiple use cases.
Create tools that can enable users (patients, clinicians, practices, and communities) to work directly with their own data at the point of care and where they live. This could be accomplished through partnerships with existing database management vendors or professional organizations (eg, the American Board of Family Medicine’s TRADEMaRQ [Trial of Aggregate Data Exchange for Maintenance of Certification and Raising Quality] and DAIQUERI [Data Abstraction and Intelligence Quality Engine for Research and Improvement] initiatives45), or through new data stewardship infrastructures as illuminated by NCVHS.24
CONCLUSION
It is a propitious moment to act in behalf of a proper data model for primary care. It is an ambitious, intimidating undertaking that is relevant, targeted, and timely. The Proceedings of the 2007 Harmonizing Primary Care Data Standards conference highlight the continued importance of this issue to primary care:
The key decision made by attendees was that it was very important to act now to develop and promote the data model for personal doctoring in the medical home to support the transformations of health IT and personalized health care that are already underway.31
In the recently released Nationwide Interoperability Roadmap report, ONC calls for a set of standards that allow sharing of health information for small (individual patient), big (population-level), and long data (wrapping around the individual and telling their health story over time).38 A primary care data model is an essential step in building national capacity to collect small data, to make it long, and to link it to big data. This will greatly enhance our efforts to improve the health of individuals and communities.
Footnotes
Conflicts of interest: author reports none.
- Received for publication May 26, 2015.
- Revision received May 26, 2015.
- Accepted for publication May 27, 2015.
- © 2015 Annals of Family Medicine, Inc.