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

3M 2020 Client Experience Summit, July 28-30, 2020, Salt Lake City, UT Postponed

AMIA 2020 Annual Symposium, November 14-18, 2020, Chicago, IL

Turn Data Into Intelligence

Bring Order to Chaos

Drive Value from Data

US Laboratories Respond to the COVID-19 Pandemic

The Women in AMIA Leadership Program: The Art of Self Reflection

Interoperability Planning for 2019 novel Coronavirus Surveillance

Patient privacy and the use of health data for research

The Women in AMIA Leadership Program

Lines of communication: How laboratory ordering can go wrong

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

Why you should consider partnering with academia

What’s new in TEFCA 2

Keeping up with changing technology: The IAB Talks

Happy 25th to LOINC!

The first nosologists: Classifying disease in 16th century London

Terminologies - critical but often deferred in FHIR application development

LOINC groups: An idea to help searching in LOINC

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 Leaves Privacy Questions Unanswered

TEFCA: A beginning for nationwide interoperability

A dedication to data interoperability

Teleradiology: More Than a Phone Call

Implementing a FHIR terminology server

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

Leveraging PHIN VADS to Coordinate SNOMED CT and LOINC in Electronic Public Health Reporting

Let’s get philosophical: Using classical logic exercises to understand mapping

Preventing information overload and making smart choices with interaction design

Quickly Differentiating Drug Product from Substance in SNOMED CT

Keeping up with the Standards

What do you do when anything is possible in terminologies?

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

Handy Example Answers Help Decide LOINC® Scale Attribute

Increase your LOINC mapping in 2019

A simple tip for mapping Anatomic Pathology in LOINC

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 ®