2.3 Interrelationships, HIE, and Continuity of Care
Key Takeaways
- Continuity of care is longitudinal integrity across settings; the highest-risk failures sit at transitions and open-loop referrals.
- An EHR is an organization’s system of record for care delivery; HIE is authorized electronic movement of information across organizations or networks.
- Directed exchange pushes a packet to a known recipient; query-based exchange pulls available records when no directed packet was sent.
- IDNs and ACOs are interrelationship models: ownership or tight affiliation versus shared financial accountability for an attributed population.
- Public-private exchange (immunization registries, reportable conditions, Medicaid) depends on legal authority, identity matching, standards, and operations—not connectivity alone.
2.3 Interrelationships, HIE, and Continuity of Care
Quick Answer: Task A.2 tests how organizations connect. Continuity of care is a longitudinal information problem. Health information exchange is authorized sharing across organizations—not another name for one EHR. Directed exchange pushes to a known recipient; query-based exchange pulls when the source is unknown or silent. IDNs, ACOs, and public-private partnerships are relationship designs that create HIT obligations.
Why interrelationships matter for CPHIMS
Patients do not experience “hospital,” “clinic,” and “home health” as separate IT projects. They experience one illness journey. Interrelationships among providers, payers, public health, and community partners determine whether that journey is safe. Domain I task A.2 rewards candidates who fix the relationship—workflow, data, legal authority, and accountability—not only the interface engine.
Continuity of care and transitions
Continuity of care means the next clinician knows what happened last: problems, medications, allergies, results, goals, and advance directives are available with enough context to act. Continuity fails when discharge summaries arrive late, specialists cannot see primary-care lists, imaging is repeated because priors are invisible, or the patient is the only courier of paper.
| Handoff | Typical parties | Information at risk |
|---|---|---|
| Primary care to specialist | Clinic and specialty group | Reason for referral, prior workup, authorization |
| ED to inpatient | Emergency and floor teams | Pending results, triage context |
| Hospital to SNF or home health | Case management and post-acute | Medications, wounds, function, goals of care |
| Behavioral and medical | Separate legal entities | Diagnoses, medications, risk, consent-sensitive notes |
| Payer utilization management and provider | Plan and clinic or hospital | Clinical criteria evidence and timelines |
CPHIMS stems plant the failure between organizations. Closed-loop referrals track whether the patient was scheduled, seen, and what changed. Open-loop “send and forget” is not coordination. Medication reconciliation at each transition is a continuity control, not a courtesy.
IDNs and ACOs as interrelationships
An integrated delivery network (IDN) owns or tightly affiliates multiple care settings to manage a continuum: hospitals, medical groups, post-acute, sometimes a pharmacy or a health plan. HIT work is enterprise identity (an EMPI), shared service lines, referral leakage control, and whether to run one EHR tenant or multiple instances connected by exchange. The relationship is structural—common ownership or affiliation.
An Accountable Care Organization (ACO) is a group of providers that accepts responsibility for quality and total cost for an attributed population, for example Medicare Shared Savings or commercial look-alikes. An ACO does not erase legal boundaries; it re-prices the incentive so poor transitions hurt participants. HIT implications include attribution lists, claims-plus-clinical mashups, ADT event notifications, preferred post-acute networks, and multi-entity data-use agreements. Treating an ACO as one more dashboard misses the consortium.
Related structures—clinically integrated networks, patient-centered medical home neighborhoods, bundled episodes—share the rule: multi-entity performance needs multi-entity data with agreed definitions.
HIE versus EHR
An electronic health record (EHR) is an organization’s, or affiliated enterprise’s, system of record for delivering and documenting care. It is typically the legal medical record for that entity.
Health information exchange (HIE) is the electronic movement of health-related information among organizations according to recognized standards and authorization. “HIE” also names regional or national networks that operate those services.
Do not say “we have an EHR, so we have HIE.” An excellent single-facility EHR can still be an island. Conversely, HIE without workflow integration—single sign-on, usable summaries, medication and allergy reconciliation—does not produce continuity. Technical green lights on an interface monitor are not the same as a clinician acting on outside data at the point of care.
Exchange patterns
| Pattern | Mechanism | Typical use |
|---|---|---|
| Directed exchange | Secure send from a known sender to a known recipient | Referral packet; discharge summary to a named skilled-nursing inbox |
| Query-based exchange | Authorized pull from connected sources | ED needs outside history for an unresponsive patient |
| Consumer-mediated exchange | Patient aggregates and shares via portal or app | Patient grants an app or a new clinician access |
| Event notification | Push on ADT or other triggers | Primary care learns of an outside admission |
Modern stacks combine HL7 version 2 messages (ADT, orders, results), C-CDA documents, FHIR APIs, and national frameworks such as TEFCA with Qualified Health Information Networks (QHINs). CPHIMS does not require you to code FHIR resources. It does require you to know why networks exist: reduce brittle point-to-point chaos and improve continuity.
Public and private relationships
U.S. healthcare is a mixed public-private system. Core interrelationships include:
- Clinical providers and public health — immunization information systems, reportable conditions, syndromic surveillance, vital records.
- Providers and Medicaid agencies or managed-care organizations — eligibility, encounters, care management for complex beneficiaries.
- Emergency preparedness networks — bed availability, diversion status, mass-casualty coordination.
- Community-based organizations and clinical teams — food, housing, and transportation referrals, increasingly via closed-loop social-care networks.
- Private HIE participants and QHINs — multi-stakeholder sharing under participation agreements.
These relationships rest on legal authority (what may be shared without individual authorization versus what needs consent), funding, and trust. A private hospital may submit immunizations to a state registry under public-health provisions while still requiring a business associate agreement and stricter controls for commercial secondary use.
Barriers you should expect on the exam
- Identity and data quality — duplicates and overlays; query-based HIE returns the wrong chart or none without a serious EMPI strategy.
- Consent and special categories — HIPAA permits many treatment, payment, and operations disclosures, but 42 CFR Part 2 substance-use records, adolescent confidentiality, and state laws may restrict redisclosure.
- Competitive incentives — leakage fears; federal information-blocking rules constrain improper interference (Chapter 3).
- Semantic heterogeneity — local lab codes, incomplete terminologies, documents that arrive but cannot be filed or compared.
- Cost and governance — who pays for the HIE, who monitors the feed at 2 a.m., who is accountable for shared longitudinal records.
- Usability — forty-page document dumps produce ignore behavior; prioritize high-value events and summary views.
Scenarios and exam traps
Scenario. A Shared Savings ACO spanning an independent primary-care group, a community hospital, and a preferred skilled-nursing facility has high readmissions. The weak answer is “buy one EHR for everyone this quarter.” The strong answer is ADT notifications, closed-loop post-acute handoffs, medication reconciliation at each transition, a shared heart-failure care plan, ACO-owned metric definitions, and query-based HIE for out-of-network hospitals.
Scenario. An ED physician needs allergies for an unresponsive patient whose records live at an unaffiliated clinic. Directed exchange never happened because nobody knew to send a packet. Query-based exchange is the pattern that fits.
Watch these traps:
- Equating HIE only with a regional nonprofit.
- Assuming HIPAA always requires extra consent for treatment-related exchange—special categories and state law may still constrain, but treatment disclosures are often permitted.
- Solving ACO problems with single-facility reports.
- Confusing interface success with clinician-usable continuity.
- Ignoring public-health partners as optional side projects.
An emergency physician needs prior allergy and medication history for an unresponsive patient who usually receives care at an unaffiliated clinic. No discharge packet was sent. Which exchange pattern best matches this need?
Which statement correctly distinguishes an EHR from health information exchange?
A hospital case manager needs to send a discharge summary and medication list to a specific skilled-nursing facility medical-records inbox that already participates in secure clinical messaging. Which pattern should HIT enable first?