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

Guide people to use 'element' rather than FHIRPath when their extension contexts are elements #819

Closed
lmckenzi opened this issue Dec 4, 2023 · 1 comment
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates enhancement New feature or request

Comments

@lmckenzi
Copy link
Contributor

lmckenzi commented Dec 4, 2023

We found a whole bunch of extensions defined with a context type of 'FHIRPath' where it turns out that the context expressions were simple elements. This means that these extensions won't show up correctly in the cross-reference lists and may create confusion for systems that don't support FHIRPath-based extension contexts.

We should check the contexts for expressions and if they are in fact simple element paths, we should at least spit out a warning that says "The context expression seems to be a simple element path rather than a FHIRPath. The context type should likely be 'element'."

@lmckenzi lmckenzi added enhancement New feature or request Approved Change has been reviewed and accepted and can now be applied to the templates labels Dec 5, 2023
@grahamegrieve
Copy link
Contributor

This is done now

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