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

Add x-fhir-query enhancement #1844

Merged
merged 37 commits into from
Apr 6, 2023
Merged

Add x-fhir-query enhancement #1844

merged 37 commits into from
Apr 6, 2023

Conversation

omarismail94
Copy link
Contributor

@omarismail94 omarismail94 commented Feb 6, 2023

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Fixes #1658

Description

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

In this PR, we pass in the context as a JSON string which we then parse. I tried passing in the context as an ID only, so that it can be fetched, but we cannot use the xFhirQueryResolver to fetch the resource as the query Resource/Id does not work

Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)

Screenshots (if applicable)

Checklist

  • I have read and acknowledged the Code of conduct.
  • I have read the Contributing page.
  • I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
  • I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
  • I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
  • I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
  • I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

@KhumboLihonga
Copy link

@omarismail94 @jingtang10 Just bringing awareness to this as I see this was marked for review 3 weeks ago but there hasn't been an update since.

@omarismail94
Copy link
Contributor Author

thanks @KhumboLihonga for the ping! We were busy working on the 1.0.0 SDC release and now that's over we can re-focus on this. I updated the PR and will talk to @jingtang10 and team on getting a review

Copy link
Collaborator

@jingtang10 jingtang10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍👍👍

@omarismail94 omarismail94 enabled auto-merge (squash) March 10, 2023 22:34
Copy link
Collaborator

@jingtang10 jingtang10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks omar - discussed... please see http:https://build.fhir.org/ig/HL7/sdc/StructureDefinition-sdc-questionnaire-launchContext.html and make sure we're matching the launch context code with the resource provided using the new arg.

Copy link
Collaborator

@jingtang10 jingtang10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think the launch context is actually coming from a value set containing a small set of resource types. so please make sure you're enforcing that and that there is documentation.

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

Successfully merging this pull request may close these issues.

Enhance x-fhir-query to handle fhirpath expression
4 participants