Isn't a community physician portal just an HIE?

No. An HIE is a network that exchanges data among many organizations, often regionally, and a clinician usually reaches it through their own EHR. A community physician portal is a hospital-provided application a referring physician logs into directly to see their own patients at that hospital. A hospital can participate in an HIE and still offer a physician portal — they solve different problems.

Do we still need a physician portal if we have a patient portal?

Yes, if you want to serve referring physicians. A patient portal is built for patients viewing their own records; it doesn't give a referring physician a clinician-oriented view of the patients they sent in, or referral status. The two audiences and workflows are distinct.

Where does Direct secure messaging or FHIR fit in?

Those are transport standards for moving data — Direct secure messaging sends results clinician-to-clinician, and FHIR/HL7 are the interfaces systems use to share data. A community physician portal is a destination clinicians use; it can be fed by standards like HL7 and FHIR. Standards move the data; the portal is where a physician actually reads it.

Referrals & physician engagement

Physician portal vs HIE vs patient portal: what's the difference?

Updated June 2026 · Reviewed by David Higginson, CHIME Innovator of the Year

Three things get lumped together in healthcare-IT conversations — physician portal, HIE, patient portal — and conflating them leads to buying the wrong thing. Here's the clean distinction.

A community physician portal gives a hospital's referring physicians a read-only view of their own patients' hospital records and referral status. A health information exchange (HIE) is infrastructure that moves patient data between separate organizations. A patient portal gives patients access to their own records. All three improve access to health information — but for different users, and they are not substitutes for one another.

Side by side

	Community physician portal	Health information exchange (HIE)	Patient portal
Primary user	Referring / community physicians	Organizations and their systems	Patients
What it's for	Seeing your own patients' hospital results and referral status	Exchanging patient data across organizations	Viewing and managing your own records
Scope of data	The physician's own patients at that hospital	Patients across participating organizations	The individual patient's own record
How it's accessed	A hospital application the physician logs into	Usually through the clinician's own EHR or a query	A website or app for the patient
Access type	Read-only, audited	Varies by network and agreement	Read-only, plus self-service actions

Why the distinction matters

Each tool leaves a gap the others don't fill. A patient portal won't give a referring physician a clinician's view of the patients they sent in. An HIE moves data between organizations but doesn't, by itself, give a specific community physician a tidy, governed view of their own patients at your hospital — and many community practices aren't deeply wired into a regional HIE anyway. EHR-native provider portals (for example, Epic's EpicCare Link) cover this for clinicians inside that ecosystem, but a standards-based portal can serve community physicians regardless of which EMR they or you run.

They work together

These aren't competitors so much as layers. A hospital can run a patient portal, participate in an HIE, and offer a community physician portal — each serving a different audience. Standards like HL7 and FHIR move the data underneath; the portal is where a referring physician actually reads it.

Where this fits at Bluefish

HealthPoint is the community physician portal in this picture: a standards-based, read-only, audited view that gives referring physicians their own patients' results and referral status, built on HL7 v2 and FHIR so it isn't tied to one EMR. Start with what a community physician portal is, or see how it handles referral status tracking.

Sources: HealthIT.gov (ONC) — What is HIE? · HealthIT.gov (ONC) — What is a patient portal?

Frequently asked questions

What's the difference between a physician portal, an HIE, and a patient portal?: They serve different users. A community physician portal gives a hospital's referring physicians a read-only view of their own patients' hospital records and referral status. A health information exchange (HIE) is infrastructure that moves patient data between separate organizations. A patient portal gives patients access to their own records. All three improve access to information, but for different people and purposes.
Isn't a community physician portal just an HIE?: No. An HIE is a network that exchanges data among many organizations, often regionally, and a clinician usually reaches it through their own EHR. A community physician portal is a hospital-provided application a referring physician logs into directly to see their own patients at that hospital. A hospital can participate in an HIE and still offer a physician portal — they solve different problems.
Do we still need a physician portal if we have a patient portal?: Yes, if you want to serve referring physicians. A patient portal is built for patients viewing their own records; it doesn't give a referring physician a clinician-oriented view of the patients they sent in, or referral status. The two audiences and workflows are distinct.
Where does Direct secure messaging or FHIR fit in?: Those are transport standards for moving data — Direct secure messaging sends results clinician-to-clinician, and FHIR/HL7 are the interfaces systems use to share data. A community physician portal is a destination clinicians use; it can be fed by standards like HL7 and FHIR. Standards move the data; the portal is where a physician actually reads it.