Stream: fhircast-github
Topic: fhircast-docs / PR #256 Ballot fixes event notification s...
Github Notifications (FHIRcast) (Jul 02 2019 at 18:54):
wmaethner opened PR #256 from Ballot-Fixes-Event-Notification-Section-1 to master.
Github Notifications (FHIRcast) (Jul 02 2019 at 18:54):
wmaethner requested isaacvetter, lbergnehr, and NiklasSvenzen for a review on PR #256.
Github Notifications (FHIRcast) (Jul 02 2019 at 18:54):
wmaethner requested isaacvetter, lbergnehr, and NiklasSvenzen for a review on PR #256.
Github Notifications (FHIRcast) (Jul 02 2019 at 18:54):
wmaethner requested isaacvetter, lbergnehr, and NiklasSvenzen for a review on PR #256.
Github Notifications (FHIRcast) (Jul 02 2019 at 18:54):
wmaethner edited PR #256 from Ballot-Fixes-Event-Notification-Section-1 to master:
Fixes to: #202, #236, #204, #203, #159, #137, #96, #95, #247, #207, #206, #205, #231, #232
Github Notifications (FHIRcast) (Jul 02 2019 at 19:24):
lbergnehr created PR Review Comment:
If the event catalog is moved outside of the spec, perhaps it shouldn't be referred here. I understand if that is not part of this PR though.
Github Notifications (FHIRcast) (Jul 02 2019 at 19:24):
lbergnehr submitted PR Review.
Github Notifications (FHIRcast) (Jul 02 2019 at 19:24):
lbergnehr submitted PR Review.
Github Notifications (FHIRcast) (Jul 03 2019 at 12:52):
wmaethner submitted PR Review.
Github Notifications (FHIRcast) (Jul 03 2019 at 12:52):
wmaethner created PR Review Comment:
@lbergnehr yeah that same thought occurred to me when looking at some of the other issues. I think for this one it is fine and then the PR that handles moving the Event Catalog will handle all the references to it throughout the spec. It'll be a big one.
Github Notifications (FHIRcast) (Jul 15 2019 at 18:23):
wmaethner closed without merge PR #256.
Last updated: Apr 12 2022 at 19:14 UTC
