Enterprise HL7 / FHIR Terminology Engine
Universal Clinical Codes & Terminology Search
Search, verify, and inspect standardized LOINC, SNOMED CT, ICD-10-CM, RxNorm, and CPT clinical codes with native HL7 FHIR R4 resource mappings.
Showing 20 of 543259 codes
Per page:
Need to map or validate codes in bulk?
Cross-reference up to 1,000 ICD-10, LOINC, and CPT records simultaneously in memory with our free utility.
| Code Value | Display Description | Code System & OID | FHIR Resource | Category | Status | Actions |
|---|---|---|---|---|---|---|
|
1003664002
|
Osteolytic lesion of phalanx of third toe
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003665001
|
Osteolytic lesion of phalanx of toe
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003666000
|
Osteolysis of phalanx of little toe
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003667009
|
Osteolytic lesion of toe
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003668004
|
Osteolysis of proximal phalanx of second toe (disorder)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003669007
|
Osteolysis of proximal phalanx of third toe (disorder)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003670008
|
Osteolytic lesion of proximal phalanx of fourth toe
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
100367009
|
DIQUEL
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003671007
|
Osteolysis of proximal phalanx of little toe
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003672000
|
Osteolytic lesion of proximal phalanx of hallux
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003673005
|
Osteolysis of metatarsal bone
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003675003
|
Osteolysis of tarsus bone (disorder)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003678001
|
Heart disease due to thyrotoxicosis
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003679009
|
Human immunodeficiency virus Centers for Disease Control and Prevention dual infection with HIV-1 and HIV-2
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003680007
|
Human immunodeficiency virus Centers for Disease Control and Prevention undifferentiated type (finding)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
100368004
|
DIRODAN
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003681006
|
Human immunodeficiency virus Centers for Disease Control and Prevention stage 0 (finding)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003682004
|
Human immunodeficiency virus Centers for Disease Control and Prevention stage 1 (finding)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003683009
|
Human immunodeficiency virus Centers for Disease Control and Prevention stage 2 (finding)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
|
1003684003
|
Human immunodeficiency virus Centers for Disease Control and Prevention stage 3 (finding)
|
SNOMED CT
2.16.840.1.113883.6.96
|
General | General | Active |
|
Healthcare Terminology & FHIR R4 Interoperability
Standardized coding guidelines governed by CodesForMD
In HL7 FHIR R4, discrete clinical findings and laboratory measurements are encapsulated inside
Observation resources. Diagnostic terms and problem list entries are represented within Condition resources, while surgical and therapeutic acts map to Procedure. CodesForMD adheres to official US Core and International FHIR Implementation Guides.
An OID is an internationally standardized dotted-decimal identifier (e.g.
2.16.840.1.113883.6.1 for LOINC) registered with HL7 and ISO. OIDs ensure unambiguous identification of terminology authorities when exchanging clinical messages across heterogeneous EHR, LIS, and PACS systems.
Yes. You can visit our platform's administrative ingestion and export engine or contact our team to obtain batch files of standardized codes.