FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

9.4 Resource FamilyMemberHistory - Content

Patient Care icon Work GroupMaturity Level: 2 Trial UseSecurity Category: Patient Compartments: Patient

Significant health conditions for a person related to the patient relevant in the context of care for the patient.

FamilyMemberHistory is one of the event resources in the FHIR workflow specification.

This resource records significant health conditions for a particular individual related to the subject. This information can be known to different levels of accuracy. Sometimes the exact condition ('asthma') is known, and sometimes it is less precise ('some sort of cancer'). Equally, sometimes the person can be identified ('my aunt Agatha') and sometimes all that is known is that the person was an uncle.

This resource represents a simple structure used to capture an 'elementary' family history for a particular family member. However, it can also be the basis for capturing a more rigorous history useful for genetic and other analysis - refer to the Genetic Pedigree profile for an example.

The entire family history for an individual can be represented by combining references to FamilyMemberHistory instances into a List resource instance.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. FamilyMemberHistory TU DomainResource Information about patient's relatives, relevant for patient
+ Rule: Can have age[x] or born[x], but not both
+ Rule: Can only have estimatedAge if age[x] is present
+ Rule: Can have age[x] or deceased[x], but not both

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ 0..* Identifier External Id(s) for this record

... status ?!Σ 1..1 code partial | completed | entered-in-error | health-unknown
Binding: Family History Status (Required)
... dataAbsentReason Σ 0..1 CodeableConcept subject-unknown | withheld | unable-to-obtain | deferred
Binding: Family History Absent Reason (Example)
... date Σ 0..1 dateTime When history was recorded or last updated
... participant Σ 0..* BackboneElement Who or what participated in the activities related to the family member history and how they were involved

.... function Σ 0..1 CodeableConcept Type of involvement
Binding: Participation Role Type (Extensible)
.... actor Σ 1..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson | Device | Organization | CareTeam) Who or what participated in the activities related to the family member history
... name Σ 0..1 string The family member described
... relationship Σ 1..1 CodeableConcept Relationship to the subject
Binding: FamilyMember icon (Example)
... sex Σ 0..1 CodeableConcept male | female | other | unknown
Binding: AdministrativeGender (Extensible)
... born[x] C 0..1 (approximate) date of birth
.... bornPeriod Period
.... bornDate date
.... bornString string
... age[x] ΣC 0..1 (approximate) age
.... ageAge Age
.... ageRange Range
.... ageString string
... estimatedAge ΣC 0..1 boolean Age is estimated?
... deceased[x] ΣC 0..1 Dead? How old/when?
.... deceasedBoolean boolean
.... deceasedAge Age
.... deceasedRange Range
.... deceasedDate date
.... deceasedString string
... reason Σ 0..* CodeableReference(Condition | Observation | AllergyIntolerance | QuestionnaireResponse | DiagnosticReport | DocumentReference) Why was family member history performed?
Binding: SNOMED CT Clinical Findings (Example)

... note 0..* Annotation General note about related person

... condition 0..* BackboneElement Condition that the related person had

.... code 1..1 CodeableConcept Condition, allergy, or intolerance suffered by relation
Binding: Condition/Problem/Diagnosis Codes (Example)
.... outcome 0..1 CodeableConcept deceased | permanent disability | etc
Binding: Condition Outcome Codes (Example)
.... contributedToDeath 0..1 boolean Whether the condition contributed to the cause of death
.... onset[x] 0..1 When condition first manifested
..... onsetAge Age
..... onsetRange Range
..... onsetPeriod Period
..... onsetString string
.... note 0..* Annotation Extra information about condition

... procedure 0..* BackboneElement Procedures that the related person had

.... code 1..1 CodeableConcept Procedures performed on the related person
Binding: Procedure Codes (SNOMED CT) (Example)
.... outcome 0..1 CodeableConcept What happened following the procedure
Binding: SNOMED CT Clinical Findings (Example)
.... contributedToDeath 0..1 boolean Whether the procedure contributed to the cause of death
.... performed[x] 0..1 When the procedure was performed
..... performedAge Age
..... performedRange Range
..... performedPeriod Period
..... performedString string
..... performedDateTime dateTime
.... note 0..* Annotation Extra information about the procedure


