| Course | BUSI 505 Healthcare Informatics (BUSI505) |
|---|---|
| Module/Week | 7 |
| Assignment | Discussion Board Forum 4 |
| Paper type | Discussion thread with two replies |
| Length | about 1,517 words (thread and replies). Course guide: a thread of at least 600 words and replies to 2 classmates of at least 450 words each; the thread and each reply include at least 1 biblical integration and 2 peer-reviewed source citations in addition to the textbooks |
| Format | APA 7 citations and reference list |
| Points | 60 |
| School | Liberty University Online |
| Program | MS in Healthcare Administration |
| Where it sits | Module/Week 7 in Liberty's published BUSI 505 course guide; current sections can differ |
| Updated | October 2026 |
Free sample paper for BUSI 505 Week 7
Discussion Board Forum 4: Emerging Technologies and Generative AI in Clinical Communication
BUSI 505 Healthcare Informatics, Discussion Board Forum 4
Thread by [Student Name]
The health system, its pilot and the classmates are composites; the textbooks, Scripture and the peer-reviewed sources cited are real.
After a vendor demonstration last month, our health system's leaders are preparing to turn on a feature that uses a large language model to draft replies to patients' portal messages. The draft appears in the clinician's inbox, the clinician edits it as needed and the clinician sends it. The vendor presented the tool as a way to save each physician an hour a week and reduce burnout from the growing volume of messages. Before we commit, leadership asked our informatics committee to review what the evidence actually shows and what safeguards we need. Several physicians are enthusiastic, a few are skeptical and the patient advisory council has asked whether patients will be told when software wrote part of a message they receive from their doctor.
Braunstein (2014) describes emerging technologies as promising but warns that their value depends on careful evaluation in real clinical settings, and Nelson and Staggers (2014) emphasize that new systems change workflows, roles and risks in ways designers do not always anticipate. Generative AI is a clear example: it writes fluently, which can make its errors harder to spot, and it shifts the clinician's task from writing to reviewing. Reviewing is a different skill, and research on automation in other fields shows that people tend to trust confident-sounding output more than they should, especially when they are busy.
The early evidence is encouraging but different from the vendor's pitch in important ways. Garcia et al. (2024) evaluated a five-week pilot of AI-drafted replies in primary care and gastroenterology at an academic medical center. Among 162 clinicians, drafts were used for about 20% of replies on average. Contrary to expectations, there was no measurable change in the time clinicians spent reading, writing or acting on messages. However, clinicians reported significant reductions in task load and in work exhaustion, a component of burnout. Crowley et al. (2026) studied 80 physicians, nurses, nurse practitioners and medical assistants across seven clinics and found that replies began from an AI draft about 20% of the time and that 40% of those replies were sent with little or no editing. Two thirds of survey respondents found the drafts useful, and nurses were more favorable than physicians.
Together, these studies suggest the tool may ease the burden clinicians feel more than the minutes they spend, and that a substantial share of drafts reach patients largely unchanged. That second finding raises the stakes for accuracy, tone and accountability. If a draft misstates a medication instruction and is sent unchanged, the error carries the clinician's name and the health system's credibility, and the patient has no way to know a machine wrote it.
I would recommend adopting the tool with four conditions. First, every draft must be reviewed and sent by a licensed clinician, who remains accountable for its content. Second, the informatics committee should audit a sample of sent messages each month for accuracy, tone and safety, with a clear path to report problems. Third, the system should adopt a disclosure policy so patients know when AI helped draft a message. Fourth, success should be measured by clinician burden, patient satisfaction and safety events, not only by time saved, and reviewed by the committee after six months. A message drafted by a machine still carries the clinician's name, and with it the clinician's responsibility.
Paul urged that no corrupting talk come from believers' mouths, but only what is good for building up, so that it gives grace to those who hear (English Standard Version Bible, 2001/2016, Ephesians 4:29). Whether a reply is drafted by a person or a program, the standard for what reaches a patient should be the same: accurate, kind and helpful.
Reply to Monica
Monica, you raised the question of whether patients should be told when AI helped draft a message, and whether telling them might undermine their trust. It is one of the most debated questions in health systems adopting these tools, and policies vary widely. Research suggests the answer involves a real trade-off that health systems should resolve in favor of disclosure. Your concern about trust is well placed, since patient trust is the foundation of the portal relationship, but the evidence suggests that disclosure costs very little satisfaction while concealment could cost a great deal of trust if patients discovered it later. Cavalier et al. (2025) surveyed 1,455 members of a health system's patient advisory group using messages that varied in author, disclosure and seriousness. Participants actually rated AI-drafted responses slightly higher for satisfaction, usefulness and feeling cared for, but their satisfaction dipped slightly when they were told AI was involved. Even so, more than three quarters were satisfied regardless of author or disclosure, and the authors concluded that disclosure should be maintained to respect patient autonomy. In other words, the cost of honesty was small, and patients remained broadly satisfied either way. Barrison et al. (2026) interviewed 30 portal users, stratified by age and education, and found that written disclosure statements often failed to communicate clearly, with nearly half unable to identify AI as the draft's writer, and that disclosures raised concerns about errors, authorship and depersonalization. Most participants nonetheless wanted disclosure, citing their right to know how their care is delivered. Those with the strongest concerns wanted to be told in advance, for example through a portal notice or a conversation, rather than learning about AI from a line at the bottom of a message. That preference suggests disclosure is a process, not a single sentence. Nelson and Staggers (2014) describe transparency as part of trustworthy information systems, and Braunstein (2014) emphasizes that patient engagement depends on trust in the technologies patients use. Both points suggest that a short-term gain in satisfaction from silence would be a poor trade for the long-term credibility of the portal. Paul wrote that he refused to practice deception and instead commended himself by the open statement of the truth (English Standard Version Bible, 2001/2016, 2 Corinthians 4:2), and health systems adopting AI should hold to the same openness. Would your organization test several versions of a disclosure statement with patients before adopting one? The research suggests that clear wording matters as much as the decision to disclose. A patient advisory council could review drafts, and the portal could include a short explanation page describing how AI is used, how clinicians review drafts and how patients can ask for a reply written entirely by their care team.
Reply to Gavin
Gavin, you focused on the finding that many AI drafts are sent with little editing and asked whether that means clinicians are trusting the tool too much. It is the right question to ask, because the safety of the whole approach rests on the assumption that a clinician reads and corrects every draft before it reaches a patient. It is a reasonable concern, sometimes called automation bias, in which people accept a computer's output because reviewing it carefully takes effort. The risk grows when clinicians are tired, behind on their inbox or reviewing many similar messages in a row, which describes many clinicians' afternoons. Crowley et al. (2026), studying a voluntary pilot across seven clinics, found that 40% of replies that began from an AI draft were sent with little or no editing. That could mean many drafts were good enough to send as written, or it could mean some errors slipped through; the study could not tell which, because it measured editing rather than the accuracy of what was sent. Garcia et al. (2024) found no change in time spent on messages, which suggests clinicians were still reading and adjusting drafts rather than simply clicking send, but a five-week pilot is too short to know whether vigilance would last. Attention often fades once a new tool becomes routine, which is precisely when careful auditing matters most. Braunstein (2014) cautions that clinical systems require ongoing evaluation after implementation, not only before it, and Nelson and Staggers (2014) emphasize that safety depends on designing systems that support careful human judgment rather than replace it. Several practical safeguards could reduce the risk, including requiring the clinician to make at least one deliberate confirmation before sending, flagging drafts that mention medication changes, test results or urgent symptoms for closer review and auditing a random sample of minimally edited replies each month, with results shared with the clinicians involved. Feedback from audits should go back to clinicians and to the vendor so that both people and the model improve. Leaders should also watch for drift over time, since a tool that performs well in a pilot may behave differently after vendor updates or as message content changes with the seasons, such as during respiratory virus surges. Proverbs says that truthful lips endure forever, while a lying tongue is but for a moment (English Standard Version Bible, 2001/2016, Proverbs 12:19), a reminder that accuracy in what we tell patients has lasting consequences. Would your organization consider a policy that drafts involving medications or new symptoms can never be sent without edits? Rules like that focus attention where errors would matter most, and they send a clear signal that the clinician, not the software, is responsible for what patients receive.
References
Barrison, P. D., Platt, J., Ackerman, M. S., Friedman, C. P., & Vinson, A. H. (2026). Patient perceptions and preferences for the disclosure of artificial intelligence generated draft replies to electronic messages: A qualitative study. International Journal of Medical Informatics, 217, 106507. https://doi.org/10.1016/j.ijmedinf.2026.106507
Braunstein, M. L. (2014). Contemporary health informatics. AHIMA Press.
Cavalier, J. S., Goldstein, B. A., Ravitsky, V., Bélisle-Pipon, J.-C., Bedoya, A., Maddocks, J., Klotman, S., Roman, M., Sperling, J., Xu, C., Poon, E. G., & Chowdhury, A. (2025). Ethics in patient preferences for artificial intelligence-drafted responses to electronic messages. JAMA Network Open, 8(3), e250449. https://doi.org/10.1001/jamanetworkopen.2025.0449
Crowley, A. P., Hanish, A., Lubken, J., Becker, M., Rosen, C., Moon, J., & Regli, S. H. (2026). Usage of and satisfaction with artificial intelligence-generated draft replies to patient portal messages. Applied Clinical Informatics, 17(3), 510-517. https://doi.org/10.1055/a-2893-7363
English Standard Version Bible. (2016). Crossway. (Original work published 2001)
Garcia, P., Ma, S. P., Shah, S., Smith, M., Jeong, Y., Devon-Sand, A., Tai-Seale, M., Takazawa, K., Clutter, D., Vogt, K., Lugtu, C., Rojo, M., Lin, S., Shanafelt, T., Pfeffer, M. A., & Sharp, C. (2024). Artificial intelligence-generated draft replies to patient inbox messages. JAMA Network Open, 7(3), e243201. https://doi.org/10.1001/jamanetworkopen.2024.3201
Nelson, R., & Staggers, N. (2014). Health informatics: An interprofessional approach. Elsevier Mosby.
What the BUSI 505 Week 7 instructions ask
The fourth regular forum of BUSI 505 arrives in the seventh module, drawing on Braunstein's chapter 9, Nelson and Staggers's chapter 30 and one presentation. The group submits its Research Project Final Document, the revised 20 to 25 page paper, the same week, along with Peer Evaluation 4 and Quiz 7. The last regular forum keeps the same minimums: more than 600 words for the thread, more than 450 for each response and, in each post, a verse and two scholarly articles cited in APA beyond the textbooks. Emerging technology topics especially reward careful use of the newest evidence, since claims often outrun data and early studies are small.
How this BUSI 505 Week 7 example is built
The sample thread describes a health system preparing to turn on AI-drafted replies to patient messages after a vendor demonstration. It summarizes two early evaluations, one measuring time, burden and burnout and one measuring how often clinicians used and edited drafts, and it explains what those findings mean for expected benefits. Using the course chapters on emerging technologies, it argues that generative tools should be governed like other clinical systems, with validation, monitoring and accountability. The recommendation includes human review requirements, auditing of sent messages and a disclosure policy. Paul's instruction that speech should give grace to hearers frames the purpose. Replies address patient disclosure preferences and the risk of sending drafts without editing. The replies end with policies a health system could adopt before launch.
BUSI 505 Week 7 grading rubric: where the points go
Faculty grading the final regular forum look for informed analysis of an emerging technology, using the course's emerging technology chapters and current evidence, and for recommendations that address benefits, risks and governance together. Each response brings its own sources and Scripture, matched to the classmate's point. Strong posts distinguish what has been measured from what vendors promise and recognize ethical issues such as transparency, accountability and patient trust, and they state conclusions with caution when early studies are short and small. With the final group paper due the same week, clear organization and concise argument are especially valuable to readers and graders alike.
BUSI 505 Week 7 help: mistakes that cost points
Choose an emerging technology you have seen introduced or proposed, such as generative AI, ambient documentation or virtual nursing, and identify what it promises. Use chapter 9 of Braunstein and chapter 30 of Nelson and Staggers to place it in the context of informatics trends. Find two recent peer-reviewed evaluations and compare their findings with the promises. Recommend governance steps, including how errors would be caught, who owns the tool and how patients would be informed. Connect honest, gracious communication to Scripture. Finish the forum early so the final group document gets its full share of attention, and note the publication dates of your sources, since this field changes quickly.
Related BUSI 505 sample papers
Other BUSI 505 weeks
- BUSI 505 Week 1: Discussion Board Forum 1
- BUSI 505 Week 2: Case Study Forum 1
- BUSI 505 Week 3: Case Study Forum 2
- BUSI 505 Week 4: Discussion Board Forum 2
- BUSI 505 Week 5: Case Study Forum 3
- BUSI 505 Week 6: Discussion Board Forum 3
- BUSI 505 Week 8: Case Study Forum 4
BUSI 505 Week 7 questions, answered
What is BUSI 505 Discussion Board Forum 4?
The last standard forum of the course, 60 points in Module/Week 7, which weighs an emerging technology's evidence and governance while groups submit their final papers.
Where can I find a free BUSI 505 Week 7 sample paper?
See this page for the complete BUSI 505 Week 7 thread on generative AI drafting replies to patient messages, with two detailed replies and full references.
Do AI-drafted replies to patient messages save clinicians time?
An academic medical center pilot found no measurable time savings, though clinicians reported meaningful reductions in task load and burnout after using AI drafts for about 20% of replies.
Do patients want to know when AI drafted a message?
A survey of 1,455 patient advisors found slightly lower satisfaction when AI use was disclosed, but researchers concluded disclosure should continue to protect patient autonomy.
What else is due in BUSI 505 Module/Week 7?
The group's final 20 to 25 page document, the fourth peer evaluation and Quiz 7 all land in the same week as this last regular forum.
Use it as a model, or ask for your own
This paper is an original model written by our desk for study. It is not a submitted student paper and not an official Liberty University document. Read it for structure and reasoning, then write your own to the instructions in your Canvas course. If you want a version built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Ask for a custom BUSI 505 Week 7 sample · All BUSI 505 weeks · All courses