yansandiego的专栏

Meaningful use is the focus of this book. This book is the first candid attempt to bridge the gap between clinicians and IT staff. Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Health IT and Medical Science 3 Meaningful Use and What It Means to Be an EHR 4 Why So Late? 5 Health IT in Health Reform 7 Evolution of Meaningful Use 7 Accountable Care Organizations 8 EHR Functionality in Context 10 2. An Anatomy of Medical Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 How Patients Reach Healthcare Organizations 14 Lab Sample Collection Before a Visit or Admission Date 17 HIPAA and Patient Identification 17 Intake, Demographics, Visits, and Admissions 20 Precertification and Prior Authorization 21 Emergency Admissions 21 Prioritization and Triage 23 Outpatient Care 24 Inpatient Care 25 Labs 27 Imaging 27 Administration and Billing 28 3. Medical Billing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Who Pays, and How 32 Claims 32 Eligibility 33 Treatment 35 Billing 37 iii The Billing Process 38 Complexities in Billing 39 Adjudication 40 The Patient’s Burden 42 4. The Bandwidth of Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Workflow Tokens 47 Why Leave Paper? 48 Step 0: Health IT Humility 49 Normalized Data 52 Good Boundaries Mean Good Data 53 Data at Peace with Itself: Linked Data 55 Flexible Data 56 Assume Health Data Changes 57 Free Text Data 57 5. Herding Cats: Healthcare Management and Business Office Operations . . . . . . . . . 61 Major Business Office Activities 63 Insurance 63 Records 64 Demographics 64 Revenue Collection 65 Auditing 65 Accounting 66 Reporting 66 Licensing, Credentials, and Enrollments 67 Nonhealthcare Interactions 68 The Evolution of the Business Office 68 6. Patient-Facing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 The PHR as Platform 71 Sharing Data in Patient-Facing Software 75 Patients Using Normal Social Media 75 E-patients 77 The Quantified Self 78 Patient-Focused Social Media 80 Patient Privacy in PHR Systems 81 Specific PHR and Patient-Directed Meaningful Use Requirements 83 7. Human Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 The Extent of Error 85 Dangerous Dosing 87 Discontents of Computerization 90 iv | Table of Contents Process Errors and Organizational Change 92 Deep Medical Errors and EHR Solutions 94 Errors Caused by Human-Computer Mismatch 95 Best Practices 96 8. Meaningful Use Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Outpatient Guidelines and Requirements 100 Inpatient Guidelines and Requirements 116 9. A Selective History of EHR Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 MUMPS: The Programming Language for Healthcare 129 Where Can We Buy Some Light Bulbs? 130 Fragmentation 131 In an Environment with Gag Clauses and No Consumer Reports 131 VistA History 132 10. Ontologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 A Throw-Away Ontology 136 Learning from Our Example 138 CPT Codes, Sermo, and CMS 141 International Classification of Diseases (ICD) 144 E-patient-Dave-gate 145 Crosswalks and ICD Versions 147 Other Claims Codes 149 Drug Databases 149 SNOMED to the Rescue 154 SNOMED Example 155 SNOMED and the Semantic Web 157 UMLS: The Universal Mapping Metaontology 158 Extending Ontologies 159 Other Ontologies 160 Sneaky Ontologies 161 Ontologies Using APIs 162 Exercising Ontologies 162 11. Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Some Lessons from Earlier Exchanges 166 The New HIE Rules 168 Strong Standards 168 Winning Protocols 171 The Billing Protocols 171 HL7 Version 2 173 First-Generation and Second-Generation HIEs 182 Table of Contents | v Continuity of Care Record 182 HL7 v3, RIM, CDA, CDD, and HITSP C32 185 The IHE Protocol 189 HIE with IHE 191 Managing Patient Identifiers with IHE 192 IHE Data Exchange, the Library Model 193 IHE in the NWHIN 194 The Direct Project/Protocol 196 The PCAST Report 198 The SMART Platform 199 Technology and Policy Were Sitting in the Tree 199 12. HIPAA: The Far-Reaching Healthcare Regulation . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Does HIPAA Cover Me? 205 Responsibilities of Covered Entities 206 HIPAA: A Reasonable Regulation 213 Duct-Tape HIPAA Strategies 214 Breach Notification Rules 215 In Summary 217 13. Open Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Why Open Source? 220 Major Open Source Healthcare Projects 221 ClearHealth 222 Mirth Connect 223 VistA Variants and Other Certified Open Source EHR Systems 223 OpenMRS 224 Appendix: Meaningful Use Implementation Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . 227 vi | Table of Conten

Machine Leaning by Peter Flach. Cambridge University Press.

Large Scale C++ Software Design.

advanced linux programming advanced linux programming advanced linux programming

Write Great Code- thinking low-level & writing High-Level, the best practice in programming.

The C++ inventor's book. Latest version 4.

Further Thoughts on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity

Within an ever-changing society, marketing represents the ongoing effort to keep the means of production—our products and services—in touch with evolving social and perso

This book is not about the failure of simply any company, but of good companies—the kinds that many managers have admired and tried to emulate, the companies known for their abilities to innovate and execute.

This material is presented in a carefully chosen sequence, much as though a tutor were sitting next to you, guiding you along. Many authors treat this material in a “systematic” fashion, which makes sense from a writer’s perspective but can be very confusing to new users. Another goal is to acquaint you with the Unix way of thinking, which is different from the Windows way of thinking.

