Family Member History Profile

Canonical	../StructureDefinition/nexus-emr-core-familymemberhistory
Status	draft (experimental) · 1.26.0
Base	FamilyMemberHistory (constraint)
Source	FSH · 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 / TypeScript

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 extends ClinicalResource — generated source

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