use standard etasu endpoint

[KeeyanGhoreshi]

Describe your changes

Makes use of the standard etasu endpoint on the rems server, replacing old format with new FHIR GuidanceResponse format. Nothing should functionally change other than a couple bits of data being changed or removed, like the case number not showing in the UI anymore or the change in the status language.

Issue ticket number and Jira link

REMS-620

Checklist before requesting a review

• I have performed a self-review of my code
• Ensure the target / base branch for any feature PR is set to dev not main (the only exception to this is releases from dev and hotfix branches)

Checklist for conducting a review

• Review the code changes and make sure they all make sense and are necessary.
• Pull the PR branch locally and test by running through workflow and making sure everything works as it is supposed to.

[plarocque4]

The GuidanceResponse $rems-etasu operation is looking for a Medication resource not a MedicationRequest. Could you please create a Medication resource and send that instead.

[KeeyanGhoreshi]

Is it looking for a medication resource by standard? The PR I made in rems-admin handles med requests.

[plarocque4]

It appears that you didn't update the query that is sent from the page returned from completion of the Patient Enrollment Form. We either need to update this as well or remove the ETASU check from that page.

[plarocque4]

looks good

[plarocque4]

works well