License and copyright of archetypes

of reciprocity and would like to advocate for it, a license shouldn't become a hindrance for the broad usage of openEHR archetypes and/or a 'paper tiger' as we call it in the Netherlands: don't create rules which you can't (or don't want to) follow up) Op 14 sep 2009, om 12:14 heeft Erik Sundvall het

License and copyright of archetypes

). For example, one of those reserved rights is the ability of the author to re-license his work or a new version of it. As you say, the best solution seems to be having both to assure the right of the authors and to show clearly how archetypes can be used (those from the CKM or any other

License and copyright of archetypes

of the authors and to show clearly how archetypes can be used (those from the CKM or any other public archetype repository). As I said in my previous mail, this will require to add a license field to the archetype description section to include it. Best regards, David 2009/9/9 Sam Heard

Medinfo 2010.. Re: clinically useful set of archetypes for a connectathon demo

On Wed, 2009-09-02 at 12:22 +0100, Tony Shannon wrote: Thanks Eric I'll have to admit I dont fully understand that question... not sure if thats a good or bad thing ;o) I am keen to help agree on a starter set of archetypes to use for the demo, though I'm coming at this from purely

License and copyright of archetypes

Dear all, These days I have been thinking about the legal issues involving the use of existing archetypes. I have seen that openEHR archetypes available on the Clinical Knowledge Manager are all Copyright (c) 200X openEHR Foundation. But, what does this exactly implies? I can download them freely

License and copyright of archetypes

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090901/54dc6e8b/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

License and copyright of archetypes

for discussing this - http://www.openehr.org/wiki/display/oecom/Archetypes+-+Copyright+and+Licensing - thomas beale David Moner wrote: Dear all, These days I have been thinking about the legal issues involving the use of existing archetypes. I have seen that openEHR archetypes available

Medinfo 2010.. Re: clinically useful set of archetypes for a connectathon demo

Hi! In addition to deciding on archetypes to use, I believe circulating a couple of complete instance examples fairly soon (this week?) would be very helpful in detecting differences in specification interpretations. Having more than one archetype editor certainly helped detect differences

Publication of the Blood Pressure and the Body Mass Index archetypes today

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090823/fdb627ed/attachment.html

Loading archetypes referenced by ArchetypeSlots

Hi, I'm doing some archetype modeling and loading tests with Java Ref Impl. I have two ACTION archetypes and a COMPOSITION archetype that references the two ACTION archetypes: content cardinality matches {0..*; unordered} matches { allow_archetype ACTION occurrences matches {0..1} matches

Next archetypes for review in CKM

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090804/317460f6/attachment.html

Results of the openEHR poll - Top archetypes/concepts for use in an Emergency

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090727/00c22eb8/attachment.html

Vote on the next archetypes for review in CKM

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090714/68612443/attachment.html

openEHR / ISO 13606 archetypes - licensing and copyright .... again!

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090714/b8871151/attachment.html

Representing knowledge in Archetypes/Templates or external rules

[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Pariya Kashfi Sent: den 1 juni 2009 10:12 To: For openEHR technical discussions Subject: Representing knowledge in Archetypes/Templates or external rules Dear All, I have encountered a question regarding knowledge representation during

Representing knowledge in Archetypes/Templates or external rules

-type nodes (often within section for clarity) and to model any equivalent clinical statement archetypes in a separate section. e.g. SECTION.Questionnaire OBSERVATION.PreopQuestionnaire.v1 Relevant medication (DV_CODEDTEXT) Atenolol Y/N Furosemide Y/N Aspirin Y/N Relevant

Representing knowledge in Archetypes/Templates or external rules

of the question-type nodes (often within section for clarity) and to model any equivalent clinical statement archetypes in a separate section. e.g. SECTION.Questionnaire OBSERVATION.PreopQuestionnaire.v1 Relevant medication (DV_CODEDTEXT) Atenolol Y/N Furosemide Y/N

Representing knowledge in Archetypes/Templates or external rules

the patient as e.g X- affected. Secondly, to represent this knowledge in Templates/ Archetypes I am designing. It can be in the form of an Item-Tree- Medication-List using internal codes ( to specify medications that may be selected in the drug list). And to check this node at runtime or during

SLots in archetypes

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090530/57a0e949/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

SLots in archetypes

Hi For that example, you should use a section archetype to group the physical examination and lab results archetypes together within A symptoms and signs heading. The key thing to understand is that these headings, though useful for humans, have no semantic value and should not normally

SLots in archetypes

Hello, In archetype-editor one item type is Slot which only accepts archetypes in form of Cluster or Element as constraint on that slot. Is there any way to put a slot for including one Observation in another? Is the only way of putting two Observations together is using templates

SLots in archetypes

is Slot which only accepts archetypes in form of Cluster or Element as constraint on that slot. Is there any way to put a slot for including one Observation in another? Is the only way of putting two Observations together is using templates? Regards Pariya MSc; PhD Candidate Department

Enquiry - status of academic work on openEHR / archetypes / related

The page http://www.openehr.org/shared-resources/usage/academic.html shows what we currently know of academic (including university hospital) work with openEHR, archetypes etc. This is a request for updates and additions to these pages. One of the goals of these pages is to help other people

SLots in archetypes

Hi Ian, Thanks for your response. In my case, I intend to use some existing Archetypes in my own observation. Having one Cluster/section named Status and Signs, I want to put two existing archetypes named Observation: Laboratory Values and Observation:Physical Examination into that. Re

SLots in archetypes

On Fri, 2009-05-29 at 16:56 +0200, Pariya Kashfi wrote: Hi Ian, Thanks for your response. In my case, I intend to use some existing Archetypes in my own observation. Having one Cluster/section named Status and Signs, I want to put two existing archetypes named Observation: Laboratory Values

Implicit semantics within Archetypes?

Hi, I think ADL has proved to be a pretty good knowledge modelling language and that the growing number of archetypes represents a good deal of clinical knowledge. What is lacking is the ability to define relationships and their types between nodes or even nodes in other archetypes. I don't

Tool for validation of archetyped RM instance against corresponding archetypes?

Georg Duftschmid wrote: Dear all, I am looking for a tool that allows to validate an instance of the reference model, which complies with one or more archetypes, against these archetypes. Is such a tool available? Thank you for any help, Georg probably it should be pointed out

Demographics Archetypes

Enviado desde mi BlackBerry? de Vodafone -Original Message- From: Tim Cook timothywayne.c...@gmail.com Date: Fri, 19 Sep 2008 19:21:17 To: edrs22 at yahoo.com; For openEHR technical discussionsopenehr-technical at openehr.org Subject: Re: Demographics Archetypes

Demographics Archetypes

All, ? When I try to pull the demographics archetype from the following link on the OpenEHR website, I get a 404 error. Can someone test to see if they get the same error? ? http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr/demographic/openehr-demographic-person.person.draft.html

Demographics Archetypes

I do 2008/9/19 Eddy Rospide edrs22 at yahoo.com: All, When I try to pull the demographics archetype from the following link on the OpenEHR website, I get a 404 error. Can someone test to see if they get the same error? http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr

Demographics Archetypes

There are some here: http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr/demographic/ but at least some of them do not conform to the openEHR RM. --Tim On Fri, 2008-09-19 at 11:46 -0700, Eddy Rospide wrote: All, When I try to pull the demographics archetype from

Creating Archetypes based on questionaire + methodology

on 3-7-2008 15:20 Heather Leslie wrote: Hi Paria, I have just uploaded a tutorial to Ocean?s new website ? went live only tonight;-) I have just devised it recently for use in introductory training for clinicians in building archetypes. This might be a useful starting point for you

Archetypes for EN13606 RM

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080808/9ba336ae/attachment.html

Archetypes for EN13606 RM

Hello Pablo, EN13606 (now ISO 13606) archetypes follow the same archetype model and ADL syntactic representation as openEHR. What changes is the underlying Reference Model, what you do is to constraint its specific classes and attributes. OpenEHR archetypes are not directly compatible

Regex in Archetypes must include TYPE

Thomas Beale wrote: Sam Heard wrote: Hi Adam I take this point and in that case I would suggest that resulting issue to discuss is: Should we drop the class name from the Archetype Slot in ADL and just use the regex? There does not appear to be any reason in the AOM to include the

Regex in Archetypes must include TYPE

Peter Gummer wrote: Sam Heard wrote: ... What we have been doing is setting the regex to: openEHR-EHR-CLASS_NAME\.REGEX_EXPRESSION This is not quite right because REGEX_EXPRESSION might contain patterns for multiple concepts, as Adam mentioned. You would have to wrap it

Regex in Archetypes must include TYPE

Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-bounces at openehr.org] On Behalf Of Thomas Beale Sent: 04 August 2008 12:12 To: For openEHR technical discussions Subject: Re: Regex in Archetypes must include TYPE Adam Flinton wrote: No need to do

