Hi Heather
I have to admit that the difference between gathering more business requirements and collating existing research is clearer in theory than in practice I will comment in the review Grahame From: openehr-clinical-boun...@openehr.org [mailto:openehr-clinical-bounces at openehr.org] On Behalf Of Heather Leslie Sent: Monday, July 06, 2009 5:09 PM To: For openEHR clinical discussions Subject: Re: Adverse Reaction archetype - review round initiated Hi Grahame, The current scope for Adverse Reaction is the initial ideal for every archetype at creation - a maximal dataset for a universal usecase. So the current intent of use of the archetype includes within a report, within DSS, a clinical summary and any other way of utilising it. The archetype can then be constrained to make it 'fit for purpose' through context/scenario-appropriate templates. The current Adverse Reaction archetype is a 'straw man' model that needs considerable refining and enhancing - no doubt about it. It represents the thinking of a few people, based on lots of experience and only one reference noted. The purpose of this review is not to gather yet more business requirements but to collate the existing research and thinking done by many learned and expert organisations and national programs into a practical and pragmatic model that we can take forward as the basis for sharing common things about adverse reactions. As you quite rightly point out, the metadata needs quite a bit of enhancement. The review process should identify any missing data elements, and usecases not currently anticipated. The metadata will be improved to support all of this. Look forward to seeing your comments through the review. You can comment on each individual data element or metadata item, plus the completeness and/or any missing elements, general issues with regard to the design of this archetype, and other resources that should be considered for this archetype. Kind regards Heather On 6/07/2009 9:15 AM, Grahame Grieve wrote: hi Sam happy to do it on CKM, but the interface didn't suggest itself as suitable for this kind of scoping discussion Grahame From: openehr-clinical-boun...@openehr.org [mailto:openehr-clinical-bounces at openehr.org] On Behalf Of Sam Heard Sent: Monday, July 06, 2009 8:37 AM To: 'For openEHR clinical discussions' Subject: RE: Adverse Reaction archetype - review round initiated Grahame, Do it on CKM - not on the list! Then the ideas will not be lost. The proposal certainly covers more than you have noted but would not in itself support a report. This would be a template. Cheers, Sam From: openehr-clinical-boun...@openehr.org [mailto:openehr-clinical-bounces at openehr.org] On Behalf Of Grahame Grieve Sent: Sunday, 5 July 2009 1:52 PM To: 'For openEHR clinical discussions' Subject: RE: Adverse Reaction archetype - review round initiated hi I'd like to start by asking about the scope of this archetype. Is the intent to report about a condition of an adverse reaction? or a concern about? or just a report of a possible one? Is it a high level clinical summary, or is it supposed to be good enough to support DSS? I have considerable interest in this archetype: as well as being involved with this model through NEHTA and HL7, my daughter is highly allergic to tree nuts, but (a little unusually), not peanuts as well. It seems to me that the current archetype is only good for a gross point report of a single episode of apparent adverse reaction. If this is all it's supposed to be, I won't have much to say, but if it's supposed to be good for more than that.. I'd like the archetype to comment on this. "Recording the presence of a harmful or undesirable response to an agent or substance including food, as determined by the clinician - excluding poisoning and abnormal use" is ambiguous concerning these questions. Grahame From: openehr-clinical-boun...@openehr.org [mailto:openehr-clinical-bounces at openehr.org] On Behalf Of Heather Leslie Sent: Friday, July 03, 2009 3:26 PM To: For openEHR clinical discussions; For openEHR technical discussions Subject: Adverse Reaction archetype - review round initiated Dear Colleagues, A review round for the Adverse Reaction archetype was initiated today. This is a significant archetype that requires careful and considered collaboration and I would like to ensure that we have the best team reviewing the specs as we can. Current reviewers comprise the openEHR Archetype Editorial Group plus existing adopters of the archetype, however we welcome broader expertise from the broader openEHR community. If you, or one of your colleagues, would like to participate in the review, please log in and adopt the archetype. Instructions and diagrams for adopting are found at http://www.openehr.org/wiki/display/healthmod/Adopt+an+archetype All adoptors will be included in the ongoing review process. [If you are a registered CKM user, and/or subscribe to multiple openEHR lists, you may have received this notification several times - my apologies;-)] Kind Regards Heather Leslie (Editor) -- Dr Heather Leslie MBBS FRACGP FACHI Director of Clinical Modelling Ocean Informatics <http://www.oceaninformatics.com/> Phone (Aust) +61 (0)418 966 670 Skype - heatherleslie __________ Information from ESET NOD32 Antivirus, version of virus signature database 4219 (20090705) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _____ _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical __________ Information from ESET NOD32 Antivirus, version of virus signature database 4219 (20090705) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- Dr Heather Leslie MBBS FRACGP FACHI Director of Clinical Modelling Ocean Informatics <http://www.oceaninformatics.com/> Phone (Aust) +61 (0)418 966 670 Skype - heatherleslie -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20090707/cdf7784c/attachment.html>
