Ok I guess pronunciation wasn't the best description of it.
in my project sample domain model the concept name really is the spoken
default.
as I've heard it will be used in the future as a common word for a concept,
i guess some medical terms which are used by med. experts which are not the
official term, like abbreviations.
ie. saying MRI instead of Magnetic Resonance Imaging.
i guess it would be a better approach to model a generic archetype which
shows how the domain model should be structured and add information at
runtime, does this make sense?
Thanks in advance
Timmy
On Tue, May 6, 2008 at 9:37 AM, Sebastian Garde <
sebastian.garde at oceaninformatics.com> wrote:
> I sent the following yesterday, but it didn't make it to the list for
> whatever reason...I had this a couple of times now that my emails to the
> openehr lists don't arrive...maybe you can check Thomas?
> In essence I agree with you Thilo...not sure this should be in the
> archetype
>
> ---
> Hi Timmy,
>
> not sure I would archetype the pronunciation of an archetype element
> within the archetype.
> Is the default pronunciation something you would want to store potentially
> with every instance of the archetype and what is the purpose of that?
> To me this sounds that the default pronunciation (Top spoken) is just like
> the name of the element (Top written): a different representation of the
> same concept, but not another data element of the archetype.
>
> Sebastian
>
>
>
> Thilo Schuler wrote:
>
> > Timmy,
> >
> > I think this speech recognition stuff is more an interface thing and
> > IMHO it doesn't belong into an archetype (if you see an archetype as a
> > means to share interoperable health information). You could have a
> > seperate XML file that tags every appropriate field to a
> > 'spokendefault' value(what would be the format? - sound file, phonetic
> > spelling,...) via the atXXXX code.
> >
> > Lets see what others think
> >
> > -Thilo
> >
> > On Mon, May 5, 2008 at 4:16 PM, Timmy K <timmyx at gmail.com> wrote:
> >
> >
> > > Sorry for being that unspecific.. The project i am working on is about
> > > speech recognition. A Software which allows med. experts to fill out
> > > a
> > > Form with speech only, so currently the xml File with the Domain
> > > Model
> > > generates a Form with Checkboxes, date Fields and so on and it
> > > includes also a spokendefault value which tells the speech
> > > recognition
> > > how this Element Name Sounds like. In the End the generated Form can
> > > be controled or navigated with speech.
> > >
> > > I would say it has to be computable.
> > >
> > > Thanks,
> > > Timmy
> > >
> > > Am 05.05.2008 um 15:11 schrieb "Ian McNicoll" <ian at mcmi.co.uk>:
> > >
> > >
> > >
> > > > Thanks Timmy,
> > > >
> > > > I am still struggling to understand the purpose of the
> > > > 'pronounciation' attribute. Does this have to be computable or is
> > > it
> > > > just for designer/user guidance? Can you give little more
> > > background
> > > > to your project?
> > > >
> > > > Ian
> > > >
> > > > On Mon, May 5, 2008 at 10: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.o
> > > >>> rg
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> _______________________________________________
> > > >>> 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
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > 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.o
> > > > rg
> > > >
> > > > _______________________________________________
> > > > 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
> >
> >
> >
> >
>
> --
>
> Ocean Informatics
> Dr Sebastian Garde
> Senior Developer
> Ocean Informatics
>
> /Dr. sc. hum., Dipl.-Inform. Med, FACHI/
>
> Skype: gardeseb
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080506/37957209/attachment.html>
