Immunization-Related Capabilities and Guidance

Total Page:16

File Type:pdf, Size:1020Kb

Immunization-Related Capabilities and Guidance Centers for Disease Control and Prevention (CDC) Office of Infectious Diseases (OID) National Center for Immunization and Respiratory Diseases (NCIRD) Office of the Director Contract No: 200-2017-95860 I MMUNIZATION I NTEGRATION P ROGRAM : I MMUNIZATION -R E L A T E D C APABILITIES AND G UIDANCE UPDATE – S E P T E M B E R 14, 2 0 2 0 EHR Certification Process, Immunization-Related Guidance Formal Deliverable, September 14, 2020 VERSION HISTORY CHC will update Deliverable 10a to reflect changes that incorporate CDC’s review and feedback, as well as any new requirements or changes to the business environment in which the project exists. The table below tracks these changes and updates to the document. Version Implemented Revision Description Approved Approval Date # by Date by Draft CNI Advantage September 1st Draft F Eisenberg September 20, v.01 20, 2015 2015 1 CNI Advantage Version 1 CDC October 30, 2015 1.01 CNI Advantage October 6, Update based on public and CDC January 23, 2016 Technical Advisory Panel 2017 Feedback during Phase 3: 1. Remove unidirectional exchange test script; retain bidirectional exchange test script (page 1 and Section 5.41, page 14) 2. Section 5.2 (page 12) – add protection indicator to patient demographics 3. Section 5.81 (page 17) – Remove the term “audit” 4. Section 5.91 (page 17) – Discuss IIS acceptance of update from provider post- immunization reconciliation 5. Section 5.10.1 (page 18) – Saving post-reconciliation forecast 6. Section 5.29 (page 33) – Address vaccine series 7. Section 5.38 (page 39) – Patient’s preferred methods for notification 8. Section 5.41.1 (page 42) Adverse event terminology 2 CNI Advantage November Add capability examples and CDC January 23, and HIMSS 27, 2016 update for publication in 2017 HIMSS Immunization Integration Program. 1. Change test references to direct readers to the testing tool where the script can be downloaded. Formal Deliverable Page i September 14, 2020 EHR Certification Process, Immunization-Related Guidance Formal Deliverable, September 14, 2020 2. Add capability examples to publish as a single capability and guidance document. 3 CNI Advantage December Update with input from and HIMSS 21, 2016 Technical Advisory Panel to address guidance and capabilities. 4 Chickasaw October 23, Update based on input from Health 2017 public comments, Consulting and implementation testing and the HIMSS Technical Advisory Panel to address guidance and capabilities. 5 Chickasaw March 26, Update based on input from CDC March 26, 2018 Health 2018 the Technical Advisory Panel Consulting and and findings from HIMSS IIP HIMSS Testing Program to address guidance and capabilities. Added Change Log (Appendix C) 6 Chickasaw September Update based on input from September 30, Health 2018 testing, program feedback and 2018 Consulting and the Technical Advisory Panel HIMSS to address guidance and capabilities. 7 Chickasaw October Update based on input from October 15, Health 2019 testing, program feedback and 2019 Consulting and the Technical Advisory Panel HIMSS to address guidance and capabilities. 8 Chickasaw March 2020 Update based on quality CDC May 4, 2020 Health review and update of test plan. Consulting and HIMSS 9 Chickasaw May 2020 Removal of test pursuant to Health guidance from CDC received Consulting and on April 29, 2020 and HIMSS discussed April 30, 2020 10 Chickasaw September Update based on input and September 14, Health 2020 agreed upon recommendations 2020 Consulting and from the Technical Advisory HIMSS Panel to address guidance and capabilities. Details to Methods in Section 5. Formal Deliverable Page ii September 14, 2020 EHR Certification Process, Immunization-Related Guidance Formal Deliverable, September 14, 2020 TABLE OF CONTENTS VERSION HISTORY ...................................................................................................................... i 1 Overview ................................................................................................................................. 1 1.1 Project Overview .............................................................................................................. 1 1.2 The Link Between Immunization-Related Capabilities Within EHRs and Improved Immunization Rates ..................................................................................................................... 1 1.3 Other Types of Value Derived from Immunization-Related Capabilities in EHRs ......... 4 1.3.1 Other Types of Value for Providers ..............................................................................4 1.3.2 Other Types of Value for IIS’ .......................................................................................5 1.3.3 Other Types of Value for EHR and Other Clinical Software Developers ....................5 1.3.4 Other Types of Value for Those Who Pay for Health Care ..........................................5 1.3.5 Other Types of Value for Individuals ...........................................................................6 2 Background.............................................................................................................................. 6 2.1 Literature Review and Requirement Definition ............................................................... 6 2.2 Evaluating EHR Software and Piloting a Testing Process ............................................... 8 2.3 Launch of the IIP and the Technical Advisory Panel ....................................................... 8 2.4 Updates for 2020 .............................................................................................................. 9 3 Overview of Conceptual Model for Requirements: General User Workflows ..................... 11 4 Functional Test Development ................................................................................................ 13 4.1 Use of NIST Tool for Test Development and Processing .............................................. 14 5 General Description of User Workflow 1: Register and Identify a Patient ........................... 15 5.1 Who Performs User Workflow 1: Register and Identify a Patient ................................. 15 5.2 Examples of Work in This Area ..................................................................................... 15 5.3 Requirement 1.1 Register New Patients ......................................................................... 16 5.3.1 Example of Scenario “Register New Patients” ...........................................................16 5.3.2 Guidance .....................................................................................................................16 5.3.3 Test ..............................................................................................................................19 5.4 Requirement 1.2 Select New Patient .............................................................................. 20 5.4.1 Example of Scenario “Select New Patient” ................................................................20 5.4.2 Guidance .....................................................................................................................20 5.4.3 Test ..............................................................................................................................20 5.5 Requirement 1.3 Select One or More Patients ............................................................... 20 5.5.1 Example of Scenario “Select One or More Patients” ..................................................21 5.5.2 Guidance .....................................................................................................................21 5.5.3 Test ..............................................................................................................................21 Formal Deliverable Page iii September 14, 2020 EHR Certification Process, Immunization-Related Guidance Formal Deliverable, September 14, 2020 6 General Description of User Workflow 2: “Manage External Query, Response, and Reconciliation” ............................................................................................................................. 21 6.1 Who Performs User Workflow 2: Manage External Query, Response, and Reconciliation ............................................................................................................................ 21 6.1.1 Examples of Work in This Area ..................................................................................22 6.2 Requirement 2.1 Batch Request / Receive Patient Immunization History .................... 22 6.3 Requirement 2.2 Request / Receipt of Patient Immunization History ........................... 22 6.3.1 Example of Scenario “Request / Receipt of Patient Immunization History” ..............22 6.3.2 Guidance .....................................................................................................................23 6.3.3 Test ..............................................................................................................................23 6.4 Requirement 2.3 Compare Public Health Immunization Registry (IIS) Immunization History to EHR Immunization History ..................................................................................... 23 6.4.1 Example of Scenario “Compare Public Health Immunization Registry (IIS) Immunization History to EHR Immunization History” .........................................................24 6.4.2 Guidance .....................................................................................................................24
Recommended publications
  • Building the Business Case for SNOMED CT®
    Building the Business Case for SNOMED CT® Promoting and Realising SNOMED CT®’s value in enabling high-performing health systems Russell Buchanan Marc Koehn A Gevity Consulting Inc. Company Building the Business Case for SNOMED CT® Promoting and Realising SNOMED CT®’s value in enabling high-performing health systems Copyright © 2014, International Health Terminology Standards Development Organisation (www.ihtsdo.org) Gordon Point Informatics Ltd. (GPi), Gevity Consulting Inc., and IHTSDO recognize all trademarks, registered trademarks and other marks as the property of their respective owners. Gordon Point Informatics Ltd. A Gevity Consulting Inc. Company (Gevity Consulting Inc. was formerly known as Global Village Consulting Inc.) #350 - 375 Water Street Vancouver, British Columbia Canada V6B 5C6 Telephone: +1-604-608-1779 www.gpinformatics.com | www.gevityinc.com ii Acknowledgments The authors would like to gratefully acknowledge a number of contributors without whose advice and support this paper would not have been possible. PROJECT STEERING COMMITTEE MEMBERS Members of the project steering committee provided overall guidance and insights throughout the project: • Liara Tutina, Customer Relations Lead (Asia Pac), IHTSDO • Vivian A. Auld, Senior Specialist for Health Data Standards, National Library of Medicine, USA • Dr. Md Khadzir Sheikh Ahmad, Deputy Director, Health informatic Centre, P&D Division, Ministry of Health, Malaysia • Kate Ebrlll, Head of National Service Operation and Management, National eHealth Transition Authority (NEHTA), Australia • Anna Adelöf, Customer Relations Lead (EMEA) , IHTSDO WORKING GROUP MEMBERS Our working group offered not only ongoing advice and reviews but also provided access to critical materials and contacts: • Liara Tutina, Customer Relations Lead (Asia Pac), IHTSDO • Dr.
    [Show full text]
  • Direct Comparison of MEDCIN and SNOMED CT for Representation Of
    Direct Comparison of MEDCIN ® and SNOMED CT ® for Representation of a General Medical Evaluation Template Steven H. Brown MS MD 1,2 , S. Trent Rosenbloom MD MPH 2 , Brent A. Bauer MD 3, Dietli nd Wahner -Roedler MD 3, David A. Froehling, MD, Kent R, Bailey PhD, M ichael J Lincoln MD, Diane Montella MD 1, Elliot M. Fielstein PhD 1,2 Peter L. Elkin MD 3 1. Department of Veterans Affairs 2. Vanderbilt University, Nashville TN 3. Mayo Clinic, Rochester MN Background : Two candidate terminologies to efforts. Usable and functionally complete support entry of ge neral medical data are standard terminologies need to be available to SNOMED CT and MEDCIN . W e compare the systems designers and architects. Two candidate ability of SNOMED CT and MEDCIN to terminologies to support entry of general medical represent concepts and interface terms from a data are SNOMED CT and MED CIN . VA gener al medical examination template. Methods : We parsed the VA general medical SNOMED CT is a reference terminology that evaluation template and mapped the resulting has been recommended for various components expressions into SNOMED CT and MEDCIN . of patient medical record information by the Internists conducted d ouble independent reviews Consolidated Health Informatics Council and the on 864 expressions . Exact concept level matches National Committee on Vital and Health were used to evaluate reference coverage. Exact Statistics. (12) SNOMED CT, licensed for US - term level matches were required for interface wide use by the National Library of Medicine in terms. 2003, was evaluated in 15 M edline indexed Resul ts : Sensitivity of SNOMED CT as a studie s in 2006 .
    [Show full text]
  • Advancing Standards for Precision Medicine
    Advancing Standards for Precision Medicine FINAL REPORT Prepared by: Audacious Inquiry on behalf of the Office of the National Coordinator for Health Information Technology under Contract No. HHSM-500-2017-000101 Task Order No. HHSP23320100013U January 2021 ONC Advancing Standards for Precision Medicine Table of Contents Executive Summary ...................................................................................................................................... 5 Standards Development and Demonstration Projects ............................................................................ 5 Mobile Health, Sensors, and Wearables ........................................................................................... 5 Social Determinants of Health (SDOH) ............................................................................................. 5 Findings and Lessons Learned .......................................................................................................... 6 Recommendations ........................................................................................................................................ 6 Introduction ................................................................................................................................................... 7 Background ................................................................................................................................................... 7 Project Purpose, Goals, and Objectives ..................................................................................................
    [Show full text]
  • Standard Nursing Terminologies: a Landscape Analysis
    Standard Nursing Terminologies: A Landscape Analysis MBL Technologies, Clinovations, Contract # GS35F0475X Task Order # HHSP2332015004726 May 15, 2017 Table of Contents I. Introduction ....................................................................................................... 4 II. Background ........................................................................................................ 4 III. Landscape Analysis Approach ............................................................................. 6 IV. Summary of Background Data ............................................................................ 7 V. Findings.............................................................................................................. 8 A. Reference Terminologies .....................................................................................................8 1. SNOMED CT ................................................................................................................................... 8 2. Logical Observation Identifiers Names and Codes (LOINC) ........................................................ 10 B. Interface Terminologies .................................................................................................... 11 1. Clinical Care Classification (CCC) System .................................................................................... 11 2. International Classification for Nursing Practice (ICNP) ............................................................. 12 3. NANDA International
    [Show full text]
  • Identifying Clinical Terms in Medical Text Using Ontology-Guided Machine Learning
    JMIR MEDICAL INFORMATICS Arbabi et al Original Paper Identifying Clinical Terms in Medical Text Using Ontology-Guided Machine Learning Aryan Arbabi1,2, MSc; David R Adams3, MD, PhD; Sanja Fidler1, PhD; Michael Brudno1,2, PhD 1Department of Computer Science, University of Toronto, Toronto, ON, Canada 2Centre for Computational Medicine, Hospital for Sick Children, Toronto, ON, Canada 3Section on Human Biochemical Genetics, National Human Genome Research Institute, National Institutes of Health, Bethesda, MD, United States Corresponding Author: Michael Brudno, PhD Department of Computer Science University of Toronto 10 King©s College Road, SF 3303 Toronto, ON, M5S 3G4 Canada Phone: 1 4169782589 Email: [email protected] Abstract Background: Automatic recognition of medical concepts in unstructured text is an important component of many clinical and research applications, and its accuracy has a large impact on electronic health record analysis. The mining of medical concepts is complicated by the broad use of synonyms and nonstandard terms in medical documents. Objective: We present a machine learning model for concept recognition in large unstructured text, which optimizes the use of ontological structures and can identify previously unobserved synonyms for concepts in the ontology. Methods: We present a neural dictionary model that can be used to predict if a phrase is synonymous to a concept in a reference ontology. Our model, called the Neural Concept Recognizer (NCR), uses a convolutional neural network to encode input phrases and then rank medical concepts based on the similarity in that space. It uses the hierarchical structure provided by the biomedical ontology as an implicit prior embedding to better learn embedding of various terms.
    [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]
  • SNOMED International Address to the NCVHS Semantic Standards Harmonization Panel
    SNOMED International address to the NCVHS Semantic Standards Harmonization Panel James T. Case MS, DVM, PhD, FACMI Chief Terminologist, SNOMED International AUGUST 25, 2021 SNOMED International: Delivering CT What do we mean by ● Clinical meaning captured specifically and explicitly semantic ○ Granularity harmonization? ○ No implied meaning ○ Computable definitions In the context of healthcare ● Lossless transfer between terminology standards, systems harmonization is interpreted ● Bidirectional equivalence maps as the maintenance of fidelity ● Compatible with multiple of meaning of data information models throughout its lifecycle, ● Meaning maintained when unaffected by mappings or translated to another language translation. 2 SNOMED International: Delivering CT What is the greatest opportunity for harmonizing terminology standards? ● Identification of a subset of high priority, robust, fit-for-purpose standards ○ “The nice thing about standards is that there are so many of them to choose from.” - Andrew S. Tanenbaum ○ Reliably maintained, frequent releases ○ Focus on enhancement (comprehensive coverage) ○ USCDI is a good start (limited scope) ● Collaboration among SDOs (formal agreements) ● Joint Initiative Council for Global Health Informatics Standardization (JIC) Focus on a small set of “fit-for-purpose” standards. Agreement needed for SDOs to work together 3 SNOMED International: Delivering CT What are the greatest barriers to semantic harmonization? How do we move the barrier? • Leverage experiences in other ● Extensive use of local
    [Show full text]
  • SNOMED CT Clinical Forum
    Benefits of SNOMED CT from a clinical perspective; The Rotherham experience Tuesday 9 April 2019 SNOMED International – Business MeetinGs 2019, London, UK Monica Jones – Associate Director of Information Services TRFT & Population Health ManaGement Lead for YHCR Agenda This presentation will provide an honest account drawing on real life experience of how using SNOMED CT has impacted the Rotherham NHS Foundation Trust, over the past six years, offering insight on the processes and challenges as well as sharing lessons learned. This session focuses on the clinical benefits of implementing SNOMED CT, gaining valuable insight from a trust that has already made the changeover. From practical necessities to wider service implications, these insights and 'top tips' will enable colleagues to accurately predict and overcome likely challenges. Rotherham NHS FT - Health Informatics • A fully co-terminus health and social care community with a population of c260,000 • ‘Medium’ District General Hospital and community services. • Approx. 4,200 staff, £250M pa budGet • Rural with Industrial Centre • Shared Health Informatics Service The NHS digital strategic landscape • The focus in digital planning has shifted from trusts to the local health community, Sustainability and Transformation Partnerships (STPs) leading to Integrated Care Systems (ICS) • The national agenda has changed from technology to ‘digitisation’ • The Wachter Report to NHS England endorsed this and led to 12 Trusts being appointed ‘Global Digitisation Exemplars (GDEs)’ attracting matched funding up to £10m • Trust-based systems are still critical in driving a paper-lite NHS agenda for the 2020’s • There is an increased awareness of CyberSecurity threats to the NHS Over the past 10 years the Trust has implemented and developed core mission-critical patient systems around Meditech (Acute) and SystmOne (Community).
    [Show full text]
  • The Need for a Global Language - SNOMED CT Introduction
    The need for a global language - SNOMED CT introduction Jane Millar Collaboration Lead Ian Green Clinical Engagement and Education business manager Purpose of tutorial ▪ Increasing knowledge of SNOMED CT and its applicability for healthcare professionals, ▪ Outlining how SNOMED CT contributes to the EHR and the benefits for those caring for individuals. ▪ Provides details of the work with ICN to align SNOMED CT and ICNP and practically what this means for nursing documentation and the shared EHR Objectives therefore: ▪ Attendees will: ▪ be able to understand what SNOMED CT is and how it fits in the EHR with other standards ▪ have an insight into its importance in supporting the information requirements for Nursing practice ▪ have an insight into the importance of nursing input into the development of SNOMED CT ▪ know how you can extend your knowledge of SNOMED CT Agenda ▪ SNOMED CT and its place as part of the EHR (part 1) ▪ Background ▪ What is SNOMED CT Break – group work ▪ SNOMED CT and its place as part of the EHR (part 2) ▪ Scope and usage of SNOMED CT ▪ Clinical input to SNOMED CT ▪ IHTSDO approach to Collaboration ▪ Linking SNOMED CT and ICNP through Collaboration Break – group work ▪ Feedback from break ▪ Taking SNOMED CT home ▪ What next, education, finding out more etc Approach ▪ High level view only in the time, with guidance on where to find out more ▪ As interactive as possible – ▪ Sharing experience of those in the room ▪ Take questions as we go – please raise your hand to indicate you have a question SNOMED CT and the EHR
    [Show full text]
  • UMLS Update & Discussion
    Introduction – Jerry Sheehan UMLS Overview – Olivier Bodenreider Brief History Overview through an example (Addison’s disease) UMLS Users and Use Cases – Patrick McLaughlin UMLS Terminology Services (UTS) Usage Statistics Distribution and other Issues 2 Olivier Bodenreider, MD, PhD Chief, Cognitive Science Branch Lister Hill National Center for Biomedical Communications National Library of Medicine [email protected] 3 Unified Medical Language System 4 Started in 1986 National Library of Medicine “Long-term R&D project” (Integrated Academic Complementary to IAIMS Information Management Systems) «[…] the UMLS project is an effort to overcome two significant barriers to effective retrieval of machine-readable information. • The first is the variety of ways the same concepts are expressed in different machine-readable sources and by different people. • The second is the distribution of useful information among many disparate databases and systems.» Lindberg DA, Humphreys BL, McCray AT. Methods Inf Med. 1993 Aug;32(4):281-91. 5 Database Series of relational files Interfaces UMLS Terminology Services (UTS) Web-based UMLS browser Controlled access To files for download (UMLS, RxNorm, SNOMED CT) To derived applications (VSAC, CDE repository) Application programming interfaces (Restful API) Applications lvg (lexical programs) MetamorphoSys (installation and customization) “middleware” rather than end-user application 6 Metathesaurus . Organize terms Concepts Inter-concept relationships . Organize concepts Semantic Network Semantic types . Categorize concepts Semantic network relationships Lexical resources SPECIALIST Lexicon . Support discovery of Lexical tools synonymy 7 (2017AB) . SNOMED CT . English 153 families of source vocabularies . Spanish Not counting 48 translations . RxNorm . FDB 25 languages (through translations) . Micromedex . Multum Broad coverage of biomedicine . CVX 10.7M names (normalized) .
    [Show full text]
  • Useful Applications for SNOMED CT®
    Useful Applications for SNOMED CT® Audio Seminar/Webinar March 8, 2007 Practical Tools for Seminar Learning © Copyright 2007 American Health Information Management Association. All rights reserved. Disclaimer The American Health Information Management Association makes no representation or guarantee with respect to the contents herein and specifically disclaims any implied guarantee of suitability for any specific purpose. AHIMA has no liability or responsibility to any person or entity with respect to any loss or damage caused by the use of this audio seminar, including but not limited to any loss of revenue, interruption of service, loss of business, or indirect damages resulting from the use of this program. As a provider of continuing education, the American Health Information Management Association (AHIMA) must assure balance, independence, objectivity and scientific rigor in all of its endeavors. AHIMA is solely responsible for control of program objectives and content and the selection of presenters. All speakers and planning committee members are expected to disclose to the audience: 1) any significant financial interest or other relationships with the manufacturer(s) or provider(s) of any commercial product(s) or services(s) discussed in an educational presentation; 2) any significant financial interest or other relationship with any companies providing commercial support for the activity; and 3) if the presentation will include discussion of investigational or unlabeled uses of a product. The intent of this requirement is not to prevent a speaker with commercial affiliations from presenting, but rather to provide the participants with information from which they may make their own judgments. AHIMA 2007 Audio Seminar Series i Faculty James Richard Campbell, MD is Professor of Internal Medicine at the University of Nebraska Medical Center.
    [Show full text]
  • A Novel Framework for Standardizing and Digitizing Clinical Pathways in Healthcare Information Systems
    Lakehead University Knowledge Commons,http://knowledgecommons.lakeheadu.ca Electronic Theses and Dissertations Electronic Theses and Dissertations from 2009 2020 A novel framework for standardizing and digitizing clinical pathways in healthcare information systems Alahmar, Ayman http://knowledgecommons.lakeheadu.ca/handle/2453/4701 Downloaded from Lakehead University, KnowledgeCommons A Novel Framework for Standardizing and Digitizing Clinical Pathways in Healthcare Information Systems by Ayman Alahmar A thesis presented to Lakehead University in fulfillment of the thesis requirement for the degree of Doctor of Philosophy in Electrical and Computer Engineering Thunder Bay, Ontario, Canada, 2020 © Ayman Alahmar 2020 Examining Committee Membership The following served on the Examining Committee for this thesis. The decision of the Examining Committee is by majority vote. External Examiner: Dr. Carson Kai-Sang Leung Professor, Dept. of Computer Science, University of Manitoba Supervisor: Dr. Rachid Benlamri Professor, Dept. of Software Engineering, Lakehead University Internal Member: Dr. Abdulsalam Yassine Assistant Professor, Dept. of Software Engineering, Lakehead University Internal-External Member: Dr. Salama Ikki Associate Professor, Dept. of Electrical Engineering, Lakehead University ii I hereby declare that I am the sole author of this thesis. This is a true copy of the thesis, including any required final revisions, as accepted by my examiners. I understand that my thesis may be made electronically available to the public. iii Abstract Most healthcare institutions are reorganizing their healthcare delivery systems based on Clinical Pathways (CPs). CPs are medical management plans designed to standardize medical activities, reduce cost, optimize resource usage, and improve quality of service. However, most CPs are still paper-based and not fully integrated with Health Information Systems (HISs).
    [Show full text]