DOCSLIB.ORG

Interoperability 101: the Past, Present, and Future

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Interoperability 101: the Past, Present, and Future Interoperability 101: The Past, Present, and Future Session PE4, March 9, 2020 Steve Lane, MD, MPH, FAAFP Clinical Informatics Director, Privacy, Information Security & Interoperability, Sutter Health Mariann Yeager, MBA Chief Executive Officer, The Sequoia Project DISCLAIMER: The views, opinions and images expressed in this presentation are those of the author and do not necessarily represent official policy or position of HIMSS. 1 Meet Our Speakers Dr. Steven Lane Mariann Yeager Clinical Informatics Director, Privacy, Information Security & Interoperability Sutter Health 2 Conflict of Interest Steven Lane, MD, MPH, FAAFP has no real or apparent conflicts of interest to report. Mariann Yeager, MBA has no real or apparent conflicts of interest to report. 3 Agenda • Health Information Exchange: a history • Sutter Health: a present-day case study • Trusted Exchange Framework and Common Agreement: the future of exchange • Physicians Engagement: the role of providers in shaping health information exchange today and tomorrow 4 Learning Objectives • Describe the multitude of health information exchange options available today • Outline the scope of TEFCA based on the draft published by the ONC • Identify opportunities for physician engagement in the development and finalization of the Common Agreement and the implementation of the Trusted Exchange Framework 5 Health Information Exchange: A history 6 Perspective • Primary care family physician and EHR user x > 30 years • Clinical informaticist x 25 years • Interoperability focus x 10 years • The Sequoia Project – Board • Carequality – Steering Committee • DirectTrust – Clinicians Steering Workgroup • HL7 Da Vinci Project – Clinical Advisory Council • HIMSS – Interoperability & HIE Committee • HHS/ONC – Health Information Technology Advisory Committee 8 Interoperability Definitions • 21st Century Cures Act • HIMSS Health information technology that enables • Foundational Interoperability: the secure exchange of electronic health System connectivity > Exchange data information with and use of electronic health information from, other health information • Structural Interoperability: technology without special effort on the part Field level formatting, syntax > Exchange information of the user; allows for complete access, exchange, and use of all electronically • Semantic Interoperability: Codification of data accessible health information for authorized > Meaning, interpretation use under applicable State or Federal law; • Organizational Interoperability: does not constitute information blocking Policy, workflow, functional > Utility, benefit, outcomes 9 Interoperability Standards • 1982 – Accredited Standards Committee (ASC) X12 Version 1 • Electronic Data Interchange (EDI) for financial / administrative transactions • Named in HIPAA as required standard for specific transactions, e.g., prior auth • 1987 – Health Level 7 (HL7) Version 2 • Point-to-point connectivity • Intra-operability – connecting applications within institutions • 2005 – HL7 Clinical Document Architecture (CDA) • Human readable XML documents • Scalable for cross organizational use • 2011 – HL7 Fast Healthcare Interoperability Resources (FHIR®) • Modern, flexible, purpose-built for healthcare • 2019 – First normative release (R4) 10 Interoperability Promise • Holistic care • Patient safety • Care coordination • Value – e.g. avoiding duplicate services • Public health • Medical research • Innovation – Care models, services • Patient engagement, empowerment, control of data, choice 11 Interoperability Successes • HIE/HIOs – Regional/state, proprietary • Central data repository and access • Connectivity and messaging – multiple stakeholders, uses • Services – e.g., event notification • Networks • Nationwide Health Information Network • Direct Project > DirectTrust • eHealth Exchange > The Sequoia Project • Vendor-based Networks: CommonWell, Epic Care Everywhere, etc. • Trusted Exchange Framework: Carequality > TEFCA 12 Interoperability Challenges • Everyone agrees that data access and liquidity is critical to support optimized coordinated care and population health management • BUT… • Significant challenges: • Clinicians drowning in data • Discrete data integration, reconciliation and use • Concerns about privacy and risk • Incentivizing data access, use, curation, and exchange • Changing federal rules and requirements 13 Drowning in Data • Due to: • EHR implementation • System Integration • Interoperability • New data sources • Patient-generated data • Multiple “-omics” • Claims data • Social determinants of health 14 Standards-based Document Exchange • Direct interoperability (push) • Query-based document exchange (pull) 15 Direct Interoperability • Direct Project: launched in 2010 as part of the Nationwide Health Information Network (NwHIN) • Goal: simple, secure, standards-based method for sending health information to trusted recipients via the Internet • Included in 2014 EHR certification criteria • Required by Meaningful Use Stage 2 • HISPs accredited through DirectTrust represent more than: • 2.3M Direct Addresses • 238K organizations • 299K patients/consumers 16 Direct – Current State • All ONC certified EHRs have the ability to send and receive transition of care documents via the Direct Standard • Many providers have not routinely implemented this functionality • Use cases: • Transitions of care – ambulatory, inpatient, post-acute, EMS • Closed loop referrals • Care coordination messaging • Push notifications – Event notification, reporting • 67M transactions / month 17 eHealth Exchange • Four Federal Agencies • Veterans Affairs • Department of Defense • Social Security Administration • CMS • 75% of US hospitals • 70,000 medical groups • >50% of regional/state HIEs • 16M documents exchanged / month 18 Epic Care Everywhere • 367 Epic customer organizations • 2,032 hospitals; 45,830 clinics • 1,689 connections to 110 unique vendors’ systems • via eHealth Exchange, Carequality, Direct • 150M records exchanged / month 19 CommonWell • Core services: • Patient ID and record location • Document exchange • 15K provider sites • 66M patient records • 60M monthly XCPD patient discovery / record locator transactions • 60M documents exchanged / month 20 Carequality Framework • Policy framework and technical standards for networks and other implementers to exchange with each other • CommonWell, Epic Care Everywhere, eHealth Exchange, HIT vendors • 600,000 Physicians, 40,000 Clinics, 1,700 hospitals • Working with The Sequoia Project in its role as the Recognized Coordinating Entity (RCE) to implement the national Trusted Exchange Framework & Common Agreement (TEFCA) • 90M documents exchanged / month 21 Standards-based Document Exchange Volume 22 Application Programming Interfaces (APIs) * in healthcare 23 Fast Healthcare Interoperability Resources (FHIR®) • Purpose-built for healthcare • Supports exchange of targeted data via APIs • A user/application may request just the data (resources) of interest in a well-defined format • Modern web-base data structure, transport and security • Rapid development 24 Evolving FHIR Use Cases • EHR applications • SMART – Substitutable Medical Apps, Reusable Technology (>75 apps) • Argonaut Project – clinical notes, assessments, bulk data access • Individual / Patient Access • CMS Blue Button 2.0 – Medicare claims data • Apple Health Records, etc. – EHR patient portal and Laboratory data • Payer-Provider Exchange • CMS Beneficiary Claims Data API (BCDA) and Data at the Point of Care (DPC) • Da Vinci Project • FHIR Accelerator Projects • Social Determinants of Health – Gravity Project • Post-Acute Care Interoperability – PACIO 25 Individual / Patient Access via APIs • Based on HIPAA individual right of access to health data • Early successes: • Blue Button 2.0 – CMS claims available to Medicare beneficiaries via API • Apple Health Records • Common Health for Android 26 Apple Health Records • FHIR® API-based access to health data from multiple vendors • EHRs: • Allscripts • Epic • Athenahealth • MEDITECH • Cerner • VA • Laboratories: • LabCorp • Quest • 454 organizations/practices participating a/o 01/27/2020 • Health records data securely stored on user iPhones • Individuals can choose to allow apps to access health records data stored in HealthKit 27 Sutter Health: A present-day case study 28 Patient Records Exchanged Monthly 29 Unique Trading Partners 30 Patient Access via APIs – 2019 API Calls / month • 18,813 patients 15 Million have requested their data using ~3,000 patient SIX patient- requests / day facing apps Trusted Exchange Framework and Common Agreement (TEFCA): The future of exchange 32 This project is supported by the Office of the National Coordinator for Health Information Technology (ONC) of the U.S. Department of Health and Human Services (HHS) under 90AX0026/01-00 Trusted Exchange Framework and Common Agreement (TEFCA) Recognized Coordinating Entity (RCE) Cooperative Agreement. This information or content and conclusions are those of the author and should not be construed as the official position or policy of, nor should any endorsements be inferred by ONC, HHS or the U.S. Government. © All rights reserved. Why Do We Need a Trusted Exchange Framework and Common Agreement (TEFCA)? COMPLEXITY OF CURRENT PROLIFERATION OF AGREEMENTS Many organizations have to join multiple Health Information Networks (HINs), and most HINs do not share data with each other. Trusted exchange must be simplified in order to scale. © All rights reserved. 21st Century Cures Act – Section 4003(b)
Load more

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]
  • 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]
  • 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]
  • Health Level 7 an Overview
    Health Level 7 An Overview W. Ed Hammond, Ph.D., FACMI Chair, HL7 © 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. What does the name HL7 mean? “Health”“Health” represents represents thethe domaindomain ofof focus.focus. HL7’sHL7’s domaindomain includesincludes clinicalclinical andand administrativeadministrative data.data. "Level"Level Seven"Seven" refersrefers toto thethe highesthighest levellevel ofof thethe InternationalInternational OrganizationOrganization for for StandardizationStandardization (ISO)(ISO) communicationscommunications modelmodel forfor OpenOpen SystemsSystems InterconnectionInterconnection (OSI)(OSI) –– i.e., i.e., thethe applicationapplication levellevel.. Health Level Seven is an American National Standards Institute (ANSI - accredited Standards Developing Organizations (SDOs). © 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. The Organization HL7 is headquartered in Ann Arbor, MI, and, like most of the other SDOs, is a not- for-profit volunteer organization. Its members—providers, vendors, payers, consultants, government groups and others who have an interest in the development and advancement of clinical and administrative standards for healthcare—develop the standards and other products. © 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. What does HL7 do? Health Level Seven adheres to a strict and well-defined set of operating procedures that ensures consensus, openness and balance of interest on all matters, including balloting of standards. Health Level Seven develops specifications, the most widely used being a messaging standard that enables disparate healthcare applications to exchange key sets of clinical and administrative data.
    [Show full text]
  • 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 ....................................................................................................................................
    [Show full text]
  • Health IT Standards for Health Information Management Practices (HIT Standards for HIM Practices)
    Integrating the Healthcare Enterprise 5 IHE IT Infrastructure (ITI) White Paper 10 Health IT Standards for Health Information Management Practices (HIT Standards for HIM Practices) 15 Revision 1.1 20 Date: September 18, 2015 Author: ITI Planning Committee Email: [email protected] Please verify you have the most recent version of this document. See here for Published 25 versions and here for Public Comment versions. Copyright © 2015: IHE International, Inc. IHE IT Infrastructure White Paper – Health IT Standards for Health Information Management Practices (HIT Standards for HIM Practices) ______________________________________________________________________________ Foreword Integrating the Healthcare Enterprise (IHE) is an international initiative to promote the use of standards to achieve interoperability among health information technology (HIT) systems and effective use of electronic health records (EHRs). IHE provides a forum for care providers, HIT 30 experts and other stakeholders in several clinical and operational domains to reach consensus on standards-based solutions to critical interoperability issues. The primary output of IHE is system implementation guides, called IHE Profiles. IHE publishes each profile through a well-defined process of public review and trial implementation and gathers profiles that have reached final text status into an IHE Technical Frameworks. 35 This white paper is published on September 18, 2015. Comments are invited and can be submitted at http://www.ihe.net/ITI_Public_Comments. For on-going development work, see http://wiki.ihe.net/index.php?title=HIT_Standards_for_HIM_Practices 40 General information about IHE can be found at: http://ihe.net. Information about the IHE IT Infrastructure domain can be found at: http://ihe.net/IHE_Domains. Information about the organization of IHE Technical Frameworks and Supplements and the process used to create them can be found at: http://ihe.net/IHE_Process and 45 http://ihe.net/Profiles.
    [Show full text]
  • The Nexus of Iot Devices and Healthcare Level 7 (HL7)
    International Journal of Technology and Engineering Studies volume 5 issue 6 pp. 183-189 doi: https://dx.doi.org/10.20469/ijtes.5.10002-6 The Nexus of IoT Devices and Healthcare Level 7 (HL7) Hasan K. Naji∗ University of Technology, Bucharest, Romania Abstract: The main goal of this study is to discuss the need for interoperability of Electronic Health Records (EHR) and Internet of Things (IoT) and highlight how the Health Level 7 (HL7) interoperability standard could be the solution to bringing the benefits of these disparate systems together for the benefit of all patients. This study conducted a thorough literature search and analyzed the EHR and HL7 critically. The results highlight that the health care industry is experiencing unprecedented changes, with a considerable increase in the use of electronic/automated systems that can make considerable improvements in the quality of life of patients around the world. However, to achieve such benefits, these systems need to be able to communicate freely with each other. Thus, more emphasis is made on improvising the health care systems such that they provide maximum benefits for the patients. Keywords: HL7, IoT, healthcare, EHR. Received: 21 May 2019; Accepted: 18 October 2019; Published: 27 December 2019 I. INTRODUCTION adoption of EHRs to improve patient safety and health Ever since the internet became a major force in care quality. There may also be more significant obstacles communication around the world and computers became to adoption of EHRs at the practice level. more commonplace, the medical industry has embraced Among the obstacles to EHR adoption noted by them to some extent.
    [Show full text]
  • Snomed Ct® and 3M™ Hdd: the Successful Implementation Strategy
    SNOMED CT® AND 3M™ HDD: THE SUCCESSFUL IMPLEMENTATION STRATEGY Federal Health Care Agencies Take the Lead The United States government has taken a leading role in the use of health information technologies to enhance the quality of patient care. Considered by leaders in health care technology to be a necessary step towards the enhancement of patient care, a 5-year, nationwide license for SNOMED Clinical Terms® (SNOMED CT®) was purchased by agencies of the Department of Health and Human Services for perpetual use by any governmental or eligible public, for- profit and non-profit organization located, incorporated and operating in the U.S. A comprehensive, widely accessible controlled medical vocabulary (CMV) such as this is deemed a required part of any integrated clinical information system that provides the communication of accurate, detailed patient information. In January 2004 the National Library of Medicine (NLM) of the National Institutes of Health will make SNOMED CT® available via the Unified Medical Language System® (UMLS). This comprehensive set of encoded medical concepts will work within a framework of interoperability standards for the electronic exchange of clinical health information. SNOMED – CT® will be incorporated into this common set of health care information technologies to support numerous efforts within the health care industry. Projects - such as the National Health Information Infrastructure (NHII) and the paperless electronic health record - have been outlined through collaborations between industry leaders, health care associations, and the U.S. government. The widespread use of an integrated set of health information standards is considered to be essential for the success of such projects, which have the potential for improving the quality of health-related services through the seamless exchange of accurate information.
    [Show full text]
  • Omg Healthcare
    Healthcare Services Specification Project (HSSP) After reading up on the condition, you Standards Leaders Collaborate decide to begin a self-imposed regimen of low-dose aspirin. You navigate to a to Create Interoperable screen within your PHR where you enter information about over-the-counter medicines you are taking and record your Healthcare Infrastructure. intention to start low-dose aspirin. A few years down the road, the way we manage our health After entering your information, you receive a drug interaction alert from the information could change. Imagine that you have a family system telling you to avoid aspirin and to consult with your doctor. You had forgotten history of heart disease and personally have many risk factors that you had experienced a bad reaction to aspirin as a child. Thankfully, the system is tied into a network that includes your for developing the condition. You want to learn more about provider’s EHR system, where your medical history is stored, preventing a potentially ways of preventing the condition, so you visit your networked adverse reaction. personal health portal, a website that maintains your electronic Your provider’s EHR systems have access to your electronically available medical medical information in a personal health record (PHR) and history and can instantly give alerts on drug interactions because in the year 2006, the US took action spurring the provides information about a variety of health concerns healthcare industry to rally around a set of commercial open standards. These and conditions. Interoperability this broad and seamless can only come from a comprehensive and capable infra- Electronic structure of industry standards.
    [Show full text]