Learn
Guides for the tedious work hospitals run on.
Clear, sourced explainers for the people who own hospital operations — HR and payroll, physician relations and HIM, compliance and IT. No fluff, no jargon: what the work is, what the rules say, and how to evaluate a tool that automates it.
Workforce pay & tax self-service
Giving hospital employees self-service access to pay statements and year-end tax forms — W-2 in the US, T4 in Canada — and the rules that govern it.
Employee self-service portals for hospitals
What an employee self-service (ESS) portal is, what hospital workforces specifically need from one, and how to evaluate one.
Read the guide → SpokeElectronic W-2 access & IRS consent rules
How US employers can furnish W-2s electronically — the affirmative-consent requirement, the six disclosures, and the January 31 deadline.
Read the guide → SpokeElectronic T4 access & CRA rules
When Canadian employers can post T4 slips to a secure portal without consent — and the former-employee and on-leave exceptions that still require paper.
Read the guide → ComparisonW-2 vs T4: US and Canada year-end forms
A side-by-side comparison of the US Form W-2 and the Canadian T4 slip — what each reports, the deadlines, and why dual-country employers need both.
Read the guide → SpokePay stub & W-2 access for former employees
How employers give offboarded staff a way to retrieve their final pay stub and W-2 — what the rules require, and why turnover-heavy hospitals should plan for it.
Read the guide → ComparisonStandalone pay/tax portal vs HRIS self-service
When a hospital's HRIS-native self-service (Workday, UKG, Oracle, Infor) is enough for pay and tax documents, and when a focused standalone portal fits better.
Read the guide → SpokeReducing payroll & HR pay/tax call volume
The recurring pay and tax questions that flood HR and payroll, how self-service deflects them, and an honest look at what to measure.
Read the guide → ResourcePay stub requirements by state (US)
How US pay-stub rules vary — no-requirement, access, access/print, opt-out and opt-in states — and what that means for going paperless. Educational, not legal advice.
Read the guide → ComparisonCloud vs on-premises for HR & payroll data
The deployment choice for sensitive employee pay and tax data — vendor cloud versus running in your own environment — and what it means for control, residency and risk.
Read the guide → ResourcePayroll record retention (US & Canada)
How long employers must keep payroll and tax records — FLSA 3 years, IRS 4 years, CRA 6 years — and what that means for offboarded-employee access. Educational, not legal advice.
Read the guide → SpokePay stub access for deskless hospital staff
Why most hospital employees can't easily reach their pay stubs through a desktop portal — and what mobile-first, no-corporate-login self-service takes.
Read the guide → ResourceEmployee portal RFP / evaluation checklist
A free, printable checklist for evaluating an employee pay & tax self-service portal for a hospital workforce — reach, dual W-2/T4, offboarded access, and deployment.
Read the guide →Referrals & physician engagement
Closing the referral loop with community and referring physicians: results delivery, referral status, and read-only access to the records of their patients treated at the hospital.
What is a community physician portal?
A read-only, audited window that lets a hospital's referring and community physicians see their own patients' results and referral status — and how it differs from a patient portal or an HIE.
Read the guide → ComparisonPhysician portal vs HIE vs patient portal
Three things often confused: a community-physician portal, a health information exchange (HIE), and a patient portal. What each is for, who uses it, and how they fit together.
Read the guide → PillarWhat is referral leakage (and how to measure it)?
A clear definition of referral (patient) leakage, how it's measured with claims or encounter data, the drivers behind it — and where physician visibility fits in.
Read the guide → SpokeDelivering results to referring physicians
How hospitals return labs, imaging and reports to the physician who referred the patient — portal, Direct secure messaging, HL7 interface, or fax — and the trade-offs of each.
Read the guide → SpokeReferral status tracking for referring physicians
Why referring physicians so often can't see what happened to a referral they sent — and what closing that visibility gap (scheduled, seen, cancelled, no-show) takes.
Read the guide → ComparisonStandalone vs EHR-native referral management
When a hospital's built-in EHR referral module is enough, and when a standalone or standards-based approach fits better — especially across organizations on different EMRs.
Read the guide → SpokeRead-only record access for community physicians
How a hospital gives referring and community physicians a secure, read-only view of their own patients' records — even when those physicians aren't users of the hospital's EMR.
Read the guide → SpokeResults routing: HL7, FHIR, Direct, TEFCA
The standards hospitals use to move results and referral data to outside clinicians — HL7 v2, FHIR, Direct secure messaging, and TEFCA/QHIN — and what each is for.
Read the guide → SpokeThe referral lifecycle, stage by stage
The end-to-end path of a referral — created, sent, received, triaged, scheduled, seen, outcome shared — and where it most often breaks down.
Read the guide → ComparisonBuild vs buy a referring-physician portal
What it really takes to build a community-physician portal in-house — identity verification, role-scoped access, PHI audit, interoperability, support — versus buying a governed one.
Read the guide → SpokeWhat a physician liaison does
The physician liaison / physician relations role in a hospital's network strategy, and the referral and results data that makes the team effective.
Read the guide → ResourceReferring-physician portal RFP / evaluation checklist
A free, printable checklist for evaluating a community / referring-physician portal — read-only scope, governed onboarding, interoperability, and data sovereignty.
Read the guide →Security & compliance
What it really means to be HIPAA-compliant, and where hospital data should live. Bluefish runs on-premises, in your environment — so employee tax data and PHI stay under your controls and certifications, never a third-party host.
HIPAA-compliant portals & on-premise security
What HIPAA compliance actually requires of a portal (there is no certificate), how employee tax data differs from PHI, and why running on-premises keeps the data under your controls.
Read the guide → SpokeSecuring employee tax data & PHI
The two sensitive data streams a hospital protects, the W-2 phishing scam the IRS warns about, and the safeguards — including why employee self-service and on-premises both reduce the risk.
Read the guide → SpokeUS vs Canada health data privacy
How HIPAA (US), PHIPA (Ontario) and PIPEDA (Canada) compare, what each governs, and the data-residency question an on-premises deployment settles by default.
Read the guide →Have a question these guides didn't answer?
Ask us. We'll point you to the right person — and if you want to see how Bluefish automates the work, we'll show you on real-looking data. No obligation.
Ask us a question