Vadim Laletin
Vadim Laletin
Currently, we have two type of drafts: server-side and local-side The server-side drafts were implemented similar to local-side: every time user edits the form (after the first editing) we save...
There's a bug in printable forms for repeating choice field. **Example:** https://emr.beda.software/patients/patient1/documents/f9dbe6fb-89f9-4bf7-9db3-ac0527811434 https://emr.beda.software/print-patient-document/patient1/f9dbe6fb-89f9-4bf7-9db3-ac0527811434 Reaction field in printable form is a single value for choice field, however it's filled as repeating.
V2.x.x
- [x] Get rid of runOnBehalfOfRoot - [x] Get rid of manifest and attributes and CREATE_MANIFEST_ATTRS - [x] Get rid of CONSTRAINT_LEGACY_BEHAVIOR - [x] Get rid of Aidbox endpoints -...
Currently, if there is an error of fhirpath expression, it is returned in OperationOutcome without information in what question and attribute it happened. Let's add information similar to how it's...
Unable to use "smart" expressions, e.g. value instead of valueDate because of lack of the model
Should be supported during populate: - Questionnaire.variable - item.variable
There's a special field [initialSelected](https://hl7.org/fhir/R4/questionnaire-definitions.html#Questionnaire.item.answerOption.initialSelected). It should be used instead of answerOption + initialCoding (it is invalid in FHIR because of que-11)
Empty question items (without answers) are removed in sdc-qrf. Only groups should be preserved
For consistency with sdc-qrf