Unit Six

Health Data Standards

Jan 2023
 Objectives
•V
 Outlines
❑ Data Interchange (exchange of data between organization
nationally or internationally electronically)
❑ Relationship between ICD and other coding terminology
databases
❑ Mapping ICD to SNOMED
❑ Using the Terminology and Classification Systems
❑ Health and health related data standards and their classification
❑ Terms used in health and health related data exchange
❑ Terminologies used in working with database and data mapping
 Electronic Data Interchange (EDI) Between
Organization
What is EDI?
❑ EDI is the concept of electronically communicating information
that was traditionally communicated on paper, such as purchase
orders, advance ship notices, and invoices.
❑ Is the exchange of electronic data between companies using
computers
❑ Is a two way information exchange that is fast, accurate, and
completely paperless.
❑ Set of hardware, software, and standards that accommodate the
EDI process
 Electronic Data Interchange …
❑ Technical standards for EDI exist to facilitate parties transacting
such instruments without having to make special arrangements.
❑ Types of data sent via EDI include
• Purchase order data
• Shipping data
• Invoice data
• Product description data
• Price list data
• Insurance data
• Computer-processable healthcare data
 Electronic Data Interchange …

Figure : Suppliers, manufacturers, and retailers cooperate in some

of the most successful applications of EDI.
 EDI Standards
❑ EDI standards are formats for EDI documents that specify what
information goes where within an EDI document.
❑ These standards include:
▪ X12 EDI standards- developed by a standard’s organization
called Accredited Standards Committee X12 (also known as
ASC X12)
▪ The Voluntary Inter-industry Commerce Standard (VICS)
▪ United Nations/Electronic Data Interchange for Administration,
Commerce and Transport (UN/EDIFACT)
▪ The Health Insurance Portability and Accountability Act (HIPAA)
- was enacted in 1996. to the establishment of national
standards for electronic healthcare transactions and national
identifiers for providers, health insurance plans and employers.
 EDI Standards
❑ There are two types of EDI standards:
▪ Proprietary (non-public or private) standard - EDI standard developed for
a specific company or industry. This is also called a non-public or private
standard.
▪ Public standard - EDI standard developed for use across one
or more industries

BACK
 Advantages of EDI
❑ Worldwide connectivity
❑ Emergence of standards and guidelines
❑ Greater reliability of information technology
❑ Globalization of organizations
❑ Need for timely, reliable data exchange in response to
rapidly changing markets
❑ Increased productivity: More efficient personnel and faster
throughput
❑ Faster trading cycle: Streamlined processes for improved
trading relationships
❑ Lower operating costs: Saves time and money
❑ Less errors, more accuracy, no data entry, so less human error
 Advantages of EDI
❑ Low speed
❑ Poor security
❑ Organizational participation
❑ Technical problems must be solved
❑ Can be expensive for small businesses to implement.
❑ There are various standard document formats for EDI that can
cause problems with cross compatibility.
 EDI in Healthcare
❑ According to the 2021 The Council for Affordable Quality
Healthcare® (CAQH) Index Report, the healthcare industry
can save $20 billion by transitioning to fully electronic
transactions.
❑ Healthcare EDI software not only saves money and
streamlines transactions, but it also ensures the security and
safety of sensitive data.
 EDI in Healthcare…
How Does Healthcare EDI Work?
❑ Let us use an inquiry from a medical provider to a payer as an
example and see how EDI works in healthcare:
▪ The medical provider initiates the inquiry by supplying specific
data, like member ID number and date of birth.
▪ The inquiry goes to a clearinghouse contracted by the provider.
▪ The clearinghouse sends the inquiry to the payer.
▪ The payer responds to the clearinghouse.
▪ The clearinghouse transmits the response to the medical provider.
❑ All involved parties transmit the information using codes laid out in
ASC X12, the general standard that governs all EDI transaction
codes, including electronic healthcare transactions.
 Relationship Between ICD and Other
Coding Terminology Databases
❑ A standard EHR will allow for interoperable health data exchange.
❑ Interoperability or the sharing of healthcare data greatly improves
the effectiveness of clinical care through
▪ improved availability and access to patient-specific health information and use
of decision support models),
▪ cost-effectiveness and value of research,
▪ the safety of patient care,
▪ public health monitoring, etc.
❑ Interoperability requires the use of uniform health information
standards.
❑ The lack of standards for health information has been a key barrier
to electronic connectivity in healthcare.
 Relationship Between ICD …
