HI560 Unit 2 Data Set Description Example

Reviewed by Chester Goodwin, MBA Health Care Data Analytics Purdue University Global Free custom sample in 24 to 48h

This HI560 Unit 2 data set description profiles a composite extract of 21,906 MRI exam rows, 31 fields and 24 months from a hospital suite and an outpatient center before any analysis begins. Purdue Global HI 560, part of the MS in Health Informatics, asks students in the second unit to describe a data set completely enough that others can judge it. The sample states provenance and the join to the image archive, defines a row as one scheduled exam attempt, groups fields by purpose and reports missing values by field and site. The longest section covers what is absent, and a five-step narrowing brings the file to 17,840 exams.

CourseHI560 Health Care Data Analytics
UnitUnit 2
Paper typeData set description
LengthAbout 890 words, 6 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramMS in Health Informatics
UpdatedOctober 2026

Free sample paper for HI560 Unit 2

1

Where the Rows Came From: A Unit 2 Data Set Description of 21,906 MRI Exams From Two Imaging Sites

[Student Name]

Purdue University Global

HI560: Health Care Data Analytics

Unit 2 Data Set Description

[Instructor Name]

[Date]

Thistlewood Health, its sites, fields and every count are composite; the sources cited are real.

What this part is doingStating provenance before any count means every later figure in the course inherits a source the reader has already been shown.
2

Provenance

The extract was pulled on January 15, 2026, from Thistlewood Health's radiology information system, covering every MRI exam scheduled from January 1, 2024, through December 31, 2025. Each exam row was joined by accession number to the image archive's series log, which records each acquired sequence with its time stamp. The query selected exams by modality code and scheduled date, not by completion, so canceled and incomplete exams are included. The hospital suite contributes 12,470 rows and the Fennimore outpatient center 9,436.

Unit of Analysis

One row is one scheduled exam attempt, identified by accession number. A patient with two exams on different days appears twice; a patient whose exam stopped and was finished in a second slot the same day may appear once or twice depending on how the technologist handled the record, which the quality assessment examines. Patients are not the unit here, because the question concerns what happens to exams.

What this part is doingDefining a row before counting rows prevents the most common confusion in later units, whether a figure counts exams, attempts or people.
3

Fields by Purpose

Before analysis, the patient's chart number, name and birth date were stripped out and replaced with a study key and an age in whole years.

1. Exam descriptors: site, scanner identifier, procedure code, body region, contrast ordered, protocol name, scheduled slot length in minutes.

2. Patient descriptors: age, sex, patient class (outpatient, inpatient or emergency), height and weight where recorded, the booking question on claustrophobia (yes, no or not asked).

3. Process fields: scheduled time, check-in time, scan start and end time, sedation or anxiolytic ordered, anesthesia involvement.

4. Outcome fields: completion status (complete, incomplete, canceled), incompletion reason chosen by the technologist, number of series acquired, number required by the protocol.

5. Linkage fields: accession number, order number, prior attempt accession where the technologist recorded one.

What Is Missing

Missing data are reported by field and by site, because a gap concentrated at one site can look like a difference between sites.

1. Incompletion reason is blank on 22 percent of incomplete exams at the hospital and 9 percent at Fennimore. Where present, technologists choose among claustrophobia, pain, motion, equipment and other, and the boundary between motion and claustrophobia is applied differently at the two sites.

2. Weight is missing on 9 percent of hospital rows and 17 percent of Fennimore rows, so body size cannot be used for adjustment without losing many Fennimore exams.

3. The booking claustrophobia question reads not asked on 14 percent of hospital rows and 3 percent of Fennimore rows, because the hospital's referral clinics book some exams directly.

4. Scanner identifier is blank on 230 rows, all from a three-week period after a software upgrade.

5. Prior attempt accession is filled on only 41 percent of exams that were repeats, so repeat attempts must be found by matching patient, procedure and date.

The field that decides the outcome, completion status, is complete on every row, but the field that would explain it, the reason, is the least complete in the file.

What this part is doingReporting each gap by site, not just overall, is what keeps a recording difference from being mistaken for a performance difference later in the course.
4

Narrowing to the Analytic File

The later units compare adult outpatient first attempts that were scheduled without sedation. The file narrows in five steps.

1. Hospital: 12,470 rows. Remove 1,480 inpatient and emergency exams, leaving 10,990.

2. Remove 310 exams for patients under 18, leaving 10,680.

3. Remove 610 exams with sedation, an anxiolytic or anesthesia ordered in advance, leaving 10,070.

4. Remove 160 repeat attempts, leaving 9,910.

5. Remove 60 duplicate accession rows created by protocol changes, leaving 9,850.

Fennimore: 9,436 rows, no inpatient or emergency exams. Remove 640 exams for patients under 18, leaving 8,796. No exams had sedation ordered, because Fennimore has no nurse on site to give it. Remove 754 repeat attempts, leaving 8,042, and 52 duplicate rows, leaving 7,990.

The analytic file holds 17,840 exams: 9,850 at the hospital and 7,990 at Fennimore. Fennimore's larger number of repeat attempts deserves a note: when an exam stops there, the patient is often rebooked into a later slot the same week, which the hospital less often does.

How the Description Was Checked

