Stream: fhircast-github
Topic: fhircast-docs / Issue #119 May 2019 Ballot Comment: Provi...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #119
## May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot labeled Issue #119
## May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot edited Issue #119
## May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 30 2019 at 03:02):
isaacvetter commented on Issue #119:
Proposed Resolution: Not Persuasive
Proposed resolution comment: Ricardo, I'm not sure that the normative-type content in the specification is the best location for this. How about we provide this content in the Launch Scenarios page?
Github Notifications (FHIRcast) (May 30 2019 at 03:02):
isaacvetter labeled Issue #119:
## May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 11 2019 at 09:28):
RicardoQuintano commented on Issue #119:
Isaac, I am fine adding the example in the Launch Scenario page.
Github Notifications (FHIRcast) (Jun 27 2019 at 14:56):
isaacvetter commented on Issue #119:
## :telephone_receiver: II Working Group Vote (5-30-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
Ricardo Quintano Neira moved the following disposition, seconded by Martin Bellehumeur
Disposition: Persuasive with Mod
Disposition Comment: We will describe a "real life" example of session discovery, perhaps with some graphics to better introduce readers new to the need for context synchronization. Perhaps this should be part of a Overview or Quick Intro page.:+1: For: 8
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jun 27 2019 at 14:56):
wmaethner labeled Issue #119:
## May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Aug 19 2019 at 17:35):
isaacvetter commented on Issue #119:
Hey @RicardoQuintano - I'm trying to address this issue, and am scratching my head, trying to figure out exactly what to do.
We've committed to updating the Launch Scenarios page to include a
"real life" example of session discovery
What does this mean to you? Would something like the below (albeit with some more content) meet our goal?
A radiologist working their EHR reporting system clicks a button to open their dictation system. The SMART dictation app performs the OAuth2 handshake to receive the
hub.urlandhub.topic. The app then subscribes to the radiologist's session by contacting thehub.urland supplying thehub.topic.
Github Notifications (FHIRcast) (Aug 21 2019 at 17:30):
RicardoQuintano commented on Issue #119:
Hi @isaacvetter,
The idea of the "real life example" is to support the reader to understand how FHIRcast can be used in a practical way. Your example is perfect and I would extend it (not only the session discovery part). Below is a different example.
"A physician checks radiology exams (such as TC-scan or X-rays) to support them to define the diagnosis and the care plan of their patients. The first time the physician needs to check the exams, they click on a button in the EHR to open the PACS image viewer app. The app performs the OAuth2 handshake to receive the hub.url and hub.topic. The app then subscribes to the physician's session by contacting the hub.url and supplying the hub.topic. Once the PACS image viewer app finishes the subscription process (subscription request and intent verification), every time the physician changes the patient in the EHR (change in context) the viewer will present the corresponding radiology exams from that specific patient."
Github Notifications (FHIRcast) (Aug 21 2019 at 17:43):
RicardoQuintano edited a comment on Issue #119:
Hi @isaacvetter,
The idea of the "real life example" is to support the reader to understand how FHIRcast can be used in a practical way. Your example is perfect and I would extend it (not only the session discovery part) as it would support even more the reader. Below is a different example. I am not an expert in the Radiology area, that's why I provided a different one.
"A physician checks radiology exams (such as TC-scan or X-rays) to support them to define the diagnosis and the care plan of their patients. The first time the physician needs to check the exams, they click on a button in the EHR to open the PACS image viewer app. The app performs the OAuth2 handshake to receive the hub.url and hub.topic. The app then subscribes to the physician's session by contacting the hub.url and supplying the hub.topic. Once the PACS image viewer app finishes the subscription process (subscription request and intent verification), every time the physician changes the patient in the EHR (change in context) the viewer will present the corresponding radiology exams from that specific patient."
Github Notifications (FHIRcast) (Sep 03 2019 at 21:58):
isaacvetter closed Issue #119:
May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:24):
isaacvetter reopened Issue #119:
May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 12 2019 at 21:01):
isaacvetter closed Issue #119:
May 2019 Ballot Comment: Provide a "real life" example of session discovery.
Submitted by Ricardo Quintano Neira
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S ClarificationSummary: Provide a "real life" example of session discovery.
Comment: It is not clear for me how the session discovery would work in a real process.
A description of a real life example will provide better understanding to the reader.
_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