Relationship Skills; Personal Skills; Business Skills;

Exit abort return 三者区别

 To understand the distinction between hardware and software.  To recognize that problem solving is an essential component of computer science.  To understand the meaning of the term algorithm.  To appreciate the role of the compiler as a translator between a higher-level programming language and the lower-level machine language.  To recognize the principal types of programming errors.  To appreciate the importance of software maintenance and the use of good software engineering practice.

Publisher : Addison Wesley Pub Date : April 21, 2003 Context: A C++ templates primer  Workable coding guidelines and extensive coding examples  Quick lists of need-to-know information about Exceptions, Assertions, and Standard Template Library components  A technique for effectively using prototypes to move your design from an initial concept to a robust solution  A technique for building debugging support into your software without a ton of overhead  Thirteen specific techniques to improve the overall performance of your software

"Code is a book about how computers work." Copyright © 2009

The intended audience of this book falls into two main categories. The first category is that of experienced C++ programmers who want to master the most modern library writing techniques. The second category consists of busy programmers who need to get the job done without undergoing a steep learning investment.

If any evolving operating system is a moving target, Linux is a rabid cheetah. Progress is measured in days, not years, and frequent releases of the kernel and other components constantly morph the playing field. No book can hope to capture such a dynamic beast in a timeless fashion. Nonetheless, the programming environment defined by system programming is set in stone.... Contents of This Book This book is broken into 10 chapters, an appendix, and a bibliography. Chapter 1, Introduction and Essential Concepts This chapter serves as an introduction, providing an overview of Linux, system programming, the kernel, the C library, and the C compiler. Even advanced users should visit this chapter—trust me. Chapter 2, File I/O This chapter introduces files, the most important abstraction in the Unix environment, and file I/O, the basis of the Linux programming mode. This chapter covers reading from and writing to files, along with other basic file I/O operations. The chapter culminates with a discussion on how the Linux kernel implements and manages files. Chapter 3, Buffered I/O This chapter discusses an issue with the basic file I/O interfaces—buffer size management—and introduces buffered I/O in general, and standard I/O in particular, as solutions. Chapter 4, Advanced File I/O This chapter completes the I/O troika with a treatment on advanced I/O interfaces, memory mappings, and optimization techniques. The chapter is capped with a discussion on avoiding seeks, and the role of the Linux kernel’s I/O scheduler Chapter 5, Process Management This chapter introduces Unix’s second most important abstraction, the process, and the family of system calls for basic process management, including the venerable fork. Chapter 6, Advanced Process Management This chapter continues the treatment with a discussion of advanced process management, including real-time processes. Chapter 7, File and Directory Management This chapter discusses creating, moving, copying, deleting, and otherwise managing files and directories. Chapter 8, Memory Management This chapter covers memory management. It begins by introducing Unix concepts of memory, such as the process address space and the page, and continues with a discussion of the interfaces for obtaining memory from and returning memory to the kernel. The chapter concludes with a treatment on advanced memory-related interfaces. Chapter 9, Signals This chapter covers signals. It begins with a discussion of signals and their role on a Unix system. It then covers signal interfaces, starting with the basic, and concluding with the advanced. Chapter 10, Time This chapter discusses time, sleeping, and clock management. It covers the basic interfaces up through POSIX clocks and high-resolution timers. Appendix, GCC Extensions to the C Language The Appendix reviews many of the optimizations provided by gcc and GNUC, such as attributes for marking a function constant, pure, and inline. The book concludes with a bibliography of recommended reading, listing both useful supplements to this work, and books that address prerequisite topics not covered herein.

Software Architecture Bootcamp is your hands-on "field manual" for becoming a great software architect! This hands-on "field manual" gives developers the essential skills they need to survive and thrive as software architects! You’ll find insightful, real-world coverage of everything from design patterns to prototyping, business case development to leadership. Leading software architects Raphael Malveau and Thomas Mowbray share profound insights and practical solutions for all the key challenges of architectures using objects, components, and distributed Internet computing, showing how to avoid time-consuming pitfalls and costly errors. You’ll master proven methods for: Identifying the best architectural model for any project Executing heavyweight or lightweight approaches to software architecture Addressing scalability and long-term business flexibility Making the most of abstraction, refactoring, and architectural prototyping Leveraging superior design patterns to improve your implementations With hands-on exercises, real-life war stories, and a takeno- prisoners attitude, Software Architect Bootcamp won’t just help you become a great software architect: it’ll help you become a true technical leader of your organization.

Very clear and concise description of Linux and Univ Shell commands.

What Is the C++ Object Model? There are two aspects to the C++ Object Model: 1. The direct support for object-oriented programming provided within the language 2. The underlying mechanisms by which this support is implemented.

What Is the C++ Object Model? There are two aspects to the C++ Object Model: 1. The direct support for object-oriented programming provided within the language 2. The underlying mechanisms by which this support is implemented. Tip: You will ace any C++ interview should you study this book and have no trouble to understand most of what is been talking about.

图解概念,帮助理解. 英文语言流畅易懂. 不可多得构架辅助读物. 对提高硬件理解和专业英语水平都有帮助. 坚持读完!

“四人帮”的书。 英文的。 Design Patterns Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides Addison-Wesley Pub Co; 1st edition (January 15, 1995)