openEHR Clinical Knowledge Manager

New archetype: Fetal Heart Monitoring (openEHR-EHR-OBSERVATION.fetal_heart-monitoring.v1)

heather.leslie — Wed, 25 Jan 2012 12:44:32

A new archetype has been uploaded: Fetal Heart Monitoring (openEHR-EHR-OBSERVATION.fetal_heart-monitoring.v1)
Log message: Initial Upload

New archetype: Fetal Heart Rate (openEHR-EHR-OBSERVATION.fetal_heart.v1)

heather.leslie — Wed, 25 Jan 2012 12:05:17

A new archetype has been uploaded: Fetal Heart Rate (openEHR-EHR-OBSERVATION.fetal_heart.v1)
Log message: Initial upload

Updated archetype: Measurement of chest and expansion (openEHR-EHR-OBSERVATION.chest_expansion.v1)

heather.leslie — Fri, 20 Jan 2012 02:37:52

An archetype has been updated: Measurement of chest and expansion (openEHR-EHR-OBSERVATION.chest_expansion.v1)
Log message: Translated archetype from English to Arabic (Syria) & Spanish (Argentina).

New comment: Feedback on Review Round #2 from Jobst Landgrebe

heather.leslie — Fri, 20 Jan 2012 01:39:00

A new comment has been posted by heather.leslie:
Feedback on Review Round #2 from Jobst Landgrebe
Normal 0 false false false EN-AU X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} Comment from Jobst Landgrebe received via email; and my response: Dear Heather, I had some problems with the tool (no intermediate saving of a review session possible, or I did not understand how it works, maybe Thomas' team can check). Therefore, I would like to summarise my findings here: Overall, the Adverse Reaction archetype is too exclusively focused on primary and secondary care (for which it is now very good) and does not sufficiently support requirements for adverse event management as requested by the FDA AERS ( http://www.fda.gov/Drugs/GuidanceComplianceRegulatoryInformation/Surveillance/AdverseDrugEffects/default.htm ). To realise these requirements, s.o. would need to analyse the data fields requested by the FDA (which is roughly equivalent to EMA and PMDA requirements). The usability of this architeype would increase beyond the primary/secondary care into the regulated pharmaceutical space, which feeds on reports from health care professionals; they need electronic forms to communicate to the FDA and other regulators ... Hope you can take the input in this form. Sincerely, Jobst Normal 0 false false false EN-AU X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} Hi Jobst, It is currently possible to save during a review – but you do need to register a Recommendation on the last tab in order to save it. Thus it will be counted in reviews and counts of reviewers etc in the same way as a fully completed review – we can’t differentiate and it will puts the onus on the user to come back and complete it. Then you can subsequently modify the review by accessing it from the Completed Reviews list in the CKM dashboard. It is a little clunky, but to implement the notion of partial saves is actually incredibly complex from an admin and governance point of view, and so we have implemented the current practice as a starting point, knowing that at some time we will tackle it better. The review is not aiming at Primary/Secondary care so much as being a pragmatic core of commonly used data (and this is what makes it seem focussed on primary and secondary care). To have a full maximal data set would make it unwieldy and overly complex and so a line was drawn to make explicit in this core archetype only the common data elements. The intent is to extend the archetype for the reporting scenario that you are flagging by use of additional Cluster archetypes in SLOTs that capture additional details for the Reaction, Exposure and Reporting – as explained in the ‘Use’ area of the metadata. We don’t have those extension archetypes on CKM yet. I have them scoped out, but haven’t built them. Clearly it will be helpful if I can scramble the time together to create them as draft candidates – it will make the design intent more transparent. My scoping for the full model, including the extension archetypes, did take into account the FDA/ICH requirements, althought it appears that at least the website has been updated since then. I will revisit it in detail ready for the next review round to make sure there are no content changes required. I’m glad this core archetype is looking OK at present. We have compared it to ones from VA, HL7, Canada Infoway and Intermountain Health and I was pleased to see it catered for all the usecases they brought up and often seemed to exceed them. But then I’m biased J Please keep in touch. I will let you know when the CLUSTERS are ready and will provide some documentation about the design to make it clearer to all. I appreciate your efforts and value your input enormously. We certainly have the same intent for the final output of this family of models. Regards Heather

Updated archetype: Poisoning or overdose (openEHR-EHR-CLUSTER.health_event-poisoning.v1)

heather.leslie — Fri, 20 Jan 2012 12:17:12

An archetype has been updated: Poisoning or overdose (openEHR-EHR-CLUSTER.health_event-poisoning.v1)
Log message: Translated archetype from English to Spanish (Argentina) and Arabic (Syria).

New comment: Re: Re: Pregnancy Test

leo.derja — Wed, 18 Jan 2012 04:09:10

A new comment has been posted by leo.derja:
Re: Re: Pregnancy Test
Hi Heather: I think what you say is right. I compared this situation with, by example: openEHR-EHR-OBSERVATION.lab_test-blood_gases.v1 , that has a slot to openEHR-EHR-CLUSTER.ambient_oxygen.v1 . This explicit reference vía a slot, allows correctly interpret the lab test. I thought it could be useful to use this attribute [ Date of LMP ] in openEHR-EHR-OBSERVATION.pregnancy_test.v1 , as it was also used in openEHR-EHR-EVALUATION.pregnancy.v1 You correctly suggested that an implicit reference between archetypes pregnancy-test and menstruation, putting both together in a composition should be the correct way to record the information. I am comfortable with that. I am just trying to apprehend the logic of this system of archetypes. Thank you. Best regards, Leonardo DJ

Updated archetype: Adverse Reaction (openEHR-EHR-EVALUATION.adverse_reaction.v1)

heather.leslie — Mon, 16 Jan 2012 11:03:10

An archetype has been updated: Adverse Reaction (openEHR-EHR-EVALUATION.adverse_reaction.v1)
Log message: **Major changes** - this archetype has been fundamentally reworked based on previous review comments, research and inclusion of input from HL7, ICH and statutory requirements and feedback from NEHTA CKM reviews. In addition, the archetype ID was updated to be clear of intent and follow recent editorial practice. Changes include: - Significant enhancement of Concept Description, Purpose, Use, Misuse, Keywords and References. - 'Agent' is now referred to 'Substance/Agent' throughout - Addition of Absolute Contraindication; Future Use; Overall Comment; Slots for Additional Reaction Detail, Additional Exposure Detail and Reporting Details; Exposure description; Earliest Exposure; Clinical Management Description; Multimedia; & Reaction Comment - Addition of Protocol containing Reaction Reported?; Report Comment; Adverse Reaction Report and Supporting Clinical Record Information - Removal of Agent Category; Reaction Severity - Modification of "Probability of Causation' to 'Certainty' - Inclusion of Translation - Arabic (Syrian) and German (Standard) where data elements/descriptions are consistent with original translations. - Inclusion of NEHTA reviewers as contributors

New comment: Re: Pregnancy Test

heather.leslie — Sun, 15 Jan 2012 11:45:55

A new comment has been posted by heather.leslie:
Re: Pregnancy Test
Hi Leonardo, The translation process that you participated in, using CKM, only allows for upload of translation to the data elements already existing in the archetype. It is not allowed for non-Editors to add new elements or edit the existing ones. Any changes to the scope/details of the archetype is only done with Editorial oversight. However your issue is noted - that you thought the archetype incomplete. And in isolation there will be many that appear that way. However the intent of the archetype is only to record the result of a commercial pregnancy test and there are a number of other pieces of information that may be useful when interpreting the result, including more details about the woman's menstrual history including LNMP, but also pattern etc which can be captured using the OBSERVATION.menstruation archetype. I think that the two of these together within a COMPOSITION for a specific clinical encounter would provide the information that you are seeking. Are you comfortable with that? Regards Heather

New comment: Re: Languages / Cultures in translation

domingo.liotta — Sat, 14 Jan 2012 05:12:43

A new comment has been posted by domingo.liotta:
Re: Languages / Cultures in translation
Hello CKM members: The translations of archetypes were part of the final evaluation of Ing. Pablo Pazos first online course of openEHR in Spanish. I was rather shocked to see so few archetypes in Spanish, so hands on task I´ll translate myself, as many as possible. So I started with archetypes in English. I found previously David’s translation and I think there is another from Chile. I looked at both; they look fine to me, so I didn’t make any variations. I believe Ian´s approach to using a root language is correct. I couldn´t find any impediment to use my es-ar translation for es-es (for the body temperature archetype). I know a fellow classmate Leonardo will also be translating archetypes, we will work together and not overlap. I do have a suggestion that may be useful in this discussion: Our School of Medicine at the UM works extensively with a Languages Lab (many languages even oriental), so I can do a small research about the variability in different variations of languages and if it impacts the meaning of a clinical concept. I hope to be able to tap this resource into the openEHR community somehow too. Hope this can be helpful Best regards (PS: When I´m knowledgeable enough to create archetypes myself they will be done in both Spanish and English) Dr. Domingo Liotta (h) Director Cátedra Abierta de Bienestar Médica, Universidad de Morón http://argentinawellness.org My profiles: Contact me: domingo.liotta dliotta domingo_liotta@hotmail.com domingo_liotta@yahoo.com.ar

New comment: Pregnancy Test

leo.derja — Sat, 14 Jan 2012 01:34:29

A new comment has been posted by leo.derja:
Pregnancy Test
Hi for all: In a recent review, I added to archetype [openEHR-EHR-OBSERVATION. pregnancy_test .v1] => " Last menstruation date " because I think it is needed for correctly interpret the test. Best regards, Dr. Leonardo Der Jachadurian

Updated archetype: Ambient oxygen (openEHR-EHR-CLUSTER.ambient_oxygen.v1)

ian.mcnicoll — Fri, 13 Jan 2012 04:55:53

An archetype has been updated: Ambient oxygen (openEHR-EHR-CLUSTER.ambient_oxygen.v1)
Log message: Translated archetype from English to Spanish (Argentina). Google Translate checked

New comment: Languages / Cultures in translation

ian.mcnicoll — Fri, 13 Jan 2012 11:22:03

A new comment has been posted by ian.mcnicoll:
Languages / Cultures in translation
Hi all, It is great to see increasing numbers of translations being offered for archetypes but I have a question for those of us working in languages which have national/cultural variants e.g English, UK English, US English or Spanish , Argentinian Spanish. Creating and maintaining translations will be quite onerous. At the moment, each translation of every sub-language is separately maintained within ADL, although it is actually quite easy to hack the ADL to copy/paste from a different language variant i.e to create en-us from en-gb. Although implementations may vary, I suspet most would work similar to the Ocean tools and will look for and make use of a parent or neutral language if possible e.g. if the tools native operating system culture is 'en-gb' it will look for 'en-gb' translation and if not found look for the parent 'en', finally defaulting to the primary archetype language if necessary. This 'default to parent' mechanism means that we could potentially simplify translation by using the parent/neutral culture if at all possible e.g translate to en rather than en-gb or es rather than es-ar. This would work pretty well in English where there few examples of clinically important spelling differences which might cause confusion between language variants. I am happy to tolerate a few American 'z' spellings instead of 's', if it reduces the translation burden. If people feel strongly they can always create the sub-language variant. My question to an international audience is whether this would be equally acceptable for other languages and cultures, appreciating that this can be a touchy subject!! One thing that might also help is to allow the sub-language variant to be expressed a a differential on the parent language within ADL i.e. rather than the es-ar variant being a complete list of translated terms, just carry those that differ from the parent language terms. So my suggestion is that when translating we use the parent language, rather than a local variant unless there are compelling reasons, and even then it may make sense to create the parent AND the variant, where the parent does not already exist. I will copy this to the openEHR clinical list to get a wider spread of opinion. Ian

New comment: Re: Re: Event offset restriction

diego.bosca — Fri, 13 Jan 2012 11:05:10

A new comment has been posted by diego.bosca:
Re: Re: Event offset restriction
Ok, I will do that right now

New comment: Re: Event offset restriction

ian.mcnicoll — Fri, 13 Jan 2012 10:58:51

A new comment has been posted by ian.mcnicoll:
Re: Event offset restriction
Hi Diego, I know the discussion on constraining functions is ongoing on the lists but it might be worthwhile highlighting the other issue re the syntax of the DV_DURATION constraint on the technical list. I think you will get a better response there. Ian

Updated archetype: Blood gas assessment (openEHR-EHR-OBSERVATION.lab_test-blood_gases.v1)

sebastian.garde — Tue, 10 Jan 2012 01:06:53

An archetype has been updated: Blood gas assessment (openEHR-EHR-OBSERVATION.lab_test-blood_gases.v1)
Log message: Translated archetype from English to Spanish (Argentina) by Leonardo Der Jachadurian.

Updated archetype: Follow up action (openEHR-EHR-ACTION.follow_up.v1)

sebastian.garde — Tue, 10 Jan 2012 01:04:16

An archetype has been updated: Follow up action (openEHR-EHR-ACTION.follow_up.v1)
Log message: Translated archetype from English to Arabic (Syria) by Monah Saleh. Translated archetype from English to Spanish (Argentina) by Leonardo Der Jachadurian.

Updated archetype: Height/Length (openEHR-EHR-OBSERVATION.height.v1)

heather.leslie — Tue, 10 Jan 2012 03:35:59

An archetype has been updated: Height/Length (openEHR-EHR-OBSERVATION.height.v1)
Log message: Translated archetype from English to Farsi, Arabic (Syria) and Spanish (Argentina).

Updated archetype: Respirations (openEHR-EHR-OBSERVATION.respiration.v1)

heather.leslie — Tue, 10 Jan 2012 12:11:45

An archetype has been updated: Respirations (openEHR-EHR-OBSERVATION.respiration.v1)
Log message: Translated archetype from English to Farsi, Arabic (Syria) and Spanish (Argentina).

Updated archetype: Intravenous fluid administration (openEHR-EHR-ACTION.intravenous_fluid_administration.v1)

heather.leslie — Mon, 09 Jan 2012 11:37:15

An archetype has been updated: Intravenous fluid administration (openEHR-EHR-ACTION.intravenous_fluid_administration.v1)
Log message: Translated archetype from English to Arabic (Syria) and Spanish (Argentina).

New comment: Event offset restriction

diego.bosca — Mon, 09 Jan 2012 11:51:43

A new comment has been posted by diego.bosca:
Event offset restriction
I have started also a discussion on the mailing list about this topic. Offset is not an attribute in the reference model an thus shouldn't be restricted as it is now on this archetype. It should be an assertion. While we decide if we change this or not, there is another error regarding offsets. Durations are described as ranges, not as a default values. so all the restrictions as this: offset existence matches {1..1} matches { DV_DURATION[at0040] occurrences matches {0..1} matches { -- value existence matches {1..1} matches {|PT10M|} } } should be changed to this: offset existence matches {1..1} matches { DV_DURATION[at0040] occurrences matches {0..1} matches { -- value existence matches {1..1} matches {PT10M} } }

Updated archetype: Body temperature (openEHR-EHR-OBSERVATION.body_temperature.v1)

heather.leslie — Fri, 06 Jan 2012 06:11:35

An archetype has been updated: Body temperature (openEHR-EHR-OBSERVATION.body_temperature.v1)
Log message: Translated archetype from English to Spanish (Spain).

Updated archetype: Clinical Synopsis (openEHR-EHR-EVALUATION.clinical_synopsis.v1)

heather.leslie — Fri, 06 Jan 2012 05:14:22

An archetype has been updated: Clinical Synopsis (openEHR-EHR-EVALUATION.clinical_synopsis.v1)
Log message: Translated archetype from English to Arabic (Syria), Syrian and Spanish (Argentina).

New comment: Pulmonary Function Archetype

domingo.liotta — Sat, 31 Dec 2011 01:41:31

A new comment has been posted by domingo.liotta:
Pulmonary Function Archetype
Dear Ian: Sorry it took me some days to get back to you. I´m also sending this mail to the Clinical Discussion List as it may benefit others. The proposed pulmonary function archetype is also adequate for adult use, I took some extra time to have it checked by the Chief of Intensive Care at my Hospital. The archetype is detailed enough for international use. Your assumption is correct VO2max does merit a separate archetype included as a subset of a more detailed " Exercise Stress Testing " arquetype. The VO2max has its clinical fundamentals for assessment of cardiovascular function which may or may not have a pulmonary component. So the pulmonary function test archetype could take the value from the Exercise Stress Test arquetype and also if a cardiac patient also have a Lung impairment the Exercise Stress Testing should read the values pre & post bronchodilation. The reason for showing the archetypes at my Hospital (and it worked as planned) was to get more Clinical experts into the Clinical Modelling process. I will be meeting next week the Chief of Acute Coronary Unit to discuss the modelling of the more General "Stress Exercise Testing" I´ll keep the list informed. Wow! For me an excellent way to finish 2011 :) Happy new years to all :=) Domingo Hi Domingo, Thanks for offering to have a look at this archetype. It was developed for use in a Paediatric EMR in Slovenia but very much as a candidate for international use. One of the issues I suspect you might challenge is whether V02max merits a separate archetype. Ian Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll@oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director/Clinical Knowledge Editor openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org

