cqframework / cqframework/cql-execution
Support External Functions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 84
- Forks
- 38
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
External functions allow CQL to call custom functions that are defined natively rather than in CQL. See: https://cql.hl7.org/03-developersguide.html#external-functions
In the CQL Execution framework, this could potentially be supported by allowing integrators to pass in a map (or hash) of supported functions, for which the name of the function is the key. For example:
const externalFunctions = {
"reverse": (list: any[]) => list.reverse(),
"consoleLog": (message: string) => console.log(string)
}
External functions are generally discouraged since they impede interoperability. As such, implementation of this feature is low priority.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by reading the linked CQL external-functions guidance and the execution framework's public API to locate how integrators provide execution context. Done should include a defined approach for registering and invoking external functions, with behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100