-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for US Core 5.0 #3641
Comments
Hit #3646 which is currently blocking this upgrade. Since the constraint in question is just a "best practice" one (and not an "validity" one), I'm thinking to use our SPI to avoid firing this constraint for now. Then we can circle back up and implement the |
lmsurpre
added a commit
that referenced
this issue
May 17, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 17, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
this is intended to be a temporary override until we get around to implementing support for the FHIRPath "repeat" function (#3646) Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
this is intended to be a temporary override until we get around to implementing support for the FHIRPath "repeat" function (#3646) Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
and refine our approach for src/test/java tools to avoid the need to have a different set of the same classes for each version of the IG Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Additionally, we were failing to validate the QuestionnaireResponse examples due to a new constraint that uses an unsupported FHIRPath function. I added a workaround and opened #3646 to get proper support added. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Additionally, we were failing to validate the QuestionnaireResponse examples due to a new constraint that uses an unsupported FHIRPath function. I added a workaround and opened #3646 to get proper support added. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 18, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Additionally, we were failing to validate the QuestionnaireResponse examples due to a new constraint that uses an unsupported FHIRPath function. I added a workaround and opened #3646 to get proper support added. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 23, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Additionally, we were failing to validate the QuestionnaireResponse examples due to a new constraint that uses an unsupported FHIRPath function. I added a workaround and opened #3646 to get proper support added. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 24, 2022
Added a fledgling VSACRegistryResourceProvider and used it to expand US Core ValueSets which were composed from VSAC value sets. The expansion step was added to the ResourceProcessor. Additionally, we were failing to validate the QuestionnaireResponse examples due to a new constraint that uses an unsupported FHIRPath function. I added a workaround and opened #3646 to get proper support added. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 27, 2022
lmsurpre
added a commit
that referenced
this issue
Jun 9, 2022
issue #3641 - package US Core 5.0.0 artifacts
QA for #3646 demonstrates support for US Core 5.0.1, so closing this too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
US Core 5.0.0 was recently published: https://hl7.org/fhir/us/core/
We should add that to our prepackaged support in fhir-ig-us-core
The text was updated successfully, but these errors were encountered: