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

Rendering of SearchParameter conformance expectations #962

Closed
dbojicic opened this issue Oct 1, 2024 · 1 comment
Closed

Rendering of SearchParameter conformance expectations #962

dbojicic opened this issue Oct 1, 2024 · 1 comment
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates enhancement New feature or request

Comments

@dbojicic
Copy link

dbojicic commented Oct 1, 2024

It would be helpful if the conformance expectations around comparators, modifiers, chains, targets etc were clearly rendered in the narrative for SearchParameters.

AU Core, like US Core, extends the usage context of the Conformance Expectation extension to define these expectations (assuming this is a tooling 'hack' that allows this extension outside of CapabilityStatement use context) but the expectations are not included in generated narrative.

@lmckenzi lmckenzi added enhancement New feature or request Approved Change has been reviewed and accepted and can now be applied to the templates labels Oct 1, 2024
@lmckenzi lmckenzi moved this from Inbox to To do in IG Publisher issue board Oct 1, 2024
@lmckenzi
Copy link
Contributor

lmckenzi commented Oct 1, 2024

Have raised as a HAPI issue - hapifhir/org.hl7.fhir.core#1759

@lmckenzi lmckenzi closed this as completed Oct 1, 2024
@github-project-automation github-project-automation bot moved this from To do to Done in IG Publisher issue board Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants