Recently several organizations in the healthcare sector have produced standards and representation forms using XML. However, the introduction of these XML-based technologies is not enough to provide a means to interpret the semantics of the exchanged messages. Instead communicating medicinal information systems are hard-coded to only work together. As a result extending the systems by new parties as well as introducing new message types is inconvenient typically requiring long lasting standardization processes. How to replace hard-coded medicinal information systems by the open healthcare information systems that support semantic interoperability, are extensible and maintainable is the topic of this paper. In particular, we described our work on using RDF-statements in exchanging messages. In such a setting, the semantics of the exchanged data is available with the data, which makes the data machine processable. We also describe how communicating medicinal information systems can use XSLT-transformations in picking out their needed information from the exchanged messages.
"Whether these goals can be achieved by utilizing Semantic Web-technologies  is the main topic of this article. The article extends the work presented in . The rest of the article is organized as follows. "
[Show abstract][Hide abstract] ABSTRACT: The allocation of clinical resources for healthcare processes in a transactional (atomic) way is a complex task. It requires the cooperation of heterogeneous medical information systems that are typically based on proprietary solutions, developed in piecemeal way, and tightly coupled through ad hoc means. In addition, the resources required for a health care process have mutual timing constraints, which further complicate resource allocation. In this paper we have restricted on these problems. In order to achieve the semantic interoperability between the managers of the clinical resources, we have developed a resource ontology, which constitutes the vocabulary for the exchanged reservation messages. The resource ontology is specified by OWL, and the content of the exchanged messages are presented in RDF. The resource allocation processes are specified by Business Process Modeling Notation (BPMN). We have also developed a specific transaction model for atomic compositions of resource allocations, i.e., it ensures that all or none of the requested resources are reserved. The gain of using this transaction model is that we can avoid the cancelations of the resources allocations that are caused by the unrealized timing constraints.
iiWAS'2009 - The Eleventh International Conference on Information Integration and Web-based Applications and Services, 14-16 December 2009, Kuala Lumpur, Malaysia; 01/2009
[Show abstract][Hide abstract] ABSTRACT: Semantic Web Services (SWS) aim at developing a machine understandable and common conceptual framework which share and accumulate concepts from different web service resources to meet a particular objective in question. Different SWS composition methods have been developed for different purpose and objectives. We have developed an agent based SWS composition method using two sets of agents i.e. Service Requester Agent (SRA) and Service Provider Agent (SPA) to represent the user's side and the solution side respectively for the problem of a medical health planning. The SRA corresponded to the patients' requirements of different consulted doctor and the SPA corresponds to hospitals and doctors, who specializing in a particular disease's cure from different places. The medical health planning is primarily based on the doctor's specialization and location. The knowledge concerned is represented in OWL, query with SPARQL, and Jena API package for interaction between Java and OWL-RDF files. We have taken a different hospitals and doctors. The composed result consists of information of different doctor form different hospitals for a particular disease.
Note: This list is based on the publications in our database and might not be exhaustive.
Data provided are for informational purposes only. Although carefully collected, accuracy cannot be guaranteed. The impact factor represents a rough estimation of the journal's impact factor and does not reflect the actual current impact factor. Publisher conditions are provided by RoMEO. Differing provisions from the publisher's actual policy or licence agreement may be applicable.