DOCSLIB.ORG

LOINC Users' Guide Version 2.66 (Published June 2019)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
LOINC Users' Guide Version 2.66 (Published June 2019) Logical Observation Identifiers Names and Codes (LOINC®) Users’ Guide Version 2.66 PUBLISHED JUNE 2019 For LOINC Version 2.66 Edited by: Clem McDonald, MD Stan Huff, MD Jamalynne Deckard, MS Sara Armson, MS Swapna Abhyankar, MD Daniel J. Vreeman, PT, DPT, MS Questions and Comments: [email protected] Website: loinc.org COPYRIGHT ©1995-2019 REGENSTRIEF INSTITUTE, INC. AND THE LOGICAL OBSERVATION IDENTIFIERS NAMES AND CODES (LOINC) COMMITTEE. ALL RIGHTS RESERVED. Table of Contents Copyright Notice and License ................................................................................................................ ix Notice of Third Party Content and Copyright Terms ........................................................................................................... xv Required Attributions for Third Party Content not identified as such in the EXTERNAL_COPYRIGHT_ NOTICE field: ....................................................................................................................................................................................... xv 1 Introduction ................................................................................................................................................1 1.1 Acknowledgments ........................................................................................................................................................................ 2 1.2 What is not part of the name .................................................................................................................................................... 3 1.3 Scope of LOINC ............................................................................................................................................................................. 4 2 Major Parts of a LOINC term ...............................................................................................................6 2.1 General naming conventions .................................................................................................................................................... 7 2.1.1 Abbreviations in names of Component (Analyte) ......................................................................................................................... 7 2.1.2 General naming rules for the Component (Analyte) ....................................................................................................................8 2.1.3 Punctuation in Analyte names ............................................................................................................................................................9 2.1.4 Case insensitivity ................................................................................................................................................................................. 10 2.1.5 Roman numerals vs. Arabic numerals .......................................................................................................................................... 10 2.1.6 Exponents ................................................................................................................................................................................................ 10 2.1.7 Use of the slash (/) ................................................................................................................................................................................ 10 2.1.8 Use of curly braces {} in LOINC names ......................................................................................................................................... 11 2.2 Component/Analyte (1st part) .................................................................................................................................................11 2.2.1 Analyte name (1st subpart) ............................................................................................................................................................... 11 2.2.2 Challenge test (2nd subpart) ............................................................................................................................................................. 13 2.2.3 Adjustments/corrections (3rd subpart) ........................................................................................................................................ 18 2.2.4 Distinguishing multiple values for any test via the test name (4th subpart) ................................................................ 18 2.3 Kind of Property (also called kind of quantity) (2nd part) ............................................................................................18 2.3.1 Quantitative Properties .......................................................................................................................................................................19 2.3.2 Qualitative Properties ..........................................................................................................................................................................21 2.3.3 More examples of LOINC Properties .............................................................................................................................................21 2.4 Time Aspect (point or moment in time vs. time interval) (3rd part) ..........................................................................26 2.4.1 Time Aspect Modifier ........................................................................................................................................................................... 28 2.5 System (sample) type (4th part) ..............................................................................................................................................28 2.5.1 Special issues related to XXX as a System ...................................................................................................................................30 2.5.2 Super System (2nd subpart) ............................................................................................................................................................... 31 2.6 Type of Scale (5th part) ..............................................................................................................................................................31 2.6.1 Quantitative (Qn) ................................................................................................................................................................................. 32 2.6.2 Ordinal (Ord) .......................................................................................................................................................................................... 32 2.6.3 Quantitative/Ordinal (OrdQn) ....................................................................................................................................................... 32 LOINC USERS’ GUIDE • JUNE 2019 ii 2.6.4 Nominal (Nom) ...................................................................................................................................................................................... 33 2.6.5 Narrative (Nar) ...................................................................................................................................................................................... 33 2.6.6 Multi .......................................................................................................................................................................................................... 33 2.6.7 Document (Doc) .................................................................................................................................................................................... 33 2.7 Type of Method (6th part) ........................................................................................................................................................34 2.7.1 Methods for identifying nucleic acids .......................................................................................................................................... 35 2.7.2 Immune assays ...................................................................................................................................................................................... 37 2.7.3 Immunoblot and Line blot Methods ...............................................................................................................................................38 2.7.4 Coagulation ............................................................................................................................................................................................ 38 2.7.5 Stains ......................................................................................................................................................................................................... 38 2.7.6 Substrates used to measure enzyme activity............................................................................................................................ 38 2.7.7 “Detection limit” Methods .................................................................................................................................................................39 2.7.8 “Confirm”Method outside of Drug/Tox .......................................................................................................................................
Load more

