Informatics Solution Proposal Letter Assignment Guide

This week's deliverable is not the proposal — it is a letter asking for **permission** to write one. That distinction decides everything about the tone and the content. You are informing an administrator of a problem, saying why it matters, and requesting authorisation to develop a solution. You are not pitching a product, and a letter that arrives at a named system and a cost estimate has skipped the step the assignment is actually setting. The persuasion you need is that the problem is real and worth someone's time, not that your answer is right. Keeping the solution out is also strategically correct in a real workplace, since an administrator asked to approve an investigation is being asked for much less than one asked to approve a purchase. It also keeps the letter honest, since at this stage you have not reviewed the products and a recommendation made before that review would be one the rest of the project has to defend rather than reach.

Choosing the issue is the decision that makes the rest of the project workable, because this letter opens a four-week sequence and you will live with the choice. The brief allows a clinical or an administrative issue, so the field is wide, but three properties make an issue tractable: it is specific enough to describe in a sentence, it produces some evidence of harm or waste that you can point to, and it is plausibly addressable by an informatics or technology solution rather than by staffing or training alone. Missed handoff information, duplicated data entry, scheduling failures, medication reconciliation gaps and unreadable documentation all qualify. Test the choice by asking whether a technology solution would actually fix it, because a problem whose real cause is workload will not be solved by software and the later weeks will expose that.

Three hundred and fifty words is short enough that structure matters more than prose. A working shape is: one paragraph stating the problem concretely, one giving the evidence that it is a concern — frequency, consequence, who is affected — one connecting it to something the administrator already cares about, and one making the specific request. The third of those is the one students omit and it is what turns a complaint into a business case: patient safety incidents, regulatory compliance, staff time, throughput, or documentation quality are the currencies an administrator works in. Make the request itself explicit and bounded — permission to investigate and propose, by a stated point — because a letter that ends by hoping the recipient will consider the matter has not asked for anything. Name who is affected as well as what happens, because a problem attached to a specific group of staff or patients is harder to defer than one described as affecting the department.

The three peer-reviewed sources are unusual in a letter and they change how it is written. In workplace correspondence you cannot pause for a literature review, so the evidence has to do its work inside the sentences: a claim that the problem is widespread supported by a study, a claim about the scale of its consequences supported by another, and a claim that informatics solutions of this kind have been effective elsewhere supported by a third. That last one is important — it justifies the request without proposing a specific system. Choose sources that describe settings resembling yours, since an administrator's first objection to any cited evidence is that it came from somewhere unlike here. Introduce each source in the sentence rather than dropping a citation at the end, since a letter reads badly when the evidence appears only as parentheses.

The formatting instruction is specific and easy to get wrong: APA guidelines for **formal business correspondence**, which is a different layout from an APA paper. That means a business letter or memo format — sender and recipient details, date, salutation, a subject line for a memo, block paragraphs, a professional closing — with APA citation conventions used inside the text and a reference page attached. Students routinely submit an APA-formatted essay with a salutation on top, which satisfies neither. Address it to a real role rather than to a generic title, since a letter to *the Chief Nursing Officer* reads as considered and one to *To Whom It May Concern* reads as a template. Keep the letter to a single page, since business correspondence that runs to two is read as a report and the three hundred and fifty words fit comfortably on one.

Two things about the wider project are worth acting on now. This is week two of a four-week sequence and each week builds on the last, so the issue you name here is the issue you will research, design a solution for and evaluate. Choosing something you have genuine access to information about will save considerable difficulty in weeks three to five. And keep the sources you find now, since the same evidence base will support the proposal itself. Write down what you would need to know to design the solution as you draft the letter, because that list is effectively the plan for the next week's work and it costs nothing to capture while the problem is fresh. Note where the data would come from too, because an administrator who agrees the problem is real will ask what you need access to, and having an answer ready shortens the approval.