Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elation: Find Physician #107

Closed
bejoinka opened this issue Apr 26, 2023 · 0 comments · Fixed by #109
Closed

Elation: Find Physician #107

bejoinka opened this issue Apr 26, 2023 · 0 comments · Fixed by #109
Assignees
Labels
enhancement New feature or request extension Related to a specific extension

Comments

@bejoinka
Copy link
Contributor

bejoinka commented Apr 26, 2023

(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 and caregiverPracticeId fields, which are necessary for various actions

Solution

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):

physicianId: result.id,
physicianFirstName: result.first_name,
physicianLastName: result.last_name,
physicianCredentials: result.credentials,
physician.email: result.email,
physicianNPI: result.npi,
physicianUserId: result.user_id
caregiverPracticeId: result.practice

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!

@bejoinka bejoinka added enhancement New feature or request extension Related to a specific extension labels Apr 26, 2023
This was referenced Apr 26, 2023
@michal-grzelak michal-grzelak self-assigned this Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request extension Related to a specific extension
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants