Zum Hauptinhalt springen

Output

Once the user finishes uploading images, the iframe runs the analysis and produces a DiagnosticReport. You have three options for consuming the result, depending on how deeply you want to integrate the output into your product.

  • API Endpoint: best for fetching the report data for processing or storage. Starting point: the API Endpoint page.
  • User Interface: best for displaying the report directly to the clinician. Starting point: the Embedded UI page.
  • JSON Schema: best for programmatic parsing (custom UI, EHR integration, analytics). Starting point: the JSON Formats section.
  • PDF Export: best for archival in EHR systems or sharing with external parties. Starting point: the PDF Export page.

Workflow Overview​

The typical sequence is:

  1. User finishes upload → iframe posts analysis_completed message.
  2. Your app stores the report ID from the message.
  3. Your backend calls the API endpoint to fetch the full report.
  4. You display/store the result in one of the formats above.

For a complete end-to-end walkthrough with code samples, see the Quickstart page.

Push delivery as an alternative

The workflow above describes the pull model. If you prefer Legit.Health to push the report to your server as soon as the analysis finishes, configure a callback URL: either the default one set during onboarding, or one overridden at the iframe level via companyCallbackUrl (see the Customize page).

Next Steps​

  • Need the API endpoint details? See the API Endpoint page.
  • Want to show the report in your UI? See the Embedded UI page.
  • Building a custom solution? See the JSON Formats section.