Mandatory elements in archetypes, and user interfaces
thomas.beale at openehr.org
Fri Nov 10 08:19:06 EST 2017
On 10/11/2017 10:24, GF wrote:
> Even when elements make no sense when both are recorded, even then
> 1..1 is a problem in Archetypes.
> It is up to the implementer to decide to restrict 0..n further in the
you can't restrict from 1..1 => 0..* in a template - it's not allowed in
any restriction algebra, of which ADL is an example.
If it is thought that no occurrnces constraint might be needed in any
derivative archetype or template, the original parent should have 0..1
or 0..* as appropriate.
More information about the openEHR-clinical