Skip to content

docs(data-integration): pin core value sets to R4, complete required enums - #64

Merged
akim1995 merged 1 commit into
mainfrom
akim/data-integration-pin-r4-valuesets
Aug 27, 2026
Merged

docs(data-integration): pin core value sets to R4, complete required enums#64
akim1995 merged 1 commit into
mainfrom
akim/data-integration-pin-r4-valuesets

Conversation

@akim1995

Copy link
Copy Markdown
Contributor

Two defect classes found by auditing every value-set link and every enumerated column in the section against the terminology server.

Unpinned core-FHIR value sets resolve to R5. US Core 6.1.0 is R4, so the codes we document are R4 codes, but the links showed R5 expansions. Four had already drifted:

value set link showed R4
clinical-findings 1,000 122,883
vaccine-code 287 130
immunization-status-reason 8 28
encounter-participant-type 9 12

All 21 hl7.org/fhir/ValueSet/ links are now pinned to 4.0.1, including the 17 that happen to agree today. US Core value sets stay unpinned: the server resolves those to 6.1.0 on its own.

Four columns listed part of a required binding, so the partial list read as the permitted set:

page column was now
care-team status 3 of 5 5
patient-demographics patient_identifier_use 4 of 5 5
patient-demographics phone_type 3 of 5 5
patient-demographics status (social history) 4 of 8 8

identifier_<n>_use already listed all five, so the two identifier rows on one page disagreed with each other.

Encounter class and participant_type_code also list subsets, but those bindings are extensible, so they stay.

…enums

Unpinned hl7.org/fhir/ValueSet links resolve to R5 on the terminology
server. Four had drifted: clinical-findings showed 1,000 codes against
R4's 122,883, vaccine-code 287 against 130, immunization-status-reason
8 against 28, encounter-participant-type 9 against 12.

Four columns listed part of a required binding: CareTeam status 3 of 5,
identifier use 4 of 5, telecom use 3 of 5, observation status 4 of 8.
@akim1995
akim1995 merged commit 2715630 into main Aug 27, 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.

1 participant