New comment: Re: Re: Translated Body Temperature to Spanish AR

domingo.liotta — Fri, 30 Dec 2011 06:34:53

A new comment has been posted by domingo.liotta:
Re: Re: Translated Body Temperature to Spanish AR
Hello Ian: How are you doing, as 2011 is ending... :) Oh! The Archetype can perfectly go as a generic "es" translation. The are no variants in the Argentinian version. I´ll edit the (es) tags off the keywords and it will be good to go. Have a very Happy New Year! Domingo

New comment: Re: Translated Body Temperature to Spanish AR

ian.mcnicoll — Fri, 30 Dec 2011 01:56:38

A new comment has been posted by ian.mcnicoll:
Re: Translated Body Temperature to Spanish AR
Hi Domingo, Thanks for this. It looks good to me (as far as any reverse translation with Google Translate goes). You do not need the (es) tags on the keywords as these are language specific - these could be removed. To what extent would the Argentinian variant of Spanish vary for this archetype - would it be possible to use this for a generic "es" translation? Ian

New comment: Translated Body Temperature to Spanish AR

domingo.liotta — Fri, 30 Dec 2011 03:57:55

A new comment has been posted by domingo.liotta:
Translated Body Temperature to Spanish AR
Dear Editors: How did the translation go? Does it need any uptate or editing in your opinion? Best regards Domingo

