Skip to content

Family Member History Profile

Canonical../StructureDefinition/nexus-emr-core-familymemberhistory
Statusdraft (experimental) · 1.26.0
BaseFamilyMemberHistory (constraint)
SourceFSH · JSON

Nexus EMR profile for FamilyMemberHistory -- family history as discrete chart content for summaries and extraction output. First pass: one relative, coded relationship, condition list with onset. Closed to SMART apps pending an exposure decision.

TypedFhir API / Python

The typed accessor surface FamilyMemberHistory exposes for FamilyMemberHistory — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.

class FamilyMemberHistory(ClinicalResource)generated source

Accessor Type Access Notes
effective_date FuzzyDate | None read-only The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f…
display str | None read-only The resource's human headline — a coded concept's label, else a title / name, else undefined.
status str | None read/write partial | completed | entered-in-error | health-unknown
data_absent_reason Concept | None read/write · raw twin subject-unknown | withheld | unable-to-obtain | deferred
patient Reference | None read/write · raw twin The patient whose family history this is
date FuzzyDate | None read/write When the history was recorded/updated -- the effective date
relationship Concept | None read/write · raw twin Who the relative is (v3 FamilyMember: MTH, FTH, SIB, ...)
sex Concept | None read/write · raw twin male | female | other | unknown
reason_code Concepts read/write · raw twin Why was family member history performed?
condition dict[] | None read/write Conditions the relative had