# 2019-10-30 FHIR Squad Call

**URL:** <https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277>\
**Category:** Community\
**Tags:** fhir\
**Created:** [October 29, 2019, 9:12pm UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277 "2019-10-29T21:12:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ccwhite23](https://talk.openmrs.org/letter_avatar/ccwhite23/32/5_5575768a8748004e209b776fc1b2916d.png) [@ccwhite23](https://talk.openmrs.org/u/ccwhite23)\
**Post date:** [October 29, 2019, 9:12pm UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277/1 "2019-10-29T21:12:26Z")

</div>

The FHIR Squad meeting is this **Wednesday, October 30 at 6pm Nairobi | 3pm UTC | 11am EDT | 8am PDT.**

Questions to Answer:

- Which use cases should the FHIR module support first?
- What are the barriers to implementing the selected use cases?

Agenda:

- Current module work updates (5 mn)
- Select use cases to focus on (10mn)
- FHIR module case study (15mn)
- Roadmap to implementing use cases (20mn)
- RFC process review (10mn)

**Who** : Anyone is welcome to join this discussion and we look forward to seeing @pmanko @janflowers @ccwhite23 @jdick @mogoodrich @ball @akanter @ckemar @corneliouzbett @dkayiwa @jmaxy @jamesfeshner @ibacher @jteich @burke @mseaton

Weekly Calendar invite: [https://iu.zoom.us/meeting/v5MscO2srDMrgdduNbTNwBFJhL9NvXi2KQ/ics?icsToken=6fd92bd29b660e0185c35548f4df663d52e11e9ac391c9192f1c057666566144](https://iu.zoom.us/meeting/v5MscO2srDMrgdduNbTNwBFJhL9NvXi2KQ/ics?icsToken=6fd92bd29b660e0185c35548f4df663d52e11e9ac391c9192f1c057666566144)

**Where** : Join from PC, Mac, Linux, iOS or Android: [https://iu.zoom.us/j/271744281](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](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: 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India) 213.19.144.110 (EMEA) 103.122.166.55 (Australia) 209.9.211.110 (Hong Kong) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) 207.226.132.110 (Japan) Meeting ID: 271 744 281

```auto
SIP: 271744281@zoomcrc.com

```

Or Skype for Business (Lync):

![](https://d24cgw3uvb9a9h.cloudfront.net/zoom.ico) [Zoom Video](https://iu.zoom.us/skype/271744281)

![](https://d24cgw3uvb9a9h.cloudfront.net/static/93719/image/thumb.png)

### [Join our Cloud HD Video Meeting now](https://iu.zoom.us/skype/271744281)

Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webinars across mobile, desktop, and room systems. Zoom Rooms is the original software-based conference…

---

<div class="post-metadata">

**Author:** ![ccwhite23](https://talk.openmrs.org/letter_avatar/ccwhite23/32/5_5575768a8748004e209b776fc1b2916d.png) [@ccwhite23](https://talk.openmrs.org/u/ccwhite23)\
**Post date:** [October 30, 2019, 4:11pm UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277/2 "2019-10-30T16:11:30Z")

</div>

Meeting notes

> **[2019-10-30 FHIR Squad Meeting](https://docs.google.com/document/d/135F6n46kq0edi3yGMTja2JbIpwHv05ZIVjjrC1bpcYI/edit?usp=sharing)**
>
> 2019-10-23 OpenMRS FHIR Squad Meeting Attendees: JJ Dick Jan Christina Piotr Bett Casey Greg Jen Ian Daniel Mike Valerio Questions to Answer: Which use cases should the FHIR module support first? What are the barriers to implementing the selected...

---

<div class="post-metadata">

**Author:** ![janflowers](https://talk.openmrs.org/user_avatar/talk.openmrs.org/janflowers/32/208_2.png) [@janflowers](https://talk.openmrs.org/u/janflowers)\
**Post date:** [October 30, 2019, 6:16pm UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277/3 "2019-10-30T18:16:14Z")

</div>

Thanks for the great call today everyone! I’m really excited about the decision to focus for the first use cases being lab and medications. Were there any other specific decisions from the call that we should summarize for the community at-large here? @ccwhite23

---

<div class="post-metadata">

**Author:** ![dkayiwa](https://talk.openmrs.org/user_avatar/talk.openmrs.org/dkayiwa/32/179_2.png) [@dkayiwa](https://talk.openmrs.org/u/dkayiwa)\
**Post date:** [October 30, 2019, 8:27pm UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277/4 "2019-10-30T20:27:30Z")

</div>

In response to this:

- JJ proposes a one approver policy
  - Squad agrees to move to one reviewer

Is that because there are no people to review? My humble advice is that, since the people raising these pull requests and the reviewers are both new to the module, it would be safer to require two reviews than one. With time, as they both get more comfortable with the code base, this can be changed to less. More reviews also have the added advantage of helping people get more familiar and up to speed with the code base. It does not hurt to have a pair of eyes on ones’ code. 🙂

---

<div class="post-metadata">

**Author:** ![ccwhite23](https://talk.openmrs.org/letter_avatar/ccwhite23/32/5_5575768a8748004e209b776fc1b2916d.png) [@ccwhite23](https://talk.openmrs.org/u/ccwhite23)\
**Post date:** [November 6, 2019, 6:09am UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277/5 "2019-11-06T06:09:07Z")

</div>

@dkayiwa - yes this is because we currently only have two people actively working on the code for the module.

---

<div class="post-metadata">

**Author:** ![janflowers](https://talk.openmrs.org/user_avatar/talk.openmrs.org/janflowers/32/208_2.png) [@janflowers](https://talk.openmrs.org/u/janflowers)\
**Post date:** [November 6, 2019, 6:10am UTC](https://talk.openmrs.org/t/2019-10-30-fhir-squad-call/25277/6 "2019-11-06T06:10:43Z")

</div>

@dkayiwa you make a great point about people here learning, and having two people could improve the oversight of the quality of the code. Let’s do this as a continuous improvement process, starting with single, keeping an eye on the result of that, and then revising to have two if needed?
