Payer & Formulary Access
Regulated development and commercialization journeys where clinical, quality, and market access align.
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 the buyer's clinical and financial goals, current formulary processes, stakeholder roles, and success signals related to specialty spend, rebate transparency, prior authorization, and biosimilar adoption.
Discovery Questions
A quick snapshot of your world
- Tell me briefly about your role, the lives you manage, and the pharmacy scope you own
- How many covered lives does your main pharmacy benefit plan include?
- Which formulary management model do you operate today
- When was the last time you changed major formulary rules, and what triggered that change
- Estimate your current annual specialty drug cost trend for the plan
Where the pressure shows up in your budget
- If specialty spend kept growing at the current rate for another year, which budget line or program would you cut first
- Who on your team feels the most day-to-day strain from rising specialty costs
- How often do provider or member complaints about prior authorization processes reach executive leadership
- Describe a recent example where rebate timing or remittance created a material reporting or cash-flow problem for you
- Which of these outcomes would change how leadership views your pharmacy strategy this year
- Which metric, if missed next quarter, would trigger a formal program review in your organization
Where your current processes fall short
- If your prior-authorization and specialty workflows suddenly failed for a week, what downstream problem would materialize first
- Which part of your formulary update cycle feels manual or brittle today
- How transparent is your current rebate reconciliation, on a scale from clear to opaque
- When a biosimilar could lower net cost, where does the project typically stall
- Tell me about the last time a vendor or internal change produced worse-than-expected clinical or financial results, what went wrong
- Which single operational failure would make you pause a new vendor selection immediately
The alternatives you are actively weighing
- Which options have you evaluated or are still considering for managing specialty and rebate complexity
- Has anyone proposed solving these problems with an internal build instead of a partner, and who champions that idea
- Which evidence would convince you to stay with your current approach rather than change vendors
- How recently have you issued an RFP or run a formal vendor review for these services
- What single condition would make you keep your incumbent even if alternatives promised better pricing
If you had a clear win, how would you measure it
- If you could reduce net specialty drug cost by 15% in 12 months, what would you do with the budget savings
- Which of these success signals matters most to your board or executive team
- How quickly do you expect to see measurable movement on those signals if a new program is implemented
- Which acceptance criteria would make a pilot successful enough to expand system-wide
- If the pilot meets your top success signal, what internal approvals would be required to sign a full contract that week
Operational readiness and technical constraints
- Which of these data feeds are currently available to share for an implementation
- Who owns the API or file endpoints the deployment will need, and are they authorized to grant access
- How much engineering bandwidth can you dedicate to integrations in the first 90 days
- Do you have named owners and SLAs for claims file delivery and prior-authorization portal access
- Which regulatory or compliance approvals could delay go-live
- Which single technical or compliance gap would stop the project from starting on your target date
Deal dynamics and decision timeline
- Who are the decision makers that must sign off to move from pilot to full contract
- Which internal metric or event would accelerate the buying decision in the next 90 days
- If a vendor can demonstrate your primary success signal in a pilot, what internal approvals would be needed to sign within two weeks
- How flexible is your desired contract term and pricing structure
- What single business outcome would make leadership push this project to the top of the priority list
Practical next steps and owners
- Who would be the day-to-day point of contact for implementation and integrations
- Which artifacts can you share in the next two weeks to speed scoping
- How soon can your team commit to a technical scoping session
- What would have to change internally for you to be ready to run a pilot within 60 days
- Are there any holidays, contracting blackout periods, or fiscal milestones we should avoid when planning go-live
- If the pilot validated your primary success signal, what would be the single next decision that accelerates full roll-out
-
Solution Experience
Translate the buyer's priorities into concrete workflows showing how the seller's formulary, rebate, clinical, and specialty management practices deliver measurable net-cost and access outcomes.
Solution Experience
- Solution Experience — Formulary and Specialty Workflows
- Confirm the current state and its cost
- You confirm the demonstrated workflow eliminates the manual reconciliation steps and produces an auditable rebate reconciliation tied to claims.
- Run a sample net-cost model using the provided 12 months of de-identified specialty claims and deliver projected net PMPM and savings by therapeutic class.
- Walk an end-to-end formulary-to-claim workflow
- You confirm the demonstrated prior-authorization flow meets your expected turnaround improvements and will reduce provider complaints.
- Prepare an auditable rebate reconciliation example that maps manufacturer remittances to claims adjustments for the scenario reviewed.
- Prove rebate pass-through and reconciliation
- Provide 12 months of de-identified specialty claims, current rebate schedules, and your current PA turnaround targets to enable the sample model and reconciliation.
- You agree on which evidence remains required to finalize scope and commercial terms, for example a claims-backed net-cost model and a test reconciliation.
- Confirm the biosimilar adoption target and the primary stakeholders who will validate clinical equivalency and provider communications.
- Demonstrate the prior-authorization and specialty channel improvements
- Quantify biosimilar adoption impact
- Validate that this matches your needs
- Solution Experience — Formulary and Specialty Workflows
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define scope, modules, responsibilities, key integrations, data exchanges, and measurable acceptance criteria for formulary management, prior authorization, rebates, and specialty channels.
Scope Configuration
- Implement Formulary Tiering and Updates
- Execute New Drug Formulary Additions and Edits
- Negotiate and Administer Manufacturer Rebate Contracts
- Reconcile and Report Rebate Pass-Throughs
- Operate Pharmacy Claims Adjudication and Payments
- Integrate Claims Platform with Buyer Claims Feed
- Deploy Provider Prior Authorization Portal
- Operate Prior Authorization Adjudication and Appeals
- Operate Specialty Pharmacy Dispensing and Fulfillment
- Operate Specialty Pharmacy Clinical Case Management
- Deploy Biosimilar Adoption and Transition Program
- Deliver Drug Utilization and Cost Analytics
- Operate Member Pharmacy Engagement Tools
Scope Questions
Implement Formulary Tiering and Updates
- Which formulary file format do you require for tier updates (NCPDP-formulary CSV, FHIR Formulary, custom CSV/Excel)?
- How often must tiering updates be applied to your live formulary (immediate upon approval, daily, weekly)?
- Who in your team signs off on tier changes and where should approvals be captured (signed PDF, ticket ID, change log entry)?
- Specify the acceptance criteria that will confirm final tier configuration (for example: matched drug list count, zero unmatched NDCs, tier mapping accuracy %) .
- Do you require automated audit trails for tier changes with user, timestamp, and change reason captured?
Execute New Drug Formulary Additions and Edits
- When a new drug review is requested, which supporting documents must accompany the request (FDA label, AMCP dossier, clinical guideline excerpts)?
- Identify where the new drug record should be staged for review (pharmacy clinical review queue, medical policy queue, P&T committee packet).
- Describe how therapeutic equivalents and biosimilar alternatives should be presented in the addition record (mapped NDCs, preferred product flag, substitution policy note).
- Do you require automatic crosswalk of a newly added drug to your existing tier and copay structures?
- Provide the maximum turnaround time you expect between final formulary decision and posting to claims adjudication (in business days).
Negotiate and Administer Manufacturer Rebate Contracts
- What rebate structures are in scope for negotiation (per-unit rebate, gross-to-net chargeback, percentage of WAC)?
- Who will be the contract negotiation contact and who on your team holds signature authority for rebate agreements?
- Define the audit rights and frequency you require for rebate contracts (for example: quarterly ledger review, annual third-party audit).
- Are there existing master rebate agreements or templates we must ingest; if so, will you provide redacted samples?
- Specify any minimum guaranteed rebate thresholds or recoupment clauses that must be preserved in scope.
Reconcile and Report Rebate Pass-Throughs
- Select the remittance reporting format you require for pass-throughs (transaction-level CSV, summarized ledger, ERA/835 mapping).
- Indicate how frequently you require pass-through reconciliation reports (monthly, quarterly, real-time dashboard).
- Identify the owner on your side who will accept reconciliation results and list the evidence you need to validate rebate allocations (for example: remittance file, matched NDC-level claims).
- List any patient-level de-identification or PHI masking rules that must be applied before rebate reports are delivered.
- Provide the tolerance threshold for reconciliation variances that will trigger investigation (dollar amount or percentage).
Operate Pharmacy Claims Adjudication and Payments
- Select the claim formats we must support for adjudication and routing (NCPDP Telecommunication Standard, EDI 837, batch flat file).
- Map the BIN/PCN/Payer ID values and any adjudication field mapping requirements we should configure for your plan.
- Indicate whether you require real-time benefit checks and copay accumulator logic during adjudication.
- Choose your desired claim turnaround SLA for real-time transactions (for example: response within 1 second).
- List the recipients for remittance advice (EDI 835) and describe how ERA fields should map to your accounting ledger.
Integrate Claims Platform with Buyer Claims Feed
- Confirm the feed delivery method you will use for paid pharmacy claims (SFTP flat file, API push with TLS, secure EDI pipeline).
- Attach or describe the sample file schema and a representative sample file you will provide for onboarding (column-level definitions, sample rows).
- Define the acceptance criteria we will use to confirm the feed is integrated and complete (for example: record count match, field-level validation > 99%, test file pass).
- Verify any encrypted transport or certificate exchange requirements (SFTP key exchange, TLS ciphers, client certificate), and provide certificate owner contact.
- Present the named owner on your side for feed delivery and escalation and the expected file cadence at go-live.
Deploy Provider Prior Authorization Portal
- Cite which prior authorization criteria repository the portal should reference (your clinical criteria documents, national criteria, or custom rule set).
- Describe required provider authentication and identity proofing methods for portal access (NPI-based SSO, SAML, OAuth).
- Enumerate the functional test cases we must execute during portal UAT (submit PA, receive 277CA response, attach supporting docs, audit log verification).
- Confirm whether the portal must send real-time PA status callbacks into an EHR/EMR via HL7 2.x or FHIR messages.
- Name the owner who will coordinate provider onboarding and training and state the number of providers to provision at go-live.
Operate Prior Authorization Adjudication and Appeals
- How should prior authorization clinical criteria be versioned and published (criteria ID, effective date, change log)?
- Name the clinical reviewer roles required for PA adjudications and the required credentials (PharmD, RPh, MD specialty).
- Are SLA targets required for PA turnaround by complexity tier (example: standard 24 hours, urgent 2 hours)?
- Detail the documentation fields you expect captured for each adjudication record (decision code, clinical rationale, reviewer ID, supporting documents).
- Include the integration points where PA status messages must be posted back to your provider portals or care management systems (API endpoint, SFTP drop, HL7 feed).
Operate Specialty Pharmacy Dispensing and Fulfillment
- Select which fulfillment channels must be supported for specialty products (ship-to-member home, buy-and-bill provider drop-ship, clinic-administered).
- What temperature-control and cold-chain requirements apply for your specialty products and do you require chain-of-custody documentation or certificate of analysis (COA)?
- Present the accountable pharmacist/licensed entity for dispensing and list required state licenses or DEA numbers we must validate.
- Choose the level of clinical support required for fulfillment coordination (24/7 nurse support, business-hours nurse, pharmacist counseling).
- Estimate target fulfillment timelines by product class (for example: same-day, 1-2 business days) and describe backorder handling rules.
Operate Specialty Pharmacy Clinical Case Management
- Outline required care pathways and case management touchpoints (initial assessment, adherence calls cadence, side-effect monitoring intervals).
- State who should receive case management outcome reports and the desired cadence (monthly, quarterly, ad hoc).
- Approve whether case notes must be pushed to your care management system via FHIR resource or exported as scheduled CSV extracts.
- Recommend KPIs for clinical case management you want tracked (medication adherence %, reduction in hospitalizations, ER visit reduction).
- Include any patient consent and state-specific data-sharing requirements we must follow for outreach and remote monitoring under HIPAA.
Deploy Biosimilar Adoption and Transition Program
- Enumerate which biosimilar substitution policies must be encoded (automatic therapeutic interchange, prescriber notification, patient consent).
- Report how you want biosimilar uptake measured (volume share by NDC, net cost per dose) and provide the uptake targets you expect.
- Cite who will approve substitution exceptions and what clinical justification documentation is required.
- Agree which provider and member communication templates you require for transitions and list approved channels (provider letter, secure portal, email/SMS).
- Detail the tracking fields you require for transitioned patients (original biologic NDC, switch date, biosimilar NDC, reason for switch).
Deliver Drug Utilization and Cost Analytics
- Report which analytics outputs are required at go-live (net drug cost PMPM, utilization by therapeutic class, rebate pass-through reconciliation).
- Estimate acceptable data latency for analytics dashboards (near real-time, daily, weekly).
- State who should receive analytics access and which role-based dashboards to provision (pharmacy director, finance, clinical leadership).
- Upload or indicate whether you require raw data extracts for your internal analytics team and in which formats (Parquet, CSV, SQL).
- Outline baseline measures and benchmarks we should compute for success tracking (for example: net cost PMPM baseline quarter, biosimilar share baseline).
-
Mutual Commit
Finalize commercial and legal terms, confirm data access, governance, timelines, and mutual obligations required to begin implementation.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Order Form / Subscription Agreement
- Data Processing Agreement (DPA) / HIPAA Business Associate Addendum (BAA)
- Service Level Agreement (SLA)
- Change Order Agreement
- Implementation Readiness & Data Access Confirmation
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Capture concrete readiness facts the deployment depends on — claims feeds, prior-authorization portal access, formulary files, named owners, and target timelines.
Pre-Deployment Questions
Environment and access
- Is a production claims feed from the buyer's adjudication engine available for integration?
- If not currently live, what date will the production claims feed be available? (so we can schedule end-to-end testing)
- Is the buyer's prior-authorization portal available for vendor integration/testing (we need test or production access to validate workflows)?
- Are the buyer's master formulary files and tier definitions finalized for import?
- Name the person (role and contact) who will provide formulary files and approve final imports.
Data and configuration
- Have required data feeds and artifacts been identified and assigned owners (claims, paid-claims, prior-auth logs, specialty dispensing, rebate reports)?
- Has the field-mapping approach been chosen (canonical buyer schema vs transform-at-ingest), and who owns final mapping approvals?
- Provide the role and contact for the person who will approve field mappings and data validation results.
- Are required data-sharing and privacy agreements (DPA/BAA/HIPAA) executed for all systems involved?
People and ownership
- Have named owners been assigned for the core deployment workstreams: integrations, configuration, training, and governance?
- List the primary named owner (role and contact) for each critical workstream: integrations, configuration, training, governance, and escalation.
- Who holds final go/no-go authority for cutover decisions?
- If Other, or to confirm the individual, provide the role and contact for the cutover decision authority.
Timing and constraints
- Are there blackout windows or blackout weeks when deployment or cutover cannot occur (e.g., benefit renewals, open enrollment, year-end)?
- If known, list blackout dates or recurring blackout rules (so we can avoid scheduling testing/cutover during them).
- What is the target go-live date for the deployment? (so we can align testing, training, and cutover sequencing)
- Are there regulatory, licensing, or compliance approvals required before go-live (state filings, PBM license, payer sign-offs), and what is their current status?
-
Configuration Details
Lock exact configuration values the deployment team will use — API endpoints, field mappings, formulary tier settings, rebate flow rules, and integration credentials.
Configuration Details
ENVIRONMENTS & ENDPOINTS
- Enter the production API endpoint URL the platform will call for claims lookups and formulary queries (format: https://api.your-domain.com/v1). This value is consumed by the production connector.
- Select the production deployment region the platform should use for data residency and routing (Default: US-East). This controls which data center the deployment targets.
AUTHENTICATION & CREDENTIAL HANDOFF (NO SECRETS)
- Choose the authentication method the platform will use to authenticate to the production API (the deployment will request the non-secret identifier; do NOT paste secrets here).
- Enter the non-secret integration identifier the platform will reference (client_id, integration username, certificate subject, or API key name). Do not paste a secret value; this is the identifier only.
- Where will the secret (client secret / private key / API key) be exchanged from the buyer to the platform? Select the secure channel your organization will use for handoff. (The deployment team will not accept raw secrets via questionnaire.)
CLAIMS FEED & DATA EXCHANGE
- Enter the hostname or full SFTP endpoint where the platform will retrieve production claims feed files (format: sftp.example.com or sftp://sftp.example.com). If you will push via API instead, enter 'api-push'. This value is consumed by the ingestion pipeline.
- Select the production claims feed file format the platform will ingest.
- Provide the exact field name from your claims feed that contains the member identifier used for matching (e.g., subscriber_id, member_num). This mapping is consumed by the ingestion matcher.
- Which drug identifier does your claims/eligibility source use for formulary and analytics mapping? Choose the single canonical code type the deployment should expect.
FORMULARY TIER & REBATE RULES
- Lock the production formulary tier labels mapped to numeric tier values the platform will apply (format: Label=Number, comma-separated). Default example: Preferred=2, Non-Preferred=3, Specialty=4. Edit to match your canonical tier names.
- Select the rebate handling variant the deployment should configure for net-cost calculation and reporting (this determines which reconciliation workflows the platform will enable).
INTEGRATION ACCEPTANCE CRITERIA
- Select the prior-authorization portal integration type to configure in production (this determines which connector and test harness are used).
- Enter the minimum acceptance pass rate for test transactions the deployment must achieve before cutover (percentage). Default is 95.
-
Deployment
Execute the rollout with clear owners, sequencing, training, go-live checkpoints, and provider/member communications to operationalize the solution.
-
-
Success
Track outcomes against agreed success signals (net drug cost, utilization, prior-authorization turnaround, biosimilar uptake), capture learnings, and maintain a shared channel for issues and enhancements.
Success Reviews
- Go-live Health Check
- First Outcomes Measurement
- Acceptance Gate Decision
- Quarterly Success Review
- Annual Outcomes Review
Issues & Enhancements
- Implement the agreed corrective actions with named owners and target dates.
- Confirm that deployment components are live and processing feed transactions without fatal errors.
- Produce a prioritized list of operational blockers with named owners and resolution dates.
- Establish baseline adoption signals to compare against first measurement outputs.
- Distribute a go-live validation report summarizing integration status, data gaps, and immediate fixes.
- Assign and publish owners and target resolution dates for each open blocker.
- Confirm access to the shared issue channel for ongoing tracking and escalation.
- Present first-period outcome data
- Determine whether net drug cost per member per month and prior-authorization average turnaround time are moving toward Solution Scope targets.
- Document root causes for any metric variance and name corrective owners with dates.
- Confirm the acceptance gate schedule and prerequisites for the day-90 decision.
- Deliver a data packet with raw and transformed datasets used for the metric calculations.
- Trend review of net drug cost and PA turnaround
- Update the acceptance gate readiness checklist to reflect outstanding remediation items.
- Restate the numeric acceptance criteria from Solution Scope
- Produce a documented acceptance decision with named buyer signatory for accepted criteria.
- List remediation items for any failed criteria with owners and completion dates.
- Confirm the incumbent decommission plan or read-only retention and the status of legacy data migration.
- Publish the acceptance decision record with signatory details and circulate to stakeholders.
- Create and schedule remediation tasks for unmet criteria with clear owners and deadlines.
- Execute the incumbent wind-down steps or confirm archival completion and update access controls.
- Confirm whether net drug cost per member per month and prior-authorization average turnaround time remain within acceptable variance of Solution Scope targets.
- Close or reassign the top operational blockers and update their resolution timelines.
- Prioritize any enhancement requests that materially affect scoped outcomes and assign owners.
- Owners to resolve the top three operational issues and report status before the next quarterly review.
- Update the shared issue and enhancement channel with current priorities and owners.
- Schedule a focused detailed review if any metric drifts more than the agreed variance from Solution Scope targets.
- Annual performance versus Solution Scope targets
- Document whether the program achieved the annual net drug cost savings and biosimilar uptake targets recorded in Solution Scope.
- Capture a set of documented lessons learned and incorporate them into the operational runbook.
- Assign long-term owners for any persistent issues and confirm the reporting and escalation cadence for the year ahead.
- Publish the annual outcomes report with data, variance analysis, and documented lessons learned.
- Update the operational runbook and reporting templates with agreed changes.
- Assign owners and deadlines for any persistent remediation items not yet closed.
- Reconfirm success criteria and owners
- Compare results to Solution Scope targets
- Deployment and data migration validation
- Lessons learned and process improvements
- Biosimilar uptake and specialty utilization update
- Present outcome data against each criterion
- Root cause diagnosis for gaps
- Open issues and blocker burn-down
- Early adoption signals and usage patterns
- Persistent issues and long-term ownership
- Document pass or fail per criterion and capture signatory
- Agree corrective actions and owners
- Remediation plan for failed or conditional items
- Operational runbook and reporting cadence confirmation
- Blockers and incident triage
- Enhancement requests and prioritization
- Agree immediate remediation actions
- Close outstanding remediation items from the acceptance gate
- Confirm timeline to acceptance gate
- Incumbent wind-down and data disposition
- Agree actions and next check-ins