XDR Test 1 RegistryError

[Pepper Pancoast]

Hello,

On XDR Test 1, we are getting a registryerror back without more details.

Failed to send XDR message to:https://ttpedge.sitenv.org:11084/xdstools/sim/edge-ttp__1/rep/xdrpr for sendertestcase1@ttpedge.sitenv.org from conor.sullivan@netsmarttest.com.  Transmitter StatusMessage: RegistryError #1:<<<>>>

Can you provide more details on what/why this RegistryError occurred?

[Kim Poletti]

Hi - Thanks for reaching out. This has been logged for review and a member of the team will reach out in the near future.

[Pepper Pancoast]

Thanks!  Any chance we'd get some feedback today?  We're prepping for our certification.

[Sai Valluripalli]

If you are using https endpoint you have to replace your certs with the certs provided by the tool.

Alternatively, you can use a http endpoint.

Thanks

[Pepper Pancoast]

Thank you, but this is outbound, so I'm calling into your endpoint and getting this error back.

We are passing those net new certs in this workflow.

Can you see an error message saying we aren't?

[Sai Valluripalli]

SOAP messages should be in MTOM format.

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/41d4a264-d325-456a-b655-e8da694a1957n%40googlegroups.com.

[Pepper Pancoast]

I just double checked and we do seem to be sending in MTOM format.
I was able to decrypt your response and saw

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><S:Header><wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope" s:mustUnderstand="1">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse</wsa:Action><wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:9e7b45bd-0f53-4205-ae05-25441b7ac67a</wsa:RelatesTo></S:Header><S:Body><rs:RegistryResponse xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure"><rs:RegistryErrorList><rs:RegistryError codeContext="Multiple Patient IDs found in submission: [1, 1^^^&amp;2.16.840.1.113883.3.3569.4714.999.1&amp;ISO]" errorCode="XDSPatientIdDoesNotMatch" location="PatientId" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></rs:RegistryErrorList></rs:RegistryResponse></S:Body></S:Envelope>

Where is the PatientID match happening against which elements?  I only saw the latter ID in the PatientID xml elements.

[Pepper Pancoast]

We got it figured out, it was the XDSSubmissionSet.PatientID.

The only other question we have is the test is staying at Pending even though we got a successful response back.

Should we be sending to some specific address?

[Sai Valluripalli]

The XDR SOAP that is being sent to the tool should have a Header and also a </direct:addressBlock> with Direct to and Direct from address. You will pass this test if Direct From Address entered on the before running the test matches with what is being sent in the Header direct:addressBlock

[Pepper Pancoast]

Just to confirm, because I don't have direct: in the element, would that cause it to not be picked up?

<addressBlock xmlns="urn:direct:addressing"

      xmlns:NS1="http://www.w3.org/2003/05/soap-envelope" NS1:relay="1" NS1:role="urn:direct:addressing:destination">

      <from xmlns="urn:direct:addressing">oncte...@theraoffice2.medalliesdirect.org</from>

      <to xmlns="urn:direct:addressing">sendert...@ttpedge.sitenv.org</to>

      <metadata-level xmlns="urn:direct:addressing">XDS</metadata-level>

      <X-DIRECT-FINAL-DESTINATION-DELIVERY xmlns="urn:direct:addressing">true</X-DIRECT-FINAL-DESTINATION-DELIVERY>

    </addressBlock>

This is what we have, and I'm curious if since it's just addressBlock, if that'd cause us to not pass?

[Sai Valluripalli]

The header should conform to the XDR IHE specifications. Example below -

<direct:addressBlock xmlns:direct="urn:direct:addressing"
            soapenv:role="urn:direct:addressing:destination" soapenv:relay="true">
            <direct:from>exa...@example.com</direct:from>
            <direct:to>aexa...@example.com</direct:to>
            <direct:X-DIRECT-FINAL-DESTINATION-DELIVERY>true</direct:X-DIRECT-FINAL-DESTINATION-DELIVERY>
        </direct:addressBlock>

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/8cd7f91f-2615-4c2a-bb93-21a0d66bb39cn%40googlegroups.com.

