Stream: fhircast-github
Topic: fhircast-docs / issue #363 Update STU3BallotDraft.md
Github Notifications (FHIRcast) (Sep 14 2021 at 22:03):
EricOnFHIR commented on issue #363:
Please let me know if this worked.
Github Notifications (FHIRcast) (Sep 14 2021 at 22:12):
ajuliansr commented on issue #363:
If what worked?
Tony Julian
From: EricOnFHIR @.***>
Sent: Tuesday, September 14, 2021 5:04 PM
To: HL7/fhircast-docs @.***>
Cc: Subscribed @.***>
Subject: [EXTERNAL] Re: [HL7/fhircast-docs] Update STU3BallotDraft.md (#363)Please let me know if this worked.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/HL7/fhircast-docs/pull/363#issuecomment-919544923>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADSP6EZBK3664BQZLC6ZF5LUB7BFTANCNFSM5EBCXLCA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
Github Notifications (FHIRcast) (Sep 16 2021 at 15:29):
isaacvetter commented on issue #363:
HL7 InM call on 20210916, notes:
- it doesn't make sense to introduce -select in the new "Sharing of Content" section
- per conversation, should probably remove the ability to update content from -close (and all events other than -update)
Github Notifications (FHIRcast) (Sep 16 2021 at 15:39):
isaacvetter edited a comment on issue #363:
HL7 InM call on 20210916, notes:
- it doesn't make sense to introduce -select in the new "Sharing of Content" section
- per conversation, should probably remove the ability to update content from -close (and all events other than -update)
- FHIRcast is missing some features that are used to guarantee message delivery. Content sent is not guaranteed to be delivered. FHIRcast -update events are considered to be "hints" that content has changed ....
Github Notifications (FHIRcast) (Sep 16 2021 at 15:41):
isaacvetter edited a comment on issue #363:
HL7 InM call on 20210916, notes:
- it doesn't make sense to introduce -select in the new "Sharing of Content" section
- per conversation, should probably remove the ability to update content from -close (and all events other than -update)
- FHIRcast is missing some features that are used to guarantee message delivery. Content sent is not guaranteed to be delivered. FHIRcast -update events are considered to be "hints" that content has changed .... Assuming this is true and makes sense, it needs to be described in the spec, such that implementers understand when and how they can use -update events.
Github Notifications (FHIRcast) (Sep 16 2021 at 15:48):
isaacvetter edited a comment on issue #363:
HL7 InM call on 20210916, notes:
- it doesn't make sense to introduce -select in the new "Sharing of Content" section
- per conversation, should probably remove the ability to update content from -close (and all events other than -update)
- FHIRcast is missing some features that are used to guarantee message delivery. Content sent is not guaranteed to be delivered. FHIRcast -update events are considered to be "hints" that content has changed .... Assuming this is true and makes sense, it needs to be described in the spec, such that implementers understand when and how they can use -update events.
Github Notifications (FHIRcast) (Sep 16 2021 at 15:54):
isaacvetter edited a comment on issue #363:
HL7 InM call on 20210916, notes:
- it doesn't make sense to introduce -select in the new "Sharing of Content" section
- per conversation, should probably remove the ability to update content from -close (and all events other than -update)
- FHIRcast is missing some features that are used to guarantee message delivery. Content sent is not guaranteed to be delivered. FHIRcast -update events are considered to be "hints" that content has changed .... Assuming this is true and makes sense, it needs to be described in the spec, such that implementers understand when and how they can use -update events.
** Do we need normative language around responding with a http status code if I'm unable to receive / process?
Github Notifications (FHIRcast) (Sep 16 2021 at 15:56):
isaacvetter edited a comment on issue #363:
HL7 InM call on 20210916, notes:
- it doesn't make sense to introduce -select in the new "Sharing of Content" section
- per conversation, should probably remove the ability to update content from -close (and all events other than -update)
- FHIRcast is missing some features that are used to guarantee message delivery. Content sent is not guaranteed to be delivered. FHIRcast -update events are considered to be "hints" that content has changed .... Assuming this is true and makes sense, it needs to be described in the spec, such that implementers understand when and how they can use -update events.
- Do we need normative language around responding with a http status code if I'm unable to receive / process?
- Also, still planning on describing a feature of not including content directly and only by _reference_ in a content update.
Github Notifications (FHIRcast) (Oct 09 2021 at 16:32):
EricOnFHIR commented on issue #363:
Add context to close event
Github Notifications (FHIRcast) (Nov 04 2021 at 16:37):
isaacvetter commented on issue #363:
From discussion in InM FHIRcast this morning (https://confluence.hl7.org/pages/viewpage.action?pageId=130485460), merging with the expectation that we'll also update to:
- (Eric) Move *-select out of content sharing, into context sharing
- (Eric, Bas) Add content sharing by reference to specification
- (Isaac) Formalizing multi-tab considerations into specification
- (Bas van den Heuvel) Turn FHIRcast content into formal FHIR implementation guide
Last updated: Apr 12 2022 at 19:14 UTC
