DOCSLIB.ORG

IT Infrastructure Technical Framework Volume 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IT Infrastructure Technical Framework Volume 2 Integrating the Healthcare Enterprise 5 IT Infrastructure Technical Framework 10 Volume 2 (ITI TF-2) Transactions 15 Revision 5.0 – Final Text December 12, 2008 20 Copyright © 2008 IHE International IHE IT Infrastructure Technical Framework, vol. 2 (ITI TF-2): Transactions _________________________________________________________________________ ________ Contents 1 Introduction........................................................................................ ............................. ........ 4 25 1.1 Overview of the Technical Framework...................................... ............................. ........ 4 1.2 Overview of IT Infrastructure Technical Framework Volume II..................................... 5 1.3 Audience..................................................................................... ............................. ........ 5 1.4 Relationship to Standards........................................................... ............................ ......... 5 1.5 Relationship to Real-world Architectures .................................. ............................. ........ 6 30 1.6 Comments................................................................................... ............................. ........ 6 1.7 Copyright Permission ................................................................. ............................. ........ 7 2 Conventions ....................................................................................... ............................. ........ 8 2.1 The Generic IHE Transaction Model ......................................... ............................. ........ 8 2.2 HL7 Profiling Conventions ........................................................ ............................ ......... 9 35 2.3 Use of Coded Entities and Coding Schemes .............................. ............................. ........ 9 3 IHE Transactions ............................................................................... ............................. ...... 10 3.1 Maintain Time ............................................................................ ............................. ...... 11 3.2 Get User Authentication............................................................. ............................. ...... 13 3.3 Get Service Ticket ...................................................................... ............................. ...... 17 40 3.4 Kerberized Communication........................................................ ............................ ....... 20 3.5 Join Context................................................................................ ............................. ...... 24 3.6 Change Context .......................................................................... ............................. ...... 29 3.7 Leave Context............................................................................. ............................. ...... 35 3.8 Patient Identity Feed................................................................... ............................. ...... 38 45 3.9 PIX Query................................................................................... ............................. ...... 53 3.10 PIX Update Notification............................................................. ............................ ....... 64 3.11 Retrieve Specific Information for Display ................................. ............................. ...... 71 3.12 Retrieve Document for Display.................................................. ............................. ...... 81 3.13 Follow Context ........................................................................... ............................. ...... 86 50 3.14 Register Document Set............................................................... ............................. ...... 91 3.15 Provide and Register Document Set........................................... ............................. ...... 99 3.16 Query Registry............................................................................ ............................. .... 114 3.17 Retrieve Document..................................................................... ............................ ..... 138 3.18 Registry Stored Query ................................................................ ............................. .... 146 55 3.19 Authenticate Node...................................................................... ............................. .... 175 3.20 Record Audit Event .................................................................... ............................. .... 181 3.21 Patient Demographics Query...................................................... ............................. .... 192 3.22 Patient Demographics and Visit Query ........................................................................ 209 3.23 Find Personnel White Pages......................................................................................... 226 60 3.24 Query Personnel White Pages ...................................................................................... 229 3.25 Intentionally Left Blank ............................................................................................... 241 3.26 Intentionally Left Blank ............................................................................................... 241 3.27 Intentionally Left Blank ............................................................................................... 241 3.28 Intentionally Left Blank ............................................................................................... 241 65 3.29 Intentionally Left Blank ............................................................................................... 241 3.30 Patient Identity Management........................................................................................ 241 3.31 Patient Encounter Management.................................................................................... 265 3.32 Distribute Document Set on Media .............................................................................. 310 ______________________________________________________________________________ IHE_ITI_TF_5.0_Vol2_FT_2008-12-12.doc 2 Copyright © 2008 IHE International IHE IT Infrastructure Technical Framework, vol. 2 (ITI TF-2): Transactions _________________________________________________________________________ ________ 3.33 Intentionally Left Blank ............................................................. ............................. .... 318 70 3.34 Intentionally Left Blank ............................................................. ............................. .... 318 3.35 Intentionally Left Blank ............................................................. ............................. .... 318 3.36 Intentionally Left Blank ............................................................. ............................. .... 318 3.37 Intentionally Left Blank ............................................................. ............................. .... 318 3.38 Intentionally Left Blank ............................................................. ............................ ..... 318 75 3.39 Intentionally Left Blank ............................................................. ............................. .... 318 3.40 Provide X-User Assertion........................................................... ............................. .... 318 3.41 Provide and Register Document Set-b ....................................... ............................. .... 324 3.42 Register Document Set-b............................................................ ............................. .... 324 3.43 Retrieve Document Set............................................................... ............................. .... 324 80 4 Cross-Transaction Specifications ...................................................... ............................ ..... 326 4.1 XDS Metadata ............................................................................ ............................. .... 326 4.2 Character String Comparisons.................................................................................. .... 377 4.3 XDS Metadata Vocabulary......................................................... ............................. .... 377 5 IHE Content Specifications ............................................................... ............................. .... 380 85 5.1 Basic Patient Privacy Consents Module..................................... ............................. .... 380 5.2 Scanned Documents Content Module ........................................ ............................ ..... 384 Appendix A: Web Service Definition for Retrieve Specific Informat i on for Display and Retrieve Document for Display Transaction.................................................... ............................. .... 400 Appendix B: Definition of Document Unique Ids ............................. ............................. .... 405 90 Appendix C: HL7 Profiling Conventions........................................... ............................. .... 408 Appendix D: Cross-Profile Interactions of PIX and PSA .................. ............................. .... 417 Appendix E: Usage of the CX Data Type in PID-3-Patient Identifie r List.......................... 420 Appendix F: Intentionally Left Blank................................................ ............................
Load more

