First we would like to thank you all for your participation to that 11th European Connectathon. We hope to see you all of you in a future connectathon. We have appreciated the work with you although this was very stressful...
Here are your priorities for this morning.
For information about the social event and pick up of your coupon, please visit the front desk of the connectathon.
You can now mark test instances that need to be verified in priority as "Critical".
Monitor will now verify the test instances marked as critical first.
We had a late drop of an Order Filler actor in the MAWF actor. Because this actor has special requirements in this profile, we regret that we cannot complete tests of MAWF in Pisa.
We (always) have a limited number of Doc Sources supporting the Doc Addendum, Replacement, Transformation & Folder Mgmt option. We have updated the test today (Wed am) to show that a Registry can use the NIST toolkit to test these features if you cannot find an available Doc Source. We still prefer that you test with a vendor (and it's a better test), but we will allow you to complete the test with the NIST toolkit as an alternative.
Several of you reported yesterday that you are having difficulty with PIR tests because of a limited number of systems able to send an ADT^A08 or A40 to trigger a reconciliation. Because of this problem, we have decided to require only ONE successful PIR test (case1 or case4 or case5), rather than 3 tests, in order to “Pass” for your PIR actor. If you have questions, see Lynn at table E.
The proxy has been successfuly used on several test instances. Just check the option when the test is launched.
It will start the channels on the proxy if they are not already started. You will have to replace your target hosts/ports with the ip of the proxy (131.114.254.7) and the proxy port provided in Gazelle. It doesn't work with TLS tests.
Then a link appear each time you mark a step as to be verified, this link is forwarding to the proxy with some preset filters depending of the step.
If you have only one message that interests you in that list, you can add its permanent link in the step comment.
From the message page, you can validate it directly with the "Validate with EVSClient" link. The message (DICOM, HL7v2 or HL7v3) can then be validated.
The proxy GUI is available at http://gazelle.ihe.net/proxy/
The long term documentation : http://gazelle.ihe.net/content/proxy
If you have any question, come to see me next to E16, on the monitor table.
The NIST Tools will bring the Dashboard online on Tuesday. The dashboard will show the status of XDS Registries (up/down, which Repository it is paired with). In order for the tool to show the proper status, each Registry must have an entry for patient ID “911” in the Red domain (patient ID assigning authority 1.3.6.1.4.1.21367.13.20.1000). (Yes, even if you are a blue or green Registry, you should have this one “Red” patient in your database.) This allows the tool to submit a document for that patient. It will help if every Registry can make this entry on Tuesday morning.
For ATNA logging tests, you may chose any ARR partner. (the partner assignments in the spreadsheet were from the Chicago connectathon, Ignore them)
Good Morning.
Tuesday is the day where you should do a lot of peer to peer tests. Looking at yesterdays figured, I have realized that some new features from Gazelle were not used.
You can use the onsite proxy for HL7 (V2 and V3) and Dicom. When using the proxy make sure that you use the proxy port and the proxy IP instead of the actual configuration of your partner.
Using the proxy will capture the log for you, allow you to link them to the test steps and also will allow you for some type of messages to validate them. If you have questions about the proxy visit the pages on Proxy and/or ask Gabriel .
If you are not using the proxy note that we have the way for you to capture logs file at the step level. This allows you to attach log files segment (please only attach the relevant part of the logs to the step) or link a test step to a sample
This makes the log reading easier, allows the used of validation tools on the attached files.
See how to do it there:
To help XDS.b and XDS-I.b testing get started on Monday and Tuesday, we make partner assignments for Registry, Repository and Source systems. Consumers are not assigned, but use these partners for query and retrieve tests.
