-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alternative to JUTE $let derective proposal #3
Comments
The order is not granted, so we have to build a dependency graph and evaluate it consequentially. |
As an alternative approach we can use an extension, please check #4 for more details. |
An alternative approach that fixes issues with ordering. With this approach, we can simplify this mapper even more {
"{% let %}": [
{"idQuestion": "patientId"}, // Example of simple string
{"qr": "{{ QuestionnaireResponse.repeat(item) }}"},
{"id": "%qr.where(linkId=%idQuestion).answer.valueString }}"},
],
"resourceType": "Bundle",
"type": "transaction",
"entry": [{
"request": {
"URL": "/Patient/{{ %id }}",
"method": "PATCH"
},
"resource": {
"{% let %}": [{"phoneGroup": "{{ $qr.where(linkId='phone-group') }}"}],
"telecom": [
{
"system": "phone",
"use": "{{ %phoneGroup.where(linkId='phone-type').answer.valueString }}",
"value": "{{ %phoneGroup.where(linkId='phone-number').answer.valueString }}"
},
]
}
}]
} |
The name Examples are available as tests here
|
The text was updated successfully, but these errors were encountered: