Semantic Integration of eGovernment Services in Schleswig-Holstein

Bednár, Peter; Furdik, Karol; Kleimann, Maren; Klischewski, Ralf; Skokan, M.; Ukena, Stefan

doi:10.1007/978-3-540-85204-9_27

Cited by 5 publications

(6 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To this end the idea of metadata has been introduced to e-government [47], and interfaces of e-government services have been semantically enhanced by employing a web service ontology ( [3], [41], [50]). …”

Section: In Search Of Mastering E-government Interoperabilitymentioning

confidence: 99%

Architectures for Tinkering?: Contextual Strategies towards Interoperability in E-government

Klischewski

2011

J. theor. appl. electron. commer. res.

Self Cite

View full text Add to dashboard Cite

Research has revealed the entanglement of e-government strategy and information infrastructure and that the control of infrastructures often remains an illusion as actual development and implementation is challenged by a constant drift. However, guidelines for public sector CIOs how to deal with these challenges remain scarce: Are governments well advised using architectures and other conceptualizations as tools in a top-down implementation of an infrastructure based on a preset interoperability strategy? Or should governments rather develop contextual strategies that build on the understanding of the actual drift of infrastructures and employ selected architectures only as facilitators for stakeholder communication during the next phase of interoperability achievement? In view of nowadays available theoretical reflections, the case of Egypt is analyzed to examine the role of service-oriented architecture in the control and drift of the G2G infrastructure.Findings reveal that what at first seemed to be an immature vendor-driven "technology-first" approach with a clear absence of IT governance strategy, in retrospect can be considered as the appropriate choice of architecture because it has successfully impacted agendas of most local stakeholder to move into the direction of e-government interoperability. Attempting to generalize, it is suggested that strategies towards e-government interoperability should select architectures based on reflection of the specific implementation context: to embrace existing infrastructure components, to be comprehensible and acceptable by the stakeholders involved, to be suitable for designing and standardizing the next generation of component interfaces, and to provide a timelimited frame for "tinkering," i.e. allowing stakeholders to find their own way of embracing and implementing the concepts in focus.

show abstract

Section: In Search Of Mastering E-government Interoperabilitymentioning

confidence: 99%

Architectures for Tinkering?: Contextual Strategies towards Interoperability in E-government

Klischewski

2011

J. theor. appl. electron. commer. res.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Using already existing ontologies assures a consistency with the widely accepted standards and avoids unnecessary double work. About 25 ontology resources and standards were analysed [3], and the following ones were finally selected for reuse: Dublin Core (Site 4), SKOS ( Figure 1). (templates).…”

Section: Access-egov Ontologiesmentioning

confidence: 99%

“…The above mentioned WSMO Studio can be, in principle, used as such a tool, but it is dedicated mostly for WSMO/WSML specialists and is too complicated for standard PA employees with very limited or no knowledge of semantic technologies. For this reason, a specialised Annotation Tool [3] (Figure 4) has been developed in the project, which is easy-to-use and requires only standard PC skills.…”

Section: The Annotation Toolmentioning

confidence: 99%

See 1 more Smart Citation

Integration of Government Services using Semantic Technologies

Hreno

Bednár

Furdik

et al. 2020

J. theor. appl. electron. commer. res.

Self Cite

View full text Add to dashboard Cite

The paper describes an approach to semantic interoperability of eGovernment services applied within the 027020 FP6 IST Access-eGov project. The goal of the project was to improve accessibility and connectivity of governmental services for citizens and businesses by means of creating integrated scenarios and providing guidance to users while following this scenario. The scenario helps the user to identify and fulfil any needed electronic or real governmental services in a selected life situation. The Access-eGov project has developed software tools enabling service integration using semantic technologies. In addition to that, a methodology providing guidance to the user-driven process of creating ontologies was developed. Sample ontologies were prepared for trial applications. The developed tools support browsing, discovery, and execution of government services according to a selected life event or goal. The project successfully developed and tested the proposed solutions. The software developed within the project is available as open source software.

show abstract

“…Research to better model and validate systems has been driven by problems from the manufacturing industry [6,7] and electronic business [8,9,10]. More recently, the same kind of problems have been encountered while integrating governmental services [11], automating precast fabrication and construction [12,13], and integrating electricity distribution [14]. The method followed in this paper was inspired by the analysis of integration problems encountered in the automotive industry [7].…”

Section: Introductionmentioning

confidence: 99%

Requirements for Interoperability in Healthcare Information Systems

Noumeir

2012

Journal of Healthcare Engineering

View full text Add to dashboard Cite

Interoperability is a requirement for the successful deployment of Electronic Health Records (EHR). EHR improves the quality of healthcare by enabling access to all relevant information at the diagnostic decision moment, regardless of location. It is a system that results from the cooperation of several heterogeneous distributed subsystems that need to successfully exchange information relative to a specific healthcare process. This paper analyzes interoperability impediments in healthcare by first defining them and providing concrete healthcare examples, followed by discussion of how specifications can be defined and how verification can be conducted to eliminate those impediments and ensure interoperability in healthcare. This paper also analyzes how Integrating the Healthcare Enterprise (IHE) has been successful in enabling interoperability, and identifies some neglected aspects that need attention. RESULTSIn this section, we analyze the technical, semantic, functional, quality and logistical integration aspects. For each category, interoperability impediments are described and discussed; we give examples derived from the healthcare domain, and provide guidance to mitigate the impediment at the specification and testing levels. Technical Concerns Connection ImpedimentThis impediment occurs when there is a disagreement between components at the communication level, including the lower layer protocols (LLP). An obvious example is when peers are not using the same version of the standard, such as when one is using HL7 version 2.3 and the other is expecting HL7 version 2.5. Although newer versions of HL7 v2 are backward compatible, interfaces between systems may be necessary to remove new fields not supported by older versions. Likewise, using the DICOM standard, peers may not agree on the service-object pair (SOP) Class, i.e., the service (or action) to be executed on the information object. Another example occurs when one peer is using secure socket and the other does not support secure communication.In order to eliminate this impediment, requirements for the communication protocol, its version, and the underlying LLP must be specified. Moreover, when the communication protocol allows for multiple possibilities, one specific possibility must be specified. For example, when security is required, one needs to specify what kind of certificate is to use, whether encryption is required and what type of encryption algorithms is supported. The testing software issues transactions using the specified protocol and the specified LLP to verify whether the connection could be established with the system under test and information could be exchanged.IHE has succeeded in eliminating this impediment by specifying, for each transaction, the communication standard to be used, such as DICOM or HL7. Moreover, it specifies the version of the standard when multiple versions exist. For example, the Modality worklist query is achieved using the DICOM standard (Radiology [19]); the Patient Identification Query is achieved using HL7 v2....

show abstract

Semantic Integration of eGovernment Services in Schleswig-Holstein

Cited by 5 publications

References 3 publications

Architectures for Tinkering?: Contextual Strategies towards Interoperability in E-government

Architectures for Tinkering?: Contextual Strategies towards Interoperability in E-government

Integration of Government Services using Semantic Technologies

Requirements for Interoperability in Healthcare Information Systems

Contact Info

Product

Resources

About