FHIR Chat · Subscription Payload missing · hapi

Stream: hapi

Topic: Subscription Payload missing


view this post on Zulip dsh (May 02 2021 at 06:25):

I am using HAPI 5.3 and the subscription resource below never sends the payload, it only sends notification with resource ID

{
  "resourceType": "Subscription",
  "id": "810395062",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2021-05-01T14:03:48.135+00:00",
    "source": "#oRbG9W73IDtbQi7G",
    "tag": [ {
      "system": "http://hapifhir.io/fhir/StructureDefinition/subscription-matching-strategy",
      "code": "DATABASE",
      "display": "Database"
    } ]
  },
  "status": "active",
  "reason": "CareTeam assignment to be handled directly by app",
  "criteria": "CareTeam?identifier:not=MCH@",
  "channel": {
    "type": "rest-hook",
    "endpoint": "https://xxxxxx.loca.lt/",
    "payload": "application/fhir+json",
    "header": [ "Authorization: Bearer xxxxxxxxxx" ]
  }
}

I have tried various combination and various settings in application.yml to absolutely no avail. I even tried the same Subscription on hapi.fhir.org/baseR4 but even then I received only notification.

@Lloyd McKenzie @James Agnew Any idea on what can I do to make HAPI send payload along on Subscription notification.

view this post on Zulip Vibin_chander (May 02 2021 at 07:06):

this seems like a new feature. I see this been reported by many. But not sure how it will help if it only sends notification with resource ID

view this post on Zulip dsh (May 02 2021 at 20:11):

Seems like a PR was submitted to fix this issue https://github.com/hapifhir/hapi-fhir/pull/1357/files and it was even merged but later the code was removed @James Agnew please comment on what's the possible path forward

view this post on Zulip dsh (May 02 2021 at 21:17):

@Sean McIlvenna any insights on Subscription payload problem ? ^^

view this post on Zulip James Agnew (May 03 2021 at 18:00):

That subscription looks right to me. You could try putting a breakpoint in SubscriptionDeliveringRestHookSubscriber to see if you can figure out why it's not doing what you expect

view this post on Zulip dsh (May 03 2021 at 18:07):

@James Agnew seems like PR had caused bunch of downstream regressions and was yanked ... it seems from your comment here https://github.com/hapifhir/hapi-fhir/pull/1357#issuecomment-521616804

view this post on Zulip dsh (May 03 2021 at 18:10):

plus I am not a Java guy and won't even know how to run HAPI in debug mode to find problem with SubscriptionDeliveringRestHookSubscriber any instructions ? or can u call some resources to look into this as this is becoming a show stopper for us and we are implementing a workaround using Mirth --> CDR --> Mirth to relay CDR's response to POST/PUT/DELETE of some resources to --> AWS SNS/SQS --> Our App

view this post on Zulip dsh (May 03 2021 at 18:14):

that does look like quite a painful way to avoid what seems like a bug in SubscriptionDeliveringRestHookSubscriber @James Agnew

view this post on Zulip James Agnew (May 03 2021 at 18:54):

If you don't have anyone available who can work with the codebase, certainly another option would be to sign up for a support contract and someone from our team could work with your team on troubleshooting.

view this post on Zulip dsh (May 03 2021 at 18:56):

@James Agnew my apologies for the confusion I just found the payload was being sent on all POST/PUT

request.raw_post

(RubyOnRails) ^

obviously it cannot be sent on DELETE for which we probably need some kind of interceptor


Last updated: Apr 12 2022 at 19:14 UTC