search

drajer-health / eCRNow

Repository for eCRNow app.
Apache License 2.0
39 stars 52 forks source link

Medication Requests in FHIR server not getting pulled in to medicationAdministration section of eICR. #704

Open nmarmelo1 opened 5 months ago

nmarmelo1 commented 5 months ago

We are sending MedicationRequest objects to our FHIR server that reflect patient prescriptions. However, none of these have been present in any of our test scenario TriggerQueryBundles, LoadingQueryBundles, or eICRs. Here is an example of a MedicationRequest response from our FHIR server (Test Scenario #1 Jill Test): JillTest_remdesivir_MedicationRequest_FHIRResponse.json

LoadingQuery: LoadingQueryBundle_JillTest_3-4-2024.json

TriggerQuery: TriggerQueryBundle_JillTest.json

eICR: JillTest_eICR_2024-03-05.txt

We were advised by testing team (Andrew Gabbeit, Deepshika Medapalli) to open a GitHub issue to discover why this is not functioning as expected and if there are any changes we could make to the data we send to the FHIR server so that the medicationAdministration section of eICRs will be populated appropriately. Can provide more information if necessary.

nbashyam commented 4 months ago

Since the data is not present in the bundle, please check the log file to see what query is being run for medicationrequest. There must be something wrong with the query , hence the data is not being returned.

nmarmelo1 commented 4 months ago

Thank you - after reviewing the log, the query below seems to be the issue: https://pc-fhir-stg.amazingcharts.com/fhir/r4/MedicationRequest?patient=Patient/622c3a96-5915-d92b-479f-ebd4e5c43c16&intent='order'

Testing with Postman indicates that the single quotes around 'order' are the reason for the lack of data being returned. The same query executed without the single quotes does indeed return a result. I double checked the MedicationRequest.intent value to confirm that it is 'order'.

I've attached updated files from the test scenario in case they may be of use to you. The MedicationRequest processing starts at line 3382 of ecrNow.log.2024-04-02 Scenario 1 - Jill.zip

nbashyam commented 4 months ago

That should have been addressed in the latest ERSDv2 file. Have you used the latest ERSD file?

mmatiasalt commented 4 months ago

@nmarmelo1 please advise if you have any additional issues after testing latest eRSD V2 file. Thank you

mmatiasalt commented 4 months ago

@nmarmelo1 are you still having issues after testing the latest eRSD V 2 file?

mmatiasalt commented 3 months ago

@nmarmelo1 are you still having issues after testing the latest eRSD V2 File? Can this issue be closed?

Thank you,

mmatiasalt commented 3 months ago

@nmarmelo1 checking to see if you're still having issues after testing latest eRSD V2 file or if we can close issue? Thank you.

nmarmelo1 commented 3 months ago

@mmatiasalt Apologies, I haven't had a chance to confirm if we are still having issues with eRSD V2 file. I believe that we started using that prior to logging this issue. Unfortunately I have been roped in to an alternate (and urgent) project for the past few weeks or so. I will try to get back to you with a solid answer within a few days.

mmatiasalt commented 3 months ago

@nmarmelo1 no worries! Thank you so much for responding.

mmatiasalt commented 2 months ago

@nmarmelo1 are you able to confirm if this issue was resolved? Thank you.

mmatiasalt commented 1 month ago

@nmarmelo1 can you confirm this issue is resolved? May we close this ticket?

mmatiasalt commented 1 month ago

@nmarmelo1 can you confirm this issue is resolved? May we close this ticket?

nmarmelo1 commented 2 weeks ago

I cannot confirm this issue is resolved. I don't have the exact date that we switched to using the eRSD V2 file, but can confirm that it is now in place and have begun re-testing this scenario for Jill Test.