Regex in Archetypes must include TYPE

Thomas Beale wrote: I also agree with Adam. A regex should be able to be used over a population of strings (identifiers in this case) and have the effect of filtering out what you want. ... Practically speaking this does not change the specifications, but I suspect we should put some

Regex in Archetypes must include TYPE

Well the problem here is that the specifications don't actually say anything about the regexes, or even that you have to use regexes to identify archetypes in slots - it is just one way of doing it. So any tools today that take a particular approach to regexes are already outside the standard

Regex in Archetypes must include TYPE

on is the Archetype ID. As such that should be the basis of the regex. doing a pseudo-meta regex will hurt in the long run. Quick example: NB: These are simply examples are not intended as a source of discussion in of themselves. Imagine English speaking people want to use archetypes whose names have

Regex in Archetypes must include TYPE

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080722/6cbd2e54/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanInformaticsl.JPG Type: image/jpeg Size: 5828

Regex in Archetypes must include TYPE

Sam Heard wrote: Hi Thomas I had a look at the AOM and did not see anything, just include and exclude statements - didn't read the ADL spec. The point here is that we could have a slot that allowed different classes which would simplify things for the archetype authors. in the AOM all

Regex in Archetypes must include TYPE

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080720/edae79d2/attachment.html -- next part -- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 5828 bytes