❑ Incorporation of clinical terminologies, such as SNOMED-CT, into EHR
systems is an important step in the creation of information systems.
❑ A standard clinical terminology provides standardization of clinical
terms, thus supporting easy transmission of patient data across
information systems.
❑ The use of clinical practice guidelines and other decision support
tools to enhance the quality of healthcare depends on the use of
common terms and concepts in health records and knowledge
resources.
 Relationship Between ICD …
❑ Together, standard clinical terminologies (such as SNOMED-CT) and
classifications (such as ICD-10) represent a common medical
language that allows clinical data to be shared between EHR
systems.
❑ Therefore, standard clinical terminologies and classifications, with
maps linking them, must be incorporated into EHR systems to achieve
system interoperability and the benefits of a national health
information infrastructure.
 Relationship Between ICD …
❑ SNOMED-CT is designed for use in electronic, not paper-based,
health record systems.
❑ SNOMED-CT codes will be embedded in EHR systems and will work
behind the scenes to encode the clinical information recorded in the
health record.
❑ It would be impractical to attempt to manually assign SNOMED-CT
codes.
❑ The number of terms and level of detail represented in a reference
terminology cannot be effectively managed without automation.
 Relationship Between ICD …
❑ Designed to support the EHR, SNOMED-CT enables:
• The development of computer-aided clinical decision support
systems (CDSS)
• Critical care monitoring (e.g., standardized capture of clinical
details such as vital signs, signs/symptoms, medications,
interventions, tests, and problem lists)
• The development of clinical alert and reminder systems
• Improved communication among clinicians
• Use in computerized physician order entry (CPOE) systems
• Advancements in disease management programs
• The practice of evidence-based medicine.
• Etc.
 Relationship Between ICD …
❑ In the same way as the clinical terminologies, disease classification
systems (such as ICD systems), are necessary to capture and
effectively use the breadth and depth of clinical data in an EHR
❑ Both terminologies and classifications are necessary to satisfy
varying intended purposes or applications, and user groups.
❑ The desired characteristics of a terminology or classification vary
with the intended purpose(s) of each system.
❑ Standardized terminologies, such as SNOMED-CT, facilitate
electronic data collection at the point of care (i.e., an input system);
retrieval of relevant data, clinical concepts, information, and
knowledge; and data reuse for multiple purposes, including
automated surveillance, CDSS, and quality and cost monitoring.
 Relationship Between ICD …
❑ Since SNOMED-CT is intended as an input system, it does not work
well as an interface terminology (a type of terminology used for
presentation to end users) or for the administrative purposes
▪ ICD (and other classification systems) complement the
standardized terminologies as they are designed for end-user
presentations and administrative purposes
▪ As a result, classification systems are used to meet reimbursement
and other external reporting requirements; whereas, the clinical
terminologies are used for clinical care processes and patient
care.
 Using the Terminology and
Classification Systems
❑ Classification systems such as ICD (ICD-9-CM, ICD-10-CM, ICD-10-
PCS) represent abstractions and combinations of clinical concepts
that are designed to support non-clinical documentation needs, such
as reimbursement or regulatory reporting.
❑ Classification systems do not work well as an interface or reference
terminology because they lack granularity, fail to define individual
concepts and their relationships, and have complex rules for code
selection.
❑ The clinical content coverage of classifications is not as
comprehensive as that of terminologies because classifications are
not intended to represent the complete clinical content of a health
record.
 Using…
❑ The ICD system was not intended or designed for the primary
documentation of clinical care.
❑ The ICD system is output, not an input coding system.
❑ Classification systems are intended for secondary data uses,
including measurement of quality of care, reimbursement, statistical
and public health reporting, operational and strategic planning,
and other administrative functions.
❑ For example, in ICD-10, a hospital stay for a newborn is
represented by codes identifying the type of birth
 Using…
❑ In contrast, SNOMED-CT codes would describe the complete clinical
detail for the healthcare encounter.
❑ There are more than 40 unique concepts for “chest pain” in
SNOMED-CT.
❑ In contrast, the ICD-10 classifies all types of chest pain into five
codes.
❑ Together, terminologies, such as SNOMED-CT, and classification
systems, such as ICD-10-CM and ICD-10-PCS, provide the common
medical language necessary for interoperability and the effective
sharing of clinical data.
❑ ICD systems and SNOMED CT can work in tandem as a powerful duo.
 Using…
