FHIR Chat · fhircast-docs / Issue #143 May 2019 Ballot Comment: What ... · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / Issue #143 May 2019 Ballot Comment: What ...


view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot opened Issue #143

## May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot labeled Issue #143

## May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot labeled Issue #143

## May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot edited Issue #143

## May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (May 06 2019 at 21:39):

NiklasSvenzen commented on Issue #143

Good point, when there is no context the proposal is to describe returning an empty context:

{
"timestamp":"2018-01-08T01:40:05.14",
"id":"wYXStHqxFQyHFELh",
"event":{
"hub.topic":"https://hub.example.com/7jaa86kgdudewiaq0wtu",
"context":[{}]
}
}

view this post on Zulip Github Notifications (FHIRcast) (May 07 2019 at 20:01):

lbergnehr commented on Issue #143

Would an empty array make more sense than an empty object inside an empty array?

6 maj 2019 kl. 23:39 skrev Niklas Svenzén <notifications@github.com>:

Good point, when there is no context the proposal is to describe returning an empty context:

{
"timestamp":"2018-01-08T01:40:05.14",
"id":"wYXStHqxFQyHFELh",
"event":{
"hub.topic":"https://hub.example.com/7jaa86kgdudewiaq0wtu",
"context":[{}]
}
}


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 01:40):

isaacvetter commented on Issue #143

Would a more elegant answer to this negative issue be that the query for current context should be removed in favor of placing the responsibility for communicating initial contextual information into the SMART app launch parameters (as the spec already says) or, in the case where SMART isn't used, as contextual parameters communicated as part of the launch process (but is outside of the spec) ?

// @NiklasSvenzen, @wmaethner, @wdvr

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 08:24):

lbergnehr commented on Issue #143

Could it be that you still want to get the current context even after launching? I’m thinking e.g. when you think communication failed for some reason.

/ Leo

8 maj 2019 kl. 03:40 skrev Isaac Vetter <notifications@github.com>:

Would a more elegant answer to this negative issue be that the query for current context should be removed in favor of placing the responsibility for communicating initial contextual information into the SMART app launch parameters (as the spec already says) or, in the case where SMART isn't used, as contextual parameters communicated as part of the launch process (but is outside of the spec) ?

// @NiklasSvenzen, @wmaethner, @wdvr


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

view this post on Zulip Github Notifications (FHIRcast) (Jun 04 2019 at 13:50):

isaacvetter commented on Issue #143:

In conversation with @NiklasSvenzen , @lbergnehr , and @wmaethner:

We see three possible options here:
1) Context passed during launch, in launch specific scenario (as described above).
2) An API call to Query-for-Current-Context, which returns the previous context and can be called at any time.
3) Upon subscription get last event.

Overall, the addition of this Query-for-Current-Context web service is pretty complicated. The absence of an event, but the presence of context doesn't really make sense.

Proposed resolution: Persuasive with Mod
Proposed resolution comment:* We will remove the "Query for Current Context" and clarify that the subscriber SHALL receive current contextual information in the form of SMART launch parameters, or if using an alternate launch mechanism, in that launch.

view this post on Zulip Github Notifications (FHIRcast) (Jun 04 2019 at 13:51):

isaacvetter labeled Issue #143:

## May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Jun 04 2019 at 13:52):

isaacvetter edited a comment on Issue #143:

In conversation with @NiklasSvenzen , @lbergnehr , and @wmaethner:

We see three possible options here:
1) Context passed during launch, in launch specific scenario (as described above).
2) An API call to Query-for-Current-Context, which returns the previous context and can be called at any time.
3) Upon subscription get last event.

Overall, the addition of this Query-for-Current-Context web service is pretty complicated. The absence of an event, but the presence of context doesn't really make sense. The community does not yet have enough implementation experience with this web service to justify it going into our STU version of the FHIRcast specification.

Proposed resolution: Persuasive with Mod
Proposed resolution comment:* We will remove the "Query for Current Context" and clarify that the subscriber SHALL receive current contextual information in the form of SMART launch parameters, or if using an alternate launch mechanism, in that launch. Based upon need, we will revisit the existence of this capability.

view this post on Zulip Github Notifications (FHIRcast) (Jul 24 2019 at 14:46):

isaacvetter commented on Issue #143:

Eric Martin points out that the exchange of Observations and Observation states
- The Hub should exactly maintain state for each subscribed client. For launch/simple stuff, this is trivial. For more complex scenarios, the client needs to receive the whole set of events.

Wouter - if current context is an imagingstudy related, does that clear previous events? Patient vs imagingstudy relationship? We should always send the full context for a sync event [and not create a need to infer context based upon previous events].

Jeremy - If the ImagingStudy.open event changes the patient, why have named events at all? Yes, we should be pushing the whole context (including the patient). FHIRcast should simply ensure that the patient in an external system in focus should be brought to the foreground in my system. Eventing makes Hub implementation more difficult. Being able to extend, AI-based measurements into reports is important.

view this post on Zulip Github Notifications (FHIRcast) (Jul 24 2019 at 14:53):

isaacvetter edited a comment on Issue #143:

Eric Martin points out that the exchange of Observations and Observation states
- The Hub should exactly maintain state for each subscribed client. For launch/simple stuff, this is trivial. For more complex scenarios, the client needs to receive the whole set of events.

Wouter - if current context is an imagingstudy related, does that clear previous events? Patient vs imagingstudy relationship? We should always send the full context for a sync event [and not create a need to infer context based upon previous events].

Jeremy - If the ImagingStudy.open event changes the patient, why have named events at all? Yes, we should be pushing the whole context (including the patient). FHIRcast should simply ensure that the patient in an external system in focus should be brought to the foreground in my system. Eventing makes Hub implementation more difficult. Being able to extend, AI-based measurements into reports is important. If "Query for Current Context" returns only last event and not "full state", this API would not be as useful.

@gkustas - a getLatestEvent function seems useful. Would be okay removing for further discussion. Would simply want to know what patient/study are open. We oughn't lump draft measurements into this one method.

Topics for further analysis:
- What is the difference between _state_ and _context_?
- How should FHIRcast enable draft measurement exchange?
- ... ?

view this post on Zulip Github Notifications (FHIRcast) (Jul 24 2019 at 14:57):

isaacvetter commented on Issue #143:

## :telephone_receiver: II Working Group Vote (5-30-2019)

Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences

@isaacvetter moved the following disposition, seconded by Bill Wallace

Disposition: Persuasive with Mod
Disposition Comment: We will remove the "Query for Current Context" and clarify that the subscriber SHALL receive current contextual information in the form of SMART launch parameters, or if using an alternate launch mechanism, in that launch. Based upon need, we will revisit the existence of this capability. We will look to add a some type of functionality to STU2.

:+1: For: 12
:expressionless: Abstain: 2
:-1: Against: 0

:tada: The motion passed! :tada:

view this post on Zulip Github Notifications (FHIRcast) (Jul 24 2019 at 14:57):

wmaethner labeled Issue #143:

## May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Aug 19 2019 at 15:25):

isaacvetter labeled Issue #143:

May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Sep 03 2019 at 21:58):

isaacvetter closed Issue #143:

May 2019 Ballot Comment: What is the response to "Query for Current Context" when there is no current context?

Submitted by Ricardo Quintano Neira
Chapter/section: Query for Current Context
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Enhancement

Summary: What is the response to "Query for Current Context" when there is no current context?

Comment: What is the response to "Query for Current Context" when there is no current context?

I recommend describing more details and add an example.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._


Last updated: Apr 12 2022 at 19:14 UTC