This page is part of the FHIR Specification (v0.11: DSTU 1 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Resource FamilyHistory - Formal Definitions 4.4.5

Formal definitions for the elements in the familyhistory resource.

FamilyHistory
DefinitionSignificant health events and conditions for people related to the subject relevant in the context of care for the subject.
Control1..1
FamilyHistory.subject
DefinitionThe person who this history concerns.
Control1..1
TypeResource(Patient)
Summarytrue
FamilyHistory.note
DefinitionConveys information about family history not specific to individual relations.
Control0..1
Typestring
FamilyHistory.relation
DefinitionThe related person. Each FamilyHistory resource contains the entire family history for a single person.
Control0..*
FamilyHistory.relation.name
DefinitionThis will either be a name or a description. E.g. "Aunt Susan", "my cousin with the red hair".
Control0..1
Typestring
RequirementsAllows greater ease in ensuring the same person is being talked about.
Summarytrue
FamilyHistory.relation.relationship
DefinitionThe type of relationship this person has to the patient (father, mother, brother etc.) At the moment this is a code linking to a fixed set of values. I'm not sure if there is an international standard for this. A fixed (possibly extensible) set of codes feels better than a codeable concept for something like this...
Control1..1
BindingFamilialRelationship : The nature of the relationship between the patient and the person with the condition. Based on the HL7v3 RoleCode: OID: 2.16.840.1.113883.5.111 with some inappropriate items removed (see http://hl7.org/fhir/familial-relationship for values)
TypeCodeableConcept
Summarytrue
FamilyHistory.relation.deceased[x]
DefinitionIf this resource is indicating that the related person is deceased, then an indicator of whether the person is deceased (yes) or not (no) or the age or age range or description of age at death - can be indicated here. If the reason for death is known, then it can be indicated in the outcome code of the condition - in this case the deceased property should still be set.
Control0..1
Typeboolean|Age|Range|string
FamilyHistory.relation.note
DefinitionThis property allows a non condition-specific note to the made about the related person. Ideally, the note would be in the condition property, but this is not always possible.
Control0..1
Typestring
FamilyHistory.relation.condition
DefinitionThe significant Conditions (or condition) that the family member had. This is a repeating section to allow a system to represent more than one condition per resource, though there is nothing stopping multiple resources - one per condition.
Control0..*
FamilyHistory.relation.condition.type
DefinitionThe actual condition specified. Could be a coded condition (like MI or Diabetes) or a less specific string like 'cancer' depending on how much is known about the condition and the capabilities of the creating system.
Control1..1
TypeCodeableConcept
FamilyHistory.relation.condition.outcome
DefinitionIndicates what happened as a result of this condition. If the condition resulted in death, deceased date is captured on the relation.
Control0..1
BindingConditionOutcome : The result of the condition for the patient. E.g. death, permanent disability, temporary disability, etc.
TypeCodeableConcept
FamilyHistory.relation.condition.onset[x]
DefinitionEither the age of onset, range of approximate age or descriptive string can be recorded.
Control0..1
TypeAge|Range|string
FamilyHistory.relation.condition.note
DefinitionAn area where general notes can be placed about this specific condition.
Control0..1
Typestring