Google Summer of Code

quartarian wrote on Friday, March 29, 2013:

What criteria did you use to select your mentors for this year’s program? Please be as specific as possible.

The criteria we used to select our mentors were; experience, accessibility, and knowledge. We achieved this by singling out the most active, experienced, and instrumental contributors to the project and asked them to participate. OpenEMR is unique software in the respects of it’s complex problem domain, and having experts at the intersections of medicine and software engineering is a tremendous source of pride. All of our mentors have years of experience working with OpenEMR and were more than happy to see the project and the students bettered.

Our mentors are:

    Rod Roark

       

    Kevin Yeh

       

    Brady Miller

       

    Brad Gregg

       

    Devi from Visolve
       

mcaloon wrote on Friday, March 29, 2013:

Matt,
    I know last year the community had a few long discussions on the multitude of jQuery versions and frames etc. related to the much desired “workflow implementation”. I know Dr. Sam Bowen has some prior posting on the workflow in a practice (can’t seem to find it tonight). There is a lot of expertise in the community that will be able to support you and other students that choose to work with us. I am also going to be supporting the effort as a mentor. I sent a blurb to Brady earlier for his late night application gauntlet. You will find many discussions on the forum regarding your topics of interest and they might be helpful to you in writing up your proposal. Here is my take on some of what you might find:

This one starts off with some good giggles about interface design (Those of you who recall Rod’s ugly baby response to Lanny) -> https://sourceforge.net/projects/openemr/forums/forum/202506/topic/5461252

Workflow -> https://sourceforge.net/projects/openemr/forums/forum/202506/topic/4380998

jQueryUI -> https://sourceforge.net/projects/openemr/forums/forum/202506/topic/6133118?message=12394742

There is a lot out here on the forum. Spend some time browsing around and it might give you some better insight into the community at large and what the peeps are thinking out here in the ether. I think your ideas are well founded and common among many community members. Let’s collaborate!

Mac

quartarian wrote on Friday, March 29, 2013:

What is your plan for dealing with disappearing students? e. What is your plan for dealing with disappearing mentors?

As in medicine, the best approach to dealing with a problem is prevention. We plan on preventing disappearing students by carefully selecting those who are the most passionate about their project and nurturing them to success. Once we have carefully selected our students, we will then pair them with our experienced mentors, who are themselves crucial to the OpenEMR project. Everyone likes to feel needed, and while guiding the students to the success of their project, they will be actively engaged with the live force of ours. Furthermore, to hedge against personal issues between a mentor and their students, we will provide students with multiple contacts.

Of course, preventions has it’s limits. If we run into the issue of a disappearing student, we will start by contacting the mentor to find out when the last engagement with the student was. If they are having any accessibility issues (or any other issues) with their mentor, we will offer to have another mentor step in. Unfortunately, some students may choose to abandon their work, but we will do everything we can to help them stay interested.

In regards to dealing with disappearing mentors, we see that as highly unlikely. We have chosen the most instrumental contributors to the project that have been with OpenEMR for years, many of whom we work with professionally. That being said, if an incident were to occur, we would contact the mentor directly and replace them if needed.

quartarian wrote on Friday, March 29, 2013:

Hey Mac,

Thanks for the links! This is why im so excitied to work with you guys.

I really hope we get approved. :slight_smile:

quartarian wrote on Friday, March 29, 2013:

What steps will you take to encourage students to interact with your project’s community before and during the program?

OpenEMR is fortunate to already have many students engaged with the community, and we feel that one of the best way’s to encourage additional students to interact with our community is by word of mouth between students. We are working to achieve this by actively interacting with these students on the forums, providing a developer wiki with a step-by-step introduction to committing bug fixes on GitHub, and encouraging active discussion about improvements that can be made to the project in a friendly environment. Ultimately we have tried to lower the barriers to entry to virtually zero. Once they become involved we also invite them to join in on the weekly OpenEMR voice conference call (Tuesdays at 9:30 AM PST).

Students who become involved during the program will be given multiple points of contact with direct lines of communication and assigned to personal mentors who will reach out to the students regularly.

bradymiller wrote on Friday, March 29, 2013:

