I am sure you were thrilled with your achievement of AWS CSA - Associate certification. I remember the same day 😛 .

I wanted to make this an opportunity to tell you about the wondeful paths that you can drive your career from the junction where you’re right now 🤔

1. AWS Speciality Certifications ?

This is the very path I took. AWS Offers a set of speciality certifications.

I certainly gathered a vast amount of new knowledge in different aspects of software engineering thanks to these wondeful certifications. Let me give a glimse of what you can expect 😃

1. You gain knowledge on the full lifecycle of enterprise software development
2. This helps in designing and deployment of solutions on AWS from scratch
3. These specializations cover almost all the services in AWS Product Catalogue which makes you an AWS Guru 😝
4. You would be able to apply this knowledge and experience learning any other cloud computing providers like GCP or Azure
5. Lots of hiring managers would keep knocking on your door 😄

I would tell you more about how I achieved these certifications in the upcoming blogs.

2. Or AWS CSA Pro Certification?

This is certainly one of the most prestigious certifications in the cloud computing world. This will help you to learn lots of valuable services and how to use them in different scenarios. This certification helped me to unleash the AWS architect in me and to uplift my career to a whole new level.

I highly recommend you taking this up.

Since this cetification covers almost all the aws services related to security, networking and databases, 1 to 2 years of hands on experience with AWS would be handy!

If you can acheive AWS Speciality Certification such as Security and Networking it would lay a good foundation for your AWS CSA PRO journey 😃. I would tell you more about how I achieved CSA Pro in the upcoming blogs.

3. Or Certifications from GCP or Azure?

After AWS CSA-Associate, you’re familiar with the AWS technologies and you are confident of taking up any chanllenge on AWS 😉. It would be great to equip your career with certifications offered by GCP or Azure to impress your next hiring manager 😃

Most of the companies in Singapore, Canada and Europe make use of GCP and Azure inaddition to AWS. Your profile as an expert in all cloud providers will certainly make you standout from the rest of the applicants in your next job interview 😆

I am also currently preparing for the GCP Associate Cloud Engineer certification in the quest of learning about other cloud providers 🙌

One thing I noticed so far is that other cloud providers are not totally different to AWS so your AWS knowledge would certainly be handy 👌

It’s your decision!

There’s actually no wrong path that you can take here! Decide where you want to be in the next 2–3 years and do what you think would benefit you the most 😃. I am sure you’ll be able to learn new things and make your career more successful!

Wish you all the best ✋

If you already decided to take up this exam, Congratulations! you’ve decided to take your career to the next level and let me make your way smoother!

I was able to achieve AWS CSA Associate, AWS Machine Learning Speciality, AWS Data Analytics speciality, AWS Networking Speciality, AWS Security Speciality and AWS CSA Professional certifications under 18 months. So I am confident I share all my experience with you 😃

Do you have experience working with AWS ?

Well don’t worry if the answer is No. Since you’ve the will I am sure you will be able to gain the required knowledge to ace the exam!

How to get started ?

I highly recommend Ryan Kroonenburg’s course as it helped me a lot!

He is one of the best lecturers when it comes to AWS and he has great tips for the exam. Do not miss even single tip 😃

Very Important!!!

Maintain a notebook and write down important facts as you watch the video so you can study them later! Treat it as your new buddy in this course 😃

Hands-on Labs would make you perfect!

Try doing the labs in the course and try doing things on your own! Just make sure you’ve created the billing alerts in your AWS account so you won’t exceed your budget limits 😅

How to prepare for exam questions?

To master the exam questions I highly recommend Whizlabs AWS Associate Exam Practice Tests. This offers you exam-like environment to try and prepare for the questions. You should be able to purchase these practice tests under $10.

It’s ok to fail!

Keep taking up the practice tests until you consistently score over 80% for each practice test! Do not worry if you find it difficult at first, but keep trying the tests again and again until you’re confident about each AWS service 😃

Whizlabs offers explanation for each question so you can learn from your mistakes. Make it a hobbit to write the question and explanation for tricky questions in our notebook so you will be thorough with them!

The rehearsal

When you’re confident you’re ready for the show down (The final exam 😃) purchase the AWS CSA Associate Practice Questions from AWS Certification Portal and give it a try 😃. It would be great if you can do this just before 1or 2 days from your real exam. If you’re lucky you might see few questions from the practice exam appearing in the real exam 😛

All the best!

Well now you’re perfectly equipped to achieve AWS Certified Solution Architect — Associate Certification !!!

Go get it champ 😛

Overview

The Patient Clinical Summary generates a summary that is being displayed on the patient dashboard which is helpful for the clinicians to make clinical decisions without going through numerous encounters/observations. It would also be helpful for clinicians access these reports off-line specially when they visit patients in rural areas.

Objectives:

• Generating Patient clinical summaries using SQL data set definitions.
• Creating scheduled tasks to generate patient clinical reports.
• Creating user interface to create report configurations.
• Creating back-end infrastructure to implement functionality.
• Creating endpoints to consume reports from Muzima Android App.
• Modifying Muzima Android app to display reports to the user.

GSoC Contributions

• GSoC 2018 Patient Clinical Summary Enhancement Changes For reveiew by dilekamadushan · Pull Request #38 · muzima/openmrs-module-muzimacore
• GSoC 2018 Patient Clinical Summary Enhancement Changes For reveiew by dilekamadushan · Pull Request #185 · muzima/muzima-android

Mid Evaluation Presentation

Video Presentation.mp4

Other Resources:

