Study guide
12.2 Design Compliance and Incorporating Industry Trends
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
12.2 Design Compliance and Incorporating Industry Trends
Key Takeaways Explain This Topic AI
Tasks B.2 and B.3 share one operating process: scan, triage, impact, update the design standard, fund the backlog, and keep evidence. A yearly offsite is not a process.
Legal-must, safety-must, and certification-must items are not optional because the project is late. Optional trends can be parked with a named owner and a revisit date; silence is not a park.
ONC certification is a product-capability constraint. Local configuration that breaks a certified API, e-prescribing, or quality-reporting criterion is a design defect, not a clever enhancement.
Accessibility (Section 508, WCAG, ADA risk) applies to portals, kiosks, training media, and custom skins—not only to the vendor’s certified core.
Safety standards belong in the design file: human factors, alert philosophy, SaMD/IEC risk thinking when software is a device, and IEC 80001-style medical devices on IT networks.
Last updated: August 2026
12.2 Design Compliance and Incorporating Industry Trends
Quick Answer: Design has two clocks. Compliance is the floor—law, certification, accessibility, safety. Trends are the horizon—new standards, infrastructure patterns, care models. Build one intake process so neither clock is “whoever attended a conference.”
Tasks B.2 and B.3 are paired on purpose. Compliance without a trend process produces a frozen, eventually non-certifiable EHR. Trend-chasing without a compliance gate produces a shiny pilot that violates Section 508, breaks an ONC-certified API, or ships an unsafe workflow. CPHIMS scores the operating system that keeps both clocks honest after the RFP is signed.
Chapter 3 covered the substance of HIPAA, HITECH, Cures, and accreditation. This section is how those rules—and the next ones—get into the design , not only into a policy binder. Use CPHIMS practice questions for “what does the architecture board do first” stems. CPHQ overlaps on safety and accreditation evidence; CPHIMS wants the design-control move.
Why this is a process, not a memo
Healthcare design constraints change on different calendars:
Statute and rule (HIPAA, Cures, information blocking, state privacy)
Certification editions and CMS Promoting Interoperability measures (not “Meaningful Use” as the current program name)
- Safety and quality (Joint Commission, CMS Conditions of Participation, FDA when software is a device)
- Accessibility (Section 508, WCAG, ADA litigation risk)
Infrastructure and industry patterns (zero trust, cloud regions, FHIR bulk and SMART apps, immutable backup, ambient documentation)
If the only “process” is a yearly strategy offsite, you will miss a mid-year ONC or CMS change and you will overfit to a vendor keynote. Task B.3 is not “list five buzzwords.” It is “show the path from signal to design standard.”
The intake process CPHIMS wants named
Architecture, informatics, and compliance share a lightweight, dated pipeline:
Stage Owner Input Output
Scan Informatics + IS architecture + compliance Federal Register, ONC, CMS, FDA, OCR, Joint Commission, IHE, NIST, vendor release notes Horizon log with source and date
Triage Design authority / architecture review board Horizon log Category: legal-must, safety-must, certification-must, optional trend, park
Impact Assigned analyst + clinical owner Affected systems, workflows, data, contracts Impact note: who, when, cost, risk if ignored
Design standard Enterprise architect Approved changes Updated pattern library, reference architecture, RFP language
- Backlog PMO / application owners Impact notes Funded work or explicit accept-risk
- Verify QA + compliance Design and build Evidence: certification letter, accessibility report, safety risk file
Rules that show up on items:
Legal-must is not optional because the project is late or the vendor cannot meet it this quarter. Document the gap and the residual risk; do not pretend the criterion vanished.
Trend does not skip privacy, safety, or accessibility review. A FHIR bulk export still needs a BAA, minimum necessary, and an owner.
Park is a decision with a named owner and a revisit date. Silence is not a park.
Record the source . “I heard FHIR is required” is not an impact note.
Certification as a design constraint
ONC Health IT Certification is a product-capability program. It is not a license to practice medicine and not proof that local order sets are safe (Chapter 9). Design implications:
If you need Promoting Interoperability credit or information-blocking “certified API” behavior, the product must maintain the relevant certification criteria after you configure it.
Customization that breaks patient-access APIs, e-prescribing, or quality reporting is a design defect, not a clever local enhancement.
Certification does not certify your MPI, your device VLAN, or your downtime plan.
USCDI data classes constrain what certified exchange is expected to support. Local “we do not store that” may be a compliance problem, not a preference.
Ask in every design review: which criteria must remain true after we configure this, and where is the evidence?
SOC 2, HITRUST, and NIST CSF can support a security story. None of them replace HIPAA, and none of them are ONC certification.
Accessibility is in the design, not the theme deck
Accessible design is a requirement:
Section 508 for federal and many state or covered systems
WCAG (perceivable, operable, understandable, robust) as the practical success criteria; many programs target 2.1 AA
Keyboard access, contrast, screen-reader names, captions on training and telehealth
Clinical reality: a nurse in gloves, a physician with low vision, a patient using a portal with a screen reader, a kiosk in a noisy lobby
Your custom portal skin, PDFs, wayfinding kiosks, and e-learning are in scope even when the EHR vendor’s core is certified. “Clinicians are too busy for accessibility” is not a design decision. Neither is “the vendor is certified, so our overlay is fine.”
Safety standards belong in the design file
HIT safety is designed, not inspected at go-live:
- Human factors: wrong-patient, look-alike orders, interruptive versus passive alerts (Chapter 7)
- Alarm and alert philosophy written before the first BPA
When software is a medical device or SaMD , think in intended use , risk file, and change control (IEC 62304 / ISO 14971 style)—FDA oversight does not replace HIPAA
IEC 80001 -style thinking for medical devices on IT networks: who owns risk when the pump rides your WLAN
Joint Commission medication-management and environment-of-care expectations that depend on BCMA, pump libraries, and downtime
Security-as-safety: ransomware is a clinical downtime event (Section 12.3)
A feature that cannot be used safely in a crash-cart moment is not “done,” even if it compiles and the sprint burned down.
Infrastructure and technical trends
Run trends through the same gate:
- Cloud regions and shared responsibility still sit under HIPAA (Chapter 5)
- Zero-trust and identity-first access often migrate from trend to standard
- FHIR R4/R5, SMART, bulk data, and subscriptions—match to a use case, do not rip working v2
Immutable backups and identity recovery are now baseline design after years of ransomware, not a conference extra
Ambient scribes and other AI tools are evaluated in Section 12.4; they still need a BAA, retention, and an accuracy owner
Do not redesign the enterprise around a single demo. Do not ignore a NIST or ONC shift because this quarter’s vendor cannot meet it—write the gap into the standard and the risk register.
Design-review questions
Which law, certification criterion, accessibility standard, or safety control does this design claim to meet?
What evidence will we keep, and who retrieves it at survey?
What trend did we consider and park—and who owns the revisit date?
If this configuration breaks a certified API or a 508 path, who is authorized to accept that risk? (Usually: no one.)
Loading diagram... Compliance and trends enter the design through one dated pipeline
Scenarios and exam traps
Scenario. A service line wants a custom portal skin that hides the certified patient-access API “until we are ready.” That is a certification and information-blocking design defect, not a marketing choice. Keep the certified path; park the skin until it passes accessibility and API tests.
Scenario. An architect hears at a conference that “everyone is on FHIR subscriptions now” and opens a project to retire v2 results. Run it through triage. It is an optional trend until an impact note shows a use case, a semantic map, and a cutover that does not break Promoting Interoperability reporting.
Scenario. A pump wireless redesign is treated as a network ticket. Safety and IEC 80001-style ownership never enter the file. Send it back: device-on-network risk is a design-compliance item, not only a VLAN change.
Scenario. Surveyors ask for WCAG evidence on the patient kiosk the marketing team launched. The EHR vendor’s certification letter does not cover the kiosk. Accessibility evidence is local.
Watch these traps:
Treating ONC certification as local clinical safety.
Skipping 508/WCAG because “only clinicians use it” or “the vendor is certified.”
Absorbing trends by hallway conversation instead of a dated impact note.
Parking a legal-must as if it were a trend.
Using SOC 2 or HITRUST as a substitute for HIPAA or ONC criteria.
Calling a yearly offsite a B.3 process.
B.2 and B.3 are how the architecture stays legal and current. Section 12.3 then asks whether that same architecture can survive weather and ransomware.