{ "$result_object_key": [ { "created_at": "Timestamp when the allergy record was created.", "id": "Unique identifier for the allergy record.", "name": "Name of the allergen.", "patient_id": "ID of the patient this allergy belongs to.", "reaction": "Description of the allergic reaction.", "severity": "Severity of the allergic reaction.", "start_date": "The date of onset for the allergy." } ]}
v1
Create Allergies
Documentation for the Create Allergies action for Elation
{ "$result_object_key": [ { "created_at": "Timestamp when the allergy record was created.", "id": "Unique identifier for the allergy record.", "name": "Name of the allergen.", "patient_id": "ID of the patient this allergy belongs to.", "reaction": "Description of the allergic reaction.", "severity": "Severity of the allergic reaction.", "start_date": "The date of onset for the allergy." } ]}
You can use the result of the action’s data as inputs to downstream workflow actions.Each fetch action requires a result object key to be specified which will nest the action’s result data inside the downstream data context in the Workflow.Here we demonstrate how to refer to this data using the prefix $result_object_key.