Inferno-Program Implantable Device tests are not executing

[ashu-bdvt]

Thank you for reporting a possible bug in Inferno! Please fill in as much of the template below as you can.

Subject of the issue Inferno Program edition Implantable Device tests are not getting executed. It is stuck at the very first test. Even after waiting for ~ 1hr no progress or no errors

The same test gets executed in my local inferno-program instance(running on docker)

Your environment

• Edition of inferno (Community or Program): Program
• Version of inferno: 1.9.0
• Which browser and version(s) is the bug present on?: Chrome

Steps to reproduce Just run the "Single Patient" tests for the below endpoint and patient Endpoint: https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d Patient: 12753537 Device: No need to give anything since it works in my local setup without it, however if needed please use 31563397

Include:

• The selected test suite
• The URL of the FHIR server being tested
• The Test ID, if it's a problem with a specific test.
• Any required configuration options (client ID, client secret, etc.)
• Anything else needed to make the issue occur. Screenshot:

Expected behavior Implantable device tests should run on the remote interno-program instance

Actual behavior Implantable device tests is not running on the remote interno-program instance

[ashu-bdvt]

Attaching local validation where these test are passing

[yunwwang]

Hello @ashu-bdvt Can you provide test-id for your test session? Thanks

[ashu-bdvt]

How do i get tht? I just cancelled the sequence and saved the instance at https://inferno.healthit.gov/inferno/3uo33ovEqrn/

[yunwwang]

What is the Device.type? It is a strange character when I query using Postman

[ashu-bdvt]

That's an interesting find. I also see the same special character via postman. However when i run against the same endpoint in my local inferno instance, it's just a plain empty string and the tests are passing. Do you think it's what causing the failure?

[yunwwang]

What I observed is that the state shows Device's ID which means Inferno did get that Device resource but something happened and crashed the process.

My first thought was the Device resource was invalid.

The resource you posted is strange. If the Device.type.text is empty, why do you have that element there?

[yunwwang]

@ashu-bdvt Our investigation indicate that you may send this in your Device resource

"type": {
  "text": "\u0000"
}

Though it is valid in FHIR, it is highly not recommended because it does not carry any meaning. If you don't have type, you should follow the US Core Missing Data section

[arscan]

I do not think we will fix this in v1.x, because there doesn't seem to be a good reason to send characters like this and we are not planning on any releases on 1.x. However, we could fix it in v2.x if you are seeing this over there as well. Have you had a chance to move over to that new version?