Step Therapy Requirements for Provider-Administered Specialty Medications
Customize your policy alerts
Sign up for all blue cross blue shield - minnesota policy alerts
Know when blue cross blue shield - minnesota releases new policies or updates existing guidance.
Monitor payer policy activity
Defines step therapy requirements for provider-administered specialty drugs listed in the document; applies to providers requesting coverage for these infused or injected specialty medications under Blue Cross Blue Shield - Minnesota.
No material clinical or coverage changes in this revision.
Coverage Criteria
General coverage conditions
Covered when ALL of the following are met
These conditions are required for coverage per the policy preface.
Product-specific step therapy
Step therapy requirements per product (table-based)
See the table rows for exact agent-to-code mappings and any product-specific notes (e.g., 'unless otherwise noted').
Step-based coverage sequencing
Coverage follows the enumerated step levels for each drug/product as listed
Document fragment maps products to numbered steps; clinical failure definitions are not present in these excerpts.
Step position mapping (code-driven)
Coverage is determined by mapped HCPCS/J-code and step position as listed; the document assigns products to step positions 1–4.
Providers must request prior authorization using the HCPCS/J/Q code that corresponds to the mapped step position.
Step therapy groupings (initial agent then alternative options)
Coverage follows step therapy sequences where a specified initial agent (by name and code) must be considered and then one of listed alternative agents may be used.
Multiple groupings appear across the policy where an initial agent is specified and then alternatives are enumerated for subsequent steps.
Step Therapy sequencing
Coverage follows an ordered step-therapy approach: an initial agent followed by specified alternatives at subsequent steps.
Steps are enumerated (commonly 1–5) and coverage for later-step agents is contingent on compliance with the sequence.
Step therapy group sequencing
Coverage follows specified step/group sequences:
Exact clinical indications, failure criteria, and exception rules are distributed across the full policy; these chunks enumerate product and code options per step.
Some listed biosimilars and branded agents are limited to oncology or non‑cosmetic indications as shown in the step tables. For example, several bevacizumab entries include the annotation “For oncology indications only” (Bevacizumab/Alymsys and related rows), and select bevacizumab/biosimilar rows specify non‑cosmetic indication limits. Providers should follow the table annotations when determining allowable indications for these products.
No supplemental notes are explicitly stated in the provided excerpt. Providers should rely on the step therapy table entries, annotations, and the general coverage conditions (provider‑administered specialty drug, medically accepted indication, and dose/frequency/duration consistent with supporting safety/efficacy) when preparing prior authorization requests.
Within these fragments there are no standalone clinical exclusions explicitly listed. The content in the provided chunks is primarily mapping of products to step positions and HCPCS/J‑codes; where exclusions apply they are expressed as inline annotations in the step table rather than as a separate exclusion section.
Certain step entries include targeted exceptions related to pegfilgrastim biosimilars. The table contains wording such as “Does not apply for patients using a pegfilgrastim biosimilar or Rolvedon” (and similar phrasing referencing indications not shared with Fulphila or Neulasta/Neulasta Onpro). When requesting later‑step pegfilgrastim products, providers should confirm whether the specific biosimilar or Rolvedon exceptions apply to the patient’s indication and document accordingly on the authorization.
Step mappings are presented as code‑driven lists and include occasional caveats. Coverage is tied to the HCPCS/J‑code mapped to each step position, and some rows contain annotations that modify applicability (for example, pegfilgrastim rows noting exceptions). Providers must ensure the selected billing code matches the mapped step position and review inline notes in the table for any special caveats affecting that mapping.
The provided segments are dominated by code and agent pairings mapped to numbered step positions; they do not include separate clinical exclusion statements. Readers should treat the listed product names and their mapped HCPCS/Q/J codes as the operative pairing for step sequencing and authorization.
The step tables focus on sequencing and code mappings without explicit clinical exclusion language in these excerpts. Step entries are organized as numbered positions (often followed by “Then one of the following” lists) to indicate allowable agent sequencing; absence of an exclusion statement in these rows does not imply universal coverage outside the listed sequence.
Several table rows in the extracted text include placeholder or blank numbered positions represented as = . or otherwise empty fields. These blank positions indicate unspecified or intentionally empty step slots in the excerpted portion of the table; providers should not assume additional allowed agents for those blank positions and must follow the explicitly listed agents and codes.
The policy requires that use for non‑medically accepted indications, or use with dose, frequency, or duration exceeding the safety and efficacy data for the indication, would not meet the general coverage conditions. Requests should document that the dose, frequency, and duration are consistent with supporting evidence for the medically accepted indication and with the policy’s stated coverage conditions.
Within the provided excerpts there are no explicit statements labeling particular uses or products as not medically necessary. The document does, however, tie coverage to meeting the general coverage conditions (provider‑administered specialty drug, medically accepted indication, and appropriate dose/frequency/duration).
These chunks do not present explicit not medically necessary (NMN) conditions for individual products. The material focuses on code mappings and step positions; NMN determinations may be specified elsewhere in the full policy outside of these excerpts.
The supplied text does not include explicit NMN conditions for the products shown. Coverage in these fragments is organized around step sequencing and code mappings; any NMN rules that apply to specific agents are not present in the provided segments.
Although the document implies that use of agents outside the listed step sequence may be subject to denial, there are no explicit NMN clinical conditions listed in these chunks. Providers should follow the enumerated step sequences and use the specified codes when requesting authorization; non‑sequenced use may require an exception.
No explicit not medically necessary rules for specific products are present in these fragments. The excerpted step lists and code mappings indicate sequencing expectations; the full policy likely contains detailed NMN criteria in sections not included here.
Step Therapy Tables and Mappings
| Requested product (step position) | Provider must document trial of one of the preferred alternatives prior to coverage |
|---|---|
| Alpha-1 Antitrypsin Deficiency, 1 = J0256 | |
| Preferred alternative: Prolastin C (column 2) must be tried and documented |
| Step / Requested product (myasthenia gravis group) | Mapped HCPCS/CPT/J-code(s) and preferred alternatives (must document trial) |
|---|---|
| Generalized Myasthenia Gravis — step 1: Daxxify / Xeomin / Q5152 Q5151 J9256 J9333 J1299 | |
| Step 2: Daxxify / Xeomin with same codes; trial of one listed preferred alternative must be documented | |
| Step 3: J0588 J0589 J9332 J9334 (toxins/infusion codes) — alternative codes listed for later steps |
| Hyaluronic acid derivative (step position) | HCPCS / J-code(s) (provider must reference on authorization) |
|---|---|
| Durolane — step 1 = J7318 | |
| Gel-One — J7318, J7326 (appears in step mappings) | |
| GenVisc 850 — J7318 J7326 J7328 J7320 | |
| Euflexxa — J7325 J7323 | |
| Synvisc / Synvisc One — J7322 J7322 (multiple entries) and related codes J7321 etc. |
| Step position (1–4) | Products / HCPCS-J code groupings (as mapped in policy) |
|---|---|
| Step 1 = products mapped to J7318, J7326, J7328, J7320, J7321, J7322 | |
| Step 2 = alternate products mapped to the same J-codes (J7318–J7332) as listed for later steps | |
| Step 3 = codes shown for third-tier options (e.g., J9332, J9334 referenced for later positions) | |
| Step 4 = entries often blank or not applicable in this fragment |
| Subsequent step position | Alternative products / HCPCS-J codes (document prior step trials) |
|---|---|
| Step 2 = listed alternative viscosupplements and other products mapped to J7318–J7332 (examples: Gel-One, GenVisc 850) | |
| Step 3 = later alternatives or infusion-related codes (J9332, J9334) as shown in mappings | |
| Step 4 = often shown as '.' (no further alternative) in this fragment |
| Step group | Products included (viscosupplements) and infliximab mapping (codes) |
|---|---|
| Viscosupplements group (examples): Monovisc, Orthovisc, Supartz FX, Synvisc, Euflexxa — mapped to J7320–J7332 series | |
| Infliximab products group: infliximab — mapped to J1745 and Q5121 (Avsola, Remicade, Inflectra, Renflexis appear in listings) | |
| Documentation must reference the mapped HCPCS/J-code for the product group when requesting authorization |
| Step / Product family | Representative HCPCS / Q / J codes (partial mapping shown) |
|---|---|
| Infliximab family — examples: J1745 (infliximab), Q5121 (Avsola/Remicade biosimilar Q-code), Q5104/Q5103 (Renflexis/Inflectra) | |
| Pegfilgrastim group — examples: J1449, J9361, Q5130, Q5122, Q5111 (Fylnetra, Nyvepria, Rolvedon, Udenyca listed) | |
| Note: some pegfilgrastim entries include exception language regarding biosimilars or Rolvedon (see mappings) |
| Step position | Example prior agent(s) and codes (pegfilgrastim group — provider must document prior agent) |
|---|---|
| Step 1 = Fylnetra Q5130 (or Nyvepria Q5122) — codes to include on PA request | |
| Step 2 = text notes exceptions: 'Does not apply for patients using a pegfilgrastim biosimilar or Rolvedon for any indication not shared with Fulphila or Neulasta/Neulasta Onpro' — document prior agent as applicable | |
| Step 3 = additional codes referenced (J1449, J9361) for later-step pegfilgrastim products |
| Step position / example | HCPCS / CPT / J-code and prior agent mapping (pegfilgrastim example included) |
|---|---|
| Pegfilgrastim — Fylnetra (Q5130), Nyvepria (Q5122), Rolvedon (J1449) — list corresponding codes on authorization | |
| Providers must document prior use of listed alternatives (e.g., Neulasta/Neulasta Onpro, Fulphila) where the mapping indicates prior-step requirement |
| Therapeutic area / step group | Mapped drugs and representative codes (MS, NMOSD, PNH, lysosomal storage examples) |
|---|---|
| Multiple Sclerosis / NMOSD — mapped agents: J3385, J0202, J2351, Q5134, Q5120 (examples appear in MS infusions lists) | |
| Lysosomal storage disorder agents — Cerezyme, Elelyso, VPRIV mapped to codes J2506, J1786, J3060, J2329, J2350 in step lists | |
| PNH / complement inhibitors — Soliris / Ultomiris mapped to J1299, J1303, Q5151/Q5152 in grouped sequences |
| Enumerated step position (initial agent) | Then one of the following (allowed alternatives) — product names and codes |
|---|---|
| Retinal agents — initial: Avastin / J9035 (Avastin listed with Q/J crosswalks) — Then one of the following: Byooviz, Eylea, Eylea HD, Lucentis (codes Q5124, J9035/C9257, J0178, J0177 shown) | |
| PNH / complement agents — initial: Uplizna / J1823 and Soliris / J1299 — Then one of the following: related complement/retinal agents as listed |
| Step number | Agent/group (initial) and enumerated allowed alternatives (codes) |
|---|---|
| Step 1 = Avastin (J0179 / J9035/C9257) — Then one of the following: Byooviz, Eylea, Eylea HD, Lucentis (Q5124, J0178, J0177) as mapped | |
| Step 2 = subsequent agents listed (Beovu, Cimerli, Enzeevu, Eydenzelt) with Q/J codes Q5149, J2778, Q5153 etc.; providers must document prior trial of step 1 agents | |
| Step 3–5 = additional listed alternatives (Visudyne, Yesafili and others) with associated codes; some later positions are shown as '.' (no entry) |
| Subsequent steps (2–5) | Agents and HCPCS/CPT/Q/J codes (providers must document progression) |
|---|---|
| Step 2 examples = Beovu / J0179, Cimerli / Q5128, Enzeevu / Q5149, Vabysmo / Q5150; mappings indicate 'Then one of the following' with listed codes | |
| Step 3 examples = Visudyne (J3396), Yesafili (Q5155) and others — codes must be used on authorization requests | |
| Steps 4–5 = some entries blank; when listed, include the mapped J/Q codes as shown in the policy |
HCPCS / CPT / Q-Code Mappings
| Q5152 | HCPCS code listed in step sequences |
| Q5151 | HCPCS code listed in step sequences |
| J9256 | J-code listed in step sequences |
| J9333 | J-code listed in step sequences |
| J1299 | J-code listed in step sequences |
| J1303 | J-code listed in step sequences |
| J1823 | J-code listed in step sequences |
| J9332 | J-code listed in step sequences |
| J9334 | J-code listed in step sequences |
| J0588 | J-code listed in step sequences |
| J7318 | Hyaluronic acid derivative code (Durolane, Gel-One, etc.) |
| J7326 | Hyaluronic acid derivative code |
| J7328 | Hyaluronic acid derivative code |
| J7320 | Hyaluronic acid derivative code |
| J7321 | Hyaluronic acid derivative code |
| J7322 | Hyaluronic acid derivative code |
| J7323 | Hyaluronic acid derivative code |
| J7325 | Hyaluronic acid derivative code (Euflexxa) |
| J7327 | Hyaluronic acid derivative code |
| J1299 | J1299 (as listed in document) |
| J1303 | J1303 (as listed in document) |
| J1823 | J1823 (as listed in document) |
| J7318 | J7318 (as listed in document) |
| J7326 | J7326 (as listed in document) |
| J7328 | J7328 (as listed in document) |
| J7320 | J7320 (as listed in document) |
| J7321 | J7321 (as listed in document) |
| J7322 | J7322 (as listed in document) |
| J7325 | J7325 (as listed in document) |
| J1745 | infliximab |
| Q5121 | infliximab product HCPCS (biosimilars/reference listed) |
| Q5104 | infliximab product HCPCS (Renflexis referenced) |
| Q5103 | infliximab HCPCS (Inflectra referenced) |
| J1748 | infliximab (appears with Zymfentra) |
| J7321 | viscosupplementation/related product code listed in segment |
| J7322 | viscosupplementation/related product code listed in segment |
| J7323 | Euflexxa (viscosupplementation) code reference |
| J7324 | viscosupplementation/related product code listed |
| J7327 | Monovisc or related viscosupplementation code reference |
| J3385 | appears in Lysosomal Storage Disorder / MS / NMOSD mappings |
| J0202 | appears in Multiple Sclerosis / NMOSD mappings |
| J2351 | appears in Multiple Sclerosis / NMOSD / PNH mappings |
| Q5134 | appears in MS/infused agent mappings |
| Q5120 | appears in MS/infused agent mappings |
| J3060 | appears in lysosomal storage disorder mappings |
| J0179 | listed product code in document |
| J1303 | listed product code in document |
| J1307 | listed product code in document |
| J1299 | listed product code in document |
| J1823 | listed product code in document |
| J2778 | listed product code in document |
| J2779 | listed product code in document |
| J2777 | listed product code in document |
| J9035 | listed product code in document |
| C9257 | listed product code in document |
| J0179 | Injection, ophthalmic anti-VEGF (listed in document) |
| J2778 | Beovu (or listed agent) J-code as referenced |
| Q5150 | Q-code referenced for Vabysmo |
| Q5128 | Q-code referenced for Cimerli or similar |
| Q5149 | Q-code referenced for listed ophthalmic agents |
| Q5170 | Q-code referenced for Yesafili/related |
| Q5153 | Q-code referenced |
| Q5147 | Q-code referenced |
| J2779 | J-code referenced |
| J0178 | J-code referenced |
| Q5153 | Q-code listed with Visudyne/Yesafili group |
| Q5147 | Q-code listed with Visudyne/Yesafili group |
| J2779 | J-code listed with Visudyne/Yesafili group |
| J2777 | J-code listed with Visudyne/Yesafili group |
| J3396 | J-code listed with Visudyne/Yesafili group |
| Q5155 | Q-code listed with Visudyne/Yesafili group |
| Q5123 | Riabni / rituximab products code |
| J2778 | Lucentis-associated J-code |
| J0178 | Avastin-associated J-code |
| J0177 | Avastin-associated J-code |
Provider Actions, Prior Authorization & Documentation
Prior authorization required; include affected HCPCS/CPT/Q/J codes
Prior authorization is required for medications listed in the step therapy table; requesters must document and request using the applicable HCPCS/CPT/Q/J codes associated with the requested product per the table.
Request authorization using the correct drug/service code(s)
Prior authorization is organized around the listed HCPCS/CPT/J‑codes for each drug and step; providers must request authorization using the specific code(s) shown for the product and step.
Use the mapped HCPCS/J-code for PA tied to step position
When requesting prior authorization, use the HCPCS/J-code that corresponds to the listed product and its step position in the policy's step therapy mappings.
Reference the listed HCPCS/Q/J codes on the authorization
Authorization requests should reference the listed HCPCS/J‑ and Q‑codes that correspond to the provider‑administered specialty product being requested to demonstrate alignment with the step table.
PA tied to specific administration/product codes
Prior authorization and step‑therapy determinations reference specific HCPCS/CPT/J‑codes for provider‑administered biologics and related products; include those administration/product codes on PA requests.
PA must include code-to-drug mapping
Prior authorization must reflect the specific HCPCS/CPT/J‑code(s) mapped to the requested specialty medication per the step therapy table; submit the code that identifies the exact product being requested.
Include the specified product HCPCS/CPT/Q codes on PA
Prior authorization is organized around the specific HCPCS/CPT/Q‑codes listed for each agent; requests should include the exact code for the administered product as shown in the table.
Code‑linked PA: administered drug must match approved code and step
Prior authorization requires that the administered drug matches an approved HCPCS/CPT/J/Q code and the step sequence in the policy; the PA should demonstrate that the product and code align with the listed step mapping.
PA must use the listed drug HCPCS/CPT/Q/J codes
Prior authorization is organized around the listed J‑, Q‑ and other HCPCS/CPT codes for each specialty product grouping; providers must request authorization using those listed codes.
Step therapy requirement: trial preferred alternative(s) first
Providers must trial one or more preferred alternative agent(s) listed in the table (column 2) prior to coverage of the requested product, unless otherwise noted in the table.
- The table states 'Must try one of the following unless otherwise noted' for requested products and lists preferred alternatives by name and code.
Follow numbered step‑therapy sequences by drug and code
The document lists numbered step‑therapy sequences (1–4, sometimes up to 5) for multiple provider‑administered specialty medications; authorization assessment follows the sequence and associated codes.
- Myasthenia gravis, viscosupplement, infliximab and other product families are presented with explicit step positions and codes.
Step therapy enforced via HCPCS/J‑code to step mapping
Step therapy is enforced by mapping specific HCPCS/J‑codes to step positions (1–4); providers must follow the mapped code‑to‑step relationships when requesting later‑step agents.
Step product groups enumerated (viscosupplements & infliximab)
Product groups such as viscosupplements and infliximab products are enumerated as step therapy product groups; providers should reference the group listings and associated codes when planning therapy.
Step listings present (product step positions shown, details partial)
Step positions are enumerated for many products (notably infliximab family and viscosupplements); the table shows products placed in positions 1–4 (details partial in this segment).
Follow drug-to-code step mappings as shown
Providers must follow the drug‑to‑code step mappings shown: each listed drug or drug group is associated with one or more step positions and specific HCPCS/CPT/J‑codes; use the mapped codes for authorization.
- Many mapped groups reference prior agents (e.g., Neulasta/Neulasta Onpro, Fulphila) and list corresponding J/Q codes to show sequencing.
Follow enumerated step therapy sequences (initial agent then alternatives)
Providers must follow the enumerated step therapy pairings where an initial agent is followed by 'Then one of the following' alternatives; the table lists initial agents and allowed alternatives for subsequent steps.
- Examples include Avastin/Lucentis groups where Avastin is followed by 'Then one of the following' lists (Byooviz, Eylea, Lucentis, etc.).
Adhere to enumerated step sequences; document prior steps
Providers must follow the step therapy sequencing where an initial agent (often Avastin or another lower‑step drug) is followed by listed alternatives at subsequent steps; authorization of later‑step agents requires documentation of prior steps.
- Ophthalmic groups list Avastin and then 'one of the following' alternatives with specific J/Q codes for each step position.
Step therapy sequencing follows code‑group based groupings
Coverage follows step therapy groupings where one listed product/code may be required prior to coverage of another; providers must reference the grouped code listings when requesting coverage.
- Grouped examples include rituximab/trastuzumab and ophthalmic biologic families with multi‑step code groupings.
Document provider‑administration, indication, and dosing justification
Documentation must demonstrate the medication is a provider‑administered specialty drug used for a medically accepted indication, and that dose, frequency, and duration align with the safety and efficacy data supporting that indication.
- The policy preface requires the drug be provider‑administered and used for a medically accepted indication with supported dose/frequency/duration.
Reference specific HCPCS/CPT/J‑code(s) and step number on PA
Prior authorization requests should reference the specific HCPCS/CPT/J‑code(s) corresponding to the drug and the step number to demonstrate adherence to the step therapy sequence.
- Include the step number from the table alongside the HCPCS/J‑code(s) listed for the product.
Submit the product‑specific HCPCS/J‑code on the authorization
Submit the appropriate HCPCS/J‑code that corresponds to the specific product being requested; authorizations should identify the exact product code rather than a generic or alternate code.
Pair product name with the listed HCPCS J/Q codes on submissions
Use product names paired with their HCPCS J‑ and Q‑codes from the table when completing authorizations and billing to ensure requests match the policy's mappings.
Ensure billing/authorization reference the policy's specific product code
Billing and authorization must reference the specific HCPCS/CPT/J‑code for the administered product as listed in the policy's step tables to support coverage determination.
Present drug name/group with corresponding HCPCS/CPT/J code(s)
Providers must present the drug name/group and corresponding HCPCS/CPT/J‑code(s) that match the step therapy mapping when requesting authorization or submitting claims.
- The policy repeatedly requires aligning the drug/group name with the listed codes to match step positions.
Document prior agent(s) tried per 'Then one of the following' lists
Document the chosen agent and, where relevant, the prior agent(s) tried consistent with the 'Then one of the following' step lists to demonstrate that required prior steps were attempted.
- Ophthalmic and other groups show 'Then one of the following' lists—document prior agents accordingly.
Reference specific HCPCS/CPT/J/Q codes on claims/authorizations
Claims and authorizations must reference the specific HCPCS/CPT/J/Q codes corresponding to the administered specialty medication as listed in the step sequences.
Reference the policy's listed HCPCS/J/Q codes when seeking authorization
Provider authorization requests should reference the exact HCPCS/J‑codes or Q‑codes listed for the specialty product(s) when seeking authorization to ensure alignment with the policy.
Denial risk if drug is not provider‑administered, indication unsupported, or dosing exceeds evidence
Requests may be denied if the medication is not a provider‑administered specialty drug, is not being used for a medically accepted indication, or if the requested dose/frequency/duration exceed supported safety and efficacy data.
- The policy preface lists these three primary coverage conditions as required for coverage.
Denial risk for mismatched HCPCS/CPT/J‑code and step sequence
Coverage may be determined by whether the requested HCPCS/CPT/J‑codes and the drug sequence align with the step entries listed for the condition; mismatched code or step alignment may lead to denial.
Denial risk if code does not match mapped step position/product
Submissions using HCPCS/CPT/J‑codes that do not match the mapped step position or product may be subject to denial if they do not conform to the policy's step mappings.
Risk of processing discrepancies if product/code not matched (implicit denial risk)
The table lists products and codes without explicit denial rules in every chunk, but failure to match products/codes to the authorization request could lead to coding or authorization discrepancies.
- Where explicit denial language is not repeated, providers should still align requests to the listed mappings to avoid processing issues.
Claims may be subject to step therapy review when using listed HCPCS/CPT/J‑codes
Claims for listed provider‑administered specialty medications submitted using the listed HCPCS/CPT/J‑codes could be subject to step therapy review or processing aligned with the step listings shown in the policy.
- Infliximab and viscosupplement groups show code lists that are used to determine step therapy processing.
Nonconforming code or step mapping may trigger denial
Requests that do not follow the documented step mappings between drug/group and listed HCPCS/CPT/J‑codes may be subject to step therapy requirements and denial if prior steps are not met.
- The policy indicates prior‑agent requirements for many groups (e.g., pegfilgrastim, MS, NMOSD) and expects adherence to sequencing.
Denial risk for nonconforming step sequence or not using listed substitutes
Failure to follow the indicated step therapy sequence or to use one of the listed substitute agents (for groups that list 'Then one of the following') may result in denial unless an approved exception is obtained.
- Several 'Then one of the following' groupings require documentation of prior agents; exceptions are available per the plan's determination process.
Denial risk for use of non‑sequenced agents
Use of a non‑step agent or failure to follow the listed sequencing of agents as presented (e.g., not following 'Then one of the following' sequences) may trigger denial of coverage.
- Ophthalmic and biologic groups explicitly list ordered step sequences; do not substitute agents outside those lists without an exception.
Denial risk if step therapy not met — exception process available
Failure to follow the plan's step therapy requirements may result in denial unless an exception is requested and approved through the organization's determination process.
- Members may request an exception to the step therapy requirement; such requests are reviewed through the plan's determination process.
Background
This policy addresses provider‑administered specialty medications across multiple indications and links coverage to both clinical and coding conditions. Coverage requires that the medication be a provider‑administered specialty drug, be used for a medically accepted indication, and that the dose, frequency, and duration align with supporting safety and efficacy data. The document enforces step therapy sequencing by mapping specific HCPCS/J/Q codes to numbered step positions; prior authorization and claims must reference the mapped code and demonstrate adherence to the step requirements where applicable.
Definitions
Initial Therapy Criteria
Initial therapy / step 1
Initial step requirement
Table rows enumerate the specific preferred alternatives and associated codes that meet the initial step requirement.
Initial therapy (code-mapped)
Products are assigned to step positions (1–4) as listed; step 1 products are initial step candidates.
Chunks list multiple products mapped to numeric step positions; prior authorization must reference the mapped code and step.
Initial step positions (partial)
Step positions indicated for listed products (partial data)
This is a partial listing of step positions and code mappings.
Initial step entries
Many groupings list an initial agent position followed by alternatives.
Repeated across multiple product groups; up to five enumerated positions may appear.
Initial therapy (examples)
Initial step often lists Avastin or a specified first-line agent
Examples in the policy show Avastin and other agents used as initial step entries before permitted alternatives are listed.
Initial step options (product/code lists)
Initial step-group listings in this fragment:
Specific indication‑based initial therapy clinical criteria are not present in these chunks; use the code/step mapping when requesting authorization.
Site of Care
Biosimilar Notes and Mappings
OpenPayer is powered by Trek Health's payer performance platform. Trek continuously ingests, validates, and normalizes Transparency in Coverage data alongside payer policies and other commercial payer data to create a structured payer intelligence foundation. OpenPayer uses this foundation to deliver personalized search results, dynamically generated policy pages, and tailored policy monitoring based on each user's payers, specialties, billing codes, and areas of interest. The same intelligence powers broader payer performance workflows, including reimbursement benchmarking, contract evaluation, payer negotiations, and financial decision-making.