Study guide
16.3 Policies, Legal Compliance, and Ethical Principles
Certified Professional in Healthcare Information and Management Systems CPHIMS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways and Qualifying Experience 1.3 Scoring, Retakes, and Recertification 1.4 Domain-Weighted Study Strategy
2 Healthcare Organizations and Relationships
2.1 Hospitals, Clinics, Ambulatory, and Community Organizations 2.2 Payers, Regulators, Research, and Academic Organizations 2.3 Interrelationships, HIE, and Continuity of Care 2.4 HIT Professional Roles and Organizational Structures
3 Policy, Accreditation, and Care Trends
3.1 Privacy and Security Law: HIPAA and HITECH 3.2 Interoperability Policy and Information Blocking 3.3 Accreditation, Patient Rights, and Environments of Care 3.4 Telehealth, Portals, Wearables, and Population Health
4 Healthcare Applications
4.1 Clinical Applications 4.2 Administrative and Financial Applications 4.3 Consumer-Facing Applications 4.4 Business Intelligence Applications
5 Technology Infrastructure
5.1 Networks and Communications 5.2 Data Integration Architectures 5.3 Infrastructure Privacy and Security 5.4 Cloud, Devices, and Identity Infrastructure
6 Clinical Language, Terminologies, and Metrics
6.1 Clinical Vocabulary 6.2 Healthcare IT Vocabulary 6.3 Clinical Terminologies: SNOMED CT, LOINC, RxNorm, and ICD 6.4 Clinical Metrics and Operational Measures
7 Clinical Effectiveness and Workflows
7.1 System Functionality for Clinical Effectiveness 7.2 Workflows, Order Sets, and Pathways 7.3 Safety, Quality, and Clinical Informatics Design
8 Informatics Analytics
8.1 Analytics Tools, Reports, Tables, and Graphs 8.2 Interpreting Clinical and Operational Outcomes 8.3 Predictive Models in Care and Operations
9 Clinical Content and Decision Support
9.1 Clinical Content Lifecycle 9.2 Clinical Decision Support Types and Design 9.3 CDS Governance, Alert Management, and Knowledge Maintenance
10 Analysis, SDLC, and Improvement Methods
10.1 Systems Development Life Cycle 10.2 Project Management: Needs, Gap, and Requirements 10.3 Process Improvement: DMAIC and PDCA 10.4 Process Maps, Flow Diagrams, and Gap Analysis
11 Analysis: Solutions and the Business Case
11.1 Disparate Data Sets and Alternate Solutions 11.2 Strategic Alignment and Cost-Benefit Analysis 11.3 Proposals, RFPs, RFIs, SLAs, SOWs, and NDAs
12 Systems Design
12.1 Interoperability of Software, Hardware, Networks, and Devices 12.2 Design Compliance and Incorporating Industry Trends 12.3 Business Continuity and Disaster Recovery Design 12.4 Emerging Technologies and Data Governance
13 Selection, Implementation, Support, and Maintenance
13.1 Solution Selection Activities 13.2 Technical Change Management, Training, and Support 13.3 Implementation: Scope, Schedule, Budget, and Quality 13.4 Maintenance, Operations, and Problem-Trend Analysis
14 Testing, Evaluation, Privacy, and Security
14.1 Testing Methodology and Internal Controls 14.2 Validation and Benefits Realization 14.3 Privacy and Security Policies, Access, and Safeguards 14.4 Vulnerabilities, Roles, Data Controls, and Ongoing Validation
15 Strategy and IT Planning
15.1 Contributing to Organizational Strategic Planning 15.2 Assessing the Organizational Environment 15.3 Forecasting Technical and Information Needs 15.4 IT Strategic Plans and Departmental Objectives
16 Performance, Policy, Ethics, and Analytics
16.1 Evaluating Performance Against SLAs and Indicators 16.2 User Satisfaction and Service Effectiveness 16.3 Policies, Legal Compliance, and Ethical Principles 16.4 Comparative Analytics and Presenting Recommendations
17 Communication, Stakeholders, and Change
17.1 Promoting Stakeholder Understanding of IT Opportunities and Constraints 17.2 Business Communications and Consultative Technology Services 17.3 Facilitating Groups, Consensus, and Conflict Resolution 17.4 Organizational Change Management and Stakeholder Relationships
18 People, Projects, Vendors, and Finance
18.1 HIT Roles, Job Descriptions, and Staff Competency 18.2 Educational Strategies and Maintaining IT Competencies 18.3 Managing Projects and Portfolios 18.4 Vendor Contracts, Budgets, and Risk Management
16.3 Policies, Legal Compliance, and Ethical Principles
Key Takeaways Explain This Topic AI
Task A.8 is develop policies and procedures for information and systems management: owners, versions, training, and audit—not a poster or a slide deck.
A policy states the rule and authority; a procedure states the steps. One without the other is either unenforceable or unauthorized.
Task A.9 is comply with legal and regulatory standards. Do not invent a workaround that “the project needs.” Chapter 3 stated major laws; here you stop the noncompliant design.
Task A.10 is understand and comply with the organization’s ethical business principles: conflicts of interest, vendor gifts, and dual loyalty. Disclose and recuse; do not self-clear a steak.
CPHIMS recertification requires 45 CE hours in three years, including 2 hours of ethics or conflict-of-interest content. HIMSS does not publish a CPHIMS-official gift-dollar table.
Last updated: August 2026
16.3 Policies, Legal Compliance, and Ethical Principles
Quick Answer: Task A.8 is develop policies and procedures for information and systems management. Task A.9 is comply with legal and regulatory standards. Task A.10 is understand and comply with the organization’s ethical business principles —conflicts of interest, vendor gifts, and dual loyalty. A steak does not recuse you.
These three tasks are how Domain 4 keeps power from becoming improvisation. Chapter 3 covered HIPAA, HITECH, interoperability policy, and accreditation as environment. Chapter 14 turned privacy and security into access and safeguards (Domain 3 E tasks). Here the management verbs are write the local rule , obey the external rule , and stay unbought . Management and Leadership remains 25% of the 100-scored-item, two-hour form.
Use free CPHIMS practice questions after you can tell policy from procedure and a disclosure from a self-clearance. Health-information legal practice goes deeper on RHIA . CPHIMS still expects you to stop a go-live that would information-block or to walk out of a vendor-funded scoring meeting.
Recertification context you should not invent: the cycle is three years , 45 CE hours , including 2 hours of ethics or conflict-of-interest content. HIMSS does not publish a CPHIMS pass rate and does not publish a CPHIMS-official gift-dollar schedule. Use the organization’s COI and gift policy plus applicable law.
A.8 Policy versus procedure, and why both exist
Artifact Job Failure mode
Policy States the rule, scope, authority, and consequences A poster with no owner, no review date, and no sanction
Procedure States who does what, in what order, with what record Tribal knowledge, or a wiki page nobody can find at 02:00
Standard / guideline Required specification, or recommended practice Treating a vendor white paper as policy
A.8 is information and systems management : access and joiner-mover-leaver, change control, backup and restore, data retention and legal hold, acceptable use, vendor and cloud use, AI or decision-support content control, downtime, and who may grant elevated privilege. Privacy-and-security policy work in chapter 14 still applies; do not pretend A.8 is only passwords. Do not pretend it is only privacy either. A change-control policy with no procedure is a sermon. A restore runbook with no policy is an unauthorized habit.
Lifecycle the exam will reward:
Trigger: law, accreditation, incident, audit, new system, or a gap you can show.
Draft with operations, privacy, security, compliance, and the people who will do the steps.
Approve through the governed body—not a hallway “looks good.”
Version, owner, effective date, review date.
Communicate and train the people in scope. A PDF on a share is not implementation.
Audit for actual use. Retire or revise when the system or the law moved.
If staff must break the procedure to finish a shift, the procedure is wrong or the staffing is wrong. Do not “fix” that with a silent exception list only three analysts know.
A.9 Comply—do not freelance the statute
A.9 is a compliance task, not a legislative drafting task. You are not asked to recite penalty tables (those move). You are asked to stop, redesign, or escalate when a plan would violate a standard that applies:
- Privacy and security of PHI (HIPAA/HITECH and organizational policy)
- Interoperability and information-blocking rules (chapter 3)
- Retention, legal hold, and discoverability
Conditions of participation, payer contracts, and accreditation patient-rights or environment-of-care requirements that touch systems
Fraud-and-abuse risk when vendor funds, physician arrangements, or referral data are in the design
FDA or other device rules when software functions as a medical device—know when to call the specialist, not when to guess a classification on a stem
Compliance behaviors that survive stems:
Name the applicable rule. A state privacy law, a 42 CFR Part 2 constraint, or a research IRB is not optional because the EHR “can” do the extract.
Do not innovate around a prohibition. “The board wants the portal dark until we are ready” is still an information-blocking problem if the rule applies.
BAA before PHI , as chapter 11 already taught. An NDA is not compliance.
Escalate early. A.9 is failed when the CPHIMS professional waits until after go-live to mention the legal issue.
A.8 writes the local operationalization. A.9 is why you cannot waive it for a favorite project.
A.10 Ethical business principles: conflicts, gifts, dual loyalty
The handbook language is understand and comply with the organization’s ethical business principles . Typical content—and the examples the plan expects you to handle—includes:
Conflicts of interest. You (or a household member) have a financial, employment, equity, or decision interest that a reasonable person would think could bias a systems decision. Owning vendor stock while scoring that vendor’s RFP is a conflict. Moonlighting for the implementer you are overseeing is a conflict. The remedy is disclose to the governed channel and recuse from the decision, not a private promise to “be objective.”
Vendor gifts and entertainment. Meals, tickets, conference travel, devices, “advisory” honoraria, and family junkets are influence unless the organization’s policy and law clearly allow a narrow courtesy and you document it. “Everyone in HIT does dinners” is not a principle. If the gift would look ugly on the evening news beside an award decision, do not take it. When in doubt, decline or route through compliance—do not self-clear because the steak was “educational.”
Dual loyalty. You owe the employer, patients, and the public a duty, and someone else is paying for a slice of your judgment. Classic HIT forms:
- Sitting on a vendor customer board while writing the RFP those products will answer
- Employed by the health system and incentivized (bonus, equity, future job) by a supplier
Clinician-informaticist promoting a tool they invented or licensed to the same organization without a managed conflict process
Consultant retained by both the buyer and the seller on the same selection
Dual loyalty is not solved by working longer hours. It is solved by transparency, recusal, and sometimes by refusing the second hat.
Ethics is also how you treat data and people: do not spy in the EHR “because I can,” do not trade patient stories for a demo, do not bury an adverse finding to save a vendor relationship. Those are A.10 failures even when no gift changed hands.
Distinctions the exam will punish
Policy versus procedure versus a slide.
A.8 write local rules versus A.9 comply with external standards versus chapter 14 implement privacy/security controls.
Disclose and recuse versus “I can be fair.”
Organizational COI/gift policy versus a made-up HIMSS dollar cap.
Relationship management (chapter 18 vendors) versus bought influence.
Loading diagram... A.8 write the rule, A.9 obey the law, A.10 refuse the conflict
Study heuristic: A.8–A.10 failures that look like getting work done (relative emphasis, not official weights)
Scenarios and exam traps
Scenario. Operations wants a “flexible” downtime practice “until we write policy later.” A.8 says write the policy and the procedure before the next outage trains you in public. A checklist on one analyst’s laptop is not an information-systems policy. Approve it, train the house supervisor, and audit the next event.
Scenario. A product owner asks to keep electronic discharge summaries from leaving the organization until the portal “looks better,” even though the records are complete and a request is on the table. That is an A.9 problem (information-blocking / access rules from chapter 3), not a branding preference. Redesign the portal later; do not withhold the designated record set to spare embarrassment.
Scenario. A vendor offers two conference flights, a dinner, and a “customer advisory” stipend the week your committee scores its RFP. Disclose to compliance, recuse from scoring, and decline anything the gift policy does not clearly allow. Staying on the committee because you “know the product best” is the conflict. Dual loyalty is the stipend plus the score.
Scenario. You hold equity in a documentation vendor. Your spouse just joined that firm. You are the internal chair for an ambient-scribe selection. File the COI and get off the chair. Objectivity speeches are not a control. If the organization still wants your technical facts, give them as a recused witness, not as a voter.
Scenario. Recertification paperwork is due. You have plenty of informatics CE and zero ethics hours. The requirement is 45 hours in three years including 2 ethics/COI hours . Technical conferences do not silently satisfy A.10’s professional duty or the renewal rule.
Watch these traps:
Calling a slide deck or a vendor SOP “the policy.”
Treating A.8 as only privacy, or treating A.9 as a reason to memorize stale civil-money-penalty tables.
Waiving a legal standard because the project is late or the board is excited.
Self-clearing gifts, meals, or honoraria as education.
Keeping a second hat (vendor board, equity, family employment) off the COI process while you award work.
Inventing a HIMSS-official CPHIMS gift-dollar limit or a published exam pass rate.
If you can produce a versioned policy-procedure pair, stop a noncompliant design, and recuse from a conflict you cannot neutralize, you are doing A.8–A.10 at professional level. Drill those stems at /practice/cphims .