use recorded-date by timerestriction

[KutSaleh]

If we use the timerestriction when querying for diagnoses in a cohort, then the onset-date is used, would it be possible to use the recorded-date in addition as well?

[juliangruendner]

@KutSaleh additionally is difficult - its still an ongoing discussion which field should be used. In this case its meant to be the clinical date and for most fhir resources this is defined, see: https://hl7.org/fhir/R4/searchparameter-registry.html (search for clinical-date).
Condition is the one exception and there is no clear agreement on what the clinical data should be, so before we search for multiple or go back to recorded-date - a mii wide decisiion has to be made on this issue
@julsas - is there a definitiv answer to this now?

[KutSaleh]

thank you for your quick reply. I would prefer the recodedDate as this is with 1..1 cardinality in the diagnosis MII module, see https://simplifier.net/mii-basismodul-diagnose-2024/mii_pr_diagnose_condition as well it is listed as a search parameter (recoded-date)

[DannyAmmon]

Please keep in mind that Condition.onsetDateTime does not exist in structured form in most primary documentation systems.

[KutSaleh]

is there anything new?

[julsas]

No final answer but I don't mind switching back to recordedDate.

Condition.onset was chosen because we assumed researchers would be most interested in onset and less interested on recordedDate. Downside is that onset is optional in our profile because most primary systems won't have it present.
Condition.recordedDate will deliver more results as primary systems will have it and it is mandatory in our diagnosis profile.

[KutSaleh]

Thanx, can it then be changed to recordedDate? or should the final answer be given first? If so, who can give the final answer?

[julsas]

Yes, it will be changed to recordedDate.