Recommended publications
  • A Method for Constructing a New Extensible Nomenclature for Clinical Coding Practices in Sub-Saharan Africa
    MEDINFO 2017: Precision Healthcare through Informatics 965 A.V. Gundlapalli et al. (Eds.) © 2017 International Medical Informatics Association (IMIA) and IOS Press. This article is published online with Open Access by IOS Press and distributed under the terms of the Creative Commons Attribution Non-Commercial License 4.0 (CC BY-NC 4.0). doi:10.3233/978-1-61499-830-3-965 A Method for Constructing a New Extensible Nomenclature for Clinical Coding Practices in Sub-Saharan Africa Sven Van Laere, Marc Nyssen, Frank Verbeke Department of Public Health (GEWE), Research Group of Biostatistics and Medical Informatics (BISI), Vrije Universiteit Brussel (VUB), Laarbeeklaan 103, 1090 Brussels, Belgium Abstract The word nomenclature has to be used with care in the context Clinical coding is a requirement to provide valuable data for of sub-Saharan Africa. By the word “nomenclature”, usually billing, epidemiology and health care resource allocation. In they understand: “a coding system to provide codes that are sub-Saharan Africa, we observe a growing awareness of the used in invoices, to specify the health services that were pro- need for coding of clinical data, not only in health insurances, vided for particular patients”. We define nomenclature in a but also in governments and the hospitals. Presently, coding broader way, also taking into account the clinical definition of systems in sub-Saharan Africa are often used for billing pur- health services. poses. In this paper we consider the use of a nomenclature to In this paper we will present a way to build this new nomen- also have a clinical impact.
    [Show full text]
  • Healthcare Terminologies and Classifications
    Healthcare Terminologies and Classifications: An Action Agenda for the United States American Medical Informatics Association and American Health Information Management Association Terminology and Classification Policy Task Force Acknowledgements AHIMA and AMIA Terminology and Classification Policy Task Force Members Keith E. Campbell, MD, PhD The American Health Chair, AHIMA and AMIA Terminologies and Classifications Policy Task Force Information Management Chief Technology Officer, Informatics, Inc., and Assistant Clinical Professor; Association (AHIMA) is the Department of Medical Informatics and Clinical Epidemiology, Oregon Health and premier association of health Science University information management Suzanne Bakken, RN, DNSc, FAAN (HIM) professionals. AHIMA’s Alumni Professor of Nursing and Professor of Biomedical Informatics School of 51,000 members are dedicated to Nursing and Department of Medical Informatics, Columbia University the effective management of personal health information Sue Bowman, RHIA, CCS needed to deliver quality Director of Coding Policy and Compliance, American Health Information healthcare to the public. Management Association Founded in 1928 to improve the quality of medical records, Christopher Chute, MD, PhD AHIMA is committed to Professor and Chair of Biomedical Informatics, Mayo Foundation advancing the HIM profession in an increasingly electronic and Don Detmer, MD, MA President and Chief Executive Officer, American Medical Informatics Association global environment through leadership in advocacy, Jennifer Hornung Garvin, PhD, RHIA, CPHQ, CCS, CTR, FAHIMA education, certification, and Medical Informatics Postdoctoral Fellow Center for Health Equity Research and lifelong learning. To learn more, Promotion, Philadelphia Veterans Administration Medical Center go to www.ahima.org. Kathy Giannangelo, MA, RHIA, CCS, CPHIMS Director, Practice Leadership, AHIMA Gail Graham, RHIA The American Medical Director, Health Data and Informatics Department of Veterans Affairs Informatics Association (AMIA) Stanley M.
    [Show full text]
  • Health & Coding Terminological Systems
    Health & Coding Terminological Systems Hamideh Sabbaghi, MS Ophthalmic Research Center, Shahid Beheshti University of Medical Sciences, Tehran, Iran Definition of Code Code is considered as word, letter, or number which has been used as passwords instead of words or phrases. Coding System 1. Classification system 2. Nomenclature system Classification System A well-known system of corrections for naming different stages of the disease. Nomenclature System A medical list of a specific system of preferred terms for naming disease. WHO- FIC • Main/reference classification • Related classifications to the main/ reference classification • Driven classification from the main/ reference classification Main/reference classification • ICD- 10 (1990, WHA) • ICD- 11 (2007, WHO) • http://who.int/classifications/apps/icd/icd10online/ ICD with a commonest usage can be used for: • Identification of health trend, mortality and morbidity statistics. • Clinical and health research purposes. Main/reference classification • ICD-9-CM (International Classification of Diseases, Ninth Revision, Clinical Modification) • ICF (International Classification of Function, Disability and Health) • ICHI (International Classification of Health Intervention) Related classifications to the main/ reference classification • ATC/DDD (The Anatomical Therapeutic chemical classification system with Defined Daily Doses) • ATCvet (The Anatomical Therapeutic Chemical Classification System for veterinary medicinal products) • ICECI (International Classification of External Causes
    [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]
  • Clinical Vocabularies for Global Real World Evidence (RWE) | Evidera
    Clinical Vocabularies for Global RWE Analysis Don O’Hara, MS Senior Research Associate, Real-World Evidence, Evidera Vernon F. Schabert, PhD Senior Research Scientist, Real-World Evidence, Evidera Introduction significant volume of real-world evidence (RWE) analyses continue to be conducted with data A repurposed from healthcare administrative Don O’Hara Vernon F. Schabert databases. The range of sources represented by those databases has grown in response to demand for richer description of patient health status and outcomes. information for improved quality and coordination Data availability, including the range of available data of care, often using standardized messaging systems sources, has grown unevenly across the globe in response such as Health Level 7 (HL7). These messages are to country-specific market and regulatory dynamics. only as good as the standardization of codes between Nonetheless, as demand globalizes for RWE insights from message senders and receivers, which motivates the databases, those demands increase pressure on analysts encoding of facts using common code sets. The second to find ways to bridge differences between local data is the increased availability of common data models to sources to achieve comparable insights across regions. standardize the extraction and analysis of these data for RWE and drug safety purposes. While common data One of the challenges in bridging differences across models make compromises on the structure of tables databases is the codes used to represent key clinical and fields extracted from healthcare systems such as facts. Historically, RWE database studies have leveraged electronic medical records (EMR) and billing systems, local code sets for cost-bearing healthcare services they can improve consistency and replicability of analyses such as drugs, procedures, and laboratory tests.
    [Show full text]
  • Ministry of Labour, Health and Social Affairs of Georgia
    WWW.MOH.GOV.GE Ministry of Labour, Health and Social Affairs of Georgia Georgia Health Management Information System Strategy “Healthy Georgia, Connected to You” 2011 Table of Contents Executive Summary . 5 Goals and Objectives. 6 Governance. 7 Operational.Aspects. 9 HMIS Standards. .10 Message.Standards. .10 Vocabulary.Standards.for.Medical.Care. .11 Diagnosis.-.ICD.10,.Medcin. .12 Treatments.-.CPT. .13 Drugs.–RXNorm,.Multum,.Medispan,.First.Data.Bank. .13 Lab.–.LOINC,.SNOMED . .13 Administrative.Standards . .13 Citizens/Patients. .14 Provider.Credentialing,.Licensing.and.Unique.Identifiers. .14 National.Drug.Database . .14 Health.Data.Dictionary . .14 HMIS.Key.Indicators.and.Metrics. .15 HMIS.Core.Data.Sets. .15 HMIS Functionality . .16 Overview. .16 What.is.not.an.HMIS.component . .19 Software.Acquisition.versus.Development. .19 Selective.review.of.relevant.systems.that.are.already.available.in.Georgia . .23 Hesperus . .23 Vaccinations.system . .23 Electronic.registration.for.births.and.deaths.system. .23 TB.system,.AIDS.system,. .23 Surveillance.system.(DETRA).–.Infectious.Disease. .24 EU.project.for.MD’s.in.villages.to.be.equipped.with.400.PC’s . .24 SIMS. .24 Electronic Medical Record (EMR) . .25 Personal.and.Health.Information. .26 Results.Management. .26 Order.Management. .26 Decision.Support. .26 Reporting . .26 Electronic.Communication.and.Connectivity. .26 Patient.Support . .27 Administrative.Processes . .28 3 Financial Information System Functionality. .29 Georgian Health Data Repository (GHDR) . .32 Populating.the.Georgian.Health.Data.Repository.(GHDR) . .33 Extract,.Transform.Load. .34 Data.Domains.(Categories). .34 Data.Analysis.and.Presentation. .35 Reporting . .35 Dashboards . .36 GHDR.Uses. .36 Georgian.Healthcare.Statistics. .36 Monitoring.Healthcare.Costs. .36 Public.Health.Surveillance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ...36 Decision.Support:..Improving.Patient.Care .
    [Show full text]
  • Ata Lements for Mergency Epartment Ystems
    D ata E lements for E mergency D epartment S ystems Release 1.0 U.S. DEPARTMENT OF HEALTH AND HUMAN SERVICES CDCCENTERS FOR DISEASE CONTROL AND PREVENTION D ata E lements for E mergency D epartment S ystems Release 1.0 National Center for Injury Prevention and Control Atlanta, Georgia 1997 Data Elements for Emergency Department Systems, Release 1.0 (DEEDS) is the result of contributions by participants in the National Workshop on Emergency Department Data, held January 23-25, 1996, in Atlanta, Georgia, subsequent review and comment by individuals who read Release 1.0 in draft form, and finalization by a multidisciplinary writing committee. DEEDS is a set of recommendations published by the National Center for Injury Prevention and Control of the Centers for Disease Control and Prevention: Centers for Disease Control and Prevention David Satcher, MD, PhD, Director National Center for Injury Prevention and Control Mark L. Rosenberg, MD, MPP, Director Division of Acute Care, Rehabilitation Research, and Disability Prevention Richard J. Waxweiler, PhD, Director Acute Care Team Daniel A. Pollock, MD, Leader Production services were provided by the staff of the Office of Communication Resources, National Center for Injury Prevention and Control, and the Management Analysis and Services Office: Editing Valerie R. Johnson Cover Design and Layout Barbara B. Lord Use of trade names is for identification only and does not constitute endorsement by the U.S. Department of Health and Human Services. This document and subsequent revisions can be found at the National Center for Injury Prevention and Control Web site: http://www.cdc.gov/ncipc/pub-res/deedspage.htm Suggested Citation: National Center for Injury Prevention and Control.
    [Show full text]
  • LOINC®: a Universal Catalogue of Individual Clinical Observations and Uniform Representation of Enumerated Collections
    Int. J. Functional Informatics and Personalised Medicine, Vol. 3, No. 4, 2010 273 LOINC®: a universal catalogue of individual clinical observations and uniform representation of enumerated collections Daniel J. Vreeman* Indiana University School of Medicine, 410 W. 10th Street, Suite 2000, Indianapolis, IN 46202, USA and Regenstrief Institute, Inc, 410 W. 10th Street, Suite 2000, Indianapolis, IN 46202, USA E-mail: [email protected] *Corresponding author Clement J. McDonald Lister Hill National Centre for Biomedical Communications, National Library of Medicine, National Institutes of Health, 8600 Rockville Pike, Bldg. 38-A, Rm. 7N704, Bethesda, MD 20894, USA E-mail: [email protected] Stanley M. Huff University of Utah, 26 South 2000 East, Room 5775 HSEB, Salt Lake City, UT 84112, USA and Intermountain Healthcare, 4646 W. Lake Park Blvd., Salt Lake City, UT 84120, USA E-mail: [email protected] Abstract: In many areas of practice and research, clinical observations are recorded on data collection forms by asking and answering questions, yet without being represented in accepted terminology standards these results cannot be easily shared among clinical care and research systems. LOINC contains a well-developed model for representing variables, answer lists and the collections that contain them. We have successfully added many assessments and other collections of variables to LOINC in this model. By creating a uniform representation and distributing it worldwide at no cost, Copyright © 2010 Inderscience Enterprises Ltd. 274 D.J. Vreeman et al. LOINC aims to lower the barriers to interoperability among systems and make this valuable data available across settings when and where it is needed.
    [Show full text]
  • Ehealth Standardisation in the Nordic Countries
    eHealth standardisation in the Nordic countries Technical and partially semantics standardisation as a strategic means for realising national policies in eHealth eHealth standardisation in the Nordic countries Technical and partially semantics standardisation as a strategic means for realising national policies in eHealth Thor Schliemann, Camilla Danielsen, Teemupekka Virtanen, Riikka Vuokko, Gudrun Audur Hardardottir, Magnus Andre Alsaker, Bjarte Aksnes, Niklas Eklöf and Erika Ericsson TemaNord 2019:537 eHealth standardisation in the Nordic countries Technical and partially semantics standardisation as a strategic means for realising national policies in eHealth Thor Schliemann, Camilla Danielsen, Teemupekka Virtanen, Riikka Vuokko, Gudrun Audur Hardardottir, Magnus Andre Alsaker, Bjarte Aksnes, Niklas Eklöf and Erika Ericsson ISBN 978-92-893-6218-4 (PDF) ISBN 978-92-893-6219-1 (EPUB) http://dx.doi.org/10.6027/TN2019-537 TemaNord 2019:537 ISSN 0908-6692 Standard: PDF/UA-1 ISO 14289-1 © Nordic Council of Ministers 2019 This publication was funded by the Nordic Council of Ministers. However, the content does not necessarily reflect the Nordic Council of Ministers’ views, opinions, attitudes or recommendations Cover photo: unsplash.com Disclaimer This publication was funded by the Nordic Council of Ministers. However, the content does not necessarily reflect the Nordic Council of Ministers’ views, opinions, attitudes or recommendations. Rights and permissions This work is made available under the Creative Commons Attribution 4.0 International license (CC BY 4.0) https://creativecommons.org/licenses/by/4.0. Translations: If you translate this work, please include the following disclaimer: This translation was not pro- duced by the Nordic Council of Ministers and should not be construed as official.
    [Show full text]
  • Advancing Nursing Terminology ONC Annual Meeting 2017 Panelists
    Advancing Nursing Terminology ONC Annual Meeting 2017 Panelists • CAPT Alicia A. Morton, DNP, RN-BC, Director, Health IT Certification Program, ONC • Susan Matney, PhD, RNC-OB, FAAN, FACMI, Consultant Medical Informaticist, Intermountain Healthcare • Greg Springan, BSN, RN, Clinical Informatics, Epic • Nikki VandeGarde, BSN, RN-BC, Director of Platform Development, Cerner • Michelle R. Troseth, MSN, RN, FNAP, FAAN, President, National Academies of Practice 2 National Interoperability Standards Susan Matney, PhD, RNC-OB, FAAN, FACMI https://www.healthit.gov/standards-advisory/draft-2017 Interoperability Need: Representing Nursing Assessments Standards Standard/Implementation Process Implementation Adoption Federally Test Tool Type Specification Maturity Maturity Level Required Cost Availability Standard for Feedback LOINC rrr® Final Production No Free N/A obsen·ations requested Standard for Feedback obsen·ation SNO:l\.1ED CT® Final Production No Free N/A requested values Limitations, Dependencies, and Preconditions for Applicable Value Set(s) and Starter Set(s): Consideration: • Assessments are represented as question/answer (name/value) • Feedback requested pairs. They are not represented in other terminologies. • LOINC® should be used for the as-sessment/observation questions and SNOMED CT® for the assessment/observation answers (value sets, choice lists). • See LOINC proj ects in the Interoperability Proving Ground Interoperability Need: Representing Nursing Interventions Standards Standard/Implementation Process Implementation Adoption
    [Show full text]
  • Aligning an Administrative Procedure Coding System with SNOMED CT
    Aligning an Administrative Procedure Coding System with SNOMED CT a,c,1 a a Stefan SCHULZ , Johannes STEFFEL , Peter POLSTER , b a Matvey PALCHUK and Philipp DAUMKE a Averbis GmbH, Freiburg, Germany b TriNetX, Cambridge, MA, USA c Institute for Medical Informatics, Statistics and Documentation, Medical University of Graz, Austria Abstract. OPS, the German coding system for therapeutic and diagnostic procedures, is a large and complex classification system. Its main purpose is to provide codes for billing. Like other systems of this type (e.g. ICD-10) it follows the principle of class disjointness and exhaustiveness. SNOMED CT, on the other hand, aims at providing standardised terms, together with logic-based descriptions, and pursues the goal to make the electronic health record (EHR) computable and interoperable across languages and jurisdictions. We investigated the feasibility of aligning OPS with SNOMED CT, based on the 1000 most frequently used OPS codes. A team of three terminologists performed the mapping (partially overlapping), using the first hundred codes to determine guidelines. From the work, which is currently being extended, we can draw the following conclusions: (i) for less than half of the OPS codes, a semantically equivalent SNOMED CT code can be found; (ii) many maps require SNOMED CT post-coordination but remain approximate; (iii) the mapping work is impaired by imprecise descriptions in either terminology system. Keywords. Medical Procedures, Medical Classifications, SNOMED CT 1. Introduction Most artefacts that provide a semantic reference – generically referred to as terminology systems [1, 2] – for the organisation of biomedical data are restricted to a well-defined scope regarding the types of referents these data denote.
    [Show full text]
  • Common Semantic Strategy for Health in the European Union WP8 Integration in National Policies and Sustainability Draft
    D8.2.2 Common Semantic Strategy for Health in the European Union WP8 Integration in National Policies and Sustainability Draft Revision 1.4, 10-05-2019 15th eHN meeting, June 2019 For Discussion Grant Agreement nº 801558 D8.2.2 Common Semantic Strategy WP8 Integration in National Policies and Sustainability Draft for Discussion Revision 1.4, 10-05-2019 CONTROL PAGE OF DOCUMENT Document name CSS for Health in the EU – Information paper for eHN Status Draft Author(s) Country Organisation Name Austria Sozial Ministerium Peter Brosch Croatia HZZO Vesna Kronstein Kufrin Czech Republic MoH Czech Republic Hynek Kruzik Estonia HWISC Kerli Linna Finland THL Mikko Härkönen Germany DIMDI Stefanie Weber Hungary AEEK Gergely Heja Eamon Coyne; Ireland HSE Theresa Barry Lithuania LMB Martynas Bieliauskas Netherlands NICTIZ Pim Volkert Norway EHELSE Jostein Vein MoH Poland Hubert Zycinski; Poland CZIOZ Ania Ostrowicka Henrique Martins; Diogo Martins; Jurgen Wehnert; Lilia Marques; Cristiana Antunes; Filipa Rasquinho; Portugal SPMS Daniela Costa; Filipe Mealha; Joana Cunha; Carla Pereira; Anabela Santos; Anderson do Carmo Slovenia NIJZ Lucija Tepej-Jocic Arturo Romero Gutiérrez; Spain MoH Spain Miguel Pedrera Jiménez Sweden Socialstyrelsen Daniel Karlsson 2/31 eHAction – Joint Action supporting the eHealth Network - www.ehaction.eu D8.2.2 Common Semantic Strategy WP8 Integration in National Policies and Sustainability Draft for Discussion Revision 1.4, 10-05-2019 REVISION HISTORY Revision Date Author Description Daniel Karlsson; Stefanie Weber; Mikko Härkönen; Vesna Kronstein Kufrin; Hynek st 0.1 11/02/2019 Kruzik; Hubert Zycinski; Kerli Linna 1 draft document Input of new content. 0.2 25/02/2019 Carla Pereira; Daniela Costa; Lucija Tepej-jocic Comments on the Document 0.3 05/03/2019 Arturo Romero; Jurgen Wehnert Comments on the Document Peter Brosch; Hynek Kruzik;Daniel Karlsson; Input of new content.
    [Show full text]