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.
Salient fields
The profile's synthesized-accessor contract: fields TypedFhir surfaces as first-class typed properties, each computed from the instance by a restricted FHIRPath expression. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.
Key
Type
Expression
Rendered as
Description
relationship
coded
relationship
Who the relative is (v3 FamilyMember: MTH, FTH, SIB, ...) i
status
code
status
partial | completed | entered-in-error | health-unknown i
date
dateTime
date
When the history was recorded/updated -- the effective date i
Who the relative is (v3 FamilyMember: MTH, FTH, SIB, ...)
Definition
The type of relationship this person has to the patient (father, mother, brother etc.).
Comments
Extensible: heritage charts may carry local relationship wording as text alongside the coding. Where this code was mapped from a source system's own vocabulary, carry the raw coding alongside the mapped one, flagged userSelected = true. See Carrying the raw code.
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.
Comments
The FIRST condition, as text: its code.text, else the first coding's display. condition is 0..*, and a relative with several recorded conditions surfaces only the first here; the full list is reachable through the typed collection, and a chart that needs every one walks condition rather than reading this. Declared string rather than coded for the same reason AllergyIntolerance's reaction is: a derived expression does not resolve to a typed Concept, so a coded declaration would name a type the accessor does not return.
Deceased flag or the actual or approximate age of the relative at the time of death for the family member history record.
Comments
Whether the relative is deceased, and ONLY the boolean arm of deceased[x]. A record carrying an age or a date of death instead leaves this absent, and absent means the fact was not stated as a boolean rather than that the relative is alive. That value stays on the raw resource.