NCPI FHIR Implementation Guide
0.2.0 - ci-build

NCPI FHIR Implementation Guide - Local Development build (v0.2.0). See the Directory of published versions

Resource Profile: NCPI Phenotype

Official URL: https://nih-ncpi.github.io/ncpi-fhir-ig/StructureDefinition/phenotype Version: 0.2.0
Draft as of 2022-12-09 Computable Name: Phenotype

Representation of phenotypic observations (present or absent)

Scope and Usage

The Phenotype profile is used to associate a patient with one or more phenotypic observations. These observations can be either present or absent and will likely have an age associated with when the phenotype was observed.

The primary code system employed by this profile is Human Phenotype Ontology.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Condition

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 0..*ConditionDetailed information about conditions, problems or diagnoses
... code 0..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: Phenotype Codes (required)

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Condition.coderequiredPhenotypeCodes (a valid code from Human Phenotype Ontology)

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Phenotype Code

The Condition.code must have one Coding from the Human Phenotype Ontology. For cases where there is no ideal HPO code to suit a researcher’s needs, users may use a general HPO code as the first entry in the code array and one or more codes from other systems which are more technically accurate.

Phenotype Present/Absent

Condition.verificationStatus is used to convey presence/absence of a given phenotype using a subset of the Hl7 codes as follows:

Present/Absent Verification Status
Present Confirmed
Absent Refuted
recordedDate vs onset

Depending on the data available the condition may be tagged using recordedDate or onset.

Condition.recordedDate is described as “date record was first recorded” and, therefore, is expected to be the earliest date associated with the ascertainment of the diagnosis. Condition.onset is expected only for cases where there is confidence that the date is an actual onset date. Both dates should be provided as relativeDateTime relative to the patient’s birth date.