Wow, very productive. All looks good. Here’s my stab at the last one (please improve…):

g. What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?
We will do everything we can to ensure that our student’s code/project gets into the official codebase. It’s really an awesome feeling to contribute code to a project that you know will have a direct positive impact on healthcare, which should encourage students to stick with OpenEMR after their project concludes. Additionally, having ownership of a part of the code is a nice way to motivate students to stick with the project. Our goal is to not simply have a student stick with the project, but to have the student become comfortable mentoring future new developers and students.

quartarian wrote on Friday, March 29, 2013:

Hey Brady,

I like yours! Here is my work in progress compiled proposal:
https://docs.google.com/document/d/11Imbs9x3gqpaLW0X60nZuqawztOmwdDuM8CswfsOCRs/edit?usp=sharing

bradymiller wrote on Friday, March 29, 2013:

Ok, here’s all the questions/answers (stuck mostly with Matt’s answers with some mods). There’s still time; feel free to modify and post here to further improve it. Here’s the current mentor list:
Rod Roark
Kevin Yeh
Brady Miller
Kevin McAloon
Kenneth Chapple
Brad Gregg (waiting for description)
Devi from Visolve (waiting for description)
A COUPLE MORE VENDORS AND Brad/Devi DESCRIPTIONS ARE NEEDED!!

And here are the current questions/answers:
a. Organization description:

The OpenEMR organization is a strong community of developers, physicians, medical professionals, open source activists, patients and concerned citizens all with the common goal of making the OpenEMR software package a superior alternative to its proprietary counterparts. The OpenEMR organization/community is dedicated to maintaining a spirit of openness, kindness and cooperation.

The OpenEMR software package is an open source electronic health records and medical practice management application that can run on almost any platform and is ONC Complete Ambulatory EHR certified. It received a 2012 Bossie Award in the “The Best Open Source Applications” category, is one of the most popular open source electronic medical records in use today with 3700 downloads monthly, and it has been estimated that OpenEMR is serving the medical records for more than 90 million patients worldwide.

b. Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?

The reason why we want to participate in Google Summer of Code is the same reason why so many small medical practices depend on us. We are a usable free (as in freedom) Electronic Medical Record solution that is surrounded by overly expensive proprietary solutions. Not only do we need to maintain the current OpenEMR feature set, we constantly need to navigate a complex set of laws, regulations and feature requirements that keep growing. To keep up with these changes and continue to grow, we continually need to invite new developers to join the project. Google Summer of Code will not only allow us to invite them, but entice them.

In no way is this a one way contribution. Our mentors are experienced developers that can provide a great deal of knowledge on web development that will be immediately beneficial for students. We will guide students on how to design software from an Object Oriented perspective that is clean and reusable. Students will learn how HTML/CSS/JS/PHP/SQL/Apache all work together to deliver web applications. Students will also get real-world experience of designing software that has explicit requirements that must be met. Furthermore, students will get the experience of working with an open source team and introduced to version control systems.

We feel we that our participation in Google Summer of Code will be mutually beneficial; to us, the students, the end-users who rely on us, and to the healthcare of millions.

c. What criteria did you use to select your mentors for this year’s program? Please be as specific as possible.
The criteria we used to select our mentors were experience, accessibility, and knowledge. We achieved this by singling out the most active, experienced, and instrumental contributors to the project and asked them to participate. OpenEMR is unique software in the respects of its complex problem domain, and having experts at the intersections of medicine and software engineering is a tremendous source of pride. All of our mentors have years of experience working with OpenEMR and would be ecstatic if given this opportunity to see the project and the students bettered.

<LIST OF MENTORS AND DESCRIPTIONS WILL GO HERE>

d. What is your plan for dealing with disappearing students?

As in medicine, the best approach to dealing with a problem is prevention. We plan on preventing disappearing students by carefully selecting those who are the most passionate about their project and nurturing them to success. Once we have carefully selected our students, we will then pair them with our experienced mentors, who are themselves crucial to the OpenEMR project. Everyone likes to feel needed, and while guiding the students to the success of their project, they will be actively engaged with the live force of ours. Furthermore, to hedge against personal issues between a mentor and their students, we will provide students with multiple contacts.

