Heath Are there people interested in providing clinical scenarios and data to assist in the requirements and content gathering process to be used in clinical workflow simulations? How can we initiate and progress this kind of activity and investigation?
Try contacting NICS - the National Institute of Clinical Studies http://www.nicsl.com.au/asp/index.asp They may be interested in assisting with this work. Gordon Tomes Projects Director Acute Care Division Department of Health and Ageing (MDP 63) PO Box 9848, Canberra ACT 2601 Ph 02 6289 5081 | Mobile 0423 024 922 | Fax 02 6289 7630 2006 Biennial Health Conference Exploring and debating acute care provision 14-16 November, Sydney, Australia for the latest information visit http://www.healthconference.com.au/ "Heath Frankel" <heath.frankel at frankelinformatics.com> Sent by: openehr-technical-bounces at openehr.org 15/09/2006 12:04 PM Please respond to For openEHR technical discussions To: "'For openEHR technical discussions'" <openehr-technical at openehr.org> cc: Subject: RE: Sources of information on HL7 EHR/OpenEHR Gerard, Interesting you raise this topic as it is becoming an interest of mine to start investigating the use of openEHR instructions to support the documentation requirements of clinical workflows such as medication prescriptions, dispense and administration, and referrals. The existing work of ContSys could certainly assist in this but being a techo, I need some clinicians to assist in developing these requirements and my Ocean clinician colleagues are already over extended. As you know, Ocean has and continues to develop the tools to support a simulation of these kind of clinical workflow scenarios and are looking for ways to gather more and varied clinical content to populate and test the OceanEHR suite. Are there people interested in providing clinical scenarios and data to assist in the requirements and content gathering process to be used in clinical workflow simulations? How can we initiate and progress this kind of activity and investigation? Regards Heath Heath Frankel Product Development Manager Ocean Informatics Ground Floor, 64 Hindmarsh Square Adelaide, SA, 5000 Australia ph: +61 (0)8 8223 3075 fax: +61 (0)8 8223 2570 mb: +61 (0)412 030 741 email: heath.frankel at oceaninformatics.biz From: [email protected] [mailto:openehr-technical-bounces at openehr.org] On Behalf Of Gerard Freriks Sent: Friday, 15 September 2006 7:39 AM To: For openEHR technical discussions Subject: Sources of information on HL7 EHR/OpenEHR Dear all, The 'next frontier' will be the various types of "workflow" and the interaction with the EHR and other components in an EHR-system. Before rushing into quick decisions and quick fixes I call for a study of: - CEN/tc251 System of Concepts for Contuity of Care, ContSys. - CEN/tc251 Health Information Services Architecture, HISA. The first contains the set of concepts dealing with co-operation between healthcare providers around the care of a patient. Several concepts dealing with care plans, clinical path ways in various sorts are defined. The second can help us think about the various levels where types of workflow take place because it defines in a generic way EHR-system components,their inter faces and behaviour. Each type of workflow will use its own model and behaviour of its components. The whole exercise needs to start with a validated set of requirements and the study of some important literature. It is my expectation that En13606/openEHR, ContSys and HISA contain more than enough ingredients to find a good solution. With regards, Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 653 108732 there are two levels of expression of clinical knowledge, guidelines, evidence etc that we can use, namely a1) guidelines etc that are mentioned in an archetype, and inform the design of the archetype. This can be done as I described. In this case, the guideline or other knowledge reference is the same for all data built from the archetype. a2) resources that are referenced on a per-archetype basis, but not in the archetype, rather they are referenced from the archetype classification ontology that indexes archetypes b) guidelines referenced in data, i.e. on a per instance basis. On the model you see here: http://www.openehr.org/uml/release-1.0/Browsable/_9_0_76d0249_1109249648736_872559_12384Report.html the class CARE_ENTRY has the attributes "protocol" (how / why did I create this clinical statement/observation/whatever), "guideline_id" that enables the referencing of guideline that caused this Entry to be created (e.g. maybe some guideline told the doc to measure the BP and also ask questions about smoking); ENTRY.workflow_id may also be relevant, for Entries created due to workflow execution. I would think these go close to supporting today's requirements in this area, although I realise we cannot predict the requirements of the future... _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical ******************************************************************************** "Important: This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error please notify the author immediately and delete all copies of this transmission." ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060918/76691f6d/attachment.html>
