Hi @Sidharth_Ramesh,
I love your work on medblocks UI. I saw your tutorial https://youtu.be/GRBIUEA_fc8 and I think a webcomponent as an npm package that automatically renders openEHR artefacts is very valuable for the community! I also think you made the right choice to use webtemplate as input artefact.
At Nedap we created something similar to let a user/customer (people with little to no openEHR knowledge) create (hundreds) of forms for a clinimetrics application. We use:
- A (for now) proprietary very simple adl2 editor.
- Automatically generated operational templates based on (observation) archetypes.
- A react component that renders âallâ elements in a template
It works well for our usecase. But there are very few ways to adjust layout. Only hiding headings based on annotations for now. The webtemplate brings a lot more to the table here. E.g. not rendering an element but still be able to record generated data on it.
I like the webcomponent better then our react component because we would have liked to use our component in Vue and angular applications.
We use the rules section for (most) of what you do with JavaScript functions. And I wondered wether you have tried the same. (I actually think that the rule to calculate GCS should be part of the ckm archetype, since itâs inherent to the clinical concept of GCS)