Of course, preventions have their limits. If we run into the issue of a disappearing student, the administrator will start by contacting the mentor to find out when the last engagement with the student was. If they are having any accessibility issues (or any other issues) with their mentor, the administrator will offer to have another mentor step in. Unfortunately, some students may choose to abandon their work, but we will do everything we can to help them stay interested.

e. What is your plan for dealing with disappearing mentors?
We see this as highly unlikely since the selected mentors are the most instrumental contributors to the project that have been with OpenEMR for years. If an incident were to occur, though, the administrator would contact the mentor directly and replace them if needed.

f. What steps will you take to encourage students to interact with your project’s community before and during the program?
OpenEMR is fortunate to already have many students engaged with the community, and we feel that one of the best ways to encourage additional students to interact with our community is by word of mouth between students. We are working to achieve this by actively interacting with these students on the forums, providing a developer wiki with a step-by-step introduction to committing bug fixes on GitHub, and encouraging active discussion about improvements that can be made to the project in a friendly environment. Ultimately we have tried to lower the barriers to entry to virtually zero. Once they become involved we also invite them to join in on the weekly OpenEMR voice conference call (Tuesdays at 9:30 AM PST).

Students who become involved during the program will be given multiple points of contact with direct lines of communication and assigned to personal mentors who will reach out to the students regularly.

g. What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?
We will do everything we can to ensure that our student’s code/project gets into the official codebase. It’s really an awesome feeling to contribute code to a project that you know will have a direct positive impact on healthcare, which should encourage students to stick with OpenEMR after their project concludes. Additionally, having ownership of a part of the code is a nice way to motivate students to stick with the project. Our goal is to not simply have a student stick with the project, but to have the student become comfortable mentoring future new developers and students.

bradymiller wrote on Friday, March 29, 2013:

Hi Matt,

We must of posted at the same time. Let me merge your stuff back in to create another revision and I will post it again.

-brady

quartarian wrote on Friday, March 29, 2013:

Oh no problem. The biggest changes were getting rid of the direct questions and adding a conclusion.

In the “What should a mentoring organization proposal look like?” FAQ by Google,  it seemed to hint that they may want a little extra besides their posted questions, and I though by getting rid of the direct questions as headers and adding the conclusion, it may imply that we gave them more :slight_smile:

That being said, Im find with whater you do. I like your version.

bradymiller wrote on Friday, March 29, 2013:

Hi,

Brought in your new stuff with only a couple minor mods. I added your conclusion to the end of the Organization description (note that application has a separate text field for each application question, but I like your idea of not rigidly staying entirely on subject). Let me know what you think and anybody feel free to post revisions/mods etc. Still have several hours left:

a. Organization description (OpenEMR):

The OpenEMR organization is a strong community of developers, physicians, medical professionals, open source activists, patients and concerned citizens all with the common goal of making the OpenEMR software package a superior alternative to its proprietary counterparts. The OpenEMR organization/community is dedicated to maintaining a spirit of openness, kindness and cooperation.

The OpenEMR software package is an open source electronic health records and medical practice management application that can run on almost any platform and is ONC Complete Ambulatory EHR certified. It received a 2012 Bossie Award in the “The Best Open Source Applications” category, is one of the most popular open source electronic medical records in use today with 3700 downloads monthly, and it has been estimated that OpenEMR is serving the medical records for more than 90 million patients worldwide.

The OpenEMR organization/community is truly special. The OpenEMR software package is literally used to keep people alive around the world. To do this effectively, the OpenEMR community has to constantly add features, fix security vulnerabilities, and follow strict and complex laws that are always changing. The OpenEMR community takes on this challenge every day and it is an amazing feeling to contribute to software that is so powerful and so important to so many. The OpenEMR community feels that we are the perfect fit for Google’s Summer of Code because we can spread this incredible feeling to students, while both nurturing their development and advancing OpenEMR.

b. Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?