New comment: Exercise Presciption Arquetype

domingo.liotta — Fri, 23 Dec 2011 01:45:09

A new comment has been posted by domingo.liotta:
Exercise Presciption Arquetype
Hello Community: There is an ongoing discussion on the email list but I´ll post it here too, I hope the community may find it interesting. I work as a general practitioner and medical informatics at a public hospital in Argentina, in a Cardiology Service. Specifically in Cardiac Rehabilitation. Physical Activity is very important as the means to reinsert our patients into society after a cardiovascular event. A very quick database search revealed that the Arquetype: Level of exertion to be useful as you will need to register the patients “level of fitness” pre and post training. Also the related clinical observations: blood pressure, heart rate, ECG recording It would be useful to create a Borg perception of exercise (subjective) as it correlates well with level of exertion. I can be bold and try to make an Arquetype for: VO2max Testing which is my expertise but I´m a real newbie in clinical modelling. I didn’t find any “exercise prescription” Arquetype. ( I´d like to see that too). I´ll re post some very helpful suggestions from the mailing list members. Be well Domingo Liotta

Updated archetype: Body mass index (openEHR-EHR-OBSERVATION.body_mass_index.v1)

heather.leslie — Tue, 20 Dec 2011 01:49:39

An archetype has been updated: Body mass index (openEHR-EHR-OBSERVATION.body_mass_index.v1)
Log message: Added translation from English to Spanish (Argentina). Added translation from English to Arabic (Syria). Updated translation from English to Farsi.

