Stream: snomed
Topic: snomed-fhir
Rein Zustand (Oct 26 2017 at 05:41):
cogito
Rein Zustand (Oct 26 2017 at 05:46):
cogito&
Grahame Grieve (Oct 26 2017 at 05:52):
hi
Grahame Grieve (Oct 26 2017 at 05:52):
;-)
snomed (Oct 26 2017 at 06:04):
rht: Oh, to explain what's going on: I'm testing a mirror/bridge to FHIR
snomed (Oct 26 2017 at 06:05):
rht: \[\partial^2\phi\]
snomed (Oct 26 2017 at 06:07):
rht: ~strike~
Rein Zustand (Oct 26 2017 at 06:07):
strike
snomed (Oct 26 2017 at 06:10):
Rory Davidson: I assumed that was it ;-)
Rory Davidson (Oct 26 2017 at 06:35):
That looks like a success
Rein Zustand (Oct 26 2017 at 06:41):
If necessary, all the public channels can be mirrored in, too, within the #snomed stream from here.
snomed (Oct 26 2017 at 06:43):
Rory Davidson: That could end up being a lot of noise into a single channel... let's see how this one evolves and go from there? Maybe the terminology channel would be interesting...
snomed (Oct 26 2017 at 06:45):
rht: I was thinking of the bot to post it in each of their own respective channel, so there shouldn't be any flooding.
snomed (Oct 26 2017 at 06:45):
Rory Davidson: so replicating the channels here? We could do that, at least for those that are relevant
snomed (Oct 26 2017 at 06:46):
rht: IC. Also, what's currently missing is to map the markdown syntax used in Rocket.Chat to Zulip's bugdown.
snomed (Oct 26 2017 at 06:46):
Rory Davidson: stanbards... standards... ;-)
Grahame Grieve (Oct 26 2017 at 06:48):
happy if snomed wants to bridge the terminology track, but I don't think any others here are of interest to snomed
snomed (Oct 26 2017 at 06:48):
Rory Davidson: also... doesn't look like it's picking up directly follow-on chats from the same author?
snomed (Oct 26 2017 at 06:49):
rht: Yeah, Rocket.Chat's API is limited so the edit can't be transported through.
Grahame Grieve (Oct 26 2017 at 06:50):
that sounds like a pretty serious limitation?
snomed (Oct 26 2017 at 06:50):
rht: There is a beta version of the new R.C API of actually subscribing to a channel. What I'm currently doing right now is to check channel history every n seconds.
snomed (Oct 26 2017 at 06:52):
Rory Davidson: I think the lack of edits coming across is one that we can live with... half the other chat solutions out there don't even allow editing so many are unaware it's even possible.
Grahame Grieve (Oct 26 2017 at 06:53):
edits != follow-on chats?
snomed (Oct 26 2017 at 06:53):
Rory Davidson: Yes, that one I agree
snomed (Oct 26 2017 at 06:53):
Rory Davidson: so just testing that with this follow on message
snomed (Oct 26 2017 at 06:54):
Rory Davidson: ah... that one got through
snomed (Oct 26 2017 at 06:54):
Rory Davidson: but that one didn't...
snomed (Oct 26 2017 at 06:55):
Rory Davidson: any thought @rht why some are being missed? I thought even if it was 2s it would still get all the messages?
Rob Hausam (Oct 26 2017 at 06:57):
so it looks like we're getting somewhere with it
snomed (Oct 26 2017 at 06:58):
Rory Davidson: 
snomed (Oct 26 2017 at 06:58):
rht: Hmmm, did you mean some of the messages didn't get delivered to the other end? https://docs.rocket.chat/developer-guides/rest-api/channels/history#query-parameters, I set "inclusive" to be false.
snomed (Oct 26 2017 at 06:59):
rht: To avoid duplication of messages
Rein Zustand (Oct 26 2017 at 09:02):
Grahame Grieve (Oct 29 2017 at 22:56):
ok so is this all go now?
snomed (Oct 29 2017 at 23:49):
rht: Uh-huh?
snomed (Oct 30 2017 at 06:56):
Rory Davidson: yes, looks good to go
Grahame Grieve (Oct 30 2017 at 07:03):
so just to be clear: the limitations are that messages cannot be edited after sending? @Rein Zustand should we create a task asking for Zulip to be able to prevent that for a stream? Any other limitations?
snomed (Oct 30 2017 at 07:05):
Rory Davidson: I don't think that is a blocker really.
snomed (Oct 30 2017 at 07:05):
rht: Yes, due to the same reason that message uid in this instance != message uid in another instance. Unless there is a way to uniquely identify a message that is cross realm (a solution I have seen in email is using Message-ID metadata), it is not possible to edit.
Grahame Grieve (Oct 30 2017 at 07:06):
agree it's not a blocker; just making sure I am clear what issues are likely to arise
snomed (Oct 30 2017 at 07:06):
rht: Another thing is Zulip's markdown syntax is more restricted than Rocket.Chat's.
Grahame Grieve (Oct 30 2017 at 07:06):
that will degrade gracefully?
snomed (Oct 30 2017 at 07:07):
rht: In Rocket.Chat, emoji without ':' will render directly, but if you use ':' strictly, the emoji will appear in both end.
snomed (Oct 30 2017 at 07:10):
rht: A ~strike~ in Rocket.Chat requires only one '~', but two '' for Zulip's strike~~.
snomed (Oct 30 2017 at 07:11):
Rory Davidson: hopefully most people will recognize the emojis even without the colon
Grahame Grieve (Oct 30 2017 at 08:34):
right. there's no catastrophic loss there
Rob Hausam (Oct 31 2017 at 12:02):
I'm testing what happens with editing on both sides. Adding this text.
snomed (Oct 31 2017 at 12:52):
rht: There was a connection time out to snomedtools.org "requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='chat.snomedtools.org', port=443): Read timed out. (read timeout=30)"
snomed (Oct 31 2017 at 12:54):
rht: I will make the bridge more robust and retry for this particular error.
snomed (Oct 31 2017 at 12:58):
rht: Oh well I run either client as a separate UNIX process so it is hard to track down which HTTPS timeout on which client.
snomed (Oct 31 2017 at 13:17):
Rory Davidson: I saw this the other day but it happened only once
snomed (Oct 31 2017 at 13:28):
Robert Hausam: I'll try it again.
snomed (Oct 31 2017 at 13:29):
Robert Hausam: So, it did work for me this time.
snomed (Oct 31 2017 at 13:31):
Robert Hausam: So, do we think this timeout problem is now solved?
snomed (Oct 31 2017 at 13:32):
Rory Davidson: I can'
snomed (Oct 31 2017 at 13:32):
Rory Davidson: t say if it has been solved, but I think we just need to keep an eye for it, and then dig deeper if necessary
snomed (Oct 31 2017 at 13:33):
Robert Hausam: ok
Rob Hausam (Nov 07 2017 at 18:57):
Just a reminder that we're having the inaugural "SNOMED on FHIR" call joint with HL7 and SNOMED International at 20:00 UTC / 4:00 PM Eastern today (in just over an hour). Here are the planned agenda and meeting details:
https://confluence.ihtsdotools.org/display/FHIR/2017-11-07+-+SNOMED+on+FHIR+Meeting
Rob Hausam (Nov 07 2017 at 18:59):
And I'll add that this is the "re-branded" TermInfo call - we're trying to broaden the reach and participation so that we can accelerate the progress on this work. Looking forward to talking with everyone!
snomed (Nov 08 2017 at 04:45):
rht: Having a scribe note for the summary of the meeting would be nice.
Grahame Grieve (Nov 08 2017 at 04:47):
+1
snomed (Dec 11 2017 at 21:30):
Suzy Roy: suzy.roy
Rob Hausam (Apr 04 2018 at 16:49):
Cross-posting to this topic (and hopefully also snochat): https://chat.fhir.org/#narrow/stream/snomed/subject/http.3A.2F.2Fsnomed.2Einfo.2Fsct
Last updated: Apr 12 2022 at 19:14 UTC
