How is it different from a patient portal?

A patient portal serves patients, giving each person access to their own records. A community physician portal serves clinicians, giving a referring physician a view of their own patients' hospital information so they can coordinate care. Same idea of secure self-service, different audience and different scope of data.

What can a referring physician actually see?

Only their own patients — the ones they referred or are involved in caring for — and only on a read-only basis. They can view referral status and clinical information such as labs, medications, problems, imaging and documents. They cannot chart, order, prescribe, or write back to the record. Emergency 'break-the-glass' access exists for urgent situations and is governed and audited separately.

How is access controlled and kept compliant?

Practices sign up online; automated checks run against sources like the NPI Registry, the OIG exclusion list (LEIE) and SAM.gov; and the hospital's HIM team approves what passes from a review queue. Every PHI access is logged at the row level — who viewed what patient, when, and from where — and access follows the hospital's own governance because the system runs in the hospital's environment.

Is it a copy of our EMR or a second record?

No. It's a governed, read-only window onto the records the hospital already holds — not a second copy and not a separate EMR. The hospital's system of record stays the single source of truth.

Referrals & physician engagement

What is a community physician portal?

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

When a community physician refers a patient to the hospital, they too often go dark — no view of the results, no idea whether the visit even happened. A community physician portal is how hospitals close that gap without burying their HIM team in records requests.

A community (or affiliated) physician portal is a secure system that gives a hospital's referring and community physicians read-only, audited access to information about their own patients treated at the hospital — typically referral status and clinical results. It is not a patient portal (which serves patients), not a health information exchange (which moves data between organizations), and not a second copy of the EMR. It's a governed window onto the records the hospital already holds.

The problem it solves

Two groups feel the pain of the old way. Referring physicians send a patient in and then wait — calling for results, watching for a faxed report that arrives days late, never sure whether a referral was scheduled or fell through. The hospital's Health Information Management (HIM) team absorbs the other side of it: a steady queue of records requests to fulfill by hand, plus paper onboarding for every new practice that wants access. A community physician portal replaces both with self-service — the physician pulls what they need, and HIM stops being a fulfillment desk.

What referring physicians can see

Scope is the whole point: a physician sees only their own patients, and only read-only. Within that, they can view the patient's referral status and clinical picture — labs, medications, problems, imaging, documents and more — in real time, rather than waiting on a fax or a callback. They cannot chart, order, prescribe or write back to the record. For genuine emergencies, a governed, separately-audited break-the-glass path exists.

How access is governed

Because the data is PHI, access is controlled tightly and provably:

Automated identity verification. Practices self-sign-up, and checks run automatically against the NPI Registry, the OIG exclusion list (LEIE) and SAM.gov before a human ever reviews the application.
HIM approves from a queue. The hospital's HIM team approves, denies or requests more information — from a review queue, not a filing cabinet.
Every access audited. Each PHI view is logged at the row level: who, which patient, when, from where.
Your governance. The portal runs in the hospital's environment, under the hospital's policies — it extends the EMR rather than exporting from it.

Where it sits among the look-alikes

A community physician portal is easy to confuse with a patient portal or a health information exchange, but each does a different job. The short version: patient portals are for patients, HIEs move data between organizations, and a community physician portal gives referring clinicians a read-only view of their own patients' hospital records. We lay out the differences in physician portal vs HIE vs patient portal.

Where this fits at Bluefish

HealthPoint is Bluefish's community-physician portal: it gives referring physicians a real-time, governed, fully-audited view of their own patients' records and referral status, and gives HIM an onboarding and review queue in place of paper. Related reading: referral status tracking and delivering results to referring physicians.

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

Frequently asked questions

What is a community physician portal?: It's a secure system that lets a hospital's referring and community physicians see information about their own patients who were treated at the hospital — typically the status of referrals they sent and the clinical results of those patients — on a read-only, fully audited basis. It exists to close the visibility gap for outside clinicians and to take the manual records-release burden off the hospital's Health Information Management (HIM) team.
How is it different from a patient portal?: A patient portal serves patients, giving each person access to their own records. A community physician portal serves clinicians, giving a referring physician a view of their own patients' hospital information so they can coordinate care. Same idea of secure self-service, different audience and different scope of data.
What can a referring physician actually see?: Only their own patients — the ones they referred or are involved in caring for — and only on a read-only basis. They can view referral status and clinical information such as labs, medications, problems, imaging and documents. They cannot chart, order, prescribe, or write back to the record. Emergency 'break-the-glass' access exists for urgent situations and is governed and audited separately.
How is access controlled and kept compliant?: Practices sign up online; automated checks run against sources like the NPI Registry, the OIG exclusion list (LEIE) and SAM.gov; and the hospital's HIM team approves what passes from a review queue. Every PHI access is logged at the row level — who viewed what patient, when, and from where — and access follows the hospital's own governance because the system runs in the hospital's environment.
Is it a copy of our EMR or a second record?: No. It's a governed, read-only window onto the records the hospital already holds — not a second copy and not a separate EMR. The hospital's system of record stays the single source of truth.