< Back

Troubleshooting

Lab ordering and result retrieval workflows depend on complete data, valid test codes, and successful routing to external laboratories. Issues typically result from validation failures, compendium mismatches, credentialing gaps, or unexpected lab responses.

Troubleshooting focuses on four categories of failure: order submission, lab rejection, delayed or missing results, and response interpretation.

Order Submission Errors

Submission failures returned during validation indicate problems in the Requisition or ServiceRequest resource before the order is routed.

Common causes include:

  • Invalid test code: The code does not exist in the selected lab’s compendium
  • Missing required fields: Required elements such as subject, requester, or code are absent
  • Unsupported specimen: The specimen type is not allowed for the requested test
  • Incomplete address: Patient or facility address is improperly formatted or missing required lines
  • Multi-vendor test mix: The order includes tests from multiple laboratory catalogs. Health Gorilla enforces vendor-based routing and blocks composite orders before transmission.

To resolve common errors, review the test code against the appropriate lab compendium. Confirm that all required fields are present and conform to FHIR structure.

Rejection from Lab

An order may be accepted by the solution but rejected by the lab due to configuration or business rule conflicts.

Common rejection reasons include:

  • Ordering provider not enrolled: The provider is not credentialed with the selected lab
  • Facility mismatch: The ordering location is not recognized by the lab
  • Unsupported insurance: The payer is not accepted by the lab or is missing required fields
  • Internal lab error: The lab's system could not process the order due to system-side failure

To resolve: Confirm provider and facility setup with Health Gorilla. Re-submit the order once credentialing or configuration has been corrected.

Delayed or Missing Results

Accepted orders may experience result delays due to transport, lab processing, or result formatting issues.

Potential causes include:

  • Lab delay: The lab has not yet released the result
  • Result not linked: The result is available but not associated with the requisition
  • Format mismatch: The result was returned in a non-FHIR format and not normalized
  • Delivery failure: The result was generated but webhook transmission failed

To resolve: Query for results using FHIR parameters such as based-on or patient. Review webhook logs or use Provenance and meta.tag to identify orphaned or delayed results.

Debugging Tips

Include the following details when reporting an issue to Health Gorilla Support:

  • Full FHIR request and response (with headers)
  • Patient identifier used in the order
  • Requisition or ServiceRequest resource ID
  • Submission and retrieval timestamps
  • HTTP status code or lab rejection message

Providing complete context accelerates triage and resolution.

Summary

Resolution typically requires verifying FHIR payload completeness, compendium alignment, provider and facility registration, and correct linkage of results. Most issues can be resolved without lab escalation when order structure and routing are correctly configured.