Constant Values and sub Elements
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.
Constant Values and sub Elements
Hi TimmyX an ac constraint has been designed for defining terminology value sets by query. In your case several constraining the text ELEMENT to several at codes should do the job (the Archetype Editor supports that via 'internal codes' in the constraints tab right to the definition area. Something like that should do ITEM_TREE[at0003] matches { -- 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 {-- Default Spoken value matches { DV_CODED_TEXT matches { defining_code matches { [local:: at0006, -- bla at0007] -- blub } } } } } } } Regarding sub elements you were right: CLUSTERS are the way to do that in Archetypes! If you have a pattern which is always the same, you could create a CLUSTER-Archetype and reuse it... Cheers, Thilo On Mon, May 5, 2008 at 10: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
Constant Values and sub Elements
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
Constant Values and sub Elements
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 -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080505/f2425dfc/attachment.html
Constant Values and sub Elements
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
Constant Values and sub Elements
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
Constant Values and sub Elements
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.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 -- 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
Data-entry for OpenEhr
-- Message: 2 Date: Sun, 04 May 2008 21:40:23 +0200 From: Bert Verhees bert.verhees at rosa.nl Subject: Re: Data-entry for OpenEhr To: For openEHR technical discussions openehr-technical at openehr.org Message-ID: 481E1127.6060805 at rosa.nl Content-Type: text/plain; charset=ISO-8859-1 I would also like to start importing openEHR content into PatientOS in the new few weeks. I am less concerned with the data at this point, rather I would like to be able to take a template (perhaps initially just archetypes and I will combine them internally to be larger forms) import it and make then available as a data entry form (and display). I am debating whether to parse the XML generated by the Archetype Editor (awesome tool by the way) or leverage the java reference implementation to read an ADL and then import. I expect the XML would be quicker but more prone to break. Though at this point it is a proof of concept not a long term solution (which may use the TDS instead). I am going to use a temporary solution, to get my data into my system. It is not that important, it is only maybe 1% percent of all the code involved, and with no interface change at most places I can switch easily to another more standardized solution if it comes up, or maybe a solution a customer wants, is also possible. I took a short look at your system (is it yours, or from a team?), I couldn't find any quick pointers to the architecture behind, and the standards used. Maybe you can point me to some information. I am interested. thanks Bert The system is open source (GPL) so the team is community based and while I have been the primary contributor there are others whose contributions have been more than valuable. The archtecture is distributed with a fat client and could be described as including elements of Domain Model, MVC/ApplicationController, DTO, Gateway, Mediator, though many of the technologies help to simplify things - specifically Hibernate, JBoss using EJB 3.0, RMI. The front end is dynamically generated Swing based upon the database defined content. The database is PostgreSQL though after 1.0 we will start supporting Oracle. PatientOS XML integrates with Mirth which does the heavy lifting for HL7, X12, NCPDP, Web services etc Today (in development) you can build clinical forms with a forms wizard but there have been a few people that have expressed interest in how PatientOS could integrate with OpenEHR. So to start things off I thought I would import archetypes to generate forms but retain the archetype value path so that each data element could be mapped to a corresponding OpenEHR value. How to use that later to support AQL or OpenEHR messages is anyones guess, I will likely wait for some direction at that point from someone who needs that level of integration. I'll start with the XML generated by the Ocean Archetype Editor and let you know when those generated 'forms' can be accessed in the demo. Greg http://www.patientos.org
Constant Values and sub Elements
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
New directions for openEHR 2008
KOBAYASHI, Shinji wrote: Dear Thomas, On Sat, 03 May 2008 13:12:59 +0100 Thomas Beale thomas.beale at oceaninformatics.com wrote: - openEHR Specification Roadmap 2008 - http://www.openehr.org/specifications/spec_roadmap_2008.html I found ADL 1.5 in this roadmap. Otherwise, ADL 2.0 specification was announced last year. Would you explain the difference between ADL 1.5 and 2.0? ADL 1.5 will contain extensions for supporting openEHR templates, i.e. some extra semantics (not much). ADL 2 is a more regular syntax for archetypes. When ADL 2 is adopted, it will contain all the semantics released in all previous versions, i.e. 1.4, 1.5 etc. - thomas beale