You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Touchstone Test Scripts for proxy testing between a client and server (such as in the test identified below) require an org key, user key or an ip address configured in the client setup in touchstone. We want anyone with access to the RI client to be able to run the touchstone test. The problem is that only the owner of the system or admins can add/change IP addresses, disallowing others to run the test.
Instead, it would be nice if the Touchstone client could be set up to accept user keys (which should be done after this issue is resolved) and the client RI could be configured in the app (along with the server URLs) and the user key would be sent in the header for USER_KEY header. The label for the entry of this user key should be clear as this would only apply to touchstone testing (a label like: USER_KEY (for touchstone proxy testing only)
The Touchstone Test Scripts for proxy testing between a client and server (such as in the test identified below) require an org key, user key or an ip address configured in the client setup in touchstone. We want anyone with access to the RI client to be able to run the touchstone test. The problem is that only the owner of the system or admins can add/change IP addresses, disallowing others to run the test.
Instead, it would be nice if the Touchstone client could be set up to accept user keys (which should be done after this issue is resolved) and the client RI could be configured in the app (along with the server URLs) and the user key would be sent in the header for USER_KEY header. The label for the entry of this user key should be clear as this would only apply to touchstone testing (a label like: USER_KEY (for touchstone proxy testing only)
/FHIRSandbox/DaVinci/FHIR4-0-1-PCT/01-AEOB-MRI/01-PCT-MRI-Scenario-GFE-Instit-Request-json
The text was updated successfully, but these errors were encountered: