This week I found CMS Data of 3000 Hospitals both inpatient & outpatient , I am searching for more datasets available by states & I have found it for California, New York, Indiana.
I have given my mentors a detailed project plan with milestones & I will discuss it maybe tomorrow via call.
What do I plan to do next week?
I will start making App UI with dummy data in next two weeks as suggested by @muarachmann , I will also scrap Hospitals CDM of California State next week.
Have you had any blockers or issues that are impeding your project?
In the fourth week of the community bonding (May 23 - May 29), I tried to communicate the sample app with the test server. I added the code to scan a QR code and make a connection with the test server and it was successful. I also tried looking into UI/UX design guidelines, to prepare a good UI for the current project.
The successful connection with the test server was done using native Android app written in Java. I am still trying to get that working in Flutter and have spent quite a bit of time working on that and is not successful so far.
What do I plan to do next week?
I will go through the spreadsheet, that @Maria-Freytsis has shared.
Come up with a plan with milestones and discuss with the mentors regarding that.
Look into app store for some inspiration for the UI and propose a UI for the app.
Have you had any blockers or issues that are impeding your project?
The linking of the Evernym SDK with the mobile app is time consuming as of now, with not much resource. So that’s the only issues which I’m facing.
Finalized datasets, models, compression methods and system architecture.
Created my first MR in the repo.
What do I plan to do next week?
Perform EDA on the dataset and begin training.
Look into Ultrasound datasets and papers.
Have you had any blockers or issues that are impeding your project?
The process of integration of the Flask app inside the Raspberry Pi is challenging and needs to be more defined. Either it will be possible or the system architecture would have to be modified.
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.
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.
@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.
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 ]
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.
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?
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.
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.
I created the fhir-observation-status using polymer/lit-element v0.7.1
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)
Finish upgrading the elements to lit-element v2.3.1
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.
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?