NUR 6310 Module 2 Current-State Analysis Paper: Medication Reconciliation Workflow Through a Sociotechnical Lens Example

Reviewed by Gwyneth Ollerton, MSN, RN Thomas Edison State University Updated October 2026

Current-state analysis of a clinical workflow is the subject of this NUR 6310 Module 2 sample paper; before a new module is configured at an invented Somerset hospital, an informatics nurse observes how admission medication reconciliation actually happens in practice. Written for TESU's MSN Nursing Informatics course on the systems life cycle, the paper organizes its findings with Sittig and Singh's eight-dimension sociotechnical model, draws on Ash, Berg and Coiera's account of the errors that patient care information systems introduce and uses Koppel and colleagues' finding that an order entry system facilitated 22 kinds of medication error risk. Requirements tied to each finding close this NUR-6310 analysis.

CourseNUR-6310 Nursing Informatics Systems Life Cycle
ModuleModule 2
Paper typeInformatics paper: analysis phase and workflow
LengthAbout 1,107 words, 7 pages
FormatAPA 7 student paper
SchoolThomas Edison State University
ProgramM.S. in Nursing, Nursing Informatics
UpdatedOctober 2026

Free sample paper for NUR 6310 Module 2

1

Three Lists, No Owner: A Current-State Analysis of Admission Medication Reconciliation at a Somerset Hospital

Student Name

M.S. in Nursing, Nursing Informatics, Thomas Edison State University

NUR-6310: Nursing Informatics: Systems Life Cycle

Mentor Name

Month Day, Year

What this page is doingThe title describes what the analysis found, because the redesign has to solve the problem of a medication list kept in three places by people who each believe someone else owns it.
2

Three Lists, No Owner: A Current-State Analysis of Admission Medication Reconciliation at a Somerset Hospital

Why Analyze First

Every person, unit and number in this paper is invented. A 290-bed hospital in Somerset plans to turn on a medication reconciliation module in its electronic health record. The vendor's default design assumes that one clinician collects the home medication list, a physician reviews each medication at admission and the list carries forward to discharge. The hospital's pharmacy and nursing leaders suspected that its actual process was different, and its safety reports showed eighteen events in a year in which a home medication was omitted, duplicated or given at the wrong dose after admission. The informatics nurse leading the analysis phase argued that configuring the module to match the policy rather than the work would automate the problems.

How the Analysis Was Done

Over three weeks, the informatics nurse observed 20 admissions from the emergency department to medical units, at different hours, following each home medication list from the first question to the first inpatient dose. She interviewed emergency nurses, admitting hospitalists, pharmacy technicians, floor nurses and four patients, collected the forms and screens in use and reviewed the eighteen safety reports. She recorded what people did, not what they said they did, and compared the two.

The Sociotechnical Model

Sittig and Singh (2010) proposed that health information technology be studied as part of a complex adaptive system in which eight dimensions shape each other. Three are technical (hardware and software, clinical content and the screen through which people use it). Two concern people and how their work and communication flow. Three concern the setting: the organization's own policies and culture, rules and pressures from outside, and how anyone checks whether the system is doing its job. They argued that problems usually arise at the intersections between dimensions, so that a technical fix to one part can fail because of another.

The analysis showed that in 14 of the 20 admissions, the home medication list was collected more than once by different people, and the versions differed in 9 of them. Physicians reconciled from whichever version appeared first on their screen. Nobody was responsible for deciding which list was right.

DimensionFinding
Hardware and softwareEmergency department and inpatient units use different screens for home medications
Clinical contentNo standard list of common over-the-counter products and supplements
Human-computer interfaceHome list buried three clicks deep; no flag for unverified entries
PeoplePharmacy technicians interview only weekday patients; nights rely on nurses
Workflow and communicationList taken up to three times; physicians reconcile from memory or from the first list they see
Organizational policies and culturePolicy names the physician as owner, but nurses and technicians do most of the work
External rules and pressuresAccreditation requires reconciliation; payer audits focus on discharge
Measurement and monitoringNo measure of list accuracy; only completion is audited
What this page is doingThe table sorts every finding by dimension. Mentors credit an analysis that uses a framework to see where problems sit.
3

How Systems Introduce Errors

Ash et al. (2004) described two kinds of error that patient care information systems introduce. The first arises in entering and retrieving information: interfaces designed for quiet, uninterrupted work are used in busy settings, and structured fields can overload users and fragment the clinical picture. The second arises in communication and coordination: systems can represent work as a tidy sequence when real work is flexible and overlapping, and they can treat communication as a transfer of data when clinicians also need conversation. The authors argued that designers must understand real work before designing.

Both kinds appeared in Somerset. Home medication screens divided each medication into many fields, so busy emergency nurses entered drug names in a free-text comment instead, which the reconciliation screen could not read. And the record assumed a sequence from collection to verification to reconciliation, when in practice the steps overlapped and were repeated.

A Warning From Order Entry

Koppel et al. (2005) examined a common commercial order entry system in a teaching hospital by watching residents work, talking with them in groups and one by one and surveying them. Their list ran to 22 kinds of medication error risk made more likely by the system, grouped as information errors, such as fragmented displays that hid a patient's other medications, and human-machine interface flaws, such as screens that showed pharmacy inventory doses that physicians mistook for recommended doses. Many of the risks were reported by large shares of the house staff surveyed, and the study showed that a system meant to reduce errors could introduce new ones when its design did not match how clinicians worked.

The study's lesson for Somerset was direct: the vendor's default reconciliation screen showed home medications on one tab and inpatient orders on another, the kind of fragmented display Koppel's study linked to errors.

