Troubleshooting
This table shows data processing and integration errors, causes, and recommended actions:
| Error or issue | Possible cause | Resolution |
|---|---|---|
| Group not found | The patient group does not exist in Azure FHIR Store or AWS HealthLake. | Verify patient group configuration. Specify the correct Group ID. |
| Authentication failed (HTTP 400) | Azure FHIR Store data source is not configured correctly. Client ID, Tenant ID, or Scope is incorrect. | Verify data source configuration. Specify the correct Client ID, Tenant ID, and Scope. |
| Authentication failed (HTTP 401) | Azure FHIR Store data source is not configured correctly. OAuth endpoint, certificate thumbprint, or subscription key is incorrect. | Verify data source configuration. Specify the correct OAuth endpoint, certificate thumbprint, and subscription key. |
| Kickoff failed (HTTP 404) | Azure FHIR Store data source is not configured correctly. Base API or location path is incorrect. | Verify data source configuration. Specify the correct Base API and location path. |
| Private key load failed | Azure FHIR Store data source is not configured correctly. Private key is incorrect. | Verify data source configuration. Specify the correct private key. |
| Access token retrieval failed | AWS HealthLake data source is not configured correctly. Token endpoint, client ID, client secret, or scope is incorrect. | Verify data source configuration. Specify the correct token endpoint, client ID, client secret, and scope. |
| Datastore not found or interaction not supported | AWS HealthLake data source is not configured correctly. Datastore endpoint is incorrect. | Verify data source configuration. Specify the correct datastore endpoint. |
| Role assumption not authorized | AWS HealthLake data source is not configured correctly. Datastore access role ARN is incorrect. | Verify data source configuration. Specify the correct datastore access role ARN. |
| Output S3 bucket not found | AWS HealthLake data source is not configured correctly. S3 bucket URI is incorrect. | Verify data source configuration. Specify the correct S3 bucket URI. |
| KMS key not found | AWS HealthLake data source is not configured correctly. KMS key ID is incorrect. | Verify data source configuration. Specify the correct KMS key ID. |
| Role assumption failed | AWS HealthLake data source is not configured correctly. S3 access delegate role ARN is incorrect. | Verify data source configuration. Specify the correct S3 access delegate role ARN. |
| No files downloaded | AWS S3 data source is not configured correctly | Verify AWS S3 data source configuration. |
| S3 bucket not found | AWS S3 data source is not configured correctly. S3 bucket URI is incorrect. | Verify data source configuration. Specify the correct S3 bucket URI. |
| Access key invalid | AWS S3 data source is not configured correctly. Access key is incorrect. | Verify data source configuration. Specify the correct access key. |
| Signature mismatch | AWS S3 data source is not configured correctly. Secret key is incorrect. | Verify data source configuration. Specify the correct secret key. |
| Message purged | The anonymizer removed all content from the inbound file. | Updatethe anonymizer configuration to retain required FHIR resource types. |
| Extract job timeout | The extract process failed while composing the longitudinal patient chart, possibly due to bundle size. | Contact Infor Support for further investigation. |
| File not found on S3 | No data is loaded for the patient. The longitudinal patient chart is not extracted. | Verify the data source and selected database. Ensure FHIR resources exist for the patient. |
| Patient resource not found | The longitudinal patient chart does not contain the patient resource. | Verify the data source. Ensure FHIR patient resources exist. |
| Internal server error (500) | Measure calculation code contains defects. | Contact Infor Support and provide the measure code. |