Regex in Archetypes must include TYPE

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080719/6364712b/attachment.html -- next part -- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 5828 bytes

Regex in Archetypes must include TYPE

Sam Heard wrote: Hi Adam I know Tom has talked to you about this. I was involved in the original discussions about this many years ago and many points of view were expressed. The issue is that, as you know, the CLASS is specified in the slot definition and there is a regex for the

Regex in Archetypes must include TYPE

On Fri, 2008-07-18 at 10:59 +0100, Adam Flinton wrote: I repeat...: If you want to use a regex then use a regex which is useable as a regex. At present it is not for no good reason. i.e. saying take the pseudo-regex append xyz to it to create the real regex is both error prone

proposal for managing migration to .adls (source form) archetypes

Dear Tom, When you say: there is the intention to move toward what we call 'source form' or 'differential' archetypes, whereby archetypes contain only changes with respect to a specialisation parent archetype how has this intention arisen, and become intended? Has there been an analysis

proposal for managing migration to .adls (source form) archetypes

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080718/d237c3b7/attachment.html

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080717/061f6655/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanInformaticsl.JPG Type: image/jpeg Size: 5828

Archetypes including inherited content

Dear All, Given we have a lot of archetypes which are then further versioned etc moving archetypes from one version to another can become a real pain based on their inherited content. i.e. if B.v1 specializes A.v1 then it includes the content of A.v1 If we then create an A.v2 wish to create

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

, it is difficult to achieve without [at-code] markers as we have on higher-level nodes in archetypes. Currently, no at-codes are used on objects nodes defining constraints on the ELEMENT.value attribute, becasuse none is needed - it does not add anything useful, and would require pointless pollution

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

of specialisation, we have the problem that if the above kind of constraint were stated, and needed to be specialised in a child archetype, it is difficult to achieve without [at-code] markers as we have on higher-level nodes in archetypes. Currently, no at-codes are used on objects nodes defining

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

Ian McNicoll wrote: Hi Thomas, Other than the requirement for specialisation, am I correct in thinking that this would give us 'named choices' which I have suggested in the past (along with named slots)? This would be very helpful in understanding the thinking behind the choice