❑ To maximize the value of health information, classifications and
terminologies should be used appropriately according to their
purpose(s) and design.
❑ Instead of selecting a single classification or terminology to serve all
clinical data functions, multiple classifications and terminologies
should be used for those functions for which they are ideally suited,
and they should be coordinated.
❑ For example, if a highly granular terminology, such as SNOMED-CT,
is used to standardize data capture in an EHR, it should be mapped
to a broader classification system, such as ICD-10 or its successor
for statistical, reimbursement, and other purposes.
 Mapping ICD to SNOMED-CT
❑ Multiple terminologies that have different purposes and that
represent concepts in different ways can work together in harmony
in an EHR via mappings and algorithms.
❑ When terminologies are integrated, one terminology is actually
embedded in another terminology.
❑ Mapping provides a linkage between multiple terminologies or
between terminologies and classifications by identifying the related
term(s) or concept(s) in each system.
❑ Mapping is the process of linking content from one terminology to
another or to a classification.
 Mapping ICD to SNOMED-CT…
❑ Maps result in an expression of the relationships between the
terminologies or classification systems involved.
❑ Mapping requires deciding how concepts in different terminologies
match, are similar, or differ.
❑ It provides a link between terminologies and classifications to:
▪ Use data collected for one purpose for another purpose
▪ Retain the value of data when migrating to newer database
formats and schemas
▪ Avoid entering data multiple times and the associated risk of
increased cost and errors
 Mapping ICD to SNOMED-CT…
❑ Maps result in an expression of the relationships between the
terminologies or classification systems involved.
❑ Mapping requires deciding how concepts in different terminologies
match, are similar, or differ.
❑ It provides a link between terminologies and classifications to:
▪ Use data collected for one purpose for another purpose
▪ Retain the value of data when migrating to newer database
formats and schemas
▪ Avoid entering data multiple times and the associated risk of
increased cost and errors
 Mapping ICD to SNOMED-CT…
❑ Creation of a map generally involves an automated translation
software engine.
❑ The mapping process employs a standard method in which the
terminology context or classification description principles are
interpreted between systems.
❑ It begins with the development of heuristics (rules of thumb used for
solving problems) and guidelines that support the use case or
purpose of the map, respecting the conventions of the source and
target to preserve the granularity and flexibility of both.
❑ Defined mapping rules must be developed and consistently applied
to minimize incompatibilities without compromising clinical integrity.
 Mapping ICD to SNOMED-CT…
❑ Because terminologies have different structures and intended uses,
cross-mapping does not necessarily involve one-to-one relationships.
❑ There can also be many-to-one and one-to-many relationships, as
well as concepts that are not mappable because the concept only
exists in the source or target terminology.
❑ Through mapping and integration, SNOMED-CT is linked with other
terminologies or classifications so that:
• Healthcare data collected for one purpose can be used for
another purpose
• Data can be more easily migrated to newer database formats
and schemas
• Data can be entered once and reused, avoiding multiple data
entry and reducing the risk of higher cost and errors.17
 Mapping ICD to SNOMED-CT…
❑ Clinical data captured at the point of care can be efficiently and
effectively used for administrative purposes such as vital and health
statistics trending, health policy decision-making, and
reimbursement.
❑ Driven by a philosophy of “code once, use many times,” after clinical
care is recorded in an EHR using SNOMED-CT, mapping tables can
be used to identify the related code(s) in ICD.
❑ This process allows data encoded in SNOMED-CT to be
aggregated into smaller groupings for data reporting and analysis.
❑ Mapping from the reference terminology to classification systems
avoids duplicate data capture, while facilitating enhanced health
reporting, billing, and statistical analysis.
 Mapping ICD to SNOMED-CT…
❑ While maps are always subject to human review, the goal is to
automate as much of the mapping process as possible using a rules-
based approach.
❑ Standardized encoded data can be extracted from EHRs to classify
the information (i.e., through mapping).
❑ The SNOMED-CT to ICD-10 map consists of correlates between
SNOMED-CT concepts in the disease and general patient-finding
hierarchies and the closest ICD-10 target code or codes.
❑ The map provides users with an approximation of the closest ICD
code(s).
❑ Since SNOMED-CT’s scope of content is much broader than ICD, less
than 30% of the content of SNOMED-CT can be mapped to ICD.
 Mapping ICD to SNOMED-CT…