Requirements

The analysis produced requirements for the configuration team, each tied to a finding. One shared home medication list across the emergency department and inpatient units. A required source field for each entry and a status of verified or unverified. A side-by-side view of home medications and inpatient orders on a single screen. A standard pick list for common over-the-counter products and supplements. Pharmacy technician coverage for evenings and weekends, so that a trained person verifies the list for most admissions. A revised policy naming the pharmacy technician or admitting nurse as owner of the verified list and the physician as owner of reconciliation decisions. And a monthly accuracy audit comparing the verified list with a gold-standard interview on a sample of patients.

What this page is doingEach requirement answers a finding, including two that are not about software. Graders look for requirements that cover people and policy as well as screens.
4

Validating the Findings

Before writing requirements, the informatics nurse took her findings back to the people she had observed. In two short sessions, emergency nurses, hospitalists and pharmacy technicians reviewed the eight-dimension table and corrected two points: night pharmacy coverage had been cut the previous year, not never offered, and hospitalists sometimes did call patients' pharmacies, but only when a list looked wrong. Both corrections changed the requirements. The sessions also built support for the redesign among the people who would use it, because they recognized their own work in the analysis.

Limits

Twenty admissions over three weeks may not capture rare situations, and the observer's presence may have changed behavior. The analysis focused on admission and did not follow medications to discharge.

Conclusion

Observation showed that admission reconciliation at Somerset ran on three lists with no clear owner. The sociotechnical model located problems in every dimension, the account of system-induced errors explained why free text and assumed sequences caused trouble and the order entry study warned against fragmented displays. Requirements built from these findings give the configuration team a design that fits the work, along with the staffing and policy changes no screen can provide.

References

Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471

Koppel, R., Metlay, J. P., Cohen, A., Abaluck, B., Localio, A. R., Kimmel, S. E., & Strom, B. L. (2005). Role of computerized physician order entry systems in facilitating medication errors. JAMA, 293(10), 1197-1203. https://doi.org/10.1001/jama.293.10.1197

Sittig, D. F., & Singh, H. (2010). A new sociotechnical model for studying health information technology in complex adaptive healthcare systems. Quality and Safety in Health Care, 19(Suppl 3), i68-i74. https://doi.org/10.1136/qshc.2010.042085

Reading the NUR 6310 Module 2 assignment instructions

TESU's catalog paragraph for NUR-6310 promises techniques that carry organizations from one life cycle stage to the next, and with the course syllabus kept from public view, module two takes the form of an analysis-phase paper on a current workflow. A paper of this kind explains how the current state was studied, sorts findings with an established framework (Sittig and Singh's model is a common choice), draws on evidence about how information systems introduce errors, compares real work with policy and writes requirements linked to each finding, including requirements for people and policy. Some sections assign a workflow diagram or a gap analysis table instead of a narrative. Check whether a swim-lane diagram or process map is expected, how many observations the brief considers enough and whether interview quotations need consent. Analyses that report the number and timing of observations are easier for a reader to trust.

Inside the NUR 6310 Module 2 example

An invented Somerset hospital preparing a new reconciliation module, and its eighteen medication safety reports, open the paper. The analysis method is described: 20 observed admissions, interviews, forms and reports. Sittig and Singh's eight dimensions organize the findings in an eight-row table. Ash, Berg and Coiera's two kinds of system-induced error explain the free-text problem and the assumed sequence. Koppel's study warns against fragmented displays. The requirements, each tied to a finding, come next, with limits before the close. Annotations explain the framework sorting and the requirements that go beyond software. A short section shows the findings taken back to staff for correction before requirements were written.

Reading the NUR 6310 Module 2 grading rubric

Analysis-phase papers are judged on a clear method, findings drawn from real observation rather than policy, accurate use of a sociotechnical or workflow framework, evidence on how systems introduce error and requirements linked to specific findings. Mentors value analyses that compare what people say they do with what they do. Including staffing and policy among the requirements shows that the writer understands the sociotechnical view, and checking findings with staff before writing requirements shows good practice. Reporting how many observations were made, and their limits, shows rigor. The framework's dimensions should be named as the authors named them, with citations in APA style and tables that a configuration team could act on.

Common NUR 6310 Module 2 mistakes, and how to avoid them

Analysis papers often describe the process from the policy manual; watch the real work and note where it departs from policy. A second trap is a list of requirements that are all about screens. Use a framework to sort findings so that none are missed. Tie every requirement to a finding. Say how many cases you observed and when, and take your findings back to the staff you watched so they can correct them. The Somerset analysis can guide yours, and the desk will turn your own observations into a first draft at no cost, following the brief you send.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official Thomas Edison State University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.

More NUR 6310 and M.S. in Nursing, Nursing Informatics sample papers

NUR 6310 Module 2 questions, answered

Where can I find a free NUR 6310 Module 2 sample paper?

The current-state analysis of medication reconciliation at an invented Somerset hospital, from the observations to the requirements, is shown above.

What are the eight dimensions of Sittig and Singh's sociotechnical model?

Technology, content and the screen itself; the people and their workflow; internal policy and culture; outside rules and pressures; and how the system is measured.

How do information systems introduce errors?

Ash, Berg and Coiera named two families: trouble putting data in and getting it out, and trouble coordinating work among people.

Can order entry systems facilitate medication errors?

Koppel and colleagues identified 22 types of medication error risk facilitated by one widely used order entry system.

Why observe workflow before configuring a system?

Policies describe intended work; observation shows real work, and a system built on the policy may automate the problems.