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
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