Events
- Active Campaign
- Acuity
- Axle Health
- Butterfly Labs
- Calendly
- Customer.io
- Elation
- Feathery
- Formsort
- Healthie
- Hubspot
- IntakeQ
- Junction
- Morf
- Segment
Actions
- Active Campaign
- Customer.io
- Facebook
- Freshdesk
- Google
- Healthie
- v1
- Append To Patient Quick Notes
- Complete Task
- Create Allergy Sensitivity
- Create Appointment
- Create Billing Item
- Create Conversation
- Create Document
- Create Family History
- Create Invoice
- Create Metric Entry
- Create Or Update Form Answer Group
- Create Or Update Insurance Policy
- Create Or Update Notification Contact
- Create Or Update Patient
- Create Or Update Patient Location
- Create Or Update Referring Provider
- Create Patient Stripe Credit Card
- Create Patient Stripe Credit Card V2
- Create Referral
- Create Requested Form Completion
- Create Task
- Get Appointment
- Get Onboarding Flow
- Get User
- List Appointments For Patient
- List Insurance Plans
- List Requested Form Completion
- Lock Form Answer Group
- Search Metric Entries
- Search Users
- Send Form Request Reminder
- Update Appointment
- Update Client Source
- Update Metric Entry
- Update Patient
- Update Patient Weight
- Update Tags
- v2
- Hubspot
- IntakeQ
- Intercom
- Mixpanel
- Morf
- Nextdoor
- Open Phone
- Segment
- Slack
- Spruce
- Stedi
- Stripe
- Tiktok
- Twilio
Create Referral
Documentation for the Create Referral action for Healthie
{
"$result_object_key": {
"id": "57211",
"metadata": {
"priority": "High",
"referral_department": "Cardiology"
},
"patient_id": "67890",
"referral_reason": "Follow-up care",
"referring_physician_id": "12345"
}
}
{
"$result_object_key": {
"id": "The unique identifier of the referral",
"metadata": "Metadata",
"patient_id": "ID of the referred patient",
"referral_reason": "The reason the client was referred to the physician",
"referring_physician_id": "ID of the referring physician"
}
}
Parameters
ID
PII
This field maps to the destination API metadata
field.
HI
This field maps to the destination API referral_reason
field.
ID
This field maps to the destination API referring_physician_id
field.
ID
This field maps to the destination API user_id
field.
{
"$result_object_key": {
"id": "57211",
"metadata": {
"priority": "High",
"referral_department": "Cardiology"
},
"patient_id": "67890",
"referral_reason": "Follow-up care",
"referring_physician_id": "12345"
}
}
{
"$result_object_key": {
"id": "The unique identifier of the referral",
"metadata": "Metadata",
"patient_id": "ID of the referred patient",
"referral_reason": "The reason the client was referred to the physician",
"referring_physician_id": "ID of the referring physician"
}
}
Result Object Field Details
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
.
The unique identifier of the referral
$result_object_key.id
"57211"
Metadata
$result_object_key.metadata
{
"priority": "High",
"referral_department": "Cardiology"
}
The reason the client was referred to the physician
$result_object_key.referral_reason
"Follow-up care"
ID of the referring physician
$result_object_key.referring_physician_id
"12345"
ID of the referred patient
$result_object_key.patient_id
"67890"
{
"$result_object_key": {
"id": "57211",
"metadata": {
"priority": "High",
"referral_department": "Cardiology"
},
"patient_id": "67890",
"referral_reason": "Follow-up care",
"referring_physician_id": "12345"
}
}
{
"$result_object_key": {
"id": "The unique identifier of the referral",
"metadata": "Metadata",
"patient_id": "ID of the referred patient",
"referral_reason": "The reason the client was referred to the physician",
"referring_physician_id": "ID of the referring physician"
}
}