Stream: implementers
Topic: Number of Previous Operations
Mohsen Jafari (Jul 15 2021 at 07:46):
Is it possible to store "Number of Previous Operations" in Condition resource?
Mareike Przysucha (Jul 15 2021 at 09:48):
I think this case is similar to this one about number of previous hospitalization.
I would not advise to add it to a condition: A condition may last longer, but the number of previous operations may change over time. Also you have to distinguish: Number of operations in total or related to a condition.
Therefore you could either count the number of procedures with a code indicating an operation, which are related to the condition in question; or if you don't have these procedures you could use an observation focussing the condition.
At least it's my point of view, others might see it differently.
Daniel Venton (Jul 15 2021 at 12:21):
I almost copied and pasted my previous answer, but yes, don't look for new places to add custom values/attributes. Find a way to get the info you need with the existing structures. That way everybody shares the same interface, shares the same documentation, shares the same info in the same way. In this situation, search for all the procedures that you consider an operation AND that reference the condition you are concerned with. For calculable fields (sums, avg, etc.) get the base data and do the math, that way if the base data changes between now and then, your calculation stays up to date, just in time.
I'll admit that there may be a situation where the data you want just isn't available on any resource (or set of resources) and that's when you go to HL7 and say, "We need to store X attribute on Y resource." But it'll probably never be an sum/avg for a point in time.
Last updated: Apr 12 2022 at 19:14 UTC