Updated archetype: Blood Pressure (openEHR-EHR-OBSERVATION.blood_pressure.v1)

heather.leslie — Mon, 19 Dec 2011 05:07:09

An archetype has been updated: Blood Pressure (openEHR-EHR-OBSERVATION.blood_pressure.v1)
Log message: Translated archetype from English to Spanish (Argentina). Traducción del arquetipo del Inglés al Español

New comment: Re: Re: Error in "braden scale" total score

rui.coutinho — Wed, 07 Dec 2011 12:21:12

A new comment has been posted by rui.coutinho:
Re: Re: Error in "braden scale" total score
Thank you

New comment: Re: Error in "braden scale" total score

heather.leslie — Wed, 07 Dec 2011 02:50:56

A new comment has been posted by heather.leslie:
Re: Error in "braden scale" total score
Thanks for pointing this out. I've corrected it and uploaded the latest revision Regards Heather

Updated archetype: Braden Scale (openEHR-EHR-OBSERVATION.braden_scale.v1)

heather.leslie — Wed, 07 Dec 2011 02:50:13

An archetype has been updated: Braden Scale (openEHR-EHR-OBSERVATION.braden_scale.v1)
Log message: Correct Total Score to max of 23. Minor changes to Use, Misuse

New comment: Error in "braden scale" total score

