Bio-medical Ontologies Maintenance and Change Management

More documents

Recommendations

Info

Design of an Online Physician-Mediated Personal Health Record System 271 Hospital Directory File Encryption Decryption Engine Public EMR Health Blog Engine Physician Directory File PHR Documents Data Extract Transform and Load Engine (ETL) Personal Profile Engine PHO Oracle DBMS Engine Authorization Engine Charting Engine Fig. 1. The Personal Health Office (PHO) architecture framework • Encryption/Decryption Engine. At the 3rd and interaction layer, this module is responsible for securely encoding and decoding of the patient PHR data during secure storage and transmission sessions. • Health Blog Engine. At the 3rd and interaction layer, this module is responsible for supporting patient’s personal health blog record management. • Personal Profile Engine. At the 3rd and interaction layer, this module enables the storage and retrieval of system user’s personal profile such as medication, allergies, contact informaiton, and current disease treatments. • Authorization Engine. At the 3rd and interaction layer, this module help manage patient’s access permission requests, perform physician‘s authorization to approve or deny patient requests to access their hospital records, and process these access requests using secure protocols. • Charting Engine. At the 3rd and interaction layer, this module is responsible for retrieving the patient’s health events and converting them to easy-to-comprehend graphical health charts. • Annotation Engine. At the 3rd and interaction layer, this module is responsible for inserting patient’s annotations on his personal health charts in the database. A chronological annotation log can be maintained in the chosen database. It also retrieves the saved annotations for reviews. • Authentication Engine. At the 3rd and interaction layer, this module performs user logon authentication of the PHO web system. It checks the credentials of the user to access approved features. Charts Lab Tests Annotation Engine Review Comments PHR Lab Test Results Authentication Engine PHO Database
272 J.Y. Chen, S. Taduri, and F. Lloyd This design has several advantages compared with existing systems. First, the design incorporates multiple data sources, which can be derived from bulk public directory information with hospital EMRs and personal PHR health selfmanagement data; therefore, it can be used to develop comprehensive datadriven patient-centric PHR applications. Second, the design converges on robust database management system which underpins a set of functional modules; therefore, the system is scalable and adaptable to changing individual user needs. Third, the management of health data has extensive built-in security and access control both at the database layer (Oracle DBMS functions) and the application layer (encryption/decryption, authentication and authorization engines). Fourth, the framework is very flexible and extensible; one can add multi-media presentations such as treatment educational videos, mp3 audios for latest treatment/health tips, and annotated image from pathology/radiology labs. 4 Usage and Functional Interactions In the previous section, we showed a framework design which shows all the components the PHO system should have in order to address current challenges in developing PHO systems. In this section, we further show how the primary users of this system could interactively use the PHO software. In Fig. 2, we show such a system relies on a web server that serves various user requests via secure http protocols. The system sets diffeent types of access privileges to three different types of users, i.e., patients, physicians, and web administrators. Depending on the type of user roles, the PHO system customizes user-specific interfaces and functional features. Key to this functional interaction paradigm is a new concept, Physicianmediated Patient EMR Review. This new concept addresses the difficult problem of enabling individual access to hospital EMRs, which traditionally is paper-based and slow, because it needs to involve hospitals and HIPAA regulations. The concept is an attempt to solve the problem, which is that hospitals own the information content located in their protected EMRs yet don’t have all the right to access the content, while individual users have the rights to access their own records yet don’t own the information/software located in the hospital EMR. The solution lies in introducing physicians into the interaction paradigm for two reaons: first, physicians are pre-authorized to access hospital EMRs related to their own patients legally; second, physicians are motivated to help their own patients access their own records conveniently, if such help could bring satisfied patients, reduced medical errors, increased patient cooperation, and increased efficiency while receiving patients in the clinic. The concept works in the following five steps: 1. Request. A patient logs in his PHO system and issue multiple requests to his/her physicians at different hospitals for permissions to access his/her own hospital EMR data. He then logs out and waits for approvals. 2. Approve. One of the patient’s physician logs into the third-party PHO system (not inside hospital EMR system) later and find several of patients‘ requests for accessing to different types of their medical records. The physician either approves or denies access to his/her requesting patients.
Page 1 and 2:
Amandeep S. Sidhu and Tharam S. Dil
Page 3 and 4:
Amandeep S. Sidhu and Tharam S. Dil
Page 5 and 6:
Preface The molecular biology commu
Page 7 and 8:
Preface VII biomedical systems, and
Page 9 and 10:
X Contents Mining Clinical, Immunol
Page 11 and 12:
2 A.S. Sidhu, M. Bellgard, and T.S.
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Towards Bioinformatics Resourceomes
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
2 The New Waves Towards Bioinformat
Page 27 and 28:
2.4 Semantic Web Towards Bioinforma
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
A Summary of Genomic Databases: Ove
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Appendix A Summary of Genomic Datab
Page 61 and 62:
Protein Data Integration Problem Am
Page 63 and 64:
Protein Data Integration Problem 57
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Fig. 3. Class Hierarchy of Protein
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
72 L. Stanescu, D. Dan Burdescu, an
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
100 L. Stanescu, D. Dan Burdescu, a
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
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:
Bio-medical Ontologies Maintenance
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
TextToOnto (Maedche and Volz 2001)
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Extraction of Constraints from Biol
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Classifying Patterns in Bioinformat
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Mining Clinical, Immunological, and
Page 217 and 218:
Page 219 and 220:
Page 221 and 222: Mining Clinical, Immunological, and
Page 241 and 242: Substructure Analysis of Metabolic
Page 253 and 254: entry compound relation subtype com
Page 257 and 258: Running Time 4500 4000 3500 3000 25
Page 263 and 264: 6 Conclusion Substructure Analysis
Page 267 and 268: 266 J.Y. Chen, S. Taduri, and F. Ll
Page 271: 270 J.Y. Chen, S. Taduri, and F. Ll
Page 281 and 282: Completing the Total Wellbeing Puzz
Page 295 and 296: 296 M. Fernandez, M. Villasana, and
Page 315 and 316: Genetic Algorithm in Ab Initio Prot
Page 323 and 324:
Genetic Algorithm in Ab Initio Prot
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341:
Author Index Apiletti, Daniele 169
show all

Bio-medical Ontologies Maintenance and Change Management

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

Delete template?

Save as template?