Documentation Index Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt
Use this file to discover all available pages before exploring further.
Morf’s Healthie Create Or Update Referring Provider action uses backend logic to avoid creating duplicate referring providers.
Deduplication Logic If no referring provider ID is specified in the node configuration, Morf will:
List all organization referring physicians already stored in Healthie, filtered to those with first and last names.
Check if any existing referring physician matches by city, state, and business name — but only if that information is included in the node. A referring physician must match all criteria provided in the node to be updated.
If a match is found, update that referring physician. Otherwise, create a new one.
Parameters This field maps to the destination API id field.
This field maps to the destination API first_name field.
This field maps to the destination API last_name field.
This field maps to the destination API location.city field.
This field maps to the destination API location.state field.
This field maps to the destination API specialty field.
This field maps to the destination API business_name field.
This field maps to the destination API phone_number field.
This field maps to the destination API email field.
National Provider Identifier
This field maps to the destination API npi field.
This field maps to the destination API fax_number field.
{ "$result_object_key" : { "business_name" : "Dr. John" , "created_at" : "2024-05-10T08:46:04Z" , "email" : "john.doe@example.com" , "first_name" : "John" , "full_name" : "John Doe" , "id" : "57211" , "last_name" : "Doe" , "location" : { "city" : "San Francisco" , "country" : "USA" , "line1" : "123 Main Street" , "line2" : "Suite 100" , "state" : "CA" , "zip" : "94117" }, "npi" : "1000321231" , "phone_number" : "+15551234123" } }
Result Object Description
{ "$result_object_key" : { "business_name" : "Provider's business name" , "created_at" : "Provider's creation date" , "email" : "Provider's email" , "first_name" : "Provider's first name" , "full_name" : "Provider's full name" , "id" : "Provider ID" , "last_name" : "Provider's last name" , "location" : { "city" : "City" , "country" : "Country" , "line1" : "First line of the address" , "line2" : "Second line of the address" , "state" : "State" , "zip" : "Zip code" }, "npi" : "Provider's NPI" , "phone_number" : "Provider's phone number" } }
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.
ReferringProvider
Fetch Action Response Object
PII Provider’s first name$result_object_key.first_name
PII Provider’s last name$result_object_key.last_name
PII Provider’s location$result_object_key.location
{ "city" : "San Francisco" , "country" : "USA" , "line1" : "123 Main Street" , "line2" : "Suite 100" , "state" : "CA" , "zip" : "94117" }
First line of the address $result_object_key.location.line 1
Second line of the address $result_object_key.location.line 2
City $result_object_key.location.city
State $result_object_key.location.state
Zip code $result_object_key.location.zip
Country $result_object_key.location.country
created_at
timing.v1.Timestamp
required
Provider’s creation date $result_object_key.created_at
PII Provider’s business name$result_object_key.business_name
PII Provider’s phone number$result_object_key.phone_number
PII Provider’s full name$result_object_key.full_name
