Blue Shield Promise at a glance
| Legal name | Blue Shield of California Promise Health Plan |
|---|---|
| Also known as | BSC Promise, Blue Shield Promise Health Plan |
| Category | Medicaid MCO |
| Parent organization | Blue Shield of California |
| Claims payer ID | Promise’s current claims page lists C1SCA for Office Ally submissions. The September 2024 Promise 837 guide separately uses 954468482 for direct ISA08/GS03 and payer 2010BB NM109. Verify the configured route; neither establishes a universal BS001 claim identifier. |
| Eligibility (270/271) payer ID | The joint January 2025 Blue Shield/Promise 270 guide uses direct inbound ISA08 940360524 and GS03 270-940360524, not the Promise 837 value. Generic eligibility BS001 is not established by these sources. |
| ERA (835) payer ID | No single all-product identifier established in this registry; see source findings and verify the member product and transaction separately. Clearinghouse-specific: The July 2026 manual and current claims page describe Office Ally/default or selected approved-clearinghouse ERA enrollment. They do not establish BS001 as one universal 835 routing ID. Preserve the separate enrollment workflow. |
| NAIC company code | Not established in this registry |
| States covered | California |
| Members covered | ~450k members |
| Provider resource entry point | https://www.blueshieldca.com/en/bsp/providers/working-with-us/electronic-claims-and-encounters |
| Provider phone | 1-800-468-9935800-468-9935 is Promise Provider Services, distinct from Blue Shield general provider support and EDI technical support. Confirm the member product and responsible administrator. |
Always verify claims-routing details against the member ID card and the payer's current EDI companion guide before submission.
Timely filing & appeals for Blue Shield Promise
The July 2026 Promise Medi-Cal manual gives 180 days from service for initial claims, with specified delayed-filing exceptions. Other Health Coverage has a separate 90-calendar-day period from that plan’s payment, and additional outer limits/exceptions are described in section 14.1. Confirm the agreement and claim circumstances; do not apply a universal 365-day initial limit.
| Submission type | Window |
|---|---|
| Initial claim reference | Medi-Cal initial claims: 180 days; exceptions apply |
| Out-of-network initial claim | Verify the member's plan and applicable out-of-network rules |
| Secondary / coordination of benefits | Verify the allowed window and start event; a primary EOB does not automatically restart filing |
| Corrected claim | Verify correction instructions; do not substitute an appeal deadline |
| Reconsideration / appeal | Use the applicable denial or decision notice and the process below |
This registry has not established a payer-specific appeal ladder for Blue Shield Promise. Use the denial notice, plan document, provider agreement, or jurisdictional rule to assign the correct route and deadline. Missing registry evidence does not mean appeal rights are unavailable.
Source: Blue Shield Promise provider policy. Always confirm before disputing a TFL denial — payer policies are versioned and product-specific.
Prior authorization with Blue Shield Promise
Decision deadlines depend on the product, service and urgency. CMS-0057-F generally starts its decision-timeframe requirements in 2026 for Medicare Advantage, Medicaid and CHIP payers subject to the rule: seven calendar days for standard requests and 72 hours for expedited requests. Those requirements exclude drug authorizations and QHP issuers on the federally facilitated exchanges. Other plans, state rules and permitted extensions can differ. Check the applicable policy; a decision deadline is not a guarantee of approval.
CMS-0057-F decision-timeframe requirements and exclusions
Verify Blue Shield Promise electronic claims (837), eligibility (270/271), remittance (835) and authorization (278) separately for the member product and clearinghouse. Registry flags and routing references are not current transaction-complete approval. Confirm the companion guide, enrollment and applicable source findings below. A blank or unverified field does not establish that the transaction is unavailable. Authorization requirements and submission channels depend on the product, service and delegated reviewer. Verify the applicable policy before scheduling; a portal listing is not proof of X12 278 connectivity.
This registry does not provide a current prior-authorization code list for Blue Shield Promise. Start with the provider resources or the policy documents below, then confirm the applicable product, service and effective date. A resource link does not establish that a live code-lookup tool is available.
- → https://www.blueshieldca.com/en/provider/about-pc/contact-us/contacts-claims
- → https://www.blueshieldca.com/en/bsp/providers/working-with-us/electronic-claims-and-encounters
- → https://www.blueshieldca.com/en/bsp/providers/working-with-us/edi-companion-guides
- → https://www.blueshieldca.com/content/dam/bsca/en/promise/docs/Blue-Shield-Promise-5010-Companion-Guide.pdf
- → https://www.blueshieldca.com/content/dam/bsca/en/promise/docs/270-271-EDI-Companion-Guide.pdf
- → https://www.blueshieldca.com/content/dam/bsca/en/provider/docs/7-26-A51765-BSCPHP-Medi-Cal-Manual.pdf
- → https://www.blueshieldca.com/en/bsp/providers/policies-guidelines-standards-forms/provider-manuals
Top denial reasons for Blue Shield Promise
Per-payer denial benchmarks publish here once the QuickIntell anonymized ETL pipeline ingests sufficient Blue Shield Promise volume. Until then, see the broader CARC reference for industry-wide remediation guides.
Electronic claims, eligibility & ERA
| Transaction | Registry indication — not verification | Routing reference |
|---|---|---|
| 837P / 837I claims | Listed in registry; verify current scope | Promise’s current claims page lists C1SCA for Office Ally submissions. The September 2024 Promise 837 guide separately uses 954468482 for direct ISA08/GS03 and payer 2010BB NM109. Verify the configured route; neither establishes a universal BS001 claim identifier. |
| 270 / 271 eligibility | Listed in registry; verify current scope | The joint January 2025 Blue Shield/Promise 270 guide uses direct inbound ISA08 940360524 and GS03 270-940360524, not the Promise 837 value. Generic eligibility BS001 is not established by these sources. |
| 278 prior authorization | Listed in registry; verify current scope | Verify X12 278 routing separately |
| 835 ERA | Verify support and enrollment separately | No single all-product identifier established in this registry; see source findings and verify the member product and transaction separately. Clearinghouse-specific: The July 2026 manual and current claims page describe Office Ally/default or selected approved-clearinghouse ERA enrollment. They do not establish BS001 as one universal 835 routing ID. Preserve the separate enrollment workflow. |
Payer IDs vary by clearinghouse — confirm against your clearinghouse payer list (Availity, Change Healthcare/Optum, Waystar) before configuring submitter routing.
What revenue cycle teams should verify before submitting claims
- Office Ally claim routing, direct 837 payer identifiers and direct 270 envelope values have different roles.
- July 2026 is the in-force manual reviewed here; January 2027 preview material is not applied as current policy.
Source checks and remaining limits
The latest partial comparison is dated . Retained earlier findings keep their original dates below. This is a partial source check, not a whole-page, clinical or legal review. It does not refresh the legacy review date above.
field_status, provider_phone — Claims contacts
Source comparison: 2026-09-18
Source scope: Contact/transaction scope only; see record findings and exact source locator. Locator: Blue Shield and Promise provider-services headings; EDI Department; Blue Card/FEP contacts Version: Undated public HTML opened with web tool 2026-09-18; do not infer policy effective date from retrieval Retrieval: 200; independent_peer_primary_public_source_read. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for field_status, provider_phone — claims contactsera_payer_id, payer_ids, payer_ids.claims, payer_ids.eligibility, payer_ids.era, transaction_scope — Managing Electronic Claims and Encounters
Source comparison: 2026-09-18
Source scope: Contact/transaction scope only; see record findings and exact source locator. Locator: Office Ally C1SCA claim routing; approved-clearinghouse ERA enrollment Version: Undated public HTML opened with web tool 2026-09-18; do not infer policy effective date from retrieval Retrieval: 200; independent_peer_primary_public_source_read. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for era_payer_id, payer_ids, payer_ids.claims, payer_ids.eligibility, payer_ids.era, transaction_scope — managing electronic claims and encountersSource version and inspection boundary — Promise EDI Companion Guides
Source comparison: 2026-09-18
Source scope: Contact/transaction scope only; see record findings and exact source locator. Locator: Current linked Promise837 and joint BSC/Promise 270 guide Version: Undated public HTML opened with web tool 2026-09-18; do not infer policy effective date from retrieval Retrieval: 200; independent_peer_primary_public_source_read. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for source version and inspection boundary — promise edi companion guidesera_payer_id, payer_ids, payer_ids.claims, payer_ids.eligibility, payer_ids.era, transaction_scope — Blue Shield of California Promise 5010Companion Guide
Source comparison: 2026-09-18
Source scope: Contact/transaction scope only; see record findings and exact source locator. Locator: PDF pages 12/27 ISA08/GS03;PDF pages 16/31 payer2010BBNM109 Version: v2024.02;effective/released September 12, 2024 Retrieval: see source-specific inspection evidence; independent_peer_primary_public_source_read. PyMuPDF rendered PNGs inspected with view_image; other cited pages text extracted only Not a whole-document review. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for era_payer_id, payer_ids, payer_ids.claims, payer_ids.eligibility, payer_ids.era, transaction_scope — blue shield of california promise 5010companion guideera_payer_id, payer_ids, payer_ids.claims, payer_ids.eligibility, payer_ids.era, transaction_scope — Blue Shield of California AND Promise 270/271 Companion Guide
Source comparison: 2026-09-18
Source scope: Contact/transaction scope only; see record findings and exact source locator. Locator: physical pages 1/4/11/14;47 PDF pages consists of 18 main +29 appendix/cover pages Version: v2.5 January 14, 2025 Retrieval: see source-specific inspection evidence; independent_peer_primary_public_source_read. PyMuPDF rendered PNGs inspected with view_image; other cited pages text extracted only Not a whole-document review. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for era_payer_id, payer_ids, payer_ids.claims, payer_ids.eligibility, payer_ids.era, transaction_scope — blue shield of california and promise 270/271 companion guidefiling_rule, timely_filing_days, timely_filing_source_url — Blue Shield Promise Medi-Cal Provider Manual
Source comparison: 2026-09-18
Source scope: Initial 180 days from service, with specified delayed-filing/OHC exceptions. ERA uses approved-clearinghouse enrollment; no generic BS001 mapping is certified. Locator: Physical PDF 308–309§14p2–3 Version: July 2026; January 2027preview not applied. Retrieval: content_read; actual_public_pdf_download_text_and_scoped_visual_review. These pages actually rendered and inspected with view_image; other pages text-only or not reviewed. Not a whole-document review. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for filing_rule, timely_filing_days, timely_filing_source_url — blue shield promise medi-cal provider manualfield_status, provider_phone — Promise provider manual index
Source comparison: 2026-09-18
Source scope: Current and future versions remain distinct; the public page lists provider contact800-468-9935. Locator: Current July 2026 manual and future January 2027 notifications Version: No publication/effective date established on checked HTML. Retrieval: content_read; public_web_read. This is a partial source comparison, not whole-field or whole-record approval.
Primary source for field_status, provider_phone — promise provider manual index
Not checked in this pass: Unresolved fields from immutable field inventory: aka, appeal_levels, category, common_denial_risks, display_name, electronic_claims_supported, legal_name, lives_covered_millions, naic, parent_org, payer_ids, prior_auth_required_codes_sample, quickintell_workflow_fit, record_scope, source_review, states_covered, supports_278, supports_279_271; Whole-record approval, current legal entity/ownership, enrollment and complete insured geography; Every agreement, product, claim type, jurisdiction, filing/appeal exception and clinical authorization policy; Current transaction-specific enrollment/capabilities and authenticated portal behavior; unknown does not mean unavailable; QuickIntell integrations/outcomes, accountable approval and historical April2026 DataForSEO demand; last_reviewed/reviewed_by and prior field-level comparison dates remain unchanged.
Sources used for this guide
State coverage
Blue Shield Promise operates in the following states. Each link opens state-level Medicaid program details, dominant commercial payers, and state-specific RCM regulations.
Evaluate QuickIntell workflow fit for Blue Shield Promise
These module references are evaluation starting points, not evidence of a validated connection, supported transaction or customer deployment. Confirm the actual member plan, data access and product scope first.
- QuickRCM
Evaluate claim preparation, follow-up and denial worklists for Blue Shield Promise; verify the actual plan rules and available connections before implementation.
- QuickAuth
Assess authorization-packet and status workflows for Blue Shield Promise; confirm product, service, delegated reviewer and permitted submission channels.
- QuickERA
Verify the actual 835 files, posting exceptions and reconciliation requirements for Blue Shield Promise before evaluating automation. An ERA identifier alone does not establish supported ingestion or posting.
Frequently asked questions about Blue Shield Promise
Where is the Blue Shield Promise provider portal?
Use https://www.blueshieldca.com/en/bsp/providers/working-with-us/electronic-claims-and-encounters as a starting point for Blue Shield Promise provider resources. This link may open a directory or contact page rather than a transaction portal. Select the applicable product and administrator, then verify the available functions, enrollment and access requirements. QuickIntell is not the official payer portal.
What is the timely filing limit for Blue Shield Promise?
The July 2026 Promise Medi-Cal manual gives 180 days from service for initial claims, with specified delayed-filing exceptions. Other Health Coverage has a separate 90-calendar-day period from that plan’s payment, and additional outer limits/exceptions are described in section 14.1. Confirm the agreement and claim circumstances; do not apply a universal 365-day initial limit.
What is the Blue Shield Promise payer ID?
Claims: Promise’s current claims page lists C1SCA for Office Ally submissions. The September 2024 Promise 837 guide separately uses 954468482 for direct ISA08/GS03 and payer 2010BB NM109. Verify the configured route; neither establishes a universal BS001 claim identifier.. Eligibility (270/271): The joint January 2025 Blue Shield/Promise 270 guide uses direct inbound ISA08 940360524 and GS03 270-940360524, not the Promise 837 value. Generic eligibility BS001 is not established by these sources.. ERA (835): No single all-product identifier established in this registry; see source findings and verify the member product and transaction separately. Clearinghouse-specific: The July 2026 manual and current claims page describe Office Ally/default or selected approved-clearinghouse ERA enrollment. They do not establish BS001 as one universal 835 routing ID. Preserve the separate enrollment workflow.. Do not substitute a claims ID for an unverified transaction ID. Check current source findings and the member ID card before submitting.
Does Blue Shield Promise accept electronic claims?
Verify Blue Shield Promise electronic claims (837), eligibility (270/271), remittance (835) and authorization (278) separately for the member product and clearinghouse. Registry flags and routing references are not current transaction-complete approval. Confirm the companion guide, enrollment and applicable source findings below. A blank or unverified field does not establish that the transaction is unavailable.
How do I appeal a Blue Shield Promise denial?
This registry has not established a payer-specific appeal ladder for Blue Shield Promise. Use the denial notice, plan document, provider agreement, or jurisdictional rule to assign the correct route and deadline. Missing registry evidence does not mean appeal rights are unavailable.
How long do Blue Shield Promise prior authorization approvals take?
Decision deadlines depend on the product, service and urgency. CMS-0057-F generally starts its decision-timeframe requirements in 2026 for Medicare Advantage, Medicaid and CHIP payers subject to the rule: seven calendar days for standard requests and 72 hours for expedited requests. Those requirements exclude drug authorizations and QHP issuers on the federally facilitated exchanges. Other plans, state rules and permitted extensions can differ. Check the applicable policy; a decision deadline is not a guarantee of approval.
What is the Blue Shield Promise provider phone number?
This registry lists 1-800-468-9935 as a contact reference for Blue Shield Promise. 800-468-9935 is Promise Provider Services, distinct from Blue Shield general provider support and EDI technical support. Confirm the member product and responsible administrator.
Automate workflows around Blue Shield Promise requirements
Connect eligibility, prior authorization, pre-submission claim checks, and remittance routing in one governed workflow. Payer and plan configuration is confirmed during implementation.
Disclaimer
This page is operational reference for medical-billing professionals. It is not legal, clinical, or contractual advice. Payer policies change without notice — always verify against Blue Shield Promise's current published documents before submission. CPT® is a registered trademark of the American Medical Association.