kthlnkeating's blog

We've reached the end of the line.

The Open Source EHR Services Project has finally come to an end, including all refactoring and API development, the VistA System Test Platform Project, Eclipse Plug-in Tool Project, and VOLDEMORT Tool Project. We want to thank you all for all of your dedicated following and input that have influenced each project's success and contributions to the open source community.

We’ve finally reached the end of the line.

The Open Source EHR Services Project has finally come to an end, including all refactoring and API development, the VistA System Test Platform Project, Eclipse Plug-in Tool Project, and VOLDEMORT Tool Project. We want to thank you all for all of your dedicated following and input that have influenced each project's success and contributions to the open source community.

Let's raise a glass of bubbly to mark this momentous occasion!

Problem List has finally made its way out of the OSEHRA Certification Group's OTJ queue! Our team's greatest thanks is extended to all who had a hand in making this milestone possible...

Now on to the next! : )

"The effective programmer is keenly aware of the limited size of his own head." - ascribed to Edsger W. Dijkstra

You may be asking yourself -- "Wait...the refactoring team is still out there?"

Why yes, yes we are...we've just had a brief (okay, maybe not so brief) break in making sure this blog is kept up to date. HOWEVER, we're back in business and ready to keep you in-the-loop on what the team has been working on and where we're headed.

Survey: Next Module to Refactor

OSEHRA community members,

As we put finishing touches on Problem List, Scheduling, and ADT, the team is looking to decide which module to refactor next -- and we would love for you to share your knowledge and input! The survey is available after the jump, but please leave any discussion topics, comments, or questions you have here. We are all looking forward to an engaging discussion around the challenges/benefits you anticipate with any of the options presented.

 

"There comes a time in the history of any project when it becomes necessary to shoot the engineers...

...and begin production." - Anonymous

Since our last Sprint update from September there have been a lot of changes in the mix for our team’s efforts...and a number of these changes have impacted our availability to post regularly to this page – our sincerest apologies to you all! However, the team is back in business and ready for more timely updates :)

Any problem in computer science can be solved with another layer of indirection. -D.Wheeler

Our team is happy to report that presentations, discussions, and collaborations at the VistA Expertise Network Symposium and Expo last week went really well. It was great to finally meet some of our supporters and followers in person! For a copy of our refactoring and test framework presentations, please navigate here.

We will encourage you to develop the three great virtues of a programmer: laziness, impatience, and hubris.– L.Wall, R.Schwartz

The main benefit from Sprint 6 was that we formally submitted our refactored Problem List code for OSEHRA certification. Other major successes of Sprint 6 were that we:

·      Executed final bug fixes for dependency improvements and finished all testing for Problem List

·      Continued Scheduling refactoring (Appointment Manager)

·      Automated Sikuli CPRS tests

Open Source EHR Refactoring Services webinar, 6/22

For all interested: this presentation will be a code level review and will cover the updates our team has incorporated thus far. For more information, we hope you'll join on Friday!

When: Friday, June 22nd, 10:00-10:50am EST

Where: 800-767-1750, 19996#; http://infiniteconferencing.com/join/, participant code 87683695 (all fields must be filled in to join the conference)

Availability poll for EHR Refactoring Services teleconference - either 6/21 or 6/22

For those interested in attending a detailed call on what our team has been working on, please select the time(s) best available for you here (it would be most appreciated if you included your name with your response) by this Friday, 6/15.

Once the most common time has been identified, an additional blog post will be available here with the call-in and web visual access information; it is anticipated that the meeting will not run any longer than 60 minutes.

Thank you!

Syndicate content