Others titles

  • FHIR Coding Resource
  • Electronic Health Records Exchange Through FHIR


  • FHIR
  • HL7
  • Medical Terminology
  • Processes Data
  • Processes Information
  • Processes Documentation
  • Health Information Exchange
  • Electronic Health Records
  • FHIR Smart
  • Smart on FHIR


A Coding is a representation of a defined concept using a symbol from a defined “code system”; it showcases the adjudicated response to a Claim, Predetermination or Preauthorization.

Log in to download

Get The Data

  • The data in CSV format DOWNLOAD
  • Metadata in Human Readable format (PDF) DOWNLOAD
  • Metadata in Machine Readable format (JSON) DOWNLOAD
Your Data License
  • Research
    Non-Commercial, Share-Alike, Attribution Free Forever
  • Commercial
    Commercial Use, Remix & Adapt, White Label Buy Subscription


This dataset details the strength of the payment aspect of the response that is matching to the strength of the original request. The meaning of the Coding is defined by the code. The system provides the source of the definition of the code, along with an optional version reference. The display is a human display for the text defined by the system and it is not intended for computation.

The system is a URI (Uniform Resource Identifier) that identifies the code system that defines the code. Choosing the correct system is important. If the code is taken from a Code System resource, CodeSystem.url is the correct value for the system element. Resolvable URLs (Uniform Resource Locator) are generally preferred by implementers over non-resolvable URNs (Uniform Resource Name), particularly opaque URNs such as Object Identifiers or OIDs (urn:oid:) and universally unique identifiers or UUIDs (urn:uuid:). The system URI does not contain a reference to a value set (e.g. ValueSet.url), since value sets just define the set of codes which are intended for use in a specific context, not the meaning of the codes themselves.

A code system version may also be supplied. If the meaning of codes within the code system is consistent across releases, this is not required. The version should be exchanged when the system does not maintain consistent definitions across versions. The following systems should always have a version specified:

– National releases of SNOMED CT (Systematized Nomenclature of Medicine Clinical Terms). Consistency of definitions varies amongst jurisdictions, and some jurisdictions may make their own rules on this.
– Various versions of ICD (International Classification of Diseases). Note: the major releases are labeled as different code systems altogether, but there is variation within versions.

Fast Healthcare Interoperability Resources (FHIR) is a draft standard describing data formats and elements (known as “resources”) and an application programming interface (API) for exchanging electronic health records. The standard was created by the Health Level Seven International (HL7) health-care standards organization.

Its goal is to facilitate interoperation between legacy healthcare systems, to make it easy to provide healthcare information to healthcare providers and individuals on a wide variety of devices from computers to tablets to cell phones, and to allow third-party application developers to provide medical applications which can be easily integrated into existing systems.

FHIR provides an alternative to document-centric approaches by directly exposing discrete data elements as services. For example, basic elements of healthcare like patients, admissions, diagnostic reports and medications can each be retrieved and manipulated via their own resource URLs (Uniform Resource Locators). FHIR was supported at an American Medical Informatics Association meeting by many EHR (Electronic Health Record) vendors which value its open and extensible nature.

About this Dataset

Data Info

Date Created


Last Modified




Update Frequency


Temporal Coverage


Spatial Coverage

United States


John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements


Source Citation



FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Coding Resource, Electronic Health Records Exchange Through FHIR

Data Fields

Name Description Type Constraints
Concept_NameName of the concept in the FHIR structurestringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe Dollar_Ref ($ref) string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON (JavaScript Object Notation) value being referenced.string-
DescriptionA free text natural language description of the structure and its usestring-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-

Data Preview

Concept NameComputer Ready NameTypeDollar RefDescriptionItems
Codingid#/definitions/stringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
CodingextensionarrayMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension there is a set of requirements that SHALL be met as part of the definition of the extension.{'$ref': '#/definitions/Extension'}
Codingsystem#/definitions/uriThe identification of the code system that defines the meaning of the symbol in the code.
Coding_system#/definitions/ElementExtensions for system
Codingversion#/definitions/stringThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported because the meaning of codes is consistent across versions. However this cannot consistently be assured and when the meaning is not guaranteed to be consistent
Coding_version#/definitions/ElementExtensions for version
Codingcode#/definitions/codeA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Coding_code#/definitions/ElementExtensions for code
Codingdisplay#/definitions/stringA representation of the meaning of the code in the system following the rules of the system.
Coding_display#/definitions/ElementExtensions for display