cqframework / cqframework/clinical-reasoning
Migrate queryPattern functionality from the ruler to the evaluator
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 43
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 13
Description
The cqf-ruler implementation of $data-requirements will return DataRequirements with a fhirQueryPattern extension. This functionality should be available in the DataRequirementsProcessor directly so it can be surfaced in the evaluator as well.
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
Start by comparing the cqf-ruler implementation of $data-requirements with DataRequirementsProcessor, then trace how the evaluator consumes DataRequirements. Move the fhirQueryPattern extension behavior into DataRequirementsProcessor so it is available through the evaluator as well. Done means the evaluator can surface the same fhirQueryPattern extension returned by the ruler.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100