While I have no opposition to the change here, I just want to note for posterity that the boundaries between a FHIR Condition and an OpenMRS Condition are different. In particular, a FHIR Condition is exactly the resource to use to express an encounter diagnosis as well as an on-going problem. While, like @jteich, I don’t think there’s a good semantic reason not to store the encounter in which the condition occurred, we do have to navigate the difficulty of having diagnoses stored as Obs and problems stored as conditions. FHIR differentiates these two uses of Condition via the Condition.category field.
E.g., to build current problem list for a patient, one might use this query in FHIR:
Meanwhile, to find the diagnoses associated with a particular encounter, one might do this:
My point in posting this is just to document some of the inherent difficulties in mapping between FHIR resources and OpenMRS objects.