Linked e-resources
Details
Table of Contents
Foreword; Preface; Trademarks and Disclaimer; Copy-Editor; Contributors; Reviewers; HL7 Conformance Working Group; Robert Snelick Acknowledgments; Frank Oemig Acknowledgments; Dedication; Contents; About the Authors; Acronyms; List of Figures; List of Tables; Healthcare Information Technology; 1 Introduction; 1.1 The Case for Common Understanding; 1.1.1 The Need for Consistency; 1.2 Information Cycle; 1.3 Motivation for Cooperation; 1.4 Definition of Key Terms and Concepts; 1.4.1 Conformance; 1.4.2 Interoperability; 1.5 Interoperability Levels; 1.6 Standards Development Life-Cycle
1.7 ISO/OSI Stack1.8 Reference Model for Open Distributed Processing (RM-ODP); 1.9 Concept Relationships; 1.10 Approaches to Standards Development; 1.11 Testing; 1.12 Scope and Purpose; 1.13 Commonly Used Terms and Definitions; 1.14 Intended Audience; 1.15 Keywords for Use; 1.16 Summary; References; 2 Architecture; 2.1 Interface; 2.1.1 Types of Interfaces; 2.1.1.1 Functional (Local + Remote); 2.1.1.2 Message-Based Data Exchange; 2.1.1.3 Document Exchange; 2.1.2 Communication Paradigms; 2.1.3 Protocol Layer; 2.1.4 Levels for Interoperability; 2.2 Interfacing; 2.2.1 Impact on Interfaces
2.3 Serving Interfaces with Data2.3.1 General "Capability" of a System; 2.3.2 Relevance for Interfaces; 2.4 Dynamic Behavior; 2.4.1 Message Pairs; 2.4.2 Timing; 2.4.3 Message Identification; 2.4.4 Routing to Multiple Destinations; 2.4.5 Responsibility of a System; 2.4.6 Event Handling; 2.4.7 Delayed Message Handling (Sender); 2.4.8 Handling of Outdated Data (Receiver); 2.5 Intermediate Message Handling; 2.6 Message Population; 2.7 Information Transmission; 2.8 Delete Indication; 2.8.1 Legal Requirements for Data Persistence; 2.8.2 Receiver Responsibility; 2.8.3 Data Granularity
2.8.4 Impact of Order of Messages2.8.5 Sender Responsibility: Impact to System Design; 2.9 Null Flavors; 2.10 Snapshot Mode Versus Update Mode; 2.11 Considerations in Application Development; 2.11.1 Introducing Functional Requirements; 2.11.2 Conformance Discussion; 2.12 Summary; References; 3 Healthcare Standards Landscape; 3.1 Introduction; 3.2 Standards Developing Organizations; 3.2.1 UNECE; 3.2.2 ASC (US); 3.2.3 ASTM (US); 3.2.4 HL7; 3.2.4.1 Affiliates; 3.2.5 DICOM; 3.2.6 KBV, ZI and QMS (Germany); 3.2.7 KV-Telematik (Germany); 3.2.8 NCPDP (USA); 3.2.9 OASIS
3.3 Profile Development Organizations3.3.1 IHE; 3.3.2 ELGA (Austria); 3.3.3 eHealth Suisse (Switzerland); 3.3.4 HITSP (US); 3.3.5 S&I Framework (US); 3.3.6 Standards Collaborative (Canada); 3.3.7 Interop'Santé (France); 3.3.8 ASIP Santé (France); 3.3.9 Phast (France); 3.3.10 eSanté (Luxembourg); 3.3.11 Interoperability Forum (Germany); 3.3.12 NHS (UK); 3.3.13 SMART Health IT on FHIR® (US); 3.3.13.1 Profiles; 3.4 Overview of Widely Used Standards; 3.4.1 HL7; 3.4.1.1 Version 2.x and 3.0; 3.4.1.2 CDA; 3.4.1.3 CCOW; 3.4.1.4 FHIR; 3.4.1.5 More HL7 Family Members; 3.4.2 Other Standards; 3.5 Summary
1.7 ISO/OSI Stack1.8 Reference Model for Open Distributed Processing (RM-ODP); 1.9 Concept Relationships; 1.10 Approaches to Standards Development; 1.11 Testing; 1.12 Scope and Purpose; 1.13 Commonly Used Terms and Definitions; 1.14 Intended Audience; 1.15 Keywords for Use; 1.16 Summary; References; 2 Architecture; 2.1 Interface; 2.1.1 Types of Interfaces; 2.1.1.1 Functional (Local + Remote); 2.1.1.2 Message-Based Data Exchange; 2.1.1.3 Document Exchange; 2.1.2 Communication Paradigms; 2.1.3 Protocol Layer; 2.1.4 Levels for Interoperability; 2.2 Interfacing; 2.2.1 Impact on Interfaces
2.3 Serving Interfaces with Data2.3.1 General "Capability" of a System; 2.3.2 Relevance for Interfaces; 2.4 Dynamic Behavior; 2.4.1 Message Pairs; 2.4.2 Timing; 2.4.3 Message Identification; 2.4.4 Routing to Multiple Destinations; 2.4.5 Responsibility of a System; 2.4.6 Event Handling; 2.4.7 Delayed Message Handling (Sender); 2.4.8 Handling of Outdated Data (Receiver); 2.5 Intermediate Message Handling; 2.6 Message Population; 2.7 Information Transmission; 2.8 Delete Indication; 2.8.1 Legal Requirements for Data Persistence; 2.8.2 Receiver Responsibility; 2.8.3 Data Granularity
2.8.4 Impact of Order of Messages2.8.5 Sender Responsibility: Impact to System Design; 2.9 Null Flavors; 2.10 Snapshot Mode Versus Update Mode; 2.11 Considerations in Application Development; 2.11.1 Introducing Functional Requirements; 2.11.2 Conformance Discussion; 2.12 Summary; References; 3 Healthcare Standards Landscape; 3.1 Introduction; 3.2 Standards Developing Organizations; 3.2.1 UNECE; 3.2.2 ASC (US); 3.2.3 ASTM (US); 3.2.4 HL7; 3.2.4.1 Affiliates; 3.2.5 DICOM; 3.2.6 KBV, ZI and QMS (Germany); 3.2.7 KV-Telematik (Germany); 3.2.8 NCPDP (USA); 3.2.9 OASIS
3.3 Profile Development Organizations3.3.1 IHE; 3.3.2 ELGA (Austria); 3.3.3 eHealth Suisse (Switzerland); 3.3.4 HITSP (US); 3.3.5 S&I Framework (US); 3.3.6 Standards Collaborative (Canada); 3.3.7 Interop'Santé (France); 3.3.8 ASIP Santé (France); 3.3.9 Phast (France); 3.3.10 eSanté (Luxembourg); 3.3.11 Interoperability Forum (Germany); 3.3.12 NHS (UK); 3.3.13 SMART Health IT on FHIR® (US); 3.3.13.1 Profiles; 3.4 Overview of Widely Used Standards; 3.4.1 HL7; 3.4.1.1 Version 2.x and 3.0; 3.4.1.2 CDA; 3.4.1.3 CCOW; 3.4.1.4 FHIR; 3.4.1.5 More HL7 Family Members; 3.4.2 Other Standards; 3.5 Summary