Impact of the policy or regulation you selected
One page, and the last requirement is the one that stops it being a summary: what your organisation actually does, or will do, about the regulation you chose.
Editorial process
Last reviewed · August 25, 2026
The local procedures requirement is what makes it a fact sheet
A fact sheet has an audience inside the organisation, and the last requirement is what separates it from an essay: name the organisational policies and procedures that address the regulation, and be specific. That is the part a colleague reads it for, since anyone can look up what a regulation says and nobody outside the compliance office knows what the hospital does about it. Choose a regulation where you can answer that, which usually means a current one with visible operational consequences, information blocking and patient access to notes, interoperability and exchange requirements, or telehealth documentation and licensure rules. A regulation you can only summarise makes the last quarter of the sheet generic. Pick something with visible operational consequences, because a regulation you can only summarise leaves the last quarter of the sheet generic and that quarter is the reason the document exists. Current candidates include information blocking and patient access to notes, exchange requirements, and telehealth documentation rules.
The three impact requirements should also be kept distinct rather than merged into general consequences. System implementation is about the build: fields, interfaces, access controls, audit logging and the vendor's release timetable. Clinical care and patient-provider interaction is about what changes in the room, which for immediate release of results means a patient may read a result before the clinician has, and that changes how results are explained and when. Workflow is about the order and cost of steps, and it is where a regulation's real burden lands, because a requirement that adds thirty seconds to an action performed forty times a shift is twenty minutes of clinical time. One page also means ruthless compression, so use headings, short statements and a small number of concrete examples rather than continuous prose. Compression is a real constraint here and it favours headings and short statements over continuous prose.
Likely learning objectives
- Choose a regulation whose local procedures you can actually describe.
- Keep system, clinical and workflow impacts distinct.
- Quantify workflow burden per repetition rather than per action.
- Write for a colleague inside the organisation rather than for a marker.
Assignment instructions
Read the full question
Review every instruction before using the planning guidance that follows.
Create a 1-page fact sheet that your healthcare organization could hypothetically use to explain the health or nursing informatics policy/regulation you selected. Your fact sheet should address the following: Briefly and generally explain the policy or regulation you selected. Address the impact of the policy or regulation you selected on system implementation. Address the impact of the policy or regulation you selected on clinical care, patient/provider interactions, and workflow. Highlight organizational policies and procedures that are/will be in place at your healthcare organization to address the policy or regulation you selected. Be specific. This week you will complete the Week 11 Assignment, ” Policy/Regulation Fact Sheet”. For this Assignment, you will examine a recent nursing informatics-related healthcare policy and share relevant details via a fact sheet designed to inform and educate colleagues in your organization. First you want to concisely explain the policy/regulation you selected. Then you need to explain the impact of the policy/regulation on four areas: System implementation Clinical care Patient/provider interactions Workflow Finally you will identify organizational policies and procedures that are or will be in place at your healthcare organization to address the policy/regulation you selected. Below are the instructions from Module 6. class. It has come to my attention that the assignment rubrics do not specify the number and types of resources required for the following assignments: Module 1: Week 2 Assignment Module 2: Week 3 Assignment Module 5: Week 10 Assignment Module 6: Week 11 Assignment The syllabus does require you to integrate credible, outside and course specific resources to demonstrate critical thinking and lend support to your ideas in your assignments. As a guide, you should integrate 3 or more peer-reviewed sources and 2 or more course resources for these four assignments. The full statement on assignments from the syllabus is also provided below. If you have any questions, please feel free to contact me. 2. Assignments: The Assignments provide you with the opportunity to apply the skills and knowledge gained through the Learning Resources and the practicum experience. See the Assignment area of specific weeks for detailed descriptions of the assignments. In grading the required Assignments, your Instructor will be using rubrics located in the Course Information area. Note: The course Assignments will require that you completely and accurately demonstrate critical thinking via assimilation and synthesis of ideas when using credible, outside and course specific resources (i.e. video, required readings, textbook), when comparing different points of view, highlighting similarities, differences, and connections, and/or when lending support to your Assignment responses.
What the Week 11 fact sheet requires
- 01A 1-page fact sheet your healthcare organisation could hypothetically use.
- 02A brief general explanation of the selected health or nursing informatics policy or regulation.
- 03The impact of the policy or regulation on system implementation.
- 04Its impact on clinical care, patient and provider interactions, and workflow.
- 05The organisational policies and procedures that are or will be in place to address it, stated specifically.
Policy, systems, care, and local response
The regulation in brief
State what it requires and who it binds, in a few lines.
What the assessor is likely looking for
Compression without loss of accuracy.
System implementation
Cover build, interfaces, access control and audit requirements.
What the assessor is likely looking for
Technical consequences named.
Clinical care and interaction
Say what changes between a patient and a clinician.
What the assessor is likely looking for
A change in the room, not in the system.
Workflow
Identify added or removed steps and their cost per shift.
What the assessor is likely looking for
Burden quantified.
What we do about it here
Name existing and planned organisational policies and procedures.
What the assessor is likely looking for
Specificity a colleague could act on.
Where to go with questions
Give the internal contact or resource.
What the assessor is likely looking for
Usability as an internal document.
Where the informatics policy sits
Recommended databases
- HealthIT.gov
- CMS
- PubMed Central
- NCBI Bookshelf
Search sequence
- 1.Choose a current informatics regulation and read the requirement itself.
- 2.Look up the implementation guidance for the build consequences.
- 3.Find literature on its clinical and workflow effects.
- 4.Check your organisation's existing policies for the final section.
Reference shortlist
These are authoritative starting points, not a ready-made bibliography. A qualified reviewer must confirm that each source fits the assignment and supports the claim beside which it is cited.
Interoperability
Office of the National Coordinator for Health Information Technology · 2024
Interoperability policy, as a candidate regulation with operational consequences.
Promoting Interoperability Programs
Centers for Medicare & Medicaid Services · 2025
Promoting interoperability requirements, for the system implementation section.
Privacy, Security, and HIPAA
HealthIT.gov, Office of the National Coordinator · 2024
Privacy and security requirements, for access control and audit obligations.
The association between perceived electronic health record usability and professional burnout among US nurses
Journal of the American Medical Informatics Association, 28(8), 1632-1641 · 2021
EHR usability and burnout, for quantifying workflow burden.
Mind the Gap: A systematic review to identify usability and safety challenges and practices during electronic health record implementation
Applied Clinical Informatics · 2016
Usability and safety during implementation, for the clinical care impact.
Before you submit
Common mistakes
- Summarising the regulation and generalising the local response.
- Merging the three impact categories into one section.
- Choosing a regulation with no visible operational consequence.
- Writing continuous prose that will not fit one page.
- Describing burden per action rather than per shift.
Submission checklist
- Are the local policies and procedures specific?
- Are system, clinical and workflow impacts separated?
- Is at least one workflow effect quantified?
- Does it fit on one page with headings?
- Would a colleague learn something they could not look up?
Use this guide to plan and review your own work. Follow your institution's rules and read Brinevia's academic-integrity policy.
Written by
Maren Caldwell
MSN, RN, CNE
Medical-surgical nursing, pharmacology and NCLEX preparation
Maren is a registered nurse with over 15 years of clinical and educational experience in medical-surgical nursing. She writes on NCLEX preparation, patient care fundamentals, pharmacology and evidence-based practice.

Reviewed by
Dr. Tessa Redmond
DNP, RN, CNE
Evidence-based practice and clinical education
Tessa is a doctorally-prepared nurse educator. She reviews Brinevia content for clinical accuracy and alignment with current evidence-based guidelines.