OpenEMR is currently in a unique position. With new Medicare and Medicaid requirements and legal requirements to have EMR, many small practices are feeling tremendous pressure. In TIME magazine’s March expose on Healthcare, Bitter Pill: Why Medical Bills Are Killing Us, Steven Brill even discusses how small practices are being absorbed by large Hospitals, who can undoubtedly afford the huge investment that most EMR systems require. The combination of requirements and cost is why many small practices depend on us.

The reason why we want to participate in Google Summer of Code is the same reason why so many small medical practices depend on us. We are a usable free (as in freedom) Electronic Medical Record solution that is surrounded by overly expensive proprietary solutions. Not only do we need to maintain the current OpenEMR feature set, we constantly need to navigate a complex set of laws, regulations and feature requirements that keep growing. To keep up with these changes and continue to grow, we continually need to invite new developers to join the project. Google Summer of Code will not only allow us to invite them, but entice them.

We don’t however feel that this is a one way contribution. Our mentors are experienced developers that can provide a great deal of knowledge on web development that will be immediately beneficial for students. We will guide students on how to design software from an Object Oriented perspective that is clean and reusable. Students will learn how HTML/CSS/JS/PHP/SQL/Apache all work together to deliver web applications. Students will also get real-world experience of designing software that has explicit requirements that must be met. Furthermore, students will get the experience of working with an open source team and introduced to version control systems.

We feel we that our participation in Google Summer of Code will be mutually beneficial; to us, the students, the end-users who rely on us, and to the healthcare of millions.

c. What criteria did you use to select your mentors for this year’s program? Please be as specific as possible.
The criteria we used to select our mentors were experience, accessibility, and knowledge. We achieved this by singling out the most active, experienced, and instrumental contributors to the project and asked them to participate. OpenEMR is unique software in the respects of its complex problem domain, and having experts at the intersections of medicine and software engineering is a tremendous source of pride. All of our mentors have years of experience working with OpenEMR and they would be ecstatic if given this opportunity to see the project and the students bettered through Google Summer of Code.

d. What is your plan for dealing with disappearing students?

As in medicine, the best approach to dealing with a problem is prevention. We plan on preventing disappearing students by carefully selecting those who are the most passionate about their project and nurturing them to success. Once we have carefully selected our students, we will then pair them with our experienced mentors, who are themselves crucial to the OpenEMR project. Everyone likes to feel needed, and while guiding the students to the success of their project, they will be actively engaged with the live force of ours. Furthermore, to hedge against personal issues between a mentor and their students, we will provide students with multiple contacts.

Of course, preventions have their limits. If we run into the issue of a disappearing student, the administrator will start by contacting the mentor to find out when the last engagement with the student was. If they are having any accessibility issues (or any other issues) with their mentor, the administrator will offer to have another mentor step in. Unfortunately, some students may choose to abandon their work, but we will do everything we can to help them stay interested.

e. What is your plan for dealing with disappearing mentors?
We see this as highly unlikely since the selected mentors are the most instrumental contributors to the project that have been with OpenEMR for years. If an incident were to occur, though, the administrator would contact the mentor directly and replace them if needed.

f. What steps will you take to encourage students to interact with your project’s community before and during the program?
OpenEMR is fortunate to already have many students engaged with the community, and we feel that one of the best ways to encourage additional students to interact with our community is by word of mouth between students. We are working to achieve this by actively interacting with these students on the forums, providing a developer wiki with a step-by-step introduction to committing bug fixes on GitHub, and encouraging active discussion about improvements that can be made to the project in a friendly environment. Ultimately we have tried to lower the barriers to entry to virtually zero. Once they become involved we also invite them to join in on the weekly OpenEMR voice conference call (Tuesdays at 9:30 AM PST).

Students who become involved during the program will be given multiple points of contact with direct lines of communication and assigned to personal mentors who will reach out to the students regularly.

g. What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?
Once Google Summer of Code has ended, we will encourage students to stick with the project by doing everything we can to ensure that our student’s code/project gets into the official codebase. It’s really an awesome feeling to contribute code to a project that you know will have a direct positive impact on healthcare, which should encourage students to stick with OpenEMR after their project concludes. Additionally, having ownership of a part of the code is a nice way to motivate students to stick with the project. Our goal is to not simply have a student stick with the project, but to have the student become comfortable mentoring future new developers and students.

h. Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
Not applicable unless somebody knows somebody.

quartarian wrote on Friday, March 29, 2013:

Awesome. I think this is brilliant.

bradymiller wrote on Friday, March 29, 2013:

Hi everybody,

One more CRITICAL thing. The Backup Admin needs to register an account here and send me their username (gsoc will not let me submit the application without this). Would prefer Rod to do this since this was the initial plan, but at this point will take anybody (except for Matt of course since that may be a conflict of interest when choosing student applications :slight_smile: ) (I’ve already emailed Tony to do this, if possible). Then I can at least submit the application tonight in case I get hammered at work tomorrow AM and don’t have time to submit it.

Here’s where the backup admin needs to register:
http://google-melange.appspot.com/gsoc/homepage/google/gsoc2013

If do it, then email your username at brady.g.miller@gmail.com .

thanks,
-brady

sunsetsystems wrote on Friday, March 29, 2013:

I’ve registered as “sunsetsystems”.

Rod
www.sunsetsystems.com

bradymiller wrote on Friday, March 29, 2013:

wooohoooo,

The application is submitted. Here’s the Project/Idea page. I made one specific to the GSOC since according to the FAQ, this is very important:
http://www.open-emr.org/wiki/index.php/GSOC_2013_Projects

-brady
OpenEMR

bradymiller wrote on Saturday, March 30, 2013:

Hi everybody,

One more thing.

The GSOC application required an IRC channel, which we have. So, if you can, please park there:
irc://testnet.freenode.net/#openemr

thanks,
-brady
OpenEMR

bradymiller wrote on Saturday, March 30, 2013:

Totally forgot that we placed a github hook into the irc channel ( irc://testnet.freenode.net/#openemr ). So, after I made some commits this popped on in the irc channel:

->| GitHub101 (~GitHub101@router1-ext.rs.github.com) has joined #openemr
GitHub101 openemr pushed 2 new commits to master: http://git.io/DMqR_w
GitHub101 openemr/master fd45e7f Dinesh: Patient balance computation improvements on patient summary page….
GitHub101 openemr/master 2c138a0 bradymiller: Reduced the font size of the billing widget in previous commit
<-| GitHub101 has left #openemr

pretty neat, the more people we can park on the irc channel the better for the GSOC application. And you can then even watch the commit in real time…

-brady

bradymiller wrote on Tuesday, April 09, 2013:

Hi,

Got the official rejection from gsoc regarding our application. I pasted the email I got below. Again, thanks for everybody pitching in (especially Matthew). Next year can try again and shoot for OEMR doing this and trying to get current GSOC organizations to recommend us (there is a question in the application if an organization wants to recommend another organization).

-brady

Thank you for submitting “OpenEMR” organization application to Google Summer of Code 2013. >Unfortunately, we were unable to accept your organization’s application at this time. >Every year we receive many more applications than we are able to accommodate, and we would >encourage you to reapply for future instances of the program.

If you would like some general feedback on why your organization was not accepted, please >consider attending the IRC meeting in #gsoc on Freenode on Friday, April 19, 2013 at 16:00 >UTC.

Best regards,

Google Open Source Programs

deschel wrote on Tuesday, April 09, 2013:

Matt,

Now, that we know that you did not get funding, does your interest in OpenEMR end?

Or, do you think that you might still have time to work on your project part-time, as a hobby?

Any plans for the people who offered mentorship to still mentor Matt if he is interested?

Also, does anyone have time to go on the IRC channel to find out why OpenEMR was rejected?

David Eschelbacher MD

unclenate wrote on Tuesday, April 09, 2013:

I plan on attending the IRC meeting… Would be great to be locked and loaded with several projects for next year.

I’ll add that if you’re reading this thread and you’re interested in getting a jump-start towards OpenEMR development, here’s a primer from Ken Chappell on how to get your development environment set up, and submitting your code contributions to the OpenEMR project.

http://www.mi-squared.com/2013/04/dev-talks-how-to-develop-submit-changes-for-the-openemr-project/