Discovery: Meet with engineers to determine needs around FHIR Path UI tool

[jakefishbein-navapbc]

Problem Statement

Existing CLI tool for onboarding engineers to test messages with specific transforms. We want to make that process easier for onboarding engineers by creating a UI. THIS IS DISCOVERY WORK.

Acceptance Criteria

• [x] Engineering purpose of testing FHIR Paths documented (reason why they do it)
• [x] Documented existing flow of what they do
• [x] Identify how often this is being done
• [x] Identify what parts of the process can be improved and what the quantifiable impact of those improvements could be
• [x] Determine how/if this can be included in the UI/functionality for the existing Message Testing Improvement work or if it should be a separate tool/interface

[jakefishbein-navapbc]

Notes from conversation with Ott.

[chris-kuryak]

From Jake: Likely doesn't need to be solved in our message testing UI

[chris-kuryak]

We have a meeting/sync with Josh (currently working on FHIR path error messaging) today.

[jillian-hammer]

is this considered done? @jakefishbein-navapbc