Skip to main content
Version: 3.1.3

Alerting and Troubleshooting

Monitoring and troubleshooting are essential aspects of maintaining optimal performance and reliability in Centaur® Data Platform. Suppose any errors are present in the data flowing through the platform. In that case, the FHIR® resource isn’t persisted in the FHIR® Server with additional details in the rejected containers about the specific validation errors.

  • Monitoring: The Data Observability dashboard, a real-time monitoring tool, is a key component of the Centaur® Data Platform. It offers immediate insights into data processing, resource use, and system performance, enabling the swift detection and resolution of errors. Alerts setup through the dashboard provide details regarding inactive components, failures as well as success/errors details related to the HL7™ Engine.

  • Troubleshooting: The Data Observability dashboard, a real-time monitoring tool, is a crucial part of the Centaur® Data Platform's troubleshooting process. When unknown or invalid validation errors occur during data processing, the platform swiftly directs the related JSON files to the 'rejected' container in the specified storage account. This container serves as a repository for files containing errors, arranged chronologically in folders to highlight the error occurrence area. By integrating monitoring features with systematic file organization, the Centaur® Data Platform enables effective and efficient troubleshooting through the prompt detection and resolution of issues.

Error Codes​

The following is the list of potential error codes logged during runtime:
  • 171: Received Data is not in allowed ADT Trigger types
  • 172: Received HL7™ Data is failed at HL7™ Validator
  • 100: Duplicate File
  • 101: Converter XML / HL7™ / JSON Catch Error
  • 102: Invalid incoming Resource
  • 103: Converter JSON Catch Error
  • 104: Incoming Source Not Found
  • 105: Ignore Process
  • 111: Curation Catch Error
  • 112: Resource Identifier Not Found
  • 113: Ignore Ingestion
  • 114: Get Identifier Error when retrieving Unique Identifiers for incoming Resource
  • 115: Resource Not Found Reject
  • 121: IG Validation Error
  • 122: Validation Catch Error
  • 123: Resource Not Found Reject
  • 151: Resource Identifier Not Found Error
  • 152: Retry Rejected Resource
  • 153: Multiple Entries Found when trying to replace Reference ID
  • 154: Reference Handler Catch Error
  • 155: Resource Not Found Reject
  • 156: Network Related Error
  • 161: FHIR® Ingestion Phase 1 Catch Error
  • 162: FHIR® Ingestion Phase 2 Catch Error
  • 163: Invalid Operation
  • 164: Ignore Resource based on Primary / Secondary Source
  • 165: Duplicate Resource
  • 166: Resource Identifier Not Found when trying to fetch a resource from FHIR® Server
  • 167: Source Identifier Not Found when trying to fetch the source of found resource from FHIR® Server
  • 168: Connection Reset / Network Error
  • 169: Multiple Entry in FHIR® Server
  • 170: Inactive Resource based on Recorded Date
  • 171: Recorded Date Attribute Not Found either from Incoming / FHIR® Server Resource
  • 4XX | 5XX: FHIR® Server API Error / Storage Account REST Error / Converter API Error / IG Validation API Error