-
Notifications
You must be signed in to change notification settings - Fork 29
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 tags to test definitions and add core tag to mandatory functionality #254
Conversation
I will have a go at modifying this pull request to represent all the changes noted here: https://chat.fhir.org/#narrow/stream/179219-analytics-on-FHIR/topic/Proposal.20for.20documenting.20.22core.22.20vs.20other.20functionality/near/462650241 |
operators: [equals (=)](https://hl7.org/fhirpath/#equals), [not equals (!=)](https://hl7.org/fhirpath/#not-equals), [greater than (>)](https://hl7.org/fhirpath/#greater-than), [less or equal (<=)](https://hl7.org/fhirpath/#less-or-equal) | ||
- [Indexer expressions](https://hl7.org/fhirpath/#index-integer-collection) | ||
|
||
### Experimental FHIRPath Functions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not quite sure how to do a "big yellow box", but maybe this is good enough for now.
# Conflicts: # input/pagecontent/StructureDefinition-ViewDefinition-notes.md
Haven't got any feedback on this, so I think I'm going to go ahead and merge this now. |
This change adds a new "tags" element to a test definition.
It also uses this feature to define a "core" set of tests that cover the mandatory functionality, and boundary and join functions have been left out of this.