Closed chandrashekar-s closed 4 months ago
@bashir2 The changes have been tested for the Patient
resource with us-core-profile
. For other resources it was failing because of existing issues in bunsen, will file a bug for the same. Also, for supporting multiple profiles will file another bug.
@bashir2 In the latest commit, I have added support for configuring fhir profiles via classpath names. By default, the classpath name containing the us-core
fhir profiles have been configured, but user can override them via a different directory as well.
Also, all the us-core
fhir profiles definitions have been moved to a common package and is being referenced in all the test cases now.
There are few issues which are open and are being tracked via #960 and #961.
Attention: Patch coverage is 53.41246%
with 157 lines
in your changes are missing coverage. Please review.
Project coverage is 49.61%. Comparing base (
ce08411
) to head (f39fbc7
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Thanks @chandrashekar-s for the changes; is this ready for another round of review? I mean, are the changes we discussed last week applied?
Thanks @chandrashekar-s for the changes; is this ready for another round of review? I mean, are the changes we discussed last week applied?
There are some minor documentation changes pending, will update once done (should be done today).
@bashir2 In the latest commit, I have partially addressed the issues listed in #960 and #961. I have also created the issue #980 to create a generic solution for multiple extensions. Updated the description of the PR to reflect the current implementation status.
You can review the last 2 commits now.
@bashir2 In the latest commit, I have partially addressed the issues listed in #960 and #961. I have also created the issue #980 to create a generic solution for multiple extensions. Updated the description of the PR to reflect the current implementation status.
You can review the last 2 commits now.
The description also contains a Pending Items section which will be addressed later on, not in this PR.
Side note1: The PRs Fixed
section of the description should probably be Issues Fixed
but even with that I am not sure if that causes merging this PR to close those issues.
Side note2: It is great to see how many issues are being resolved by this PR; great job.
Description of what I changed
Issues Fixed:
560
400
753
558
Pending Changes:
In the long term, we need to provide support for multiple custom profiles. This is being tracked in #980 The issues mentioned in #960 and #961 are partially fixed in the current PR.
E2E test
The application was loaded with custom
us-core-profile
definitions and the pipeline was run. The tables that were created in the spark thrift server contained the extended definitions defined in theus-core-profile
.TESTED:
Please replace this with a description of how you tested your PR beyond the automated e2e/unit tests.
Checklist: I completed these to help reviewers :)
[x] I have read and will follow the review process.
[x] I am familiar with Google Style Guides for the language I have coded in.
No? Please take some time and review Java and Python style guides.
[x] My IDE is configured to follow the Google code styles.
No? Unsure? -> configure your IDE.
[x] I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)
[x] I ran
mvn clean package
right before creating this pull request and added all formatting changes to my commit.[x] All new and existing tests passed.
[x] My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command
git pull --rebase upstream master