Creating Archetypes based on questionaire

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080708/46019882/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanInformaticsl.JPG Type: image/jpeg Size: 5828

Reusable Archetypes

Hi again Paria, Your concerns are definitely not unreasonable. Building archetypes ideally needs some reasonable RM knowledge and training, but templating using an agreed/published set of archetypes is something that could be achieved by many at the local level with a minimum of training

Reusable Archetypes

to build archetypes for orders and results. Someone who doesn't understand that there are 5 or so quantity data types might make the mistake of using the Quantity one for everything. The semantics of the RM that need to be understood in this way probably constitute somewhat over 50% of the total

Creating Archetypes based on questionaire + methodology

Hi Paria, I have just uploaded a tutorial to Ocean?s new website ? went live only tonight;-) I have just devised it recently for use in introductory training for clinicians in building archetypes. This might be a useful starting point for you ? http://www.oceaninformatics.com/ocean

Reusable Archetypes

sounds simple at first glance but is a tedious task. It seems to me that one should be aware of all existing Archetypes and their ingredients ( data section at least) to be able to recognizing Archetypes that may be used for the case, as bases for Template. Otherwise, How one can realize how

Creating Archetypes based on questionaire

Dear Sam, Thank you for your response, Now, I'm taking a look at existing archetypes to find if they will be useful for my case or not. Having an idea of the keyword to be searched is important itself! is there any other way to view all existing archetypes? Anyway, I used web service to find

Creating Archetypes based on questionaire + methodology

As Sam wrote there are a number of approaches that help creating archetypes. Is there any booked methodology or approach available? does anyone know any useful reference for it? Regards paria On Jul 2, 2008, at 1:34 PM, Sam Heard wrote: Hi P?ria... P?ria Kashfi wrote: It means

Creating Archetypes based on questionaire

Hi Paria, Now, I'm taking a look at existing archetypes to find if they will be useful for my case or not. Having an idea of the keyword to be searched is important itself! is there any other way to view all existing archetypes? http://www.openehr.org/svn/knowledge/archetypes/dev/html

Creating Archetypes based on questionaire

Thanks to Ian, Does the list locating here http://www.openehr.org/svn/knowledge/archetypes/dev/html/index_en.html include all existing Archetypes? I mean at least all reliable and examined ones? in that case, If I cannot find the archetype I need, I should start another step to create a new

Creating Archetypes based on questionaire

Anyway, I used web service to find archetypes, there is a mind map file relating to each archetype, is there any way to save the mm file ? I can just open it in firefox .mm files are Freemind files - free download at: http://freemind.sourceforge.net/wiki/index.php/Download Hi P?ria

Creating Archetypes based on questionaire

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080702/86e69ea1/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanInformaticsl.JPG Type: image/jpeg Size: 5828

Archetypes - regex question

Sam Heard wrote: Hi Adam This is another example of the approach to be as specific as possible. The exclude statement can be used to exclude specific archetypes and the Include ALL in this case means that all others are allowed. If the Exclude ALL statement is added to an archetype

Archetypes - regex question

to revisions of the existing ones, deletions and new to be added might lead to inconsistent calls to archetypes over time. I believe such constraining should not take place on the archetype over archetype level, but at the (OpenEHR) template level. In here you can be explicit in what is to be included

Archetypes - regex question

Thomas Beale wrote: Andrew Patterson wrote: Sam, without putting words in Adams mouth, I think he was asking about the precedence of include/exclude sections. It is a common problem is coming up with rule system like this - for instance one can look at the allow/deny pattern of the

Archetypes - regex question

is completely unconstrained. Therefore, all archetypes are in the include list. * Excluding some archetypes shifts them to the exclude list. * Excluding all shifts all archetypes into the exclude list. * Including some archetypes overrides exclusion, moving them back to the include list. * Include

Archetypes - regex question

This is another example of the approach to be as specific as possible. The exclude statement can be used to exclude specific archetypes and the Include ALL in this case means that all others are allowed. If the Exclude ALL statement is added to an archetype, it means ONLY those specifically

Archetypes - regex question

