Glossary

Glossary

Knowledge on the following terminology is necessary in order to use this guide. Complete documentation of FHIR STU3 is available at - https://hl7.org/fhir/R5/

  • Resource - This specification defines a series of different types of resource that can be used to exchange and/or store data in order to solve a wide range of healthcare related problems, both clinical and administrative. In addition, this specification defines several different ways of exchanging the resources.
    More details at - https://hl7.org/fhir/R5/resourcelist.html

  • Data types - The FHIR specification defines a set of data types that are used for the resource elements. There are four categories of data types:

    • Simple / primitive types, which are single elements with a primitive value (below)
    • General purpose complex types, which are re-usable clusters of elements (below)
    • Complex data types for metadata
    • Special purpose data types: Reference, Narrative, Extension, Meta, and Dosage
      More details at - http://hl7.org/fhir/R5/datatypes.html

  • Extension - Extensions are used to cover additional but valid requirements in an implementation that are not in the specification. The FHIR specification is based on generally agreed common requirements across healthcare - covering many jurisdictions, domains, and different functional approaches. It is common for specific implementations to have valid requirements that are not part of these agreed common requirements. Incorporating all valid requirements would make this specification very cumbersome and difficult to implement. .
    More details at - https://www.hl7.org/fhir/R5/extensibility.html

  • CodeSystem - Code systems define concepts and give them meaning through formal definitions, and assign codes that represent the concepts.
    More details at - https://www.hl7.org/fhir/R5/terminologies.html

  • ValueSet - Value set specifies a set of codes defined by code systems that can be used in a specific context.
    More details at - https://www.hl7.org/fhir/R5/terminologies.html

  • Profiles - The FHIR methodology uses FHIR profiles to express conformant instances of FHIR objects in use. They are customized structure definitions of the resource which describe in detail:

    • What elements of the resource are used and what not
    • What is the cardinality and data type of each element
    • If the element has any fixed values, binding to any ValueSet or any additional constraints
    • Extensions to hold information that does not fit in the spec
      More details at - https://www.hl7.org/fhir/R5/profiling.html

  • Cardinality - the lower and upper bounds on how many times this element is allowed to appear in the resource.
    More details at - https://www.hl7.org/fhir/R5/profiling.html#cardinality

  • Canonical url - Many resource types have a defined element "url" which is the canonical URL that always identifies the resource across all contexts of use. Typically, terminology, conformance or knowledge resources have canonical URLs. The canonical URL is the preferred way to reference a resource instance for the resource types on which it is defined.
    More details at - http://hl7.org/fhir/R5/references.html#canonical

  • Messaging - Messaging is supported via exchange using any applicable method of "Message Bundles". To use messaging with a RESTful API, a message bundle is POSTed to the endpoint.
    More details at - http://hl7.org/fhir/R5/messaging.html

  • Bundles - A Bundle is a FHIR resource type that is essentially a wrapper around other resources that can then be transmitted point to point in a single exchange. A "Message Bundle" is a type of Bundle that contains a MessageHeader resource that acts as a manifest and identifies a trigger event that defines why the Bundle is being exchanged. This MessageHeader is followed in the Bundle by the other resources that are involved in the event.
    More details at - http://hl7.org/fhir/R5/bundle.html