Recommended publications
  • SIMS 4.0 Reference Manual
    Sun Internet Mail Server™ 4.0 Reference Manual A Sun Microsystems, Inc. Business 901 San Antonio Road Palo Alto, CA 94303 USA 650 960-1300 fax 650 969-9131 Part No.: 805-7677-10 Revision A, July 1999 Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 U.S.A. All rights reserved. Copyright 1992-1996 Regents of the University of Michigan. All Rights Reserved. Redistribution and use in source and binary forms are permitted provided that this notice is preserved and that due credit is given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from this software or documentation without specific prior written permission. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Solaris, Sun Internet Mail Server, HotJava, Java, Sun Workstation, OpenWindows, SunExpress, SunDocs, Sun Webserver are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the United States and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • ® Common Abbreviations
    ® Common Abbreviations AA auto-answer AAL A TM adaptation layer AAN autonomously attached network ABM asynchronous balanced mode AbMAN Aberdeen MAN ABNF augmented BNF AC access control ACAP application configuration access protocol ACK acknowledge ACL access control list ADC analogue-to-digital converter ADPCM adaptive delta pulse code modulation AES audio engineering society AFI authority and format identifier AGENTX agent extensibility protocol AGP accelerated graphics port AM amplitude modulation AMI alternative mark inversion ANSI American National Standard Institute APCM adaptive pulse code modulation API application program interface ARM asynchronous response mode ARP address resolution protocol ASCII American standard code for information exchange ASK amplitude-shift keying AT attention ATM asynchronous transfer mode AUI attachment unit interface BCC blind carbon copy BCD binary coded decimal BGP border gateway protocol BIOS basic input/output system B-ISDN broadband ISDN BMP bitmapped BNC British Naval Connector BaM beginning of message BOOTP bootstrap protocol BPDU bridge protocol data units bps bits per second BVCP Banyan Vines control protocol CAD computer-aided design 403 CAN concentrated area network CASE common applications service elements CATNIP common architecture for the Internet CC carbon copy CCITT International Telegraph and Telephone Consultative CD carrier detect CD compact disk CDE common desktop environment CDFS CD file system CD-R CD-recordable CD-ROM compact disk - read-only memory CF control field CGI common
    [Show full text]
  • Network Working Group M. Wahl Request for Comments: 2252 Critical Angle Inc. Category: Standards Track A. Coulbeck Isode Inc
    Network Working Group M. Wahl Request for Comments: 2252 Critical Angle Inc. Category: Standards Track A. Coulbeck Isode Inc. T. Howes Netscape Communications Corp. S. Kille Isode Limited December 1997 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions 1. Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1997). All Rights Reserved. IESG Note This document describes a directory access protocol that provides both read and update access. Update access requires secure authentication, but this document does not mandate implementation of any satisfactory authentication mechanisms. In accordance with RFC 2026, section 4.4.1, this specification is being approved by IESG as a Proposed Standard despite this limitation, for the following reasons: a. to encourage implementation and interoperability testing of these protocols (with or without update access) before they are deployed, and b. to encourage deployment and use of these protocols in read-only applications. (e.g. applications where LDAPv3 is used as a query language for directories which are updated by some secure mechanism other than LDAP), and Wahl, et. al. Standards Track [Page 1] RFC 2252 LADPv3 Attributes December 1997 c. to avoid delaying the advancement and deployment of other Internet standards-track protocols which require the ability to query, but not update, LDAPv3 directory servers. Readers are hereby warned that until mandatory authentication mechanisms are standardized, clients and servers written according to this specification which make use of update functionality are UNLIKELY TO INTEROPERATE, or MAY INTEROPERATE ONLY IF AUTHENTICATION IS REDUCED TO AN UNACCEPTABLY WEAK LEVEL.
    [Show full text]
  • Model MTA128ST-USB External ISDN Terminal Adapter User Guide
    Model MTA128ST-USB External ISDN Terminal Adapter User Guide User Guide Model MTA128ST-USB S000337A Revision A Copyright ©2004, by Multi-Tech Systems, Inc. All rights reserved. This publication may not be reproduced, in whole or in part, without prior expressed written permission from Multi-Tech Systems, Inc. Multi-Tech Systems, Inc. makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Multi-Tech Systems, Inc. reserves the right to revise this publication and to make changes in the content hereof without obligation of Multi-Tech Systems, Inc. to notify any person or organization of such revisions or changes. Record of Revisions Revision Date Description A 4/15/04 This manual replaces printed manual 88311704 Rev E. Trademarks MultiModemISDN, Multi-Tech, and the Multi-Tech logo are trademarks of Multi-Tech Systems, Inc. AT&T and 5ESS are registered trademarks of American Telephone and Telegraph. Microsoft, Windows, Windows 2000, Windows 98, and Windows 95 are registered trademarks of Microsoft Corporation. NETCOM is a registered trademark of NETCOM On-Line Communication Services, Inc. Netscape and Navigator are trademarks of Netscape Communications Corp. DMS-100 is a trademark of Northern Telecom. All other trademarks are owned by their respective companies. Multi-Tech Systems, Inc. 2205 Woodale Drive Mounds View, MN 55112 U.S.A (763) 785-3500 or (800) 328-9717 Fax (763) 785-9874 Technical Support (800) 972-2439 Internet Address http://www.multitech.com Contents Chapter 1 - Introduction and Description Introduction ................................................................................................................................................. 6 Product Description ...................................................................................................................................
    [Show full text]