| Course | C792 Data Modeling and Database Management Systems |
|---|---|
| Task | Task 1 |
| Paper type | Clinical workflow analysis |
| Length | About 1,200 words, 4 pages |
| Format | APA 7 |
| School | Western Governors University (WGU) |
| Program | MSN Nursing Informatics |
| Updated | September 2026 |
Free sample paper for C792 Task 1
Workflow Analysis: Suicide Risk Screening in a Rural Emergency Department, Current Paper Process Against the Proposed Structured EHR Process
Student Name
Leavitt School of Health, Western Governors University
C792: Data Modeling and Database Management Systems, Task 1
Course Instructor
Month Day, Year
Workflow Analysis: Suicide Risk Screening in a Rural Emergency Department, Current Paper Process Against the Proposed Structured EHR Process
Purpose and Scope
Workflow is the sequence of tasks, people, information and tools through which work gets done, and informatics research uses the term in several overlapping ways, from the flow of a single task to the coordination of a whole team (Unertl et al., 2010). This analysis concerns one process in a composite 14-bed emergency department (ED) at a 110-bed rural hospital: screening patients for suicide risk and acting on the result. The hospital plans to retire its paper version of the Columbia Suicide Severity Rating Scale screening questions (the C-SSRS) in favor of a structured version inside the electronic health record (EHR) and to widen screening to all ED patients 12 years and older, well beyond the behavioral health patients the national patient safety goal requires it to screen (The Joint Commission, 2019). The analysis documents the current workflow, identifies its failure points, specifies the future workflow and names the data the future workflow must capture. That data list becomes the input to the database design in the next part of this project.
Current times were estimated by observing 20 screenings over four shifts and reviewing 60 records. They are approximate, but they are consistent enough to show where time and information are lost.
Current State: The Paper Workflow
The table lists each step as it happens now, who performs it and what goes wrong.
| Step | Actor | Current practice | Failure point |
|---|---|---|---|
| 1. Decide who to screen | Triage nurse | Screens only patients with a behavioral health complaint, by judgment | Patients presenting for other reasons are not screened |
| 2. Obtain the form | Triage nurse | Takes a paper screener from a folder at triage | Folder empty on 3 of 20 observed screenings |
| 3. Ask the questions | Triage or primary nurse | Reads questions aloud, marks yes or no | Some forms left partly blank |
| 4. Determine risk level | Primary nurse | Interprets answers against a laminated card | Card and form versions differ; risk level sometimes not written |
| 5. Initiate precautions | Primary nurse, charge nurse | Calls charge nurse, who requests a sitter and a room check | Median 34 minutes from screen to sitter at the bedside for high-risk patients |
| 6. Notify provider and liaison | Primary nurse | Verbal report; liaison paged | No record of when the provider was told |
| 7. Store the result | Unit secretary | Scans form into the record after discharge or admission | Result invisible to inpatient nurses until scanned; not searchable |
| 8. Report | Quality coordinator | Manual audit of 30 charts a month | No reliable screening rate for the whole department |
Analysis of the Current Workflow
Three problems explain most of what the table shows. First, the decision about whom to screen depends on individual judgment at triage, which is exactly the gap that universal screening closes; in a multisite study, universal screening lifted the share of ED visits with a documented screen from about a quarter to more than four in five (Boudreaux et al., 2016). Second, the process has no data at all until a person transcribes it: the risk level exists only in handwriting, so nothing can trigger precautions, remind a nurse of a missing answer or tell an inpatient nurse what the ED found. Third, several handoffs are verbal and undocumented, so neither the time from screen to sitter nor the time a provider was informed can be measured.
The workarounds staff use make sense locally but add risk. Nurses keep blank forms in their pockets because the triage folder runs out, which means some are older versions. Charge nurses keep a sticky note of patients on precautions because the tracking board has no field for it.
Future State: The Structured EHR Workflow
In the future workflow, the screener becomes a required section of the triage documentation for every patient aged 12 and older. The EHR presents the six screener questions with branching, so later questions appear only when earlier answers make them relevant, and it will not allow the section to be closed with an unanswered question unless the nurse selects a reason, such as patient unable to respond. When the section is completed, the system calculates the risk level from the answers and displays it on the ED tracking board with a color indicator. A high-risk result opens a precautions order set for the provider to sign, sends a secure message to the behavioral health liaison and adds a task for the charge nurse to arrange one-to-one observation. The time of each of those events is recorded automatically. If the patient is admitted, the most recent screen and risk level appear in the inpatient admission navigator, where the admitting nurse either accepts it or rescreens.
| Step | Future practice | Data captured |
|---|---|---|
| 1. Decide who to screen | Automatic for every patient 12 and older | Patient age, encounter type |
| 2 to 3. Ask the questions | Structured screener with branching and required answers | Each answer, date and time, screener, interpreter use |
| 4. Determine risk level | Calculated by the system | Risk level, calculation version |
| 5. Initiate precautions | Order set and charge nurse task generated on high risk | Order time, observation start time, observer |
| 6. Notify provider and liaison | Tracking board flag and secure message | Notification time, recipient, acknowledgment |
| 7. Store the result | Stored as discrete data at the moment of entry | Available to every user with access |
| 8. Report | Automated report of screening rate and times | Denominator of eligible patients, numerator screened |
Expected Benefits and New Risks
The future workflow should raise the screening rate toward all eligible patients, shorten the time from a high-risk screen to observation and give inpatient nurses the ED result at admission. It also gives the quality coordinator an automatic report instead of a monthly chart audit.
It introduces new risks that the design must address. A required screen at triage adds about two minutes per patient during surges; the design allows the screen to be deferred once, with a reason, and reminds the primary nurse within an hour. More patients screened means more positive screens, most of them low risk, and the behavioral health liaison's workload will rise; the order set therefore routes only moderate and high-risk results to the liaison. Finally, structured sensitive data raises privacy questions, so the screener answers will carry the same access controls as other behavioral health documentation.
Implications for the Database Design
The data column of the future state table defines what the database must hold: patients and encounters, each screening event with its individual answers, the calculated risk level, the interventions ordered and their times, the staff who performed each action and the notifications sent. Several relationships are already visible. A patient has many encounters; an encounter can have more than one screening, since inpatients may be rescreened; each screening has many answers and one risk level; and a high-risk screening can lead to many interventions. The next part of this project turns those entities and relationships into an entity relationship diagram.
References
Boudreaux, E. D., Camargo, C. A., Arias, S. A., Sullivan, A. F., Allen, M. H., Goldstein, A. B., Manton, A. P., Espinola, J. A., & Miller, I. W. (2016). Improving suicide risk screening and detection in the emergency department. American Journal of Preventive Medicine, 50(4), 445-453. https://doi.org/10.1016/j.amepre.2015.09.029
The Joint Commission. (2019). R3 report issue 18: National patient safety goal for suicide prevention. The Joint Commission.
Unertl, K. M., Novak, L. L., Johnson, K. B., & Lorenzi, N. M. (2010). Traversing the many paths of workflow research: Developing a conceptual framework of workflow terminology through a systematic literature review. Journal of the American Medical Informatics Association, 17(3), 265-273. https://doi.org/10.1136/jamia.2010.004333
What the C792 Task 1 instructions ask
The first C792 task asks you to analyze a clinical workflow as groundwork for a data model. Most versions ask you to describe the current workflow, identify problems, propose a future workflow, and explain how the change would affect people, processes and data. Many expect a table or diagram of steps. The task sits in a database course, so the analysis should end by identifying the data the future process creates and uses. The evaluator reads for a workflow described at the level of real steps and roles, and for problems explained by their causes rather than listed as complaints.
How this C792 Task 1 example is built
The sample opens with a definition of workflow and the scope of the analysis. The current state appears as a table with steps, roles, tools and failure points, so the reader sees the whole process at once. The analysis section explains three root problems rather than repeating the table. The future state describes the structured screener, its required fields and what happens after a positive screen. Benefits and new risks are weighed honestly, including alert fatigue. The final section turns the future-state data column into a list of what the database must store, which prepares for the entity relationship model in the next task. Because the table and the analysis are kept separate, the reader sees the facts before the interpretation.
Where the C792 Task 1 rubric puts the marks
Each C792 Task 1 aspect is judged competent, approaching competence or not evident. A current state aspect checks that the existing workflow is described accurately, often with a table or diagram. A problems aspect asks for issues explained by their causes. A future state aspect looks for a clear, feasible redesign. Aspects on impact may ask how people, processes and data will change. A data aspect expects you to identify the information the new workflow requires. Evaluators also look for citations supporting claims about workflow and technology, in APA style, and professional writing. A table that lists steps, roles and failure points tends to show the current state most clearly.
C792 Task 1 help: what sends it back
Workflow analyses are returned most often when the current state is too general. Break the process into steps a person actually performs, with who does each. Second, problems are listed without causes. Ask why each failure happens, such as reliance on individual judgment. Third, future states are sometimes idealized; include the new risks a change creates, such as alerts that staff learn to ignore. Fourth, students forget the data. End with the information the database must hold, because the next task depends on it. Finally, if you collect current state data at work, observe and ask staff rather than relying on policy documents, which often describe the process as it should be, not as it is.
Get a C792 Task 1 example written to your instructions
Send the Task 1 instructions and rubric aspects from your C792 course of study, with the process you are analyzing. We write a custom workflow analysis to those exact aspects, returned in 24-48h. The first custom sample is free.
More C792 papers
Other Nursing (MSN) sample papers
- D161 Task 2 Results Presentation
- D029 Task 2 Technology Annotated Bibliography and Summary
- C922 Task 2 Program Response Plan
- D156 Task 2 Business Case
C792 Task 1 questions, answered
Does a C792 workflow analysis need a diagram?
Many versions ask for a flowchart or swimlane diagram. A step table like this sample's can accompany it and makes failure points easy to find.
How do I collect current state data for C792?
Observe the process, talk with staff who do it and review a sample of records. Policies describe the intended process, so combine them with what actually happens on shifts.
Should C792 Task 1 discuss the database?
Yes, briefly. End the analysis by listing the data the future workflow creates and uses, since that list becomes the starting point for the entity relationship model in Task 2.
Can I use the same project as my other informatics courses?
Usually yes, and it saves time. The sample continues the suicide screening project from C790, which lets the workflow analysis build on a problem, setting and stakeholders already defined.
Where can I find a free C792 Task 1 sample paper?
The current-state table, the analysis and the future workflow are all above with notes. Send your own process and the C792 task, and the first custom analysis costs nothing.