cqframework / cqframework/clinical-reasoning
QuestionnaireResponse instance selector fails
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 49
- Forks
- 43
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 13
Description
Consider the following expression:
define TestQuestionnaireResponse:
QuestionnaireResponse {
"id": id('phq-9-questionnaireresponse'),
"questionnaire": canonical('http://somewhere.org/fhir/uv/mycontentig/Questionnaire/phq-9-questionnaire'),
"status": QuestionnaireResponseStatus('completed'),
"subject": Reference {
"reference": string('Patient/example')
},
"authored": dateTime(@2021-09-13T16:29:00-07:00),
"item": {
FHIR.QuestionnaireResponse.Item {
"linkId": string('LittleInterest'),
"text": string('Little interest or pleasure in doing things'),
"answer": {
FHIR.QuestionnaireResponse.Item.Answer {
"value": Coding {
"system": uri('http://loinc.org'),
"code": code('LA6568-5'),
"display": string('Not at all')
}
}
}
},
FHIR.QuestionnaireResponse.Item {
"linkId": string('TotalScore'),
"text": string('Total score'),
"answer": {
FHIR.QuestionnaireResponse.Item.Answer {
"value": integer(3)
}
}
}
}
}
Although this translates without error, it cannot be invoked because the component types cannot be resolved by the FHIR package
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 with the supplied CQL QuestionnaireResponse expression and investigate how the FHIR package resolves its component types after translation. Reproduce the failure by attempting to invoke the translated expression; done means the component types resolve and the instance selector can be invoked successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100