clinical-reasoning
clinical-reasoning copied to clipboard
cqframework
CQF Clinical Reasoning on FHIR for Java
These two works good: 2019-01-01T00:00:00.0-08:00 2020-01-01T00:00:00.0-08:00 The following two is having exception 2022-01-01T00:00:00.0-08:00 2020-01-01T00:00:00.0-08:00 Git some findings: actually it throws exception when the periodEnd is lesser than the periodStart. The...
The cql-evaluator needs documentation around the APIs a platform needs to implement in order to support CQL execution and the FHIR operations. These are roughly: 1. FHIR Resource Crud 2....
Measure evaluation doesn't currently have a way to bubble up validations to the report building components. Need a way to do that, such as a list of "ValidationMessages" on the...
Currently, the population criteria must return a type consistent with the population basis, which is only allowed to be a FHIR type. We can consider an option to return a...
"Inject prefetch resources some other way, like parameters in CQL", but that breaks a whole bunch of ecosystem stuff. null = unknown empty empty = known empty otherwise = known...
Consider the following expression: ```cql 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":...
Given the following library: ```cql library QuestionnaireExtraction using FHIR version '4.0.1' include FHIRHelpers version '4.0.1' context Patient define QuestionnaireResponses: [QuestionnaireResponse] ``` Even with an appropriate test case, the result of...
The logic currently looks for the word increase/decrease, rather than using the coded improvementNotation concepts (holdover from STU3 when it was only defined as text). Update this code to use...
Unexpanded valuesets should be alerted with a "WARN" status Naively expanded valuesets should be alerted with "INFO" status
When evaluating PlanDefinition/$apply, ActivityDefinition/$apply, Library/$evaluate, and Measure/$evaluate-measure, log the URL and version of the artifact that is being evaluated.