| Course | HIM 680 Advanced Topics in HIM I |
|---|---|
| Module | Module 3 |
| Paper type | graduate milestone assessing the current governance of an enterprise data domain |
| Length | About 1,030 words, 6 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | MS Health Information Management |
| Updated | October 2026 |
Free sample paper for HIM 680 Module 3
Final Project Milestone One: Collected but Not Governed. An Assessment of Social Risk Data Governance at Cedar Prairie Health
[Student Name]
Southern New Hampshire University
HIM 680: Advanced Topics in HIM I
Final Project Milestone One
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Final Project Milestone One: Collected but Not Governed. An Assessment of Social Risk Data Governance at Cedar Prairie Health
Cedar Prairie Health, a composite system of four hospitals and 22 clinics in eastern Iowa, collects a great deal of information about patients' social needs. It does not govern it. Nobody is accountable for its accuracy, the term food insecure means different things in different reports and much of what is collected never reaches the data warehouse. This milestone assesses the current state of social risk data governance as the starting point for a data governance program. It inventories the data elements, maps who touches each, examines definitions and data quality, rates the maturity of current governance and ranks the gaps the program must address.
Approach
The assessment drew on four sources over five weeks: the electronic record's build documentation for the social needs screener and related fields, a query of twelve months of data in the record and the warehouse, interviews with nine people who capture or use the data and a review of every report that mentions social needs. The DAMA body of knowledge frames governance as decision authority over data assets and advises starting with an inventory of what exists and who is responsible (DAMA International, 2017). That framing guided the questions asked in each interview: what the data element means to you, where you get it, what you do with it and who you would call if it looked wrong.
Data Element Inventory
Table 1 lists the six data elements that make up the social risk domain today, where each originates, where it is stored and who uses it. The final column records whether anyone is formally responsible.
Table 1. Social Risk Data Elements at Cedar Prairie Health
| Data element | Captured by | Stored in | Used by | Formal owner |
|---|---|---|---|---|
| Screener answers (10 items) | Clinic medical assistants | Clinic flowsheet | Clinic social workers | None |
| Screener positive flag | Calculated by record logic | Clinic flowsheet | Population health (manual pull) | None |
| Social need problem list entry | Clinicians | Problem list | Care managers | None |
| Social risk codes Z55-Z65 | Hospital coders | Encounter and claim | Finance, quality, health plan | Coding manager (informal) |
| Community referral | Social workers | Referral platform | Social work, equity committee | Vendor contract owner |
| Referral outcome | Community agency | Referral platform | Rarely used | None |
Note. Compiled from build documentation, data queries and interviews, June 2026.
Definitions
The term food insecure has at least three working definitions in the organization. The screener logic flags a patient as positive if either of two food questions is answered sometimes true or often true. The population health team's dashboard counts a patient as food insecure only if the flag was set in the past six months. The equity committee's report counts any patient with a Z59 code in the past year. In a test of 1,000 clinic patients, the three definitions identified 164, 131 and 9 patients respectively. Each number is correct under its own definition, and each has been presented to leaders as the system's food insecurity count. Without an agreed definition and a named owner for it, the organization cannot answer a basic question about its own patients.
Data Quality
Quality was assessed with the framework of Kahn et al. (2016), whose three headings cover adherence to formats and code lists, gaps where values should exist and values that defy belief. On conformance, screener answers use locally invented codes rather than a standard terminology, and 4% of records store free text in fields meant for coded answers. On completeness, 71% of eligible clinic visits had a completed screener, but only 38% of positive screens led to a problem list entry, and fewer than 3% of hospital admissions of patients with a positive screen in the prior six months carried any social risk code. On plausibility, some clinics reported positive rates below 5% while others in similar neighborhoods reported above 25%, a pattern that suggests differences in how the questions are asked rather than in need. These findings echo the national pattern of low social risk coding reported by Truong et al. (2020).
Governance Maturity
Using a simple five-level scale, from ad hoc through defined, managed and measured to optimized, social risk data governance at Cedar Prairie is at the first level. Activity exists, and some of it is good, but it depends on individuals rather than roles, definitions and processes. The informal ownership of codes by the coding manager is the only exception, and even there no one measures whether codes are captured. Gottlieb et al. (2016) observed that social data efforts tend to focus on screening individuals rather than on extracting data that can support population health, and that observation fits: Cedar Prairie built screening carefully but never built the path from screening to usable data.
What Users Need
Interviews showed that users want the same data for different reasons, which is why a single definition must be chosen deliberately. The population health team needs a patient-level flag refreshed monthly to target outreach. The Medicaid health plan wants screening rates and positive rates by clinic each quarter in a standard format. The equity committee wants trends by race, language and neighborhood. Hospital case managers want to see a positive screen at admission so they can plan discharge. No current source serves all four, and each group has built a workaround that adds to the inconsistency.
Ranked Gaps
Five gaps were ranked by a working group of the director, the population health manager and the coding manager, weighing risk to decisions, number of users affected and ease of correction. First, there is no single definition for core measures such as food insecurity and housing instability. Second, no element has a named owner or steward. Third, screener answers are stored in local codes and never loaded to the warehouse. Fourth, coders cannot see clinic screening results during hospital coding. Fifth, referral outcomes are not returned from community agencies in usable form. The first two are governance gaps and come first, because fixing the technical gaps without them would simply move undefined data faster.
Conclusion
Cedar Prairie collects social risk data diligently and governs it hardly at all. The inventory, definitions test, quality review and maturity rating point to the same conclusion: the system needs owners, definitions and standards before it needs new tools. Milestone Two will design the governance framework to provide them.
References
DAMA International. (2017). DAMA-DMBOK: Data management body of knowledge (2nd ed.). Technics Publications.
Gottlieb, L., Tobey, R., Cantor, J., Hessler, D., & Adler, N. E. (2016). Integrating social and medical data to improve population health: Opportunities and barriers. Health Affairs, 35(11), 2116-2123. https://doi.org/10.1377/hlthaff.2016.0723
Kahn, M. G., Callahan, T. J., Barnard, J., Bauck, A. E., Brown, J., Davidson, B. N., Estiri, H., Goerg, C., Holve, E., Johnson, S. G., Liaw, S.-T., Hamilton-Lopez, M., Meeker, D., Ong, T. C., Ryan, P., Shang, N., Weiskopf, N. G., Weng, C., Zozus, M. N., & Schilling, L. (2016). A harmonized data quality assessment terminology and framework for the secondary use of electronic health record data. eGEMs, 4(1), Article 1244. https://doi.org/10.13063/2327-9214.1244
Truong, H. P., Luke, A. A., Hammond, G., Wadhera, R. K., Reidhead, M., & Joynt Maddox, K. E. (2020). Utilization of social determinants of health ICD-10 Z-codes among hospitalized patients in the United States, 2016-2017. Medical Care, 58(12), 1037-1043. https://doi.org/10.1097/MLR.0000000000001418
What the HIM 680 Module 3 instructions ask for
HIM 680's first milestone, in Module Three, is a current-state assessment of data governance for one domain. Most guidelines ask for four to five pages in APA 7. Choose a domain, such as social risk data, problem lists, quality measures or a registry, and inventory its data elements with their sources, storage, users and owners, ideally in a table. Examine how key terms are defined across the organization and test whether the definitions produce different numbers. Assess data quality against a published framework. Rate the maturity of current governance using a stated scale. Then rank the gaps you find with clear criteria, separating governance gaps such as ownership and definitions from technical ones, and explain the order in which they should be addressed.
How this HIM 680 Module 3 final project milestone one example is built
Cedar Prairie Health's assessment uses build documentation, a twelve-month query, nine interviews and a report review, guided by the DAMA body of knowledge. Table 1 inventories six social risk elements and finds only one with even an informal owner. A test on 1,000 patients shows three definitions of food insecurity yielding 164, 131 and 9. Quality is judged with the Kahn team's three-part framework, which turns up local codes, 38% of positive screens reaching the problem list and implausible clinic spreads, echoing Truong and colleagues. Maturity rates at the lowest level, consistent with Gottlieb and colleagues. The HIM 680 milestone ranks five gaps, governance first.
Where the HIM 680 Module 3 rubric puts the points
Rubrics for the first HIM 680 milestone typically reward a clearly bounded domain, a complete inventory of data elements with sources, users and owners, analysis of definitions with evidence of their effects, a data quality assessment organized by a recognized framework, a maturity rating with a stated scale and a ranked list of gaps with criteria. Assessments that excel quantify problems, such as different counts from different definitions, and distinguish governance gaps from technical ones. Graders also value a method section naming sources and interviews. Tables should be readable and dated. Correct APA 7 citations for frameworks and research, and an objective tone that avoids blaming individuals, complete the higher levels.
HIM 680 Module 3 help: the mistakes that cost points
Governance assessments in this course often lose credit by describing a committee instead of the data, listing data elements without owners or users, asserting quality problems without a framework or numbers, skipping definitions or ranking gaps with no criteria. Some jump straight to solutions. If your domain is different, such as medication lists, quality measure data, a cancer registry or patient identity, send the prompt and a description of your organization's situation, and the assessment will inventory and test that domain instead. Even rough counts from a report make the quality section credible. Our HIM 680 assessments inventory every element, test definitions with real counts and separate governance gaps from technical ones.
Get HIM 680 Module 3 written to your instructions
Send your HIM 680 Milestone One guidelines and a description of the data domain you are assessing. The milestone will inventory its elements with owners and users, test conflicting definitions, assess quality with a recognized framework, rate governance maturity and rank the gaps, returned within one to two days, and a first order is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.
More HIM 680 papers and related MS Health Information Management samples
- HIM 680 Module 1 Discussion: What Classification Systems Are For
- HIM 680 Module 2 Terminology Short Paper: Coding Social Needs in Three Systems
- HIM 680 Module 4 Discussion: Who Owns a Data Element
- HIM 680 Module 5 Final Project Milestone Two: A Governance Framework With Standards and Stewards
- HIM 680 Module 6 Data Quality Short Paper: Tracing One Answer From Screener to Warehouse
- HIM 680 Module 7 Final Project Milestone Three: A Data Management and Informatics Plan
- HIM 680 Module 8 Journal: Asking Patients About Hunger
- HIM 680 Module 9 Final Project: The Data Governance Program Proposal
- HIM 680 Module 10 Reflection: What Governing Data Taught the Writer
- HIM 660 Module 4 Discussion: Payment Models and What They Ask of HIM
- HIM 510 Module 6 HIPAA Short Paper: Privacy in Payment, Payer Audits and Records Requests
- HIM 520 Module 1 Discussion: Leadership Styles and What They Change in an HIM Team
- HIM 600 Module 9 Final Project: The Coding Compliance Program Proposal
HIM 680 Module 3 questions, answered
Where can I find a free HIM 680 Module 3 Milestone One sample?
This page carries the full HIM 680 Milestone One assessment of social risk data governance at an Iowa health system, with an element inventory, definitions test, quality review and ranked gaps.
What is a data governance assessment?
A review of how a data domain is currently managed: which elements exist, who captures, stores, uses and owns them, how they are defined, how good they are and how mature the governance is.
Which framework can be used to assess data quality?
Many teams use a three-heading framework covering format rules, missing values and believability, tested against both internal rules and outside sources.
Why test definitions in a governance assessment?
Because different definitions of the same term can produce very different counts, and showing that difference proves the need for agreed definitions and owners.
What is a data governance maturity scale?
A set of levels, often from ad hoc through defined, managed and measured to optimized, used to describe how consistently an organization governs its data.