Add exact search endpoint for criteria and for value sets

[juliangruendner]

Add exact search endpoint for criteria (ontology) and value sets (codeableConcept)

for cirteria = context + terminology + codes (comma separated or newline separated)
for value sets = terminology + codes (comma separated or newline separated)

Should return the standard elastic search response + a list of codes not found.

suggestion @michael-82 -> list with found and list with not found

Needed for these issues:

medizininformatik-initiative/feasibility-gui#460
medizininformatik-initiative/feasibility-gui#461

This requires changes in the generated files from the fhir-ontology-generator. The changes will be included in release 3.10.0

[michael-82]

Requires changes in the onto -> fhir-ontology-generator PR

Will be included in the release 3.10.0

[michael-82]

@Shayan1375 @thkoehler11 - Could you please check the modifications in the commited open api documentation to see if this fits your needs?

[Shayan1375]

We suggest following response for the endpoint /terminology/entry/search-exact which should be renamed to /terminology/entry/bulk-search

{
	"uiProfile": {...},
  "found": [
    {
      "display": {
        "original": "display entry",
        "translations": [
          {
            "language": "de-DE",
            "value": "localized entry"
          }
        ]
      },
      "id": "203e04cd-4f0a-321b-b1ad-9ec6d211e0a8",
      "availability": 119578,
			"context": {
				"code": "119373006",
				"system": "http://snomed.info/sct",
				"version": "http://snomed.info/sct/900000000000207008/version/20210731",
				"display": "Amniotic fluid specimen (specimen)"
			},
			"termCodes": [
				{
					"code": "119373006",
					"system": "http://snomed.info/sct",
					"version": "http://snomed.info/sct/900000000000207008/version/20210731",
					"display": "Amniotic fluid specimen (specimen)"
				}
			],      
			"kdsModule": "Condition",
      "selectable": true
    }
  ],
  "notFound": [
    "foo"
  ]
}

[michael-82]

We also discussed changing the request from including the parameters (context, terminology, searchterms) in the url to sending a json document as request body

For the terminology endpoint the schema would be

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://www.forschen-fuer-gesundheit.de/ontology-bulk-search.schema.json",
  "title": "Request body for ontology bulk search endpoints",
  "description": "This represents the json document that specifies the entries that should be found.",
  "type": "object",
  "properties": {
    "terminology": {
      "type": "string"
    },
    "context": {
      "type": "string"
    },
    "searchTerms": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minContains": 1
    }
  },
  "required": [
    "terminology",
    "context",
    "searchTerms"
  ]
}

and an example:

{
  "context": "Diagnose",
  "terminology": "http://fhir.de/CodeSystem/bfarm/icd-10-gm",
  "searchTerms": [
    "Z01.81",
    "R84",
    "O28",
    "something invalid"
  ]
}

For the codeable concepts endpoint the schema would be

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://www.forschen-fuer-gesundheit.de/codeable-conceptbulk-search.schema.json",
  "title": "Request body for codeable concept bulk search",
  "description": "This represents the json document that specifies the entries that should be found.",
  "type": "object",
  "properties": {
    "valueSet": {
      "type": "string"
    },
    "searchTerms": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minContains": 1
    }
  },
  "required": [
    "valueSet",
    "searchTerms"
  ]
}

and an example:

{
  "valueSet": "https://www.medizininformatik-initiative.de/fhir/ext/modul-biobank/ValueSet/sct-body-structures",
  "searchTerms": [
    "763436008",
    "763434006",
    "something invalid"
  ]
}