SNOMED CT Implementation Guide for FHIR
0.0.1 - CI Build

SNOMED CT Implementation Guide for FHIR, published by SNOMED on FHIR project group. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHTSDO/snomed-ig/ and changes regularly. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Allergy Intolerance - Finding Focused

Profile of Allergy Intolerance resource with bindings to SNOMED CT Clinical findings as well as additional constraints to avoid overlap with the binding.

Allergy Intolerance - Substance Focused

Profile of Allergy Intolerance resource with bindings to SNOMED CT Substances as well as additional constraints to avoid overlap with the binding.

BMI

Profile of HL7 BMI profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Blood pressure

Profile of HL7 blood pressure profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Body Height

Profile of HL7 body height profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Body Temperature

Profile of HL7 body temperature profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Body Weight

Profile of HL7 body weight profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Head Circumference

Profile of HL7 head circumference profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Heart Rate

Profile of HL7 heart rate profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Oxygen Saturation

Profile of HL7 oxygen saturation profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Respiratory Rate

Profile of HL7 respiratory rate profile with SNOMED CT binding in addition to 'magic number' binding from base profile.

Specimen

Profile of the Specimen resource for use with SNOMED CT coding.

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Allergy Intolerance Detailed Type Extension

Extension to allow detailed coding similar to AllergyIntolerance.type.

Designation Use Context Extension

Extension to allow specific contexts of use (eg SNOMED Language Reference Sets, LOINC short name, long common name, consumer name, as well as ICD-10 rubrics) to be specified when working with designations

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Allergy Intolerance Detailed Type Value Set

A value set with detailed type of allergy or intolerance to be used in addition to AllergeyIntolerance.type in R4. R5 have been amended with an update value set.

Allergy-Intolerance Finding Code
This value set contains concept codes for allergy or intolerance clinical findings. It includes codes from SNOMED where concept is-a 420134006 Propensity to adverse reaction (finding)
BMI Observable entity Code
This value set contains concept codes for BMI observable entities. It includes the single code from SNOMED 60621009 Body mass index (observable entity)
Body Height Observable entity Codes
This value set contains concept codes for body height observable entities. It includes codes from SNOMED meeting the constraint << 248334005 Length of body (observable entity)
Body weight Observable entity Code
This value set contains concept codes for body weight observable entities. It includes codes from SNOMED meeting the constraint (<< 27113001 Body weight (observable entity) MINUS (<< 248350002 Reference weight (observable entity) OR << 301334000 Birth weight centile (observable entity) ))
Core body temperature Observable entity Code
This value set contains concept codes for core body temperature observable entities. It includes codes from SNOMED meeting the constraint << 276885007 Core body temperature (observable entity)
Diastolic blood pressure Observable entity Code
This value set contains concept codes for diastolic blood pressure observable entities. It includes codes from SNOMED meeting the constraint (<< 271650006 Diastolic blood pressure (observable entity) MINUS (<< 314465004 24 hour diastolic blood pressure (observable entity) OR << 716632005 Baseline diastolic blood pressure (observable entity) OR << 315613000 Target diastolic blood pressure (observable entity) ))
Head circumference Observable entity Code
This value set contains concept codes for head circumference observable entities. It includes codes from SNOMED meeting the constraint (<< 363812007 Head circumference (observable entity) MINUS << 248397001 Head circumference centile (observable entity) )
Heart rate Observable entity Code
This value set contains concept codes for heart rate observable entities. It includes codes from SNOMED meeting the constraint (<< 364075005 Heart rate (observable entity) MINUS 428420003 Target heart rate (observable entity) )
Peripehral oxygen saturation Observable entity Code
This value set contains concept codes for peripheral oxygen saturation observable entities. It includes codes from SNOMED meeting the constraint <<431314004 Peripheral oxygen saturation (observable entity)
Respiratory rate Observable entity Code
This value set contains concept codes for respiratory rate observable entities. It includes codes from SNOMED meeting the constraint << 86290005 Respiratory rate (observable entity)
Specimen Collection Bodysite ValueSet Set

Codes describing the specimen collcetion bodysite.

Specimen Collection Method ValueSet

Codes describing the specimen collection method.

Specimen Processing Procedure ValueSet

Codes describing the specimen processing procedure.

Specimen Value Set

Codes describing the type of specimen.

