Provide ability to provide column-based arguments to terminology functions
Open
Nobody has claimed this yet.
fhirpath
new feature
- Dominant language
- Java
- Stars
- 134
- Forks
- 24
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 8
Description
At the moment, arguments to the terminology functions (e.g. value set URI, concept map equivalence) are required to be provided as static, literal values.
We could provide the ability to supply these arguments as columns instead, with the inputs taken from a source data set.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the terminology functions and their current argument handling, then trace how source datasets provide columns. Done means terminology arguments can be supplied from columns rather than only static literal values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100