Google Summer of Code 2020 Weekly Feedback

Community Google Summer of Code
21

This week’s progress (05/25 - 05/29)

  1. Refreshed my skills on components creation with polymer 3.
  2. Set up the environment for the start of the coding session. Obtained access to the previous lh-toolkit GitLab projects.
  3. Posted a blog.

Next week’s Plan (06/01 - 06/05)

  1. Create at least three web components (fhir-observation-status, fhir-observation-category, and fhir-observation-period )
  2. Perform unit testing on the components.
22

Shouldn’t you be integrating with the mHBS app and use the same style for the UI? @iainbarclay @shbucher

23

Is your plan still to build a separate UI? Please look at the OHIF Viewer and try to integrate your work into that, as that is part of the lh-radiology. Please don’t start from scratch. That is not how FOSS should be done.

1 Like
24

There are two Dockerfiles, one for dev and one that makes a production bundle (It’s a meteor.js app)

25

I should be integrating with the mHBS app, but I was told that it would be a standalone application for now, as the main work is to integrate with the evernym SDK and get that part of the project going. @iainbarclay correct me if I’m wrong. However, @shbucher mentioned in the video call recently that I still have some pending work on the mHBS app and that I would be contacted by @sunbiz.

As far as UI goes, the colour schema would still be followed similar to the mHBS app.

1 Like
26

@sunbiz @r0bby , I have looked into OHIF viewer demo app. It is great, but what I understand from the chat I had with @judywawira and @pri2si17 the other day, there is a lack of annotated medical images on which object detection can be performed. So we use heatmaps and other tricks to resolve that issue. We propose to make a simple webapp for AI guided annotations. The doctors who will be doing annotations will get bounding boxes from our AI as a starting reference and they can add more bounding boxes, delete, reshape or change positions if they like. Now, for Machine learning we need the bounding Boxes and nothing else. The OHIF viewer on the other hand is for detailed analysis and data recording of radiology images for medical research. I think our app is solely for data collection for ML research so we should have a separate app.

Also, I have some very specific features in my mind for the above application to make the process more efficient and effective.

27

Yes @prajwal27 , you are correct - the app you are working on at the moment will be used directly on the smartphones of mothers/guardians, so its good for you and @sradha to look into the app stores to get a sense of the “state of the art” for UI design and flow for this type of “baby management” app to inform our direction.

Ultimately we hope that this Guardian app will become part of the mHBS suite, so we’ll definitely be very mindful of the UI work done there already, and propose a direction for this UI that fits well into the mHBS family, and brings best practise from the UI of well regarded apps aimed at use directly by mothers too. [cc @Maria-Freytsis @sunbiz @shbucher @shbucher ]

2 Likes
28

Thanks Iain. @prajwal27 I am preparing some prototype screens which we can use as a starting point for discussion. I will have the page descriptions and prototype screens soon and will setup a call with you and Iain to discuss.

1 Like
29

Keep chatter on this thread to a minimum, please. If @mentors have a concern with reports here, please bring it up your project threads.

No need to reply.

1 Like
30

What progress have you made this week?

This week I made UI screens of app with dummy data, I made Home, Search Screens & other screens , I added Navigation Drawer & bottom navigation UI.

I made a merge request of it & it was successfully merged. I am also scraping CDM of Alaska State , I have already created two issues in Repo (Link), I will make its PR by Sunday

What do I plan to do next week?

I will make UI of rest of the features of app & will scrap CDM of California State

Have you had any blockers or issues that are impeding your project?

No

1 Like
31

What progress have you made this week?

In the first week of coding period (May 30 - June 5), I have gone through the User Stories which @Maria-Freytsis had shared and also had discussions regarding that. I pushed my code to gitlab with few commits.

I have started working on accpeting the credential which the issuer will provide. I worked on getting messages from the cloud agent, as we will not be using Push Notification (work under progress from Evernym side). I have been constantly interacting with the Evernym team, I also had a video call with one of the Mobile Developers to understand the working of the SDK (very useful).

I also started to maintain documents ( WIKI ) of the responses I got from the SDK. However, the plan is to maintain a wiki consisting of all the discussions, important points, decisions taken to help the developers in future.

What do I plan to do next week?

  • @sradha has shared the UI design and I will start developing those screens.
  • Work on credentials ( receiving and accepting ) given from the issuer.

Have you had any blockers or issues that are impeding your project?

I was initially stuck with issues and doubts in the SDK, but luckily received help from the Evernym team and I believe I have made decent progress.

