mb-formexports data according to the openEHR simSDT data format. The paths are automatically generated from the openEHR web template by the VSCode extension and the
pathattribute are set for the custom elements. Once the data is filled out in these fields, the internal data property gets populated. These are then serialized to the simSDT format when the submit button is clicked.
mb-contextelements are smartly populated during submit. Things like time, event, category, setting, language, encoding are auto-populated. This can be overridden by setting the
<mb-fhir-form>supports translation of paths and Medblocks UI components into FHIR resources and Questionnaires.
code, these need to be explicitly stated in the
datatypeattribute - eg: in
mb-formweb component has a
pluginproperty that can be replaced by any other class with the following interface:
mb-formand translates it to the desired output which is emitted as the detail of the
mbElementsprovides an object with the
pathas the key and the Custom HTML Element (
EhrElement) as the value. You can process the data in the HTML element, usually in the
dataproperty, and provide the serialized output that you desire.
importmethod of the form is called. Responsible for returning the internal state of the form, so that it can be bound to the
dataproperty of the custom elements.
mbElementsas well as the unprocessed
datato be parsed. The function must return an object with the
pathas keys, and the
datato be set on the HTML Elements' data property.