Is Strkr HIPAA compliant for healthcare provider use?
Yes. Strkr is HIPAA compliant with a signed Business Associate Agreement available for all healthcare provider customers. The BAA covers all services touching PHI including patient relationship management, care coordination workflow, patient communication through SMS (Strkr Messaging) and email, EHR integration, HIE integration, patient portal integration, and referral network management. HIPAA technical safeguards include encryption at rest and in transit, role-based access controls scoped to minimum necessary, audit logging on every PHI access, and session timeout for inactive users. HIPAA administrative safeguards include workforce training requirements, incident response procedures, and periodic access review. For integrated delivery networks and provider networks with heavy clinical operations integration, the BAA explicitly covers the clinical workflow integration with the appropriate scope controls. Strkr is also pursuing SOC 2 Type II certification which continues through 2026-Q4 for additional security attestation. GDPR and CCPA compliance covers international and California patients.
What EHR integrations ship for healthcare providers?
Native integrations for the major provider EHRs: Epic (ambulatory via MyChart FHIR APIs, enterprise via EpicCare Link, specific analytics via Caboodle in some implementations), Cerner (now Oracle Health, via Millennium platform integration), athenahealth athenaOne (ambulatory focus), Meditech Expanse (small-to-mid hospital focus), Allscripts (Professional, TouchWorks, Sunrise Clinical), eClinicalWorks (ambulatory focus), NextGen (specialty and primary care), Greenway Health (ambulatory), AdvancedMD, DrChrono, CPSI (rural hospital focus), Nextgen Office, Practice Fusion. The integration surfaces patient demographics, encounter history, procedure history, discharge disposition, specific clinical context under HIPAA scope. Writeback capability varies by EHR vendor. For enterprise Epic environments, the integration typically runs through MyChart FHIR for ambulatory data with EpicCare Link for broader clinical data access where appropriate. For Cerner (Oracle Health) environments, the Millennium platform integration covers both ambulatory and inpatient data. KMS-encrypted credential storage with the integration debugger surfacing every sync event. We never route the integration through Zapier because every integration ships as first-class native code.
How does the referral network management workflow run?
Each referring physician record carries practice affiliation, specialty, NPI number, referral volume by service line and quarter, last liaison contact, upcoming visit, specific clinical interests, personal preferences, and cultivation state (scored 0 to 100). The physician liaison owns a territory of referring physicians with structured cultivation cadence: quarterly visit minimum for priority accounts, speaker program invitations for clinical interest matches, clinical update distribution per service line, specific cultivation activities (grand rounds presentations, co-authored case reports, continuing medical education opportunities, academic affiliations where applicable). Weekly liaison review surfaces overdue cultivation, declining referral volume signals, and upcoming visit targets. The liaison captures structured visit notes (clinical discussion, specific interest surfaced, next-step commitments). Monthly performance review ties referral volume to cultivation activity. For health systems with multiple service lines and specific physician liaison teams per service line, the territory assignment handles overlapping relationships with the appropriate service line context. Quarterly review drives business development planning for the next quarter with specific accounts targeted for cultivation investment or deprioritization.
How does care coordination work across the continuum?
Care coordination workflow handles the structured post-encounter transitions: post-surgical follow-up with specific day-count check-ins per procedure (knee replacement day 3, 7, 14, 30, 90), post-discharge care with 7-day post-discharge check for all discharges and specific condition protocols for high-risk conditions (CHF, COPD, pneumonia, sepsis, hip fracture), chronic condition management with specific disease management protocols per condition (diabetes with A1C monitoring, hypertension with BP tracking, heart failure with weight monitoring, COPD with inhaler technique review), preventive care gap closure (annual physical, specific age-appropriate screening, immunization updates), transitions of care with structured handoffs between providers. The workflow runs through care managers, patient care coordinators, and clinical pharmacists depending on the protocol. HIPAA scope controls limit PHI exposure to minimum-necessary. For health systems operating under risk-bearing contracts (Medicare Advantage, ACO contracts, bundled payment arrangements), the care coordination workflow drives measurable quality metric improvement and cost of care management. For health systems not operating under risk, the workflow drives patient satisfaction and patient retention.
What does patient leakage detection look like?
Patient leakage detection surfaces patients receiving care outside the health system network when in-network capability exists. The detection runs through claims data (where contractually available from payer feeds), referral tracking (outgoing referrals to out-of-network providers), patient self-reported care, and HIE data showing care encounters at non-network facilities. The alert routes to the primary care physician or care manager for retention conversation with specific context (which service was received out-of-network, which in-network provider could have delivered that service, what triggered the out-of-network choice). Retention outreach runs through structured conversation with service recovery (specific scheduling with the in-network provider, specific concerns addressed, specific communication improvements). For health systems operating under risk-bearing contracts, leakage reduction drives measurable financial impact (every patient retained in-network represents roughly $11,000 to $14,000 in annual revenue at typical case mix). For health systems not operating under risk but focused on growth, leakage reduction drives market share retention. The leakage detection respects HIPAA scope with the alert data limited to necessary context for the retention conversation.
How does satisfaction and experience survey management work?
Patient satisfaction surveys capture HCAHPS (Hospital Consumer Assessment of Healthcare Providers and Systems) measures for inpatient care, CG-CAHPS (Clinician and Group CAHPS) measures for ambulatory care, specific service line surveys (OAS CAHPS for outpatient and ambulatory surgery, ICH CAHPS for in-center hemodialysis, Hospice CAHPS, Home Health CAHPS, specific commercial surveys). The survey instrument validation respects the CMS requirements for publicly reported measures. Score trending surfaces decline patterns per nursing unit, physician, service line, and location with specific intervention triggers for low-scoring responses (routing to patient advocacy for immediate service recovery, routing to clinical quality for pattern investigation, routing to specific improvement teams for sustained improvement). Dashboard reporting runs for the executive team, service line directors, nursing leadership, and specific physician groups with the appropriate scope. For health systems with publicly reported CMS measures affecting Medicare reimbursement (Hospital Value-Based Purchasing, specific star rating measures), the satisfaction trending feeds directly into reimbursement improvement activity. For health systems focused on reputation and market share, the trending drives marketing and brand investment decisions.
