- About Us
- My OSEHRA
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 :)
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
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)
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.
Despite the unexpected bump in the road in early May (see the May 11th blog post here), Sprint 5 certainly got us to a point where we were able to submit our refactored Problem List.
Our major objectives of Sprint 5 were to:
- Wrap up testing from Sprint 4
- Submit the refactored Problem List and all associated tests (M-unit and functional) for certification
- Validate our updated XINDEX-based tool
Some of our major successes were:
We previously told the community that our goal was to submit our unit tests, functional tests, scripts, and refactored Problem List code in early May.
This original schedule slipped slightly when we encountered problems with transactions in the GTM environment for our unit and functional tests. We have been able to find workarounds for the unit tests, but are still investigating the functional tests.
Any fool can write code that a computer can understand. Good programmers write code that humans can understand. (M. Fowler)
On the road to Sprint 4, our team tackled Sprint 3 to the ground and just kept going! We wrapped up on April 6th, and were able to achieve the following:
So it seems that with two Sprints under our belts we’re ready to take on another! Sprint 2 really let us hit the ground running, and Sprint 3 is looking like it will put us in a really stable place in terms of what we can offer for a refactored Problem List module.
Some of the high-level success of Sprint 2 were: