325 RxStatus

[zacharyrobin]

Describe your changes

Note: Should be tested with the 325-RxStatus branch in request-generator (mcode/request-generator#90). You may also need to cd in to backend of pims and run an npm install to get the XML parser.

• Added RxStatus Response when NewRx is received
• Reviewed NCPDP SCRIPT guidelines and determined RxStatus is only used as a response protocol and should not be stored in EHR, rather is used for notifying the EHR that the NewRx was received and processed

To test, go through workflow, after sending Rx to Pharmacy, check the pims backend logs for RxStatus, should be sent right after NewRx is received.

...yes, Prettier is giving me the business

Issue ticket number and Jira link

REMS-325

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.

Workflow

Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.