FHIR Chat · Fhir Validation

Stream: ibm

Topic: Fhir Validation

Sridhar S (Sep 10 2020 at 09:56):

Is there anyway we can disable validation in the IBM fhir-server

Sridhar S (Sep 10 2020 at 09:58):

if so can you give some guide on it

Paul Bastide (Sep 10 2020 at 12:09):

Depends on what you mean... there are fundamental constraints which are always on... if you are referring to the CodeableConcept validation that is now baked in, you can disable it with fhirServer/core/extendedCodeableConceptValidation boolean A boolean flag which indicates whether extended validation is performed by the server during object construction for code, Coding, CodeableConcept, Quantity, Uri, and String elements which have required bindings to value sets.

Paul Bastide (Sep 10 2020 at 12:10):

link is here https://ibm.github.io/FHIR/guides/FHIRServerUsersGuide#51.1-property-descriptions

Lee Surprenant (Sep 10 2020 at 15:02):

more generally, disabling validation on create/update is not something we support today. our design has been that we would make the fastest validator possible and keep validation on all the time. if its slowing you down for a particular use case, please let us know

Digamber Kalivemula (Sep 14 2020 at 05:47):

why resources are getting validated while retrieving data from server?

Lee Surprenant (Sep 14 2020 at 12:33):

there's 2 levels of validation:

ability to parse into our object model
validation of conformance to the constraints of the specification and any profiles declared

Lee Surprenant (Sep 14 2020 at 12:34):

on resource ingestion, we perfrom both 1 and 2

Lee Surprenant (Sep 14 2020 at 12:34):

on resource retrieval, only #1 is performed

Paul Bastide (Sep 14 2020 at 12:35):

Lee Surprenant said:

on resource retrieval, only #1 is performed

To add to Lee's explanation, the IBM FHIR Server saves one rendition of the resource (e.g. application/fhir+json), if a requestor wants to serialize it back, we have to convert it to the intermediate Java object, and serialize it back (e.g. application/fhir+xml)

Lee Surprenant (Sep 14 2020 at 12:39):

because we chose to model codes with a required binding as Java Enumeration, the parsing implicitly includes validation of these fields.
recently, we decided to add similar validation for Coding and CodeableConcept fields with a required-binding to a valueset with an enumerable list of values.
however, because folks may have invalid data sitting in their db (since we weren't checking language code or ucum syntax before), we added a flag to turn this extra validation so that you can disable it long enough to fix the data.