-
Notifications
You must be signed in to change notification settings - Fork 1
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
align customize query flow to design #17
Conversation
@@ -75,7 +75,7 @@ export class CustomQuery { | |||
: ""; | |||
this.medicationRequestQuery = | |||
rxnormFilter !== "" | |||
? `/MedicationRequest?subject=${patientId}&code=${rxnormFilter}&_include=MedicationRequest:medication&_include=MedicationRequest:medication.administration` | |||
? `/MedicationRequest?subject=${patientId}&code=${rxnormFilter}&_include=MedicationRequest:medication&_include=MedicationRequest:intended-performer` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason, Public HAPI didn't like medication.administration
as an includes param, which was breaking the inclusion of the medication requests for the patient. I did a bit of sparse googling and think this is the closest of the provided options below from the error message but if someone knows better lmk and I'm happy to change it.
Invalid _include parameter value: "MedicationRequest:medication.administration". Unknown search parameter "medication.administration" for resource type "MedicationRequest". Valid search parameters for this search are: [encounter, intended-dispenser, intended-performer, medication, patient, requester, subject]
}); | ||
}); | ||
|
||
test("query/test page loads", async ({ page }) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleted these since we removed the test page flow as discussed here
ab92642
to
dd038d1
Compare
…gov/dibbs-query-connector into bob/2663-query-flow-redirect
@@ -0,0 +1,81 @@ | |||
import { test, expect } from "@playwright/test"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this whole page is just a copy-paste from the existing file to help parallelize the playwright runners
import { TEST_URL } from "../playwright-setup"; | ||
import { metadata } from "@/app/constants"; | ||
|
||
test("landing page loads", async ({ page }) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this whole page is just a copy-paste from the existing file to help parallelize the playwright runners
closing in favor of #25 |
PULL REQUEST
Summary
Breaks the query flow into the intended four step process by
SelectQuery
/ their own hooks file.Related Issue
After all the demo v0 pages are implemented independently, ensure that the pages link to one another according to the user flow that Michelle put together
Fixes #2663
Acceptance Criteria
For design
Step 1 Patient discovery
Step 2 Patient Selection
Step 3 Query Selection
Step 4 Patient Record shouldn't have changed