DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.28.5 Resource FamilyMemberHistory - Detailed Descriptions

Detailed Descriptions for the elements in the FamilyMemberHistory resource.

FamilyMemberHistory
Definition

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

Control1..1
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')]))
FamilyMemberHistory.identifier
Definition

This records identifiers associated with this family member 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).

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

FamilyMemberHistory.patient
Definition

The person who this history concerns.

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

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

Control0..1
TypedateTime
Requirements

Allows determination of how current the summary is.

Summarytrue
Comments

This should be captured even if the same as the date on the List aggregating the full family history.

FamilyMemberHistory.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
FamilyMemberHistory.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 member history (Required)
TypeCodeableConcept
Summarytrue
FamilyMemberHistory.gender
Definition

Administrative Gender - the gender that the relative is considered to have for administration and record keeping purposes.

Control0..1
BindingAdministrativeGender: Required: http://hl7.org/fhir/administrative-gender (The gender of a person used for administrative purposes)
Typecode
Requirements

Not all relationship codes imply gender and the relative's gender can be relevant for risk assessments.

Summarytrue
FamilyMemberHistory.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')]))
FamilyMemberHistory.age[x]
Definition

The actual or approximate age of the relative at the time the family member 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')]))
FamilyMemberHistory.deceased[x]
Definition

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

Control0..1
Typeboolean|Age|Range|date|string
FamilyMemberHistory.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
FamilyMemberHistory.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..*
Comments

If none of the conditions listed have an outcome of "death" specified, that indicates that none of the specified conditions are known to have been the primary cause of death.

FamilyMemberHistory.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
FamilyMemberHistory.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
FamilyMemberHistory.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.
FamilyMemberHistory.condition.note
Definition

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

Control0..1
Typestring