Pharmacy Cost Management
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
-
Stakeholder & Data Discovery
Align on financial objectives, renewal timing, decision-makers, and the claims and contract data sources required for a granular PBM audit.
Discovery Questions
Why this renewal feels different
- To begin, what specifically pushed you to request an independent PBM audit for this renewal?
- Walk me through the timeline of your current PBM contract, including the expiration date and any auto-renew clauses.
- During the last 12 months, which unexpected pricing or rebate items did finance flag in PBM reports?
- Estimate the portion of annual pharmacy spend you suspect could be recoverable if hidden spread or retained rebates are corrected.
- Who in your organization will be most affected if the audit finds multi-million dollar discrepancies?
- Can you proceed with an audit that completes after the renewal decision, or must findings arrive before signature to be specific?
Where the dollars might be slipping through the cracks
- Estimate the dollar range you consider material for this audit, and describe the financial consequence if that range is confirmed.
- Describe a recent example where PBM reporting left your team unable to reconcile a rebate or generic pricing line item.
- How often do you receive NDC-level detail from the PBM versus aggregated category summaries?
- If the audit identifies specific NDCs with overpayment, what minimum dollar impact would compel you to pursue contract change or negotiation?
- Which savings levers would you prioritize if the audit shows issues, select all that apply.
Who needs to be convinced, and how decisions actually happen
- Who on your leadership team has final approval authority for multi-year PBM contracts and why?
- Tell me how procurement, benefits, and finance currently coordinate during a renewal review, including typical meetings or decision gates.
- Share an example of a past renewal decision where incentives or relationships influenced the outcome and what you learned from it.
- How many formal approvals or committee signoffs are required before a PBM contract is executed?
- If the audit validates your concern about overpayment, who must authorize the change in direction and how quickly can they act?
Where the platform will need to reach, and what that access looks like
- Assume the PBM resists providing NDC-level claims, what fallback sources or tactics could you use to produce the same analysis?
- Identify every system that currently stores pharmacy claims, rebate records, or contract files you can grant access to.
- Which internal owner controls requests to the PBM and has authority to approve NDC-level extracts?
- Describe the formats and cadences of extracts you can provide today, for example daily API, weekly SFTP CSV, or monthly files.
- What single data gap, if unresolved, would prevent completion of an NDC-level audit in time to influence your renewal?
Operational readiness, gating items, and who will do the work
- Identify any legal, security, or governance blockers that could stop data transfer or delay fieldwork beyond your target timeline.
- Confirm whether your legal team requires a separate data use agreement, a security questionnaire, or external counsel review before claims can be shared.
- How many full time equivalents or named individuals can your team dedicate to the audit and platform onboarding over the next 90 days?
- List the compliance frameworks or certifications your security team requires for vendor access, for example encryption standards or SOC reporting.
- Would inability to commit required headcount or to sign data access within 30 days force you to lock current PBM terms?
Risks that can halt the audit or limit its impact
- Name the most likely source of pushback that would lead stakeholders to dismiss audit findings.
- Explain the responses you expect from the PBM when a vendor flags NDC-level pricing or rebate discrepancies.
- How quickly does your legal or procurement team escalate vendor disputes and what typical resolution path do they follow?
- In that case, which governance step would your team take if a PBM refuses to honor audit requests or legal holds, and could that step stop the engagement?
Competitive options you are weighing
- List every alternative you have evaluated or are actively considering, including the incumbent PBM and any internal audit plans.
- Have any internal teams proposed handling this audit without an outside vendor or partner?
- Tell me who originally recommended your current PBM, and whether that party has any ongoing financial relationship that could create perceived bias.
- For you to keep the incumbent PBM rather than change vendors after the audit, what would have to be true?
If the numbers check out, how fast can you move
- Could leadership approve contract changes within 30 days if the audit confirms material overpayment?
- Name the stakeholders who must review and sign commercial changes for a midterm correction versus a full RFP.
- By when do you need final audit data to influence the next negotiation cycle, for example 60 days before renewal?
- What single decision or signature would accelerate a purchase to close within your desired timeline?
- Select how soon you want an initial findings report after the platform receives data.
How we should work together if we move forward
- Before we proceed, what single communication channel and cadence will keep stakeholders informed without creating extra review work?
- Please name the primary point of contact on your side for data, decisions, and issue escalation, and their role.
- How do you prefer draft findings to be delivered, for example an executive summary first, a full NDC-level appendix, or both?
- Would you allow the seller to present preliminary findings to a small cross-functional committee for immediate triage?
- Are there internal approvals already in place to act within six weeks if the audit shows your net cost is materially higher than reported?
-
Solution Experience
Translate the buyer's goals into a shared plan showing how the audit and platform will surface NDC-level discrepancies, rebate pass-through gaps, and ongoing monitoring outcomes.
Solution Experience
- Solution Experience: Audit & Platform Plan
- Confirm the current state and its cost to your team
- You confirm the stated current state and the estimated urgency and dollar-level consequence that make this work mission-critical.
- Provide 12 months of de-identified paid claims, rebate statements, and the current PBM contract excerpts that reference rebates, spread, and MAC guarantees.
- You confirm the demonstrated workflow produces NDC-level findings you trust and that the platform's reconciliation maps to contract language you care about.
- Prove the NDC-level discrepancy detection with a representative claim scenario
- Provide a list of decision-makers, the renewal timeline, and any contract deadlines that would affect fieldwork scheduling.
- You agree to the proposed audit scope, success criteria, and the next-step deliverables and timeline required to keep the work inside the renewal window.
- Show how the platform reconciles rebates and supports ongoing monitoring
- Run a sample NDC-level audit on the provided 90-day claims and deliver a preliminary dollar-level findings summary before the follow-up session.
- Validate that this maps to your need
- Prepare a draft audit scope with measurable NDC-level success criteria and a proposed monitoring cadence for review in the follow-up session.
- Agree next steps, timeline, and responsibilities
- Solution Experience: Audit & Platform Plan
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Engagement Scope
Define the audit deliverables, platform modules, data responsibilities, timelines, and measurable NDC-level success criteria.
Scope Configuration
- Ingest and Normalize Claims Data
- Configure Contract Terms and Guarantees Mapping
- NDC-Level Pricing Reconciliation
- Rebate Pass-Through Reconciliation by Invoice/NDC
- MAC and Spread Compliance Monitoring
- Pricing Benchmark Calibration and Indexing
- NDC-Level Savings Modeling and Projection
- Therapeutic Substitution Implementation
- Biosimilar Conversion Program Execution
- Specialty Drug Site-of-Care Redirection Program
- 340B Identification and Carve-In Optimization
- Recover Overpayments and Claims Remediation Support
- Live Claims Monitoring and Alerting Dashboard
- Platform Training and Operational Handoff
Scope Questions
Ingest and Normalize Claims Data
- Which claim file types can you provide for the baseline period (select all that apply)?
- How many months of adjudicated claim lines do you want included in the baseline audit?
- Do the claim extracts include the following fields: NDC, paid ingredient cost, dispensing fee, days supply, quantity, BIN/PCN, group ID, patient-member ID?
- Who in your organization owns the claims extracts and will approve access (title or role)?
- When do you have a sample claims file available for schema mapping and test ingest?
Configure Contract Terms and Guarantees Mapping
- Provide the contract documents or PDF pages that contain guarantees, pass-through percentages, MAC list clauses, and rebate schedules for the contract to be audited.
- List the contract effective dates and renewal window you want the audit to cover (start date and end date).
- Specify the guarantee types to map at NDC level (select up to three):
- Identify any contract clauses that limit data use, require anonymization, or define independent-audit procedures (attach clause identifiers or page numbers).
- Are contract interpretation disputes expected and who will be the internal contract reviewer for clarification on ambiguous clauses (title or role)?
- Are the following activities out of scope for this engagement (select all that apply)?
NDC-Level Pricing Reconciliation
- Specify which pricing benchmarks you want reconciled against adjudicated paid amounts for each NDC (choose up to two):
- How will you identify invoice-to-claim linkage for reconciliation (select the primary mapping key)?
- Do any of your claims use National Drug Code (NDC) variants or billing NDCs that require mapping to a standard NDC table (RxNorm or internal crosswalk)?
- Indicate the dollar or percentage tolerance for reporting a pricing exception at NDC level (examples: $0.25 per claim, 5% above benchmark).
- What acceptance criteria will confirm the reconciliation baseline is complete (for example, >=98% of adjudicated claim lines ingested and mapped to an NDC)?
Rebate Pass-Through Reconciliation by Invoice/NDC
- Which rebate artifacts can you provide for the contract period (select all that apply)?
- How are rebate payments currently remitted and documented (select one)?
- Specify how manufacturer-level rebate schedules should be mapped to NDCs for pass-through (attach schedule naming convention or example).
- Who in your finance or pharmacy team can confirm reconciliation of rebate remittances to PBM invoices if discrepancies are identified (title or role)?
- Are rebate aggregation or allocation rules in contract wording that restrict NDC-level pass-through attribution (for example, pooled rebates by therapeutic class)?
MAC and Spread Compliance Monitoring
- Which MAC (Maximum Allowable Cost) source should be authoritative for monitoring: contract MAC list, PBM portal MAC, or published third-party MAC?
- How frequently do you receive MAC list updates and do you want those updates ingested automatically for ongoing monitoring?
- Describe any spread pricing disclosure thresholds in the contract that must trigger an alert (for example, spread >$10 per claim or >15% of benchmark).
- Who will be responsible for responding to a MAC appeal timeframe when we flag a MAC violation (title or role)?
- Are there specific pharmacies or pharmacy networks excluded or carved out from MAC/spread guarantees in your contract?
Pricing Benchmark Calibration and Indexing
- Select how you want benchmarks indexed over time for trend comparison:
- Which external benchmark sources do you accept for specialty pricing indexing (select all that apply)?
- Do you want automated alerts when benchmark divergence exceeds a threshold for a high-dollar NDC (specify threshold)?
- Identify any internal pricing overrides or manual adjustments we should apply when calibrating the benchmark (for example, negotiated distributor discounts).
- Are there bench-marking acceptance constraints we must meet for reporting (for example, minimum benchmark coverage of 95% of NDC spend)?
NDC-Level Savings Modeling and Projection
- Choose the time horizon for savings projections:
- Estimate the baseline spend period to use for modeling (select one):
- Describe which intervention scenarios you want modeled at NDC level (select up to three):
- Indicate clinical or operational constraints that must be applied to projected savings (examples: no substitution for narrow therapeutic index drugs, provider consent required).
- Are there reporting slices required for finance review (for example, savings by cost center, by plan tier, or by therapeutic class)?
Therapeutic Substitution Implementation
- Which therapeutic classes do you want targeted first for substitution (provide specific class names or examples)?
- Do you require clinical review and approval workflows mapped into the substitution program (for example pharmacist review, medical director signoff)?
- Specify whether substitution should be implemented via formulary PD/PA edits, prior authorization, or prescriber outreach.
- Who will approve communication templates to prescribers or members for therapeutic substitution (title or role)?
- Are there clinical exclusion lists we must respect (for example, disease states or patient subgroups where substitution is prohibited)?
Biosimilar Conversion Program Execution
- List the biologic molecules in your claims population you want evaluated for biosimilar conversion (attach NDCs or therapeutic names).
- Which legal or state substitution constraints must the program respect (for example, interchangeability rules, prescriber notification laws)?
- Describe provider acceptance risk and whether you want direct provider outreach or incentive alignment included.
- Specify whether step therapy or preferred product edits should be simulated before implementation.
- Are there patient continuity requirements we must enforce (for example, patients on an originator cannot be auto-switched)?
Specialty Drug Site-of-Care Redirection Program
- Which site-of-care shifts are you targeting (select all that apply)?
- Which place-of-service codes or billing indicators should we use to identify site-of-care claims in the data?
- What minimum per-claim cost delta must be present to consider redirection (for example, $500 or 25% differential)?
- Who will approve patient continuity and clinical safety checks before site-of-care changes are recommended (title or role)?
- Are there vendor relationships (home infusion providers, specialty pharmacies) you require we exclude or include in redirection recommendations?
340B Identification and Carve-In Optimization
- Do you have a canonical list of 340B covered entities to match against prescribing NPI or dispensing pharmacy identifiers?
- Which identifiers should be used to detect 340B claims (select all that apply)?
- Describe desired carve-in outcomes (examples: re-price claims, exclude from network, pursue refund) and which outcome is preferred.
- Are there contract clauses specifically addressing 340B that we must map and monitor (attach clause pages if available)?
- Who in your organization will sign off on 340B remediation recommendations (title or role)?
Recover Overpayments and Claims Remediation Support
- Which recoverable event types do you want pursued (select all that apply)?
- Specify any statutory or contractual lookback window we must respect when submitting recovery requests (for example, 12 months).
- How should recovered funds be handled if returned (select one)?
- Describe whether you want us to perform claim-level remediation or provide a prioritized findings package for your team to act on.
-
Agreement & Data Authorization
Finalize commercial terms, SOW, data-access authorization, independence disclosures, and the fee schedule required before fieldwork begins.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Subscription Agreement
- Order Form & Fee Schedule
- Data Access Authorization
- Data Processing Agreement (DPA) / HIPAA Business Associate Addendum (BAA)
- Independence & Conflict of Interest Disclosure
- Service Level Agreement (SLA)
- Change Order Agreement
- Termination & Data Transition Agreement
-
Independent Audit & Findings
Execute the NDC-level claims audit, contract compliance tests, and rebate reconciliation, delivering a dollar-level findings report with prioritized savings and contract risks.
- desired_state
- success_criteria
- decision_readiness
- gaps
- stakeholders
- current_state
- decision_readiness
- gaps
- success_criteria
- desired_state
- current_state
- stakeholders
- stakeholders
- desired_state
- decision_readiness
- current_state
- success_criteria
- gaps
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm datasets, owners, integration endpoints, security requirements, and timing needed to onboard claims into the platform for continuous monitoring.
Pre-Deployment Questions
Environment and site access
- Which claims source systems and environment names will we ingest from? (List each by category: e.g., PBM claims extract - production; benefits admin claims export - production)
- Is a non-production test environment or a representative test extract available for ingestion validation? If yes, select the available type and provide the date it will be accessible.
- Which integration method(s) have been agreed for each source system? (select all that apply so we know what technical handoffs to plan)
Data and configuration
- Which claim‑level datasets and date range will be provided for the audit and ongoing monitoring? (examples: adjudicated claims, paid amounts, remittance records, rebate reports — state earliest month included)
- Has the canonical field‑mapping approach been finalized (which system is the source of truth for NDC, service dates, paid amount, member identifier)?
- Who is the named data owner responsible for approving field mappings and dataset completeness? (provide name, role, and email)
People and ownership
- Who is the primary deployment owner on the buyer side (name, role, email)? This person will be our single point for schedule and approvals.
- Who will own technical integration and access approvals for each source? (select all that apply so we can route technical requests correctly)
- If a third party or 'other' will manage integrations, provide company name and technical contact (name, role, email).
Timing, security, and constraints
- What is the target date to begin claims ingestion into the platform (or earliest acceptable start date)? (so we can schedule cutover windows and resource bookings)
- Are there blackout windows, contract renewal deadlines, or regulatory freeze periods that restrict data transfers or cutovers? (select best answer)
- Which security/compliance gates must be completed before onboarding? (select all that apply — this determines pre-launch deliverables)
- Is the data‑access authorization (signed access release and independence disclosure permitting line‑level claims sharing) executed and available?
-
Configuration Details
Capture exact configuration values the deployment team will use — API credentials, file-transfer settings, pricing benchmark parameters, and contract-rule thresholds.
Configuration Details
Deployment Environments & Endpoints
- Enter the production environment name the platform will use (Default: prod)
- Enter the production API base URL (format: https://api.example.com/)
- Enter the sandbox/staging environment name the platform will use (Default: sandbox)
- Enter the sandbox/staging API base URL (format: https://staging-api.example.com/)
- Select the primary deployment region for the platform instance that will host your data
- If you selected 'Other' for deployment region, specify the region string exactly as your compliance team requires
Authentication & Secrets Exchange
- Select the primary authentication method the platform will use to access buyer endpoints (do not paste secrets here)
- Enter the non-secret API client identifier, integration user name, or key NAME the buyer will provide (example: integration-client-123)
- Enter the name of the person or team that owns the secret/credential in the buyer organization (example: 'Platform Infra Team')
- Select the secure channel you will use to exchange the secret at kickoff (we will not accept the secret in this sheet)
- If you selected 'Other' for secret exchange channel, specify the exact channel name or process
- Select the identity provider type for SSO configuration for platform access
- Enter the IdP metadata URL or issuer URL for the chosen IdP (format: https://idp.example.com/metadata)
File Transfer & Claims Ingestion
- Select the primary claims file delivery method the buyer will use
- If SFTP chosen, enter the SFTP host (format: sftp.example.com). Leave blank if not using SFTP.
- If SFTP chosen, enter the non-secret SFTP username (integration account name). Leave blank if not using SFTP.
- If SFTP chosen, enter the exact directory path where claims files will be dropped (format: /incoming/claims/). Leave blank if not using SFTP.
- If cloud storage chosen, enter the bucket name or storage container path (do not paste credentials)
- Enter the exact claims file naming convention the buyer will use (Default example: claims_<YYYYMMDD>.csv). Provide the literal pattern we should expect.
- Enter the preferred daily ingestion window start time in UTC (Default: 02:00)
- Enter the expected maximum single claims file size in GB the buyer will send (Default: 10)
Canonical Schema & Field Identifiers
- Provide the canonical claims schema document name or URL the platform should validate against (exact filename or URL)
- Enter the exact column header for the NDC field in your claims file (case-sensitive)
- Enter the exact column header for the date-of-service field in your claims file (case-sensitive)
- Enter the exact column header for the member identifier field in your claims file (case-sensitive)
- Enter the exact column header for the paid amount field in your claims file (case-sensitive)
- Enter the exact column header for the quantity/units field in your claims file (case-sensitive)
- Enter the exact column header for the prescriber NPI or ID field (case-sensitive). If not present, enter 'NONE'.
Enrollment & Roster Linkage
- Enter the source system name for your enrollment roster (e.g., 'your HRIS/enrollment system')
- Enter the exact column header used as the member ID in the enrollment roster (case-sensitive)
- Enter the enrollment file delivery method if different from claims (select 'Same as claims' if identical)
- Enter the expected update cadence for the roster file (Default: monthly). Provide one value (e.g., daily/weekly/monthly)
- If you selected 'Other' for roster cadence, specify the cadence text
Pricing Benchmarks & Calibration
- Select which pricing benchmark variant the platform should apply for initial calibration
- If you selected 'Custom benchmark', enter the benchmark file name or canonical URL (do not paste credentials)
- Enter the benchmark currency code to use for calibration (Default: USD)
- If you selected 'Other' for benchmark currency, specify the 3-letter currency code
- Enter the benchmark effective date the platform should apply (format: YYYY-MM-DD)
- Enter the allowed pricing variance percentage that will trigger a pricing discrepancy alert (Default: 2.0)
- Enter the minimum dollars per NDC over the selected lookback period to generate a prioritized finding (Default: 1,000)
- Enter the rebate pass-through shortfall percentage that will flag a rebate alert (Default: 1.0)
Contract Rule Thresholds & Compliance Tests
- Enter the exact contract term name/identifier to be configured for automated tests (use the name from your SOW)
- Enter the MAC guarantee tolerance percentage to allow before flagging noncompliance (Default: 0.5)
- Enter the per-unit spread threshold (currency units) to flag potential spread pricing (Default: 0.01)
- Enter the maximum reconciliation lag in days considered compliant for rebate aggregation (Default: 180)
- Enter the allowed MAC appeal window in days after claim adjudication the platform should enforce (Default: 30)
- Select the numeric rounding rule to apply when comparing prices to contract guarantees
Modules, Feature Toggles & Variants
- Enable the continuous claims monitoring module for live feed evaluation? (Default: Yes)
- Enable the invoice reconciliation module for monthly PBM invoice validation? (Default: Yes)
- Enable the formulary compliance monitoring module? (Default: Yes)
- Enable the site-of-care and specialty routing analysis module? (Default: No)
- Enable the 340B carve-in monitoring module? (Default: No)
- Enable biosimilar conversion tracking and reporting? (Default: No)
Limits, Retention, Locale & Performance
- Enter the data retention period in days for pricing and claims data (Default: 3650)
- Enter the maximum historical months of claims to import during initial onboarding (Default: 36)
- Select the timezone to use for scheduled jobs and reporting timestamps (Default: UTC)
- If you selected 'Other' for timezone, specify the IANA timezone string exactly (example: Pacific/Honolulu)
- Enter the currency code for financial reporting (Default: USD)
- If you selected 'Other' for currency, provide the 3-letter ISO currency code
- Enter the maximum allowed concurrent requests per second the buyer endpoint will accept (numeric)
-
Platform Onboarding & Launch
Execute claims ingestion, validate pricing benchmarks, run initial reconciliations, and transition to live monitoring with clear owners and milestones.
-
-
Outcomes & Ongoing Monitoring
Validate accepted findings and realized savings, schedule recurring audits and review cadences, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Acceptance Gate, Outcomes Certification (around day 90)
- Ongoing Reviews, Monthly Operational Check-in
- Quarterly Business Review
Issues & Enhancements
- Close the top 5 exceptions in the queue and publish updated reconciliation results.
- Execute the incumbent data archival or read-only configuration and publish confirmation of archival completion.
- Open remediation tickets for any failed criteria with specific resolution dates and tracking in the shared channel.
- Review monthly realized savings and reconciliation outcomes
- Validate the monthly realized savings run-rate in dollars is tracking to the quarterly target recorded in Engagement Scope or capture corrective actions if not.
- Reduce the NDC-level discrepancy backlog count month over month and close the highest-dollar exceptions.
- Prioritize and schedule resolution or roadmap placement for outstanding enhancement requests.
- Reconfirm scope and acceptance criteria
- Publish a prioritized enhancement list with estimated delivery quarters for requests raised in the shared channel.
- Confirm next monthly check-in date and any special data extracts required for that meeting.
- Cumulative outcomes versus Engagement Scope targets
- Confirm cumulative realized savings YTD in dollars and rebate pass-through recovery percentage relative to Engagement Scope targets.
- Agree the schedule and scope for the next independent audit and the quarterly executive reporting package.
- Document any contract risk items that require remediation and assign tracking in the shared channel.
- Schedule the next independent audit and publish the audit scope and timeline to the shared workspace.
- Publish the quarterly executive summary including reconciliations, savings realized, and outstanding contract risks.
- Update the enhancement roadmap with committed delivery quarters for items approved in the review.
- Confirm the deployment completed per the deployment checklist and that initial reconciliations have run successfully.
- Document the top 3 operational blockers with agreed remediation actions and target dates.
- Verify that training completion and basic user access are in place for the buyer's finance and clinical reviewers.
- Deliver an errors and exceptions report for the initial ingestion run and a remediation plan for each issue.
- Publish a short how-to note on accessing the reconciliation dashboard and reading NDC-level findings.
- Schedule the First Measurement Review within 4-10 weeks post go-live.
- Present first measurement data
- Validate whether realized savings to date in dollars are on track versus targets recorded in Engagement Scope.
- Confirm the NDC-level discrepancy count and rebate pass-through shortfall dollars are understood and have root-cause owners.
- Agree a corrective action plan with dates that moves the engagement to the Acceptance Gate window.
- Produce a root-cause analysis for the top 5 NDC discrepancies and circulate to the shared channel.
- Adjust pricing benchmark parameters or contract-rule thresholds identified as causes of false positives, and document the change log.
- Prepare the dataset and executive summary required for the Acceptance Gate meeting.
- Restate acceptance criteria from Engagement Scope
- Produce a documented acceptance decision against each numeric target recorded in Engagement Scope.
- Confirm incumbent system is either decommissioned or formally retained read-only and that data archival/migration is complete.
- Agree remediation plan and deadlines for any unmet criteria, with the tracking channel identified.
- Publish the acceptance decision and the outcome summary to the shared workspace for the buyer's finance and clinical reviewers.
- Deployment and ingestion validation
- Contract compliance and risk review
- Present outcome data versus each criterion
- Root-cause diagnosis for metric gaps
- Monitor claim-validation rate and exception queue
- Recurring audit and monitoring cadence confirmation
- Corrective action planning
- Early adoption signals and usage patterns
- Document pass, fail, or conditional per criterion and capture formal acceptance
- Issue and enhancement triage
- Short operational housekeeping
- Confirm timeline to Acceptance Gate
- Incumbent wind-down and data handover
- Open issues, blockers, and remediation plan
- Enhancement roadmap and prioritization
- Agree remediation items and escalation path for any failed criteria