Health Information and Integration Platform ontology
|
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
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 Adjunct Professor, Victoria University, Melbourne ACHI Council member Standards Australia member ehovenga@gmail.com evelyn@evelynhovenga.com e.hovenga@ehealtheducation.net Mob +61 (0)408 309839 Qld Office Ph. +61 (0)7 4921 3029 |
_______________________________________________ openEHR-clinical mailing list openEHR-clinical@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical