GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

Hi All, This extension idea is used in XForms in a similar manner. In fact this extension mechanism is actually something that I played with 18 months ago to represent AOM constraints of data associated with each form control expressed in XForms. I shelved this approach due to the complexity of

GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

Hi Thilo, It is interesting you have talked about the idea of scaffolding a GUI. This is exactly the work Ocean is doing at present. We have redeveloped our Web Forms engine to work based on this principle. From a template developed using the Ocean template Designer, we now generate a Form

GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

Hi! Thanks for a lot of interesting response regarding GUI-hints and other things. Please excuse a little left-to-right analogy below: There seems too be a scale or spectrum of detail level and use case specificity going from... Left: purely semantic (maximum data set) models = archetypes ...via

GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

-technical_lists.openehr.org/attachments/20080630/6c380501/attachment.html

GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

Is it true that there are two types of templates: generic ones like 'lab request' (which contains a combination of several archetypes), and a further constrained version for local usage? If so, this might mean that clinicians that are trained in openEHR could design the first kind of templates