You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the case where one or more profiles have been loaded in the FHIR server, but a customer does not want to allow those profiles to be used to validate resources, the customer should have a way via a config property to specify the list of profiles they do not want to allow to be used.
Describe the solution you'd like
Similar to the fhirServer/resources/<resourceType>/profiles/atLeastOne config property, which specifies a list of profiles, one of which must be specified by a resource to validate against, there could be a config property which specifies a list of profiles which a resource is not allowed to validate against.
Describe alternatives you've considered
None.
Acceptance Criteria
GIVEN a profile is specified in a config property as not being allowed to be validated against
AND a resource specifies that profile to be validated against
WHEN a request is made to create or update the resource
THEN the request will fail
notably, the setting does NOT prevent validation from occurring on our $validate endpoint. that was never really discussed and so I think this behavior is fine, but i wanted to make sure it was clear that the server will still try to validate against the "notAllowed" profiles at this alternate endpoint
Is your feature request related to a problem? Please describe.
In the case where one or more profiles have been loaded in the FHIR server, but a customer does not want to allow those profiles to be used to validate resources, the customer should have a way via a config property to specify the list of profiles they do not want to allow to be used.
Describe the solution you'd like
Similar to the
fhirServer/resources/<resourceType>/profiles/atLeastOne
config property, which specifies a list of profiles, one of which must be specified by a resource to validate against, there could be a config property which specifies a list of profiles which a resource is not allowed to validate against.Describe alternatives you've considered
None.
Acceptance Criteria
AND a resource specifies that profile to be validated against
WHEN a request is made to create or update the resource
THEN the request will fail
Additional context
Related issues: #2551 , #2832
The text was updated successfully, but these errors were encountered: