This resource contains health conditions for a person related to a patient that may be relevant to the patient’s care. The history may be very specific or not, depending on the level of disclosure by the patient. One resource contains details for one individual, not a patient’s entire family.
You can receive, retrieve, or save family history details for a related person.
$write
This operation allows you to save new or updated clinical condition details for a person related to a patient that you’re interacting with or treating.
cURL request example
Request Body Schema
- resourceTyperequired, string
Identifies the type of the resource
Value:Bundle
- typerequired, string
Identifies this bundle as a message
Value:message
- entryrequired, Array of MessageHeader, Patient, FamilyMemberHistory or Other
An array of FHIR resources. At a minimum, a Family Member History should include the following entries:
- Patient - the patient
- FamilyMemberHistory - the family member history as it relates to the patient
- resourcerequired, object
Additional metadata about the message including the event
- resourceTyperequired, string
Identifies the type of the resource
Value:MessageHeader
- sourcerequired, object
Information about the sender of the message. This will typically be populated by Redox.
- endpointrequired, string
Identifies the routing target to send acknowledgements to.
- namestring
Human-readable name for the source system.
- eventCodingrequired, object
This describes the message being communicated
- systemstring
The identification of the code system that defines the meaning of the symbol in the code.
- codestring
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Value:FamilyMemberHistory-New
An entry in the bundle containing a FHIR resource
- timestampstring
The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle.