Re: Problem displaying a self constructed archetype

[Bert Verhees <bert.verhees@rosa.nl>]

> this is correct; the ADL for what you want, if you are using a 
> DV_BOOLEAN, would look like this:
>
> definition matches {
>     AD[at0001] matches {
>        complexContent existence matches {1..1; unordered} matches
>           BOOLEAN matches {
>              value matches {true, false}
>           }
>     }
> }
>
> It depends on what your reference model says: if it says that 
> complexContent is of type Boolean, then your ADL is correct; if it 
> says that it is of type DV_BOOLEAN, then the ADL I have given above is 
> correct.

Thanks, Thomas, your answer is very helpful, it is in fact the 
CompexContent is not a Boolean. ComplexContent is  XSD-syntax telling 
that the complex content of a complex type will be described from this 
point. In this case, a boolean is part of the complex content of the 
type AD (which is address in HL7)

<explanation of why I do this>
I read in your documents that there is a match for almost all HL7 
datatypes to OpenEhr datatypes, except for addresses, names, and a few 
more. That is why I create archetypes for them (I generate them from 
XSD-files), so that I can automatically convert from HL7 to OpenEhr 
datatypes, and as I planned, start with a one to one storage from HL7 
PrimaryCare DMIM in OpenEhr, and later move to a OpenEhr reference 
model, and being able to do that step by step, and having an application 
running in a few weeks, with 90% of the code of it generated
</explanation of why I do this>


> Note that unless AD is a container, it can't have "cardinality", only 
> "existence" (I am assuming in the above it is not a container).
AD is the name of the HL7 type which is reflected here. So it is a 
container, I did not want to use OpenEhr terminology to be clear what 
the meaning is.

regards
Bert