Understanding Observations and Observation Values

Many kinds of health data are represented as observations. A laboratory test result, a vital sign measurement, a pain scale rating, or recording the kind of exercise activity that a patient engaged in (e.g. running, walking, swimming, etc.) can all be considered observations. In this context, we use observation as a generic term. Depending on the domain of interest, you might call these tests, variables, or data elements, etc.

Within and among health IT systems, observations are communicated with a structure that has two key structural elements. The first element identifies what the observation is, e.g. diastolic blood pressure, hematocrit, tobacco smoking status, or pain intensity on a 0 to 10 scale. The second element carries the result value of the observation, e.g. 80 (mmHg), 40 (%), “current every day smoker”, or 5. When used together, these two elements carry the instance of specific test result for a given patient.

Another way to think about this model is as questions and answers. This first element of the structure (the observation) is like the question, and the second element (the observation value) is like the answer. For example, the question might be: What is this patient’s blood type? The answer then, might be O Positive.

When identifying Vocabulary/Code Sets/Terminology Standards for health data represented as observations, the ISA lists separately the different standards for the observation and the observation value because they fulfill different roles. Quantitative results don’t need a standard code for the value: the observation value is simply a number (with its associated units of measure). On the other hand, nominal or ordinal results benefit from having a standard code.

A common pairing for many domains is to use LOINC as the standard code for the observation (that’s what the O in LOINC stands for), and SNOMED CT as the standard code for the observation value when needed. This approach is endorsed by the developers of both of these terminologies and fits their design purpose. Yet, the choice of which vocabulary standard to use for these roles varies by domain. For example, when reporting the results of a validated patient assessment (e.g. the Morse Fall Scale), you may choose to use the LOINC Answer Codes as the observation value because they represent the exact text as it appears in that instrument. In contrast, a different approach may be needed when reporting genetic variant results. For example, when reporting a simple genetic variant you could pair the LOINC observation code [81252-9] for “Discrete genetic variant” with an observation value using an identifier from NCBI's ClinVar. Reporting a complex genetic variant may instead pair the LOINC observation code [81262-8] for “Complex variant HGVS name” with an observation value expressed in the HGVS nomenclature.

There are some situations where the structure of health IT system removes the need for the two-part observation structure. If an EHR has a “Problem” table where the records are instances or assertions of patient problems (conditions), then there is no need for an observation code. On the other hand, if the structure of the health IT system or the exchange format lacks such a structural element, the patient’s problem list could be represented using the observation and observation value pattern.

Text developed by the Health IT Standards Committee as part of the 2017 ISA Task Force

Form Guide

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

This field is entirely optional and serves the following purposes:

Provides context for reviewers
Serves as an introduction if submitting multiple comments
Functions as a cover letter for formal submissions

If you are submitting a single comment for a specific data class or element, you may leave this field blank. For multiple comments, this space is useful for explaining the overall purpose or connection between your comments.

Fig 1 The "Optional Background Text / Cover Letter" field allows users to provide contextual information or introductory remarks for their comment submission.

2. Complete the Comment Form

The comment form contains several fields that require your input:

ISA Content: This field is automatically populated based on the page you are currently viewing. No action is required.

Standards and Implementation Specifications: This drop-down menu is pre-selected based on the topic you're commenting on. The selection reflects the relevant standard or implementation specification for your current page.

Subject: Enter a concise title that summarizes the focus of your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: This is the main field where you provide your detailed feedback, concerns, or suggestions. The comment box includes a text editor with formatting options that allow you to:

Format text as bold or italic
Insert hyperlinks
Create bullet points
Create numbered lists
Apply strike-through formatting
Attach images
Insert tables

Use these formatting options as needed to clearly present your information.

Fig 2 The comment text editor toolbar provides formatting options including bold, italic, links, lists, tables, and image insertion capabilities.

3. Optional: Add Additional Comments

If you need to provide feedback on multiple aspects of the ISA content, you can add additional comments:

After completing your first comment, locate and click the link labeled "Comment on another interoperability need" at the bottom of the form.
A new comment section will appear, allowing you to enter details for your additional comment.
For this new comment section, the "ISA Content" and "Standards and Implementation Specifications" fields will not be automatically populated. You must select the appropriate content and specification from the drop-down menus for each additional comment.
Complete all required fields for your additional comment.
Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another interoperability need" link enables users to add multiple comments within a single submission.

4. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

Locate the "File Upload" section at the bottom of the comment form.
Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

5. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

Click the "Save and Exit" button at the bottom of the form.
Your comment will be saved as a draft that you can access and complete later.
When you return to the platform, you will see a red triangle with an exclamation mark next to the "Return to saved Comment" button, indicating that you have saved comments in draft status.
Click the "Return to saved Comment " button to continue working on your draft.
You will be taken to a review page where you can:
1. Select "Submit Comment" to officially submit your feedback.
2. Click "Edit" to return to the comment form and make changes
3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the "Return to saved Comment" button when draft comments are saved in the system.

6. Review and Submit

Once you have completed your comment:

Click the "Review and Submit" button at the bottom of the form.
This will take you to a review screen displaying your comment(s) in full.
Review all information for accuracy and completeness.
On this review screen, you have three options:
1. Click "Submit Comment" to officially submit your feedback
2. Click "Edit" to return to the comment form and make changes
3. Click "Discard Draft" to delete the comment and start fresh
The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.