rui.coutinho — Wed, 07 Dec 2011 12:25:55

A new comment has been posted by rui.coutinho:
Error in "braden scale" total score
Please review the maximum tota score for the braden scale. As you can easily notice, the possible maximum score is 23 not 20.

New comment: Re: Re: Re: wrong regular expression?

ian.mcnicoll — Fri, 02 Dec 2011 03:20:24

A new comment has been posted by ian.mcnicoll:
Re: Re: Re: wrong regular expression?
Thanks. I am hoping Sergio Friere might respond as he is the main author and might have a different perspective but here is my view. As I understand the original slot constraint it means "Use any archetype which is an address.v1 archetype or any specialisation thereof." What is the purpse of your prefixed regex? What does that add? Also regarding the fixed v1 suffix, I would probably agree that in the context of EHR content, we would probably leave the structural version identifier open, but Sergio may argue that in the much slower-moving world of Demographics models, that it is reasonable to require any slotted archetypes to be fixed to a particular version, so that the query semantics are closely defined. I suppose it comes down to the tightness of the binding/coupling between the 2 archetypes. This is generally a bad idea in clinical content because it enforces too much inter-locked dependency, but might not be a bad strategy in Demographic models where the main purpose of slotting out e.g Address cluster, is to allow some limited local specialisation. Definitely worth discussion .. any other views? Ian

