Others titles

  • FHIR Observation 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


Observation is the measurement and simple assertion made about a patient, device or other subject. Most observations are simple name/value pair assertions with some metadata, but some observations group other observations together logically, or even are multi-component observations.

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


Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics. Note that the Diagnostic Report resource provides a clinical or workflow context for a set of observations and the Observation resource is referenced by Diagnostic Report to represent laboratory, imaging, and other clinical and diagnostic data to form a complete report.

Uses for the Observation resource include:
– Vital signs such as body weight, blood pressure, and temperature
– Laboratory Data like blood glucose, or an estimated Glomerular Filtration Rate (GFR)
– Imaging results like bone density or fetal measurements
– Clinical Findings such as abdominal tenderness
– Device measurements such as Electrocardiogram (EKG) data or Pulse Oximetry data
– Clinical assessment tools such as ‘Appearance, Pulse, Grimace, Activity, and Respiration (APGAR)’ or a Glasgow Coma Score
– Personal characteristics: such as eye-color
– Social history like tobacco use, family support, or cognitive status
– Core characteristics like pregnancy status, or a death assertion

The boundaries between clinical findings and disorders remains a challenge in medical ontology. These boundaries can be clarified by profiling Observation for a particular use case.

The Media resource captures a specific type of observation whose value is audio, video or image data. This resource is used instead of Observation to represent such forms of information as it exposes the metadata relevant for interpreting the information.

In contrast to the Observation resource, the Diagnostic Report resource typically includes additional clinical context and some mix of atomic results, images, imaging reports, textual and coded interpretation, and formatted representations. Laboratory reports, pathology reports, and imaging reports should be represented using the Diagnostic Report resource. The Observation resource is referenced by the Diagnostic Report to provide the atomic results for a particular investigation. “Laboratories routinely have a variable that is summative across a series of discrete variables – these are usually called ‘impressions’ or ‘interpretations’. Sometimes they are algorithmically specified and sometimes they have the imprimatur of pathologists and they are conveyed in Observation or Diagnostic Report instead of the Clinical Impression resource. The Observation resource should not be used to record clinical diagnosis about a patient or subject.

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 Observation Resource, Electronic Health Records Exchange Through FHIR

Data Fields

Name Description Type Constraints
Concept_NameName of the concept in the FHIR structure.stringrequired : 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 "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
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-
EnumThe enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.string-
RequiredThe value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.string-
ConstThe value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.string-

Data Preview

Concept NameComputer Ready NameTypeDollar RefDescriptionItemsEnumRequiredConst
OrganizationresourceTypeThis is a Organization resourceOrganization
Organizationid#/definitions/idThe logical id of the resource as used in the URL for the resource. Once assigned this value never changes.
Organizationmeta#/definitions/MetaThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
OrganizationimplicitRules#/definitions/uriA reference to a set of rules that were followed when the resource was constructed and which must be understood when processing the content. Often this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Organization_implicitRules#/definitions/ElementExtensions for implicitRules
Organizationlanguage#/definitions/codeThe base language in which the resource is written.
Organization_language#/definitions/ElementExtensions for language
Organizationtext#/definitions/NarrativeA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
OrganizationcontainedarrayThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently and nor can they have their own independent transaction scope.{'$ref': '#/definitions/ResourceList'}
OrganizationextensionarrayMay be used to represent additional information that is not part of the basic definition of the resource. 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'}