[Pepper Pancoast]

Can you double check, our XDR validator is showing this as valid, but we're still not getting a success.

        <direct:addressBlock xmlns:direct="urn:direct:addressing" relay="true" role="urn:direct:addressing:destination">

            <direct:from>360xte...@nseuatmoqa.medalliesdirect.org</direct:from>

            <direct:to>sendert...@ttpedge.sitenv.org</direct:to>

            <direct:X-DIRECT-FINAL-DESTINATION-DELIVERY>true</direct:X-DIRECT-FINAL-DESTINATION-DELIVERY>

        </direct:addressBlock>

[Pepper Pancoast]

Not sure if it helps, but I grabbed more of the payload and defined the soapenv namespace

<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><S:Header><To xmlns="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:mustUnderstand="true">https://ttpedge.sitenv.org:11084/xdstools/sim/edge-ttp__1/rep/xdrpr</To><direct:addressBlock xmlns:direct="urn:direct:addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:relay="true" soapenv:role="urn:direct:addressing:destination"><direct:from>oncte...@theraoffice2.medalliesdirect.org</direct:from><direct:to>sendert...@ttpedge.sitenv.org</direct:to><direct:X-DIRECT-FINAL-DESTINATION-DELIVERY>true</direct:X-DIRECT-FINAL-DESTINATION-DELIVERY></direct:addressBlock><MessageID xmlns="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:mustUnderstand="true">uuid:4fb1cc9a-bb15-46b8-a155-66bc1fd53ee5</MessageID><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b</Action><ReplyTo xmlns="http://www.w3.org/2005/08/addressing">

[Sai Valluripalli]

<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <direct:metadata-level xmlns:direct="urn:direct:addressing">minimal</direct:metadata-level>
    <direct:addressBlock xmlns:direct="urn:direct:addressing" soapenv:relay="true" soapenv:role="urn:direct:addressing:destination">
        <direct:from>#DIRECT_FROM#</direct:from>
         <direct:to>#DIRECT_TO#</direct:to>
    </direct:addressBlock>
    <wsa:To soapenv:mustUnderstand="true">http://example/xdrmessagevalidator/Dispatcher/XDRService.wsdl</wsa:To>
    <wsa:MessageID soapenv:mustUnderstand="true">urn:uuid:AD26219DC8B723A59C1717776435403</wsa:MessageID>
    <wsa:Action soapenv:mustUnderstand="true">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b</wsa:Action>
</soapenv:Header>

This is an example of SOAP header with limited metadata that the tool expects. Make sure your XDR message adheres to the above format.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/68c8e000-b6e7-4788-aca1-e6dac86d85b2n%40googlegroups.com.

[Pepper Pancoast]

I'm still stuck because the only difference I can really find is listing namespaces, which I wouldn't imagine would flag us as that doesn't seem defined in the spec.

<S:Header>

    <direct:metadata-level xmlns:direct="urn:direct:addressing">minimal</direct:metadata-level>

    <direct:addressBlock xmlns:direct="urn:direct:addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:relay="true" soapenv:role="urn:direct:addressing:destination">

        <direct:from>oncte...@theraoffice2.medalliesdirect.org</direct:from>

        <direct:to>sendert...@ttpedge.sitenv.org</direct:to>

    </direct:addressBlock>

    <To xmlns="http://www.w3.org/2005/08/addressing" xmlns:mustUnderstand="true" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:mustUnderstand="true">https://ttpedge.sitenv.org:11084/xdstools/sim/edge-ttp__1/rep/xdrpr</To>

    <MessageID xmlns="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:mustUnderstand="true">uuid:2cefd3f0-f5e8-4213-bd2c-bd3011b9a639</MessageID>

    <Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b</Action>

