Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] What's the purpose of Stream Analytics? #77

Closed
giacomodeliberali opened this issue Nov 20, 2020 · 1 comment
Closed

[Question] What's the purpose of Stream Analytics? #77

giacomodeliberali opened this issue Nov 20, 2020 · 1 comment

Comments

@giacomodeliberali
Copy link

giacomodeliberali commented Nov 20, 2020

We have successfully deployed the connector, but I still haven't figured out the Stream Analytics role. I saw #68, and I was wondering the implications of directly invoking the FHIR conversion function from the normalized data Event Hub, as #68 seems to be doing.

Do you have any plan to merge that pull request? Can we safely get rid of the SA? Does it have anything to do with Output Error Policies for failed jobs? Or is it only meant to efficently support SampledData measurement type?

Sorry for all those questions but I'm trying to clarify my ideas 😅

@dustinburson
Copy link
Member

Hello @giacomodeliberali,

Stream Analytics is used to group and buffer data prior to converting to FHIR. The main reason is for efficiently supporting the SampledData type and the different grouping strategies like hourly observations of data or correlation id assosication.

If you don't plan on using SampledData to render time series data you could technically remove SA though you would need to replace the HttpTrigger Azure function with an EventHubTrigger from the Normalized Event Hub directly. One down side to removing SA, even if you don't need to generate SampledData is if you have a device that sends duplicate data it will result in multiple updates on the FHIR server

The PR your referenced, #68, we don't plan on completing as is. This was a prototype work stream the team was investigating. The team is working on a more full featured version that is currently in PR #78. You are welcome to use once complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants