D190 Task 2 Data Analysis Memo Example

This D190 Task 2 example is a data analysis memo to a composite hospital's HIM director showing that unbilled accounts doubled in the spring and have not fully recovered. WGU D190, Introduction to Healthcare IT Systems, has BS Health Information Management students analyze twelve months of revenue cycle data and report what it shows. The sample opens with the bottom line, summarizes monthly discharges, discharged-not-final-billed accounts, coding turnaround and open queries in a table, and identifies three trends: the spring rise followed coding vacancies rather than volume, queries open longer than a week tripled and stayed high, and a smaller winter rise came before any staffing change. It explains what monthly totals cannot prove and recommends a weekly unbilled report by hold reason and a query escalation rule.

CourseD190 Introduction to Healthcare IT Systems
TaskTask 2
Paper typeData analysis memo
LengthAbout 1,000 words, 3 pages
FormatAPA 7
SchoolWestern Governors University (WGU)
ProgramBS Health Information Management
UpdatedSeptember 2026

Free sample paper for D190 Task 2

1

Memorandum

To: Director of Health Information Management, Lakeview Regional Hospital

From: HIM Data Analyst

Date: September 29, 2026

Re: Trends in unbilled accounts, coding turnaround and open physician queries, October 2025 to September 2026

 

Purpose and Bottom Line

You asked for an analysis of the past year's revenue cycle data from the HIM department. The main finding is that the dollar value of accounts discharged but not final billed (DNFB) roughly doubled between February and May, when two coding positions were vacant, and has not returned to its fall level even though coding staff are back to full strength. The data point to a second cause that has outlasted the staffing gap: physician queries left unanswered for more than a week. I recommend three actions below.

The Data

The table summarizes the monthly figures from the abstracting system, the patient accounting system and the query tracking log. DNFB is measured on the last day of each month.

MonthDischargesDNFB ($ millions)Average days, discharge to codedQueries open more than 7 daysCoding positions filled (of 9)
Oct 20251,2102.13.2149
Nov 20251,1802.03.1129
Dec 20251,2502.33.4169
Jan 20261,3202.63.8198
Feb 20261,2403.45.1227
Mar 20261,2904.26.3317
Apr 20261,2304.66.9387
May 20261,2604.46.6417
Jun 20261,2003.14.8279
Jul 20261,1902.74.1249
Aug 20261,2202.63.9269
Sep 20261,2402.84.0299

Trend 1: The Spring Rise Followed Coding Vacancies, Not Volume

Discharges stayed within a narrow range all year, from 1,180 to 1,320 a month, so patient volume does not explain the change. DNFB rose from about $2 million in October and November to a peak of $4.6 million in April, and average time from discharge to coding more than doubled, from 3.1 days to 6.9 days. The rise began in January, when the first coding position became vacant, and was steepest in February through May, when two of nine positions were empty. When two contract coders started in June, DNFB fell by $1.3 million in one month. Measured per discharge, unbilled dollars went from about $1,740 in October to about $3,740 in April and were about $2,260 in September.

What this page is doingEach claim is tied to figures in the table, and volume is ruled out as a cause before staffing is named. A memo that reports numbers without eliminating other explanations is weaker.
2

Trend 2: Queries Open Longer Than a Week Tripled and Stayed High

The number of physician queries open for more than seven days rose from 12 in November to 41 in May, more than three times higher. Unlike coding turnaround, this measure has not recovered: it was still 29 in September, about twice the fall level. An account cannot be final coded while a query about its documentation is unanswered, so unanswered queries hold revenue regardless of how many coders are working. This is the most likely reason DNFB has settled around $2.6 to $2.8 million rather than returning to $2.0 million.

The query backlog may have started as a side effect of the vacancies, since coders who were behind had less time to follow up on queries, but it now appears to have its own momentum. Physicians' experience of queries matters here. In a qualitative survey of hospitalists and surgeons at a safety-net academic medical center, physicians accepted the importance of documentation integrity but described queries as disruptive to their workflow and emotionally taxing, and many saw physician advisors as trusted leaders who improved communication and engagement (Nepal et al., 2026).

Trend 3: A Smaller Winter Rise Before the Vacancies

December and January show modest increases in DNFB and turnaround before any major staffing change. January had the highest discharge count of the year, 1,320, and the holiday period usually brings coder leave and slower physician responses. This seasonal effect was small, about $0.5 million, but it means the department started the spring vacancies from a weaker position than in the fall.

What the Data Cannot Show

These are monthly totals, so they show patterns but cannot prove cause. To confirm that open queries are holding accounts, we need account-level data showing the reason each DNFB account is on hold: awaiting coding, awaiting a query response or awaiting missing documentation. DNFB dollars also depend on the charges of the accounts on hold, so a few high-cost surgical cases could inflate a month. Finally, filled positions are not the same as coding productivity; new and contract coders may code fewer charts per day than experienced staff.

What this page is doingThe memo states the limits of the data and names the specific additional data that would test the explanation. That honesty strengthens the recommendations rather than weakening them.
3

Recommendations

First, add a weekly DNFB report by hold reason, drawn from the patient accounting system, so that the department can see how many dollars are waiting on queries, coding and documentation separately. This will confirm or correct the explanation in this memo within a month.

