Skip to content

[HealthSamurai/smartbox#431] document CARIN BB 2.1.0 and Plan-Net 1.2.0 - #33

Merged
Seryiza merged 1 commit into
mainfrom
431-carin-bb-2.1.0-plan-net-1.2.0
Aug 19, 2026
Merged

[HealthSamurai/smartbox#431] document CARIN BB 2.1.0 and Plan-Net 1.2.0#33
Seryiza merged 1 commit into
mainfrom
431-carin-bb-2.1.0-plan-net-1.2.0

Conversation

@Seryiza

@Seryiza Seryiza commented Aug 18, 2026

Copy link
Copy Markdown
Member

Part of stage 2 of HealthSamurai/smartbox#431 — the documentation half.

File Change
docs/api-reference/implementation-guides.md CARIN BB STU 2.0.0 -> 2.1.0, Plan Net STU 1.1.0 -> 1.2.0
docs/api-reference/capability-statement.md same two rows in the profile-family table
docs/interop-apis/provider-directory.md two "Plan-Net 1.1.0" mentions in prose
docs/get-started/quickstart-run-locally.md BOX_BOOTSTRAP_FHIR_PACKAGES sample
assets/get-started/quickstart/docker-compose.yaml same, the file readers actually run

Spec links move with the versions: carin-bb/STU2 -> STU2.1,
plan-net/STU1.1 -> STU1.2. Both new URLs return 200.

This also resolves a standing inconsistency: docs/interop-apis/provider-access.md
and docs/interop-apis/payer-to-payer.md already promise the CARIN BB non-financial
Basis profiles, which exist only from 2.1.0 onward.

bun run lint passes — 13 checks, 0 errors. The 4 warnings (title mismatches,
orphan/dead-end pages) are pre-existing and untouched by this PR.

Brings the IG matrix, capability statement, provider-directory page and the
quickstart compose file in line with what the deployments run. Spec links move
with the versions (carin-bb/STU2 -> STU2.1, plan-net/STU1.1 -> STU1.2).

Also resolves a standing inconsistency: the provider-access and payer-to-payer
pages already promise the CARIN BB non-financial Basis profiles, which exist
only from 2.1.0 onward.
@Seryiza
Seryiza merged commit c066ef1 into main Aug 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants