docs: point data-integration value set links at tx.fhir.org - #46
Open
Nesmeshnoy wants to merge 1 commit into
Open
docs: point data-integration value set links at tx.fhir.org#46Nesmeshnoy wants to merge 1 commit into
Nesmeshnoy wants to merge 1 commit into
Conversation
The five VSAC links in the section resolve to a login wall. VSAC serves an SPA that returns HTTP 200 with a byte-identical shell for every OID, so the codes are only visible to a reader holding a UMLS account. tx.fhir.org renders the same value sets publicly. Each link now carries the pinned version id, the convention the US Core profile pages use for this kind of binding. Every target verified: HTTP 200, status active, title matching the existing link text. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The five VSAC links in the data-integration section do not open. VSAC serves a single-page app behind a UMLS login: it answers HTTP 200 with a byte-identical shell for every OID, so a reader without an account sees no codes. Identical response sizes across different OIDs is the tell; a status check alone passes.
tx.fhir.org renders the same value sets publicly, and it is where the US Core profile pages themselves point this kind of binding. Link text is unchanged.
uscdi/care-team.mdspecialty_nucc2.16.840.1.114222.4.11.1066-20240606uscdi/care-team.mdpractitioner_role_code,role_code2.16.840.1.113762.1.4.1099.30-20240605uscdi/health-insurance.mdcoverage_type_code2.16.840.1.114222.4.11.3591-20250419provider-directory/README.mdspecialty_nucc2.16.840.1.114222.4.11.1066-20240606Each target verified: HTTP 200, distinct response bodies,
status=active, title matching the existing link text. Versions are pinned so the link cannot drift, matching a section already pinned to US Core 6.1.0. Every OID also has an older retired version on tx.fhir.org; the active one is used in all three cases.@akim1995 two things for you, neither changed here:
sex. If you had a reason to prefer VSAC as the target, say so and I will drop this.uscdi/patient-demographics.mdstill links thesexrow to theus-core-sexStructureDefinition rather than a code list, which is the defect docs: correct data integration terminology links and codes #45 identified and which never landed. The Sex value set is on tx.fhir.org as2.16.840.1.113762.1.4.1240.3-20230628, status active. Left alone to keep this change to dead links only.🤖 Generated with Claude Code