❑ The use of a map from SNOMED-CT to ICD will allow clinical
information captured at a very granular level to be aggregated for
reporting and statistical analysis purposes.
❑ Mapping a reference terminology to modern classification systems:
▪ Decreases administrative costs
▪ Decreases time in revenue cycle
▪ Increases specificity and accuracy of data
▪ Maintains comparable data.
 Mapping ICD to SNOMED-CT…
❑ Mapping between SNOMED-CT and ICD is an imperfect science.
❑ It is very difficult to adequately represent some of the ICD coding
conventions for a computer’s purposes. The codes produced by the
crossmap will need to be evaluated in the context of the complete
medical record and applicable reporting rules and reimbursement
requirements before being submitted to payers and other external
entities.
 Mapping from
SNOMED CT to ICD-10
and ICD-10-CM

Dr. Kin Wah Fung

U.S. National Library of Medicine,
Bethesda, MD, USA
Background
• SNOMED CT is inherently more suitable for clinical documentation in
an Electronic Health Record (EHR)
• Content coverage
• Clinical orientation
• Flexible data entry and retrieval
• Extensibility
• Requirements for ICD-10 (mortality report to WHO) and ICD-10-CM
(reimbursement starting Oct 2013) codes have a strong influence on
EHR development
• A map from SNOMED CT to ICD will promote the use of SNOMED CT
for clinical documentation while allowing the generation of
administrative codes
• Other potential benefits: improve speed and quality of ICD coding
Two mapping projects
• Mapping SNOMED CT to ICD-10
• Joint effort between IHTSDO and WHO
• International participation (including USA, UK, Canada, Sweden,
Australia, and New Zealand)
• Funded by IHTSDO with a lot of volunteer contribution
• Mapping SNOMED CT to ICD-10-CM
• Led by NLM with direct involvement from National Center for Health
Statistics (NCHS)
• Methodology and tools – based on ICD-10 Map project
• A lot of overlap between the 2 projects – people,
methodology, tooling, mapping data
Rule-based mapping
At run-time Final map
resolve to

• Map group 1
• Rule 1 → target code 1
• Rule 2 → target code 2 code1
• Map group 2
• Rule 1 → target code 3 Codes 1 + 4 +6
• Rule 2 → target code 4
code4
• Map group 3
• Rule 1 → target code 5
• Rule 2 → target code 6
code6

www.ihtsdo.org
1
 Multiple ICD codes – dagger and asterisk

• Source concepts which map to ICD chapters with asterisk

conventions will be mapped to two target codes.
• The asterisk classification will always be the second map
group

Source concept: 111900000 Pneumonia in aspergillosis

(disorder)
Map group 1
Rule 1 → B44.1 Other pulmonary aspergillosis
Map group 2
Rule 1 → J17.2 Pneumonia in mycoses
 Multiple ICD codes – External causes

• The source concepts denoting a condition with an identifiable cause

within scope of ICD-10 chapter XX(20) will be mapped to two
target codes.
• The external cause code will be assigned to the second target
record.

Source concept: 242012005 Thermal burns from lightning (disorder)

:
Map group 1
Rule 1 → T30.0 Burn of unspecified region
Map group 2
Rule 1 → X33 Victim of lightning
Map rule – gender
• Source concept: 8619003 Infertile (finding)
• Map group 1
• Rule 1 IFA 1086007| FEMALE (FINDING) | → N97.9
Female infertility, unspecified
• Rule 2 IFA 248153007 | MALE (FINDING) | → N46
Male infertility
• Rule 3 OTHERWISE TRUE -> NULL

www.ihtsdo.org
Map rule – age of onset
• Source concept: 32398004 Bronchitis (disorder)
• Map group 1
• Rule 1 IF 44518008 | AGE AT ONSET OF CLINICAL
FINDING (OBSERVABLE)| < 15 YEARS → J20.9 Acute
bronchitis, unspecified
• Rule 2 OTHERWISE TRUE → J40 Bronchitis not specified
as acute or chronic

