"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 :)

For those followers unfamiliar with our Scrum methodology, we implement 4 week Sprint cycles and try our best to post an update here at the end of each of those. Certainly if you have any feedback or questions in between these postings, are our team is ready to provide responses to whatever questions you may have.

As for this month’s blog post, our team would like to share an inclusive update for Sprints 1-3; these updates will touch on our team’s refactoring efforts, M-Routine Analyzer updates, system test platform work, VOLDEMORT creation, and MU certification efforts.

Major accomplishments:

  • General
    • Presented refactoring and testing strategies and accomplishments at the OSEHRA Summit at National Harbor in mid-October
  • VOLDEMORT (Conor makes far more exciting and thorough posts here, so check ‘em out)
    • Demos provided 10/15, 11/5 to Customer, stakeholders, and other management personnel
    • Delivered to UAT 12/1
    • Delivered final, UAT tested tool 12/15
  • VistA System Test Platform
    • Delivered SSH support for Automated Testing Framework (ATF) in October and added this to the OSEHRA Automated Testing tool in November
    • Prototype implementation and updates (improved SSH connection control and project linking) of VistA Roll-and-Scroll Recorder (RASR) and SSH feature of ATF demonstrated in October and December to Customer
    • Integrated Selenium support into ATF and created prototype Selenium test scripts in December
    • Started to investigate more advanced Sikuli image control to improve test portability
  • Refactoring
    • Scheduling – Appointment Manager menu items not previously refactored were added to the API in October
    • Hard coded messages in Problem List and Scheduling – Appointment Manager menu relayed code were moved to DIALOG file in October
    • Began refactoring Admission, Discharge, and Transfer (ADT) module with concentration on Bed Control menu in November
    • Wrote new and updated existing tests for respective modules/packages being refactored
  • M-Routine Analyzer
    • Java test code improved; now able to be switched from abbreviated form of commands, intrinsic variables, intrinsic functions, and structure system variables to full forms and vice versa
    • Refactored code for implementation of recursive M entry tag fan-in information
  • MU
    • Attended MU off-site in Albuquerque, NM mid-October

Upcoming objectives for Sprint 4:

  • Revise Scheduling – Appointment Manager technical journal and execute bug fixes
  • Refactor ADT Bed Control, prepare technical journal, and prep for certification submission (dependent on testing)
  • Update ADT and Scheduling functional tests according to technical journal updates and bug fixes
  • Submit completed ADT test scripts to OSEHRA
  • Add Scheduling tests and Problem List tests per Jira tickets
  • Revise Problem List technical journal and execute bug fixes (mostly repackaging)
  • Update RASR features per Jira tickets
  • Finalize RASR design and user documentation
  • Continue Stage 1 vs. Stage 2 MU assessment

More details will be shared as they become available for our next webinar. Until then or until we’ve reached the end of our current Sprint, please post any questions or discussion topics here.

 

 

like0

Comments

ADT APIs

Ayman Ghaith's picture

Dears,

Does ADT APIs finished ,, and if yes, how i can get them.

 

Best Regards.

like0

Re: ADT APIs

Peter Li's picture

Hi Ayman,

The ADT API was never finished.

Peter

like0

Thanks Peter,

Ayman Ghaith's picture

Thanks Peter,

If we need to start developing it , does there any advice, notes or documents can help us ?

 

 

like0

"There comes a time in the history of any project when it...

Peter Li's picture

Here is the link to the OSEHRA Technical Journal entry submitted by the PwC on the ADT API back in 2013 - http://code.osehra.org/journal/journal/view/87. It included code and documentation.

Peter

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of Ayman Ghaith
Sent: Tuesday, July 26, 2016 9:12 AM
To: EHR Refactoring Services
Subject: Re: [ehr-refactoring-services] "There comes a time in the history of any project when it becomes necessary to shoot the engineers...

Thanks Peter,

If we need to start developing it , does there any advice, notes or documents can help us ?

--
Full post: https://www.osehra.org/blog/there-comes-time-history-any-project-when-it...
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/260

like0

Thanks a lot Mr peter, this

Ayman Ghaith's picture

Thanks a lot Mr peter, this will help us for sure.

like0

Dear Mr Peter,

Ayman Ghaith's picture

Dear Mr Peter,

Thanks again for the link, we are testing it and till now it is working fine for us,

but i am wondoring , what did it take to refactor such a huge package like ADT? how many days they spent and how much developers wored on the patch you sent !!  Because for me i think it will take minimum a month for three resources ,

 

Best Regards.

like0

Re: ADT APIs

Peter Li's picture

PwC did the refactoring on a VA contract.   It was over many months and with couple engineers.  I don't have the exact details.

I could get you a contact if you send me an email at lip@osehra.org

like0

I sent you an email but i am

Ayman Ghaith's picture

I sent you an email but i am afraid it moved to junk or spam folder.

 

ayman,

 

like0

"There comes a time in the history of any project when it...

Sam Habiel's picture

Ayman,

I am glad to hear that it's actually working.

--Sam

On Fri, Aug 5, 2016 at 6:16 AM, Peter Li
wrote:
> PwC did the refactoring on a VA contract. It was over many months and with
> couple engineers. I don't have the exact details.
>
> I could get you a contact if you send me an email at lip@osehra.org
>
> --
> Full post:
> https://www.osehra.org/blog/there-comes-time-history-any-project-when-it...
> Manage my subscriptions: https://www.osehra.org/mailinglist
> Stop emails for this post:
> https://www.osehra.org/mailinglist/unsubscribe/260

like0

Yes it is working :D, at

Ayman Ghaith's picture

Yes it is working :D, at least for the three main options that we tested till now (admit,discharge and transfer patients) , and they really did a great job.

like0

"There comes a time in the history of any project when it...

Peter Li's picture

You guessed. I’ll forward this request shortly.

Peter

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of Ayman Ghaith
Sent: Sunday, August 7, 2016 1:36 PM
To: EHR Refactoring Services
Subject: Re: [ehr-refactoring-services] "There comes a time in the history of any project when it becomes necessary to shoot the engineers...

I sent you an email but i am afraid it moved to junk or spam folder.

ayman,

--
Full post: https://www.osehra.org/blog/there-comes-time-history-any-project-when-it...
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/260

like0