and new to be added might lead to inconsistent calls to archetypes over time. I believe such constraining should not take place on the archetype over archetype level, but at the (OpenEHR) template level. In here you can be explicit in what is to be included or excluded. Hi Adam

Archetypes - regex question

William, It is potentially dangerous ground. But ... - Archetypes express what can be documented about a specific topic. Since such a 'Real Archetype' can or will consist of re-usable patterns, 'Real Archetypes' consist many times of a collection of sub- archetypes that express recurring

Fwd: Re: xml archetypes to xforms

--- Ime Asangansi asangansi at yahoo.com wrote: Date: Wed, 9 Apr 2008 10:51:50 -0700 (PDT) From: Ime Asangansi asangansi at yahoo.com Subject: Re: xml archetypes to xforms To: adam.flinton at nhs.net Hi Adams, Please find my comments below: I have the XForms Engine up on the OHT

xml archetypes to xforms

Hi Adams et al, Nice to hear that. But I think the tough issue is converting the archetypes xml to xforms. Please how do you do that? especially converting the definition section... Just to add this: we are shifting from Infopath... It has never been a nice thing to be locked into that. Thats

xml archetypes to xforms

Ime Asangansi wrote: Hi Adams et al, Nice to hear that. But I think the tough issue is converting the archetypes xml to xforms. Please how do you do that? especially converting the definition section... there are already answers to this, but you don't want to convert archetypes to Xforms

xml archetypes to xforms

Hmm... yes, thanks for that correction looking forward to that... Ime --- Thomas Beale thomas.beale at oceaninformatics.com wrote: Ime Asangansi wrote: Hi Adams et al, Nice to hear that. But I think the tough issue is converting the archetypes xml to xforms. Please how do you do

xml archetypes to xforms

Ime Asangansi wrote: Hi Lisa, Thilo et al, Really appreciate your comments... I have the impression that much still has to be done about Xforms... OpenMRS is based on infopath for now, so I am now looking at archetypes as form templates (.xtp files). These are relatively reusable form

xml archetypes to xforms

Hi Lisa, Thilo et al, Really appreciate your comments... I have the impression that much still has to be done about Xforms... OpenMRS is based on infopath for now, so I am now looking at archetypes as form templates (.xtp files). These are relatively reusable form parts and are analogous

Understanding XML archetypes..

Oxford Partnership wrote: Erik Many thanks for the quick reply. I have no issues with the two level models used in OpenEHR, it makes perfect sense to me to have an underlying RM for all archetypes to be based on. If I am understand you correctly, then : - No attributes within

Understanding XML archetypes..

An archetype not based on a reference model is impossible (or at least pointless). Erik Sundvall Erik, I love this comment, it should be put up on the openEHR Web Site as the Play of the Day. So many times I see people trying to use Archetypes without a RM, or even worse using openEHR

Understanding XML archetypes..

of templates where individual RM attributes can be turned on or off, right down to the data type attributes if needed. We are also looking at alternate visualisation of archetypes for the next iteration of the Ocean Archetype Editor. Regards ? Heath ? Heath Frankel Product Development Manager Ocean

Understanding XML archetypes..

in OpenEHR, it makes perfect sense to me to have an underlying RM for all archetypes to be based on. If I am understand you correctly, then : - No attributes within an OpenEHR class can be assumed to be mandatory within the XML representations, as in all cases the RM can

Understanding XML archetypes..

Heath Frankel wrote: An archetype not based on a reference model is impossible (or at least pointless). Erik Sundvall Erik, I love this comment, it should be put up on the openEHR Web Site as the Play of the Day. So many times I see people trying to use Archetypes without a RM, or even

Understanding XML archetypes..

I have been looking at the OpenEHR Information Model ( ehr_im.pdf ) to get a better understanding of the underlying classes used within the OpenEHR. Whilst I am beginning to understand the main classes used within the archetypes, I am still confused as how they make it to the XML version

xml archetypes to xforms

Hey Lisa, ime et al back from skiing - had 6 sunny days and time. Thanks for the valuable replies. Comments inline... Hi Ime, Thilo and all We investigated using XForms for automatically-generated data entry GUIs last year. There are some features of XForms which made it seem

Understanding XML archetypes..