Systolic blood pressure Observable entity Code
This value set contains concept codes for systolic blood pressure observable entities. It includes codes from SNOMED meeting the constraint (<< 271649006 Systolic blood pressure (observable entity) MINUS (<< 314464000 24 hour systolic blood pressure (observable entity) OR << 716579001 Baseline systolic blood pressure (observable entity) OR << 315612005 Target systolic blood pressure (observable entity) ))

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

AllergyConditionExample1-1

Scenario: A review of systems fails to reveal any other causes and the physician believes that the patient may be having an urticarial reaction to penicillin. He has lingering uncertainty about this and tells the patient to stop the penicillin and employ diphenhydramine for relief. He schedules him back in a week for follow-up and when recording his note for the visit, he adds to his assessment in the problem list: "Moderate urticarial reaction, possible penicillin allergy".

AllergyConditionExample3-1

Scenario: A 34-year-old female is seen by her primary care provider for complaints of abdominal pain, bloating and change in bowel habits within hours or a few days after ingesting whole wheat bread. In addition, she complains of feeling tired but denies itching rash or wheezing. Those complaints are entered as observations in the EHR.

AllergyConditionExample3-2

Scenario: A 34-year-old female is seen by her primary care provider for complaints of abdominal pain, bloating and change in bowel habits within hours or a few days after ingesting whole wheat bread. In addition, she complains of feeling tired but denies itching rash or wheezing. Those complaints are entered as observations in the EHR.

AllergyConditionExample3-3

Scenario: A 34-year-old female is seen by her primary care provider for complaints of abdominal pain, bloating and change in bowel habits within hours or a few days after ingesting whole wheat bread. In addition, she complains of feeling tired but denies itching rash or wheezing. Those complaints are entered as observations in the EHR.

AllergyConditionExample3-4

Scenario: Due to a family history of celiac disease, tissue transglutaminase IgG and IgA are ordered which are negative. The patient is also referred to a gastroenterologist, who performs an endoscopic biopsy, which is negative for celiac disease. (Both of these examination results can be recorded in the EHR as a FHIR observation using LOINC codes). The patient is advised to avoid wheat and gluten containing products. An encounter diagnosis of moderate wheat intolerance is documented in the patient’s health record and wheat is entered in the patient’s "allergy" list.

AllergyConditionExample7-1

Scenario: A licensed nurse presents to her personal physician for recurring problems of a generalized rash and itching. She works in an intensive care unit and is constantly handing chemicals, disinfectants, assisting in surgical procedures and performing catheter cares for her patients. As a part of the health history, she noticed that she had an eruption on her hands after handling latex catheters. Additionally, she reports a serious allergic reaction to papaya in the past and has been careful in the fruits she eats as a consequence. The clinician suspects a latex allergy cross-reacting with foodstuffs and orders IgE testing for Hevea latex antibody. The serology testing is strongly positive and the clinician advises the nurse of his findings with warnings about other foods, which may cross react.

AllergyConditionExample7-2

Scenario: A licensed nurse presents to her personal physician for recurring problems of a generalized rash and itching. She works in an intensive care unit and is constantly handing chemicals, disinfectants, assisting in surgical procedures and performing catheter cares for her patients. As a part of the health history, she noticed that she had an eruption on her hands after handling latex catheters. Additionally, she reports a serious allergic reaction to papaya in the past and has been careful in the fruits she eats as a consequence. The clinician suspects a latex allergy cross-reacting with foodstuffs and orders IgE testing for Hevea latex antibody. The serology testing is strongly positive and the clinician advises the nurse of his findings with warnings about other foods, which may cross react.

AllergyIntoleranceExample1-2

Scenario: A week later, the patient returns for follow-up with the itching and rash entirely resolved. He reports that the reaction subsided within days after stopping the penicillin. The physician adds “Penicillin allergy probable: moderate reaction of hives; criticality unable-to-assess” to the allergy list.

AllergyIntoleranceExample1-2-alt

Scenario: A week later, the patient returns for follow-up with the itching and rash entirely resolved. He reports that the reaction subsided within days after stopping the penicillin. The physician adds “Penicillin allergy probable: moderate reaction of hives; criticality unable-to-assess” to the allergy list.

AllergyIntoleranceExample2

