| Course | CIS 450 Informatics in Healthcare |
|---|---|
| Module | Module 1 |
| Paper type | Informatics theory paper |
| Length | About 1,059 words, 6 pages |
| Format | APA 7 student paper |
| School | Aspen University |
| Program | Health Care Administration |
| Updated | September 2026 |
Free sample paper for CIS 450 Module 1
Why Theory Matters in Health Informatics: Three Models Applied to a Home Blood Pressure Program
Student Name
Health Care Administration Program, Aspen University
CIS 450: Informatics in Healthcare
Instructor Name
Month Day, Year
Why Theory Matters in Health Informatics: Three Models Applied to a Home Blood Pressure Program
Health care informatics sits between clinical care, information science and management. Its theories explain how data become useful knowledge, why technology succeeds or fails in real organizations and why people adopt or resist new tools. This paper introduces three foundational ideas and applies them to a composite primary care practice launching a home blood pressure monitoring program.
The Case
A six-clinician practice gives patients with uncontrolled hypertension a cellular-connected blood pressure cuff. Readings upload automatically to a vendor dashboard, and a nurse reviews them weekly, contacting patients whose averages stay high. After three months, about half the enrolled patients have stopped taking readings, and clinicians rarely look at the dashboard. The practice manager wants to understand why. Commentators on consumer health devices have warned that engagement often fades and that the data rarely reach clinicians in a usable form (Piwek et al., 2016), and the practice seemed to be living that warning.
From Data to Wisdom
A classic informatics framework describes a progression from data, raw values such as 152/94, to information, data given context such as a two-week average of 148/92 for a patient on two medicines, to knowledge, an understanding that this patient's control is inadequate and a dose change is warranted, and finally to wisdom, judgment about how to act for this patient given preferences and circumstances. Technology can deliver data easily; turning data into knowledge and wise action is harder.
Applying the Hierarchy
The dashboard showed individual readings for every patient, a flood of data with little information. Nurses had to calculate averages manually and decide who needed attention. Clinicians saw no summary in the record where they worked. The hierarchy explains the problem: the system stopped at data, leaving people to do the conversion to information and knowledge without support.
The Sociotechnical Model
Sittig and Singh's sociotechnical model holds that health IT succeeds only when eight interlocking pieces line up, from the equipment and clinical content to the screen, the staff and their routines, the organization's own rules, outside regulation and the way performance is monitored (Sittig & Singh, 2010).
Applying the Sociotechnical Model
Several dimensions were misaligned. The interface was a separate dashboard, not the record. Workflow gave review to one nurse once a week, too infrequently for timely action. Communication with patients about readings was irregular, so patients felt no one was watching. Measurement was absent: no one tracked how many patients were still sending readings. The cuffs worked; the system around them did not.
The Technology Acceptance Model
The technology acceptance model holds that people's intention to use a technology depends mainly on its perceived usefulness and perceived ease of use. Holden and Karsh reviewed its health care applications and concluded that it explains much of whether clinicians and patients take up health IT, though it works better when adapted to clinical settings (Holden & Karsh, 2010).
Applying Acceptance
Patients found the cuff easy to use but, without feedback, not useful; readings seemed to vanish. Clinicians found the dashboard neither easy, since it required a separate login, nor useful, since it did not summarize. Low perceived usefulness for both groups explains falling use better than any technical problem.
Theories Side by Side
The table summarizes what each theory explains in the case.
| Theory | Core idea | What it explained | What it missed |
|---|---|---|---|
| Data to wisdom | Value comes from turning data into knowledge and action | Dashboard delivered data, not information | Why people stopped using it |
| Sociotechnical model | Eight interdependent dimensions must fit | Interface, workflow and measurement gaps | Individual motivation |
| Technology acceptance | Use depends on perceived usefulness and ease | Why patients and clinicians disengaged | Organizational and workflow causes |
Redesign Guided by Theory
Using the three lenses, the practice made changes: the vendor feed was integrated into the record with a weekly average and a flag for patients above target; a medical assistant reviewed flags twice weekly; patients received a monthly message summarizing their readings and any changes; and the manager tracked how many enrolled patients were still uploading. Each change addressed a gap one of the theories identified.
Early Results
Two months after the redesign, the share of patients sending readings rose from about half to about three-quarters, and clinicians adjusted medications for more patients. These composite results illustrate how theory-guided changes can target the real causes of failure.
Limits of Theory
Theories simplify. The sociotechnical model lists dimensions but does not say which matter most in a given case. The acceptance model focuses on individual perceptions and can miss organizational constraints. The data hierarchy describes value but not how to build it. Using several theories together compensates for each one's blind spots.
Why Administrators Need Theory
Administrators often judge technology projects by whether the equipment works. Theory shifts attention to whether the whole system, people, workflow, interface and measurement, supports the goal. That shift prevents expensive failures and guides practical fixes.
Informatics as a Discipline
Health care informatics draws on computer science, information science, cognitive psychology, organizational behavior and clinical practice. Its theories reflect that mix: the data hierarchy comes from information science, the sociotechnical model from systems thinking and the acceptance model from management research. Recognizing these roots helps administrators see why no single discipline, and no single vendor, can solve informatics problems alone.
Measuring Success With Theory in Mind
Theory also shapes measurement. The practice now tracks not only cuff uploads but also the share of patients whose averages appear in the record, how quickly flags are reviewed and whether medication changes follow. These measures map to the data hierarchy's steps from data to action, making it clear where the program succeeds or stalls.
Choosing a Theory
For a new project, administrators can match theory to question: the data hierarchy for what information the system should deliver, the sociotechnical model for what must change around it and the acceptance model for how users will respond. Asking all three questions before launch would have prevented the practice's early problems.
Conclusion
The data-to-wisdom hierarchy, the sociotechnical model and the technology acceptance model each explained part of why a home blood pressure program faltered: data without information, misaligned system dimensions and low perceived usefulness. Together they guided a redesign that improved engagement. Informatics theory is practical, giving administrators a structured way to plan, diagnose and improve technology in care.
References
Holden, R. J., & Karsh, B.-T. (2010). The technology acceptance model: Its past and its future in health care. Journal of Biomedical Informatics, 43(1), 159-172. https://doi.org/10.1016/j.jbi.2009.07.002
Piwek, L., Ellis, D. A., Andrews, S., & Joinson, A. (2016). The rise of consumer health wearables: Promises and barriers. PLOS Medicine, 13(2), Article e1001953. https://doi.org/10.1371/journal.pmed.1001953
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
What the CIS 450 Module 1 instructions ask for
Aspen's catalog says CIS 450 explores the theoretical underpinnings of health care informatics among its foundational concepts, and because each module's prompt is released only inside the course, that starting point shaped this example. In a first informatics assignment you will often describe at least one informatics theory or model and apply it to a practice setting you know. Check whether your prompt names specific models. Summarize each model accurately in a few sentences and cite its source. Then apply it to concrete details of your case, showing what it explains and what it misses. End with how the theories would guide action, since graders want theory connected to practice rather than described in isolation.
How this CIS 450 Module 1 example is built
The paper runs about 1,065 words across seventeen headings and includes a three-row comparison table. After the case, each theory is explained and applied in turn: the data hierarchy, the sociotechnical model and the acceptance model. The table compares their core ideas, what each explained and what each missed. A redesign guided by the three lenses, early results, the limits of theory and why administrators need theory follow. Informatics as a discipline, measuring success with theory in mind and choosing a theory close the body. A comment beside the data hierarchy section explains how diagnosing a data-to-information gap points to a specific fix.
Reading the CIS 450 Module 1 grading rubric
Theory application papers are usually graded on accurate explanation, meaningful application, critical evaluation and sources. Each model is explained correctly and cited in APA form, including the original sociotechnical model article and a review of acceptance research in health care. Application uses specific case details rather than general statements. Critical evaluation appears in the table and the limits section. A redesign shows that theory produced action. Graders also reward papers that combine theories to cover each one's blind spots, which this example does deliberately. Clear, parallel sections for each theory make the comparison easy to follow, and the early results section shows that the analysis produced measurable change. Honest limits make the argument more credible rather than less.
Common CIS 450 Module 1 mistakes, and how to avoid them
Papers often spend paragraphs describing theories and a line applying them; reverse that ratio. Students also choose theories that do not fit the case. Another gap is ignoring each theory's limits. Use a table to compare if you apply more than one model. Tie your conclusion to a practical recommendation. A tutor can check whether each theory is applied to specific facts or only named. Keep a short definition of each model in your own words so you can check your application against it. Use one case throughout rather than switching examples, since a single case lets readers compare theories directly. Finish with measures that show whether theory-guided changes worked. Show one action each theory led to.
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 Aspen 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 CIS 450 and Health Care Administration sample papers
- CIS 450 Module 2: Information Systems Across Care Settings
- CIS 450 Module 3: The E-Patient and Participatory Informatics
- CIS 450 Module 4: Data Standards and Interoperability
- CIS 450 Module 5: Quality and Usability of Health Information Systems
- CIS 450 Module 6: Legal and Ethical Issues in Health Data
- CIS 450 Module 7: Evaluating an Information System
- CIS 450 Module 8: An Emerging Technology in Health Informatics
- HCA 499 Module 7: Evaluation Plan With Measures
- HCA 125 Module 5: Capital Budgeting Analysis
- HCA 130 Module 2: Proofreading and Revision as a Habit
- HCA 305 Module 5: Practice Finances and Daily Reconciliation
CIS 450 Module 1 questions, answered
What does CIS 450 Module 1 usually ask for?
Aspen's CIS 450 description begins with the theoretical underpinnings of health care informatics, so a paper applying informatics theory is a typical first assignment. Check your classroom prompt.
What is the sociotechnical model?
A model holding that health IT succeeds only when eight interdependent dimensions, from hardware and interface to workflow, culture, regulation and measurement, fit together.
What does the technology acceptance model predict?
That intention to use a technology depends mainly on how useful and how easy to use people perceive it to be.
Where can I find a free CIS 450 Module 1 sample paper?
The informatics theory paper above is complete, comparison table and redesign included. It opens the eight CIS 450 samples.
What is the data-information-knowledge-wisdom hierarchy in CIS 450 Module 1?
A framework describing how raw data gain context to become information, understanding to become knowledge and judgment to become wise action.