Issue #2832 - enable default profile version configuration #2904
Conversation
Signed-off-by: Mike Schroeder <mschroed@us.ibm.com>
| If a profile in either the list specified by the `fhirServer/resources/<resourceType>/profiles/atLeastOne` configuration parameter or the list specified by the `fhirServer/resources/<resourceType>/profiles/notAllowed` configuration parameter contains a version, for example `http://ibm.com/fhir/profile/partner|1.0`, then a profile of the same name specified in the resource's `meta.profile` element will only be considered a match if it contains exactly the same version. However, if a profile in the lists specified by the configuration parameters does not contain a version, for example `http://ibm.com/fhir/profile/partner`, then a profile of the same name specified in the resource's `meta.profile` element will be considered a match whether it contains a version or not. Using the example configuration above for the `Observation` resource type, if the profile `http://ibm.com/fhir/profile/partnerA|3.2` was specified in a resource's `meta.profile` element then it would be considered a match for the `http://ibm.com/fhir/profile/partnerA` profile specified in the `fhirServer/resources/Observation/profiles/atLeastOne` list. Conversely, if the profile `http://ibm.com/fhir/profile/partnerB` was specified in the resource's `meta.profile` element then it would *not* be considered a match for the `http://ibm.com/fhir/profile/partnerB|1.0` profile specified in the `fhirServer/resources/Observation/profiles/atLeastOne` list. | ||
| If a profile in either the list specified by the `fhirServer/resources/<resourceType>/profiles/atLeastOne` configuration parameter or the list specified by the `fhirServer/resources/<resourceType>/profiles/notAllowed` configuration parameter contains a version, for example `http://ibm.com/fhir/profile/partner|1.0`, then a profile of the same name specified in the resource's `meta.profile` element will only be considered a match if it contains exactly the same version. However, if a profile in the lists specified by the configuration parameters does not contain a version, for example `http://ibm.com/fhir/profile/partner`, then a profile of the same name specified in the resource's `meta.profile` element will be considered a match whether it contains a version or not. | ||
|
|
||
| Keep in mind that a profile specified in the resource's `meta.profile` element could be modified due to the resource's `fhirServer/resources/<resourceType>/profiles/defaultVersions` configuration, and it is the modified profile name that is used in the matching process. |
There was a problem hiding this comment.
do we modify the actual value on the resource or do we just treat it as if it was modified for the purposes of evaluation?
There was a problem hiding this comment.
We do not modify the actual resource. If any profile names get modified, we pass a copy of the resource to the validator with the modified names set in the copy's meta.profile field. I've updated the doc to clarify this.
There was a problem hiding this comment.
OK, that matches my expectation.
Although when I read "that a profile specified in the resource's meta.profile element could be modified" I started thinking of the merits of this :-)
The big advantage of actually setting the version on the profile tag of the actual resource that gets saved is that we'd always know which version it was validated against.
One issue with using version-less references is that, down the line, its very hard to know which version of that IG it was validated against and it might not be valid against the latest/current default version...
Anyway, lets go with whats there...just wanted to write that thought out :-)
Signed-off-by: Mike Schroeder <mschroed@us.ibm.com>
Signed-off-by: Mike Schroeder mschroed@us.ibm.com