Search Constraints
Results for:
Business Strategy
Remove constraint Business Strategy
Search Results
-
e-book
-
Others
-
Presentation
This video was recorded at CeGD eGovernance Academy Seminar Series (SEeHealth): The Roadmap from Concept to Practice, Ljubljana 2010. The key of mutual integration of health care institutions lies in their interoperability, gathering and common utilization of data by different applications. Seemingly, imperceptible and smooth applications' integration enables an efficient mutual linkage of all departments within a single health care institution as well as horizontal and vertical linkage of more health care institutions, all with the aim of improvement of health and quality of patient's life. Health care system quality improvement needs a continuous rationalization of resources funds, which leads towards optimization of business processes and availability of all necessary information in the shortest possible period. All necessary information and data on patients must be available independently on location or time of such a necessity. The greatest obstacles for interoperability represent heterogeneous applications. Such heterogeneity can be presented by the fact that they were written in various program languages, that they are intended for utilization at different types of computers or the fact that they use various communication networks and data transfer methods. IT managers in hospitals must decide how to contribute to cross‐organizational integration and what strategy and means to choose for achieving interoperability. If a system is poor in its interoperability, any increasing functions or little changes could stop its working properly. Interoperability must be ensured at technical, semantic and process levels but also in a legislative level, where all recommendations for legal and lawful solutions are given, which remove the most frequent obstacles – human and bureaucratic factors. The Oncology Institute of Vojvodina as a referent center for oncology and a center for medical informatics signed its own Integrated hospital and business information system. The information system at the IOV consists of the following modules: 1. hospital‐clinical IS 2. laboratory IS 3. pharmaceutical IS 4. radiological IS 5. invoicing (accounting) IS 6. business IS 7. managerial IS All of these modules are mutually optimally integrated, and their interoperability at the level of communicational protocols (HL7, DICOM, internal interface), semantics (the same code‐records, rules) and legislative level (the same accounting calculations) enables the user to see all these complex modules as one system. Thus, we created necessary preconditions for our integration into information society, which is a 21st century strategy at the state level.
-
Presentation
This video was recorded at 7th International Semantic Web Conference (ISWC), Karlsruhe 2008. The documentation of Enterprise Research Planning (ERP) systems is usually (1) extremely large and (2) combines various views from the business and the technical implementation perspective. Also, a very specific vocabulary has evolved, in particular in the SAP domain (e.g. SAP Solution Maps or SAP software module names). This vocabulary is not clearly mapped to business management terminology and concepts. It is a well-known problem in practice that searching in SAP ERP documentation is difficult, because it requires in-depth knowledge of a large and proprietary terminology. We propose to use ontologies and automatic annotation of such large HTML software documentation in order to improve the usability and accessibility, namely of ERP help files. In order to achieve that, we have developed an ontology and prototype for SAP ERP 6.0. Our approach integrates concepts and lexical resources from (1) business management terminology, (2) SAP business terminology, (3) SAP system terminology, and (4) Wordnet synsets. We use standard GATE/KIM technology to annotate SAP help documentation with respective references to our ontology. Eventually, our approach consolidates the knowledge contained in the SAP help functionality at a conceptual level. This allows users to express their queries using a terminology they are familiar with, e.g. referring to general management terms. Despite a widely automated ontology construction process and a simplistic annotation strategy with minimal human intervention, we experienced convincing results. For an average query linked to an action and a topic, our technology returns more than 3 relevant resources, while a naïve term-based search returns on average only about 0.2 relevant resources.
- Subjects:
- Computing, Data Science and Artificial Intelligence and Management
- Keywords:
- Software documentation Enterprise resource planning Ontologies (Information retrieval)
- Resource Type:
- Presentation
-
-
Presentation
This video was recorded at 11th International Semantic Web Conference (ISWC), Boston 2012. The New York Times committment to Linked Data began over 160 years ago. Starting in 1851, The New York Times has always catalogued its archival articles using a controlled vocabulary of people, places, organizations and descriptors. In 2009 The New York Times started publishing this vocabulary as linked data using semantic web standards. In 2011 The Times announced the launch of several RESTful Semantic APIs. And in late 2012 and early 2013, The Times will migrate its entire process for vocabulary management to a system designed around the principles of Linked Data. In my remarks, I will survey the history of Semantic publishing at The New York Times, outline our semantic strategy, detail the business-case for linked data at The Times and provide an in-depth explanation of our new vocabulary management system.
- Subjects:
- Computing, Data Science and Artificial Intelligence and Management
- Keywords:
- New York times Linked data
- Resource Type:
- Presentation
-
-
Courseware