Study guide

5.2 Data Integration Architectures

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

5.2 Data Integration Architectures

Key Takeaways Explain This Topic AI

Interfaces are usually asynchronous event messages; APIs, including FHIR REST, are typically request/response resources with a different authorization model.

HL7 v2 remains the high-volume workhorse for ADT, orders, and results; FHIR does not replace every v2 feed.

CDA and CCD are point-in-time clinical documents for transitions and summaries, not live subscriptions.

Interface engines provide fan-out, transformation, queueing, replay, and monitoring; unmanaged point-to-point does not scale.

MPI and EMPI quality is independent of green interface queues—wrong identifiers file to the wrong chart.

Last updated: August 2026

5.2 Data Integration Architectures

Quick Answer: Domain I B.2 treats integration as the hospital’s circulatory system. Know when a legacy HL7 v2 interface is the right tool, when a CDA document or FHIR API is, and why an interface engine plus MPI/EMPI is not optional plumbing.

Why integration is an infrastructure competency

Applications in Chapter 4 only create value if data moves: ADT to the lab, results back to the EHR, claims to the payer, a CCD to the next hospital, a FHIR query from a patient app. CPHIMS items punish people who treat “we bought FHIR” as a rip-and-replace of every feed. Task B.2 asks you to match the pattern to the job , keep identity straight, and know what the engine is for.

This is the same interoperability policy story as Chapter 3 (Cures Act, information blocking) viewed from the pipe . Quality programs on /study-guides/cphq and HIM on /study-guides/rhia consume what these feeds produce. Practice mixed stems at /practice/cphims .

Interfaces versus APIs

An interface in healthcare usually means a message-oriented, often asynchronous feed : a sending system emits a defined event (ADT^A04, ORU^R01), an engine transforms and routes it, the receiver files it. The unit of work is a message . Delivery is store-and-forward. The sender does not wait for a clinical decision.

An API (application programming interface), including FHIR RESTful APIs , is typically request/response : a client asks for Patient/123 or posts a ServiceRequest , the server answers now. The unit of work is a resource or transaction. Authorization is often OAuth 2.0 / SMART on FHIR rather than a static VPN plus a sending-facility ID.

Pattern Unit Timing Typical use Weakness if misapplied

HL7 v2 interface Pipe-delimited message Event-driven, async ADT, orders, results, charges, scheduling Hard to query; brittle Z-segments; version drift

CDA / CCD document XML clinical document Encounter or transition Summaries, referrals, HIE payloads Not a live query; can be huge and stale

FHIR API Resources plus REST, subscriptions, bulk export Query, write-back, some events Apps, patient access, modern HIE, bulk extract Does not magically replace high-volume v2 lab or ADT

X12 / EDI Transaction set Batch or real-time 837 claims, 270/271 eligibility, 835 remits Wrong tool for clinical results

File / batch Flat file, CSV, CCD zip Scheduled Registries, warehouse, public health Latency; identity errors compound

Exam trap: FHIR does not replace every HL7 v2 feed. A 2,000-message-per-hour lab ORU stream is still a v2 job in most hospitals. FHIR is the right answer for app platforms, patient-access APIs, and many new HIE use cases. It is the wrong answer when the stem describes a mature ADT or results interface that already works and no query requirement exists. Saying “FHIR is newer, so retire v2 next quarter” is a project-risk answer, not an architecture answer.

HL7 v2, CDA, and FHIR — what each is for

HL7 Version 2 is the workhorse of inpatient integration. Segments (MSH, PID, PV1, ORC, OBR, OBX) carry events. Common message types you should recognize by purpose, not by field number:

ADT — admit, discharge, transfer, registration, merge. This is how ancillary systems learn who is in which bed.

ORM / OML — orders (lab, radiology, diet, depending on flavor).

ORU — observational results (labs, some vitals).

SIU — scheduling.

DFT / BAR — charges and account events.

MDM — document notifications.

v2 is event-centric . If no event fires, the downstream system stays stale. Custom Z-segments create local dialects that the next vendor cannot read. CPHIMS does not ask you to parse a field; it asks whether ADT is the right feed to update the pharmacy census, and whether a missing transfer message is why the blood bank still thinks the patient is on 4-West.

