bcda: vendor the upstream files that define behaviour, not only the dictionaries #1299
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upstream review docs/superpowers/specs/2026-10-25-bcda-upstream-review.md §G. Add to
dev/vendor/MANIFEST.toml(weekly drift workflow):BCDA_Partially_Adjudicated_Data_Dictionary.xlsx,unmapped-fields-between-cclf-and-bcda.xlsx(compare withdev/seeds/bcda_v3_cclf_absent.csv), docs pagesfilter-claims-data.md,partially-adjudicated-claims-data.md,access-claims-data.md,how-to-migrate-v3.md,faqs.md,_announcements/*.md; bcda-appbcda/fhir/param.go,bcda/client/bluebutton.go,conf/configs/prod.yml.The docs repo is
CMSgov/bcda-static-site(the manifest'sbcda-siteentry should name it).Done in
2cc1300: manifest pins bcda-appbcda/fhir/param.go,bcda/client/bluebutton.go,bcda/service/service.go, constants, models,conf/configs/prod.yml; new sourceCMSgov/bcda-static-site(filter/access/migrate/PAC/comparison/FAQ pages, announcements);BCDA_Partially_Adjudicated_Data_Dictionary.xlsxandunmapped-fields-between-cclf-and-bcda.xlsx.--verifyclean.