Is much different to change the field from 'test
result:positive/negative' to 'test result positive:true/false'?
If the semantics if not the same then the 'positive/negative' has more
meaning that a simple boolean and I think they should be coded
2011/2/2 Koray Atalag k.atalag at auckland.ac.nz:
Hi!
Good points from both of you, I just want to add a thought.
When designing or locally adapting GUIs I think it can be valuable to
have the option to use radio-buttons (or widgets with similar
visibility and semantics) also for DV_CODED_TEXT items if you know
that the number of options are
Hi Diego, thanks for your points...
I agree that changing data item to 'Test X result Positive: True|False' is the
right way to use Boolean data type...But while this is an elegant technical
approach it has problems in two ways (in my opinion):
1) From modelling point of view the non-techy
-technical_lists.openehr.org/attachments/20110202/14ec39b2/attachment.html
That seems a clear 'null flavour' use case
2011/2/2 Fabiane Bizinella Nardon fabiane at tridedalo.com.br:
I came across this problem several times. It became almost impossible to use
DV_BOOLEAN. The worst problem is that since DV_BOOLEAN has to be always true
or false, if someone simply does
was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110202/3445d84f/attachment.html
-technical_lists.openehr.org/attachments/20110202/b483f348/attachment.html
hope is that this message
helps more than it hurts.
Previously parts of a board announcement said...
*
*
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110202/460c9e09
8 matches
Mail list logo