Blog

13 Apr 2011

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.

 

12 Apr 2011

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.

12 Apr 2011

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)

12 Apr 2011

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: 

28 Mar 2011

The following text is the content of the NDA section of the contract signed by participants to the Pisa Connectathon

 

The Integrating the Healthcare Enterprise ("IHE") initiative has the goal of stimulating integration of information and imaging systems used in the delivery of healthcare. IHE develops guidelines and supports a testing process and other activities to encourage the implementation of standards to enable communication among such systems.

23 Mar 2011

Thanks to Chung-Yueh Lien from the Institute of Biomedical Engineering at the National Yang-Ming University, Taiwan we are now offering the generation of dummy patient data for Taiwan within the Demographic Data Server application.


Please visit the documentation of the tool to find out how to use it as web service and feed your SUT with dummy patient data.

 

23 Feb 2011

Gazelle offers the participants to the epSOS projectathon in Pisa the ability to share samples. 

Visit the page : Connectathon -> List of samples to find out which document you need to share with your partners. 

 

PS + ePresc

NI-A -> Friendly-A ->  NCP-A -> pivot -> NCP-B -> Friendly-B -> NI-B

 

eDisp

NI-B -> Friendly-B ->  NCP-B -> pivot -> NCP-A -> Friendly-A -> NI-A

9 Feb 2011

These tables suggest the list of actors and profiles that systems can implement.

  • NCP-B and Portal-B can be grouped together. 
  • NCP-A and Portal-A can be grouped together. 
  • R/O Column defines the requirement : R means required, O means optional

NCP-A

 

Profile

Actor

Option

R/O

       

epSOS-Authentication

NCP-A

 

R

epSOS-IdentificationService

NCP-A

 

R

8 Feb 2011

RootOID

 

AT     2.16.17.710.780 

CZ     2.16.17.710.804 

DE     2.16.17.710.803 

DK     2.16.17.710.802 

EE unknown

ES     2.16.17.710.801 

FR     2.16.17.710.790 

GR     2.16.17.710.808 

IT     2.16.17.710.806 

IH 2.16.17.710.812

NL     2.16.17.710.810 

SE     2.16.17.710.807 

SI unknown

SK     2.16.17.710.805 

TR     2.16.17.710.813 

UK     2.16.17.710.809

 

 

 

Codes for CDA documents content are provided in MVC spreadsheet are non ambiguous and published there as XML: 

Pages

Subscribe to RSS - blogs