New comment: Re: Re: wrong regular expression?

diego.bosca — Fri, 02 Dec 2011 02:50:19

A new comment has been posted by diego.bosca:
Re: Re: wrong regular expression?
well, this kind of expressions archetype_id/value matches {/(address)([a-zA-Z0-9_-]+)*\.v1/} archetype_id/value matches {/(electronic_communication)[a-zA-Z0-9_-]*\.v1/} would change to something like this archetype_id/value matches {/([a-zA-Z0-9_-]+)(address)([a-zA-Z0-9_-]+)*\.v1/} archetype_id/value matches {/([a-zA-Z0-9_-]+)(electronic_communication)[a-zA-Z0-9_-]*\.v1/} and I believe that ([a-zA-Z0-9_-]+)* is equivalent to this ([a-zA-Z0-9_-]*) version shouldn't be fixed to 'v1'

New comment: Re: wrong regular expression?

ian.mcnicoll — Fri, 02 Dec 2011 02:16:48

A new comment has been posted by ian.mcnicoll:
Re: wrong regular expression?
Hi Diego, I am not sure I understand. Can you give me a specific example of how you think the current slot constraints need to be changed. Ian

New comment: wrong regular expression?

diego.bosca — Wed, 30 Nov 2011 10:00:51

A new comment has been posted by diego.bosca:
wrong regular expression?
Maybe I am wrong, but I think all slot includes need [A-Za-z0-9_-]+ to be added to the start of current regular expression

New comment: Re: Re: Bad reference model?

diego.bosca — Fri, 23 Sep 2011 08:46:26

A new comment has been posted by diego.bosca:
Re: Re: Bad reference model?
But nothing is stopping you to make an slot to a cluster of the demographic reference model defining the address (and I am assuming that both clusters are compatible). That would give you two different addresses on the demographic model, which is not a problem 'per-se' but can mislead some people. Another different discussion would be that if the concept of ADDRESS is really needed on the archetype, then maybe the demographic concepts should be included into the openEHR reference model (or at least a way of doing that) Just for curiosity, which is that archetype?

New comment: Re: Bad reference model?

ian.mcnicoll — Fri, 23 Sep 2011 06:48:58

A new comment has been posted by ian.mcnicoll:
Re: Bad reference model?
Hi Diego, In theory, yes but in practice we have found a number of circumstances where people need to express some aspects of demographics in the EHR model e.g. 3rd party details where use of a demographics service is limited or unavailable, or use of such a service is disallowed for 3rd parties. Ian

New comment: Bad reference model?

diego.bosca — Thu, 22 Sep 2011 05:25:30

A new comment has been posted by diego.bosca:
Bad reference model?
Shouldn't this concept be in the demographics model?

New comment: Snomed 2011 changes - need to rethink this query

sebastian.garde — Fri, 09 Sep 2011 09:26:55

A new comment has been posted by sebastian.garde:
Snomed 2011 changes - need to rethink this query
In the Snomed 2011 version the Infectious Agent concept (36272005) has no child concepts anymore. The child concepts are all there but they no langer have this concept as a parent - for example 'Fungus' in 2009 had parent 'Microorganism' and 'Infectious Agent'. In 2011, it's just 'Microorganism". Hugh Grady did a quick google and found the following quote from Keith Spackman which may explain what's happened: " Infectious agent currently subsumes bacterium in SNOMED. The taxonomic constraints suggest this is inconsistent and should be changed." Also see http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.71.1992&rep=rep1&type=pdf This is why this query does not currently return any results - thanks Hugh Grady for discovering this! Sebastian

New comment: Re: complie error in ADL workbench