Scenario: Scenario: Several years later, the patient from scenario 4.1 who has since received an aortic valve replacement is seeing another physician within the organization for consultation on antibiotic prophylaxis for an upcoming dental procedure. The second physician decides that a penicillin class antibiotic is appropriate for the patient.
When the physician creates an order for amoxicillin 2 g orally as a single dose and commits to the electronic prescription, an alert appears which requires a response by the physician warning him of an allergy history to penicillin. The substance-based alert is generated by the EHR drug-disease interactions software, which uses the Allergy list as a reference. As the patient has not received penicillin class antibiotics for several years, the physician decides to refer the patient to an allergy specialist for clarification of current status of penicillin allergy. The specialist performs skin testing for penicillin allergy, the results of which are positive. The patient is confirmed as penicillin allergic and the results of the testing are documented in the patient’s medical record. The patient is subsequently prescribed azithromycin for his dental procedure.

AllergyIntoleranceExample2-alt

Scenario: Scenario: Several years later, the patient from scenario 4.1 who has since received an aortic valve replacement is seeing another physician within the organization for consultation on antibiotic prophylaxis for an upcoming dental procedure. The second physician decides that a penicillin class antibiotic is appropriate for the patient.
When the physician creates an order for amoxicillin 2 g orally as a single dose and commits to the electronic prescription, an alert appears which requires a response by the physician warning him of an allergy history to penicillin. The substance-based alert is generated by the EHR drug-disease interactions software, which uses the Allergy list as a reference. As the patient has not received penicillin class antibiotics for several years, the physician decides to refer the patient to an allergy specialist for clarification of current status of penicillin allergy. The specialist performs skin testing for penicillin allergy, the results of which are positive. The patient is confirmed as penicillin allergic and the results of the testing are documented in the patient’s medical record. The patient is subsequently prescribed azithromycin for his dental procedure.

AllergyIntoleranceExample3

Scenario: Scenario: Several years later, the patient from scenario 4.1 who has since received an aortic valve replacement is seeing another physician within the organization for consultation on antibiotic prophylaxis for an upcoming dental procedure. The second physician decides that a penicillin class antibiotic is appropriate for the patient.
When the physician creates an order for amoxicillin 2 g orally as a single dose and commits to the electronic prescription, an alert appears which requires a response by the physician warning him of an allergy history to penicillin. The substance-based alert is generated by the EHR drug-disease interactions software, which uses the Allergy list as a reference. As the patient has not received penicillin class antibiotics for several years, the physician decides to refer the patient to an allergy specialist for clarification of current status of penicillin allergy. The specialist performs skin testing for penicillin allergy, the results of which are positive. The patient is confirmed as penicillin allergic and the results of the testing are documented in the patient’s medical record. The patient is subsequently prescribed azithromycin for his dental procedure.

AllergyIntoleranceExample3-alt

Scenario: Scenario: Several years later, the patient from scenario 4.1 who has since received an aortic valve replacement is seeing another physician within the organization for consultation on antibiotic prophylaxis for an upcoming dental procedure. The second physician decides that a penicillin class antibiotic is appropriate for the patient.
When the physician creates an order for amoxicillin 2 g orally as a single dose and commits to the electronic prescription, an alert appears which requires a response by the physician warning him of an allergy history to penicillin. The substance-based alert is generated by the EHR drug-disease interactions software, which uses the Allergy list as a reference. As the patient has not received penicillin class antibiotics for several years, the physician decides to refer the patient to an allergy specialist for clarification of current status of penicillin allergy. The specialist performs skin testing for penicillin allergy, the results of which are positive. The patient is confirmed as penicillin allergic and the results of the testing are documented in the patient’s medical record. The patient is subsequently prescribed azithromycin for his dental procedure.

AllergyIntoleranceExample5

Scenario: The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of "severe".

AllergyIntoleranceExample5-alt

Scenario: The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of "severe".

AllergyIntoleranceExample6

Scenario: The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of "severe".

AllergyIntoleranceExample6-alt

Scenario: The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of "severe".

AllergyIntoleranceExample7

Scenario: The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of "severe".

AllergyIntoleranceExample7-alt

Scenario: The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of "severe".

AllergyIntoleranceExample8

Scenario: A nurse is performing an intake examination on a patient that is new to the clinical practice. As part of the clinical interview, he inquires about medication and other allergies. The patient reports that she is not allergic to any medications, foods, chemicals or animals. The nurse opens the 'allergy list' in the EHR and documents 'No known allergies' which electronically validates that the nurse inquired of the patient and that the history was confirmed negative at the date and time recorded. This satisfies decision support criteria that allergies be documented before medication orders are written and is encoded in the EHR allergy list as confirmed absence of dispositions to adverse reactions.

