Potential Idempotency Issues in the NormalizeDeviceData Function about iomt-fhir HOT 4 CLOSED

@NullPointer4096 - Just to clarify this issue, The NormalizeDeviceData function can add duplicate normalized measurements to the Event Hub when an error occurs. Is this correct?

I ask because the data processing has not completed at this point. After this first stage, the duplicate normalized measurements will be read by the MeasurementCollectionToFhir function and de-duping takes place there. The data output is idempotent at the FHIR Observation, not the normalized measurements.

Is this a performance improvement you are suggesting? Or are you using the normalized measurements for something that requires no duplicates be emitted?

from iomt-fhir.

Dear @namalu ,

Thanks for getting back to me. Pardon me for my ignorance, but I was not able to follow the invocation flow from the NormalizeDeviceData function to the MeasurementCollectionToFhir function that you have mentioned. The former seems to be outputting to event hub, and the latter seems to be taking http post triggers. In addition, I don't find the output event hub used in other functions within this repo. I wonder how these two functions are connected so that the de-dup action can happen. I would really appreciate if you can elaborate on this flow of functions. Thanks!

Best wishes

from iomt-fhir.

@NullPointer4096,

The solution uses Azure Stream Analytics as a processing step before the MeasurementCollectionToFhir Function is invoked. Azure Stream Analytics reads from the Event Hub and groups normalized measurements by identifiers and sends the normalized measurements to the MeasurementCollectionToFhir Function (via the HttpTrigger).

from iomt-fhir.