peng.chen — Tue, 30 Aug 2011 02:03:19

A new comment has been posted by peng.chen:
Re: complie error in ADL workbench
Hi Sebastian, I've tried your suggestion, but unfortunately I got no luck. The archetype for lipid study is openEHR-EHR-OBSERVATION.lab_test-lipids.v1 and there is no .adls for that archetype, but it still failed. In contrast, the archetype for " fundoscopic_examination " has both .adl and .adls (openEHR-EHR-OBSERVATION.fundoscopic_examination.v1, openEHR-EHR-OBSERVATION.fundoscopic_examination.v1.adls) and it turned out passing the compiler successfully. Does this have something to do with the reference model? I extracted the archetype model from knowledge manager. In ADL1.4 workbench, we don't really need to worry about the RM configuration as it requires in ADL1.5 workbench. Is there anything I would miss out? Cheers, Peng

New comment: Re: Re: complie error in ADL workbench

sebastian.garde — Mon, 29 Aug 2011 07:13:36

A new comment has been posted by sebastian.garde:
Re: Re: complie error in ADL workbench
Hi Peng, you possibly have some .adls (the differential form of the archetype, which is generated automatically by the Workbench) files flying around. The Workbench is parsing them instead of the .adl it seems. Try to delete the .adls files (likely generated by the 1.5 Workbench) and try again. That said, this archetype has some validation errors (see its Validation report), which should be cleaned up. Sebastian

New comment: Re: complie error in ADL workbench

peng.chen — Mon, 29 Aug 2011 02:34:05

A new comment has been posted by peng.chen:
Re: complie error in ADL workbench
Hi Sam, Thank you for your reply. I uninstalled ADL1.5 workbench and installed ADL1.4 workbench (v.1.4.1.595), but 'Lipid studies' archetype still failed and other v1.4 arhcetyps failed as well. I copied the compile error message as below: ------------- compiling openEHR-EHR-OBSERVATION.lab_test.v1 ------------- ERROR - line 1: parse error [last token = V_IDENTIFIER] line 1: In 'archetype' clause; expecting archetype id (model_issuer-ref_model-model_class.concept.version) [last token = V_IDENTIFIER] (Parse failed) (ARCHETYPE_PARSER.parse_archetype) INFO - Archetype differential form file found; parsing that (ARCHETYPE_PARSER.parse_archetype) ------------- compiling openEHR-EHR-OBSERVATION.lab_test-liver_function.v1 ------------- ERROR - PARSE FAILED DUE TO EXCEPTION; see 'status'; call 'reset' to clear (ARCHETYPE_PARSER.parse_archetype) ERROR - Software Exception 1 caught; stack: ------------------------------------------------------------------------------- Class / Object Routine Nature of exception Effect ------------------------------------------------------------------------------- DIFFERENTIAL_ARCHETYPE make_from_flat @15 <00000000030B3468> Feature call on void target. Fail ------------------------------------------------------------------------------- DIFFERENTIAL_ARCHETYPE make_from_flat @15 <00000000030B3468> Routine failure. Fail ------------------------------------------------------------------------------- FLAT_ARCHETYPE to_differential @1 <00000000030B30A8> Routine failure. Fail ------------------------------------------------------------------------------- ARCH_REP_ARCHETYPE set_archetype_flat @3 <0000000003835080> Routine failure. Fail ------------------------------------------------------------------------------- ARCHETYPE_PARSER parse_archetype @16 <00000000039C4FF0> Routine failure. Rescue ------------------------------------------------------------------------------- (ARCHETYPE_PARSER.parse_archetype) INFO - Archetype openEHR-EHR-OBSERVATION.lab_test-liver_function.v1 semantics VALIDATED (ARCH_REP_ARCHETYPE.set_archetype_flat) INFO - Archetype openEHR-EHR-OBSERVATION.lab_test-liver_function.v1 syntax VALIDATED (ARCHETYPE_PARSER.parse_archetype) I'm doing my final year computer science master thesis in health informatics. My topic is to capture phenotype data from genetic variant databases. I've finshed my survey on how the phenotype data are stored in genetic variant databases. I'm now learning the openEHR and find out the feasibility to use archetypes to capture the phenotype data. Cheers, peng

New comment: Re: complie error in ADL workbench

sam.heard — Sun, 28 Aug 2011 09:44:54

A new comment has been posted by sam.heard:
Re: complie error in ADL workbench
Hi Chen The archetypes are in ADL 1.4 - so you need to use a compiler that is compatible. ADL 1.5 is still experimental and has not been stabilised as yet. Cheers, Sam Heard

