Errors
Sometimes the Viewer Integration is not working as intended and shows an error message. In order to help you find the correct involved party to quickly resolve the error, we have made an overview of potential errors and steps to take to mitigate.
| Error message | Description | If you cannot solve it, then |
|---|---|---|
| Retrieving PatientOrder failed | Getting patient data from the external system (e.g., EMR) failed. | Contact external system (e.g., EMR) support |
| External system configuration not found | We can’t find the configuration to talk to the external system, so either something is misconfigured or the wrong config id is passed. | Contact external system (e.g., EMR) support |
| Unauthenticated | Something went wrong with the authentication, maybe token refresh failed. | Contact Luscii |
| Validation errors for missing or incorrectly formatted fields | These can take various forms but should be self explanatory | Contact external system (e.g., EMR) support |
| Script error | An error in Internet Explorer 11, which causes the app the stop functioning. | Contact Luscii with a screenshot containing (at least): - Error - Line - Char - URL |
| Network error, please try again at a later stage | This error appears if an essential request to Luscii can’t be made, this could be caused by the network (which should be communicated with the internal IT department), but we’ve seen this error being triggered for other causes. | Share the Trace ID (available on the error page) with Luscii. From the logs we can determine the actual cause and help you find the correct party to contact. |
| Claim: not found or still encrypted | The value is not available in the data, or it’s impossible to decrypt it. | Validate whether the value described in the error message is set for the patient. If that’s the case and it doesn’t work, retry after a couple of minutes. When the same message appears, contact the external system (e.g., EMR) for support. |
| Authentication failed - Consumer does not allow that token type | Requesting party cannot consume token. | Contact external system (e.g., EMR) support |
| Authentication failed - The requested token type is not supported | Requesting party does not have the rights to request this token | Contact external system (e.g., EMR) support |
| Authentication failed - Connection type is invalid or: Connectiontype claim of token is not valid | A token is requested for an environment (acceptance/production) but this is not allowed from the current environment. | Contact external system (e.g., EMR) support |
| Authentication failed - Resource ID invalid. or Authentication failed – Patient claims invalid | A citizen service number (BSN) is used in an environment that is not allowed or "onboarding" of the patient is not allowed in Zorgplatform management portal | Contact external system (e.g., EMR) support |
| Authentication failed - OID is invalid | Zorgplatform token server cannot (correctly) validate the requesting organization. This occurs, among other things, if the set OID does not match the certificate set in Zorgplatform. | Contact external system (e.g., EMR) support |
| The SAML response field is required | The Viewer Integration didn’t receive the identification for the Healthcare Professional or couldn’t extract it from the delivered data. Therefore it’s impossible to match the Application user with the Luscii User | Contact external system (e.g., EMR) support |
Updated about 2 years ago