Imaging Reports Using HL7​ Clinical Document Architecture​ Page 2​

Total Page:16

File Type:pdf, Size:1020Kb

Imaging Reports Using HL7​ Clinical Document Architecture​ Page 2​ PS3.20​ DICOM PS3.20 2021d - Imaging Reports using HL7​ Clinical Document Architecture​ Page 2​ PS3.20: DICOM PS3.20 2021d - Imaging Reports using HL7 Clinical Document​ Architecture​ Copyright © 2021 NEMA​ A DICOM® publication​ - Standard -​ DICOM PS3.20 2021d - Imaging Reports using HL7 Clinical Document Architecture​ Page 3​ Table of Contents​ Notice and Disclaimer ........................................................................................................................................... 13​ Foreword ............................................................................................................................................................ 15​ 1. Scope and Field of Application ............................................................................................................................. 17​ 2. Normative and Informative References .................................................................................................................. 19​ 3. Definitions ....................................................................................................................................................... 21​ 4. Symbols and Abbreviations ................................................................................................................................. 23​ 5. Conventions ..................................................................................................................................................... 25​ 5.1. Template Metadata ..................................................................................................................................... 25​ 5.1.1. Template IDs and Version ...................................................................................................................... 25​ 5.1.2. Context .............................................................................................................................................. 25​ 5.1.3. Open and Closed Templates .................................................................................................................. 25​ 5.2. Template Table Structure ............................................................................................................................. 25​ 5.2.1. Business Name ................................................................................................................................... 26​ 5.2.1.1. Multiple Instantiations ..................................................................................................................... 27​ 5.2.1.2. Implicit Element Structure For Business Name .................................................................................... 27​ 5.2.2. Nesting Level ...................................................................................................................................... 27​ 5.2.3. Element/Attribute Names and XPath Notation ............................................................................................ 27​ 5.2.4. Cardinality .......................................................................................................................................... 28​ 5.2.5. Element/Attribute Conformance .............................................................................................................. 29​ 5.2.6. Data Type .......................................................................................................................................... 29​ 5.2.7. Value Conformance .............................................................................................................................. 29​ 5.2.8. Value Specification ............................................................................................................................... 29​ 5.2.8.1. Coded Simple Value ...................................................................................................................... 30​ 5.2.8.2. Concept Descriptor and Coded With Equivalents ................................................................................. 30​ 5.2.8.3. Value Set ..................................................................................................................................... 30​ 5.2.8.4. Concept Domains .......................................................................................................................... 30​ 5.2.8.5. Mapping From DICOM SOP Instances and HL7v2 Messages ................................................................. 30​ 5.2.9. Subsidiary Templates ........................................................................................................................... 31​ 5.2.9.1. Vocabulary Binding and Constraints .................................................................................................. 31​ 5.2.10. Additional Requirements ...................................................................................................................... 31​ 5.3. Encoding .................................................................................................................................................. 31​ 5.3.1. Translation Code Element ...................................................................................................................... 32​ 5.3.2. Null Flavor .......................................................................................................................................... 32​ 5.3.3. Unknown Information ............................................................................................................................ 33​ 5.3.4. XML ID .............................................................................................................................................. 34​ 5.4. Extension and Namespace ........................................................................................................................... 35​ 5.5. Serialization Order of Elements ..................................................................................................................... 35​ 6. Conformance ................................................................................................................................................... 37​ 7. Document-level Templates .................................................................................................................................. 39​ 7.1. Imaging Report .......................................................................................................................................... 39​ 7.1.1. clinicalDocument/code .......................................................................................................................... 40​ 7.1.2. Addendum .......................................................................................................................................... 41​ 7.2. Imaging Addendum Report ........................................................................................................................... 41​ 8. Header Content Templates ................................................................................................................................. 43​ 8.1. General Header ......................................................................................................................................... 43​ 8.1.1. templateId - contentTemplate ................................................................................................................. 45​ 8.1.2. title .................................................................................................................................................... 45​ 8.1.3. effectiveTime ...................................................................................................................................... 46​ 8.1.4. setID and versionNumber ...................................................................................................................... 46​ 8.1.5. recordTarget/patientRole ....................................................................................................................... 46​ 8.1.6. legalAuthenticator ................................................................................................................................ 46​ 8.1.7. recordTarget/patientRole/Patient/birthTime ................................................................................................ 47​ 8.1.8. author/assignedAuthor .......................................................................................................................... 48​ 8.1.9. InformationRecipient/intendedRecipient .................................................................................................... 49​ 8.2. Imaging Header ......................................................................................................................................... 49​ 8.2.1. componentOf/encompassingEncounter .................................................................................................... 52​ 8.2.2. Physician of Record Participant ............................................................................................................... 53​ - Standard -​ Page 4​ DICOM PS3.20 2021d - Imaging Reports using HL7 Clinical Document Architecture​ 8.2.3. inFulfillmentOf/Order and @ID ................................................................................................................ 53​ 8.2.4. documentationOf/serviceEvent
Recommended publications
  • Technology and Standards for Health Care
    Technology and Standards for Health Care Messaging Standards Used for: HL7 Clinical data X12N Financial data, HIPAA mandated transactions DICOM Images NCPDP Prescription from providers to pharmacies IEEE Bedside instruments, medical information bus Terminology Standards LOINC Drugs NLM/FDA/VA collaboration on RxNorm, NDF-RT Billing CPT, ICD-9CM Clinical UMLS, SNOMED and others Table adopted from Stan Huff MD, HIMSS, 2003 Standards and Standards Organizations American Society for Testing and Materials (ASTM) A component of the American National Standards Institute (ANSI) that has a subcommittee (E31) for general healthcare informatics. This E31 Subcommittee on Healthcare Informatics develops standards related to the architecture, content, storage, security, confidentiality, functionality, and communication of information used within healthcare and healthcare decision making, including patient-specific information and knowledge. URL: www.astm.org Current Procedural Terminology (CPT) CPT® Current Procedural Terminology was developed by the American Medical Association in 1966. These codes are used for the billing of medical procedures. Each year, an annual publication is prepared, that makes changes corresponding with significant updates in medical technology and practice. The most recent version of CPT, CPT 2003, contains 8,107 codes and descriptors. URL: http://www.ama-assn.org/ama/pub/category/3113.html Digital Imaging and Communications in Medicine (DICOM) The Digital Imaging and Communications in Medicine (DICOM) Standard was developed for the transmission of images and is used internationally for Picture Archiving and Communication Systems (PACS). This standard was developed by the joint committee of the ACR (the American College of Radiology) and NEMA (the National Electrical Manufacturers Association) to meet the needs of manufacturers and users of medical imaging equipment for interconnection of devices on standard networks.
    [Show full text]
  • Microsoft Amalga the Unified Intelligence System
    m Microsoft Amalga the Unified Intelligence System > Turn information into health intelligence and critical knowledge PG 02 MICROSOFT AMALGA MICROSOFT AMALGA PG 03 Our vision: For more than a decade, Microsoft has invested significant time and resources into understanding the needs of healthcare organizations. We are developing solutions that To improve health encompass both the provider and the consumer to help you achieve your goals from better patient care to improving the financial health of your organization. We believe around the world the issues that Microsoft is best positioned to address focus on healthcare information management—getting the right data in front of the right people in the right way at the right time. That’s why we’re working to speed and improve the capture, manipulation, aggregation, and presentation of healthcare data by offering a family of integrated IT systems for the healthcare enterprise. The Microsoft® Amalga™ Family of Enterprise Health Systems is built on Microsoft technology, offering a comprehensive range of solutions to meet the needs of your health enterprise. Microsoft Amalga Microsoft Amalga, the new version of the product formerly known as Azyxxi, is the Unified Intelligence System that allows hospital enterprises to unlock the power of all their data sitting in clinical, financial, and administrative silos. Without replacing current systems, Amalga offers leading-edge institutions an innovative way to capture, consoli- date, store, access, and quickly present data in meaningful ways. Microsoft Amalga Hospital Information System Microsoft Amalga Hospital Information System (HIS), the new version of Hospital 2000, is a state-of-the-art, integrated hospital information system designed to meet the needs of developing and emerging markets.
    [Show full text]
  • Introduction to Health Level Seven (HL7) International Organization & Process Orientation
    Introduction to Health Level Seven (HL7) International Organization & Process Orientation January 2018 HL7 Working Group Meeting New Orleans, LA January 2018 Calvin Beebe © 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Agenda HL7 International ➢ What is it ➢ How is it Organized ➢ Vision and Mission ➢ Organizational Chart ➢ Affiliates ➢ Role in enabling interoperability ➢ What’s in a name? © 2015 Health Level Seven ® International. All Rights Reserved. 2 HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Agenda How do we work? ➢ Consensus Driven ➢ Work Groups ➢ Technical Steering Committee ➢ Steering Divisions HL7 International Processes ➢ Meetings ➢ Projects ➢ Ballots HL7 Products Appendices © 2015 Health Level Seven ® International. All Rights Reserved. 3 HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. HL7 INTERNATIONAL WHAT IS IT & HOW IT IS ORGANIZED? © 2015 Health Level Seven ® International. All Rights Reserved. 4 HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. What is HL7 International? HL7 International is one of several American National Standards Institute (ANSI) accredited Standards Developing Organizations (SDOs) operating in the healthcare arena. ➢ Most of these SDOs produce standards (sometimes called specifications or protocols) for a particular healthcare domain such as pharmacy, medical devices, imaging or insurance (claims processing) transactions. © 2015 Health Level Seven ® International. All Rights Reserved. 5 HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
    [Show full text]
  • Health Level 7 (HL7) Adapter
    Health Level 7 (HL7) Adapter Edifecs SpecBuilder and XEngine Accelerate the Design, Development, Validation and Integration of HL7 Messages Background on HL7 Messages Edifecs HL7 Highlights Healthcare providers are facing a daunting challenge: to provide the best clinical patient care while reducing Supports HL7 versions: 2.1, 2.2, 2.3, costs. Adoption of HL7 message protocols provides 2.3.1, 2.4, 2.x and 3.x (XML based) a valuable resource in overcoming these challenges. HL7 is an ANSI-accredited standards organization that Produces CCD and CDA, including publishes specifications for the electronic exchange of schematron validation administrative, clinical, and financial information among independent healthcareoriented systems. This approach Validates against HL7 message enables provider healthcare organizations to select and specifications and custom rules integrate best-of-breed systems for patient care, clinical lab, etc. However, implementation of HL7 is not plug-n- Creates automatic acknowledgements play because each organization and department has its own specific business needs. These needs translate into Supports full envelope and batching custom requirements that must be properly documented, communicated and applied to the various systems in order Converts to and from HL7 2.x XML to function properly. Edifecs products include HL7 support format to provide an easy way to capture, document and maintain these requirements and ensure that messages comply Exports HL7 message specifications with these requirements. to W3C XML Schema format SB Solution Brief | Health Level 7 (HL7) Adapter 1 Comprehensive HL7 standards support with seamless, Comprehensive Standards Support fast integration The Edifecs HL7 solution offers comprehensive standards support, a powerful editor with compliance checking and easy, seamless integration through a COM, Java API, or standalone server (includes connectors to IBM Websphere MQ, Java messaging server (JMS) or folder).
    [Show full text]
  • Session 100: Beyond Claims: Unlocking the Power of EMR And
    Session 100, Beyond Claims: Unlocking the Power of EMR and Real-Time Clinical ADT Data SOA Antitrust Disclaimer SOA Presentation Disclaimer 2019 Health Meeting ANDREW LOEWER, KELVIN WURSTEN, & KATHERINE ZHAO Session 100: Beyond Claims: Unlocking the Power of EMR and Real-Time Clinical ADT Data June 25, 2019 SOCIETY OF ACTUARIES Antitrust Compliance Guidelines Active participation in the Society of Actuaries is an important aspect of membership. While the positive contributions of professional societies and associations are well-recognized and encouraged, association activities are vulnerable to close antitrust scrutiny. By their very nature, associations bring together industry competitors and other market participants. The United States antitrust laws aim to protect consumers by preserving the free economy and prohibiting anti-competitive business practices; they promote competition. There are both state and federal antitrust laws, although state antitrust laws closely follow federal law. The Sherman Act, is the primary U.S. antitrust law pertaining to association activities. The Sherman Act prohibits every contract, combination or conspiracy that places an unreasonable restraint on trade. There are, however, some activities that are illegal under all circumstances, such as price fixing, market allocation and collusive bidding. There is no safe harbor under the antitrust law for professional association activities. Therefore, association meeting participants should refrain from discussing any activity that could potentially be construed as having an anti-competitive effect. Discussions relating to product or service pricing, market allocations, membership restrictions, product standardization or other conditions on trade could arguably be perceived as a restraint on trade and may expose the SOA and its members to antitrust enforcement procedures.
    [Show full text]
  • Using LOINC with SNOMED CT 3 April 2017
    Using LOINC with SNOMED CT 3 April 2017 Latest web browsable version: http://snomed.org/loinc SNOMED CT Document Library: http://snomed.org/doc 1. Using LOINC with SNOMED CT . 3 1 Introduction . 4 2 Short Introduction to SNOMED CT . 6 2.1 Features of SNOMED CT . 6 2.2 Benefits of SNOMED CT . 7 3 Short Introduction to LOINC . 9 3.1 Features of LOINC . 9 3.2 Benefits of LOINC . 13 4 Cooperative Work . 15 4.1 Cooperative Work Overview . 15 4.2 Release File Specifications . 16 4.2.1 LOINC Part map reference set . 16 4.2.2 LOINC Term to Expression Reference Set . 18 4.3 Benefits of Products of the Cooperative Work . 21 5 Guidance on Use of SNOMED CT and LOINC Together . 22 5.1 Use of SNOMED CT and/or LOINC in . 22 5.2 Practical Guidance on Uses of SNOMED CT and LOINC . 23 5.2.1 Guideline A - Vital Signs (Observation Names and Values) . 23 5.2.2 Guideline B - Laboratory Orders . 24 5.2.3 Guideline C - Laboratory Test Results (Observation Names and Values) . 26 5.2.4 Guideline D - Specimens . 30 5.2.5 Guideline E - Animal Species and Breeds . 32 5.2.6 Guideline F - Procedures (Laboratory Methods) . 33 5.2.7 Practical Uses of Part Maps and Expression Associations . 34 5.2 Terminology Scenarios - Summary . 40 6 References . 40 Using LOINC with SNOMED CT (3 April 2017) Using LOINC with SNOMED CT The Guide to Use of SNOMED CT and LOINC together provides advice on combined use of SNOMED CT and LOINC.
    [Show full text]
  • Managing Non-DICOM Images Within an Enterprise Imaging Solution Agenda • Enterprise Imaging / Non-DICOM Market Trends
    Managing Non-DICOM Images within an Enterprise Imaging Solution Agenda • Enterprise Imaging / Non-DICOM Market Trends • Managing Non-DICOM Images in the Enterprise • Merge’s Non-DICOM Solution Options • Questions? Enterprise Imaging / Non-DICOM Trends 3 Interoperability Market Drivers M&A / Consolidation Enterprise Image Management Clinical and Financial Economies of Scale Comprehensive Image Record Connecting Providers EHR Optimization Patient Centric Care Across Sites Unified Patient Image Record 4 Providers Generate a Flood of Data Digital Clinical Objects Specialty MPEG, JPEG Other Most Common Devices DICOM A/V, WAV , PDF Clinical Anesthesia In Room C-Arm, X-ray, Anesthetic, Record Keeping Reports Cardiology CVMR, CVCT, Cath, CVUS, CVECG / Holter / Stress / Pace Dermatology Photos, dermatological Reports Emergency Medicine X-ray, CT, ECG, Triage Reports Endocrinology SPECT / CT, PET / CT, Physician Reports, Voice Dictation Files Family Medicine Physician Notes, Reports Gastroenterology Barium X-ray, CT, NM, Endoscopes, US, Reports, Voice Dictation Files Hematology HT Reports, Voice Dictation Files ICU Medicine In Dept C-Arm, X-ray, Patient CIS Flow Chart Reports Nephrology US and MRI Angiography, Scintigraphy (Nuc Med) Reports Voice Neurology Renal Scans, SPECT/CT, PET/CT, Physician Reports, Renal Grams, Voice iConnect™ Solution Nuclear Medicine Stored in a VNA US, Physician Reports, Voice Dictation Files Obstetrics X-ray, CT, US, Reports, Voice Dictation Files, Fetal Strips, Reports Oncology
    [Show full text]
  • Intro to HL7 and DICOM
    Working in an Integrated Digital Healthcare Enterprise 2004 Introduction and Update to HL7 and DICOM Herman Oosterwijk, Adjunct faculty, University of North Texas President OTech Inc. [email protected] www.otechimg.com DICOM/HL7 slide 1 Working in an Integrated Digital Healthcare Enterprise 2004 Agenda: ! What is HL7 ! What’s new in HL7 ! What is DICOM ! What’s new in DICOM ! Conclusion, Q and A DICOM/HL7 slide 2 DICOM/HL7 what’s new? Herman Oosterwijk www.otechimg.com page 1 Working in an Integrated Digital Healthcare Enterprise 2004 What is HL7: ! A pragmatic, simple protocol to exchange information dealing with, for example: ! Patient registration ! Orders (clinical, radiology, laboratory, etc.) ! results and observations ! queries, e.g. for patient demographics ! finance for billing purposes ! master files and indexes ! document control, such as approval status ! scheduling and logistics DICOM/HL7 slide 3 Working in an Integrated Digital Healthcare Enterprise 2004 Information Workflow example: Broker System Ordering, Scheduling Modality Worklist Mgt HL7 Storage Archive Storage Cmt Reporting Retrieve Performed Procedure Viewing Step DICOM/HL7 slide 4 DICOM/HL7 what’s new? Herman Oosterwijk www.otechimg.com page 2 Working in an Integrated Digital Healthcare Enterprise 2004 DICOM vs HL7 ! Scope is Imaging ! Scope beyond Imaging ! Protocol is mainly ! Protocol is Event driven, Client/Server i.e. unsolicited Events ! Based on Object ! Object Oriented in v 3.0 Oriented principles ! Attributes encoded ! Attributes: text strings ! Conformance
    [Show full text]
  • (DICOM) Part 16: Content Mapping Resource
    PS 3.16-2001 Digital Imaging and Communications in Medicine (DICOM) Part 16: Content Mapping Resource Published by National Electrical Manufacturers Association 1300 N. 17th Street Rosslyn, Virginia 22209 USA © Copyright 2001 by the National Electrical Manufacturers Association. All rights including translation into other languages, reserved under the Universal Copyright Convention, the Berne Convention or the Protection of Literacy and Artistic Works, and the International and Pan American Copyright Conventions. - Standard - PS 3.16 - 2001 Page 2 CONTENTS CONTENTS..........................................................................................................................................................................2 FOREWORD........................................................................................................................................................................4 1.....Scope and field of application...................................................................................................................................5 2.....Normative references .................................................................................................................................................5 BI-RADS Terminology and Nomenclature...................................................................................................5 MQCM 1999 Terminology and Nomenclature................................................................................................5 MQSA Terminology and Nomenclature...........................................................................................................5
    [Show full text]
  • Comparative Study of Healthcare Messaging Standards for Interoperability in Ehealth Systems
    Comparative Study of Healthcare Messaging Standards for Interoperability in eHealth systems BOAZ ABRAHAM | STUDENT ID: 18481798 | SUPERVISOR: DR ANUPAMA GINIGE |SUBMISSION YEAR: 2017 DEDICATION To my loving wife Ruth and daughter Sharon Rose Page | I ACKNOWLEDGEMENTS I would like to express my sincere thanks to, Dr Anupama Ginige, my supervisor, for providing guidance from the beginning and reviewing the thesis regularly. Her encouragement, feedback, tips and knowledge sharing helped me to complete this dissertation. I would like to thank all the Western Sydney University, SCEM and GRS department staffs who supported throughout my Master of Research course. I would like to thank my eHealth and Ministry of Health colleagues, friends and management who helped at different stages to gather information for the research. Lastly, I would like to thank my family for sharing their family time and support to complete this course in time. Page | II STATEMENT OF AUTHENTICATION The content presented in this thesis is, to the best of my knowledge and belief, original except as acknowledged in the references. I hereby declare that I have not submitted this material, either in full or in part, for a degree at this or any other institution. Boaz Abraham Page | III Table of Contents List of Tables .......................................................................................................................... VI List of figures ........................................................................................................................
    [Show full text]
  • Cooperating Standards in Healthcare GS1 Standards and Other Standards Cooperating in Clinical Treatment Scenarios
    GS1 identifiers Other standards The Global Language of Business GTIN (Global Trade Item Number) SNOMED CT (Systematized Nomenclature of Products such as medicinal products, medical Medicine / Clinical Terms) devices, medical consumables, vaccines, blood It is the most comprehensive and precise clinical derivatives and raw materials at all product and health terminology product in the world, owned and packaging levels (e.g. unit of use, primary distributed around the world by SNOMED Cooperating standards packaging, retail unit, inner pack, case and pallet). International. SNOMED CT has been developed Attributes such as batch/lot number and expiry date collaboratively to ensure it meets the diverse needs in healthcare can provide additional traceability information. and expectations of clinicians worldwide and is now Individual trade item instance(s) can be identified accepted as a common global language for health GS1 standards and other standards by combining the GTIN with a serial number, which is terms. Improved health records, clinical decisions cooperating in clinical treatment scenarios mandated by an increasing number of regulations. and analysis, leading to higher quality, consistency and safety in healthcare delivery benefit from GLN (Global Location Number) SNOMED CT. www.snomed.org Locations: Theatres, Patient rooms, Wards, DICOM (Digital Imaging and Communications in Pharmacies, imprest/Store rooms, Pathology, Medicine) Radiology, Distribution centres, Manufacturing sites, It is the international standard to transmit, store,
    [Show full text]
  • Working with the DICOM Data Standard in R
    Working with the DICOM Data Standard in R Brandon Whitcher Volker J. Schmid Pfizer Worldwide R&D Ludwig-Maximilians Universit¨at Munchen¨ Andrew Thornton Cardiff University Abstract The package oro.dicom facilitates the interaction with and manipulation of medical imaging data that conform to the DICOM standard. DICOM data, from a single file or single directory or directory tree, may be uploaded into R using basic data structures: a data frame for the header information and a matrix for the image data. A list structure is used to organize multiple DICOM files. The conversion from DICOM to ANALYZE/NIfTI is straightforward using the capabilities of oro.dicom and oro.nifti. Keywords: export, imaging, import, medical, visualization. 1. Introduction Medical imaging is well established in both the clinical and research areas with numerous equipment manufacturers supplying a wide variety of modalities. The DICOM (Digital Imag- ing and Communications in Medicine; http://medical.nema.org) standard was developed from earlier standards and released in 1993. It is the data format for clinical imaging equip- ment and a variety of other devices whose complete specification is beyond the scope of this paper. All major manufacturers of medical imaging equipment (e.g., GE, Siemens, Philips) have so-called DICOM conformance statements that explicitly state how their hardware im- plements DICOM. The DICOM standard provides interoperability across hardware, but was not designed to facilitate efficient data manipulation and image processing. Hence, additional data formats have been developed over the years to accommodate data analysis and image processing. The material presented here provides users with a method of interacting with DICOM files in R (R Development Core Team 2010).
    [Show full text]