Erik Many thanks for the quick reply. I have no issues with the two level models used in OpenEHR, it makes perfect sense to me to have an underlying RM for all archetypes to be based on. If I am understand you correctly, then : - No attributes within an OpenEHR class can be assumed

Understanding XML archetypes..

guess you mean attributes of an OpenEHR _RM_ class within XML representations of _archetypes_. (Some things in the AM are mandatory in archetypes.) In the XML representations of _archetypes_ I don't think any RM attributes are _mandatory_ but an empty archetype would be of limited value... (I hope

xml archetypes to xforms

Ime Asangansi wrote: Thilo and others, Thanks for this remarkable and engaging read! This will come in helpful in the project... BTW: This is a really supportive community But it will be nice to hear from the guys who did the things you outlined... It will be nice to have such a

xml archetypes to xforms

towards a pure full blown open-source openehr implementation rgds, Ime Thilo Schuler thilo.schuler at gmail.com wrote: Hi Ime and others XForms is an intriguing technology and IMHO (and others' !) it seems very suited to generate forms from templates and their underlying archetypes . I will first

xml archetypes to xforms

Hi Ime and others XForms is an intriguing technology and IMHO (and others' !) it seems very suited to generate forms from templates and their underlying archetypes . I will first point you to two recent sources where XForms where mentioned within the openEHR community: 1. Wiki (look

xml archetypes

file) Ime Asangansi wrote: Hi all, I am involved in an internship project with the OpenMRS (www.openmrs.org) that involves the integration of this open source web application medical record system with OpenEHR archetypes. My work is to provide only a proof of concept for the OpenEHR

xml archetypes

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080203/9c1c3186/attachment.html -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

xml archetypes

Hi all, I am involved in an internship project with the OpenMRS (www.openmrs.org) that involves the integration of this open source web application medical record system with OpenEHR archetypes. My work is to provide only a proof of concept for the OpenEHR modelling approach by allowing

Developing with Archetypes

Hello everyone I am attempting to build some tools to help in the development/publication of archetypes, as such I have a couple of questions : - Is it possible to get an up to date copy of the schemas for archetypes, I see the versions on SVN but they seem to be a little out of date ( certainly

Developing with Archetypes

Richard Kavanagh wrote: Hello everyone I am attempting to build some tools to help in the development/publication of archetypes, as such I have a couple of questions : - Is it possible to get an up to date copy of the schemas for archetypes, I see the versions on SVN but they seem

Archetype production: Types of Archetypes

A few thoughts about Types of Archetypes Archetypes are constraints on an UML model. Archetypes define what can be documented about a topic. Templates are Archetypes. Archetypes are not Templates because Templates are the aggregated archetypes, collected and further constrained to suit

Suggestion wrt XML Archetypes Templates

be satisfied. - thomas beale When will the tooling decorate the generated xml archetypes with the required attribute? Pretty printing is the norm. The text should be normalized the normalization should be enforceable. Adam ___ openEHR-technical

Suggestion wrt XML Archetypes Templates

[mailto:openehr-technical- bounces at openehr.org] On Behalf Of Lisa Thurston Sent: Tuesday, 11 December 2007 10:23 AM To: For openEHR technical discussions Subject: Re: Suggestion wrt XML Archetypes Templates Adam Flinton wrote: I would like though to enquire wrt the rationale of containing _id info

Suggestion wrt XML Archetypes Templates

Adam Flinton wrote: I would like though to enquire wrt the rationale of containing _id info in a separate value/ element. If you are being consistent instead of : terminology_id valueISO_639-1/value /terminology_id it should be simply:

Suggestion wrt XML Archetypes Templates

-Original Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- bounces at openehr.org] On Behalf Of Thomas Beale Sent: Monday, 10 December 2007 7:34 AM To: adam.flinton at nhs.net; For openEHR technical discussions Subject: Re: Suggestion wrt XML Archetypes

Suggestion wrt XML Archetypes Templates

Thomas Beale wrote: Adam Flinton wrote: I reserve my views wrt attributes vs text() however that would do on the proviso of a bit of testing with many tools as it used to be patchily supported by different tools. I accept that was a few years back things may well have improved. So

<    1   2   3   4   5   6   >