Open juliangruendner opened 6 months ago
@bastianschaffer , @alexanderkiel we should discuss how best to transport the information for the context. The information is already already indirectly provided in the measure in form of the criteria expression - as the profile can map to the context for our criteria.
I personally would tconsider adding another coding to the stratifier, for example
{
{
"code": [
{
"coding": [
{
"system": "http://fhir-evaluator/strat/system",
"code": "condition-icd10-code"
},
{
"system": "http://fdpg-plus/context/system",
"code": "Diagnose"
}
]
}
],
"stratum": [
{
"value": {
"coding": [
{
"system": "http://fhir.de/CodeSystem/bfarm/icd-10-gm",
"code": "I95.0"
}
]
},
"population": [
{
"code": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/measure-population",
"code": "initial-population",
"display": "display"
}
]
},
"count": 10804
}
]
}
When loading data into the elastic search (https://github.com/medizininformatik-initiative/feasibility-ontology-elasticsearch) used for the ontology in FDPG+ to add the availability for each criterion the context of each criterion has to be considered.
Example entry in elastic search for a criterion
This uses the context to calculate the contextualized-termcode-hash, which is used to identify the criterion. Example of a criterion in the ui_tree which the availability has to be matched to
Therefore it should be possible to add the context to each group of a measure, which then has to be available in the MeasureReport.
so that a MeasureReport with a stratifier would contain a coding for the context