2nd DSTU Draft For Comment

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

4.29.4 Resource FamilyHistory - Detailed Descriptions

Detailed Descriptions for the elements in the FamilyHistory resource.

FamilyHistory
Definition

Significant health events and conditions for people related to the subject relevant in the context of care for the subject.

Control1..1
FamilyHistory.identifier
Definition

This records identifiers associated with this family history record that are defined by business processes and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

Summarytrue
FamilyHistory.patient
Definition

The person who this history concerns.

Control1..1
TypeReference(Patient)
Alternate NamesProband
Summarytrue
FamilyHistory.date
Definition

The date (and possibly time) when the family history was taken.

Control0..1
TypedateTime
Requirements

Allows determination of how current the summary is.

Summarytrue
FamilyHistory.note
Definition

Conveys information about family history not specific to individual relations.

Control0..1
Typestring
FamilyHistory.relation
Definition

The related person. Each FamilyHistory resource contains the entire family history for a single person.

Control0..*
InvariantsDefined on this element
fhs-1: Can have age[x] or birth[x], but not both (xpath: not (*[starts-with(local-name(.), 'age')] and *[starts-with(local-name(.), 'birth')]))
FamilyHistory.relation.name
Definition

This will either be a name or a description. E.g. "Aunt Susan", "my cousin with the red hair".

Control0..1
Typestring
Requirements

Allows greater ease in ensuring the same person is being talked about.

Summarytrue
FamilyHistory.relation.relationship
Definition

The type of relationship this person has to the patient (father, mother, brother etc.).

Control1..1
BindingFamilialRelationship: The nature of the relationship between the patient and the related person being described in the family history (Preferred)
TypeCodeableConcept
Summarytrue
FamilyHistory.relation.born[x]
Definition

The actual or approximate date of birth of the relative.

Control0..1
TypePeriod|date|string
Requirements

Allows calculation of the relative's age.

InvariantsAffect this element
fhs-1: Can have age[x] or birth[x], but not both (xpath: not (*[starts-with(local-name(.), 'age')] and *[starts-with(local-name(.), 'birth')]))
FamilyHistory.relation.age[x]
Definition

The actual or approximate age of the relative at the time the family history is recorded.

Control0..1
TypeAge|Range|string
Requirements

While age can be calculated from date of birth, sometimes recording age directly is more natureal for clinicians.

InvariantsAffect this element
fhs-1: Can have age[x] or birth[x], but not both (xpath: not (*[starts-with(local-name(.), 'age')] and *[starts-with(local-name(.), 'birth')]))
FamilyHistory.relation.deceased[x]
Definition

If 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|date|string
FamilyHistory.relation.note
Definition

This 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
Definition

The 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
Definition

The 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
Definition

Indicates 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]
Definition

Either the age of onset, range of approximate age or descriptive string can be recorded. For conditions with multiple occurrences, this describes the first known occurrence.

Control0..1
TypeAge|Range|string
Requirements

Age of onset of a condition in relatives is predictive of risk for the patient.

To DoDefine/find appropriate observation code.
FamilyHistory.relation.condition.note
Definition

An area where general notes can be placed about this specific condition.

Control0..1
Typestring