Current need in multi-openEHR-vendor projects (in Sweden) where we would like at least some GUI/form logic to be authored once and then reused in several different vendor solutions (Cambio, Tieto/Better, SECTRA structured forms, perhaps NeoEHR?)
Previous mail list discussions (2008) regarding GUI-hints in openEHR templates. Some highlights:
Start some experiments with template annotations reusing most of the design patterns of “EnableWhen” in FHIR Questionnaires that could optionally be used by form building tools as input for creating (possibly vendor specific) conditional logic in forms (like now available in e.g. Better’s and Cambio’s tools)
Maybe later look at
“Presentation mode visibility” annotations - see option in Better’s EHR studio
“Hide on form” - e.g. useful for marking medium level branch levels that are needed for logic storage structure but not contributing to understanding at a GUI-level in the template-specific use case.
LOD - level of detail annotations - subtrees/parts that can be initially collapsed/hidden when screen space (or attention span) is limited. (Like the “More…”-buttons in Clinergy/PEN&PAD)
SelectWhen - Select a multiple choice when a condition is met
Copy data between fields (and possibly discuss the Pandora’s box of “simple” calculations)
Discussions (all):
considers rules from ADL - (Definately useful within an archetype - with ADL2 possibly also in templates across data from different archetypes?)
Nedap is using these rules, need to ask Pieter Bos for feedback