> as they should remain purely about the semantics.  There are others that
> don't agree with me.  The "hide on form" function in the Template designer
> was partly to meet requirements for documentation of the templates for some
> groups using this technology.  I am not sure if the hide_in_ui parameter is
> going to make it into the final template spec - Tom will have something to
> say about that.

I agree with Hugh - I would push back very strongly on the concept of
UI hints in the template definitions.

I'd make the point that everyone always thinks that given enough hints
computers will be able to intelligently lay out interface components (not
just in openehr world - I have seen this in many UI projects). Invariably,
the autogenerated interfaces are the exception rather than the rule - by
that, I mean that the autogenerated interfaces can be made useful but
most real users end up preferring an interface layout designed explicitly
by a human being.

The classic case in point for this is indeed the blood pressure archetype -
where any real user interface would present the data

[systolic] / [diastolic]

and yet there is no real reason why this is the case (that could be
deduced by a computer)


Reply via email to