Thanks Evelyn,

You're not afraid of a "grand challenge" then.. ;o)

Without going into any detail, the distinct areas that I would describe as;
#Information management -specific to a patient patient (eg EHR for
patient with Chest Pain and Diabetes)
and
#Knowledge management - agnostic of a patient patient (eg passive/active
Decision Support for management of Chest Pain/ Diabetes)
..are poorly understood with most people, often knitting them together
in their thinking and solutions.. is a key area where this could help..

Kind regards,

Tony


Dr. Tony Shannon
Consultant in Emergency Medicine, Leeds Teaching Hospitals
Clinical Lead for Informatics,    Leeds Teaching Hospitals
Chair, Clinical Review Board, openEHR Foundation
+44.789.988 5068            tony.shannon at nhs.net




Koray Atalag wrote:
> Hi Evelyn, what a fantastic initiative...I am really quite disturbed how
> these fundamental terms are being used inconsistently. Here are the most
> difficult ones for me:
>
>
>
> -          Clinical model (can be a model patient for med students! If
> context is not given)
>
> -          Clinical information model (originally this refers to
> knowledge artifacts as you say but that is difficult to comprehend by
> non-openEHR/13606/HL7 aware people. This is commonly mistaken for RIM)
>
> -          Concept model (too generic)
>
> -          Clinical concept model (not too bad ? but doesn?t say much
> about the nature of modelling)
>
> -
>
> Also please add these to you list:
>
>
>
> -          Clinical data set
>
> -          Clinical data repository
>
> -          Meta-data repository
>
> -          Clinical concept repository
>
> -          Minimum data sets
>
> -          Core data sets
>
> -          Clinical core data sets
>
> -          National collections
>
> -          Registries (clinical/disease etc.)
>
> -          Research databases
>
>
>
> Will continue...
>
>
>
> Cheers,
>
>
>
> -koray
>
>
>
> *From:* openehr-clinical-bounces at openehr.org
> [mailto:openehr-clinical-bounces at openehr.org] *On Behalf Of *Hugh Leslie
> *Sent:* Sunday, 27 June 2010 2:35 a.m.
> *To:* openehr-clinical at openehr.org
> *Subject:* Re: Health Information and Integration Platform ontology
>
>
>
> Good idea Evelyn - I am happy to help.
>
> On 26/06/2010 11:54 PM, Evelyn Hovenga wrote:
>
> Colleagues,
>
>
>
> I would like to develop a high level ontology model of the health
> information and integration platform showing the entities, concepts  and
> their various relationships as a means of enabling us to clearly show
> what this is all about and to enable us to communicate to non technical
> people the implications (and limitations imposed)  of decisions made
> regarding the adoption of such a national infrastructure platform.  It?s
> about all the stuff that sits between  the hardware and software
> applications.  This area is not well understood by non technical people
> (including me) yet the term ? platform? is  used heavily for marketing
> purposes by big software suppliers.  An ontological model of this domain
> should serve us well for educational purposes.  I?d like to adopt the
> clinical knowledge artifacts (my generic term for archetypes or detailed
> clinical models) as central to such a platform as these provide the
> foundation for all health information and processing needs at the
> individual, local, organisational, national and international levels.
>
>
>
> I would welcome your views on which entities and concepts (and their
> associated generic names)  to include in such an ontological model.   At
> this stage my review of the literature etc has resulted in the following
> list but I need help in defining these and their relationships in a
> generic  mutual exclusive sense as clearly the adoption of one or more
> specific entities/concepts influences others either positively or
> negatively.  Many different platforms are in existence  but how does one
> evaluate their completeness, functionality, efficiency, effectiveness,
> impact on patient safety or outcomes?  The terms below are used in non
> standard ways making it difficult to gain a clear understanding about
> these from the literature.
>
>
>
> Reference information model
>
> Data types
>
> Service Oriented Architectures
>
> Web services
>
> Clinical Knowledge Repository
>
> Terminology server
>
> Clinical modelling tools
>
> Tooling to convert clinical knowledge to machine processable schema or
> templates
>
> EHR services
>
> Longitudinal EHR services
>
> Technology platform eg .net, java, mobile versions
>
> Middleware products
>
> GUI Standards & frameworks
>
> Identifiers standard
>
> Demographic service
>
> Application development platform
>
> Knowledge management platform
>
> Semantic interoperability
>
> Functions such as authentication of users and applications, guaranteed
> delivery of messages between components and users, logical connections
>
> Consent management services
>
>
> I look forward to your comments.
>
> Evelyn
>
> *Evelyn J.S Hovenga RN PhD FACS FACHI*
>
> Professor & Director  eHealth Education Pty Ltd
>
> Director of EJSH Consulting,
>
> PO Box 9783 Frenchville, Rockhampton Qld 4701
>
>
>
> Editor in Chief, eJHI http://www.ejhi.net <http://www.ejhi.net/>
>
> Adjunct Professor, Victoria University, Melbourne
>
> ACHI Council member
>
> Standards Australia member
>
>
>
> ehovenga at gmail.com <mailto:ehovenga at gmail.com>
>
> evelyn at evelynhovenga.com <mailto:evelyn at evelynhovenga.com>
>
> e.hovenga at ehealtheducation.net <mailto:e.hovenga at ehealtheducation.net>
>
> Mob +61 (0)408 309839
>
> Qld Office Ph. +61 (0)7 4921 3029
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> openEHR-clinical mailing list
>
> openEHR-clinical at openehr.org <mailto:openEHR-clinical at openehr.org>
>
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>
>
>
> --
>
> ________________________________________________
> Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI
> Clinical Director
> Ocean Informatics Pty Ltd
> M: +61 404 033 767   E: hugh.leslie at oceaninformatics.com
> <mailto:hugh.leslie at oceaninformatics.com>  W: www.oceaninformatics.com
> <http://www.oceaninformatics.com>
>

--
Dr. Tony Shannon
Consultant in Emergency Medicine, Leeds Teaching Hospitals
Clinical Lead for Informatics,    Leeds Teaching Hospitals
Chair, Clinical Review Board, openEHR Foundation
+44.789.988 5068            tony.shannon at nhs.net

********************************************************************************************************************

This message may contain confidential information. If you are not the intended 
recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take 
any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff 
in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive information 
with NHSmail and GSI recipients
NHSmail provides an email address for your career in the NHS and can be 
accessed anywhere
For more information and to find out how you can switch, visit 
www.connectingforhealth.nhs.uk/nhsmail

********************************************************************************************************************



Reply via email to