Clinical Document Architecture (CDA) and the Continuity of Care Document (CCD) are document standards. They package a clinical summary—problems, medications, allergies, results—as an XML document, often for transitions, referrals, or HIE. CDA is a snapshot, not a subscription. Sending a CCD does not keep the receiving EHR current after the next medication change. A 90-page CCD that no receiving clinician can find the potassium in is a usability failure even if the interface “succeeded.”

FHIR (Fast Healthcare Interoperability Resources) models healthcare as resources (Patient, Encounter, Observation, MedicationRequest, AllergyIntolerance) with standard REST operations, search, and—in later versions—subscriptions and bulk data ( $export ). US Core profiles constrain those resources for U.S. regulation. SMART on FHIR is how apps launch with scoped OAuth tokens so a third-party diabetes app does not receive the entire chart.

Use FHIR when the need is query, granular write-back, patient-facing apps, or standardized bulk extract . Use v2 when the need is high-volume, event-driven ancillary integration . Use CDA when the need is a human-and-machine readable summary at a point in time . A mature health system runs all three . That is not indecision; it is matching payload to purpose.

Interface engines and integration patterns

An interface engine (integration engine) is the broker: it receives, validates, transforms, filters, routes, queues, and logs messages among many systems. It is not “the interface.” Each connection is a channel with an acknowledgment contract (accept ACK versus application ACK). Green channels mean transport is alive; they do not mean the clinical content is correct.

Why the engine exists:

Fan-out — one ADT feed becomes twenty (lab, radiology, dietary, RTLS, patient portal).

Transformation — code-system mapping, field moves, Z-segment isolation.

Queueing and replay — the lab can be down without losing results.

Monitoring — aged queues are a patient-safety indicator, not an IT curiosity.

Common patterns:

Point-to-point — A talks only to B. Fine for a single ancillary; unmanageable at hospital scale.

Hub-and-spoke (engine-centric) — the default enterprise pattern.

Publish/subscribe — engine or event bus fans events to interested systems.

API gateway — fronts FHIR and other APIs with authorization, throttling, and audit.

ETL / ELT — scheduled extract into a warehouse or lake; not a substitute for real-time ADT.

Do not dual-write without a source of truth. Two systems both “owning” allergies is how you get conflicting lists. Pick a system of record and propagate. When a new FHIR app writes an allergy the EHR does not store, you have created a second chart.

MPI and EMPI: identity is the integration constraint

A Master Patient Index (MPI) is the organization’s authority for “is this the same person?” An Enterprise MPI (EMPI) extends that authority across facilities, affiliates, or an HIE.

Without a working MPI:

ADT creates duplicate charts.

Results file to the wrong encounter.

FHIR Patient search returns two IDs for one human.

Quality measures double-count.

Matching uses deterministic keys (MRN inside a facility) plus probabilistic traits (name, date of birth, sex, address, last four SSN, mobile). Merges and unmerges are clinical events: a bad merge mixes two patients’ allergies. CPHIMS items often hide an identity problem inside an “interface is down” story. If the engine is green but the lab is filing under a new MRN, the failure is MPI , not TCP.

HIE and multi-hospital systems need an EMPI or a carefully governed crosswalk. Local MRNs remain; the EMPI issues a surviving enterprise ID and links source identifiers. HIM owns many of the merge procedures; infrastructure owns the feeds and the match thresholds. Both must be at the table.

Scenarios and traps

Trap: “FHIR replaces HL7.” It does not replace high-volume v2 ADT, orders, or results in most enterprises.

Trap: “CDA is real-time interoperability.” It is a document snapshot.

Trap: “The engine is optional if we use APIs.” You still need routing, authorization, transformation, and replay—often an API gateway plus an engine.

Trap: “Interfaces fix identity.” Interfaces move whatever identifier they are given. MPI/EMPI quality is a separate control.

Trap: “More messages mean better care.” Unfiltered ADT floods can crash a downstream pharmacy just as a missing ORU can hide a critical potassium.

When a stem says a new patient-access app must read medications and allergies with the patient’s authorization, think FHIR plus SMART , not a new v2 feed. When a stem says the blood bank never saw the transfer, think ADT plus engine queue , not a missing FHIR server.

Loading diagram... Match the integration payload to the job; the engine and MPI sit in the middle

Study heuristic: relative fit of each payload for a high-volume inpatient lab result (illustrative)