</S:Header>

[Sai Valluripalli]

From the logs it looks like your header and metadata are correct. But the content of the XDR CCDA you are sending is not correctly formatted.

It fails when ETT tries to validate it.

2024-06-07 12:51:18 INFO ResponseHandler:? - found correlation with existing record using direct from address and simId : oncte...@theraoffice2.medalliesdirect.org , edge-ttp__1
2024-06-07 12:51:18 INFO TestCase:? - XDR Test Case 1: Metadata was minimal and NO errors detected by toolkit.
2024-06-07 12:51:18 INFO TestCase:? - Validating CCDA ccda with validation objective 170.315_b1_ToC_Amb and reference filename 170.315_b1_toc_amb_sample1_v2.pdf
org.json.JSONException: A JSONObject text must begin with '{' at 1 [character 2 line 1]

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/7a3fb3ac-aed7-4ca9-a5d9-3156fcf69e1bn%40googlegroups.com.

[Pepper Pancoast]

Our CDA is in XML, it isn't in JSON.

Here's the CCD from our payload.  I can send over the pcap showing the headers being set to XML as well

[Alan Woolsey]

@Sai can we please get an update? This is the only thing left to complete our cert and we have to have it done asap to meet the regulations. Using the Direct XDR test tool at https://site.healthit.gov/sandbox-direct/xdr yields the same issues. All examples and required test ccd files from Health IT are in XML and so your log showing the tool trying to parse as json is confusing. As I said this is very critical for us to complete so any update would be greatly appreciated. 

[Sai Valluripalli]

"https://site.healthit.gov/sandbox-direct/xdr yields the same issues" meaning, you sent from site.healthit.gov to ETT and see the same issue? I sent an XDR from SITE to ETT and it works fine. ETT also validates the CCDA you sent in XDR. To validate ETT parses the MTOM content and validates the CCDA.

I'd advise you to sendXDR  from SITE to ETT (because it works) look at the payload being sent and send the XDR to ETT in a similar way to pass XDR 1.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/90f5a14a-4a0d-489b-892d-5051146c446cn%40googlegroups.com.

[Alan Woolsey]

Just as Pepper reported, we never get off of Pending Refresh.
I attached the steps I went through using site.healthit.gov. Do you see anything in the log for that?

[Sai Valluripalli]

I was able to run XDR 1 from SITE. See screenshot below. I used the same direct addresses as you shared in the attachement.

You received this message because you are subscribed to a topic in the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/edge-test-tool/acmYBy-nXVM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to edge-test-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/fe6b5eae-731b-467b-98ac-6bc2d5700672n%40googlegroups.com.

[Alan Woolsey]

I can get it to work doing what you are doing, but the problem is in your example, you are not selecting the cures checkbox. If you check that box you will not get the same samples you picked. If you choose 170.315_b1_toc_amb_sample1_v2.pdf it is not getting past pending refresh.

[Sai Valluripalli]

Are you running the test from here - https://ett.healthit.gov/ett/#/certification/certb1?

If so, can you please try running it from here - https://ett.healthit.gov/ett/#/edge/xdr (Select your system as sender)

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/0b2ba5c4-cc60-4933-8f34-951cca3d9455n%40googlegroups.com.

[Alan Woolsey]

Yes I am running it from  https://ett.healthit.gov/ett/#/edge/xdr (Select your system as sender). Here is another file showing all the steps I took including the url in the screen shots. Again the problem seems to be if you select the cures check box and pick one of those samples, it doesn't work. 

[Stephanie Barnett]

Through extensive testing - We have also found the CURES checkbox causes our system to be unable to send to the ETT. 

I have a thread where we've been going through extensive internal testing and my outcomes are the same - the CURES checkbox doesn't exit the PENDING REFRESH status even when a valid payload is sent.
https://groups.google.com/g/edge-test-tool/c/sshnpl4C2RU