2 Likes
32

Week 1 : Coding Period

What progress have you made this week?

  1. Finished EDA on RSNA dataset.
  2. Completed extraction of useful data items and began training.

What do I plan to do next week?

Complete training of models.

Have you had any blockers or issues that are impeding your project?

Ran out of memory errors on my local machine as well as Google Colab due to the masssive dataset size. I am currently implementing mini-batching during training to overcome this error.

2 Likes
33

"30-may-2020 to 5-june-2020"

[ Progress ]

  1. Made the APIs for the django app.
  2. Generated API documentation from Postman. “Link”

[Next Week]

  1. Start the Training.
  2. Setup tf server.
  3. Connect Django and tf Serving.

[Blockers]

N/A

2 Likes
34

This week’s Plan (06/01 - 06/05)

  1. I created the fhir-observation-status using polymer/lit-element v0.7.1
  2. My mentor suggested that I upgrade all the previous elements from polymer/lit-element version 0.5.1 to lit-element v2.3.1. I started upgrading the elements as instructed.

Next week’s Plan (06/08 - 06/12)

  1. Finish upgrading the elements to lit-element v2.3.1
  2. Create 3 new web components with lit-element v2.3.1 if I complete the upgrade early enough

Blockers

Components not rendering as desired after upgrade. Currently trying to figure out a solution.

2 Likes
35

"6-june-2020 to 12-june-2020"

[ Progress ]

  1. Setup Tensorflow serving for a trained model on Chest Xrays.

  2. Wrote a python script for communication between TF-Serving and Django Rest Framework.

[Next Week]

  1. Make the python middleware Asynchronous.
  2. Write a CLI for the python middleware.

[Blockers]

N/A

2 Likes
36

What progress have you made this week?

In the second week of coding period (June 6 - June 12), I have developed few of the UI screens of the app and am yet to push the commits. I’m still working on accepting the credential-offer and the credential from the issuer.

What do I plan to do next week?

  • Complete the UI development of the app.
  • Complete the work on credentials given from the issuer.

Have you had any blockers or issues that are impeding your project?

None as of now.

2 Likes
37

What progress have you made this week?

  1. This week I developed UI for Filtering search, I made bottom sheet UI, I also developed UI for “view cdm” screen. I have sent both these merge requests.

  2. I also worked on Scraper, I setup gitlab CI Pipeline correctly , scraped CDM of Alaska state, made a merge request for it.

  3. I made database class in App using sqflite package, made its Merge Request, some function of it are pending which I will do in upcoming days.

  4. Discussed a lot with mentors about scraper

  5. UI needed for main feature of this App is complete

What do I plan to do next week?

  • Scrap CDM of Indiana State

  • Work on Home Screen backend code

  • Complete the database class

Have you had any blockers or issues that are impeding your project?

No

2 Likes
38

Week 2 : Coding Period

What progress have you made this week?

  1. Successfully implemented mini-batching.
  2. Trained DenseNet201 and InceptionV4

What do I plan to do next week?

Fine-tune models till they reach acceptable accuracy.

Have you had any blockers or issues that are impeding your project?

NA

2 Likes
39

This week’s Plan (06/08 - 06/12)

  1. Successfully upgraded 32 of 43 components to lit-element v2.3.1.
  2. I also replaced native HTML tags with material web components when appropriate.

Next week’s Plan (06/15 - 06/19)

  1. Complete upgrade for the remaining 9 elements and initiate MR for all components. (due 6/15)
  2. Create 3 new web components with lit-element v2.3.1

Blockers

Property bindings of arrays and JS objects in lit-element seems a bit difficult. Currently reading up on it

2 Likes
40

What progress have you made this week?

  1. I worked on Home Screen backend code

    • Fetched & Displayed User Location using Geolocator Package

    • Fetched Nearby Hospitals using Overpass API

    • Fetching Image of each hospital from Google

    • Using Shimmer Loading Effect to load list

  2. Used Flutter BLoC [ Business Logic Component ] Architecture which is the implementation of MVVM Architecture in Android

  3. Scraped CDM of Indiana State

  4. Completed Main functionality of SQL Database class

What do I plan to do next week?

  1. I have used shared pref to store some data, I will replace it with Hive

  2. I will use sqflite to store CDM

  3. Working on Main Feature of this App [ Compare Prices Screen]

  4. Scraping CDM of New York State

Have you had any blockers or issues that are impeding your project?

No