HI570 Unit 5 Ethical Dilemma Analysis Example

Her Own Hospital's Chart: A Unit 5 Ethical Dilemma Analysis of a Nurse's Request to Hide a Psychiatric Admission From Coworkers

[Student Name]

Purdue University Global

HI570: Legal and Ethical Issues in Health Information

Unit 5 Ethical Dilemma Analysis

[Instructor Name]

[Date]

Larchmere Health, the nurse, her units and every detail are composite; the regulation and sources cited are real.

The Facts

A registered nurse who works on Larchmere Health's telemetry unit was admitted to the system's inpatient psychiatric unit after an intentional overdose and stayed four days. She was discharged to outpatient psychiatric care and a return-to-work plan with occupational health. Two days before her first shift back, she wrote to the privacy office asking that the psychiatric admission be hidden from anyone in the system who is not treating her, and in particular from staff on her own unit. Larchmere's three hospitals share one electronic record, and nurses on any unit can technically open any patient's chart, with access logged.

The Legal Floor

The Privacy Rule gives her the right to request a restriction on uses and disclosures of her information, and it allows the covered entity to decline, with one exception: when a patient pays the whole bill herself and asks that the service be kept from her insurer, the hospital must comply (45 C.F.R. § 164.522, 2024). Her admission was billed to her health plan, so the exception does not apply. If Larchmere agrees to a restriction, it is bound by it except in an emergency.

Separately, the rule already forbids coworkers from looking at her chart without a work reason. Access for curiosity is an impermissible use whether or not a restriction exists. So the law gives her two things: a right to ask, and a prohibition on snooping that the system must enforce. It does not say whether agreeing to her request is wise, and it does not say how to stop a prohibited look before it happens.

The Framework

Helen Nissenbaum's theory of contextual integrity holds that information flows carry the norms of the context in which they began (Nissenbaum, 2010). A flow is appropriate when it matches those norms, defined by the actors involved, the type of information and the principle under which it moves, such as confidentiality, need or consent. Privacy is violated not when information is shared, but when it moves in a way the original context would not support. The framework suits this case because the problem is not secrecy; the nurse expects her treating clinicians to know everything. The problem is which flows are appropriate.

Four Flows

First flow: to her treating outpatient psychiatrist. She disclosed to the inpatient team in a clinical context under norms of confidentiality and care. Her outpatient psychiatrist is part of that same context, receiving information to continue her treatment. The flow matches its norms.

Second flow: to an emergency physician at a sister hospital, should she arrive unwell. Emergency care is a context in which clinicians need recent psychiatric history to treat safely, and patients generally expect that. The flow matches.

Third flow: to a pharmacist checking interactions on a new prescription. The pharmacist needs her current medications and conditions to prevent harm, a purpose consistent with the clinical context. The flow matches.

Fourth flow: to a coworker on her own unit, curious about her absence. The coworker has no clinical role, and the information would move from a context of care into a context of employment and collegial reputation, where it could affect how she is treated, assigned or trusted. The original context never contemplated this flow. It violates contextual integrity, even though the system's technical permissions already allow it.

Three of the four flows match the norms under which she disclosed, and the one that does not is the one the system currently makes easiest.

The Asymmetry That Decides the Case

The analysis shows that a blanket restriction would be wrong. Hiding the admission from all non-treating users could also hide it from an emergency physician who has not yet established a treatment relationship, which would damage a flow she herself would want. At the same time, doing nothing would leave the fourth flow open and rely entirely on after-the-fact discipline. Because she works in the same system, the risk of a curious look is concrete, not hypothetical. Health information professionals have an ethical duty to protect confidential information from inappropriate access and to advocate for safeguards proportionate to the risk (American Health Information Management Association [AHIMA], 2019).

Decision

Larchmere should agree in part, without accepting a formal restriction that would bind emergency care.

1. Place a sensitivity flag on her record that requires any user to state a reason before opening it, with a warning that access is monitored.

2. Run a proactive audit of every access to her record for twelve months, reviewed weekly by the privacy office rather than only when a complaint is made.

3. Remove her own unit's staff from her care team list so that her chart does not appear in their worklists.

4. Tell her in writing what the system will and will not do, including that clinicians who need the information for her care will still see it.

The decision refuses a formal restriction under the rule because a restriction would bind the system even when a clinician later needs the information, while the flag and audit address the actual harm she fears.

Principles Behind the Decision

The decision honors respect for autonomy by treating her request as legitimate and responding to its purpose. It honors nonmaleficence by protecting her from the foreseeable harm of disclosure to coworkers while avoiding the harm a blanket restriction could cause in an emergency (Beauchamp & Childress, 2019). It also honors justice in a quieter way: staff who are patients in their own hospital face a risk other patients do not, and a system that employs them owes them protection matched to that risk.

Why Not Simply Refuse

Refusing outright would be lawful and administratively simple. It would also tell a nurse returning from a suicide attempt that her employer sees her request as an inconvenience, at the point when her trust in the system matters most for her recovery and her return to work. The cost of the partial yes is modest: a flag that already exists for other sensitive records, a weekly audit report and a change to one care team list.

Limits

A reason prompt and audit deter snooping but cannot prevent a determined person from looking once. The protection depends on the privacy office actually reviewing audits weekly, which takes staff time. And the case does not address her return-to-work evaluation, which belongs to occupational health under separate confidentiality rules.

References

American Health Information Management Association. (2019). AHIMA code of ethics. AHIMA.

Beauchamp, T. L., & Childress, J. F. (2019). Principles of biomedical ethics (8th ed.). Oxford University Press.

45 C.F.R. § 164.522 (2024). https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.522

Nissenbaum, H. (2010). Privacy in context: Technology, policy, and the integrity of social life. Stanford University Press.