pharmacist bundle #18
Conversation
| priorAuthBundle.signature = signature; | ||
| priorAuthBundle.entry.unshift({ resource: priorAuthClaim }); | ||
|
|
||
| const specialtyRxBundle = JSON.parse(JSON.stringify(priorAuthBundle)); |
There was a problem hiding this comment.
Is there a reason to keep the priorAuthBundle around? Can we just remove it and use the specialtyRxBundle exclusively or does REMS have some use for the priorAuthBundle?
There was a problem hiding this comment.
I think its nice to show the synergy between the two but its ultimately not a part of this use case
| const specialtyRxBundle = JSON.parse(JSON.stringify(priorAuthBundle)); | ||
| specialtyRxBundle.type = "message"; | ||
| if (this.makeReference(priorAuthBundle, "MedicationRequest")) { | ||
| const pharmacy = { |
There was a problem hiding this comment.
This is probably a broader question but how is DTR supposed to know where to send this bundle? Will it be a config option or is it supposed to be dynamic and passed in when the app launches? Theoretically this resource or the MessageHeader should have the info on where to send it.
There was a problem hiding this comment.
for now hard code it to send to the the PIS system at the following url:
localhost:3010/api/doctorOder/FHIR
| } | ||
|
|
||
| const specialtyRxMessageHeader = { | ||
| resourceType: "MessageHeader", |
There was a problem hiding this comment.
MessageHeader is missing required source field
There was a problem hiding this comment.
discussed at meeting, will be added in as part of REMS-86
send message
No description provided.