-
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
Update to PDex PlanNet 1.1.0 #3650
Labels
enhancement
New feature or request
Comments
lmsurpre
added a commit
that referenced
this issue
May 20, 2022
And update ResourceProcessor to pretty-print both the conformance files and the examples. I grouped all the "lots of files" changes into this commit. I will make a separate commit for adding the RegistryResourceProvider and any other code changes. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 20, 2022
Also added version suffix to 1.0.0 canonical URLs to prevent 1.0.0 validation from using 1.1.0 profiles and value set. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 20, 2022
Also added version suffix to 1.0.0 canonical URLs to prevent 1.0.0 validation from using 1.1.0 profiles and value set. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 20, 2022
Also added version suffix to 1.0.0 canonical URLs to prevent 1.0.0 validation from using 1.1.0 profiles and value set. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 24, 2022
And update ResourceProcessor to pretty-print both the conformance files and the examples. I grouped all the "lots of files" changes into this commit. I will make a separate commit for adding the RegistryResourceProvider and any other code changes. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 24, 2022
Also added version suffix to 1.0.0 canonical URLs to prevent 1.0.0 validation from using 1.1.0 profiles and value set. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 24, 2022
And update ResourceProcessor to pretty-print both the conformance files and the examples. I grouped all the "lots of files" changes into this commit. I will make a separate commit for adding the RegistryResourceProvider and any other code changes. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 24, 2022
Also added version suffix to 1.0.0 canonical URLs to prevent 1.0.0 validation from using 1.1.0 profiles and value set. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
May 27, 2022
We found that 1.0.0 profiles which reference extensions did not have their versions specified and so ended up being validated against the extension definitions from 1.1.0. Needs work. |
lmsurpre
added a commit
that referenced
this issue
Sep 2, 2022
1. update StructureDefinition artifacts to specify that the plannet extensions referenced from 1.0.0 profiles should be the 1.0.0 version of the extension definitions 2. update StructureDefinition artifacts to specify that plannet code systems referenced from 1.0.0 valuesets should be the 1.0.0 version of those code systems 3. fix the ConstraintGeneratorTest to specify the version of artifacts to generate constraints from (previously it would always use the "latest" vesion, even for the test that was supposed to execute against the 1.0.0 artifacts) Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Sep 7, 2022
issue #3650 - specify target version for more 1.0.0 artifacts
Walked through the ConstraintGenerator output with Robin and Prasanna. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
PDex PlanNet 1.1.0 was published April 4, 2022 ... its time we add that to our fhir-ig-pdex-plan-net module.
Describe the solution you'd like
Add 1.1.0 alongside 1.0.0 ...similar to what we've done.
We should also move the corresponding examples from fhir-examples down to src/test/resources/examples/100 and add the new examples alongside those in a 110 directory.
Describe alternatives you've considered
Replace 1.0.0 with 1.1.0
Acceptance Criteria
GIVEN the fhir-ig-davinci-pdex-plan-net jar is in userlib
WHEN a resource is validated against an applicable profile with no version suffix (or specifies a version of 1.1.0)
THEN validation uses the artifacts from PDex PlanNet 1.1.0
GIVEN the fhir-ig-davinci-pdex-plan-net jar is in userlib
WHEN a resource is validated against an applicable profile with a version id of 1.0.0
THEN validation uses the artifacts from PDex PlanNet 1.0.0
Additional context
The text was updated successfully, but these errors were encountered: