Thanks Thilo,
although this might not be worth it, i will try to model a generic element
as cluster-archetype.
also i dont quite understand what you meant with
"model the 'spoken default' explicitly with a text ELEMENT that is
preset to the constant value."
how would i do that if i wanted to add a "spoken default field" to a date
field?
thanks in advance
Timmy
On Mon, May 5, 2008 at 12:36 PM, Thilo Schuler <thilo.schuler at gmail.com>
wrote:
> Timmy,
>
> I guess in your case with so littel elements I would bite the bullet
> and model the 'spoken default' explicitly with a text ELEMENT that is
> preset to the constant value.
>
> An option would be to model a generic element as a CLUSTER-archetype
> (including the 'spoken default' element) and specialize an from it for
> every element you need. These specialised CLUSTERS could be assembled
> in an OBSERVATION archetype via slots. But it think this would be to
> complex for such a simple model and the specialisation would not
> provide much added value.
>
> Cheers, Thilo
>
> On Mon, May 5, 2008 at 11:53 AM, Timmy K <timmyx at gmail.com> wrote:
> > Hi,
> >
> > sure, it consist of a parent node and several child nodes, which
> describes
> > the appearance of a patient.
> >
> > structured by
> > -common information
> > weight
> > birthdate
> > height
> > -face
> > --eyes
> > color
> > --mouth
> > --nose
> >
> > and so on
> > all elements have an attribute which says how it should be pronounced
> which
> > is constant.
> >
> > Thanks for the quick replies.
> > Timmy
> >
> >
> >
> > On Mon, May 5, 2008 at 11:35 AM, Ian McNicoll <ian at mcmi.co.uk> wrote:
> > > Hi Timmy,
> > >
> > > Can you explain the domain model in a little more detail?
> > >
> > > Ian
> > >
> > >
> > >
> > >
> > >
> > > On Mon, May 5, 2008 at 9:58 AM, TimmyX <TimmyX at gmail.com> wrote:
> > > >
> > > > Hello!
> > > >
> > > > Within the context of my bachelor thesis, i am trying to transform
> a
> > domain
> > > > model into an archetype, but now i am having some problems and i
> hope
> > maybe
> > > > some of you here can help me.
> > > >
> > > > My first question is, is it possible to define constant or "hard
> coded"
> > > > values ie. constant text which contains a description?
> > > > So far I am trying to add a CODED_TEXT that matches a defined
> > constraint
> > > > ac0001, but i am not sure if this is a valid solution.
> > > >
> > > > ITEM_TREE[at0003] matches { -- ITEM_TREE
> > > > items cardinality matches {0..*; unordered} matches
> {
> > > > CLUSTER[at0004] occurrences matches {0..1}
> > matches { -- Top
> > > > items cardinality matches {0..*;
> > unordered} matches {
> > > > ELEMENT[at0005] occurrences
> > matches {0..1} matches { -- SpokenDefault
> > > > value matches {
> > > >
> DV_CODED_TEXT
> > matches {
> > > >
> > defining_code matches {[ac0001]} -- Top
> > > > }
> > > > }
> > > >
> > > > and the other question
> > > > How do i add "sub-elements", is it even possible? ie. I have a Text
> > field
> > > > "Top" and i want to add a Text field "SpokenDefault" to it, which
> shows
> > how
> > > > to pronounce the word Top. the way i do it right now is creating a
> > cluster
> > > > for every "element" which is not very effective.
> > > >
> > > > thanks in advance
> > > > TimmyX
> > > > --
> > > > View this message in context:
> >
> http://www.nabble.com/Constant-Values-and-%22sub%22-Elements-tp17053994p17053994.html
> > > > Sent from the openehr-technical mailing list archive at Nabble.com.
> > > >
> > > > _______________________________________________
> > > > openEHR-technical mailing list
> > > > openEHR-technical at openehr.org
> > > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
> > > >
> > >
> > >
> > >
> > > --
> > > Dr Ian McNicoll
> > > office +44(0)141 560 4657
> > > fax +44(0)141 560 4657
> > > mobile +44 (0)775 209 7859
> > > skype ianmcnicoll
> > >
> > > Consultant - Ocean Informatics ian.mcnicoll at oceaninformatics.com
> > > Consultant - IRIS GP Accounts
> > >
> > > Member of BCS Primary Health Care Specialist Group ?
> http://www.phcsg.org
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > openEHR-technical mailing list
> > > openEHR-technical at openehr.org
> > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
> > >
> >
> >
> > _______________________________________________
> > openEHR-technical mailing list
> > openEHR-technical at openehr.org
> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
> >
> >
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080505/02bc5923/attachment.html>
