Does Strkr replace the EHR, or does it sit alongside it?
Strkr sits alongside the EHR. The EHR (Epic, athenahealth, eClinicalWorks, Dentrix, Open Dental, or whatever the practice runs) remains the system of record for the clinical chart, prescribing, lab orders, diagnosis codes, and billing. Strkr holds the operations and growth record of truth: patient outreach history, referring provider pipeline, recall campaign motion, review and reputation surface, new patient lead-to-booked-visit funnel, and the staff workflow around all of it. The two systems are linked by patient ID so the front desk can click through from a Strkr patient record to the EHR chart without duplicating clinical data on the Strkr side.
How does Strkr handle HIPAA and patient data?
Strkr is designed with the healthcare compliance posture a Practice Manager needs for operations and outreach. Data is encrypted in transit and at rest, access is permissioned per role and per location, and a full audit log holds every record view, message send, and consent change. Business Associate Agreements are available on the healthcare-tier plan. Strkr intentionally does not ingest the clinical chart from the EHR because the operations use case does not need it. The practice sends contact details, communication preferences, appointment metadata, and consent flags to Strkr; the clinical note stays in the EHR where the HIPAA posture is already in place.
What EHRs does Strkr integrate with?
Strkr integrates with the EHRs that expose a reasonable API or event feed, including athenahealth, eClinicalWorks, DrChrono, Open Dental, Dentrix (via middleware), Kareo, and Elation Health. Epic and Cerner integrations run through FHIR where the practice has access to it. The common integration pattern is a one-way patient feed (new patient, appointment scheduled, appointment completed, appointment cancelled or no-show) into Strkr, which fires the right campaign, reminder, or review request. Strkr does not write back to the chart. For EHRs without a modern API, Strkr supports a nightly CSV ingest with the same event shape.
How does the recall campaign work with the EHR patient list?
The recall list imports from the EHR on a schedule (weekly or monthly) and lands in Strkr as a campaign-worked list. Strkr segments the list by overdue window (90 days, 180 days, 12 months), fires the right multi-step touch (text, email, mailed postcard, follow-up call task), and tracks booked-visit conversion per channel. The Practice Manager approves the Monday morning segment, the campaign runs itself for the week, and the conversion report rolls up by location, provider, and overdue window. Patients with do-not-contact flags in the EHR are suppressed automatically. The recall motion stops being a one-time quarterly push and becomes a continuous operational surface.
Does Strkr handle appointment reminders, or does the EHR do that?
Both can send appointment reminders. The practice chooses which system is the sender of record. Most practices keep the EHR for same-day and next-day appointment confirmations because that is where the schedule lives, and use Strkr for the broader communication layer: recall campaigns, reactivation of lapsed patients, review requests, referring provider marketing, new patient intake messages, birthday and anniversary touches, and no-show follow-up. Where the practice wants a single sender of record, Strkr can take over appointment reminders with the EHR appointment feed as the trigger and native send through the practice brand and phone number.
How does Strkr help with referring provider marketing for a specialty practice?
A specialty practice (orthopedics, cardiology, oral surgery, dermatology, physical therapy, imaging) lives on the referring provider relationship. Strkr holds each referring practice as an account record with contacts (the referring doctor, the office manager, the scheduling coordinator), activity timeline, marketing drop history, referral volume by quarter, and liaison owner. The Practice Manager builds a saved view of referring providers with declining referral trend and routes a liaison visit task before the quarter closes. A referral volume drop fires an automated flow so the practice never finds out six months later that a top referring group stopped sending patients.
Can Strkr replace Birdeye or Podium for reviews?
Strkr handles the review request flow natively (automated post-visit text and email with service recovery path for negative sentiment) and reports star rating trend by location and provider. For practices that already pay for Birdeye or Podium and value the review aggregation across many surfaces, Strkr fires the request and the external tool handles the aggregation. For practices starting fresh, the native Strkr review flow covers the Google and Facebook review funnel without a separate tool, with the request firing on the completed appointment event from the EHR so the request lands within the 2 to 24 hour post-visit window where response rate is highest.
Is this built for a solo practice or a multi-location group?
Both. A solo practice runs the same primitives (patient outreach pipeline, referring provider directory, recall queue, review flow) with a single location dimension on every record. A multi-location group practice or dental organization runs the same primitives across 3 to 50 offices with a location dimension on every record and every report, cross-location saved views, per-location brand and sender identity, and permission scoping so the office manager at a specific location sees only their patients while the Practice Manager at the group level sees every office on one scoreboard.