www.ihtsdo.org
Map rule – exclusions
• Source concept: 367403001 Pyloric stenosis (disorder)
• Map group 1
• Rule 1 IFA 204671009 | CONGENITAL PYLORIC STENOSIS
(DISORDER) | OR DESCENDANTS → Q40.0 Congenital
hypertrophic pyloric stenosis
• Rule 2 OTHERWISE TRUE → K31.1 Adult hypertrophic
pyloric stenosis

www.ihtsdo.org
Map advice
• Explicit guidance on the map’s usage
• DESCENDANTS NOT EXHAUSTIVELY MAPPED
• EPISODE OF CARE INFORMATION NEEDED
• CONSIDER ADDITIONAL CODE TO IDENTIFY SPECIFIC CONDITION OR
DISEASE
• CONSIDER LATERALITY SPECIFICATION
• CONSIDER TRIMESTER SPECIFICATION
• CONSIDER WHICH FETUS IS AFFECTED BY THE MATERNAL CONDITION
• POSSIBLE REQUIREMENT FOR AN EXTERNAL CAUSE CODE
• THIS IS A MANIFESTATION CODE FOR USE IN A SECONDARY POSITION
• THIS IS AN EXTERNAL CAUSE CODE FOR USE IN A SECONDARY POSITION

www.ihtsdo.org
Dual independent mapping
• Built-in quality assurance process – each map has to be agreed by 2
independent sources
• Concepts with no legacy maps – mapped independently by 2 map specialists
• Concepts with legacy maps – mapped by 1 map specialist first, and by another
if there is discordance between legacy map and 1st map specialist
• Sources of legacy maps
• Existing UK maps (to ICD-10)
• CMT maps (to ICD-10-CM)
• UMLS synonymy
• ICD-10-CM maps derived from finalized ICD-10 maps
• Minor conflicts resolved by map leads
• Otherwise referred for broader discussion or consensus management
panel
 Intended uses of the map

• Embedded in the EHR for real-time, interactive ICD

codes generation (I-MAGIC=Interactive Map-
Assisted Generation of ICD Codes)
• To assist coding professionals by suggesting ICD
codes based on SNOMED CT-encoded problem list
entries
Interactive Map-Assisted Generation of ICD
Codes (I-MAGIC) Algorithm
SNOMED CT concepts that are in
scope for mapping
• Any concept in the following three SNOMED CT
hierarchies
• Clinical finding
• Event
• Situation with explicit context
• Total about 110,000 concepts in scope

www.ihtsdo.org
Priorities for phase 1 work
• ICD-10 map
• NLM’s CORE Problem List Subset
• SNOMED CT concepts that correspond to top ranking
ICD-10 codes in 5 countries
• ICD-10-CM map
• NLM’s CORE Problem List Subset
• Donated content from Kaiser Permanente’s Convergent
Medical Terminology (CMT) – top 2,500, sub-specialty
subsets (cardiology, neurology, mental health, musculo-
skeletal)
Work progress
• ICD-10 map
• Preview publication of maps for 5,000 concepts in
September 2011
• Final publication of phase 1 maps (about 20,000
concepts) planned for April 2012
• ICD-10-CM map
• Planned release dates
• Feb 2012 – preview release (6,000 concepts)
• June 2012 – full phase 1 maps (15,000 concepts)
I-MAGIC demo tool
http://imagic.nlm.nih.gov/imagic/code/map
Questions?
• kfung@mail.nih.gov
SNOMED CT to ICD-10
Maps
Other and Unspecified
 Overview

• A feature of the ICD-10 Example D39

classification, that
distinguishes it from a
terminology like
SNOMED CT, is the
presence of codes for
the ‘other specified’
and ‘unspecified’ form
of a disorder

• These are usually, but

not always.8 and .9
 NEC
• NEC stands for Not
Elsewhere Classified
‘Not Elsewhere
Classified’ indicates that
specified variants or
types of the disease are
classified elsewhere, and
that where appropriate,
a more precise term
should be looked for
• If the specific diagnostic
term cannot be found
 Other specified in use
D39.7 shown below is a grouped code • The ‘other’ category (.7 here but
which includes neoplasm of uncertain or usually .8) is also known as the
unknown behaviour of any specific residual (and sometimes ‘bucket’)
anatomical area of female genital category and immediately follows
organs, other than Uterus, Ovary or
Placenta. For example fallopian tube, or
the specific codes/categories to
vulva, would be coded here because which it pertains.
they do not have a specific fourth
character of their own
 SNOMED CT to ICD-10 Map
