WWW/Internet - Portal do Software Público Brasileiro

ISBN: 978-972-8939-25-0 © 2010 IADISThe ontology model is the abstract model. It is a set of classes and properties that model a domainconcept. The ontology (individuals) comprises of the instantiations of the ontology model. The individualsare concrete information or knowledge of a domain.The application model (APM) is a platform dependent or programming language specific implementationof the ontology model that translates the platform independent ontology model (e.g. provide in OWL) into aprogramming language structure (e.g. classes and relations or database schema).The application answer is the aim of the ODAM. Dependent on the ontology model, on the applicationmodel and on the ontology instances, an application derives its functionality dynamically and returns theapplication answer. The application answer is dependent on the requirements the ODAM is designed for.3.2 The SystemThe system is divided into a server side implementation that provides the semantic web application’sfunctionality, web services accesses and basic application logic. And the second part of the system is a clientimplementation to demonstrate the ISO 13606 compliant communication and to beautify the user interface.3.2.1 The ServerThe server is an implementation of two APMs, the Demographics APM and the EHR ontology APM.The demographic APM accesses the demographics ontology. The demographics ontology is an OWLmodel of the ISO 13606 demographic package provided as UML model. The application answer of theODAM is the identification of a patient or a healthcare professional.The EHR ontology APM accesses the EHR ontology. The EHR ontology is based on the work mentionedin section 0. We extended the union (the archetype ontology) of both ontologies to additionally meet thecriteria of the ISO 13606 part 1 reference model. Therefore we had to add the classes and properties ofEHR_EXTRACT and EXTRACT_CRITERIA to the archetype ontology. According to ISO 13606 standardan instance of EHR_EXTRACT represents the top-level container for each patient’s health data. An instanceof EXTRACT_CRITERIA covers meta-information that facilitates finding an EHR_EXTRACT instance.The “EHR Ontology APM” builds the accessor functionality to reveal the information of the individuals, andto work with this information programmatically. The application of the ODAM for this APM is also to createnew EHR extracts (updating or changing an extract means the creation of new version) to store new patientinformation in the EHR ontology combined with domain knowledge of the archetype description. This APMcan be seen as wrapper for all the 13606 relevant operations.The functionalities of the controller, basic application logic and the web services are to call the APMs andpass information from/to the web services. The basic application logic comprises: login – user authentication;user administration, patient search, patient documentation call (load, save EHR extracts, process insensitive);logout. The access to the System is provided through web services. These web services facilitate the access tothe patient demographics APM and the EHR ontology APM, wrapped by the controller and basic applicationlogic. Furthermore the web services are designed to meet the criteria of ISO 13606 Part 5 standard thatspecifies the interfaces to access EHR and archetypes and are implemented to handle security issues.3.2.2 The ClientThe client is a J2EE compliant web application written in Java (Java ServerFaces). The patients suffer fromchronic wounds and the aim of this implementation is to establish a multi professional homecaremanagement. We have been capturing archetype based EHR data for documenting patients with chronicwounds. The graphical user interfaces supports input validation derived from archetype constraints. Thefunctionality of the client is to pass the user input data from and to the web services. The application logic isbuild around the web services. The client implements session handling to prevent the user from logging inagain every time he/she calls a web service.4. DISCUSSION - ODAM AND ISO 13606The ODAM could be applied onto a non OWL-, programming language-, and relational database- dependentimplementation of ISO 13606 as well. Thus can play an important role for simplifying the implementation:336