| Course | HLTH 2120 Health Informatics |
|---|---|
| Week | Week 2 |
| Paper type | Terminology brief |
| Length | About 1,080 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | BS in Healthcare Administration |
| Updated | October 2026 |
Free sample paper for HLTH 2120 Week 2
Five Words Held Apart: Data, Information, Structured Entry, Free Text and the Three Things People Mean by the Record, Tested on One Admission Weight
Student Name
Walden University
HLTH 2120: Health Informatics
Instructor Name
Month Day, Year
Five Words Held Apart: Data, Information, Structured Entry, Free Text and the Three Things People Mean by the Record, Tested on One Admission Weight
Purpose
Informatics discussions go wrong when people use the same word for different things. A nurse, a coder and a records manager can all say "the record" and mean three different collections of documents. This brief separates five terms that are often blurred and then tests each distinction on one concrete example: the weight recorded for a patient admitted to a medical-surgical unit. If a distinction cannot be applied to that one weight, it is not useful. The example is a composite drawn from common practice, not a real patient.
Data and Information
Data are recorded values without interpretation. Information is data placed in a context that gives it meaning for a purpose. Informatics texts commonly describe a hierarchy running from data to information to knowledge, in which each level adds context and interpretation (Hoyt & Hersh, 2022).
Test on the example. The entry "82" in a field labeled weight is data. It becomes information only when the reader knows the unit (kilograms, not pounds), the date and time, whether it was measured on a scale or reported by the patient and whose weight it is. "82 kg, measured on the bed scale at 1410 on admission" is information a pharmacist can use to calculate a weight-based dose. "82" alone is dangerous, because a reader who assumes pounds would calculate a dose less than half of what the patient needs. The distinction holds: the same number is data or information depending on the context recorded with it.
Structured Entry and Free Text
Structured entry records a value in a predefined field with rules about what it may contain, such as a number, a unit chosen from a list and a date. Free text records language typed or dictated by the writer, without constraints on form. Structured data can be counted, compared, checked and passed automatically to other systems; free text can capture nuance and context that no field anticipated, but a computer cannot reliably use it without processing it first (Rosenbloom et al., 2011).
Test on the example. On most units the admission weight is entered in a structured flowsheet field with a unit selector and a required method of measurement. That structure is what allows the weight to flow into pharmacy dosing tools and nutrition calculations. But suppose the nurse also writes in a free-text note: "Patient unable to stand; weight per daughter, who thinks he has lost weight recently." That sentence carries the most important fact about the number, that it may be wrong, and it sits where no dosing tool will read it. The distinction holds, and it shows the cost of each form: the structured field travels but loses nuance, the free text keeps nuance but stays put.
Three Things People Mean by the Record
People use "the record" for at least three different collections, and confusing them causes real problems.
The electronic health record system. The software and everything stored in it, including drafts, audit logs, alerts and data the organization uses for operations.
The legal health record. The documents and data an organization defines, in its own policy, as its official business record of care, the version it produces in response to a subpoena or court order. Organizations decide what belongs in it, and professional guidance recommends that each organization define it explicitly (American Health Information Management Association, 2011).
The designated record set. Under the HIPAA Privacy Rule, the records a covered entity uses to make decisions about individuals, including medical and billing records, which the individual may inspect, obtain copies of and ask to have corrected (45 C.F.R. § 164.501). This set can be larger than the legal health record, because it includes billing records.
Test on the example. The admission weight in the flowsheet belongs to all three. The draft weight the nurse started to enter and canceled exists in the system's audit log, so it is part of the first collection, but it is not part of the legal health record under most organizations' policies and would not normally be produced for a court. The daughter's statement in the free-text note is part of all three. If the patient later asked to see his records, the weight and the note would be released because they are in the designated record set, and he could ask to amend a weight he believed was wrong. The distinction holds, and it shows that a question like "is that in the record?" has three possible answers.
Two Related Terms: Metadata and Provenance
Two more terms come up constantly in this course and are worth placing beside the five. Metadata is data about data: the unit, the timestamp, the user who entered a value and the method of measurement are all metadata about the weight. Much of what turns data into information, in the sense defined above, is metadata. Provenance is the history of where a value came from and how it changed. A weight whose provenance shows it was measured on a bed scale by the admitting nurse and never edited deserves more trust than one whose provenance shows it was copied from a prior admission. Electronic systems record a great deal of metadata automatically, in audit logs, but often do not display it where clinicians make decisions. That gap between what the system knows and what the screen shows is one of the recurring themes of informatics.
Why the Distinctions Matter
Holding these terms apart is not academic tidiness. The data and information distinction explains why a weight without a unit is a safety risk. The structured and free text distinction explains why the most important caveat about the weight never reached the pharmacist. And the three meanings of the record explain why a records manager, a lawyer and a patient can give different answers about the same entry without any of them being wrong. In the rest of this course, when I write about the record, I will say which of the three I mean, and when I write about data quality, I will separate a missing value from a value missing its context.
The example also previews next week's assignment. The weight does not stay in the flowsheet. It moves into pharmacy, nutrition and quality reports, and at every step it can lose the context that made it information. Following that movement is the next task.
References
American Health Information Management Association. (2011). Fundamentals of the legal health record and designated record set. Journal of AHIMA, 82(2), Expanded online version.
Definitions, 45 C.F.R. § 164.501 (2024).
Hoyt, R. E., & Hersh, W. R. (Eds.). (2022). Health informatics: Practical guide (8th ed.). Lulu.com.
Rosenbloom, S. T., Denny, J. C., Xu, H., Lorenzi, N., Stead, W. W., & Johnson, K. B. (2011). Data from clinical notes: A perspective on the tension between structure and flexible documentation. Journal of the American Medical Informatics Association, 18(2), 181-186. https://doi.org/10.1136/jamia.2010.007237
Reading the HLTH 2120 Week 2 instructions
A terminology brief at this stage usually asks you to define a small set of informatics terms and show that you can apply them. Choose terms that are often confused, define each briefly from a reliable source and then test every definition on the same concrete example. If a distinction does not change how you would treat the example, it is not doing work. Use regulations or professional guidance for terms with legal meanings, such as what counts as the record. Explain why each distinction matters in practice, ideally with a safety or legal consequence. Keep the brief short and organized by term, and close by showing how the terms will be used in later work rather than repeating the definitions.
How this HLTH 2120 Week 2 example is built
The purpose section explains the single-example test. The data and information section shows how 82 without a unit could produce a dose less than half of what the patient needs, citing Hoyt and Hersh. The structured and free text section contrasts the flowsheet weight with a daughter's estimate in a note, citing Rosenbloom and colleagues. The record section defines the system, the legal health record from AHIMA guidance and the designated record set from the federal regulation, then places a canceled draft and the note in each. A new section adds metadata and provenance. The closing explains what each distinction is for and introduces the following week's data flow map.
HLTH 2120 Week 2 rubric: what earns full marks
Faculty usually reward briefs whose distinctions hold up when applied, so the test on a concrete example carries most of the weight. Definitions copied without application earn little. Credit increases when the writer uses authoritative sources for legally defined terms and shows why a distinction matters, for instance in dosing or in responding to a records request. Faculty value precision, such as noting that the designated record set can be larger than the legal health record. Brevity and clear organization are expected for this genre. A closing that links the terms to later assignments shows they will be used. Correct APA citations, including for regulations, complete what is assessed.
HLTH 2120 Week 2 help from the desk
Terminology briefs often become glossaries, with each term defined in isolation and never applied. Others use the same word in two senses within one paragraph, which undermines the point. Some cite a dictionary or a vendor's website for terms that have legal definitions. Pick one example before you write any definition, then ask of each term what it changes about the example. Use the regulation itself for terms like designated record set. Read your draft looking for places where you used a defined term loosely. Our writers can prepare a terminology brief for this course that defines each term from a reliable source and tests it on one concrete example.
Get a HLTH 2120 Week 2 example written to your instructions
Send the Week 2 prompt, any term list the classroom hands out, and the rubric; the desk returns a brief that defines the set, works one described encounter and formats to the style your section requires. Free for the first custom piece, delivered in 24-48h. Term lists differ by instructor, so the one from your own classroom governs.
More HLTH 2120 papers and BS in Healthcare Administration samples
- HLTH 2120 Week 1: Health Record Purpose Post
- HLTH 2120 Week 3: Patient Weight Data Flow Map
- HLTH 2120 Week 4: Barcode System Evaluation
- HLTH 2120 Week 5: Data Quality Audit
- HLTH 2120 Week 6: Alert Override Discussion Post
- HLTH 2120 Week 7: Record Access Privacy Analysis
- HLTH 2120 Week 8: Interoperability Brief
- HLTH 2120 Week 9: Workflow Change Analysis
- HLTH 2120 Week 10: System Change Implementation Memo
- HLTH 2120 Week 11: Health Informatics Reflection
- HLTH 1015 Week 2: Evidence-Based Self-Assessment
- HLTH 1005 Week 2: Health System Overview
HLTH 2120 Week 2 questions, answered
Where can I find a free HLTH 2120 Week 2 sample paper?
The brief, with every term tested on the admission weight, is available on this page in full and free of charge.
What is the difference between data and information in the HLTH 2120 Week 2 brief?
The number 82 is data; 82 kilograms measured on the bed scale at admission is information, because the unit, time and method give it meaning for dosing.
Why does structured entry matter for the weight?
A structured field with a unit selector lets the weight flow into pharmacy dosing tools, while a caveat typed in free text stays in the note where no tool reads it.
What are the three meanings of the record?
The EHR system and everything stored in it, the legal health record an organization defines in policy and the HIPAA designated record set patients can access and ask to amend.
What are metadata and provenance?
Metadata is data about data, such as unit and timestamp; provenance is the history of where a value came from and how it changed.