Late in an informatics practicum the writing turns to two questions that decide whether anything you built will survive: how will this be measured, and who is allowed to say what the measure means. That is evaluation design and data governance, and they are one piece of writing rather than two. A metric without a stewarded definition drifts within a quarter; a definition with no metric attached to it is a memo nobody reads. The graded skill at this stage is writing a measure so exactly that a report writer who has never met you could build it and get the number you intended. Your section may print this as NR 640B, NR640B or NR 640-B; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-640B Week 7 asks for
What does an unstewarded metric look like from the clinic floor? It looks like the front desk at a federally funded community health center printing a depression screening rate every Monday while the behavioral health lead prints a different one from the same record system, because one of them counts every visit and the other counts unique clients per year, and neither definition was written down when the reports were built. Both numbers are honest. Both are useless in the same room. Your evaluation section exists so that your project never becomes the third number in that argument.
A measure specification is a small piece of technical writing with a fixed anatomy, and this stage is scored on whether you can produce it. Every measure needs a name, a plain-language statement of what it is supposed to tell somebody, a numerator, a denominator, the inclusion and exclusion criteria that decide who is in each, the exact data source and field the value is pulled from, the time window, the reporting cadence, the person by role who owns the definition, and the target or comparison the number will be read against. Nine of those ten elements are missing from most student drafts, which usually offer a sentence like we will measure whether the new workflow improved documentation. That is an intention, not a measure.
The second demand is the family of measures rather than the single number. Practicum projects tend to bring one outcome measure and stop. Improvement work in health settings is written with at least three types. Process measures tell you whether the change is actually being performed, which is what you look at in the first weeks and the only thing that will tell you why an outcome did not move. Outcome measures tell you whether the thing you cared about changed. Balancing measures tell you whether you broke something else while fixing this, which in informatics is almost always a time cost, a downstream report, or an alert that people now click through without reading. A student who writes all three has demonstrated the reasoning the course is looking for far more convincingly than one who writes a single ambitious outcome.
Governance is the other half. Who has the authority to change a data definition at your organization, what committee or steward approves a new report, what is the process for requesting access to a data set, how is minimum necessary applied when a project needs client-level data, and what happens to a report when the person who built it leaves. In a community health setting these answers are often informal, and writing them down honestly, including where the process is undocumented, is more valuable analysis than describing an idealized governance structure that does not exist where you are standing.
Where our help stops and your practicum begins
The 72 practicum hours in this course are yours and cannot be delegated, condensed or performed by anybody else. We do not complete hours, attend governance or data committee meetings, contact your mentor, your analytics or privacy teams, or produce anything your site or your school verifies. Hour logs, activity and encounter records, mentor and preceptor evaluations, learning agreements and any signed or countersigned form are your own record, and they are never drafted, reconstructed or estimated with our help. We also do not run queries, pull data, validate counts or judge the quality of your organization's data, because none of that can be done from outside the building.
Where we work is the written specification and the argument around it: how a numerator and denominator are worded so they exclude nothing by accident, how inclusion criteria are phrased in the language a report writer uses, how a balancing measure is justified in a paragraph, how a governance narrative describes an approval route without overstating how formal it is, and how the whole section is sourced and cited to published measurement and informatics literature. The value on offer is clearer written reasoning about work you genuinely did.
De-identification tightens at this stage rather than relaxing, because measurement writing pulls toward real records. Nothing identifiable belongs on your page: no client names, record numbers, dates of birth, appointment dates or free-text notes copied from a chart. Sample output, if you show any, carries invented values, and any cell small enough to identify a person in a small clinic population is suppressed or described in words instead. Staff appear by role. If your organization has rules about sharing report layouts or data dictionaries outside the building, those rules apply to your paper, and faculty in an informatics course read for exactly this.
The NR-640B Week 7 method, step by step
Six moves for writing measures somebody else could build without calling you.
-
Write the question before the measure
One sentence: what do you want to be able to say in ten weeks that you cannot say today. Every element of the specification is then chosen to answer that sentence, and measures that answer nothing get cut early instead of late.
-
Build the denominator first and defend its edges
Who belongs in the population, and by what rule. Clients seen at the site during the window, or clients with an active care relationship, or visits rather than clients. Write the exclusions explicitly, since the arguments about a number are nearly always arguments about who was left out.
-
Trace the numerator to a field, not to a concept
Not documentation completed but the presence of a value in the specific structured element where the workflow now records it. If the only evidence lives in free text, say so plainly and describe how it would be counted, because that limitation shapes everything downstream.
-
Add one process and one balancing measure to every outcome
The process measure tells you whether the change happened at all. The balancing measure names what you are watching for harm in: added minutes per encounter, a downstream count that shifts, an alert acknowledgment rate that falls.
-
Name the steward and the approval route in writing
Who by role owns this definition, who must approve a change to it, where the definition will physically live so a future analyst can find it, and how often it is reviewed. An unowned definition has a shelf life of one staffing change.
-
State how the number will be read before you have it
Baseline, target or comparison, and what variation you would treat as real rather than as noise in a small population. Deciding that in advance is what stops a two-point move in a denominator of forty from becoming a success story.
A layout and word budget for an evaluation and governance section
Our frame for a measurement and governance write-up of roughly 1,200 to 1,500 words alongside the specification table. It is our own outline rather than anything the university issues, and your scoring guide outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| The evaluation question | The single sentence your measurement exists to answer, with the decision it would inform. | 110 to 140 |
| Measure specifications | Each measure in prose: numerator, denominator, exclusions, source field, window and cadence. | 320 to 400 |
| Process and balancing set | Why each supporting measure was chosen and what it would reveal that the outcome cannot. | 200 to 250 |
| Data sources and quality | Where each value comes from, how completely that field is populated today, and known gaps. | 180 to 230 |
| Governance and stewardship | Definition owner by role, approval route, where the definition is stored and its review cycle. | 200 to 260 |
| Interpretation rules | Baseline, comparison, the variation you would treat as signal, and what you will not claim. | 150 to 190 |
Evidence craft for measurement and governance writing
Cite a published measurement framework and use its vocabulary. Improvement science, health information management and clinical quality measurement all have literature that defines process, outcome and balancing measures and the elements of a measure specification. Naming one with its year keeps your structure from looking invented.
Report existing data completeness with its base. The field was populated in 47 of the 208 encounters reviewed across one month is a data quality finding. Documentation is inconsistent is an impression, and in a data-facing course the difference is directly scored.
Anchor governance claims to something written. If your organization has a data governance charter, a stewardship policy or a report request process, cite it as an organizational document rather than describing it from memory. Where nothing is written, say that the route is informal and describe how it actually works, which is a legitimate and useful finding.
Keep privacy language technical rather than decorative. Minimum necessary, role-based access, de-identification and small-cell suppression have specific meanings under health privacy regulation and in professional guidance. Use them where they apply, cite the source of the standard, and do not use them as general reassurance.
Five mistakes that cost points in this week's territory
- A measure with no denominator. Counts alone rise and fall with volume, so a numerator reported by itself tells the reader nothing about performance.
- Measuring something the system does not record. If no structured field holds the value, the measure cannot be built, and discovering that in the final week is expensive.
- No balancing measure. An improvement claim with nothing watching for harm reads as advocacy, and in informatics the harm is usually clinician time.
- Governance described as it should be. An idealized committee structure that does not operate at your site is a fabrication dressed as analysis; the honest informal version scores better.
- Interpretation rules written after the number arrives. Deciding what counts as improvement once you can see the result is the oldest way to make a small project look successful.
Before you submit
- Every measure states a numerator, a denominator and its exclusions
- Each value is traced to a named data source and a structured field
- At least one process and one balancing measure accompany the outcome
- A definition steward is named by role with an approval route and a storage location
- Baseline, comparison and the threshold for real change are stated in advance
- No identifiable client or staff information and no small cell appears anywhere
Writing the evaluation plan for your informatics project?
Send the scoring guide, your charter and whatever you have drafted of the measures. A premium original draft comes back in 24 to 48 hours with every measure specified to a source field and stewardship written into the plan, and revisions run until the grade lands.