Integration manual
How Legit.Health is integrated
Legit.Health is integrated as an app: you embed it as an iframe, and it comes with its own API. Your users get the complete clinical interface, and your backend receives every report as JSON, HL7 FHIR or PDF.
The app (iframe), with its API
Embedding the iframe gives your users guided capture, the image quality check acted on, the report the Instructions For Use describe with its regulatory label, finished severity scores, a PDF, a patient mode and the AI assistant, in your colours and your users' language. Its API tells the page around it when a report is ready, with the report's identifier, and your backend fetches the report from our endpoint in the format you choose; we can also push it to a callback URL you configure. The Iframe section documents every parameter, callback and format.
Integrating via the device API, without the app
The medical device behind the app also has an API of its own, documented in the installation manual of the instructions for use. Integrating through it is perfectly possible, but it puts the work the app does on you: the instructions for use still require an interface that shows the top five, the referral recommendation, the malignancy gauge and the six safety indicators; the image quality check, the entropy and the severity scores become yours to handle; the app's own features are lost; and usage is counted per call rather than per report. The implementation page explains each point and when it makes sense.
Embedding the iframe and personalising it takes ~ 15 minutes; saving the JSON response to your database takes less than 1 day; building a full clinical workflow on top of the report data takes less than 1 week. See the iframe time-estimate breakdown in the Iframe overview page.
Our integration team provides dedicated support throughout the whole process.