Skip to main content

CMS Medicare Advantage PBP files to the Benefit Plan Standard

The schema repository includes an importer, scripts/from-pbp.js, that reads the Plan Benefit Package (PBP) Benefits files published by CMS and writes 1 Benefit Plan Standard (BPS) document per Medicare Advantage plan. It is the second importer for the standard, after the Marketplace importer. Anyone can run it locally; it needs Node.js, the ajv and ajv-formats packages that the validator also uses, and the PBP files.

Where this importer sits beside the Marketplace importer and the FHIR converter, with every command, is on How the data flows.

The CMS file​

CMS publishes the PBP Benefits data for each contract year on its benefits data page. The 2027 release is on its own PBP Benefits-2027 page and downloads as 1 zip, pbp-benefits-2027.zip, about 23 MB.

PBP Benefits data is the benefit and financial data that Medicare Advantage organizations submit with their bids: for every plan, the cost shares, limits, deductibles, out-of-pocket maximums, out-of-network and point-of-service options, and service area. CMS publishes it as tab-delimited text, 1 file per table, with a dictionary and a readme in the zip.

  • 71 tables. The zip holds 71 data files, 71 SAS input programs, the readme and the dictionary. The tables are by section (A general, C out-of-network and point-of-service, D plan-level financials), by service category (B1 to B20), for optional supplemental packages, for Part D, and for the service area.
  • 7,973 plans. A plan is 1 contract, plan and segment, written H2406-013-000. Of the 7,973, the importer builds the 6,872 plans of the 4 Medicare Advantage types it supports: HMO (3,115), HMO with point-of-service option (1,273), local PPO (2,411) and regional PPO (73). Since October 24, 2026 it also builds the 323 stand-alone Medicare Prescription Drug Plans (PDPs) that file a Part D design (see Part D below). The rest are the 283 employer PDPs whose files hold no Part D design, the 2 employer direct-contract PDPs, PACE, Medical Savings Account, private fee-for-service and cost plans, which the importer refuses.

CMS gives the release no quarter, only the label "PBP Benefits-2027" and the report period 2027; the zip's Last-Modified date is October 1, 2026. The files are Windows-1252 text, not UTF-8, and the importer reads them that way.

The files are not in the repository. You download them into data/pbp/<year>/, which is git-ignored.

What the importer produces​

1 plan in, 1 BPS v1.2.0 document out. The document is checked against the v1.2.0 schema before it is written; a document that fails is not written. The importer writes v1.2.0, not v1.1.0, because the PBP data needs fields that only v1.2.0 has: the contract, plan and segment identifiers (plan_identifiers), the service area, copay and coinsurance ranges, inpatient day intervals, per-ear hearing aid limits and a coverage basis for supplemental benefits.