Example
This slide shows an example of a SNOMED CT concept and its ICD-10 map based
on what has been explained previously (see slides 2 and 4)
94837001|Neoplasm of uncertain behavior of female genital organ (disorder)|

ICD-10 Index
Neoplasm
- genital organ or tract
- - female NEC D39.9
- - - specified site NEC D39.7
 NEC in the Tabular list
• NEC Not Elsewhere
Classified • The exclusion notes will help you find
alternative codes for various types of
oedema. The fourth character
categories in R60.- are only used if
• If you see this phrase or you cannot find a more specific code
for the case of oedema.
its abbreviation used in a
code title or in an
inclusion or exclusion
note, it alerts you to
consult the Index or the
inclusion and exclusion
notes because other
conditions which include
the same terms are to be
 SNOMED CT to ICD-10 Map
Example

ICD-10 Index
Edema, edematous
- heat T67.7
 .9 in the Index, Volume 3
• A term without any • In the index the code assignment
is most often that which directly
essential modifiers is follows the lead term or the
usually the unspecified ‘unmodified’ term. The
abbreviation NOS is found in the
form of the condition Tabular List not the Index.

• When mapping a
concept for a diagnosis,
problem or reason for
an encounter that has no
modifiers it is said to be
unspecified or
unqualified or NOS (not
 SNOMED CT to ICD-10 Map
Examples
129103003|Endometriosis (disorder)|

61640006|Endometriosis of cervix (disorder)|

- parent Endometriosis of uterus (disorder)

ICD-10 Index
• Endometriosis N80.9
- uterus N80.0
 Unspecified terms in Volume 1
• Unspecified or NOS • ‘Vitamin B deficiency, unspecified’
means use E53.9 if you do not have
indicates where a any more information other than there
is a deficiency of Vitamin B.
disease/injury belongs
if it is not qualified or if
you have no further
information to allow you
to use a specific three- or
four-character code for
a disease.

Deficiency, deficient
193188009 Polyneuropathy due to vitamin B deficiency

• In this case, the vitamin is known to be

B but is unspecified as no further
information is available.

Index:
Polyneuropathy (peripheral) G62.9

-- in (due to)

- - lack of vitamin NEC E56.9† G63.4*

 Axis of classification
• In ICD-10 anatomy is
the primary axis of classification
and codes are based on the
anatomical systems.
BUT
• ICD-10 is a variable or multi-axial
classification
Other examples of axes used are:
• Etiology or cause of disease
(certain infectious and
parasitic diseases)
• Type of disease
(cardiac arrhythmia)
• The use of assorted axes of
classification is necessary to meet
the needs of a varied groups of
users in classifying diseases,
injuries and other reasons for
health services being provided in
a wide array of healthcare
settings.
• A combination of multiple and
varied axes are used in
classifying some diseases within
the same chapter.
 Example types of axis of
classification
When coding injuries, the • S50 Example
first axis of classification
is the body region
affected (such as head,
neck, thorax, etc.)

The second axis of

classification of injuries is
the specific type of injury
(such as superficial, open
wound, fracture,
dislocation and sprain,
 SNOMED CT to ICD-10 Map
Example
211251003|Abrasion, elbow area (disorder)|

ICD-10 Index
Abrasion — see also Injury, superficial T14.0

Injury — see also specified injury type T14.9

- superficial (for contusions, see first
Contusion)

- - elbow S50.9
 Example of axis of classification
• The meaning of ‘other’ (and thus .8) is determined by
the preceding codes/categories to which it pertains as
‘other’.
S60 Superficial injury of wrist and hand
S61 Open wound of wrist and hand
S62 Fracture at wrist and hand level
S63 Dislocation, sprain and strain of joints and ligaments at wrist and hand level
S64 Injury of nerves at wrist and hand level
S65 Injury of blood vessels at wrist and hand level
S66 Injury of muscle and tendon at wrist and hand level
S67 Crushing injury of wrist and hand
S68 Traumatic amputation of wrist and hand

S69 Other and unspecified injuries of wrist and hand

S69.7 Multiple injuries of wrist and hand
S69.8 Other specified injuries of wrist and hand
 SNOMED CT to ICD-10 Map
Example
438480008|Injury of
nail bed of
finger
(disorder)|

ICD-10 Index
Injury
- finger (nail) S69.9