Browse HDD Access

We Make Computers Understand Healthcare

3M can help you to:

Integrate medical terminology standards into your applications
Make the data from all your systems semantically interoperable for exchange, analytics, decision support, alerts and reminders
Comply with quality measures and Meaningful Use requirements specified by ONC and CMS
Minimize terminology development and maintenance costs
Be more efficient and effective in every aspect of your operations where actionable data is needed

HDD on FHIR^®

fhirlogo 400

3M HDD now supports FHIR. Find out more about our FHIR terminology server.

HDD Overview

The 3M Healthcare Data Dictionary (HDD) provides a simplified solution for the translation, standardization and usability of healthcare data. More importantly, it provides knowledge management for clinical decision-making, research, public health, meaningful use, and quality reporting.

Events
Use Cases
Blog
Tips

LOINC International Fall Conference 2019, October 23-25, 2019, Barcelona, Spain

SNOMED CT Expo 2019, October 31-November 1, 2019, Kuala Lumpur, Malaysia

AMIA 2019 Annual Symposium, November 16-20, 2019, Washington, D.C.

HL7 FHIR DevDays, November 20-22, 2019, Amsterdam

Clinical Care Classification (CCC) User Group Seminar, December 4-5, 2019, Nashville, TN

Turn Data Into Intelligence

Bring Order to Chaos

Drive Value from Data

September is Sepsis Awareness Month

What’s for dinner? Creating something meaningful from raw data

Raising the bar: Implementing the latest LOINC release further supports interoperability

What’s new in TEFCA 2

Keeping up with changing technology: The IAB Talks

Why you should consider partnering with academia

Happy 25th to LOINC!

The first nosologists: Classifying disease in 16th century London

LOINC groups: An idea to help searching in LOINC

Terminologies - critical but often deferred in FHIR application development

Focusing on CIMI: Getting the most out of the HL7 Working Group Meeting

Five things I learned from my EHR patient portal

Miles to go on interoperability

TEFCA: A beginning for nationwide interoperability

TEFCA Leaves Privacy Questions Unanswered

A dedication to data interoperability

Teleradiology: More Than a Phone Call

Implementing a FHIR terminology server

What to expect at the HL7 working group meeting: A first timer’s experience

AMIA 2017 Learning Showcase: Terminology-Enabled Clinical Natural Language Processing for Unstructur…

Opioid Crisis: Transitioning Care Through a Paradigm Shift

How I learned HL7 FHIR as a clinician without losing my mind

Advancing informatics: Experiencing AMIA for the first time

Report from the FHIR Connectathon at the HL7: September 2017 Working Group Meeting

Reflections from a laboratory scientist: Terminology’s role in U.S. healthcare paradigm shift

New Additions to ICD-10-CM for Fiscal Year 2020

Staying ahead of the curve: latest LOINC® release changes

Tracking an RxCUI Through Time

Life in the LOINC lane…Keeping up with the latest version

What do you do when anything is possible in terminologies?

A simple tip for mapping Anatomic Pathology in LOINC

Increase your LOINC mapping in 2019

What is a HCPCS level II code?

Understanding LOINC® Groups

How to contribute to SNOMED CT

What is a Map Set?

Mapping Specimens to SNOMED CT

What’s new for the 2019 ICD-10-CM

Parenthesis, Brackets and Braces in LOINC®

Searching for a LOINC® Document Ontology Term

Understanding the LOINC® Document Ontology

When to use LOINC® specialist reviews

The evolution of CPT® code conventions

Ampersand (&) versus the plus (+) sign in LOINC ®

SNOMED CT Browser Hacks

The Challenges of Mapping CPT® to ICD-10-PCS

What is Qualitative Distinction in RxNorm?

There’s Nothing Sexy about Gender in LOINC®

What’s new for the 2018 ICD-10-CM

Working with UCUM