2020-03-11 FHIR Squad Meeting

Sorry for the late notice on this

Please join us for our FHIR Squad meeting to be held on Zoom today (Wednesday) March 11, 2020 at 6pm EAT | 3pm UTC | 11am EDT | 8am PDT.


  • Dev Updates

Here’s the connection information:

Please download and import the following iCalendar (.ics) files to your calendar system.

Weekly FHIR Squad Meeting: https://iu.zoom.us/meeting/v5MscO2srDMrgdduNbTNwBFJhL9NvXi2KQ/ics?icsToken=6fd92bd29b660e0185c35548f4df663d52e11e9ac391c9192f1c057666566144

Join from PC, Mac, Linux, iOS or Android: https://iu.zoom.us/j/271744281

Or Telephone:

Dial: +1 669 900 6833 (US Toll) or +1 646 558 8656 (US Toll) Meeting ID: 271 744 281

International numbers available: https://zoom.us/u/adeN7jZCo3

Or connecting from IU videoconferencing equipment: Video Bridge: 26 271 744 281

Or connecting from videoconferencing equipment outside of IU: H.323: (US West) (US East) (China) (India) (EMEA) (Australia) (Hong Kong) (Brazil) (Canada) (Japan)

Meeting ID: 271 744 281

SIP: 271744281@zoomcrc.com

Or Skype for Business (Lync): https://iu.zoom.us/skype/271744281

Zoom@IU Team | cthelp@iu.edu | https://kb.iu.edu/d/bfqu

Hope to see you there!

1 Like

Sorry @ibacher i missed recordings ?

@tendomart Sorry, I didn’t record the call. The notes are here, however.

1 Like

Thanks @ibacher for sharing the notes (BTW, the title says 2020-03-04?). I missed the meeting too; is it fair to assume that this meeting happens every Wednesday at the same time?

I am making slow progress on Condition search (https://issues.openmrs.org/browse/FM2-87) and hopefully have a PR ready sometime next week. One question I wanted to ask in the meeting: The Condition implementation seems to have changed significantly in platform version 2.2+. Do we want all fhir2 module functionality to work for any 2.* versions?

Yeah, the title is wrong and the result of copy-paste. I’ll fix that. The meeting is every week at approximately the same time, for some value of “same time” (the meeting is currently following US DST rules, but it does mean I have to keep checking the relative time in UTC, EAT, and IST).

Support-wise, our target is platform 2.0.5 or newer. For Condition, that likely does mean needing two different versions of the same code (I think Conditions were migrated from a module to core in version 2.2)

1 Like