Testing

Next OSEHRA Interoperability Work Group Meeting - Wed., Jan. 14, 2015 at 3:00 PM (EST) - Topic: 2015 Roadmap & Planning Session

Next Meeting of the OSEHRA Interoperability Work Group (IWG) will be held on Wednesday, January 14th at 3:00 PM (EST).  All are welcome to join the meeting through WebEx, below you will find the login information. We are currently seeking new open source vendor, Federal agency and industry participations for our work group.

OSEHRA Certification Tutorials Blog II

Stewardship of the code entrusted to its care is an important part of the mission of OSEHRA. This stewardship requires that OSEHRA take care that the code it accepts and certifies meets community standards for understandability, usability and correctness. Achieving this is not easy and the processes and procedures used can be difficult to apply.

OSEHRA Certification Tutorials Blog I

Stewardship of the code entrusted to its care is an important part of the mission of OSEHRA. This stewardship requires that OSEHRA take care that the code it accepts and certifies meets community standards for understandability, usability and correctness.

Source of DICOM Images for Testing

During today's imaging work group call I mentioned that The Cancer Imaging Archive(TCIA) is available as a source of test images.  TCIA is an open access information repository to support cancer research.  It is also a ready source of DICOM images from most modalities and vendors that can be used for testing purposes.  You can review the available images on the collections page.

The Official Launch of the OSEHRA Interoperability Work Group (IWG)

@OSEHRA is pleased to announce that Mario Hyland (@Interopguy) as Chair for the new OSEHRA Interoperability Working Group (IWG).

OSEHRA Call for Work Group Participation is now OPEN.  We are currently seeking new open source vendor, Federal agency and industry participations for our work group. Please e-mail Barry Dickman if you would like to volunteer and participate in our work group.

‘It’s the eye of the tiger, it’s the thrill of the fight…’ [Survivor]

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:

Baby Got Backlog

This week initiates a technical take on Sir Mix A Lot’s approach: our team has adopted our product backlog! And while it’s not yet that big, it has been broken into three sections: dependencyrefactoring of Problem List, and testing of Problem List.  It goes without saying that it is certainly subject to revisions as we gain Lessons Learned from Problem List and start planning for future modules to refactor (again, if time permits since we near the end of our contract in September).

Subscribe to RSS - Testing