Accountable Care Organizations
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
-
Outcome Discovery
Align on target outcomes (quality, shared savings, downside tolerance), current workflows, patient panel characteristics, EHRs, and the practice decision-makers and operational owners.
Discovery Questions
A quick practice snapshot to get us started
- Tell me briefly about your practice model, location, and whether you operate as independent, part of a group, or under a larger health system
- How many clinicians and mid-level providers are on site across your locations
- Which patient panel sizes and payer mixes best describe your typical primary care site
- In a typical month, how many annual wellness visits (AWVs) and chronic-care outreach tasks does a single clinician need to complete
- Do you currently have a target for shared savings participation, downside tolerance, or a threshold that would rule this out
Where your daily workflows leak value
- When was the last time your practice missed a quality payment or incentive because of data, documentation, or workflow gaps, and what happened
- Walk me through the steps your team takes when a high-risk patient needs outreach from identification to closure
- Which specific part of that flow, for example lab reconciliation, scheduling AWVs, or post-discharge follow-up, consumes the most time or causes the most missed opportunities
- Who on your team notices these misses first, and how do they normally escalate them
- Pinpoint a recent patient example where the current workflow failed and explain the downstream impact on revenue, quality score, or patient care
Outcomes that would change the math for you
- What single outcome, expressed in quality measure improvement, savings percent, or AWV lift, would make participation worth the effort for your practice
- Describe how a successful year would look operationally, for example changes to staff time, workflows, and patient touchpoints
- If you were to list your top three financial and clinical priorities for the next 12 months, what are they
- List the top three metrics you already track internally that relate to those priorities
- How confident are you that your current tools can reliably report those metrics for an external payer or ACO audit
- If a pilot showed a 5% reduction in total cost of care while holding quality steady, what internal steps or approvals would have to happen for you to sign within two weeks
Who controls the risk and who executes it
- Assuming your practice considered downside risk, where would the biggest financial exposure fall and why
- Name the roles that must approve participation at your practice and the order in which approvals typically happen
- Who would run care management and daily coordination after go-live, and is that a current role or a new hire
- Describe the current onboarding and clinical training cadence for new staff and how much protected time you can allocate for training in a quarter
- What single governance, reporting, or accountability gap would cause you to pause joining a shared savings arrangement
The other options on your short list
- Across the alternatives you are considering, which approach feels closest to a safe choice and why
- List the vendors, incumbents, or internal build-options you have evaluated so far
- Under what specific conditions would you decide to stay with your current approach instead of switching to an external ACO platform
- Have any internal leaders proposed solving population health capabilities in-house, and if so who would lead that effort
- Estimate one-time and annual costs you expect if you were to build these capabilities internally, even as rough bands
- Point to the alternative that would make you end this evaluation today and tell us what it offers that matters most
Concrete readiness and integration constraints
- Imagine your external data feed failed for two weeks, identify what breaks first and who on your team would raise the alarm
- Enumerate the EHR systems, versions, and whether your practice controls the integration endpoints for each
- Identify the person or role who owns payer IDs, enrollment, and contracting relationships for your practice
- Do you have internal IT or third-party integration support that can manage secure feeds, FHIR/API connections, or HL7 interfaces
- Rate the accessibility and cleanliness of your claims, encounters, and problem list data today
- Name any legal, compliance, or payer approvals that must be obtained before a pilot can start and estimate typical lead times
- Identify the single technical or contractual blocker that would prevent deployment from starting on your preferred timeline
If the pilot works, what accelerates or stops a signature
- Assuming the pilot meets the agreed success metrics, what internal change or decision would be required for you to execute a contract within 30 days
- Select the one success metric that will be most decisive for your leadership, quality measures, cost reduction, or AWV completion
- When do your next budget reviews, board meetings, or partner approval cycles occur that could affect contract timing
- State your internal target window for go-live after contract execution if approvals are completed
- Point to the person or decision that can block the agreement after leadership review and explain what evidence they will need to sign
-
Solution Experience
Walk through how the ACO platform, care coordination model, and practice transformation support deliver the buyer's outcomes using real workflows and scenarios.
Solution Experience
- Solution Experience — Care Model & Platform Walkthrough
- Quick orientation, what happens between signing and go-live
- You confirm the demonstrated analytics and care workflow eliminate the specific gaps and rework you described in Discovery.
- Provide a de-identified sample patient panel (500-1,000 attributed patients) and your current EHR name and version.
- You accept the sample financial example as a realistic path to shared savings with explicit downside controls.
- Confirm the current state and its cost to your practice
- Seller to run a tailored 12-month financial model using the provided panel and deliver the model before the follow-up session.
- Proof — patient identification and gap closure using your scenario
- Seller to execute a short trial feed on a de-identified subset and deliver a care-gap report that mirrors the live walkthrough within two weeks.
- You agree on the evidence and integration steps remaining before a contracting decision.
- Proof — care coordination workflow in your clinic context
- Identify your internal decision criteria and timeline for participation, and share with the seller before the next meeting.
- Proof — financial flow and downside protection example
- Validate the future state
- Agree remaining evidence and next steps
- Solution Experience — Care Model & Platform Walkthrough
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define the included services and modules (analytics, care managers, quality reporting, AWV support), responsibilities, timelines, and measurable acceptance criteria.
Scope Configuration
- EHR Data Integration and Daily Feed
- Risk Stratification and Patient Registry Build
- Deploy Embedded Care Managers
- Care Coordination Workflow Implementation
- Chronic Disease Management Programs
- Annual Wellness Visit Support and Coding
- Quality Measure Abstraction and Reporting
- Claims Processing, Attribution, and Reconciliation
- Shared Savings Calculation and Distribution
- Payer Contracting and Risk Arrangement Management
- Regulatory Compliance and Audit Support
- Performance Dashboards and Monthly Reporting
- Practice Staff Training and Change Management
- Patient Engagement and Outreach Campaigns
Scope Questions
EHR Data Integration and Daily Feed
- Which EHR exchange formats can your current system produce for a daily clinical feed (e.g., Consolidated CDA, FHIR Patient/Encounter, HL7 v2 ADT or ORU)?
- Who on your IT team can provide API credentials and firewall/IP allowlist approvals for daily feeds?
- How many attributed patients should be present in the initial daily feed (estimated count)?
- How will you verify daily feed completeness and timeliness: define the acceptance criteria and monitoring threshold for record arrival (example: >=95% of encounters for attributed patients arrive within 24 hours)?
- When can you provide a test EHR export for initial mapping and what daily window do clinicians expect (e.g., overnight 02:00-06:00)?
- Which patient identifiers must be preserved in the feed to match claims and attribution (for example: medical record number, date of birth, Medicare Beneficiary Identifier, payer member ID)?
Risk Stratification and Patient Registry Build
- Which sources should contribute to the registry build for risk scores: your EHR problem list, problem list crosswalked to ICD codes, historical claims, or lab/medication data?
- Who will own ongoing reconciliation between claims-based risk and EHR problem-list HCCs on your side?
- How many months of claims or encounter history should we include for baseline risk modeling (options reflect data availability)?
- How will you validate the registry build accuracy: state the measurable acceptance threshold for patient-level match and HCC capture (example: registry matches claims attribution >=90% and HCC capture within +/-2%)?
- Identify the clinical flags or cohorts you want prioritized for care management (examples: uncontrolled diabetes with A1c >9%, multiple admissions in 6 months, complex polypharmacy).
- Which risk scoring method do you prefer for stratification (select available inputs you can provide)?
Deploy Embedded Care Managers
- How many full-time equivalent embedded care managers does your practice need on go-live?
- Where will embedded care managers be physically located (options to capture on-site, hybrid, or virtual)?
- Who will supervise embedded care managers in your organization and what is the escalation path for complex clinical issues?
- Which clinical responsibilities should embedded care managers perform at launch (for example: transitional care calls, medication reconciliation, high-risk outreach, AWV scheduling)?
- How will success of embedded care managers be measured in the first 90 days (examples: number of high-risk patients engaged, percent with care plan documented)?
- Do you have space, badge access, and clinical EHR login licenses available for embedded staff at go-live?
Care Coordination Workflow Implementation
- Which care coordination workflows must be implemented first: transitions of care, referrals, post-discharge follow-up, or chronic care huddles?
- Who on your clinical staff currently owns referral routing and follow-up confirmation?
- How many referral partners require an inter-organizational workflow (e.g., hospital discharge teams, skilled nursing facilities)?
- Which EHR workflow artifacts must be populated when care managers open a case (for example: encounter type, problem list entry, care plan template, visit task)?
- Describe the notification channels you require for care team handoffs (examples: EHR in-basket message, secure chat, daily huddle report).
- Will your practice require custom order sets or documentation templates to support the coordination workflows?
Chronic Disease Management Programs
- Which chronic conditions should be in scope for disease management at launch (examples: diabetes with A1c >8, CHF with recent admission, COPD with oxygen therapy)?
- Who on your clinical team will be the clinical lead for each disease program and who will approve clinical protocols?
- How often should program members receive outreach cadence (e.g., weekly calls, monthly monitoring, quarterly check-ins)?
- Which remote monitoring devices or biosensor data do you plan to incorporate into disease management (examples: home BP cuffs, glucometers, weight scales)?
- Identify the clinical thresholds that should trigger escalation to a clinician (examples: A1c >9, systolic BP >160, weight gain >5 lbs in 7 days).
- Do you require program-level patient education materials and care plan templates tailored to your patient population?
Annual Wellness Visit Support and Coding
- Which AWV workflow elements do you need support for: pre-visit outreach, preventive service checklist, Medicare AWV documentation, or billing/coding validation?
- Who will be responsible for scheduling and preparing patients for AWVs within your practice?
- How many AWVs per month do you expect to complete after launch?
- Which AWV billing codes should be validated in your billing system (enter known CPT/G-codes or indicate vendor will supply list)?
- When do you want AWV outreach to start relative to go-live (examples: 30 days before, at go-live, 60 days after)?
- Do you require documentation templates that auto-populate medication lists, preventive screens, and care plan elements for AWVs?
Quality Measure Abstraction and Reporting
- Which quality measure sets do you need reported: Medicare Shared Savings Program measures, Medicare Advantage measure sets, or commercial contract measures?
- Who will provide denominators and any manual chart abstraction evidence if CMS or a payer requires chart-level confirmation?
- How often do you require measure refreshes and reports (monthly, quarterly, annually)?
- How will you verify reported measure compliance and attestation readiness: define the evidence threshold and acceptance criteria for each measure (example: source documentation for 100% of sampled claims)?
- Which EHR chart zones should abstractors reference for measure evidence (examples: problem list, medication list, preventive care flowsheet, lab results)?
- Do you need automated numerator/denominator calculations in the registry or manual abstraction by certified abstractors?
Claims Processing, Attribution, and Reconciliation
- Which payer claim feeds can you provide for reconciliation (options: Medicare FFS claims, Medicare Advantage encounter data, commercial professional claims)?
- Who on your billing team will coordinate remittance and ERA (electronic remittance advice) ingestion for reconciliation?
- How frequently do you want attribution and reconciliation runs (daily, weekly, monthly)?
- Which attribution rule set should we use for initial reconciliation (examples: plurality of primary care E&M visits, historical payer attribution file)?
- Identify the tolerance for reconciliation variance between claims and EHR attribution that you will accept before escalation (example: <3% variance in attributed lives).
- Do you have a preference for automated claim matching keys (for example: member ID + service date + provider NPI) or manual review?
Shared Savings Calculation and Distribution
- Which cost and utilization baselines should we use for shared savings modeling (examples: rolling 12-month claims baseline, payer-specific historical baseline)?
- Who on your finance team will approve the distribution schedule and reporting cadence for shared savings?
- How often should shared savings be calculated and distributed (quarterly, biannually, annually)?
- Which allocation drivers are required for distribution (examples: panel size, performance on quality measures, risk-adjusted savings)?
- Indicate any fixed contractual constraints on distribution (for example: minimum reserve retained by the ACO or holdback percentage).
- Do you require an audit trail and exportable ledger for every shared-savings calculation and payment?
Payer Contracting and Risk Arrangement Management
- Which payer contract types are in scope for this deployment: Medicare Shared Savings Program, Medicare Advantage, commercial gainshare or downside-risk arrangements?
- Who will be the authorized signatory for payer contracting and who will coordinate payer data access on your side?
- How should contract-level performance attribution be rolled up to practice-level reporting (by TIN, by clinic location, by individual NPI)?
- Which contractual risk corridors or floors must the scope model respect when presenting financial projections?
- Will you require assistance with payer data use agreements and Business Associate Agreement (BAA) review?
- Specify any payer-specific requirements for patient notification or opt-out workflows mandated by contract.
-
Mutual Commit
Finalize commercial terms, data-sharing and payer contracting responsibilities, financial risk-sharing structure, and formal approvals required to proceed.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Subscription Order Form
- Data Use & Sharing Agreement
- HIPAA Business Associate Addendum (BAA)
- Financial Risk Sharing Agreement
- Payer Contracting & Agent Authorization
- Provider Participation Agreement
- Fee Schedule & Payment Terms
- Approvals & Signoff Matrix
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Capture concrete readiness facts the deployment depends on — data access, EHR versions, payer IDs, practice champions, and go-live timing confirmations.
Pre-Deployment Questions
Environment and site access
- List the practice site(s) being onboarded (site name and physical address — one line per site).
- Are all onboarded sites on the same production EHR and version?
- If EHRs or versions differ, list each site with its EHR system name and version (one line per site).
Data and configuration
- Is production read-only data access (claims, encounter, clinical feeds) available to the seller for the listed sites? (this determines whether we schedule a production cutover or plan a staging validation)
- Is the attribution list for the target population finalized and shared with the seller?
- Are payer IDs / contract identifiers for the included value-based contracts assigned and available to support payer feeds and reporting?
People and ownership
- Designated practice deployment champion(s) — name, role, and preferred contact (one per line).
- Who will own configuration and field mapping for clinical and billing data between the buyer and the platform?
- If mapping ownership is buyer or shared, list the mapping owner(s) with name, role, and contact info (one per line).
Timing and constraints
- What is the buyer-confirmed target go-live date or window?
- Are there blackout or reporting-freeze windows (e.g., year-end close, MIPS submission, flu clinics) that would prevent a go-live? If yes, we will avoid those dates.
- If yes or TBD above, list blackout windows or scheduling constraints (date ranges and reason).
-
Configuration & Integrations
Record exact configuration values and integration details the deployment team will use — EHR endpoints, secure feed specs, attribution lists, role mappings, and care-management thresholds.
Configuration Details
Environments & Endpoints
- Select the EHR integration transport type the buyer will use (choose one). Options describe the source format the integration will consume: "FHIR R4 API (HTTPS)", "HL7 v2 over MLLP (real-time feeds)", "SFTP file drop (CSV or JSON)", "C-CDA via Direct Secure Messaging", "Custom API (provide production URL below)".
- Enter the production EHR integration endpoint URL or file location the platform will connect to (format: https://... or sftp://... or filename pattern). This exact value will be used in the connector settings.
Authentication & Credential Exchange
- Select the authentication method for the EHR integration (choose one). We will NOT ask for secrets here — provide only non-secret identifiers below and confirm which secrets manager will be used to exchange credentials at kickoff.
- Enter the non-secret integration credential identifier the buyer will provide (e.g., client_id, API key name, integration username, or certificate CN). Do NOT paste secrets here.
Data Feeds & Formats
- Select the primary source of the patient attribution list the platform will consume (choose one). Examples: payer attribution file, EHR panel export, combined deduped file, or manual CSV upload.
- Enter the production location or API endpoint for the attribution feed (format: s3://bucket/path/*.csv or https://api.example.org/attribution or filename pattern). Provide the exact path the build will point at.
Mappings & Feature Options
- Enter the exact EHR role label that should map to the platform role 'Care Manager' (example: "Care Coordinator", "RN Care Manager", exact string as it appears in your EHR). This single value will be used for role mapping.
- Enter the numeric high-risk threshold value used by the platform to mark a patient 'High Risk' (range 0.0–1.0). Default is 0.75 — confirm or provide another numeric value (format: 0.75).
Cutover & Acceptance
- Will the buyer require historical data backfill to the platform as part of go-live? (Default: No)
- Enter the primary role/title that will approve data validation acceptance for go-live (enter role only, e.g., "Practice Manager", "Clinical Director"). This role will be referenced in the deployment acceptance checklist.
-
Deployment
Execute onboarding and practice transformation with sequenced tasks, embedded care manager placement, training, data validation, and go-live checkpoints.
-
-
Success
Monitor outcomes against agreed success criteria (quality measures, cost/savings, AWV completion), run recurring success reviews, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Outcome Measurement (weeks 4-10)
- Acceptance Gate Review (around day 90)
- Quarterly Success Review (ongoing)
Issues & Enhancements
- Circulate the quarterly action plan and schedule the next Quarterly Success Review.
- Publish the go-live issue log with owners and target resolution dates within 48 hours.
- Re-confirm success criteria and owners
- Produce a documented pass/fail decision for each numeric acceptance criterion recorded in the Solution Scope.
- For any non-passing criteria, agree a remediation plan with concrete dates and validation steps.
- Publish the acceptance decision and next steps within 48 hours of the meeting.
- Publish the formal acceptance record showing pass/fail per criterion and any conditional items within 48 hours.
- For failed or conditional criteria, produce a remediation schedule with validation tests and target dates.
- If all criteria pass, transition the tracked items to the Ongoing Quarterly Success Review cadence and update the dashboard access.
- Performance trends and variance analysis
- Confirm whether the ACO quality measure composite and AWV completion rate remain on track against Solution Scope targets.
- Reduce the high-priority issue backlog and assign clear resolution timelines for remaining blockers.
- Prioritize enhancement requests for the next quarter and document the deliverables and timelines.
- Update and publish the issue backlog with status and target resolution dates within 5 business days.
- Publish the prioritized enhancement request list and the planned delivery quarter within 10 business days.
- Set the date and prerequisites for the First Outcome Measurement meeting.
- Confirm feeds, attribution, and access are functioning so first outcome measurement will be valid.
- Produce an agreed open-issue list with owners and target resolution dates.
- Enable read-only access to the outcome dashboard for named buyer users and confirm access within 3 business days.
- Schedule the First Outcome Measurement meeting once all critical blockers are cleared or mitigated.
- Present first-period outcome data
- Determine whether AWV completion rate and risk-adjusted total cost of care per attributed beneficiary are trending toward the Solution Scope targets.
- Agree a prioritized remediation plan with deadlines to close identified gaps before the acceptance gate.
- Confirm the acceptance gate date and the data package required for that meeting.
- Produce a detailed metric drill-down report for AWV completion rate and risk-adjusted total cost per attributed beneficiary within 10 business days.
- Create and publish a remediation plan with discrete tasks and target dates to address each identified root cause.
- Deliver the dataset and data lineage notes that will be used in the Acceptance Gate meeting at least 7 calendar days before that meeting.
- Restate acceptance criteria and numeric targets
- Present outcome data against each criterion
- Deployment and data feed validation
- Persistent issues and blocker burn-down
- Diagnose root causes for any gaps
- Enhancement requests and prioritization
- Early adoption and usage signals
- Document pass or fail per criterion and record decision
- Agree corrective actions and owners
- Agree remediation or realization tracking plan
- Open issues and blockers
- Confirm readiness and timeline to acceptance gate
- Agree quarterly action plan and next checkpoints
- Immediate remediation actions