<?xml version="1.0" encoding="UTF-8" standalone="yes"?><rss version="2.0"><channel><title>openEHR Clinical Knowledge Manager</title><link>http://openehr.org/knowledge/</link><description>The official feed of the openEHR Clinical Knowledge Manager</description><language>en</language><item><title>New comment: Re: Quantity by Volume occurrence 1..2</title><link>http://openehr.org/knowledge/#showComment_1013.18.172_1013.1.156</link><description>A new comment has been posted by daniel.karlsson:&lt;br/&gt;Re: Quantity by Volume occurrence 1..2&lt;br/&gt;This occurence seems wrong. For our use (representing mg/d) in the Swedish pilot we will have to relax the occurence from 1..2 to 0..2 while I would prefer 0..1 as above.  Also, how should the possibility of having multiple quantities for a dose be interpreted? </description><author>daniel.karlsson</author><pubDate>Thu, 11 Mar 2010 08:22:16</pubDate></item><item><title>Updated archetype: Histopathology (openEHR-EHR-OBSERVATION.lab_test-histopathology.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.351</link><description>An archetype has been updated: Histopathology (openEHR-EHR-OBSERVATION.lab_test-histopathology.v1)&lt;br/&gt;Log message: Relaxed location and microscopic details occurrences constraints.</description><author>ian.mcnicoll</author><pubDate>Thu, 11 Mar 2010 12:40:59</pubDate></item><item><title>Updated archetype: Tumour- Lymph node metastases (openEHR-EHR-CLUSTER.lymph_node_metastases.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.396</link><description>An archetype has been updated: Tumour- Lymph node metastases (openEHR-EHR-CLUSTER.lymph_node_metastases.v1)&lt;br/&gt;Log message: Added Lymph node details slot.</description><author>ian.mcnicoll</author><pubDate>Thu, 11 Mar 2010 12:36:54</pubDate></item><item><title>New comment: Re: Dose Unit mandatory, why?</title><link>http://openehr.org/knowledge/#showComment_1013.18.170_1013.1.156</link><description>A new comment has been posted by rong.chen:&lt;br/&gt;Re: Dose Unit mandatory, why?&lt;br/&gt;Agree with Health. There seems to be some room for improvement in the model. The Dose Unit can be redundant if dose is specified by Absolute Quantity, where units is required by the underlying data type DV_QUANTITY. </description><author>rong.chen</author><pubDate>Wed, 10 Mar 2010 01:29:27</pubDate></item><item><title>New comment: Re: Re: Re: Suggest that ESR is modelled separately</title><link>http://openehr.org/knowledge/#showComment_1013.18.206_1013.1.566</link><description>A new comment has been posted by ian.mcnicoll:&lt;br/&gt;Re: Re: Re: Suggest that ESR is modelled separately&lt;br/&gt;Thanks Michael,  I think we have reasonable consensus that ESR should be split out into a separate archetype.The way would would handle a FBC+ESR panel is to aggregate them together within a template. </description><author>ian.mcnicoll</author><pubDate>Mon, 08 Mar 2010 10:51:15</pubDate></item><item><title>New comment: Re: Re: Suggest that ESR is modelled separately</title><link>http://openehr.org/knowledge/#showComment_1013.18.206_1013.1.566</link><description>A new comment has been posted by michael.reynolds:&lt;br/&gt;Re: Re: Suggest that ESR is modelled separately&lt;br/&gt;If they are separate tests that are often ordered together, it would seem that we would achieve the greatest flexability by keeping them separate. It is a simple matter to order them together at the clinic-side.     On the boarder issue of LOINC, etc...  Perhaps the best solution would be to allow test archetypes to reference other archetypes to bundle them together and, in short, build lab results panels out of lab archetypes? </description><author>michael.reynolds</author><pubDate>Mon, 08 Mar 2010 03:12:18</pubDate></item><item><title>Updated archetype: Device details (openEHR-EHR-CLUSTER.device.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.17</link><description>An archetype has been updated: Device details (openEHR-EHR-CLUSTER.device.v1)&lt;br/&gt;Log message: Added elements to better align with HL7 CDA device class</description><author>ian.mcnicoll</author><pubDate>Sat, 06 Mar 2010 06:22:20</pubDate></item><item><title>Updated archetype: Indirect oximetry (openEHR-EHR-OBSERVATION.indirect_oximetry.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.188</link><description>An archetype has been updated: Indirect oximetry (openEHR-EHR-OBSERVATION.indirect_oximetry.v1)&lt;br/&gt;Log message: Added keywords. Corrected typo prior to publication.</description><author>ian.mcnicoll</author><pubDate>Sat, 06 Mar 2010 11:09:55</pubDate></item><item><title>Updated archetype: Pulse (openEHR-EHR-OBSERVATION.heart_rate-pulse.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.171</link><description>An archetype has been updated: Pulse (openEHR-EHR-OBSERVATION.heart_rate-pulse.v1)&lt;br/&gt;Log message: Updated to align with parent heart_rate</description><author>ian.mcnicoll</author><pubDate>Wed, 03 Mar 2010 10:07:49</pubDate></item><item><title>New comment: Concepts of Problem, Issue, Diagnosis and Concern </title><link>http://openehr.org/knowledge/#showComment_1013.18.216_1013.1.169</link><description>A new comment has been posted by ian.mcnicoll:&lt;br/&gt;Concepts of Problem, Issue, Diagnosis and Concern &lt;br/&gt;I would like to re-open some of the discussions around the concepts of Problem, Issue, Condition, Concern, Diagnosis etc, that have cropped up in previous reviews of the Problem and Diagnosis archetypes. I have created a wiki page at  http://www.openehr.org/wiki/display/healthmod/Problem%2C+Issue%2C+Diagnosis+and+Concern  which describes the various concepts that I am aware of , having pulled together examples from working systems and other standards efforts such HL7 Concern tracking and the CEN Contsys standards.   This is probably the best location for on-going discussion, rather than the wiki but I will monitor both for comments.   Any and all opinions gratefully received. The initial intention is to stay clear of discussions around names - let's try to agree the broad concepts first of all.  Ian </description><author>ian.mcnicoll</author><pubDate>Wed, 03 Mar 2010 06:31:34</pubDate></item><item><title>Updated archetype: Glasgow Coma Scale (openEHR-EHR-OBSERVATION.glasgow_coma.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.137</link><description>An archetype has been updated: Glasgow Coma Scale (openEHR-EHR-OBSERVATION.glasgow_coma.v1)&lt;br/&gt;Log message: Add descriptions to all ordinal elements
Update metadata
Add EMV profile
Add protocol</description><author>heather.leslie</author><pubDate>Thu, 25 Feb 2010 11:21:31</pubDate></item><item><title>Updated archetype: ECG recording (openEHR-EHR-OBSERVATION.ecg.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.276</link><description>An archetype has been updated: ECG recording (openEHR-EHR-OBSERVATION.ecg.v1)&lt;br/&gt;Log message: Added description of leads to Per Lead run-time name constraints
Added reference
Modified Use
Modified Purpose</description><author>heather.leslie</author><pubDate>Mon, 22 Feb 2010 11:16:20</pubDate></item><item><title>Updated archetype: Microbiolology of urine (openEHR-EHR-OBSERVATION.lab_test-microbiology-urine.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.559</link><description>An archetype has been updated: Microbiolology of urine (openEHR-EHR-OBSERVATION.lab_test-microbiology-urine.v1)&lt;br/&gt;Log message: Added Antimicrobial advice node, changed concept name.</description><author>ian.mcnicoll</author><pubDate>Tue, 16 Feb 2010 04:27:43</pubDate></item><item><title>Updated archetype: Microbiolology (openEHR-EHR-OBSERVATION.lab_test-microbiology.v1)</title><link>http://openehr.org/knowledge/#showArchetype_1013.1.558</link><description>An archetype has been updated: Microbiolology (openEHR-EHR-OBSERVATION.lab_test-microbiology.v1)&lt;br/&gt;Log message: Added Antimicrobial advice node</description><author>ian.mcnicoll</author><pubDate>Tue, 16 Feb 2010 04:24:57</pubDate></item><item><title>New comment: Re: Re: White cell differentiation</title><link>http://openehr.org/knowledge/#showComment_1013.18.211_1013.1.566</link><description>A new comment has been posted by shinji.kobayashi:&lt;br/&gt;Re: Re: White cell differentiation&lt;br/&gt;Thanks Ian  Although RBC findings are usually reported present/absent e.g. poikilocytes, eliptocytes..., WBC differentiation, especially in haematology, should be reported as percentage of count. Percentage of blast is an important criteria of myelodysplastic syndrome. I think that it is not a good way to have separated or specialised WBC differentiation archetype for haematologist, because it lacks interoperability between haematologists and other fields' clinicians. Anyone has possibility to be hit leukemia. We, haematologists, need information of changes FBC and WBC differentiation in times around onset of diseases. I agree with to have cluster archetype for universal WBC differentiation.  Thank you for your comment.  Shinji  </description><author>shinji.kobayashi</author><pubDate>Mon, 15 Feb 2010 02:36:19</pubDate></item></channel></rss>