Second, create a query escalation path. Queries unanswered after three days would trigger an automatic reminder in the physician's EHR inbox; after seven days, the clinical documentation specialist would contact the physician advisor, who would follow up directly. Query wording and escalation must stay within industry query practice guidelines, which require queries to be clear and non-leading (American Health Information Management Association & Association of Clinical Documentation Integrity Specialists, 2022). Target: fewer than 15 queries open more than seven days by the end of December.

Third, reduce the department's exposure to future vacancies. Keep a standing agreement with the coding contractor so that temporary coders can start within two weeks, and evaluate computer-assisted coding for the highest-volume outpatient and inpatient account types. A narrative review found that computer-assisted coding has shown value for coding accuracy and quality, while stressing that implementation requires sound change management and a redesign of coding workflows (Campbell & Giadresco, 2020). Target: DNFB below $2.3 million and discharge-to-coded time below 3.5 days by the end of the calendar year.

I would be glad to walk through the account-level report with you once the first week of data is available.

References

American Health Information Management Association & Association of Clinical Documentation Integrity Specialists. (2022). Guidelines for achieving a compliant query practice (2022 update). AHIMA.

Campbell, S., & Giadresco, K. (2020). Computer-assisted clinical coding: A narrative review of the literature on its benefits, limitations, implementation and impact on clinical coding professionals. Health Information Management Journal, 49(1), 5-18. https://doi.org/10.1177/1833358319851305

Nepal, S., Allyn, R., Keniston, A., & Pierce, R. (2026). A conundrum in clinical practice: Clinical documentation queries, more money, or more problems? A qualitative survey of hospitalists and surgeons in a safety-net academic medical center. Journal of Hospital Medicine. Advance online publication. https://doi.org/10.1002/jhm.70398

What the D190 Task 2 instructions ask

The second D190 task asks you to analyze a data set and communicate findings in a memo. You will usually summarize the data, identify trends, explain possible causes, note limitations and recommend actions for a named reader. The memo format matters: it should lead with the main finding, stay concise and speak to the decision maker. Evaluators look for trends supported by specific figures, causes offered cautiously with the data that point to them, limitations stated honestly and recommendations the reader can act on. A memo that reports numbers without interpretation, or claims causes the data cannot show, will not meet the analysis aspects. The memo should name its reader.

How this D190 Task 2 example is built

The memo begins with its purpose and bottom line in two sentences, as a busy director would want. A table summarizes the monthly data so later statements can be checked. Each trend has its own heading that states the finding, followed by the figures that support it and a possible explanation. The section on what the data cannot show explains the limits of monthly totals and suggests the account-level data that would confirm causes. Recommendations are numbered, specific and linked to the trends, such as a weekly report by hold reason. The memo closes with an offer to review results after two months, which suits the format.

Where the D190 Task 2 rubric puts the marks

D190 Task 2 aspects are scored competent, approaching competence or not evident. A format aspect checks that the memo is addressed, concise and led by the main finding. A data summary aspect rewards accurate presentation of the figures. A trends aspect looks for patterns identified with evidence. An interpretation aspect asks for possible causes offered with appropriate caution. A limitations aspect wants what the data cannot show. A recommendations aspect looks for actions tied to the findings. Evaluators check that every figure in the text matches the table and notice memos that respect the reader's time.

Memos that keep interpretation separate from the data table make each claim easy to check, and a clear closing request helps the director act.

D190 Task 2 help: what sends it back

Data memos come back most often because they bury the finding. Put the bottom line first. Second, trends are described without numbers. Quote the figures that show each one. Third, causes are stated as facts. Use careful language and point to the data that suggest each cause. Fourth, limitations are skipped. Say what monthly totals cannot prove and what data would help. Finally, recommendations should be specific and owned, such as a weekly report produced by a named role, so the director knows exactly what to approve.

Read the memo once as the director would, looking only at the first paragraph and the headings. If the main finding and the main request are not clear from those alone, rewrite the opening.

Get a D190 Task 2 example written to your instructions

Send the task data and rubric aspects from your D190 course of study. We write a custom data analysis memo to those exact aspects, returned in 24-48h. The first custom sample is free.

More D190 papers

Other Health information sample papers

D190 Task 2 questions, answered

How long should a D190 memo be?

Short enough for a director to read quickly, usually two to three pages with a table. The sample leads with the bottom line and keeps each trend to a short section.

Should a D190 memo include recommendations?

Yes. A memo to a decision maker should end with actions. The sample recommends a weekly unbilled report by hold reason and an escalation rule for open queries.

What is DNFB in D190 Task 2?

Discharged not final billed: accounts for patients who have left the hospital but whose claims have not been sent. It is a common measure of how quickly coding and billing move.

Is the D190 hospital data in the sample real?

No. The monthly figures are hypothetical, created to show the method. The measures used, such as DNFB and query turnaround, are standard in health information management. Real departments track the same measures.

Where can I find a free D190 Task 2 sample paper?

Every part of this D190 Task 2 data analysis memo is shown above, and each D190 section carries a margin note. Send the D190 rubric with your details, and a first Task 2 draft tailored to you is free.