doco Documentation for this format icon

See the Extensions for this resource

 

Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis

Path ValueSet Type Documentation
FamilyMemberHistory.status FamilyHistoryStatus Required

A code that identifies the status of the family history record.

FamilyMemberHistory.dataAbsentReason FamilyHistoryAbsentReason Example

Codes describing the reason why a family member's history is not available.

FamilyMemberHistory.participant.function ParticipationRoleType Extensible

This FHIR value set is comprised of Actor participation Type codes, which can be used to value FHIR agents, actors, and other role elements. The codes are intended to express how the agent participated in some activity. Sometimes refered to the agent functional-role relative to the activity.

FamilyMemberHistory.relationship FamilyMember icon Example

A relationship between two people characterizing their "familial" relationship

FamilyMemberHistory.sex AdministrativeGender Extensible

The gender of a person used for administrative purposes.

FamilyMemberHistory.reason SNOMEDCTClinicalFindings Example

This value set includes all the "Clinical finding" SNOMED CT icon codes - concepts where concept is-a 404684003 (Clinical finding (finding)).

FamilyMemberHistory.condition.code ConditionProblemDiagnosisCodes Example

Example value set for Condition/Problem/Diagnosis codes.

FamilyMemberHistory.condition.outcome ConditionOutcomeCodes Example

Example value set for condition outcomes.

FamilyMemberHistory.procedure.code ProcedureCodesSNOMEDCT Example

Procedure Code: All SNOMED CT procedure codes.

FamilyMemberHistory.procedure.outcome SNOMEDCTClinicalFindings Example

This value set includes all the "Clinical finding" SNOMED CT icon codes - concepts where concept is-a 404684003 (Clinical finding (finding)).

UniqueKeyLevelLocationDescriptionExpression
img fhs-1Rule (base)Can have age[x] or born[x], but not bothage.empty() or born.empty()
img fhs-2Rule (base)Can only have estimatedAge if age[x] is presentage.exists() or estimatedAge.empty()
img fhs-3Rule (base)Can have age[x] or deceased[x], but not bothage.empty() or deceased.empty()

The Family Member History List may contain other than FamilyMemberHistory resources. For example, a full Family History could be a List that might include a mixture of FamilyMemberHistory records as well as Observation records of things like "maternal family history of breast cancer", "number of siblings", "number of female family members with breast cancer" etc.

The List representing a patient's "family history" can include Condition and Observation records that capture "family-history" relevant assertions about the patient themselves that would typically be captured as part of a family history.

Not Reviewed, Not Asked

When a sending system does not have family history about any family members or the statement is about family history not yet being asked, then the List resource should be used to indicate the List.emptyReason="notasked".

Reviewed, None Identified for Family

After reasonable investigation that there are no known items for the family member history list, then the List resource should be used to indicate the List.emptyReason="nilknown". The List.emptyReason represents a statement about the full scope of the list (i.e. the patient or patient's agent/guardian has asserted that there are no conditions or significant events for any family members to record).

Reviewed, No Information Available for a Family Member

When an individual family member's history is not available, FamilyMemberHistory.dataAbsentReason can be used to indicate why that family member's history is not available (e.g. subject unknown).

Reviewed, No Known Problems or Negated Condition for a Family Member

The FamilyMemberHistory.condition.code can be used to capture "No Known Problems" or negated conditions, such as "No history of malignant tumor of breast", for an individual family member.

Search parameters for this resource. See also the full list of search parameters for this resource, and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
code token A search by a condition code FamilyMemberHistory.condition.code 21 Resources
date date When history was recorded or last updated FamilyMemberHistory.date 26 Resources
identifier token A search by a record identifier FamilyMemberHistory.identifier 65 Resources
patient reference The identity of a subject to list family member history items for FamilyMemberHistory.patient
(Patient)
65 Resources
relationship token A search by a relationship type FamilyMemberHistory.relationship
sex token A search by a sex code of a family member FamilyMemberHistory.sex
status token partial | completed | entered-in-error | health-unknown FamilyMemberHistory.status