The Medicare Advantage importer reads the MVP benefit set, 41 benefits: primary care, specialist, inpatient hospital, skilled nursing facility, home health, outpatient hospital, observation, ambulatory surgery center, emergency and urgent care, ambulance, transportation, diagnostic tests, lab, radiology, therapy, mental health individual sessions, chiropractic, podiatry, acupuncture, hearing and eye exams, hearing aids, eyeglasses, dental cleaning and fillings, over-the-counter items, meals, fitness and, since October 20, 2026, preventive services (category 14a, a $0 copay in network on the plan's attestation). Other service categories, such as Part B drugs, cardiac rehabilitation, other dental services, contact lenses and the other defined supplemental benefits, are not imported yet.

At plan level, the Medicare Advantage importer also reads, since October 20, 2026, the premium and the Part B premium reduction from Section D, and the member services phone, the website and the provider directory link from Section A. It writes them to premium, part_b_premium_reduction, contacts and the in-network tier's provider_directory_url, fields of the Benefit Plan Standard schema 1.2.0; contacts and provider_directory_url were added to its draft that day. On a plan with drug coverage the premium in Section D leaves its Part D part out, and no PBP file states that part; since November 11, 2026 the premium's notes say so, and the Part D formulary importer writes the Part D part as premium.drug_amount (the monthly premium is the sum of the 2). A website or directory address is written only when the file gives it as an http or https address with its scheme; an address without one, such as "www.aetna.com/medicare", is quoted in source_references, because the Medicare Advantage importer adds no scheme it would have to guess. With preventive services and the key on category 7i (see The benefit crosswalk below), these closed the gaps G1 to G5 of the medical MVP technical specification on October 20, 2026.

Since November 4, 2026 (1.2.0 draft 8) the importer also writes a limits entry with unlimited true and value null for every unlimited or no-maximum answer on a covered benefit, so a document says "no limit" where the file does, and an app can tell it from a limit not read. Over the 6,872 plans, covering plans with a limits entry went, before and after, from 37 to 2,681 of 2,681 for meals, from 1,367 to 4,795 of 4,795 for fitness and from 1,551 to 1,816 of 1,816 for rides to medical appointments.

Since November 11, 2026 the importer reads Section D's Reductions in Cost Sharing: an amount per period that lowers the member's cost sharing for the services it lists, such as a credit of $450 every 3 months on a debit card. Each group is 1 benefit entry, PBP_D_RICS_<n>, after the medical benefits, with category REDUCTIONS_IN_COST_SHARING, the amount as a dollars limit, and the service categories, the delivery mode and whether it can be applied to a deductible as conditions; a group that shares its amount with a combined supplemental benefit group takes that group's shared_limit_id. 95 plans of contract year 2027 file 110 groups; none of the 5 examples has one. Mapping: section 5.10 of the importer spec.

What it carries over:

  • Ranges. When the file gives a minimum and a maximum copay or coinsurance (for example a specialist at $0 to $65), the importer writes both ends. It never picks 1, because the file does not say which service carries the minimum.
  • Day intervals. Inpatient hospital cost sharing by day (days 1 to 5 at 1 price, days 6 to 90 at another) is written as a per-day step with a day range.
  • Limits. Visit and treatment limits, dollar maximums, and the hearing aid limits: 1 count per period, per ear or for both ears, and a maximum that hearing aids share with routine hearing exams.
  • Hospital cost tiers. A plan with tiered inpatient hospital prices gets 1 tier per hospital tier number. The files do not name the facilities in a tier.
  • Network tiers. IN always; OUT for PPOs; POS for HMO-POS plans.

The importer never adds a value the files do not contain. A Medicare-defined amount that the file names but does not state, such as the Part B deductible, is not filled in. A code outside the dictionary stops the import for that plan, with the column and value quoted, rather than being guessed. A value with no BPS field is kept as text in source_references[] (at plan level or on the benefit it belongs to) or in a tier's notes, so nothing is dropped without a trace. Each cost share's notes quote the file cells it was read from.

The importer never produces FHIR. The FHIR converter, scripts/to-insuranceplan.js, does that, from the importer's output, unchanged. It is the same converter that produces the FHIR InsurancePlan files for the other examples.

Over the whole 2027 file, in a run on October 20, 2026, the Medicare Advantage importer built all 6,872 plans with 0 errors and 0 schema failures against the Benefit Plan Standard schema 1.2.0 draft, and wrote 260,800 benefits. It raises 234 warnings, all of 1 kind: the 117 Part B-only plans leave their inpatient hospital and skilled nursing facility cost shares blank, so those 2 benefits are not written for them. The same run writes the premium on 5,510 plans, the Part B premium reduction on 1,412, the member services phone on 6,872, the website on 457 and the provider directory link on 1,585. Its latest recorded run, on October 24, 2026, with the Part D sections, builds the 6,872 plans and the 323 PDPs with 0 errors and 0 schema failures, and writes 235,324 Part D benefits on the Medicare Advantage plans and 16,304 on the PDPs.

From the file to a FHIR Bundle​

First, once per contract year, download and unzip the files into data/pbp/<year>/ and record the download date in data/pbp/<year>/download.json (for example {"downloaded": "2026-10-06", "release_label": "PBP Benefits-2027"}). The importer spec, section 11, gives the exact steps:

mkdir -p data/pbp/2027 && cd data/pbp/2027
curl -L -O https://www.cms.gov/files/zip/pbp-benefits-2027.zip
unzip pbp-benefits-2027.zip
cd ../../..

Then, from the schema repository:

# 1. Import 1 plan (here UnitedHealthcare, AARP Medicare Advantage from UHC FL-0021, Florida, contract year 2027)
node scripts/from-pbp.js --year 2027 --plan H2406-013-000 --out plan.json

# 2. Validate the BPS document (v1.2.0 schema and vocabularies)
node scripts/validate.js --schema schema/v1.2.0/benefit-plan.schema.json plan.json

# 3. Convert it to a FHIR Bundle; the Bundle is written to stdout
node scripts/to-insuranceplan.js plan.json > plan.insuranceplan.json

# 4. Validate the Bundle with the HL7 FHIR validator
java -Dfile.encoding=UTF-8 -jar validator_cli.jar -version 4.0.1 \
-ig hl7.fhir.us.insurance-card#2.0.0-ballot \
-ig fhir/definitions \
plan.insuranceplan.json

To find a plan ID, list a contract's plans:

node scripts/from-pbp.js --year 2027 --contract H2406

An eligibility response (HETS 271) gives a member's contract and plan but not the segment, and in the contract year 2027 files 266 contract and plan pairs have more than 1 segment, each serving different counties. The segment tool, scripts/pbp-segment.js, reads PlanArea.txt with the Medicare Advantage importer's reader and gives the segment and the full plan key from the county's SSA code (--county 10150) or from its name and state. For Duval County, Florida, node scripts/pbp-segment.js --year 2027 --contract H1609 --plan 028 --county-name "Duval, FL" prints county 10150 Duval FL, partial_flag "", eghp_flag "0", segment 000 and plan key H1609-028-000, the key that scripts/from-pbp.js --plan takes. The steps an app follows from a published service-areas.json are in Identifying the plan in the medical MVP technical specification.

An import with the Medicare Advantage importer takes about 4 seconds, most of it reading the 172 MB service area file. The same files and download date always give byte-identical output.

The benefit crosswalk​

Each PBP service category has its own columns, and their names differ from category to category (pbp_b7a_copay_amt_mc_min, pbp_b7b_copay_mc_amt_min, pbp_b18a_copay_amt). The crosswalk, fhir/pbp-crosswalk.json, has 1 row per benefit the importer writes. Each row names the PBP category, the file, every column read, and the BPS canonical benefit key, or nothing.

41 benefits: 35 mapped, 6 unmapped. An unmapped row is written like a mapped one, carried by name and by the dictionary's label, with no canonical key. The 6 are the Medicare-covered podiatry, hearing exam and eye exam rows, and the 3 prescription hearing aid rows for a single aid type (inner ear, outer ear, over the ear), because the Benefit Plan Standard canonical benefit vocabulary has no key for them. Routine foot care, routine hearing and eye exams, and hearing aids of all types have keys and are mapped, and since October 20, 2026 so are the combined physical therapy and speech-language pathology row and preventive services (preventive_care).

A category maps only when it clearly is the canonical service. There is no nearest fit, because a nearest fit would attach a cost share to a service it does not describe. Physical therapy and speech-language pathology is 1 category in the PBP file, priced once for both therapies, so mapping it to physical_therapy or speech_therapy would put the wrong price on the other. It has its own key, physical_and_speech_therapy, added in version 1.3.0 of the Benefit Plan Standard canonical benefit vocabulary (118 keys) on October 20, 2026.

Part D​

Since October 24, 2026 the importer reads the 3 Part D files of the release, pbp_mrx.txt (1 row per plan), pbp_mrx_tier.txt (1 row per drug tier) and pbp_mrx_p.txt (1 row per tier after the out-of-pocket threshold). The mapping, with every count and decision, is the Part D mapping in the schema repository.

  • Medicare Advantage plans with drug coverage (5,996 of the 6,872) get a pharmacy object, the Benefit Plan Standard's place for drug coverage since the 1.2.0 draft 6: the Part D deductible and the tiers it applies to, the out-of-pocket threshold, the coverage stages (deductible, initial coverage, catastrophic), the drug tiers with their labels, and the pharmacy networks (standard and preferred retail, standard and preferred mail order, out of network, long-term care). After the medical benefits, which keep their places, come the Part D benefits: 1 per tier, pharmacy network and day supply in initial coverage (for example Tier 3, preferred mail order, 100-day supply), and 1 per tier in catastrophic coverage. A plan that answers that it offers no Part D benefit, and an employer plan whose row holds no Part D design, gets a source reference that says so instead.
  • Stand-alone Part D plans (type 29) get a document of their own, with plan type PDP, market medicare_part_d, the pharmacy object and the Part D benefits, and no medical benefit. A PDP is sold by Part D region, which the schema has no field for, so the region is kept as text; the PDP premium is in no PBP file, so none is written; since November 11, 2026 the Part D formulary importer writes it from the formulary file's PREMIUM. Its member services phone comes from the Part D phone column of Section A (pbp_a_pd_curmbr_phone, filled on all 323 PDPs), because a PDP leaves the Medicare Advantage phone column blank.
  • 2 values come from outside the files. No PBP column states the Part D out-of-pocket threshold, $2,400 for 2027; the importer takes it from CMS's CY 2027 Rate Announcement and cites it. After the threshold a member pays $0 for covered Part D drugs (42 CFR 423.104(d)(5)(i)); where the file gives an amount after the threshold, it is the cost sharing of drugs on the tier that Part D excludes, and the importer quotes it in the step's notes instead of writing it as the cost share.
  • Insulin has its own cost sharing on each tier in the files ("25% up to $35"). The importer quotes those cells and writes no insulin benefit yet: which drugs are insulin comes with the formulary, which a later reader will add.

Two plans are checked against their Summary of Benefits on Part D, with 0 differences (see The Summary of Benefits check below). The FHIR converter lists every Part D benefit by name only, because the CARIN SBC InsurancePlan profile has no coverage stage, pharmacy network or day supply, and keeps the Part D deductible and threshold as plan-level costs; it does not convert a stand-alone Part D plan, because the profile describes a medical plan.

The 7 examples​

BPS documentPlanContract yearFHIR Bundle
unitedhealthcare-aarp-medicare-advantage-from-uhc-fl-0021.pbp.jsonUnitedHealthcare, AARP Medicare Advantage from UHC FL-0021 (PPO), H2406-013-000, Florida, local PPO, 7 counties2027aarp-medicare-advantage-from-uhc-fl-0021-ppo-h2406-013-000.json
humana-humana-gold-plus-h1036-068.pbp.jsonHumana, Humana Gold Plus H1036-068 (HMO), H1036-068-000, Florida, 9 counties2027humana-gold-plus-h1036-068-hmo-h1036-068-000.json
aetna-medicare-aetna-medicare-select-extra.pbp.jsonAetna Medicare, Aetna Medicare Select Extra (HMO-POS), H1609-028-000, Florida, 11 counties2027aetna-medicare-select-extra-hmo-pos-h1609-028-000.json
upmc-for-life-upmc-for-life-ppo-rx-choice.pbp.jsonUPMC for Life, UPMC for Life PPO Rx Choice (PPO), H5533-019-000, Pennsylvania, 1 county2027upmc-for-life-ppo-rx-choice-ppo-h5533-019-000.json
scan-health-plan-scan-costco-medicare-advantage.pbp.jsonSCAN Health Plan, SCAN Costco Medicare Advantage (HMO), H5425-140-000, California, 1 county2027scan-costco-medicare-advantage-hmo-h5425-140-000.json
unitedhealthcare-aarp-medicare-rx-preferred-from-uhc.pbp.jsonUnitedHealthcare, AARP Medicare Rx Preferred from UHC (PDP), S5921-383-000, Part D region Florida2027Not converted (a stand-alone Part D plan)
wellcare-wellcare-value-script.pbp.jsonWellcare, Wellcare Value Script (PDP), S4802-146-000, Part D region Florida2027Not converted (a stand-alone Part D plan)

The 5 Medicare Advantage plans were chosen to cover the cases: the UnitedHealthcare PPO has an out-of-network deductible and copay ranges; the Humana HMO has no medical deductible; the Aetna plan is an HMO-POS with point-of-service groups; the UPMC plan has inpatient hospital cost tiers; the SCAN plan has hearing aids that share the routine hearing exam maximum. All 5 have drug coverage, with 33 to 67 Part D benefits each. The 2 PDPs have a deductible that skips Tiers 1 and 2, split retail and mail order pharmacies and an excluded-drug amount after the threshold (UnitedHealthcare, 41 Part D benefits), and 6 tiers, 2 of them with labels that have no HL7 drug tier code (Wellcare, 70).

Each Benefit Plan Standard document has 38 of the 41 crosswalk benefits. The 3 not written are the hearing aid rows for a single aid type (inner ear, outer ear, over the ear), which are written only when a plan chooses that type. Each Bundle places 16 of the 38 and lists 22 by name only, because the Benefit Plan Standard converter's crosswalk places those benefits on none of the 29 benefit category codes of the CARIN SBC InsurancePlan profile; since October 24, 2026 it lists its Part D benefits by name only too (see Part D above). The 16th placed benefit, since October 20, 2026, is preventive services, under preventive-care. The 5 Bundles are in examples/fhir/ and are published on this site beside the 10 read from plan documents: see FHIR InsurancePlan.

What the PBP files do not carry​

Some BPS fields have nothing to fill them in the PBP files:

  • No dates. There is no effective date, expiry date or coverage period. The plan year comes from the contract year.
  • No accumulator or limit period. The files say "Every year", never plan year or calendar year, so period is not written on accumulators and a yearly limit is written as per_year.
  • No family amounts. Section D gives individual deductibles and out-of-pocket maximums only.
  • No page numbers. The files are tables, not documents, so every source reference is text with no page.
  • No FIPS county codes. The service area file uses the Social Security Administration (SSA) county code, which is not FIPS (Duval County, Florida is 10150 in the file and 12031 in FIPS). The importer writes the county name, leaves fips empty and keeps the SSA code as text.
  • Cost-share basis on most services. The files say per visit only for a few categories, so basis is written only where the file states it.

Going the other way, the PBP files carry things BPS has no field for. The importer keeps each one as text, and the spec lists each with a proposed field:

  • the combined in-network and out-of-network deductible and out-of-pocket maximum (the Summary of Benefits prints the combined maximum in its out-of-network column);
  • a Medicare-defined deductible or cost share with no amount in the file, such as the Part B deductible or the Medicare-defined inpatient stay;
  • the out-of-pocket maximum type (lower, intermediate or mandatory) and service-specific out-of-pocket maximums;
  • which services a deductible covers, as a list of service categories;
  • which service carries the minimum of a range;
  • whether a cost share counts toward the plan deductible, as distinct from being subject to it;
  • hearing aid copays per pair of aids, and a coinsurance rate's base ("90% of the allowance");
  • a supplemental benefit that is both mandatory and optional;
  • the plan's counties across more than 1 state, partial counties, and the regions of a regional PPO;
  • employer-only and special needs plan flags;
  • the facilities in a hospital cost tier, which the files do not name.

The full list, with each workaround, is in section 9 of the importer spec. Optional supplemental packages and cost sharing for special populations are not read at all; the v1.2.0 draft defers both.

The Summary of Benefits check​

The PBP file is data that carriers submit; the document a member sees is the Summary of Benefits. To check the importer against it, the schema repository has a script, scripts/pbp-sob-check.js, that compares an imported document with the values a plan's Summary of Benefits prints. Its input is 1 expectations file per plan, with the printed value, its page, and where it sits in the document. Each check comes out as:

  • MATCH: the document holds the printed value;
  • READING: the document holds a different value on purpose, and the check says why (for example, the file gives a range where the Summary of Benefits prints 1 end of it);
  • DIFFERENCE: the document disagrees, and the script exits with an error.

Four plans are checked, 2 on their medical benefits and 2 on Part D. On October 20, 2026 the medical checks gained the values the Medicare Advantage importer now reads where the Summary of Benefits prints them: the premium, preventive services, the member services phone, the website and the provider directory link. On October 24, 2026 the Part D checks were added: the deductible and its tiers, the threshold, the stages, the tiers and networks, each tier's retail and mail order cost shares for each printed day supply, the catastrophic stage and long-term care.

PlanSummary of BenefitsChecksMatchReadingDifference
H2406-013-000, UnitedHealthcare PPO2027, document ID Y0066_SB_H2406_013_000_2027_M8371120
H1609-028-000, Aetna HMO-POS2027, document ID Y0001_H1609_028_HP32_SB2027_M6547162
H1036-068-000, Humana HMO, Part D2027, document ID H1036_SB_MAPD_HMO_068000_2027_M464510
S5921-383-000, UnitedHealthcare PDP2027, document ID Y0066_SB_S5921_383_000_2027_M434030

All 4 plans have 0 differences on cost shares. The Part D readings are the insulin rows (no insulin benefit is written yet) and, for the PDP, the premium and the service area, which the files do not carry as fields. The 2 differences on the Aetna plan are on links: its Summary of Benefits prints AetnaMedicare.com as the website and AetnaMedicare.com/H1609-028 for the provider directories, while the PBP file gives "www.aetna.com/medicare" and "www.aetnamedicare.com/findprovider"; all 4 addresses resolved on October 20, 2026. The Benefit Plan Standard document holds the filing, which has no scheme, so it quotes both addresses and writes neither to a field, and scripts/pbp-sob-check.js exits with an error on the Aetna file because of the 2. The 2 new readings on the UnitedHealthcare plan are its website and directory address, filed as AARPMedicarePlans.com with no scheme, so quoted and not written.

On November 11, 2026, 10 more UnitedHealthcare and AARP plans, 5 Medicare Advantage plans and 5 stand-alone Part D plans in Florida, Texas and California, were checked against their 2027 Summaries of Benefits, premium included, on documents with their Part D drug lists and premium parts from the Part D formulary importer: 453 checks, 424 match, 29 readings, 0 differences. The first run had 1 difference, a credit the Medicare Advantage importer did not read yet, filed as Reductions in Cost Sharing; it reads it since the same day. The check files are in docs/specs/pbp-sob-checks/ in the schema repository.

Reading the PDFs and writing the expectations files is done by hand; the script does the comparison. The check has limits. Some readings are confirmed on 1 plan only, and the spec lists what is still to confirm: the out-of-network deductible rule for PPOs (UnitedHealthcare only), the $0 cost share for a service answered "No" to both copay and coinsurance (no Summary of Benefits checked yet), and the out-of-network maximum of HMO-POS plans.

HMO-POS plans​

An HMO with a point-of-service option (HMO-POS) has no out-of-network benefit in the PBP file: all 1,273 declare a point-of-service option instead. The importer writes them a POS tier, and reads the file's out-of-network deductible and out-of-pocket maximum columns as the POS option's, with a note quoting the columns.

That reading is confirmed on 1 plan, Aetna Medicare Select Extra (H1609-028-000), from 2 sources:

  • Aetna's 2027 Summary of Benefits prints the point-of-service side under "Your out-of-network costs": no in-network deductible and $500 for certain out-of-network services (page 2), a specialist at $70 after the plan deductible, and an inpatient stay at 50% after the plan deductible (page 3).
  • CMS Medicare Plan Finder for the same plan labels the $500 deductible "Out-of-network" and prints the specialist at $0 to $38 in network and $70 out of network.

The converter maps the POS tier to out-of-network with a text-only qualifier, "Point-of-service option". Before it did, the converter refused the tier, and no HMO-POS plan reached FHIR. The 10 Bundles read from plan documents are byte-identical before and after the change.

Where a plan's Section C and Section D disagree on the point-of-service deductible (12 plans), the importer writes Section D and quotes Section C with a note. Also open: a covered service that the plan's point-of-service list leaves out, which the Aetna Summary of Benefits prints as "Not Covered" (8 checked rows: primary care, the Medicare-covered and routine hearing exams, hearing aids, mental health individual sessions, dental, eyeglasses and fitness). The Medicare Advantage importer writes no POS row for it, and the Benefit Plan Standard converter's "Not stated in the BPS document" placeholder shows in its place.

The validator result​

The 5 Bundles were validated on October 20, 2026, after the Medicare Advantage importer gained preventive services, the premium, the contacts and the provider directory link, and again after each later change: the Part D sections (October 24), the combined supplemental benefit groups (October 28), and the 1.2.0 drafts 7, 8 and 9 (October 31, November 4 and November 11, 2026), each run with the result below. The validator is the HL7 FHIR validator 7.0.0, FHIR 4.0.1, against hl7.fhir.us.insurance-card#2.0.0-ballot and the Benefit Plan Standard definitions in fhir/definitions. All 5 pass with 0 errors. 17 warnings:

BundleErrorsWarnings
aarp-medicare-advantage-from-uhc-fl-0021-ppo-h2406-013-000.json00
humana-gold-plus-h1036-068-hmo-h1036-068-000.json00
aetna-medicare-select-extra-hmo-pos-h1609-028-000.json013
upmc-for-life-ppo-rx-choice-ppo-h5533-019-000.json04
scan-costco-medicare-advantage-hmo-h5425-140-000.json00

The 17 warnings are of 2 kinds:

  • 16 are text-only cost qualifiers. The profile's Cost Tier value set has only value-choice, standard and virtual, so the tiers the Medicare Advantage importer writes have no code: 12 Point-of-service option entries on the Aetna Bundle (the 12th, since October 20, 2026, on the preventive services benefit) and 4 hospital cost tier names on the UPMC Bundle. The binding is extensible, so each carries its name as text.
  • 1 is the Aetna plan type. The SBC Plan Type value set has no code for HMO-POS, so the Benefit Plan Standard converter writes the plan type as text.

The information messages are the extension slicing messages that the 10 SBC Bundles raise too. The full record is the sixth run in examples/fhir/VALIDATION.md.

The importer, its decisions and its open questions are in the importer spec, and the table layout is in the record layout notes.