FHIR Chat · Subscriptions on history · fhir/infrastructure-wg

Stream: fhir/infrastructure-wg

Topic: Subscriptions on history

Josh Mandel (Jan 17 2019 at 20:42):

(for those in our meeting right now)

{
  "resourceType": "Subscription",
  "historyCriterion": {
    "interaction": ["create", "update", "delete"],
    "filter": "$current.patient == '123' or $previous.patient == '123'"
  }
}

Josh Mandel (Jan 17 2019 at 20:46):

(This was meant to be an example of a constrained/simple syntax for subscribing to a filtered history of events on a server. It would be an alternative to searchCriterion which subscribes to a search result list, or eventCriterion which subscribes to named events like V2 messages.)

Isaac Vetter (Jan 17 2019 at 20:54):

Here's an example of the extension we prototyped to add events to subscriptions in late 2017: http://wiki.hl7.org/index.php?title=201709_FHIR_Subscriptions#example-subscription-resource-with-proposed-extension

Isaac Vetter (Jan 17 2019 at 20:55):

The advantages of this indirection is that it allows a server to advertise which events (in the form of EventDefinitions) in the case where a FHIR server can't support the full, rich complexity of FHIRpath event definitions.

Isaac Vetter (Jan 17 2019 at 20:56):

I'd wonder if there's also authorization considerations for authorizing an app to subscribe to a FHIRpath defined event.

Josh Mandel (Jan 17 2019 at 20:56):

Always!

Grahame Grieve (Jan 17 2019 at 22:03):

@Ewout Kramer where are the FHIR-I minutes?

Grahame Grieve (Jan 17 2019 at 22:41):

My sentence: Main focus points include: Reviewing CapabilityStatement design (trial use parts); Managing Composition content (e.g. GraphDefinition...), Subscriptions, and Digital Signatures

Last updated: Apr 12 2022 at 19:14 UTC

Main menu