You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please make sure the physicianId is congruent with primaryPhysicianId (primary_physician_id) as it shows up in fields in other places in elation. Do the same with the caregiver_practice_id.
Given Find Physicians works successfully
When I use the provided physicianId or caregiverPracticeId datapoints as inputs for fields in other elation actions
Then there are no errors resulting from an incorrect type
(fyi the physicianUserId datapoint can be used as the "author" field for the chart note)
Thanks!
The text was updated successfully, but these errors were encountered:
(note to everyone... if you write a description and convert to an issue before you save your description, you lose your description)
Problem
It's difficult to find the
primaryPhysicianId
andcaregiverPracticeId
fields, which are necessary for various actionsSolution
Find Physicians action
Acceptance criteria
Leverage the elation api documentation for the uri
Given the ability to add the Find Physicians action to the step
When I add the Find Physicians action
All three query parameters are available as fields (strings are fine, even though the npi number is technically a number)
Given i run the Find Physicians action
When the number of responses != 1
Then provide an error with a message such as "Find Physicians returned {x} results, but the number of results must equal exactly 1."
Given i run the find physicians action
When the number of responses == 1
Then add the following datapoints in onComplete (assuming the result is saved as
result
):Please make sure the physicianId is congruent with primaryPhysicianId (
primary_physician_id
) as it shows up in fields in other places in elation. Do the same with thecaregiver_practice_id
.(fyi the
physicianUserId
datapoint can be used as the "author" field for the chart note)Thanks!
The text was updated successfully, but these errors were encountered: