Adds Hyper Unlucky as the fill field patient for most* demo cases
Adds Public HAPI: Direct connections
Makes Public HAPI: Direct connection the default FHIR Server
Standardizes URL formation (Patient originally did not start with /, which led to some funkiness when building FHIR URLs)
Made some improvements to the e2e flow (pulling the test URL into an env var, adding video playback to CI) to fix some test timeout issues
We suspect that Public HAPI might be a bit slow, so we may want to set up our own FHIR server to have more control over our testing / demo environment.
Related Issue
Fixes #2646
Acceptance Criteria
Please copy the acceptance criteria from your ticket and paste it here for your reviewer(s)
Additional Information
How do we want to handle the standard Newborn? For example, if we were to switch to Hyper Unlucky for everything, as is done for the other cases, what happens is that all the newborn screening data is returned. Do we need to create at least 1 other distinct patient to show a pass/referall/fail? Or update Hyper Unlucky to only have one newborn screening, then just have Mango/Watermelon/Cucumber in our back pocket in case we need to show a pass/referral/fail?
How do we want to handle the socialHistoryQuery in CustomQuery.ts? In our other patient data, we did not have social history data, so to mimic existing demo displays, I commented it out so that the social determinants of health were not present. Is it better to display them?
Unrelated, but having some trouble with the e2e tests. If I run them individually, they pass. If I replicate them, they pass. But running the full script, 4 fail. Running on GitHub Actions, 6 fail. very confusing.
Checklist
[ ] If this code affects the other scrum team, have they been notified? (In Slack, as reviewers, etc.)
PULL REQUEST
Summary
/, which led to some funkiness when building FHIR URLs)Related Issue
Fixes #2646
Acceptance Criteria
Please copy the acceptance criteria from your ticket and paste it here for your reviewer(s)
Additional Information
socialHistoryQueryinCustomQuery.ts? In our other patient data, we did not have social history data, so to mimic existing demo displays, I commented it out so that the social determinants of health were not present. Is it better to display them?Unrelated, but having some trouble with the e2e tests. If I run them individually, they pass. If I replicate them, they pass. But running the full script, 4 fail. Running on GitHub Actions, 6 fail. very confusing.
Checklist