Counts at each narrowing step were reproduced by a second analyst from the same query. Field definitions were confirmed with the imaging informatics lead, who also explained the scanner identifier gap. Describing data before analysis in this way follows the view that data quality depends on whether a data set suits a particular use, not on whether it is error-free in general (Wang & Strong, 1996), and the framework used in Unit 4 builds on that view (Kahn et al., 2016). A review of electronic record quality methods also found that completeness and correctness are the dimensions most often assessed, and that they must be judged against the intended reuse (Weiskopf & Weng, 2013).

Questions for the Data Owner

1. Can technologists record a limited study separately from a complete one?

2. Is the booking question asked the same way at both sites?

3. When an exam stops and resumes the same day, which accession carries the images?

4. Can the anxiolytic order be linked to the booking question answer?

5

References

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., 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), 1244. https://doi.org/10.13063/2327-9214.1244

Wang, R. Y., & Strong, D. M. (1996). Beyond accuracy: What data quality means to data consumers. Journal of Management Information Systems, 12(4), 5-33. https://doi.org/10.1080/07421222.1996.11518099

Weiskopf, N. G., & Weng, C. (2013). Methods and dimensions of electronic health record data quality assessment: Enabling reuse for clinical research. Journal of the American Medical Informatics Association, 20(1), 144-151. https://doi.org/10.1136/amiajnl-2011-000681

HI560 Unit 2 instructions, in plain terms

Unit 2 typically asks for a written description of a health care data set you will analyze in later units. Expect to state where the data came from, define the unit of analysis, list the fields with types and allowed values, report missing data and explain any narrowing to an analytic file. Many prompts suggest about five pages plus a data dictionary. State the extraction date and query logic before any counts, because every later figure depends on them. Group fields by purpose rather than alphabetically. Report missing values by subgroup as well as overall, since gaps concentrated in one group can look like real differences later. Close with questions for the data owner, which show the file was examined closely.

Inside the HI560 Unit 2 example

Provenance comes first: the extraction date, the period covered, the join by accession number to the image archive and the row counts by site. The unit of analysis is defined as one exam attempt, with a note on same-day second slots. Fields are grouped into exam descriptors, patient descriptors, process fields, outcome fields and linkage fields. Five numbered gaps follow, from blank incompletion reasons to unlinked repeat attempts, each reported by site, and the highlighted sentence contrasts the always-complete outcome field with the least complete explanatory one. The narrowing section takes each site's rows through five exclusions to 9,850 and 7,990 exams. A short section explains how counts were checked, citing work on fitness for use, and four questions for the data owner close the paper.

Where the points sit in the HI560 Unit 2 rubric

Data set descriptions are commonly graded on completeness, accuracy, organization and attention to data limitations. The largest share often goes to completeness: provenance, unit of analysis, field definitions and missing data must all be present. Accuracy is judged on whether counts reconcile through each narrowing step. Organization earns credit when fields are grouped logically and tables are easy to scan. Attention to limitations is rewarded when missing data are reported by subgroup and their likely effect is noted. A data dictionary appendix and APA citations complete the rubric. Descriptions that list fields alphabetically with no missing-data analysis, or that jump to summary statistics, lose points.

Common HI560 Unit 2 mistakes, and how to avoid them

Students often lose points by skipping provenance or giving counts without an extraction date. Another common problem is an undefined unit of analysis, so readers cannot tell whether a row is a patient or a visit. Missing data are frequently reported only overall, which hides site differences. Some descriptions fill in missing values before describing the file. A narrowing sequence whose counts fail to reconcile is usually the first thing marked. If your data come from a registry, claims file or survey instead of an electronic record, send the field list and the prompt, and a description can be written around your own file.

Get an HI560 Unit 2 example written to your instructions

Attach the file your section supplied, or its data dictionary if the file is large, plus the rubric and the assignment text for Unit 2. The free first sample is ready in 24-48h, built from that file's own fields and gaps rather than Thistlewood's, with missingness reported by group wherever the data allows it. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More HI560 papers and MS in Health Informatics samples

HI560 Unit 2 questions, answered

How much detail belongs in a data set description?

Enough that a reader could decide whether the file suits a question without opening it. That usually means source, date range, extraction date, unit of analysis, row count, a field table with types and missing percentages, and a note on anything derived. Summary statistics generally wait for the descriptive unit, so this paper stays with structure and completeness.

Should missing values be filled in before describing the data?

No. Describe the file as received, with every gap counted, and leave handling decisions for later units where they can be justified against a specific analysis. Imputing values at this stage hides the very pattern a reviewer should notice, especially when one site or one group accounts for most of the blanks.

What if my data set has no data dictionary?

Build a short one inside the description, labeled as a reading of the file rather than an official source. For each field, infer the type and allowed values from the data, note anything ambiguous, and list the questions a data owner would need to answer. That list of questions often earns credit on its own, because it shows the file was actually examined.

Why report missing data separately for each site?

A gap concentrated at one site can later look like a real difference between sites, so the description shows where blanks fall before anyone compares groups.

Where can I find a free HI560 Unit 2 sample paper?

You can read the complete Unit 2 description here, from provenance and field groups to missing data by site and the narrowing to 17,840 exams.