AllergyIntoleranceExample8-alt

Scenario: A nurse is performing an intake examination on a patient that is new to the clinical practice. As part of the clinical interview, he inquires about medication and other allergies. The patient reports that she is not allergic to any medications, foods, chemicals or animals. The nurse opens the 'allergy list' in the EHR and documents 'No known allergies' which electronically validates that the nurse inquired of the patient and that the history was confirmed negative at the date and time recorded. This satisfies decision support criteria that allergies be documented before medication orders are written and is encoded in the EHR allergy list as confirmed absence of dispositions to adverse reactions.

AllergyObservationExample1-1

Scenario: A physician sees a patient in clinic for routine outpatient care. Recently the patient was prescribed penicillin V 500 mg orally two times daily x 10 days for streptococcal pharyngitis. He tells the physician that he has developed hives the previous week and on examination, the physician confirms the presence of generalized hives. He records this in the patient record as an Observation.

AllergyObservationExample2

Scenario: Several years later, the patient from scenario 4.1 who has since received an aortic valve replacement is seeing another physician within the organization for consultation on antibiotic prophylaxis for an upcoming dental procedure. The second physician decides that a penicillin class antibiotic is appropriate for the patient.
When the physician creates an order for amoxicillin 2 g orally as a single dose and commits to the electronic prescription, an alert appears which requires a response by the physician warning him of an allergy history to penicillin. The substance-based alert is generated by the EHR drug-disease interactions software, which uses the Allergy list as a reference. As the patient has not received penicillin class antibiotics for several years, the physician decides to refer the patient to an allergy specialist for clarification of current status of penicillin allergy. The specialist performs skin testing for penicillin allergy, the results of which are positive. The patient is confirmed as penicillin allergic and the results of the testing are documented in the patient’s medical record. The patient is subsequently prescribed azithromycin for his dental procedure.

AllergyObservationExample5

Scenario: A patient's mother reports to their child's physician that the child reacts violently to eating peanuts with symptoms that include generalized hives, wheezing and hypotension requiring use of epinephrine for resuscitation. The physician obtains a blood test which documents high levels of IgE antibody against the Arachis h2 peanut protein which is found in unrefined peanut oil (Arachis oil) - the sensitizing agent for clinical peanut allergy. Ara h2 is associated with a risk of severe reactions to peanut.

AllergyObservationExample6

Scenario: A patient's mother reports to their child's physician that the child reacts violently to eating peanuts with symptoms that include generalized hives, wheezing and hypotension requiring use of epinephrine for resuscitation. The physician obtains a blood test which documents high levels of IgE antibody against the Arachis h2 peanut protein which is found in unrefined peanut oil (Arachis oil) - the sensitizing agent for clinical peanut allergy. Ara h2 is associated with a risk of severe reactions to peanut.

AllergyObservationExample7

Scenario: While documenting the clinical encounter, he records a latex allergy in the allergy list. The EHR software supports selection of foods, chemicals and animal biological products as substances, which may be identified as source substances for an entry onto the allergy list or for recording of an adverse reaction.

AllergySpecimenExample5
AllergySpecimenExample6
AllergySpecimenExample7
DrugValueSetExample0

Example of drug concepts with multiple designation uses

DrugValueSetExample1

Example of drug concepts with multiple designations with different use contexts

DrugValueSetExample2

Example of drug concepts with multiple designations with different use contexts

PatientExample1

Example for Patient

PatientExample2

Example for Patient

PatientExample7

Example for Patient

Problem List

Scenario: A 34-year-old female is seen by her primary care provider for complaints of abdominal pain, bloating and change in bowel habits within hours or a few days after ingesting whole wheat bread. In addition, she complains of feeling tired but denies itching rash or wheezing. Those complaints are entered as observations in the EHR.

Problem List

Scenario: A 34-year-old female is seen by her primary care provider for complaints of abdominal pain, bloating and change in bowel habits within hours or a few days after ingesting whole wheat bread. In addition, she complains of feeling tired but denies itching rash or wheezing. Those complaints are entered as observations in the EHR.

SimpleCodeSystem

Example of multiple contextual uses