Radiology insights GA

[koen-mertens]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• [ ] The pull request does not introduce [breaking changes]
• [ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
• [ ] I have read the contribution guidelines.

General Guidelines and Best Practices

• [ ] Title of the pull request is clear and informative.
• [ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• [ ] Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

com.azure:azure-health-insights-radiologyinsights

[weidongxu-microsoft]

There is FhirR4## classes that could be duplicated in future module from healthinsights (e.g. cancerprofiling, clinicalmatching, etc.). And it would be very hard to move them to shared lib, after GA.

Do we have a decision on this?

[hvanhoe]

There is FhirR4## classes that could be duplicated in future module from healthinsights (e.g. cancerprofiling, clinicalmatching, etc.). And it would be very hard to move them to shared lib, after GA.

Do we have a decision on this?

That has been discussed and the current decision was not to have a shared lib.

[weidongxu-microsoft]

There is discussion of the method signature of the LRO API in apiview https://apiview.dev/Assemblies/Conversation/c48b47bd12a6493aa27b2cec58f9e54e#46f262e257de451485c82b43abb61bb5

Please reach a decision (if possible in SDK review meeting, for cross-language agreement). I can help you customize this API whatever the decision be (the customize on method parameter should be very simple; the customize on method return would need some knowledge). Ping me when you need my help.

[KarolGel]

/azp run java - healthinsights - ci

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[KarolGel]

/azp run java - healthinsights - ci

[azure-pipelines[bot]]

Pull request contains merge conflicts.

[weidongxu-microsoft]

The branch seems having problem. There's 2516 files

[JimSuplizio]

The branch seems having problem. There's 2516 files There's also over 1200 Checks which pretty much amounts to the build storm that's happening. @koen-mertens I think the base way to sort this out is to rebase you branch on top of main.

[JimSuplizio]

I'm going to close this to kill the build storm and I'm going to recommend recreating the PR after rebasing.