Employer Group Health
Multi-stakeholder benefits decisions where employer groups, brokers, and members must align on coverage and cost.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Benefit Strategy Discovery
Surface renewal targets, cost drivers, network coverage gaps, clinical priorities, data transparency needs, and the buyer's decision-making timeline.
Discovery Questions
Quick orientation: the renewal picture
- Tell me briefly how you currently run your annual renewal process for group medical, who owns each step, and the cadence.
- How large is your employee population for the plans under review?
- What is your current annual medical premium trend target for next renewal?
- Which stakeholders must sign the final decision and who usually leads negotiations with brokers or consultants?
- Estimate the financial runway you need before a new vendor contract would be approved, in months.
- Describe any recent renewal surprises that changed budget or headcount plans.
Where the money actually goes
- What single forecasting failure on medical trend would make you walk away from a proposed solution this renewal?
- How much of your last year's trend came from pharmacy versus medical claims, in percentage points?
- Which three ICD categories or service lines drove the biggest cost increases last year?
- When you look at provider pricing outliers, which markets create the largest leakage in dollars?
- Tell me about a recent high-cost claim that required cross-team escalation, what happened and what was the result?
- If preserving employee access to their current providers became costly, what would be the acceptable trade-offs for your leadership?
Network and care experience in real life
- When a member cannot find an in-network provider nearby, what breaks downstream for your benefits team and employees?
- Estimate the number of employees in geographies where network adequacy has been reported as an issue.
- List the top specialties or facility types your employees would prioritize, and approximate headcount affected.
- Walk me through a recent claims or prior authorization denial that led to an employee complaint, and how long it took to resolve.
- Do you have existing provider continuity protections in plan documents, and are they enforceable across states?
- Name two metrics you would use to judge whether a network change is causing member disruption.
Clinical programs that actually bend trend
- If a clinical program failed to reduce ER visits by your target, what would you do next?
- Describe how you currently measure the ROI of care management or chronic disease programs, and who vets the calculation.
- List the chronic conditions that drive the most spend, and rank them by annual cost.
- Walk me through an example where a vendor clinical program missed expected outcomes, who raised the concern, and what corrective steps were taken.
- Would your CFO accept a guarantee tied to readmission reduction, and what level of accountability would be required?
- Who on your team must approve any clinical program protocols or patient-level data sharing?
What's getting in the way, and who else is on the table
- Explain why each alternative still looks viable and which one would be hardest to replace if you stayed with it.
- Provide the names or descriptions of the external vendors you have shortlisted or invited to bid.
- Who owns the incumbent relationship internally and what would it take for them to recommend staying?
- Give the top three reasons your procurement or benefits team might prefer an internal solution over an outside carrier.
- Would a two-year trend guarantee matching your target stop the process, or are there other factors that would keep you searching?
- Are any internal teams prepared to operate claims or pharmacy feeds if you chose a self-funded model?
Practical gates: data, systems, and timeline
- Identify the single technical dependency that would block a go-live inside your target enrollment window.
- Provide the category names for systems that must connect, for example HRIS, payroll, benefits admin, or EDI gateway.
- Identify the owner of API access or SFTP credentials for those systems, and confirm whether they are authorized to share them.
- On a three-point scale, rate the readiness of your member and claims data: clean, needs work, high manual cleanup.
- Do you have any regulatory approvals, union agreements, or multi-state filing needs that could delay data sharing or plan changes?
- Name the single resource gap that would kill the timeline if left unfilled, for example staffing, vendor mapping, or executive approvals.
Closing the loop: decision criteria and next steps
- Pinpoint the one remaining approval or policy that would prevent a near-term signature even if numbers look right.
- Select the metrics that must be included in a contract to trigger payment or guarantees.
- Within how many weeks does your finance team need final pricing to commit to budget?
- Give the primary and backup owners on your side for implementation, including titles and contact roles.
- Are there legal or procurement gates that require more than routine review, such as union signoffs or multi-state approvals?
- By what date do you need a signed contract to meet your open enrollment or billing cycle?
-
Clinical & Network Experience
Walk through how network breadth, clinical programs, pharmacy integration, and analytics will address the buyer's specific scenarios and risks.
Solution Experience
- Clinical & Network Experience Session
- Confirm the current state and its cost
- Deliver a tailored provider access map for your top 10 employee ZIP codes showing in-network provider counts and typical travel times.
- You confirm that the assessed network coverage would prevent the employee disruption scenarios you described.
- You confirm that the clinical workflows shown would change utilization outcomes for the specific cases you raised, such as ER visits and readmissions.
- Map employee scenarios to network coverage
- Run claims and pharmacy analytics on a sample 6-month extract and deliver a one-page executive summary of top trend drivers and recommended interventions.
- You confirm that the pharmacy analytics shown surface the main trend drivers you need to control premium trend.
- Run clinical program workflows against your example cases
- Provide a de-identified sample claims and pharmacy extract for the requested 6-month period to enable the analytics run.
- Demonstrate pharmacy integration and analytics on trend drivers
- List the top five employee locations and three example clinical cases you want modeled in the next analysis.
- You agree on the remaining evidence needed before selection and the timeline for those deliverables.
- Validate the future state
- Confirm the decision timeline and who must validate the evidence before award.
- Clinical & Network Experience Session
- Clinical & Network Experience Deck
- Solution Brief – Clinical & Network Experience
- meeting
- slides
- document
-
Plan & Services Scope
Define plan designs, funding model (fully-, self-, level-funded), network adequacy requirements, clinical program scope, data access, reporting cadence, and responsibilities.
Scope Configuration
- Administer Medical Claims Processing
- Provide National Provider Network Access
- Manage Provider Credentialing and Network Adequacy
- Administer Pharmacy Benefit Management
- Deliver Monthly Claims and Pharmacy Analytics Feed
- Operate Care Management for High-Cost Members
- Perform Utilization Management and Prior Authorization
- Coordinate Transitions of Care and Readmission Reduction
- Run Chronic Disease Management Programs
- Integrate Behavioral Health Services and Care Coordination
- Provide Dedicated Account Management and Client Support
- Deliver Renewal Pricing Proposal with Trend Guarantee
Scope Questions
Administer Medical Claims Processing
- Which claim submission formats must be supported for your population (for example EDI 837 Institutional, 837 Professional, flat-file CSV of adjudicated lines)?
- How many paid claims and claim lines do you expect per month at go-live and at 12 months?
- What turnaround SLA do you require for first-pass adjudication of clean claims (for example adjudicate clean electronic claims within 48 hours)?
- Who will supply initial member eligibility and census (for example an HRIS export with employee ID, DOB, plan code, hire date)?
- Confirm required remittance format for payment reconciliation (for example EDI 835, CSV with claim identifier and paid amount).
- Within which systems must claim-level integrations be validated (for example your payroll/Human Resources Information System (HRIS), benefits platform, or third-party stop-loss administrator)?
- List any specialized claim types that need separate handling at go-live (for example workers compensation crossover, COB/coordination of benefits, carve-out vendors).
Provide National Provider Network Access
- Which geographic coverage rule should we apply to test network adequacy by ZIP code or county (for example 95% of employee ZIP codes must have in-network access to a primary care provider within 30 minutes)?
- How many named providers or NPIs must be maintained as in-network to avoid disruption for employees undergoing active treatment (please list NPIs or attach roster)?
- What percentage of your employee census must retain access to their current in-network specialist without a change in authorization requirement?
- Name any critical facilities or systems (for example specific hospital IDs or system names) that must be included in the network at go-live.
- Acceptance criteria for network adequacy: what measurable evidence will validate go-live (for example county-by-county ZIP coverage report showing X% access, provider directory match to provided NPI roster)?
- Are telehealth, behavioral health virtual visits, or urgent care sites required to meet the same travel-time coverage thresholds as brick-and-mortar providers?
- Specify whether you require continuity-of-care letters or outreach to affected employees when a PCP or specialist is out-of-network within the first 90 days.
Manage Provider Credentialing and Network Adequacy
- State the required primary source verification frequency for credentialing (for example every 36 months or at hire).
- Outline the provider roster update cadence you require for the public directory and for internal network files (for example weekly CSV, monthly API).
- Describe any delegated credentialing relationships you expect to remain in place (for example delegated medical group credentialing versus central credentialing).
- Identify the provider directory fields you require in the feed (for example NPI, taxonomy, TIN, practice address, phone, accepting new patients flag).
- Specify required notification lead time for provider termination or contract change that impacts access (for example 30 days prior notice to affected members).
- Indicate the monitoring cadence for network adequacy reports you want (for example monthly county-level access exceptions delivered as CSV).
Administer Pharmacy Benefit Management
- Describe the formulary design you require (for example 3-tier, 4-tier with specialty tier, step therapy rules) and any must-have excluded or preferred drug classes.
- Which pharmacy claims formats and standards must be supported for your integration (for example NCPDP SCRIPT for e-prescribing and NCPDP claim transactions)?
- Indicate whether you require rebate pass-through reporting and the level of transparency (for example gross vs net per NDC).
- Specify required specialty pharmacy handling and whether you permit external specialty vendors or require in-network specialty distribution.
- Provide your preferred prior authorization rules delivery method for pharmacy (for example real-time API, pre-populated CSV, portal) and expected decision SLA.
- Select the mail-order fulfillment options you require (for example 90-day mail order with NDC mapping, copay parity), and any required pharmacy network exclusions.
Deliver Monthly Claims and Pharmacy Analytics Feed
- Format for the analytics feed: which of the following formats do you require for claims and pharmacy analytics delivery (for example line-level CSV, parquet to S3, or API)?
- Cadence for reporting: what is the acceptable maximum lag for monthly feeds (for example 10 business days after month close)?
- Acceptance criteria for data feeds: what evidence will validate feed completeness and accuracy (for example file-level row counts match ledger totals, field-level coverage > 99%, timestamped load manifest)?
- Owner for data integration: who in your organization will be the named technical contact for SFTP/API ingestion and field mapping approvals?
- Where will the analytics files be delivered or accessible (for example SFTP host, secure API endpoint, cloud bucket) and do you require encrypted transfer with specific cipher?
- Which reporting measures must be present in the monthly feed schema (for example claim paid amount, allowed amount, member age, diagnosis ICD-10, NDC for pharmacy)?
Operate Care Management for High-Cost Members
- Define the threshold for 'high-cost' member enrollment in care management (for example claims > $50,000 in 12 months or top 1% by spend).
- How will you authorize outreach to high-cost members (for example opt-in, opt-out, implied consent via plan SPD, signed consent form)?
- What clinical artifacts must care managers access or produce (for example care plan in CCD, case notes, documented discharge summary), and in which format?
- Identify EHR or ADT integrations required for case-finding (for example HL7 ADT feeds from partner hospitals).
- Estimate target outcomes for high-cost care management over 12 months (for example reduce inpatient days by X, lower average claim per member by Y%).
- Indicate whether you require direct member-facing remote monitoring (for example device-supplied BP/glucose data integrated via FHIR) as part of chronic/high-cost management.
Perform Utilization Management and Prior Authorization
- Which service categories require prior authorization at go-live (for example advanced imaging CPT codes, outpatient surgery, DME above threshold)?
- What decision SLA do you require for standard prior authorization requests (for example 72 hours for routine, 24 hours for urgent)?
- Which clinical criteria sources should be applied for determinations (for example InterQual, MCG, or custom clinical policy), and do you require visibility to applied criteria in the authorization response?
- How should prior authorization decisions be delivered to providers (for example portal, HL7 FHIR DocumentReference, automated fax/email)?
- Authorization turnaround: who will own appeals and external review workflows and what timelines do you require for appeals handling?
- Which retrospective review windows should be enforced (for example 30/60/90 days after claim) and which services are excluded from retrospective review?
Coordinate Transitions of Care and Readmission Reduction
- How should admission-discharge-transfer (ADT) data be delivered for transition-of-care workflows (for example HL7 ADT feed, daily CSV of admissions with member ID and facility)?
- What is your current baseline 30-day all-cause readmission rate for the population (provide numeric rate per 1,000 or percentage)?
- Which post-discharge interventions do you require as part of the program (for example pharmacist medication reconciliation within 48 hours, nurse follow-up call within 72 hours)?
- Who will provide discharge rosters or ADT exceptions when a member is admitted out of network?
- Specify reporting needs for readmission reduction (for example weekly inpatient census, monthly readmission rate by facility) and delivery method.
- Indicate escalation rules for high-risk discharges (for example within 24 hours escalate to clinical director if no contact).
Run Chronic Disease Management Programs
- For which chronic conditions do you want targeted programs at go-live (for example diabetes with HbA1c tracking, congestive heart failure with BNP monitoring, COPD)?
- Which enrollment triggers should be used to enroll members (for example ICD-10 diagnosis in claims, medication fills, clinical lab thresholds)?
- What clinical metrics must the program track and report (for example percent with HbA1c < 8%, blood pressure control defined as <140/90)?
- Describe required device or remote monitoring integrations (for example Bluetooth glucometer data via FHIR, BP cuff uploads) and expected data ingestion cadence.
- What target improvement do you expect in 12 months for each condition (for example reduce uncontrolled HbA1c by X percentage points)?
- Identify who will own member consent and escalation to primary care for chronic program enrollment.
Integrate Behavioral Health Services and Care Coordination
- Which behavioral health services must be included in the integrated offering (for example outpatient therapy, intensive outpatient programs, crisis services)?
- Does your plan require parity reporting or specialized behavioral health utilization reports for compliance purposes (for example MHPAEA parity metrics)?
- Which screening tools should be captured and reported for behavioral health measurement (for example PHQ-9 scores, GAD-7 scores) and how often?
- How should referrals into behavioral health care coordination be triggered (for example primary care referral, ED screening, claims-based flags)?
-
Mutual Commitment
Finalize pricing, trend guarantees, performance SLAs, data-sharing permissions, and contractual modules needed to move to implementation.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW) — Implementation
- Pricing & Trend Guarantee Exhibit
- Service Level Agreement (SLA) & Performance Remedies
- Data Use & Security Agreement (DPA)
- HIPAA Business Associate Addendum (BAA) — conditional
- Stop-Loss / Reinsurance Exhibit — conditional
- Implementation Change Order
-
Implementation Planning
Plan enrollment timing, claims and pharmacy data feeds, provider network activation, communications, and operational handoffs with named owners and milestones.
-
Outcomes & Continuous Improvement
Track success against agreed metrics (premium trend, network access incidents, ER use, readmissions, chronic care outcomes) and maintain a shared log for issues and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Acceptance Gate Review (around day 90)
- Quarterly Outcomes Review
- Continuous Improvement Backlog Review (monthly operational)
Issues & Enhancements
- Update the shared issue and enhancement log with agreed priorities, owners, and resolution dates.
- Publish the acceptance record showing pass/fail per criterion and the captured buyer acceptance decision.
- Create remediation tickets for conditional or failed criteria with milestones and final re-evaluation dates.
- If applicable, produce the incumbent decommission checklist and schedule the decommission activities.
- Quarterly trend presentation
- Confirm whether network access incidents and 30-day readmission rate are improving or require further action.
- Ensure the shared issue log is current with clear owners and resolution dates for all active items.
- Agree the priority order for enhancement requests to be advanced in the next quarter.
- Re-confirm success criteria and ownership
- Deliver a concise quarterly outcomes report highlighting metric deltas and remediation progress.
- Schedule any targeted detailed review sessions for persistent high-impact issues.
- Metric delta review
- Ensure monthly premium trend and ER utilization rate deltas are tracked and any adverse movements have assigned remediation.
- Reduce the active improvement backlog by closing verified items and escalating blocked work.
- Confirm short-term operational commitments and dates for the next monthly checkpoint.
- Update and circulate the monthly metric snapshot and the updated backlog status.
- Close verified tickets and move conditional items to re-test with clear acceptance criteria.
- Flag any persistent or high-severity items for escalation to the quarterly Outcomes Review.
- Deployment validation documented and distributed with a clear owner for each item.
- Top go-live blockers identified with owners and target resolution dates.
- Confirmation that initial data feeds are producing expected records and no critical reconciliation gaps remain.
- Publish the deployment validation report capturing feed health, user access counts, and outstanding defects.
- Open remediation tickets for critical blockers with target resolution dates and escalate any that threaten core operations.
- Schedule the First Measurement Review for the first meaningful data window within weeks 4-10.
- Present first-cycle results
- Determine whether monthly premium trend and ER utilization rate are moving toward the targets and document any shortfalls.
- Assign specific corrective actions with owners and dates for each material gap.
- Confirm readiness and timeline for the Acceptance Gate meeting.
- Deliver the detailed metric pack showing methodology, baselines, and the first measurement window data.
- Open remediation tasks for data or operational gaps identified, with completion dates and acceptance criteria.
- Share the timeline and evidence requirements required for the Acceptance Gate meeting.
- Restate acceptance criteria and numeric targets
- Formal acceptance status recorded per acceptance criterion and the buyer's acceptance decision captured.
- Remediation plan documented with owners and firm resolution dates for any non-conformances.
- If replacing an incumbent, confirm a single owner will complete decommissioning or archival tasks on the agreed timeline.
- Review open issues and remediation progress
- Backlog burn-down and ticket status
- Present outcome data against each criterion
- Root-cause diagnosis for variances
- Deployment and data feed validation
- Enhancement request prioritization
- Document pass/fail per criterion and capture acceptance decision
- Test and verification of fixes
- Agree corrective actions and timelines
- Early adoption signals and usage patterns
- Agree immediate next actions
- Open blockers and defect triage
- Confirm path to Acceptance Gate
- Operational handoffs and next steps
- Agree remediation plan for failed or conditional items
- Agree immediate remediation actions
- Incumbent decommission check, if applicable