New comment: complie error in ADL workbench

peng.chen — Sat, 27 Aug 2011 10:11:51

A new comment has been posted by peng.chen:
complie error in ADL workbench
This archetype couldn't pass the compiler in ADL workbench. Its definition couldn't be viewed. I compiled all the archetypes version 1.5 in my ADL workbench, but many of the archetypes failed. As a result, I couldn't view the definition of the archetypes with compile errors.

Updated archetype: Fetal Movement (openEHR-EHR-OBSERVATION.fetal_movement.v1)

heather.leslie — Fri, 19 Aug 2011 06:50:27

An archetype has been updated: Fetal Movement (openEHR-EHR-OBSERVATION.fetal_movement.v1)
Log message: Partial translation of archetype from English to Arabic (Syria) - translation refers to previous revision of archetype but content is still close. Needs review of translation.

New archetype: Obstetric summary (openEHR-EHR-EVALUATION.obstetric_summary.v1)

heather.leslie — Wed, 17 Aug 2011 08:11:26

A new archetype has been uploaded: Obstetric summary (openEHR-EHR-EVALUATION.obstetric_summary.v1)
Log message: Initial upload; from NEHTA CKM

Updated archetype: Body weight (openEHR-EHR-OBSERVATION.body_weight.v1)

heather.leslie — Tue, 16 Aug 2011 03:25:46

An archetype has been updated: Body weight (openEHR-EHR-OBSERVATION.body_weight.v1)
Log message: Translated archetype from English to Farsi. Translated archetype from English to Arabic (Syria). Translated archetype from English to Spanish (Spain). Updated other contributors of the archetype.

Updated archetype: ECG recording (openEHR-EHR-OBSERVATION.ecg.v1)

heather.leslie — Mon, 15 Aug 2011 12:44:12

An archetype has been updated: ECG recording (openEHR-EHR-OBSERVATION.ecg.v1)
Log message: Translated archetype from English to Arabic (Syria).

Updated archetype: Examination findings (openEHR-EHR-OBSERVATION.exam.v1)

heather.leslie — Mon, 15 Aug 2011 12:42:10

An archetype has been updated: Examination findings (openEHR-EHR-OBSERVATION.exam.v1)
Log message: Translated archetype from English to Arabic (Syria).

Updated archetype: Blood matching (openEHR-EHR-OBSERVATION.blood_match.v1)

heather.leslie — Mon, 15 Aug 2011 12:41:10

An archetype has been updated: Blood matching (openEHR-EHR-OBSERVATION.blood_match.v1)
Log message: Translated archetype from English to Arabic (Syria).

Updated archetype: Barthel Index (openEHR-EHR-OBSERVATION.barthel.v1)

heather.leslie — Mon, 15 Aug 2011 12:38:20

An archetype has been updated: Barthel Index (openEHR-EHR-OBSERVATION.barthel.v1)
Log message: Translated archetype from Dutch to Arabic (Syria).

Updated archetype: Audiogram result (openEHR-EHR-OBSERVATION.audiogram.v1)

heather.leslie — Mon, 15 Aug 2011 12:36:37

An archetype has been updated: Audiogram result (openEHR-EHR-OBSERVATION.audiogram.v1)
Log message: Translated archetype from English to Arabic (Syria).

New archetype: Waterlow score (openEHR-EHR-OBSERVATION.waterlow_score.v1)

ian.mcnicoll — Mon, 08 Aug 2011 03:25:18

A new archetype has been uploaded: Waterlow score (openEHR-EHR-OBSERVATION.waterlow_score.v1)
Log message: Initial upload.

New archetype: Neonatal Braden scale (NSRAS) (openEHR-EHR-OBSERVATION.braden_scale_neonate.v1)

ian.mcnicoll — Mon, 08 Aug 2011 03:00:22

A new archetype has been uploaded: Neonatal Braden scale (NSRAS) (openEHR-EHR-OBSERVATION.braden_scale_neonate.v1)
Log message: Initial upload

New archetype: Modified Braden Q Scale (openEHR-EHR-OBSERVATION.braden_scale-child.v1)

ian.mcnicoll — Mon, 08 Aug 2011 02:55:31

A new archetype has been uploaded: Modified Braden Q Scale (openEHR-EHR-OBSERVATION.braden_scale-child.v1)
Log message: Initial upload.