| |
|
|
| |
|
| Visit STEMSOFT at the following events: |
|
 |
Tandem BMT Meetings; Orlando, FL |
| |
FEB. 24-28, 2010 | BOOTH #4 |
|
 |
Canadian Blood and Marrow Transplant Group (CBMTG); Vancouver, BC |
| |
APRIL 7-10, 2010 |
|
 |
International Society for Cellular Therapy (ISCT); Philadelphia, PA |
| |
MAY 22-25, 2010 |
|
 |
International Cord Blood Symposium; San Francisco, CA |
| |
JUNE 4-5, 2010 |
|
 |
|
| If you know of other events STEMSOFT should be present at please let us know. |
|
 |
 |
|
|
|
 |
|
|
 |
|
|
|
|
|
| |
|
STEMSOFT is pleased to announce that the public release date for STEMSOFT BMTbase™ 4 for MS SQL Server is February 22nd, 2010. As you may already know, BMTbase has been completely redesigned to use the new AGNIS 2 service for retrieving your submitted CIBMTR forms. Over the next few weeks, the STEMSOFT development, quality control and documentation teams will be working hard to put the finishing touches on this much anticipated release. When the software is made generally available, all customers whose maintenance plan is in good standing will receive detailed instructions for downloading, installing and using the new software. If you are unsure of the status of your institution’s STEMSOFT maintenance and support plan, please contact STEMSOFT Customer Support.
Following the release of STEMSOFT BMTbase 4 for MS SQL Server, the STEMSOFT team will complete validation of the Oracle version of the application. The public release date for STEMSOFT BMTbase™ 4 for Oracle has not been determined at this time however every effort is being made to ensure that the lag between release dates is as short as possible. |
| BY GEOFF BROWNE, PRODUCT MANAGER |
|
|
|
|
|
| |
|
Piers Coleman joined the STEMSOFT team 1 year ago as STEMSOFT’s R&D Manager/Architect. He has been extremely busy positioning us for our new product development.
“STEMSOFT has streamlined our software development process for new products by using Agile best practices. Through a process of continuous planning and feedback. STEMSOFT is able to ensure that value is maximized throughout the development process. As a result of this iterative planning and feedback loop, teams are able to continuously align the delivered software with desired business needs, easily adapting to changing requirements throughout the process. By having a continuous integration build environment and delivering internal nightly builds to the quality control department, much more accurate visibility into the actual progress of projects is available. As a result of following an Agile process, at the conclusion of a project is a software system that addresses the business and customer needs much better.”
- Piers Coleman, R&D Manager/Architect
|
|
|
|
|
|
| |
|
|
| |
|
|
|