FHIR Chat · Electronic Case Reporting

Stream: connectathon mgmt

Topic: Electronic Case Reporting

Grahame Grieve (Dec 23 2017 at 21:55):

@Rick Geimer I'm reading the eCR track, and it feels as though the scenarios are under-specified. I'm not exactly sure how far this is envisaged to go with regard to 'triggering' - more than just exchanging vale sets? Also, please ask John L to join us here.

Rick Geimer (Jan 27 2018 at 16:17):

Connectathon 17 thread starter

Rick Geimer (Jan 27 2018 at 16:18):

The trigger code Bundle is available at Grahame's server here:
http://test.fhir.org/r3/Bundle/rctc

Sarah Gaunt (Jan 27 2018 at 16:19):

So it is supposed to be R3?

Grahame Grieve (Jan 27 2018 at 16:22):

Isn't the guide an R3 guide?

Sarah Gaunt (Jan 27 2018 at 16:30):

Yes, I just checked - that's what it says in the spec.

Sarah Gaunt (Jan 27 2018 at 16:30):

So @Rick Geimer that means we need to get the composition posted up to R3. Which makes me think there is something wrong with slicing on @Grahame Grieve 's R3 server?

Sarah Gaunt (Jan 27 2018 at 16:31):

Seeing as it posted to R4 without any issues?

Sarah Gaunt (Jan 27 2018 at 16:51):

@Grahame Grieve When you have some time (hahahaha!) could we chat about the slicing issue I'm having on your R3 server? Not sure if it's a problem with 1. the structuredefinition, 2. your server 3. my xml...

Rick Geimer (Jan 27 2018 at 16:51):

Sample Subscription for retrieving the RCTC value set Bundle:

<?xml version="1.0" encoding="UTF-8"?>
<Subscription xmlns="http://hl7.org/fhir">
<status value="requested"/>
<contact>
<system value="email"/>
<value value="rick.geimer@lantanagroup.com"></value>
</contact>
<reason value="Case Reporting: Trigger Codes Updated"/>
<criteria value="Bundle?_id=rctc"/>
<channel>
<type value="email"/>
<endpoint value="mailto:rick.geimer@lantanagroup.com"/>
<payload value="application/fhir+json"/>
</channel>
</Subscription>

Rick Geimer (Jan 27 2018 at 16:54):

Verified that the above Subscription works with the email channel.

Rick Geimer (Jan 27 2018 at 17:04):

Here is the URL for the Subscription on Grahame's server:
http://test.fhir.org/r3/Subscription/1

Grahame Grieve (Jan 27 2018 at 17:18):

I will come look at the slicing soon

Sarah Gaunt (Jan 27 2018 at 17:18):

Tx!

Rick Geimer (Jan 27 2018 at 21:39):

Can try subscription on vonk as well. Post to http://vonk.furore.com/Subscription

Rishi Tarar (Jan 28 2018 at 14:20):

We also verified the rest-hook pattern for subscription yesterday. The Notifications worked as expected and the resource bundle was delivered as a POST to the callback url for the rest hook. There are however some clarifications needed on the purpose of a Subscription Notification without a payload. Meaning as a consumer you got a POST on the the callback with and empty payload.

Grahame Grieve (Jan 28 2018 at 14:21):

that's what should happen, yes:

Grahame Grieve (Jan 28 2018 at 14:22):

"The mime type to send the payload in - either application/fhir+xml, or application/fhir+json. If the payload is not present, then there is no payload in the notification, just a notificatio"

Rishi Tarar (Jan 28 2018 at 14:22):

What should a consumer do with such a notification...

Rishi Tarar (Jan 28 2018 at 14:23):

I know it depends on the usecases.. but are there any examples on how others are using this empty notification

Grahame Grieve (Jan 28 2018 at 14:24):

it's most useful for webhooks - if you get a ping on a webhook channel, you know to do something useful

Grahame Grieve (Jan 28 2018 at 14:24):

in general, if you don't find such a notification useful, you shouldn't ask for it

Grahame Grieve (Jan 28 2018 at 14:24):

the key thing that makes it really useful is that it's subject to way less security concerns

Rishi Tarar (Jan 28 2018 at 14:28):

understood , the call back URL on consumer side can only be registered to one subscriptions 1 to 1. Also the consumer must be "aware" and handle these empty callbacks equals some thing happened to the subscription resource this callback url is tied to.. and must maintain some kind of explicit process to do that ... I am thinking that in case of various subscriptions it could get hairy

Grahame Grieve (Jan 28 2018 at 14:28):

yep. obviously much more convenient to get the content. But against that must be weighed the security consequences; hence we define both options, and leave it to the implementers to make appropriate chjoices