Add 2026 US Quality Core v0.5.0 resources#10
Open
arscan wants to merge 2 commits into
Open
Conversation
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.
Summary
This PR adds resources and search parameters for the 2026 US Quality Core IG in preparation for deployment of the US Quality Core Test Kit to inferno.healthit.gov. These resources are used for client tests, as the client tests proxy data served by the inferno.healthit.gov reference server instance to simulate a conformant data exchange partner for the client under test. They also are used to demonstrate the server tests. This is patterned off US Core usage of this server.
These patient bundle resources are based off examples in the IG, which themselves were originally provided by QI-Core 6. However, many updates were made to fill out all 'USCDI+ Quality' tagged elements, while also attempting to retain clinical realism.
The search parameters bundle resources introduce search parameters not supported by base FHIR. These allow HAPI to index these fields and provide searching of these parameters.
This PR does not update the Bulk Data cache, as the current use case does not involve accessing the data via a bulk data interface.
Impacts and side effects
Because this is a shared server, the team considered possible impacts to other uses of the server.
There should not be any ID collisions with existing content on the reference server.
We do not believe that the number of new resources this adds to the server will have any impact to the performance of the server. There are only a moderate amount of resources, and there are only a handful of search parameters.
The only known side effect during usage of existing test kits should be an extra patient will be available for selection during SMART App Launches in the 'patient picker' dialog (when a test performs a patient launch). Several other test kits have added patients over time that show up in this view, and I do not believe having one more patient in that dialog will have any impact to users.
Testing Guidance
The highest risk impact is on the (g)(10) test kit when being demonstrated against the reference server. We have verified it is not impacted locally but this should be verified on the QA server.
Note that the docker volume will need to be removed from the reference server's postgres db volume in order to trigger a reimport of this content. Care should be taken to ensure that the correct volume is deleted, as other services may also provide postgres dbs.