Is Strkr HIPAA compliant for healthcare marketing use?
Yes. Strkr is HIPAA compliant with a signed Business Associate Agreement available for all healthcare marketing customers. The BAA covers all services touching PHI including marketing campaign management, patient communication through SMS (Strkr Messaging) and email, EHR integration, patient portal integration, and attribution tracking. 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. The marketing-specific HIPAA considerations include authorization requirement for marketing communications using PHI, minimum-necessary scope for campaign targeting, and audit trail for every campaign send with recipient scope documented. For health systems with heavy direct-to-consumer marketing (service line awareness, patient acquisition, retention campaigns), the BAA explicitly covers the marketing campaigns with the appropriate authorization scope. 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.
How does Strkr handle CMS Medicare marketing rules?
For health systems with Medicare Advantage plans or Part D sponsors, the CMS compliance workflow handles the requirements: content pre-approval through the Health Plan Management System (HPMS) with submission tracking and version control, scope of appointment documentation for sales activity with electronic capture and audit trail, specific disclosures required in printed and electronic marketing material, lookback and lookforward period management for AEP (Annual Enrollment Period) communication running October 15 through December 7, OEP (Open Enrollment Period) communication for January 1 through March 31, SEP (Special Enrollment Period) rules for qualifying events. The content review workflow routes material through the CMS-required reviewers with the audit trail capturing every version and approval. For dual-eligible special needs plans (D-SNPs), institutional special needs plans (I-SNPs), and chronic condition special needs plans (C-SNPs), the plan-type marketing rules apply with the appropriate scope. For health systems not operating Medicare Advantage directly but marketing to Medicare-eligible patients for service line care, the HIPAA authorization requirements apply without the CMS pre-approval overhead.
What EHR integrations ship for healthcare marketing attribution?
Native integrations for Epic (via MyChart FHIR APIs for ambulatory practice; EpicCare Link for broader clinical data; Epic Caboodle for enterprise analytics in specific implementations), Cerner (now Oracle Health, via CernerCare and Millennium platform), athenahealth athenaOne, Allscripts Professional and TouchWorks, eClinicalWorks, NextGen, Greenway Health, AdvancedMD, Meditech, CPSI. The integration surfaces appointment history, procedure history, service line encounter data, and discharge disposition for marketing attribution. HIPAA scope controls limit PHI exposure to minimum-necessary for the marketing use. Writeback capability varies by EHR vendor; Epic FHIR writes are limited by scope. For health systems with heavy Epic implementation, the attribution integration typically runs through FHIR for ambulatory data with the enterprise clinical data available through broader Epic integration channels. KMS-encrypted credential storage with the integration debugger surfacing every sync event.
How does the physician liaison outreach workflow run?
Each physician liaison owns a territory of referring practices (primary care physicians, urgent care centers, specialty peers in referring positions) grouped by geographic area, service line relevance, and priority tier. Structured cultivation cadence runs per account: quarterly visit minimum for priority accounts, speaker program invitations for clinical interest matches, clinical update distribution for the service lines, specific cultivation activities (grand rounds presentations, co-authored case reports, continuing medical education opportunities). The liaison captures structured visit notes (clinical discussion, specific interest surfaced, next-step commitments). Referral volume attributes per referring physician per service line per quarter for ROI reporting. Monthly performance review covers visits completed, referral volume captured, specific cultivation wins (new high-volume referrer activated, declining referrer re-engaged, speaker program success). Quarterly review ties referral volume trends to cultivation activity for the growth operations conversation. For health systems with multiple service lines and territorial complexity, the territory assignment handles overlapping specialty focus and priority rebalancing.
How does attribution work across phone, web, direct scheduling, and portal?
Attribution runs multi-touch across channels: phone calls through CallRail, CallTrackingMetrics, DialogTech, or Invoca attribute to the campaign source (TV, radio, print, digital, specific landing page) with call recordings and speech analytics for conversion quality analysis; web traffic through UTM parameters, Google Analytics 4, and specific attribution pixels attribute to campaign source; direct scheduling through Zocdoc, Solv, Luma Health, DocASAP, Phreesia, or health system scheduling tools attribute appointment type, specific physician, and specific procedure to the originating campaign; patient portal signup through MyChart, FollowMyHealth, athenaPatient attributes new portal enrollment to the originating campaign. The multi-touch model attributes credit across the patient journey (first touch, last touch, position-based, data-driven) based on the health system's attribution preference. HIPAA scope controls limit PHI exposure in attribution data. Service line attribution calculates ROI per campaign with campaign spend, volume acquired, net revenue contribution adjusted for payer mix, downstream revenue (follow-on procedures, specialist referrals, hospital admissions), and total ROI. For health systems with complex multi-service-line patient journeys, the attribution model handles the cross-service-line conversion patterns.
Can Strkr handle TCPA consent capture at health-system scale?
Yes. TCPA compliance for SMS and voice outreach requires express written consent from the patient before promotional messages with specific statutory language. The consent workflow captures consent through intake forms (digital or paper with signed scan), patient portal signup, website form submission, in-office intake tablet, and inbound call recording with verbal consent capture. The consent record stamps the patient profile with the executed consent date, specific scope (appointment reminders, service line marketing, educational content, recall campaigns, specific promotional campaigns), and the original consent capture mechanism. SMS and voice messages respect the consent scope with the audit log tracking every outbound message with sender, recipient, content, timestamp. For patients who opt out via STOP keyword or verbal request, the opt-out stamps the profile immediately and blocks future messaging. For health systems scaling from informal consent capture to structured capture, the migration workflow handles the transition without re-consenting existing patients while bringing new patients through structured capture. For TCPA class action defense, the full audit trail provides evidence of express written consent, specific scope agreed, opt-out respect, and complete message history per patient.