• Project Documentation: https://wiki.openmrs.org/display/projects/Patient+Clinical+Summary+Enhancement
• Talk Discussion: Openmrs Talk Thread
• Blogs: Medium Blogs

Thoughts on GSoC:

It has been a wonderful experience for me for the last 12 weeks to work with OpenMRS and GSoC community. I gained lots of valuable technical knowledge. I had the opportunity to dive deep into Spring and Android in development phase. It was a real pleasure working with the likes of my mentor whom had a lot to offer me 😆.

Though GSoC is coming to an end, my contributions to the open source community starts from this year and I hope to continue it for a long time to come 😅!

In this week I developed muzima Android app to display patient reports. I had to try out different methods this week. here is a brief description of how I approached my task.

I used the functions of muzima api to call the server. Those middle-ware was developed by muzima developers, so my work was easier 😆! The muzima api calls the server asynchronously, so I had to wait until the report is fetched to muzima app. So I created a background process which listens for the message

When the download is complete I receive the message and then displays the report to the user.

The above code snippet shows how the view is loaded when the message is received. I am hoping to complete the functionality in the coming week 😯!

The GSoC 2018 was reaching its end, so I had to steam in to finish on time 😅. In this week I engaged in displaying the data(MuzimaGeneratedReport) that is fetched from the server.

I first tried to create a view containing a list of the reports of a particular patient. I followed the procedure to create a list as you normally follow in Android.

I created a layout file named report_list_view and created a list as follows.

Then I created an Android Activity named PatientReportListViewActivity and used the following code 😆

As at this moment I was unable to bring patient reports from the server, I created a list of dummy values for now 😅. When a user selects a report name, the report should be loaded. The report is a HTML page. So I am going to load the report using WebView in Android as follows

The PatientReportWebActivity that is triggered on item click takes the user to the WebView where report is displayed.

This was successful 😆. But in muzima-android there is a preferred way to create this work-flow. In the next week I will be doing this in that way. This was just to get my head in 😅. See you next week with more!

This week was also a successful week as I completed the job of finalizing the end points in muzimacore module. This endpoint would be used by the muzima android app to download patient reports.

First I had to add a change to the existing database because the design team had requested to add a new field priority to muzima_generated_report. This attribute was set as a tiny_int and the default value was set to 0. So if the user wants to create a report_cohort_config with high priority priority the check box in the following diagram should be ticked, so that priority column in the SQL table is set to one.

Then I worked on the REST endpoint which returns the last patient report created due to a cohort report mapping set to high priority 😃. The endpoint requires the uuid of the patient as the only parameter.

I am hoping to get these reports into muzima android app in the coming weeks 😯.

The 9th week of the program was really important as the 2nd evaluation was scheduled. I engaged in improving the scheduled task in muzimacore module which creates summary reports for each patient in a cohort.

I installed reporting compatibility module so that cohorts could be built. Next I had to add a concept dictionary so that I could add Obs for a patient.

Once a report configuration is created by the user(i.e-mapping a cohort with report definition) the scheduled task of creating patient reports take over.

Introduction to the Report Generation Task

1. The process is started everyday at 00:00 hrs, and it first gets all the report configurations from the database and loops through each one of them.
2. It loops through each patient belonging to the cohort of the report configuration.
3. The task then checks for any in-completed reports belonging to that particular patient in the generated reports table. If any are found, the report is generated and saved as a “completed” report(setting the status column to “complete”)
4. The task next checks for new Obs for that patient since 00:00 hrs last day and generates a new report only if any are added.
5. If no previous reports of that patient are found, the task creates a new report (This would happen for the very first run of the task).

Currently I am engaging in testing the scheduled task. I hope to configure the muzima android app so it could consume these reports and render it to the mobile user 😃.

The start of this week was a landmark of my project, because I had to complete development in the muzima core module and then move to the development in muzima android app.

I tried to complete the scheduled task to generate reports for patients with in this week. But I ran into a dead end when rendering the output for each report request. The report generation is implemented as an asynchronous task in the reporting module. So waiting until the task report is generated was a problem.

The generated patient reports by the muzima core module should then be displayed in the muzima mobile app. In the muzima app I first tried to add the following interface changes.

I must thank in heaps to my mentor Samuel Mbuga and Bernard Mokaya who helped a lot to begin working in the muzima app.

This week was one of the busiest week as I was required to complete generation of summary reports in openMRS webapp.

First I created controllers which are capable of mapping a cohort with report designs and display them in interfaces that I created last week. I achieved this task with the help of controllers created previously by early programmers. Skills in AngularJs made this work easier 😆.

Then I had the task of creating back-end functionality to add scheduled task to generate summary reports according to each report configuration added by the user in the following interface.

For this task I had to add dependency of reporting-api to muzimacore module which consumed most of the time in the task 😞

The following link would be very useful for anyone of you who would want to know available versions of jars in openMRS 😰.

https://openmrs.jfrog.io/openmrs/public/org/openmrs/module/reporting-api

Once the dependencies are all sorted out, I am now coding the scheduler task which should be capable of generating a summary report for each patient in a cohort if Obs of that patent are changed. The relevant controllers in openMRS reporting module helped me to get started with implementing the required functionality.

In the last week I had finalized all the designs with my mentor so that implementation could begin soon 😅. As we planned, the coding started this week! I started with changes in the openMRS webapp first before muzima mobile application is modified.

My first task was to produce the user interfaces with in the muzima-core module. Skills of HTML and AngularJS 1 helped me to achive this task after few days of work 😆.

Then I started to add required back-end functionality for each user interface. First I needed to come up with a database change which was implemented under the guidance of my mentor Samuel Mbuga 😃.