Open juliangruendner opened 4 months ago
pageSize
and page
must be included in the endpoint --> Pagination.API Request:
GET /terminology/entry/search?criteriaSet=http://fdpg.mii.cds/CriteriaSet/Diagnose/icd-10-gm,http://fhir.de/CodeSystem/bfarm/icd-10-gm&searchterm=Diabetes
Response:
{
"totalHits": 42,
"results": [
{
"name": "Diabetes Mellitus",
"id": "203e04cd-4f0a-321b-b1ad-9ec6d211e0a8",
"availability": 119578,
"context": "Diagnosis",
"terminology": "icd-10",
"termcode": "E10-E14",
"kdsModule": "Condition",
"selectable": true
}
]
}
Internal Steps:
ElasticSearchResult
.External Steps:
API Request:
GET /codeableConcept/entry/search/?valueSet=http://hl7.org/fhir/sid/icd-o-3,http://second-value-set&searchterm=Diabetes
Response:
{
"resultHits": 444,
"results": [
{
"code": "",
"display": "",
"system": "",
"version": ""
}
]
}
Internal Steps:
selectedConcepts
. Similarly, removing it means deleting it from selectedConcepts
.ElasticSearchResult
.External Steps:
@michael-82 , @Shayan1375 , @thkoehler11 the necessary input from the ontology generator is part of the following issues: https://github.com/medizininformatik-initiative/fhir-ontology-generator/issues/37 https://github.com/medizininformatik-initiative/fhir-ontology-generator/issues/36 https://github.com/medizininformatik-initiative/fhir-ontology-generator/issues/35
Overview
The UI, backend and ontology have to be extended to make the selected Concepts / or criteria for an attribute of a criterion searchable by valueSet / criteriaSet.
There are two type of searches that have to be distinguished.
1. Searching for a criterion as part of a value set
One criterion can be part of mulitple value sets. It is therefore necessary to extend each criterion with the additional information about the criteriaSets: ["http://fdpg.mii.cds/CriteriaSet/Diagnose/icd-10-gm"] and then add the referencedCriteriaSets to the ui profile as approppriate:
In profile:
In ES Input:
in ES Search:
criteriaSet is a param - keyword (exact match filter) and transparent for the user - only used internally and added automatically based on the attribute information from the ui profile
2. Searching for a codeableConcept (without context) within a value set of codeableConcepts
in profile:
in ES input:
in ES Search: