LEADER 05436nam 2200637 450 001 9910809950403321 005 20200520144314.0 010 $a0-12-799919-1 035 $a(CKB)3710000000279287 035 $a(EBL)1838181 035 $a(SSID)ssj0001413434 035 $a(PQKBManifestationID)11777247 035 $a(PQKBTitleCode)TC0001413434 035 $a(PQKBWorkID)11430630 035 $a(PQKB)10872358 035 $a(Au-PeEL)EBL1838181 035 $a(CaPaEBR)ebr10989340 035 $a(CaONFJC)MIL127282 035 $a(OCoLC)897442538 035 $a(MiAaPQ)EBC1838181 035 $a(PPN)240178475 035 $a(EXLCZ)993710000000279287 100 $a20141208h20152015 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 00$aPractical guide to clinical computing systems $edesign, operations, and infrastructure /$fedited by Thomas H. Payne 205 $aSecond edition. 210 1$aLondon, England :$cAcademic Press,$d2015. 210 4$dİ2015 215 $a1 online resource (243 p.) 300 $aDescription based upon print version of record. 311 $a0-12-420217-9 320 $aIncludes bibliographical references and index. 327 $aFront Cover; Dedication; Practical Guide to Clinical Computing Systems: Design, Operations, and Infrastructure; Copyright; Contents; Contributors; Preface to the Second Edition; Preface to the First Edition; Chapter 1: Introduction and Overview of Clinical Computing Systems within a Medical Center; 1. The healthcare setting; 2. Rising dependence on clinical computing systems; 3. The importance of computing operations and support; 4. Importance of monitoring performance; 5. Real-world problems and their implications; 6. Introducing clinical computing systems can introduce errors 327 $a7. We need greater emphasis on safe operations of clinical computing systemsReferences; Chapter 2: Architecture of Clinical Computing Systems; 1. What is architecture, and why is it important?; 2. Architectural models; 3. Architecture of computing systems in healthcare organizations; 3.1. Core EHR (Electronic Health Record) Systems; 3.2. Departmental Systems; 3.2.1. Foundational Systems; 3.2.2. Data Repositories; 3.3. Interface Engines; 3.4. Networks, Hosts, Servers, ""Middleware,"" Workstations; 3.5. Best of Breed versus Suite from a Single Vendor 327 $a4. End-user applications: strengths/weaknesses of web and other development choices4.1. Application Delivery; 5. Examples of clinical computing architectures; References; Chapter 3: Creating and Supporting Interfaces; 1. Integrating and interfacing applications; 1.1. What Do We Mean by Integration?; 2. HL7 in the real-world; 2.1. Integration before HL7; 2.2. What HL7 Stands for; 2.3. HL7 Definition, History, and Evolution; 2.4. HL7 Communication Protocols; 3. What is needed to succeed with interface development; 3.1. Foundation; 3.2. Interface Engines; 3.3. Interface Development 327 $a3.3.1. Interface Development Methodology3.4 Why isnt Developing an HL7 Interface Easier?; 4. Other standards; 4.1. X12; 4.2. DICOM; 4.3. Application Level Standards; 4.4. Arden Syntax; 5. Data exchange and meaningful use; 6. Final thoughts regarding interfaces; References; Chapter 4: Infrastructure; 1. Introduction; 2. Data centers; 2.1. Electrical Power; 2.2. Power Distribution and Backup Power; 2.3. Cooling; 2.4. Data Center Reliability; 2.5. Environmental Protection and Data Center Security; 2.6. Data Center Management and Remote Data Centers; 2.7. Future of Data Centers 327 $a3. Servers, operating systems, and databases4. Managing the desktop and other clients; 4.1. Standardizing Desktop Configurations; 4.2. Patching, Updating, Cloning, and Inventory; 4.3. Life Cycle and Desktop Replacement; 4.4. Windows, Linux, and Mac OS Clients; 4.5. Virtual Desktops, Single Sign-on, and other Desktop Support Middleware; 5. Backup, redundancy, disaster planning, and recovery; 5.1. Reliability, Availability, and Redundancy; 5.2. Availability, Failures, and Backups; 5.3. Disasters, Disaster Recovery, and Business Continuity; 6. Operations; 6.1. Daily Operations 327 $a6.2. Infrastructure Support and other Related Activities 330 $aAlthough informatics trainees and practitioners who assume operational computing roles in their organization may have reasonably advanced understanding of theoretical informatics, many are unfamiliar with the practical topics - such as downtime procedures, interface engines, user support, JCAHO compliance, and budgets - which will become the mainstay of their working lives. Practical Guide to Clinical Computing Systems 2nd edition helps prepare these individuals for the electronic age of health care delivery. It is also designed for those who migrate into clinical computing operations roles 606 $aInformation storage and retrieval systems$xMedical care 606 $aHealth services administration$xData processing 615 0$aInformation storage and retrieval systems$xMedical care. 615 0$aHealth services administration$xData processing. 676 $a362.10285 702 $aPayne$b Thomas H. 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910809950403321 996 $aPractical guide to clinical computing systems$93916851 997 $aUNINA