Mandatory elements in archetypes, and user interfaces

Pablo Pazos pablo.pazos at cabolabs.com
Fri Nov 10 12:38:45 EST 2017


Hi, there are several cases:

1. data recorded by the software: when a data element is added to the
composition by the software, doesn't need a UI element at all

2. recording null flavour: if no data is entered on the UI field (field is
not mandatory on UI), null_flavour is recorded on the element. null_flavour
can be set by the system, or there can be a null_flavour field on the UI to
let the user specify why there is no data on the field, on this case what
can be mandatory is the data field or the null_flavour for that field.

Hope that helps.



On Fri, Nov 10, 2017 at 7:47 AM, Bakke, Silje Ljosland <
silje.ljosland.bakke at nasjonalikt.no> wrote:

> Crossposting this between the clinical and implementers lists, since it
> belongs in both:
>
>
>
> In some archetypes, one or more elements are set as mandatory (typically
> occurrences 1..1 or 1..*), because the rest of the concept makes no sense
> without this particular element recorded. Examples are Problem/diagnosis
> name in Problem/diagnosis, and Temperature in Body temperature. This is not
> intended to mean that it’s mandatory to enter data into the element in a
> UI, but that this particular element is mandatory in any persisted
> composition that uses the archetype.
>
>
>
> Recently however, we received a request to change the Head circumference
> element in the Head circumference archetype from 1..1 to 0..1 because the
> element being mandatory in the archetype automatically made the UI form
> builder mandate the entering of data into the UI field, and removing the
> archetype on the fly made more unnecessary clicks. In a fit of mental
> hiccups, I agreed with and performed this change, but have since realised
> this is wrong, because:
>
> ·       A mandatory archetype element is not the same as a mandatory UI
> field
>
> ·       A mandatory UI field is more like a field where you only allow
> persisting non *null* values, while a mandatory archetype element can be
> persisted with a * null* value without a problem.
>
>
>
> How are implementers actually handling this? Do you separate UI field
> mandation and archetype element mandation?
>
>
>
> Kind regards,
> *Silje Ljosland Bakke*
>
>
>
> Information Architect, RN
>
> Coordinator, National Editorial Board for Archetypes
> Nasjonal IKT HF, Norway
>
> Tel. +47 40203298 <+47%20402%2003%20298>
>
> Web: http://arketyper.no / Twitter: @arketyper_no
> <https://twitter.com/arketyper_no>
>
>
>
> _______________________________________________
> openEHR-implementers mailing list
> openEHR-implementers at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-
> implementers_lists.openehr.org
>



-- 
Ing. Pablo Pazos Gutiérrez
e: pablo.pazos at cabolabs.com
p: +598 99 043 145
skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com
https://cloudehrserver.com
Subscribe to our newsletter <http://eepurl.com/b_w_tj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20171110/5446740f/attachment-0002.html>


More information about the openEHR-clinical mailing list