1 / 20

Use of the MESA Tools

Use of the MESA Tools. Steve Moore Mallinckrodt Institute of Radiology. Outline. New in 2004 Requirements Interpreting results of tools Bug reporting. Supported Operating Systems. Windows NT Windows 2000 Redhat Linux (7, 8) Sun Solaris (7, 8). New in 2004 - Radiology. PDI NM

codymartin
Download Presentation

Use of the MESA Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Use of the MESA Tools Steve Moore Mallinckrodt Institute of Radiology

  2. Outline • New in 2004 • Requirements • Interpreting results of tools • Bug reporting MESA Tools

  3. Supported Operating Systems • Windows NT • Windows 2000 • Redhat Linux (7, 8) • Sun Solaris (7, 8) MESA Tools

  4. New in 2004 - Radiology • PDI • NM • SWF Options • Appointment notification • Instance availability notification MESA Tools

  5. New in 2004 - Cardiology • Cath workflow • Echo workflow • ECG display MESA Tools

  6. New in 2004 – IT Infrastructure • XDS – through NIST • PDQ • ATNA • PWP MESA Tools

  7. Outline • New in 2004 • Requirements • Interpreting results of tools • Bug reporting MESA Tools

  8. Requirements – Due Dates MESA Tools

  9. What Tests Are Required? • Each actor has one or two documents that lists the tests for that actor; these docs are independent of Integration Profile • IHE-Europe web tool will be used to indicate which tests are required for your system • You should see a personalized list of requirements for each registered system MESA Tools

  10. Outline • New in 2004 • Requirements • Interpreting results of tools • Bug reporting MESA Tools

  11. MESA Test Format • User runs an interactive Perl script that • Announces each message to be sent to you • Prompts you for messages that you should send to a MESA actor • A second, evaluation script is then run to examine the messages produced by your system MESA Tools

  12. MESA Evaluation Output • Each evaluation script has output in subsections • 103.1 • 103.2 • 103.3 • Each subsection evaluates a specific message or part of a transaction MESA Tools

  13. Format of Evaluation Output • Each test assumes a MESA example message that is 100% accurate • Test output shows differences between your message and the MESA message • The bottom line of the test output is the number of differences found • When the number of differences reaches 0, you are done! MESA Tools

  14. What Do I Do If I Don’t Pass? • Determine which subsection has failed; there might be more than one • Use the differences to see what you should have included in your message • Correct the difference and rerun the test • Ask the Project Manager if the test output is too obscure MESA Tools

  15. What Are Warnings? • Some evaluation scripts will produce warnings • These are items that are probably suggested by the framework but not required • The evaluation output is usually clear about warnings and does not count these as failures MESA Tools

  16. Are There Some Differences That Are Tolerated? • If they are items one enters by hand, probably yes • If they are items one receives/maps from another message, absolutely not • If they are coded items, absolutely not MESA Tools

  17. Overriding Assumption • MESA tools assume the user has read and understood the relevant sections of the TF • The tools may not explain failures nor do they indicate where to find answers in the framework • Some scripts give pointers into the framework, but this is a works in progress MESA Tools

  18. Outline • New in Year 5 • Requirements • Interpreting results of tools • Bug reporting MESA Tools

  19. Bug Reports - Bugzilla • We use bugzilla for tracking bug reports • You can also send us email if you are not sure if this is a bug MESA Tools

  20. Web Address • www.connectathon.net • Managed by Glen Marshall, SMS • Will have public connectathon information • Will have pointers to private information MESA Tools

More Related