READIT - 2009 - Indira Gandhi Centre for Atomic Research

More documents

Recommendations

Info

Proceedings of READIT-2009, Kalpakkam - 603 102, 29-30 Dec 2009 Folders Compositions Sections Entries Clusters Elements Data Values High level organization of EHR – per episode A clinical care session – test result Clinical headings reflecting workflow and consultation Clinical statement about observation, evaluation, instruction, etc. Nested multi part data structures Leaf node with single node value – body weight Data types for instance values – coded terms, measurements with units Table 1: CEN TC251 HL7 – There are HL7 Reference Information Model, Clinical Document Architecture and Messaging standard. There is no underlying reference model. CDA is a document markup standard developed by Health Level Seven. The document is encoded in XML. CDA distinguishes three levels of granularity. The documents derive their meaning from HL7 RIM. Level one focuses on content of narrative documents. Level two allows constraining the structure and content of the document using templates. Level three is for machine processing [11,12,13]. ISO TC215 – There are several working groups including work group for data structure, messaging and communication, health concept representation, security, health card, pharmacy and medication, devices and business requirements for electronic health records. 6. WEB SERVICE A web service can be defined as a network accessible interface to application functionality, built using standard internet technologies [1]. Web service provides an interface between the application code and the user of the code. It behaves as an abstraction layer separating platform and program-language-specific details of how application code is actually invoked. The standardized layer permits any language that supports web service to access the application’s functionality. Interoperability is a key benefit from implementing web services. It does not matter if the application logic is written in Java and the browser in C++. The application services can be deployed on any platform and the browser can be deployed in some other platform say the former in UNIX and the later in Windows. Still web services layer between the client and the application can remove the friction. Web services can be assumed as a messaging framework. Using some combination of standard internet protocols web services sends and receives messages. 67
Proceedings of READIT-2009, Kalpakkam - 603 102, 29-30 Dec 2009 APPLICATION CODE WEB SERVICE APPLICATION CLIENT PLATFORM AND LANGUAGE SPECIFIC COMMUNICATION PLATFORM AND LANGUAGE NEUTRAL COMMUNICATION Fig 1: Web Service – Abstraction layer Service Registry FIND PUBLISH Service Customer Service Provider BIND Fig 2: Web Service – Architecture Remote clients and applications (Service customer) uses XML for data transport and SOAP (Simple Object Access Protocol) for using the service. Web service can be thought of as component architecture over the web. Similar to the component development model, web services must support registration with lookup services and a public interface for the client to invoke the service. Each web service must register itself with a central repository and the clients can lookup the registry for a desired service. When a service is located the client has to obtain the reference to the service. The service provider must publish the public interface for the service so that the clients can invoke the various methods using the reference. A web service receives information from the client in the form of messages similar to method calls. On completion of the service the response message is encoded in XML. Public interfaces and the repositories are also implemented in XML. XML provides platform neutral data transport. Theoretically XML based web services can thus interoperate with another XML based web service provided both the services agree upon common protocols for communication. We now discuss on the most commonly used web service technologies. To create a web service the following technologies are used. SOAP – Simple Object Access Protocol is a lightweight and simple XML based protocol. It promotes exchange of structured and typed information on the web by describing messaging format for machine-to-machine communication. WSDL – Web Services Description Language is an XML format for describing the web service interface. It also covers information on the data types for all message requests and responses. Additionally 68
Page 1 and 2:
National Conference on Recent Advan
Page 3 and 4:
Foreword The 7th biennial national
Page 5 and 6:
access to information resources. RF
Page 7 and 8:
Organising Committee READIT-2009 Ch
Page 9 and 10:
Invited Presentations: CONTENTS Ses
Page 11 and 12:
C. Jaykumar, E. Soundararajan, V. R
Page 13 and 14:
Session-I: Semantic Web Technologie
Page 15 and 16:
Proceedings of READIT-2009, Kalpakk
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Session-III: Open Source Solutions
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Session-IV: Knowledge Management Pr
Page 31 and 32:
Page 33 and 34: Proceedings of READIT-2009, Kalpakk
Page 41 and 42: totally around Internet protocols a
Page 43 and 44: Linux has been under continuous dev
Page 83: Proceedings of READIT-2009, Kalpakk
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
upon by indwelling and is the basis
Page 165 and 166:
new, and its combination of new ide
Page 167 and 168:
o Knowledge: Both explicit and taci
Page 169 and 170:
Knowledge Management Practices in L
Page 171 and 172:
To these paraphrases of Macintosh
Page 173 and 174:
(iii) Healthy interactions among pr
Page 175 and 176:
9. CONCLUSION Knowledge management
Page 177 and 178:
Ontologies define a common vocabula
Page 179 and 180:
to have an environment that allows
Page 181 and 182:
CDPS PC System Based SS-I SS-II RAA
Page 183 and 184:
Preservation of Manuscripts with Sp
Page 185 and 186:
- (Many more) 3 Chemical Factors a.
Page 187 and 188:
6.2.2 Software The Softwares requir
Page 189 and 190:
7.1.3 Current Work As the above pro
Page 191 and 192:
Treatment process 7.2.6 Drying Afte
Page 193 and 194:
Before Editing & Cropping After Edi
Page 195 and 196:
Knowledge Management - An Organizat
Page 197 and 198:
5. KNOWLEDGE MANAGEMENT ACTIVITIES
Page 199 and 200:
Management System and is made avail
Page 201 and 202:
Services 3.0 make it easier than ev
Page 203 and 204:
ecover data when a disk fails and r
Page 205 and 206:
Symmetric Multi Processing (SMP) Se
Page 207 and 208:
Knowledge management practice in li
Page 209 and 210:
3. KNOWLEDGE MANAGEMENT: SOME DEFIN
Page 211 and 212:
It is to create a set of effective
Page 213 and 214:
REFERENCES 1. Banka Bihari Chand (2
Page 215 and 216:
2 Fig : 1. Five ‘ C ‘ Model Kn
Page 217 and 218:
4 Knowledge acquisition is the star
Page 219 and 220:
6 group of audience. Similarly wit
Page 221 and 222:
8 Knowledge sharing is enhanced by
Page 223 and 224:
10 sharing, and creating a map of
Page 225 and 226:
12 10. REQUIRED SKILLS AND CAPABILI
Page 227:
14 Wireless Communication, Networki
show all

READIT - 2009 - Indira Gandhi Centre for Atomic Research

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?