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

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).

Need to allow connection to a wider workflow.

The person who A protocol or questionnaire that was adhered to in whole or in part by this history concerns. event.

A code specifying the status of the record of the family history of a specific family member.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

The date (and possibly time) when If true, indicates the taking of an individual family member member's history was taken. did not occur. The notDone element should not be used to document negated conditions, such as a family member that did not have a condition.

Allows determination of how current Creating a FamilyMemberHistory where notDone is true is intended for situations where there's a need for a specific statement in the summary is. record about something not being done. If the need is merely to indicate that a request wasn't fulfilled, that should be handled using Task.

This should be captured even if the same element is labeled as a modifier because it marks the date on family member history as a family member history that did not occur. The more attributes are populated, the List aggregating more constrained the full family history. negated statement is. This notDone element is being evaluated and will likely be removed in a subsequent release.

A code specifying a state of a Family Member History record. Describes why the family member's history is absent.

This is a separate element to allow it to have a distinct binding from reasonCode.

This notDoneReason element is being evaluated and will likely be replaced in a subsequent release (e.g. dataAbsentReason).

The person who this history concerns.

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

Allows determination of how current the summary is.

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

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

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

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

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

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

The actual or approximate date of birth of the relative.

Allows calculation of the relative's age.

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

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

use estimatedAge to indicate whether the age is actual or not.

If true, indicates that the age value specified is an estimated value.

Clinicians often prefer to specify an estimaged age rather than an age range.

This element is labeled as a modifier because the fact tha age is estimated can/should change the results of any algorithm that calculates based on the specified age.

Deceased flag or the actual or approximate age of the relative at the time of death for the family member history record.

Describes why the family member history occurred in coded or textual form.

Textual reasons can be caprued using reasonCode.text.

Indicates a Condition, Observation, AllergyIntolerance, or QuestionnaireResponse that justifies this family member history event.

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.

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.

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.

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.

Indicates what happened as a result of this condition. If the condition resulted in death, deceased date is captured on the relation.

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.

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

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